Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

HDL: Surrogate ID in AssignedPayroll.dat file

edited Feb 22, 2018 3:17PM in HCM Integrations 6 comments

Summary

What other Source System IDs can be used instead of AssignmentNumber in AssignedPayroll.dat file

Content

We have a requirement when a third party system is sending files to create record in HCM via HDL. This system will only have Person Number and rest all of the IDs will be derived using SourceSytemID of a component in Worker file. E.g. Salary.dat
METADATA|Salary|SourceSystemOwner|SourceSystemId|AssignmentId(SourceSystemId)|DateFrom|DateTo|SalaryAmount|SalaryBasisName|SalaryApproved|ActionCode|ActionReasonCode
MERGE|Salary|UNIFICATIONHUB|654321_SAL_1|654321_ASG_1|2017/01/01|4712/12/31|70000|GBP Annual Salary|Y|XXHR_UH_CHG_SAL_HR|XXHR_UH_UPDATE

AssignmentId(SourceSystemId) - SourceSystemId of Assignment component in Worker file is being used as a surrogate ID to AssignmentNumber.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!