Mass Legal Employer Change in Oracle Fusion through HDL
Hi friends, we are going to discuss about how we can Mass change Legal Employers for employees in Oracle Fusion through HDL. We will share the detail Oracle Fusion HDL script which helps to mass change employees legal employer in oracle fusion. If you have a requirement to change the legal employers for hundreds of employees in oracle fusion , then you can refer this HDL script for that. HDL is known as HCM data loader which helps to upload/update the employees details. HDL we do use for mass upload and mass update the employee details in oracle fusion. In this post , We are going to share the HDL script which we do call as a Global Transfer HDL script which helps to change the legal employer for employees. We can use the same script to mass change the legal employers too. Please find below the complete detail about Mass Legal Employer Change in Oracle Fusion through HDL.
What is Global Transfer(Legal Employer Change) in Oracle Fusion?
In Legal Employer Change , We do transfer the Employees from one LE to another LE. Global Transfer is the combination to two steps. In first step , Employees Old work relationship got terminated with old LE and System creates the new work relationship/assignment with new LE.
Global Transfer process known as Legal Employer change through front end application is very simple process. If we have few Business transfer cases , then we can follow the manual approach and change the Employee LE through Global Transfer in Oracle Fusion. But we have mass volume of employees for global transfer then we have to use the HDL tool.
Step by Step to Mass change the legal employer through HDL
Step 1:-
Sample HDL script for Employee Global Transfer in Oracle Fusion.
If we want to do Global Transfer any Employees , We have to use the column 'GlobalTransferFlag' in WorkRelationship metadata.
If we are doing global transfer for any employee , We cannot use the existing Source System ID for WorkRelationship , WorkTerms, Assignment as well we need to use the new Assignment number(We cannot use the existing Assignment Number).
Note : We have to provide the New Legal Employer Name , New Business Unit Name in Work Relationship, WorkTerms and in Assignment to which we are transferring this employees.
METADATA|WorkRelationship|PersonId(SourceSystemId)|PersonNumber|LegalEmployerName|DateStart|WorkerType|PrimaryFlag|SourceSystemOwner|SourceSystemId|TerminateWorkRelationshipFlag|ActualTerminationDate|ActionCode|ReasonCode|ReverseTerminationFlag|GlobalTransferFlag
MERGE|WorkRelationship|XXEMPNO|XXEMPNO|NEW LE NAME|2020/06/28|E|Y|TESTOWNER|XXEMPNO_India_T|||HIRE|||Y
MERGE|WorkRelationship|XXEMPNO2|XXEMPNO2|NEW LE NAME|2020/06/28|E|Y|TESTOWNER|XXEMPNO2_US_T|||HIRE|||Y
Step 2:-
METADATA|WorkTerms|PersonNumber|PeriodOfServiceId(SourceSystemId)|ProposedUserPersonType|LegalEmployerName|ActionCode|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|PrimaryWorkTermsFlag|SourceSystemOwner|SourceSystemId
MERGE|WorkTerms|XXEMPNO|XXEMPNO_India_T|Employee|NEW LE NAME|GLB_TRANSFER|2020/06/28|4712/12/31|1|Y|Y|TESTOWNER|XXEMPNO_W_T
MERGE|WorkTerms|XXEMPNO2|XXEMPNO2_US_T|Employee|NEW LE NAME|GLB_TRANSFER|2020/06/28|4712/12/31|1|Y|Y|TESTOWNER|XXEMPNO2_W_T
METADATA|Assignment|PersonNumber|ActionCode|EffectiveStartDate|EffectiveEndDate|EffectiveSequence|EffectiveLatestChange|AssignmentType|HourlySalariedCode|AssignmentStatusTypeCode|PeriodOfServiceId(SourceSystemId)|WorkTermsAssignmentId(SourceSystemId)|WorkerType|PersonTypeCode|AssignmentNumber|PrimaryAssignmentFlag|PrimaryFlag|LegalEmployerName|BusinessUnitShortCode|AssignmentCategory|DefaultExpenseAccount|DepartmentName|JobCode|PositionCode|LocationCode|SourceSystemOwner|SourceSystemId
MERGE|Assignment|XXEMPNO|GLB_TRANSFER|2020/06/28|4712/12/31|1|Y|E|H|ACTIVE_PROCESS|XXEMPNO_India_T|XXEMPNO_W_T|E|Employee|EXXEMPNO-2|Y|Y|NEW LE NAME|NEW BU NAME|FR|||||00010|TESTOWNER|XXEMPNO_XXEMPNO_A_T
MERGE|Assignment|XXEMPNO2|GLB_TRANSFER|2020/06/28|4712/12/31|1|Y|E|H|ACTIVE_PROCESS|XXEMPNO2_US_T|XXEMPNO2_W_T|E|Employee|EXXEMPNO2-2|Y|Y|NEW LE NAME|NEW BU NAME|FR||||||TESTOWNER|XXEMPNO2_XXEMPNO2_A_T
 |
| Mass Legal Employer Change in Oracle Fusion through HDL |
Step3:-
Once we have prepared these two metadata for Terminated employee to rehire we need to save this meta data in Worker.dat file.
 |
| Mass Legal Employer Change in Oracle Fusion through HDL |
Then We need to put this Worker.dat file in the Worker.zip folder. After this We need to put this Worker.zip folder in the Cloud Application.
To Import this Worker.Zip file we need to follow these steps as below.
 |
| Mass Legal Employer Change in Oracle Fusion through HDL |
 |
| Mass Legal Employer Change in Oracle Fusion through HDL |
 |
| Mass Legal Employer Change in Oracle Fusion through HDL |
Once the zip file have been prepared. Then We need to go Data Exchange.
Step 10:-
Here below we need to go to Data Exchange.
Navigator ==> My Client Groups ==> Data Exchange
 |
| Mass Legal Employer Change in Oracle Fusion through HDL |
Step 11 :- Then Data Exchange ==> HCM Data Loader ==> Import and Load Data
 |
| Mass Legal Employer Change in Oracle Fusion through HDL |
 |
| Mass Legal Employer Change in Oracle Fusion through HDL |
1 comments:
Your website is very beautiful or Articles. I love it thank you for sharing for everyone. Workflow en la nube
Post a Comment