1.
Creating the HCM Extract
Below is a simplified guide to building the extract. Your actual extract logic may vary
based on how the appraisal result is stored.
1. Create a New Extract Definition
o Navigator → Data Exchange → Extract Definitions → Create
o Enter the Extract Name (e.g., Non Renewal Termination Extract),
Extract Type = Full Profile or Full (depending on your exact approach).
2. Define Extract Parameters (if needed)
o Start Date / End Date: Usually, you might pass current date or a date
range to find employees whose contract is set to end.
o Performance Document Period: If relevant, you may have a
parameter to filter the performance cycle or period.
3. Create Data Groups
o Primary Data Group (PDG): “Person” or “Assignment,” depending on
how you want to structure the extract. Typically, you start with
“Assignment.”
o Related Data Groups: If the performance rating is stored in a specific
table or an extended table, you may need a related DG to pull that
rating/decision.
4. Extract Criteria
o In your Primary Data Group filter, you will specify the condition that
picks only those employees who have a “Non-Renewal” outcome in the
performance appraisal. For example:
WHERE pm_table.final_rating = 'Non Renewal'
OR pm_table.custom_indicator = 'NRC'
(Exact code depends on how/where the data is stored in the Performance
Management tables.)
5. Create Record Definitions and Fast Formula (if needed)
o Each Record within the Extract corresponds to a segment of data you
want to output (person details, assignment details, date, action reason,
etc.).
o If you need dynamic logic (e.g., to compute the Termination Effective
Date from the Contract End Date), you might use a Fast Formula or you
can do this in the extraction query/logic.
6. Define the Output File
o You want the output in a format that closely follows HDL’s Work
Relationship / Work Terms / Assignment / Terminate structure.
o Typically, you can design your Extract to directly produce the .dat file
used by HDL.
Here’s an example snippet of an HDL Termination file (simplified):
METADATA|WorkRelationship|SourceSystemId|DateStart|ActionCode|
ActionReasonCode|EffectiveStartDate|LegislationCode|PersonNumber
MERGE|WorkRelationship|WR_{PERSON_NUMBER}|{START_DATE}|TERMINATION|
NON_RENEWAL|{EFFECTIVE_DATE}|US|{PERSON_NUMBER}
METADATA|WorkTerms|SourceSystemId|DateStart|ActionCode|EffectiveStartDate|
PrimaryWorkTermsFlag|AssignmentNumber
MERGE|WorkTerms|WT_{ASSIGNMENT_NUMBER}|{START_DATE}|TERMINATION|
{EFFECTIVE_DATE}|Y|{ASSIGNMENT_NUMBER}
METADATA|Assignment|SourceSystemId|DateStart|ActionCode|EffectiveStartDate|
AssignmentNumber|ActionReasonCode
MERGE|Assignment|A_{ASSIGNMENT_NUMBER}|{START_DATE}|TERMINATION|
{EFFECTIVE_DATE}|{ASSIGNMENT_NUMBER}|NON_RENEWAL
o You’ll build your HCM Extract XML/CSV output so that it exactly maps to
the HDL file structure.
7. Output Delivery
o Configure the Extract Delivery Options to produce a .dat file.
o You may store it on the UCM (Universal Content Management) account
or an SFTP location from which the file will be picked up for HDL
loading.
2. Automating the HDL Load
Once you have the Extract generating the HDL file, you can automate the load:
1. Set Up Import and Load Process
o In Navigator → Data Exchange → HCM Data Loader, there is a
process called Import and Load Data.
o You can schedule a job in Fusion to pick up the .dat file from UCM or
SFTP and then import it.
2. Automate via ESS Job
o Create an ESS (Enterprise Scheduler Service) job that:
1. Triggers the HCM Extract (Non Renewal Termination Extract).
2. Waits for the extract to complete (which publishes the .dat file to
UCM or SFTP).
3. Invokes Import and Load Data to process that .dat file.
o This can be a chain of ESS jobs or integrated within Oracle Integration
Cloud (OIC), if you use that for orchestrations.
3. Monitor and Error Handling
o In Data Exchange → HCM Data Loader → Import and Load Data,
monitor the status of loads.
o If some records fail (for example, if the employee is already terminated
or missing data), you’ll see errors in the log.
3. Testing and Validation
1. Create Test Appraisals
o Create test employees with different performance decisions (renew vs.
non-renew).
2. Run Extract in Test Environment
o Ensure only “Non Renewal” employees appear in the output file.
o Validate the generated .dat structure.
3. Load via HDL
o Manually load the .dat in a test environment to verify it creates correct
termination records.
o Check Person Management → Manage Work Relationships to see if the
termination was created with correct Action/Reason.
4. Refine Any Gaps
o Adjust the logic in the Extract (e.g., effective date calculations,
assignment details) if results are not correct.
o Ensure the reason code and action code are consistent with your global
HR setup.
4. Move to Production
1. Migrate Extract
o Use Configuration Package or Migration Tools to move the HCM
Extract definition and Fast Formulas from Test to Production.
2. Schedule the ESS Process
o In Production, schedule it appropriately (e.g., nightly or weekly) so that
each new set of “Non Renewal” records is processed automatically.
3. Ongoing Maintenance
o Periodically check logs for any issues.
o If performance rating or appraisal structures change, you may need to
update the Extract logic.
Email Data Group
EXT_EXT_HEX_EE_E_MAIL_DETAILS_100004195270091
Email Details
Properties
Email Details
