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.

Changes to Organization & Location objects starting in R13 19D

edited Nov 9, 2019 1:24AM in HCM Integrations

Summary

Organization.dat and Location.dat files encountering error messages on R13 19D, working on R13 19C

Content

Overall, found that passing updates to existing records via Organization.dat sample syntax

METADATA|Organization|Name|EffectiveStartDate|SourceSystemOwner|SourceSystemId
MERGE|Organization|10100-001100|1951/01/01|SOURCE|DEP_10100-001100
MERGE|Organization|20200-002200|1951/01/01|SOURCE|DEP_20200-002200
MERGE|Organization|30300-003300|1951/01/01|SOURCE|DEP_30300-003300

worked as expected on R13 19C, but upgrading to R13 19D encountered error message

An error occurred. To review details of the error run the HCM Data Loader Error Analysis Report diagnostic test. Message details: ORA-00001: unique constraint (FUSION.HRC_DL_VO_MAPS_U1) violated

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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