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.

Best Practice for reporting team to prepare for Oracle Monthly/Quarterly Patches

edited Nov 9, 2018 8:16PM in Reporting and Analytics for HCM 2 comments

Summary

Best Practice for reporting team to prepare for Oracle Monthly/Quarterly Patches

Content

Hello!

We are a team of OTBI and BI Publisher users, new to Oracle HCM.

Is there a best practice, when Oracle begins to send out notice of their monthly patches, to (1) identify a change that will impact one of the reporting tools above and (2) identify data/database/schema changes that will also impact reporting.  Oracle seems to push a lot of information out for each patch and we'd like to know if there is a method to quickly locate changes that impact the reporting side of the business.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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