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.

Offerings load created new records with sysdate as effective start date

in HCM Integrations 3 comments

Summary:

Reloading the same offerings rows updated the offerings with new effective start date instead of correcting the existing record.

Content (please ensure you mask any confidential information):

We loaded courses and offerings on June 12, 2024, and they were successfully loaded with the correct effective start dates. However, on June 16, 2024, I reloaded the same file, and all the offerings were updated instead of getting corrected.. A new record was added for each offering with an effective start date of June 16, 2024, even though I specified different effective start dates. The old records were end-dated with an effective end date of June 15, 2024. The change event date remains June 12, 2024, for both records in the backend. This is causing issues when trying to

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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