Oracle Fusion Technical: Reports, Data, Integrations and Extensions · Module 8 · HDL for HCM data
Effective dates: the part that catches everyone
Lesson 80 of 177 · 2 min
Loading a record with the wrong effective date DOES NOT FAIL. It creates history that is wrong, and every report afterwards reproduces it faithfully. That is the whole lesson and it is worth stating twice. A salary loaded effective the first of January when it should have been the first of February is not an error — it is a version of the record that says the person earned the new amount for a month they did not. Payroll will use it. A retroactive calculation will use it. A report of average salary by month will use it. Nothing is broken; the history simply says something untrue. Three specific traps. A date a day early, which is usually a time-zone or a spreadsheet artefact and produces a one-day version nobody intended. A date in the FUTURE, which creates a version that is invisible today — the record looks unchanged, because…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Fusion Technical: Reports, Data, Integrations and Extensions, with a certificate on completion and a fourteen-day refund window.
In this module: Module 8 · HDL for HCM data
- 1Why HCM has its own loader
- 2The .dat file format
- 3Business objects and their dependencies
- 4Effective dates: the part that catches everyone
- 5Source keys and matching existing records
- 6Loading, monitoring and the error report
- 7Corrections and the delete you cannot do
- 8HDL versus HSDL, and when to use each
- 9What breaks: four HCM load failures
- 10Lab briefing · Load a workforce, then correct it