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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Threading dbi action occurence id in department hcm extract
We are developing an HCM Extract that captures changes only for historical and future Department details. The root UE is PER_EXT_SEC_HISTORY_ORGANIZATION_UE. When we use the organization ID as the threading DBI, we encounter duplicate rows. However, when we use the Extract Historical Organization Action Occurrence ID, we get unique rows. Is Organization Action Occurrence ID the correct DBI to use, and will it always be unique? Has anyone used this threading DBI before?
0