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.

How to determine timing delay how long does it take for data to be committed to the audit tables?

Summary:

We receive ad hoc tasks from business every time there's a compensation refresh happening. This process contains updates in the Assignment and Salary Section of the associates. We also have a job that sends delta information from Cloud to Peoplesoft, this runs every 15 mins. This job maintains the data in both systems are in sync.

Content (required):

This ad hoc request usually has 120K records in the HDL load (worker and salary component), as compared to our daily runs 6K (at max). With this number, a delay in committing data to audit tables is observed, creating a huge problem for us. Since HDL follows the hierarchy worker then salary in loading, NEW-Worker and OLD-salary are often sent first to Peoplesoft. We would like to seek your advice on a more feasible way to do this. Are there steps that we're missing or we can improve? In an SR, the support recommended BI Caching, but we

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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