Oracle HCM Cloud V1 Connector

Back Next

Configuring Request Message

You can configure the request message based on how you submit the HCM extract definitions to the Oracle HCM Cloud application when you create a mapping.

You can either submit the HCM extract definitions from the Oracle HCM Cloud application directly or use the

Submit Extract

connection property. On the Source transformation, click

Configure

in the

Request Options

section to configure the request message.

When you submit the HCM extract definitions from the Oracle HCM Cloud application directly, specify the request message and attributes in the following XML format and validate the message:

<!--1 or more repetitions:-->
<proc:requestMessage_INPUT xmlns:proc="http://xml.schemas/infa/procedure/">
  <!--1 or more repetitions:-->
  <integrationName>
    <!--STRING-->
  </integrationName>
  <!--Optional:-->
  <contentID>
    <!--STRING-->
  </contentID>
  <!--Optional:-->
  <advancedQuery>
    <!--STRING-->
  </advancedQuery>
</proc:requestMessage_INPUT>

The

Integration Name

parameter is mandatory. You must specify the same value of the

Integration Name

property that you specified in the Oracle HCM Cloud application when you create the HCM extract definition.

The

advancedQuery

parameter is optional. If you want to process multiple XML files based on the filter query options or between date range, you must provide the

advancedQuery

parameter. When you add the QueryText syntax in the

advancedQuery

parameter, ensure that the QueryText syntax is based on the Verity Query language.

By default, Oracle HCM Cloud V1 Connector processes the XML data of the latest submitted HCM extract definition instance. Specify the

Content ID

parameter if you want to process the XML data corresponding to a different instance of the submitted HCM extract definition.

You can obtain the

Content ID

of the submitted HCM extract definition instance from the Oracle HCM Cloud application. Navigate to the

Extract Delivery Options

tab under the

View Extract Results

page to obtain the

Content ID

. The following image shows the

View Extract Results

page where you can obtain the value of the

Content ID

When you submit the HCM extract definitions using the

Submit Extract

connection property, specify the request message and attributes in the following XML format and validate the message:

<!--1 or more repetitions:-->
<proc:requestMessage_INPUT xmlns:proc="http://xml.schemas/infa/procedure/">
	<!--1 or more repetitions:-->
	 <flowName>
		<!--STRING-->
	 </flowName>
<!--1 or more repetitions:-->
	 <flowInstanceName>
		<!--STRING-->
	 </flowInstanceName>
	<!--Optional:-->
<legislativeDataGroupName>
	 <!--STRING-->
</legislativeDataGroupName>
<!--Zero or more repetitions:-->
  <parameterValues>
<!--1 or more repetitions:-->
  <ParameterName>
  <!--STRING-->
  </ParameterName>
<!--1 or more repetitions:-->
  <ParameterValue>
  <!--STRING-->
  </ParameterValue>
 </parameterValues>
<!--1 or more repetitions:-->
  <integrationName>
  <!--STRING-->
  </integrationName>
</proc:requestMessage_INPUT>

The

flowName

parameter is mandatory. You must specify the name of the HCM extract definition as

flowName

The

flowInstanceName

parameter is optional. If you provide a value for the

flowInstanceName

parameter, it must be unique for each mapping task. If you do not provide a value for

flowInstanceName

or the flowInstanceName
tag is missing in the request message, the connector generates a unique value based on the flow name and has the syntax

flowInstanceName = flowName_currentTimeStamp

(timestamp in epoch). For example, if you provide flow name as

Taleo Job

then the flow instance name generated by the connector is

Taleo Job_1565028486

Specify the

legislativeDataGroupName

parameter to provide a name for the legislative data group in which you created the HCM extract definition.

Specify the

ParameterValue

parameter to provide parameters that are defined for the HCM extract definition.

The

Integration Name

parameter is mandatory. You must specify the same value of the

Integration Name

property that you specified in the Oracle HCM Cloud application when you created the HCM extract definition.

If you submit multiple instances for the same HCM extract definition in parallel, Informatica recommends that you provide a unique

Integration Name

for each of the HCM extract definitions in the request message.

Source Transformation Mapping Example

Download Guide

Watch

Comments

Cloud Connectivity Homepage

Communities

Knowledge Base

Success Portal

0 COMMENTS

We’d like to hear from you! Log in to comment.

Rename Saved Search

Table of Contents

Oracle HCM Cloud V1 Connector

Oracle HCM Cloud V1 Connector

Configuring Request Message

Configuring Request Message