OIC - How to Reprocess an HCM Extract in OIC Without Resubmitting the Flow

Use Case

In Oracle HCM integrations, it’s common to schedule extracts and process their output to a target destination like Oracle Object Storage. However, in real-world scenarios, the extract may fail in the middle of the process — for example, due to downstream errors — even though the extract itself completed successfully in HCM.

When this happens, you often want to reprocess the existing extract output rather than re-running the extract flow in HCM (which could cause data duplication or require additional system resources).

To handle this, we design an OIC-based solution with:

• A Scheduler Integration to initiate the process.
• A Main Integration to execute or reprocess the extract depending on parameters.

---

Solution Approach

We will create two integrations:

1. Scheduler Integration

• Purpose: Accepts runtime parameters and decides whether to submit a new extract or reprocess an existing one.
• Parameters:
  • EffectiveDate – Extract run date (YYYY-MM-DD format)
  • ExtractFlowInstanceName – Name of the extract flow instance to reprocess
  • SkipExtractSubmission – Yes/No flag to skip submitting the extract and instead retrieve an existing output
• Logic:
• If SkipExtractSubmission = No → Call HCM submit extract API, wait for completion, download the file.
• If SkipExtractSubmission = Yes → Skip submit step, directly get extract instance details, retrieve document ID, and download from UCM.

---

2. Main Integration

• Purpose: Handles the extract execution, monitoring, file retrieval, and delivery to Object Storage.
• Key Steps:
  1. Assign & Initialize Variables – Store parameters.
  2. Switch Condition – Decide if extract needs submission or reprocessing.
  3. While Loop – Poll HCM extract status until completion.
  4. Get Document ID – Retrieve from extract instance data.
  5. Download from UCM – Fetch the output file.
  6. Transform Data – Apply required mapping/format changes.
  7. Upload to Object Storage – Store file in the designated bucket.
  8. Error Handling – Throw faults if extract fails or file retrieval fails.

---

High-Level Flow Diagram

---

Benefits

• No Duplicate Data – Avoid re-running the same extract unnecessarily.
• Faster Recovery – Quickly reprocess failed integrations.
• Parameter Driven – Flexible execution controlled at runtime.
• Error Handling Built-In – Ensures issues are caught and handled.

---

How to download HCM extract, for details >> follow my previous blog:

https://soalicious.blogspot.com/2024/08/oic-hcm-how-to-schedule-and-download.html?m=1