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: 

How To Plan For A Successful Data Conversion In Your Move to Oracle Cloud ERP

Many organizations are moving to Oracle Fusion cloud services, taking advantage of the enhanced levels of support and overall reduction in cost of ownership the product offers. If your organization is preparing to implement Fusion ,in this post, I will focus on one of the big ones, the impact of which can often be underestimated: Data Conversion for Oracle Cloud ERP.

No matter which system you’re moving away from (PeopleSoft, Oracle EBS, etc.), exporting the data you need and loading it to Fusion will be a tedious and time-consuming effort (just as any data conversion effort from one system to another would be). However, with proper planning it can be executed logically and methodically, minimizing potential roadblocks and the risk of unpleasant surprises.

Because Cloud ERP is a SaaS product, you will not have access to update any of the tables yourself and instead must leverage the data conversion tools Oracle provides for populating Fusion with your organization’s data. The primary tool you’ll work with is File-Based Data Loader (FBDL), HCM Data Loader (HDL) and it’s critical to take the time upfront to understand how the tool works and which business objects it supports .

I will be following up on a few data conversion approaches that can be taken to reduce time and effort spent on converting data with the use of open source tools. We can use the tools to do data profiling of the data upfront to report on data quality and build conversion logic using ETL based approach to make the transition smooth during extracting data.

Understanding Oracle Cloud HCM Transaction Design Studio

The Transaction Design Studio is available within the HCM Experience Design Studio in its initial BETA phase. There are limited features and actions available to configure at this time. Transaction Design Studio It allows you create rules to configure transactions and pages in the responsive user designed pages. You can change how sections and fields are displayed, based on the user’s role and the employee’s business unit or legal employer. You can:

• Control the visibility of regions and sections on the page.
• Control the visibility for attributes within a page, region, or a section.
• Change the required status of optional attributes.
• Control the availability of the questionnaire page for actions that use the guided process design.

You can create one or more rules for any page available in the Transaction Design Studio to manage your business needs. For example:

• Make different fields visible and required in the new hire flow for employees in the US and employees in other countries.

• If employees in the US don’t get salary increases as part of a promotion, hide the salary and compensation regions for US employees only, while making these regions available for employees in other countries when being promoted.

• Hide the Ethnicity and Religion fields from the Personal Details page for countries or legal employers that you don’t want to store that information. You can still modify the person spotlight and upload images for pages that use the HCM landing page design.

BUSINESS VALUE OF TRANSACTION DESIGN STUDIO

Using Transaction Design Studio is easy. The design is like any other newly designed responsive page for a seamless experience. And when configuring a page or transaction, the sections and fields map directly to the user-facing page so you know exactly what you’re looking at and configuring. Once you save a rule, you can quickly test it by accessing the page from global search or quick actions to see the results of your configured rule. There’s no more guessing what part of the page you need to edit or needing to use complex EL expressions to vary the page as when using page composer. You don’t need a technical resource to create or maintain your rules, so as business rules change, your HR analyst can make the change themselves. Really complex business requirements may require you to use page composer, but in general, configuring your pages for different populations of employees is just a lot simpler now.

What’s New in Oracle Cloud HCM Global Payroll for 19C

Quick Retroactive Pay for Single Worker

It is now possible to Run Quick Retroactive Pay for the Single Worker task to enable the processing of Retroactive pay. This task adds the retroactive element entries and the pay period for which retroactive pay is applicable and may be added to an existing flow or a new flow.

Support for Latest Person Search on Classic Payroll Pages

The latest Person Search feature that was existing for responsive payroll pages has now been extended to the Classic pages in Payroll as well.

Read-Only Version of Manage Payroll Relationship

The Manage Payroll Relationship page can now be accessed in a Read-only mode.

Display Person Number on Personal Payment Method, Payslip, and Year-End Documents

Personalization can now be used to include the Person Number on the personal information page headers for the Personal Payment Method, Payslip as well as year- end documents.

Removal of Unprocessed Payroll Element Batches

When an element entry created by the HCM Data Loader is rolled back, the application also rolls back events and notifications that are not consumed or processed based on the following:

• If the event has an unprocessed status, then the event is removed. However, the event is not removed if it has been already processed, such as by retroactive pay.
• If the batch action created an element entry, then the event is removed. Other types of element entry events, such as an update element entry event, are not supported.
• If the element entry has not been updated, then the event is removed. However, the batch event is not deleted if the element entry has been updated, such as a change in input value.
• If the element entry is created by HCM Data Loader.

Display All Hours in Payroll Reports

The following reports have been enhanced with an option to report hours from Supplemental Earnings and other element classifications in addition to that from Regular or Standard Earnings and Absence earnings in earlier versions:

1. Gross-to-Net Report
2. Payroll Activity Report
3. Payroll Register
4. Payroll Balance Report

Payroll and Time Definition List of Values REST API

In 19C, REST APIs have been provided to configure real time and up-to-date list of values for selecting Payroll and/ or overtime period that is to be assigned to an Employee.

For the Payroll Definition list of values, use payrollDefinitionsLOV and for Time Definition List of values, use payrollTimeDefinitions