Turning staged PeopleSoft data into Oracle HCM Data Loader (HDL) files — code normalization, source-to-target field mapping, and business-rule transformation — the bridge between the legacy data model and Oracle Fusion.
Extracted data lands in the staging table PS_AZ_FILE_OC_STG for cleansing and standardization before HDL conversion:
A source-to-target mapping matches each PeopleSoft field to its Oracle Fusion equivalent — meticulous work that is critical for statutory compliance and for consistency across systems. Examples include EMPLOYEE_ID → PERSON_NUMBER, name and department fields, and the Irish Revenue and PRSI fields that payroll reporting depends on.
Fields required for Irish Revenue reporting mapped explicitly so payroll data is compliant on day one.
Pay Related Social Insurance fields carried through mapping into the Fusion model.
Converting staged data into HDL format is automated, which brings an accelerated timeline (less manual effort) and error reduction (less human error). The output is a set of HDL files ready for the Oracle HCM Data Loader.
HDL is the Oracle HCM Data Loader — the supported bulk-load mechanism for Oracle Fusion HCM. Staged PeopleSoft data is transformed into HDL-compliant files that conform to Fusion specifications.
Through a source-to-target mapping document that matches each PeopleSoft field to its Fusion equivalent (e.g. EMPLOYEE_ID → PERSON_NUMBER), including the Irish Revenue and PRSI fields payroll needs.
Code normalization (country, state, business-unit and department codes), business-rule and eligibility filtering, and record enrichment in the staging table.
Tell us your PeopleSoft footprint and target Fusion modules — Core HR, Absence, Payroll — and we’ll scope an automated, HDL-based migration on the Syntra ETL platform.