HDL Template to Accrual Plan Enrollment of Worker

HDL Template to Accrual Plan Enrollment of Worker

Please find the below sample template :

File Name - PersonAccrualPlanEnrollment.dat

METADATA|PersonAccrualPlanEnrollment|PersonNumber|WorkTermAsgNum|PlanName|EnrtStDt|SourceSystemId|SourceSystemOwner

MERGE|PersonAccrualPlanEnrollment|XXTEST22|XXTEST_WRKTERM22|Sick|2021/01/01|XXTEST_SICK1|XXTEST

HDL Template for Global Temporary Transfer of Worker

For this use Worker.dat

Please find the below sample template :

METADATA|WorkRelationship|PersonNumber|LegalEmployerName|DateStart|ActualTerminationDate|PrimaryFlag|WorkerNumber|WorkerType|RehireRecommendationFlag|OnMilitaryServiceFlag|ActionCode|ReasonCode|DateOfDeath

MERGE|WorkRelationship|XXTEST9|US1 Legal Entity|2018/01/01||Y|XXTEST9|E|Y|N|GLB_TEMP_ASG||

MERGE|WorkRelationship|XXTEST9|UK Legal Entity|2019/01/01||N|XXTEST9|E|Y|N|GLB_TEMP_ASG||

METADATA|WorkTerms|ActionCode|PersonNumber|LegalEmployerName|DateStart|WorkerType|AssignmentNumber|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentType|PersonTypeCode|AssignmentStatusTypeCode|BusinessUnitShortCode|PrimaryWorkTermsFlag|SystemPersonType|ReasonCode

MERGE|WorkTerms|GLB_TEMP_ASG|XXTEST9|US1 Legal Entity|2018/01/01|E|XXTEST_WRKTERM9|2019/01/01|4712/12/31|Y|1|ET|Employee|SUSPEND_PROCESS|US1 Business Unit|Y|EMP|

MERGE|WorkTerms|GLB_TEMP_ASG|XXTEST9|UK Legal Entity|2019/01/01|E|XXTEST_WRKTERM9-2|2019/01/01|4712/12/31|Y|1|ET|Employee|ACTIVE_PROCESS|UK Business Unit|Y|EMP|

METADATA|Assignment|ActionCode|PersonNumber|LegalEmployerName|DateStart|WorkerType|AssignmentNumber|WorkTermsNumber|EffectiveStartDate|EffectiveEndDate|EffectiveLatestChange|EffectiveSequence|AssignmentType|PersonTypeCode|AssignmentStatusTypeCode|BusinessUnitShortCode|GradeCode|JobCode|LocationCode|DepartmentName|ManagerFlag|LabourUnionMemberFlag|ReasonCode

MERGE|Assignment|GLB_TEMP_ASG|XXTEST9|US1 Legal Entity|2018/01/01|E|XXTEST_ASSIGN9|XXTEST_WRKTERM9|2019/01/01|4712/12/31|Y|1|E|Employee|SUSPEND_PROCESS|US1 Business Unit|XXTEST_GRADE1|XXTEST_CFO|XXTEST_LOC12|XXTEST Department1|Y|N|

MERGE|Assignment|GLB_TEMP_ASG|XXTEST9|UK Legal Entity|2019/01/01|E|XXTEST_ASSIGN9-2|XXTEST_WRKTERM9-2|2019/01/01|4712/12/31|Y|1|E|Employee|ACTIVE_PROCESS|UK Business Unit|XXTEST_GRADE1|ADM|XXTEST_LOC12|XXTEST Department1|Y|N|

 

Top 50 Fusion HCM Technical Questions - Part 2

 Top 50 Oracle Fusion HCM Technical Questions - Part 2

Top 50 Oracle Fusion HCM Technical Questions - Part 1 Click 

Q) Mandatory Records to Load Worker File for NEW Hire?

->  Worker , Person Name , Person Legislative Data, Assignment, Work Term.

Q) Sequence of WorkStructure Business Object While Load?

-> Work Structure Business Object loads in below sequence 

     1. Location

     2. Grade

     3. Job

     4. Orgnization

     5. Position

Q) If any Location is end dated and same location we are providing in Worker File then what will happen?

-> HDL will fail to load the data. It will give error as "You must enter a valid value for the LocationId field." 

Q) Can we delete Location using HDL?

-> We can not delete Location. You can end date the that Location and make inactive.

Q) What will happen in below Scenario?

        Scenario - If we have future date changes for any worker and we tried to load the current any changes for the same worker using HDL.

-> If we tried to load the current changes then it will purge the future changes because by default 

     PURGE_FUTURE_CHANGES value set as Y.

     If you want to keep future dated changes then set PURGE_FUTURE_CHANGES N so that it will         keep future dated changes after the data load.

Q) Which Role is required to process the file using HCM Data Loader?

->  You required the Human Capital Management Integration Specialist Role (ORA_HRC_HUMAN_CAPITAL_MANAGEMENT_INTEGRATION_SPECIALIST_JOB)

Q) How can you change the delimiter in HDL File at run time?

->  You can set delimiter in HDL File using SET FILE_DELIMITER command.

Q) "The party identified by the specified party ID does not exist" Error while loading Personal Payment Method using HDL?

-> Reason - > Party Id is not created for those Worker.

 Solution - Run Below scheduled process 

                1 - Maintain Party and Location Current Record information

                2 - Synchronize Person Records 

Q) How to create personal Payment Method incase joint account scenario?

-> Create two different personal payment method for each employee and both can be tagged to same account.

In this case primary account holder name will be displayed in UI for both methods. 

Q) Talent Profile data loaded successfully using HDL, But not able to see at front end.

->  Loaded Profile information is not able to see at front end because of two reasons

            1. Check Section Id/Section Name is correctly used

             2. Check Content Type Id/Content Type is used correctly.

Q) Load Non Workers with person type Pensioner using HDL?

-> You can use Person Type Code and System Person Type with Pensioner in WorTerm and assignment Metadata line. 

Q) Supervisor Load is failed what could be the reason and solution for the same?

-> Cause - Manager's hire date is earlier than assignments effective start date

      Solution -  Add Work Term and Assignment record which is later than Manger's hire date   along with supervisor record.

          

 

Changes Only Mode in HCM Extracts

 Changes Only Mode in HCM Extracts

You can create HCM Extract to extract the results. In HCM extract there are several modes, you can use these modes to extract the data which got changed since earlier extract run which we call it as Baseline.

To Enable these modes you have to enable Changes_Only parameter while you are defining HCM Extract.

At the time of running the Extract you can use Changes Only parameter to fetch the filtered data as per the parameter.

Below are the different parameters in changes only mode :

1. All Attribute
2. Changed Attributes
3. Changed and Marked Attributes
4. Changed and Marked Attributes with previous value
5. Changed, Marked Attributes under threading group
6. Changed, Marked Attributes, previous data under threading group

If you want to see step by step video for this visit  Link

In this blog we will see how first two parameter will works.

All Attribute - If we run the HCM Extract with this parameter then extract will fetch all the attributes     defined in HCM Extracts.

Now we will see how to create Changes only HCM Extract.

Requirement - 1. Need to create HCM Extract with Changes Only Functionality.

                        2. Change any record and fetch this record only using Changes only mode.

Let's Start - 

Navigation - My Client Group -> Data exchange -> Extract Definition -> Create Extract (+).

Name	PersonData_Change
Start Date	Date as you wish
Type	Full Profile
Changes Only	Enable this option

 

Create Data Group - 

Name	Person_Details
Tag Name	Person_Details
User Entity	PER_EXT_SEC_PERSON_UE
Threading Database Item	Extract Person ID
Threading Action Type	Object actions
Root Data Group	Enable this option to make this Root Data Group

Threading Database Item - If we are implementing Changes Only HCM Extract then its required to define threading database item. It is the Unique Id for the selected User Entity

Create Record - 

Sequence	10
Name	Person_Details
Tag Name	Person_Details
Type	Detail Record
Process Type	Fast Formula

Create the Attributes -

1. Person Id - Attribute

Name	Person_ID
Tag Name	Person_ID
Shor Code	Person_ID
Data Type	Number
Type	Database Item Group
Database Item Group	Extract Person ID
Output Label	Person_ID
Output Column	1
Key Attribute	Enable this option

 

Key Attribute - We need to configure Key Attribute which is uniquely identify each row return by the data group. For Changes only mode, you must select at least one attribute in the block as key attribute.

2. Person Full Name - Attribute 

Name	Person_FullName
Tag Name	Person_FullName
Shor Code	Person_FullName
Data Type	Text
Type	Database Item Group
Database Item Group	Person Full Name
Output Label	Person_FullName
Output Column	2

3. Person Gender - Attribute

Name	Person_Gender
Tag Name	Person_Gender
Shor Code	Person_Gender
Data Type	Text
Type	Database Item Group
Database Item Group	Person Gender
Output Label	Person_Gender
Output Column	3

4. Person Date of Birth - Attribute

Name	Person_DOB
Tag Name	Person_DOB
Shor Code	Person_DOB
Data Type	Date
Type	Database Item Group
Database Item Group	Person Date Of Birth
Output Label	Person_DOB
Output Column	4

Define the Delivery Option 

Delivery Option Name	Data
Output Type	Data
Output Name	Data
Delivery Type	None

Navigate to Extract Execution Tree to compile all the formula and validate Extract.

Once HCM Extract validate successfully, then Submit the extract.

All Attribute Mode - 

Submit the Extract with All Attribute Parameter in changes only.

It will Extract full data output at that point of time. We can utilize this as a baseline.

Check the result of Extract.

Now we will change the Person name using Person management Option.

Open Any Worker using Person Management and change the Person Name and save the changes.

Once person changes successfully submitted then we will run again the extract with another mode.

Changed Attribute Parameter - If we run the HCM Extract with this parameter then Extract will compare with    previous extract run and fetch only those records got changed.

Run the Extract with Changed Attribute Parameter.

HCM Extract will fetch those records got changed after previous run to till that point of time.

Now you can check the results. You will get changes only records in output.

In this way you can defined Changes Only Extract and run it with All Attribute Parameter and Changed Attributes Parameter.

In next Blog we will see rest of the Changes only Parameter.

If you want to see step by step video for visit  Link

Changed and Marked Attributes -  Extract will fetch those records which got changed after previous extract run along with this those attributes which are marked as change.

Marked as a Change -  If we enable this option at attribute level which mean that we made that attribute as a required to fetch by HCM Extract irrespective of any data changes.

If you want to see step by step video for Changed and Marked Attribute - visit  Link 

For this we will enable the Marked as a change option for Person Full Name attribute which was

highlighted in yellow.

Person Full Name - Attribute 

Name	Person_FullName
Tag Name	Person_FullName
Shor Code	Person_FullName
Data Type	Text
Type	Database Item Group
Database Item Group	Person Full Name
Output Label	Person_FullName
Output Column	2

Marked as Change

Enable this option

Save Extract.

Now we will change the Person name of any worker using person management and then Submit the extract.

Submit HCM Extract with Changed and Marked Attribute Parameter.

Expected output  -  HCM Extract will fetch those records got changed after the previous run and also those attributes which was marked as change.

If you want to see output for Changed and Marked Attribute - visit  Link 

Changed and Marked Attributes with previous value - 

 HCM Extract with this parameter will fetch the Changed attribute after previous extract run and those attributes which marked as change at attribute level along with old values.

For this we will enable Marked ass change option for person Date of birth Attribute.

If you want to see details for Changed and Marked Attribute with Previous Value - visit  Link 

 Person Date of Birth - Attribute

Name	Person_DOB
Tag Name	Person_DOB
Shor Code	Person_DOB
Data Type	Date
Type	Database Item Group
Database Item Group	Person Date Of Birth
Output Label	Person_DOB
Output Column	4

Marked as Change

Enable this option

Now we have Person Full Name and Person DOB these two attribute are marked as change.

We will change Person Gender for any person and will submit the Extract.

Changed the Gender for any person and save the changes.

Submit the HCM Extract with Changed and Marked Attributes with Previous Value Parameter.

It should fetch Person Full Name, Person DOB, Person Gender with old Values.

If you want to see output for Changed and Marked Attribute with Previous Value - visit  Link 

Sample Template for eText BIP Report

 Sample Template for eText BIP Report 

You can see step by step video to develop eText BIP Report using this Link

Please find the attached templates:

1) eText Template -

You can see step by step video to develop eText BIP Report using this Link

<TEMPLATE TYPE>	DELIMITER_BASED
<OUTPUT CHARACTER SET>	iso-8859-1
<CASE CONVERSION>	UPPER
<NEW RECORD CHARACTER>	Carriage Return

 

<LEVEL>	DATA_DS
<MAXIMUMLENGTH>	<FORMAT>	<DATA>	<COMMENTS>
<NEW RECORD>	TableHeader
20	Alpha	'Person Id'
1	Alpha	'|'
20	Alpha	'Title'
1	Alpha	'|'
20	Alpha	'First Name'
1	Alpha	'|'
20	Alpha	'Last Name'

 

<LEVEL>	G_1
<MAXIMUMLENGTH>	<FORMAT>	<DATA>	<COMMENTS>
<NEW RECORD>	CLRDAta
20	Alpha	PERSON_ID
1	Alpha	'|'
20	Alpha	TITLE
1	Alpha	'|'
20	Alpha	FIRST_NAME
1		'|'
20	Alpha	LAST_NAME
<END LEVEL>	G_1

 

<END LEVEL>

DATA_DS

 

2) Fixed Position eText Template  - 

You can see step by step video to develop Fixed Position eText BIP Report using this Link

<TEMPLATE TYPE>	FIXED_POSITION_BASED
<OUTPUT CHARACTER SET>	iso-8859-1
<CASE CONVERSION>	UPPER
<NEW RECORD CHARACTER>	Carriage Return

 

<LEVEL>					DATA_DS
<POSITION>			<LENGTH>		<FORMAT>		<PAD>		<DATA>		<COMMENTS>
<NEW RECORD>					TABLE_HEADER
1		15			Alpha		R, ' '		'Person Id'
16		3			Alpha		R, ' '		'|'
19		15			Alpha		R, ' '		'Title'
35		3			Alpha		R, ' '		'|'
39		50			Alpha		R, ' '		'First Name'
90		3			Alpha		R, ' '		'|'
94		20			Alpha		R, ' '		'Last Name'
<LEVEL>					G_1
<POSITION>			<LENGTH>		<FORMAT>		<PAD>		<DATA>		<COMMENTS>
<NEW RECORD>					TABLE_HEADER
1		15			Alpha		R, ' '		PERSON_ID
16		3			Alpha		R, ' '		'|'
19		15			Alpha		R, ' '		TITLE
35		3			Alpha		R, ' '		'|'
39		50			Alpha		R, ' '		FIRST_NAME
90		3			Alpha		R, ' '		'|'
94		20			Alpha		R, ' '		LAST_NAME
<END LEVEL>					G_1
<END LEVEL>					DATA_DS