Target transformation mapping example

An organization uses Salesforce to manage customer data. To master the customer data, the organization wants to load the customer data to the Business 360 data store. Use the Business 360 Connector to read data from Salesforce and write data to the Business 360 data store.

1Create a Business 360 connection.

2Create a connection.

3Create a mapping.

4Add a Source transformation, and specify a name and description in the general properties.

5Select the connection to the Salesforce application.

6On the Target tab, perform the following steps:

aIn the Connection field, select the Business 360 connection.
bIn the Source Type field, select Single Object.
cIn the Objects field, select the target object to which you want to write data.

The following image shows the target assets:

dTo view the list of supported business applications, on the left pane, select Home.
eTo view the list of available assets, select the asset type under an application. For example, if you select Customer 360 and Business Entities on the left pane, you can view the list of available business entities on the right pane from which you can select the required target object.
fTo view the list of custom assets, on the left pane, expand Custom Assets, and select an asset type.

The custom assets are grouped based on the asset type.

The list of custom assets appears on the right pane. For example, if you choose Hierarchies, the list of hierarchies appears on the right pane.

Note: You cannot map multiple source objects to a hierarchy. If you map multiple source objects to a hierarchy, an error appears when you map input fields to target fields on the Field Mapping tab. Ensure that you create separate mappings for each source object to the hierarchy. If you change the name of the custom business entity or delete it in the Business 360 Console, the existing mappings with references to that custom business entity will fail when you run the mapping.

gTo select relationships within hierarchies, expand Custom Assets, and then click Hierarchies. Select the required relationship from the right pane.

Note: To specify relationships within hierarchies as the target object, ensure that you specify unique display names for each relationship within a hierarchy. Don't select the relationship from the Relationships folder under Custom Assets.

7On the Field Mapping tab, select the input fields that you want to map to the target fields.

Map the following fields from the Input Fields section to the Target Fields section based on the purpose of the fields described in the following list:

- BusinessId. Optional. Unique identifier for the input records.

Note: When you ingress hierarchies or relationships, ensure that you don't map the BusinessId field.

For more information about using business IDs in the ingress process, see Ingress data with business ID in the Business 360 Console help.

- sourceLastUpdateDate. Optional. The ingress process uses the sourceLastUpdateDate field to import the updated date of a field or field group from the source system. Currently, you can map the sourceLastUpdateDate field to the required root fields and root field groups. To view the sourceLastUpdateDate fields in the Target Fields section, expand the _cm nodes within a field group. The last updated date is essential to establish the best version of the truth when you import data from multiple source systems into the Business 360 data store.

For more information about establishing the best version of the truth, see Establishing the best version of the truth in the help of business applications.

If you map the sourceLastUpdateDate field but the field value isn't in the input file, then the process updates the value in one of the following ways:

▪ For a root field, the mapping considers the last updated date of the root field as the value.
▪ For a field group, the mapping considers the sourceLastUpdateDate field value of the root field as the value.
▪ For the root field and field group, the mapping considers the last updated date of the root field as the value.

Note: You can't map the sourceLastUpdateDate field to nested field groups.

The following image shows the input fields on the left pane in a hierarchical format and the target fields on the right pane:

If you have multiple source objects mapped to a target transformation, you must define primary and foreign keys. For more information, see Primary and foreign key.

Note: When you map field groups, map the root fields first before mapping the fields within field groups.

8Go to Target > Parameters Panel > Input-Output Parameters, and create a parameter.

The input-output parameter is internally mapped to the job instance ID. When you run an ingress or export job, Cloud Application Integration process passes the job instance ID to the input-output parameter in Cloud Data Integration. Based on the defined taskflows, the job is executed. If you do not define the input-output parameter for the Target transformation in Cloud Data Integration, your job fails.

The following image shows the input-output parameter dialog box:

9Draw links to connect the Source transformation to the Target transformation.

10Save the mapping.