Wednesday, 25 October 2017

FUSION HCM: HCM DATA LOADING OVERVIEW

HDL:
HCM Data loader prerequisite setup steps:
 1) Configure HCM Data Loader
    and set the Data loader scope : Full mode
 2) Add Human Capital Management integration specialist Role and/or Human capital management application Administrator
 3)Download the HCM dataloader documentation template from oracle support.
    `BusinessObject Documentation  DOC ID :2020600.1
 4) Identify the mandatory columns to load Business Object.
 5)Prepare .dat file
 6) Save .dat 
 7) Zip the file
 8) Set the source system owner in manage common Lookup: HRC_SOURCE_SYSTEM_OWNER
 9) Go to navigator work area under My workforce section Select Data Exchange --> HCM DATA LOADER --> Import and Load data -->Import file--> Submit Business Object
  
HDL supported business objects:
Global HR: 
 Action reasons, actions,locations, grade,grade rate,grade ladder,jobfamily,job,organization,position,department,department tree node,worker, person contact,person contact relationship.
Global payroll:
  Element entry
Talent:
   Educational establishment, Educational establishment translations,Rating model, rating model translation,content items, goal,goal plan, goalplan set,talent pool,talent profile,content item relationship 
 compensation:
 Salary, salary basis
 Absence:
 Person accrual detail,person entitlement detail,person absence entry
 Time and labor :
 Time record group.

HDL Commanads:
 1) META DATA :  Business object component and the attributes for which values are included in the data file.
 2) MERGE :Data to be added to oracle fusion Merge : Create/Update
 3) DELETE :Business objects components to be removed from Fusion HCM.
 4) SET :Enables override of the default behaviour of the file.
 5) COMMENT: Add comment in the data file

FUSION HDL KEYS :
 Use any of the below HDL Keys:
 1)GUID: Global Unique Identifier . When we create new record in the cloud system it will create automatically.
         It's unique for acrsoss the business objects.
 It's Stored as Hexadecimal value format.
 Unique across all objects.
 Held in Integration Key Map.
 2)Surrogate ID: When we create new record in cloud system it will create automatically.
         It's stored as numeric values.
 It's unique for specific business objects.
 Held on the object
 3) User Key : Primary key.
         User Readable and Generated Keys
         Natural values
         One or many attributes
         Sometimes alternatives
         Sometimes updateable
         Held on the object definition
 4) Source Key : Source System Key Information 
         Two values combined Source system ID and Source system owner
         Held in Integration Key Map

 
Example of Creating .dat file for Grade and Gradestep Business Object:

METADATA|Grade|EffectiveStartDate|SetCode|GradeName|GradeCode|ActiveStatus|ActionReasonCode|SourceSystemOwner|SourceSystemId
METADATA|GradeStep|EffectiveStartDate|GradeStepName|GradeStepSequence|CeilingStepFlag|GradeCode|SetCode|SourceSystemOwner|SourceSystemId
MERGE|Grade|2016/01/11|COMMON|GE_Z|GE_Z_CODE|A|RMZ_GRADE_REASON|RMZ_DATA|E8
MERGE|Grade|2016/01/11|COMMON|GE_Z1|GE_Z_CODE1|A|RMZ_GRADE_REASON|RMZ_DATA|E118
MERGE|GradeStep|2016/01/11|GEG_STEP1|10|N|GE_Z_CODE|COMMON|RMZ_DATA|E9
MERGE|GradeStep|2016/01/11|GEG_STEP2|20|Y|GE_Z_CODE|COMMON|RMZ_DATA|E19
MERGE|GradeStep|2016/01/11|GEG_STEP3|30|N|GE_Z_CODE|COMMON|RMZ_DATA|E119
MERGE|GradeStep|2016/01/11|GE_STEP1|1|N|GE_Z_CODE1|COMMON|RMZ_DATA|E9456
MERGE|GradeStep|2016/01/11|GE_STEP2|2|Y|GE_Z_CODE1|COMMON|RMZ_DATA|E19546

0 comments:

Post a Comment