Get Started: AI Resources for Oracle Cloud HCM – Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Upgrade to 23B
Summary:
Hello All,
I have question regarding whether we use V2 or V1 for Seniority dates.
wIf run below query I see V2
Select * from FUSION.PER_EMPL_CONFIGURATIONS
Result-
CREATED_BY (DATA_MIGRATION_SCRIPT)
CREATION_DATE (2018-10-27T10:22:30.000+00:00)
LAST_UPDATE_DATE (2018-10-27T10:22:30.000+00:00)
LAST_UPDATED_BY (DATA_MIGRATION_SCRIPT)
OBJECT_VERSION_NUMBER (1)
LAST_UPDATE_LOGIN (-1)
CONFIGURATION_ID (100000091030392)
RECORD_CREATOR (Configure Seniority Date - MIGR)
CONFIGURATION_CODE (ORA_SENIORITY_HOUR_CONV)
CONFIGURATION_TYPE (ORA_SENIORITY)
HOURS_IN_DAY (8)
HOURS_IN_MONTH (173.33)
HOURS_IN_YEAR (2080)
VERSION_CODE (V2)
But when I check Work relationship page, I see that Legal Employer Seniority Date and Enterprise Seniority Date are populated.
Tagged:
1