Configure The Extract Bulk Data Option in An Integration

This document provides instructions for configuring an integration to use the extract bulk data option in the Oracle HCM Cloud Adapter. It describes creating a scheduled integration, adding a schedule parameter, invoking the adapter to extract data, mapping fields, staging the file, and updating the schedule parameter.

Uploaded by

balasuk

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

69 views2 pages

Configure The Extract Bulk Data Option in An Integration

Uploaded by

balasuk

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 2

4/9/23, 1:07 PM Configure the Extract Bulk Data Option in an Integration

upgraded to our latest version, see Oracle Integration 3. Go to Integration 3

Using the Oracle HCM Cloud Adapter with

Oracle Integration Generation 2

Configure the Extract Bulk Data Option in an Integration

You can use the extract bulk data option in an orchestrated integration. This section provides a high-level design of an
integration using this feature.

Note: You must schedule and create the HCM data extract in Oracle HCM Cloud. It must be configured
with a delivery option of type WebCenter Content. When configuring this delivery option, the Integration
Name field must be populated with a unique value that is later specified in the What is the Integration
Name for HCM Extracts field of the Operations page when configuring the Oracle HCM Cloud Adapter.

To configure an extract bulk data integration:

1. Create a scheduled, orchestrated integration pattern.

2. Add a schedule parameter to store the processed Document ID and initialize it with a value of 0. An HCM extract is
associated with a Document ID. Once the extract is processed by the integration, the ID is stored in the schedule
parameter. This value is required as input by the data extract operation in the Oracle HCM Cloud Adapter.
3. Drag the Oracle HCM Cloud Adapter to the invoke section of the integration canvas and configure the extract bulk
data operation.
4. Configure the mapper for the data extract operation and map the schedule parameter with the
lastProcessedDocumentID field.
5. Drag a Stage File action to the integration canvas. This invokes the Configure Stage File Action wizard.
a. On the Configure Operation page, select the Read File in Segments operation.
b. Map the filename and directory from the data extract response payload in the Expression Builder:
XPath to filename:
$getFile/nsmpr2:GetFileResponse/nsmpr2:HcmDataExtractResponse/nsmpr2:ICSFile/nsmpr1:Prop
erties/nsmpr1:filename
XPath to directory:
$getFile/nsmpr2:GetFileResponse/nsmpr2:HcmDataExtractResponse/nsmpr2:ICSFile/nsmpr1:Prop
erties/nsmpr1:directory
c. On the Schema Options page, select an existing schema from the file system.
i. On the Format Definition page, upload the extract schema. This schema should belong to the HCM
extract and must be exported from Oracle HCM Cloud.
ii. For the Select Repeating Batch Element field, click the Expression Builder icon. The extract schema is
shown in the Source tree.
iii. Identify and select the repeating element from the schema.
d. In the Stage File scope, use any appropriate adapter to process the extract.

https://docs.oracle.com/en/cloud/paas/integration-cloud/hcm-adapter/sample-integration-flow-demonstrate-extract-bulk-data-option.html 1/2
4/9/23, 1:07 PM Configure the Extract Bulk Data Option in an Integration

6. Immediately after the Stage File scope, assign the processed Document ID in the schedule parameter. This enables
you to use this value the next time the Oracle HCM Cloud Adapter is invoked.

https://docs.oracle.com/en/cloud/paas/integration-cloud/hcm-adapter/sample-integration-flow-demonstrate-extract-bulk-data-option.html 2/2