Oracle Fusion Cloud ERP Jobs: HCM Data Load
Automic Automation HCM Data Load Jobs allow you to submit the Oracle HCM Data Load from Automic Automation.
The HCM Data Loader is a powerful tool for bulk-loading and maintaining data. It supports a file-based upload of business objects, components, and component attributes using a flexible, delimited file. You can use the HCM Data Loader for data migration, ongoing maintenance of HCM data, and coexistence scenarios, where core HR data is uploaded regularly. The HCM Data Loader (HDL) job in Oracle Fusion Human Capital Management (HCM) is a tool that allows for the bulk loading and maintenance of data.
To start an integration successfully, you have to define all the relevant parameters. Optionally, you can also define other properties and parameters that you want to pass to the integration in JSON format.
This page includes the following:
Defining Oracle Fusion Cloud ERP HCM Data Load Parameters
In the HCM Data Load section, you define the parameters relevant to run the job on your Oracle Fusion Cloud ERP environment.
-
Connection
Select the Oracle Fusion Cloud ERP Connection object containing the relevant information to connect to the application.
To search for a Connection object, start typing its name to limit the list of the objects that match your input.
-
Content ID
The content ID of the HCM data to be loaded.
-
Parameters Input Type
Allows you to pass arguments created at runtime to Oracle Fusion Cloud ERP in JSON format.
Select one of the options available:
-
None (default)
Select this option if you do not want to pass any parameters to Oracle Fusion Cloud ERP.
-
JSON
Use the JSON field to enter the JSON payload definition.
Important!There are many options available to define the JSON payload. For more information and examples of the JSON definition, see Defining the JSON.
-
File Path
Use the JSON File Path field to define the path to the JSON file containing the attributes that you want to pass to the application. Make sure that the file is available on the Agent machine (host).
-
Defining the JSON
This section gives you examples of how you could define the JSON field when defining an HCM Data LoadJob. You have different options available.
Simple JSON Definition
The first option to define the JSON field is a simple payload definition. To do so, make sure you define the parameters that you want to pass to Oracle Fusion Cloud ERP.
Example
{ "parameters": [ { "type":"STRING", "name":"shortValue", "value":"3"
} ] }
Using Variables
You can also use variables in the payload definition.
Example
In the JSON field, enter the following:
&JSON_VARIABLES#
If the variable is not defined yet, you must define it now. You do it on the Variables page of the HCM Data Load Job definition:
(Click to expand)
When you execute the Job, the variables will be replaced with the value you have just defined. This is visible in the Agent log (PLOG), see Monitoring Oracle Fusion Cloud ERP Jobs.
HCM Data Load Job in a Workflow
You can also use the JSON field if you want to include an HCM Data Load Job in a Workflow and you want to use Automation Engine variables in it.
Example
In the Workflow, a Script object (SCRI) with the variable definition relevant for said value and time precedes your HCM Data LoadJob:
(Click to expand)
In the HCM Data Load Job, the JSON definition includes those variables:
(Click to expand)
When the Job is executed, the variables will be replaced with the value you have just defined. This is visible in the Agent log (PLOG), see Monitoring Oracle Fusion Cloud ERP Jobs.
See also: