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

BICC Extract Object / VO for PER_SENIORITY_DATES_F After V3 Seniority Date Migration

in HCM Integrations

We are seeking clarification regarding the impact of the V3 Seniority Date Migration on BICC extracts and the associated View Objects (VOs).
Prior to enabling V3 Seniority Dates, we were retrieving Original Hire Date through the BICC extract object based on:
FscmTopModelAM.PersonAM.GlobalPersonForETLPVO
The attribute was sourced from PER_PERIODS_OF_SERVICE.ORIGINAL_DATE_OF_HIRE.
Oracle documentation indicates that seniority-related information is now managed through PER_SENIORITY_DATES_F. However, we have been unable to identify the corresponding BICC Extract Object / VO that exposes this data post-migration.
Which BICC Extract Object or Fusion VO exposes data from PER_SENIORITY_DATES_F?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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