Global Transfer In and Out

Mass Legal Employer Change\ Global Transfer

When we need to transfer multiple employees to the same legal employer, use the Mass Legal Employer Change task. This accomplishes the transfers in a single batch.

It uses the Local and Global Transfer process to copy the selected employees' assignment and work relationship data from the source to the destination work relationship. The data is copied as of the global transfer date along with any future-dated changes.

 

 

 

In the Mass Legal Employer Change flow, select the checkbox Copy future assignment updates to copy future changes on employment data.

 

After hitting Submit, It kicks off a schedule process 'Perform Mass Update'

Revisiting the Mass Legal Employer quick actin link would then show up a Dashboad of the bulk requests processed. 

It gives the details of the run and the error list.


 

If the proces is Success, we can requery the records in the Selection Criteria and see that the Global Transfer Action is now Performed.

 

Things to consider:

  • Use this task to transfer people from different legal employers into the same target legal employer.

  • Use this task when changing legal employers within the same country or legislation. If you use this task to mass change legal employers across legislations, it doesn't copy the data for salary and payroll. Additionally, there may be issues with certain personal data elements that aren't copied across legislations.

·       You can override certain assignment attributes from the source assignment that are common and apply to the set of workers transferring to new legal employers.

·       For example, these attributes can include the business unit, department, and location. However, you can't override assignment attributes like job, grade, and position because they are unique and may differ for each worker in the destination assignment.

·       All types of direct reports are copied to the assignment, which gets newly created during the Mass Legal Employer Change process.

·       Pending and draft performance goals aren't transferred to the new assignment when you do a mass legal employer change. Therefore, you must make sure approvals for such performance goals are complete before you perform the transfer.

·       You can't do a mass legal employer change for an employee that has:

o   Future-dated global transfer or global temporary assignment change

o   Pending transaction awaiting approval that involves an assignment change

o   Work relationship start date with the same as the effective date of the transfer


Exceptions to Handle

  •  Terminations 
    •       At times if we are doing a back dated Transfer we cannot search for the Employee to select for Transfer. In such case, we need to Reverse Terminate the Employee, Process the Transfer and put back the Termination

  • Absences 

    • Future Absences applied in the system will be Withdrawn by the Mass LE process. But not automatically Reapplied in the new LE.

Comments

Post a Comment

Popular posts from this blog

Oracle Cloud HCM Open Ended Absences Update

  Oracle Cloud HCM Open Ended Absences       In Oracle Cloud HCM, when there exist open ended absences like Maternity and Sickness and Employee is terminated, it is seen that there is no end date updated to these open absences as of Termination Date. This leads to ambiguity in reporting and payroll To address this issue, worked on an automation process which will pick such records and put an end date same as the termination date.   Design Steps   1.       Build a BIP report to list the Open ended absences for Terminated employees 2.      Write the Bursting definition to feed the BIP report output to Extract 3.      Desing the ETF template to build the HDL Template for End dating Open Absence 4.      Design a HCM Extract that will take the output fed from BIP Report and Auto Loads as   HDL process 5.   ...
Read more

Oracle HCM Absence Orphan Records

Image
Sometimes We come across a less known Error while submitting an Absence in Oracle Cloud HCM with an Error Code ANC-3405194 Likely caused when  Update of Accrual plan is done after an accrual process has already run till a date in future. OR  Entering accrual via HDL in a previous plan period and missing to run calculate accrual. This is Resolved when we Delete the Orphaned records found by Below Query Query to identify the Orphan Absence Records in the System SELECT  per_accrual_entry_dtl_id,         ppl.person_number       ,         ass.assignment_number   ,         plans_tl.NAME           ,         TYPE                    ,         procd_date FROM    fusion.anc_per_acrl_entry_dtls acrl_dtls ,         fusion.per_all_people_f ppl  ...
Read more
Image
           Deploying an AI agent on Redwood Page                                    1.     N avigate to the AI Agent Studio from the Tools Menu             2.    Select any available delivered AI agent and Copy it to be used by    your business.                         3.     Run it to see all the Profiles and Config are good.         4.     Publish the AI Agent              5.       Navigate to My Client Groups -> Guided Journeys      6.       Create New Journey      7.       Create Draf...
Read more