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.

Seniority Dimension OTBI Reporting

edited May 14, 2020 2:08PM in Reporting and Analytics for HCM 1 comment

Summary

Seniority date dimension added in 19D for V3 seniority dates

Content

Hello,

19D introduced a new dimension for Seniority Date reporting, specifically for use with the V3 seniority dates. We've run into an issue where we can't get any data to come through for that dimension in OTBI. I've opened an SR, but wanted to see if anyone else ran into this issue, and how they were able to fix it. We're wondering if there was another process that needed to run once we migrated to V3, but we're not sure. We have the ESS job to calculate the seniority dates running daily, so we don't think it's that. The 19D release

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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