Oracle Transactional Business Intelligence

HCM Seniority Date v1 to v3

Received Response
21
Views
1
Comments

We're currently in the process of migrating Seniority date from v1 to v3 and attempting to migrate all of our reports to these new fields. From what I'm seeing, legal employer seniority date and enterprise seniority can only be pulled from separate subject areas as opposed to be being able to be pulled from one as we previously were able to.

We previously could use "Workforce Management - Worker Assignment Real Time" and then in the Worker bucket, we could use both fields "Enterprise Seniority Date" and "Legal Employer Seniority Date".

My team doing the upgrade has informed me that in order to accomplish this with v3 Seniority dates we'd have to include 2 additional subject areas. The fields required from "Workforce Management - Worker Assignment Real Time" would stay, then for Enterprise Seniority Date we'd have to join in "Workforce Management - Person Seniority Real Time", then in the bucket "Person Seniority Details" add in the field "Seniority Date". We'd also have to rename this field as if we didn't it, it would get confused with the next field we're bringing in. Now to get Legal Employer Seniority Date we also need to add "Workforce Management - Work Relationship Real Time", then in the bucket "Seniority Date" add in the field "Seniority Date" Which is the same as the previous field, so again, renaming is key to ensure they don't get confused.

Is there something we've missed? Is this the expected solution to having all these dates in a report? Adding in 2 additional subject areas (and of course the calculated values to get those subject areas to work) where we used to be able to do this all in one? Please tell me we've missed something or our team overlooked a setup step. Given how adding subject areas slow down reports I'm finding really hard to believe this is the recommended setup to pull the data needed.

Thanks in advance.

Tagged:

Answers