Tuesday, September 15, 2020

Employee Conversion Strategy for Oracle Cloud


Oracle Workforce Structure should be configured before the employee conversion.

  • HCM Organizations (Business Units , Legal Employers ,Departments)
  • Locations ( Employee assignment address)
  • Actions ( Hire, Re-Hire, Data Change, Assignment Change )
  • Jobs
  • Action and Action reasons for Assignments need to be mapped from source to target or needs to be created as per the requirement.
  • Employee types to be converted from legacy system need to be determined. eg: Permanent, Contractors.
  • All the active employees will be converted as part of the conversion.
  • Assignment number for Employees will start with “E” (E001) and Work Terms with “ET”(ET001).
  • Assignment number for Contingent Workers will start with “C” (C001) and Work Terms with “CT”(CT001).
  • Oracle HCM accepts only one company transfer per day. So for employees having more than one company transfers in a day, data needs to be cleaned up in the source system or new logic needs to be implemented during conversion.

Employee User/Role assignment

  • Auto Role Provisioning needs to be finalized prior to employee conversion in order for employees to login into Oracle cloud. Generally “Employee” is the default role assigned to all converted workers.
  • User Account naming convention needs to be decided for SSO (eg: Email id, Employee id , combination of First name and Last Name )
  • Contractors requiring access to self service also need to be converted as users.
Person Number Generation/Assignment Option:



Terminated Employees Conversion:
Decision will be made as per the following scenarios whether terminated workers will be converted from legacy system to cloud



Data Load Sequence: 



No comments:

Post a Comment