Introduction

In some of the previous articles like Sample HDL Files for Loading Worker Records in Oracle Fusion HCM Cloud Application and Applying UPDATE and CORRECTION Mode Changes to PersonName Metadata using HDL Files In Oracle Fusion HCM Cloud Application we have seen how we can import and update (both correction and update mode changes) records from a 3rd party system to Oracle HCM Cloud Application . We have used the Source Keys (Source System Owner and Source System ID) for the same. However, couple of  questions which does troubles a lot of consultants at times are:

1. How to update/correct HCM records which were created from UI (Manual Entry)?

2. Can we use Source Keys for the same ?

In thsi post we will try to find answers to the above questions. For this we would need to perform the below steps

1. Create a Worker Record From Application (Manually using UI)

2. Fetch the relevant keys namely GUID, SourceSystemOwner and SourceSystemID using BI query

3. Try to update (correction mode) to the Worker Record (DateofBirth field for this example) using GUID approach and verify results

4. Try to update (correction mode) to the Worker Record (DateofBirth field for this example) using SourceKey approach and verify results

So without much ado let’s begin.

Creating Worker Record From Application UI

As a first step we would login to the Oracle Fusion HCM Cloud Application with an user having appropriate privilege and navigate to (Navigator -> My Workforce -> New Person). We would populate the required details and submit the request (as shown in sceenshot below)

We could see that the Person Number 5006 is generated once the request is submitted.

A quick look at the Personal Details of the worker record reveals that the Date of Birth is 4/12/1998

Fetch Relevant Keys using BI Query

In this step we wil run a BI query to fetch the revelant keys. The BI query used is mentioned in the below table

The BI Data model would appear as below:

And the data retrieved is as below:

GUID Approach

In this approach we will use the GUID to make corrections to the Worker Record. For this example we will make changes to the Date of Birth field where we will change the current value of 4/12/1998 to a new value of 12/10/1995. The data file will look as below:

When we verify the load from application using “Import and Load” the load is successful

A quick verification on the application UI confirms that the changes have been records in the system

SourceKey Approach

In this approach we will use Source Keys (Source System Owner and Source System ID) and will try to

Change the Date of Birth value from 12/10/1995 to 7/12/1994

The data file would look as below:

The “Import and Load” page shows the load is successful

And a quick look at the Application UI (Manage Person shows that the Date of Birth field has got

Changed to the new value)

Summary

From the above we can clearly summarized that we can use either of Source Keys or GUID to make

Changes to records created via UI. The important point to note however is to that one needs to fetch the

GUID value and Source System ID value . The Source System Key for all records created via UI is

FUSION.

Ashish Harbhajanka

Add comment