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|

 

SQL Query to Fetch Global Transfer records in Fusion HCM

SQL Query to Fetch Global Transfer records in Fusion HCM 

select

papf.person_number, ppnf.full_name,

to_char(ppos.date_start,'mm/dd/yyyy') Hire_date

,(select hou.name from hr_organization_units hou where organization_id = ppos.LEGAL_ENTITY_ID)  Current_LE

from per_All_assignments_m paam

,per_all_people_F papf

,per_person_names_f ppnf

,PER_PERIODS_OF_SERVICE ppos

where paam.person_id = papf.person_id

and papf.person_id = ppnf.person_id

and ppos.period_of_service_id = paam.period_of_service_id

and ppnf.name_type = 'GLOBAL'

and sysdate between papf.effective_start_date and papf.effective_end_date

and sysdate between ppnf.effective_start_date and ppnf.effective_end_date

and  sysdate  between paam.effective_start_date and paam.effective_end_date

and paam.person_id = papf.person_id

and paam.assignment_status_type = 'ACTIVE' 

and paam.assignment_type = 'E'

and paam.action_code = 'GLB_TRANSFER'

Note :- Do let me know in case of any issue in query.

SQL Query to Fetch Inactive Employees in Fusion HCM

SQL Query to Fetch Inactive Employees in Fusion HCM 

select 

paam.*

from

 per_all_assignments_m paam ,

per_all_people_f  papf 

where 1=1

and papf.person_id = paam.person_id

and paam.ASSIGNMENT_STATUS_TYPE <> 'INACTIVE'

and paam.effective_latest_change = 'Y'

and paam.primary_flag = 'Y'

and paam.assignment_type= 'E'

and trunc(sysdate) between papf.effective_start_date and papf.effective_end_date

and exists ( select '1' from per_all_assignments_m paam1 where paam1 .assignment_id = paam.assignment_id

             and trunc(sysdate) between paam1 .effective_start_date and paam1 .effective_end_date

and t1.ASSIGNMENT_STATUS_TYPE <> 'INACTIVE'

)

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.

          

 

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