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.
Archive Transaction Console Completed Transactions clarification
Summary:
We have a custom report that utilizes the console transaction tables like HRC_TXN_DATA, HRC_TXN_HEADER, and HRC_TXN_CONSOLE_ENTRY). However, if the ESS job "Archive Transaction
Console Completed Transactions" is scheduled it will archive data from the console transaction tables. Thus, these reports will no longer pull in the necessary data for our customer.
1. What is the recommendation to archive console transaction tables and what kind of issues could occur if we decide to only archive once every 12 or 24 months?
2. When running the ESS archive job "Archive Transaction Console Completed Transactions", does this job only archive where HRC_TXN_DATA.STATUS IN ('APPROVED')
Tagged:
0