Oracle HCM Cloud V1 Connector > Mappings and Mapping Tasks with Oracle HCM Cloud V1 Connector > Oracle HCM Cloud V1 Source Transformation in Mappings
  

Oracle HCM Cloud V1 Source Transformation in Mappings

When you configure a Source transformation, select the Oracle HCM Cloud V1 connection and choose an Oracle HCM operation to represent an Oracle HCM Cloud V1 source.
Configure the advanced source properties to set the tracing level and the cache size for the web service response.
You can view the response structure in the field mapping. When you map the elements from the response structure to the output fields, the Secure Agent creates the output groups, along with the keys for the field names. When you use the mapping in a mapping task and run the task, the Secure Agent reads the data from the Oracle HCM Cloud application.
Note: When you run a mapping to read data that contains a Unicode character from the Oracle HCM Cloud application, the Secure Agent does not read the data correctly.

Source Transformation Properties

You can use one or more Source transformations in a mapping.
When you select a source transformation, the Properties panel displays the following sections:
General
Use to configure the name and a description for the source.
Source
Use to select the connection and the operation. You can configure the request options, and advanced source properties.
Field Mapping
Use to map elements of the response structure with the output fields.
Fields
Use to edit the metadata source field metadata that you want to use in the mapping.

Oracle HCM Cloud V1 Advanced Source Properties in Mappings

In a mapping, you can configure or create a Source transformation and configure the advanced properties in the Source page of the Mapping Task wizard.
The following table describes the advanced properties that you can configure in a Source transformation:
Property
Description
Tracing Level
Amount of detail that appears in the log for the Source transformation. Use the following tracing levels:
  • - Terse
  • - Normal
  • - Verbose Initialization
  • - Verbose
Default is normal.
Cache Size for Web Service Response (KB)
Not Applicable.
Note: Do not change the value of this property unless Informatica Global Customer Support instructs you to do so.

Source Transformation Mapping Example

You can map an Oracle HCM Cloud V1 source to a target and use the mapping to perform a mapping task.
To read data from an Oracle HCM Cloud and write to a flat file, perform the following tasks:
    1. In Data Integration, click New > Mapping > Create.
    The New Mapping dialog box appears.
    2. Enter a name and description for the mapping.
    3. On the Source transformation, specify a name and description in the general properties.
    The following image shows a simple Oracle HCM Cloud V1 reader mapping:
    4. On the Source tab, perform the following steps to configure the source properties:
    1. a. In the Connection field, select the configured Oracle HCM Cloud V1 connection to connect to Oracle HCM Cloud application.
    2. b. In the Operation field, select the required object in the Package Explorer section and select the required operation.
    3. The following image shows the list of the read operations:
    4. c. In the Request Options section, click Configure to configure the request message. For more information about configuring the request message, see Configuring Request Message.
    5. d. In the Advanced Properties section, set the tracing level to normal, and use the default cache size of 1024.
    5. On the Field Mapping tab, select the elements in the response structure that you want to map to the output fields.
    The following image shows the response structure on the left pane in a hierarchical format and the output groups on the right pane in a relational format:
    6. On the Target transformations, specify the target connection, target type, object, and operation for the target transformations.
    7. Map the source and target.
    8. Click Save and Run the mapping.
    9. In Data Integration, click New > Task.
    10. Click Mapping Task > Create and select the mapping for the task.
    The following image shows the Mapping Task wizard with the applied mapping:
In Monitor, you can monitor the status of the logs after you run the task.

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.
Note: 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:
You can obtain the content ID in the Extract Delivery Options tab under the View Extract Results page.
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.
Note: 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.