Saturday, 14 October 2017

FUSION HCM : OVERVIEW OF HCM DATA MIGRATION

Fusion Inbound Interface :

1. Extract the data from third party system

2.Transform into HDL/Spreadsheet/Payroll batch file format
3.Zip the data file
4. Place the file in fusion UCM.
5. Run the HDL/Payroll batch loader

HCM Data Loading:

1. objects can refered by their name or Fusion ID
2. wider range of objects supported
3. Deletion Supported
4. Incremental load supported

FBL:

1. Generating the GUID
2. Limited object support
3. Deletion not supported
4. Incremental load  not supported

Spreadsheet data loader :

1. Less volume of Data
2. Each object have ceperate excel for each task like create/update

Payroll Batch Loader:

1. Loading  payroll related objects

Keys : 
Integration Key map Table : ORACLE Fusion ID , Source System ID 
Belonging object Application Table : Oracle Fusion SurrogateID, User Key .

Enterprise setup data:

Setup data :
Master data :

Before starts the data migration manual setups required for below data:

Business object                             Task
Application reference data set Manage Reference data sets
Assignment Status Type Manage Assignment status
Business Unit Manage Busibness Unit
Content Type Manage Profile Content Types
Currency code Manage Currencies
Element Type Manage elements
Legal Entity Manage Legal entity
Official Language Code Manage Languages
Profile Type Manage Profile types
Schedule Manage Work Schedules
Person Types Manage Person type
Lookup Type

Worker Data Loading:

Person Address
Person Email
Person name
Person Legislative Data
Person Phone
Person Visa
Work Relationship  ---> Employment Terms ---> Assignment 
Worker extra information

Roles :

Human capital management application Administrator
Human Capital management Integration Specialist
 above 2 are job roles
 Duties are :
 HCM data load Duty
 HCM data load error managemnt Duty
 File import and export management duty

HCM Data Loader Keys :
Keys are used for unique identification of :

  1.    Business object component
  2.    Parent business object component
  3.    Any other object referenced by a business object component.

Whether you are planning to implement coexistence with ongoing data sync, one time conversion or ongoing  integrations you must select the right key type to identify records uniquely. If you select a wrong key type then it may result in huge amount of rework down the line. 
So please pay special attention to various key types and see what makes most sense in your situation,

Supported Key Types:
HCM Data Loader (HDL) supports 4 different types of keys as listed below (in the order of key resolution sequence)

GUID – Oracle Fusion Global Unique ID
Oracle Fusion Surrogate ID
Source Keys
User Keys

Oracle Fusion GUID:

  • Integration Key Generated by Fusion
  • Generated in Oracle Fusion when a record is created
  • Hexadecimal value
  • Unique across all objects
  • Held in Integration Key Map


Oracle Fusion Surrogate ID :

  • Fusion Generated Unique ID
  • Generated in Oracle Fusion when the record is created
  • Numeric value
  • Unique only for the object type
  • Held on the object

Source Keys :

  • Source System Key Information
  • Two values combined: SourceSystemOwner , SourceSystemID
  • Held in Integration Key Map

User Keys :

  • User Readable and Generated Keys
  • Natural values
  • One or many attributes
  • Sometimes alternatives
  • Sometimes updateable
  • Held on the object definition

Notes:-
1.    You can use surrogate IDs when updating objects, but the IDs may not be readily available to Oracle HCM Cloud users. 
2.    Default source keys are generated only if you don't supply a source key when creating an object. 
3.    You can't use user keys alone when updating some objects because their values are subject to change.
4.    Keys that aren't held on the object exist in the Integration Key Map table.

Integration Key Map table

Keys that aren’t held on the object are stored in the HDL integration key map table - HRC_INTEGRATION_KEY_MAP. You should be able to use BIP to fire up a SQL statement and view the contents of this table. e.g. 

select OBJECT_NAME, SOURCE_SYSTEM_ID, SOURCE_SYSTEM_OWNER, SURROGATE_ID, RAWTOHEX(GUID) guid from fusion.HRC_INTEGRATION_KEY_MAP WHERE SOURCE_SYSTEM_OWNER ='STUDENT1‘

Fusion GUID: System generated GUID
Source Key:  Source System Owner is the reference to source application like PS or EBS, Source System Key is the actual key\id provided in the Location.dat file. 
Surrogate ID: System generated. In this case it is the primary key from locations record. e.g. select * from PER_LOCATION_DETAILS_F_VL  where location_code = 'STUDENT1 Location1‘   (Result Location ID = 300000001572671)
User Key:- Best way to get this info is the Business Object Documentation from MOS or other option is UI as shown below. Online page should highlight user keys with * 

Classification of keys based on storage location:
Integration Key map Table : oracle fusion guid,Source system id
Belonging Object application table : Oracle fusion surrogate id, ser key

File instruction tags :

METADATA: Business object component and the attributes for which values are included in the data file.
MERGE: Data to be added to oracle fusion Merge : Create/Update
DELETE :Business objects components to be removed from Fusion HCM.
SET : Enables override of the default behaviour of the file
Comment : Add comment in the data file

Line structure :

Definition : METADATA|file descriminator|Atttribute1| Attribute2|...
Data :       MERGE|File descriminator|Value1|Value2|Value3|...
Control :    SET FILE_Delimeter,
Comment :    COMMENT This file contains data related to worker and batch no 12

0 comments:

Post a Comment