Oracle HCM’s Best Practice for Effective Dating
in Compensation
Per Oracle HCM’s Best Practice for Effective Dating, not from Conversion perspective but for ongoing business operations, and from data integrity/tracking perspective, are the following statements correct?
The effective date for a Compensation Zone (city/state) should reflect the actual business-effective date, defined as the date when the location begins to impact compensation decisions and should not be a placeholder date such as 01/01/1951.
Similarly, for All Work Structure objects (Job, Department etc.), we should always use the actual business-effective date — the date when the object becomes valid, available, or applicable in the business —not a placeholder date like 01/01/1951.
Tagged:
0