Before you ingress data, ensure that you have defined the following assets and objects:
1In Administrator, create a source connection to read data from source and a Business 360 connection to write to the Business 360 assets. For more information about creating connections, see Configuring a connection in the Administrator help.
2In Administrator, specify a Secure Agent that is up and running as a runtime environment to run a mapping task.
Note: Ensure that you don't share runtime environments between parent and sub-organizations. If you use a runtime environment of the parent organization in the sub-organizations, MDM SaaS can't retrieve the data from the parent organization.
For more information about Secure Agent, see Runtime environments in the Administrator help.
3Create a mapping in one of the following ways:
- Manual mapping. In Cloud Data Integration, create a mapping with the source connection as the source transformation and the Business 360 connection as the target transformation. Manually map the fields between the source and target transformations. For more information about manually creating a mapping, see Mapping configuration in the Data Integration help.
- Automapping. Start the mapping creation process from a business entity in Business 360 Console. In Cloud Data Integration, the business entity becomes the target for the mapping. After you select a source, Cloud Data Integration automatically maps the fields between the source and the target.
Ensure that you create an in-out parameter jobInstanceId in the Parameters panel.
Note: The name of the in-out parameter is case sensitive.
4In Cloud Data Integration, create a mapping task by selecting the runtime environment and adding the mapping that you create. For more information about configuring a mapping task, see Defining a mapping task in the Data Integration help.
5In Cloud Data Integration, create the required taskflows. Publish the taskflows to use in your ingress job. For more information about creating taskflows, see Taskflows in the Data Integration help.
Note: Ensure that you don't add a Command Task step to the taskflows that you create. If the taskflows contain the Command Task step, the ingress jobs fail.
6Consider the data source for the ingress jobs because not all the connectors available in IDMC can be used in the mapping for ingress jobs.
For example, you can't use the Databricks Delta connector with custom queries in an ingress mapping for MDM SaaS. Before you define an ingress job, identify the source systems and validate the connectivity.
7Validate the connectivity with the MongoDB Atlas instance and Business 360 Connector.
8To load a multibyte data set, meet the following requirements:
9Ensure that a match model is defined for the business entity.
10Without a match model, an ingress job can't generate match keys for source and master records.
11If you configure data quality rule associations for crosswalk standardization, Informatica recommends that you use the Business 360 FEP Connector to run ingress jobs.
For more information about configuring rule associations for crosswalk standardization, see Crosswalk standardization.
MDM SaaS allocates fixed memory to store field mappings for crosswalk standardization. When you run an ingress job that processes large volumes of data with crosswalk rule associations in business entities through the Business 360 Connector, you might exceed the allocated memory. The ingress job fails because of insufficient memory.
Rules and guidelines for importing data
Consider the following rules and guidelines when you create an ingress job to import data:
•Identify the differences between Business 360 Connector and Business 360 FEP Connector.
•When you ingress a large volume of data, use the chunking strategy to load a maximum of 25 to 50 million records per ingress job. To optimize the load time and help with the recovery time in case of any job failures, logically divide large source data into multiple jobs.
•If you change the name of a business entity or delete it in Business 360 Console, the existing mappings with references to that business entity fail when you run the mappings. When you run an ingress job that uses these mappings, the job fails.
•Ensure that the you don't create mappings in the advanced mode in Cloud Data Integration.
If you create mappings in the advanced mode with the Business 360 Connector or the Business 360 FEP Connector in the Target Transformation, you can't ingress data into MDM SaaS.
•Use Business 360 FEP Connector instead of Business 360 Connector for parallel execution and enhanced performance.
•In Data Integration, create separate mappings for hierarchy instances, root relationships, and relationships. Add each mapping to its own mapping task, and then add all the mapping tasks to a common taskflow.
•Ensure that the primary key of each relationship in a hierarchy is unique.
•If you want to insert, update, upsert, or delete field values of records in a single mapping, ensure that you add separate target transformations for each operation in Data Integration.
•Ingress jobs process records based on the operation type of the root field in Data Integration mappings, regardless of the operations specified for field groups. When you specify an update operation for any field group of records without a root field in Data Integration mappings, ingress jobs perform the update operation on the records.
•If you specify the update operation to update field values of existing records, the load step rejects records with field values that are identical to the field values of existing records.
•Ensure that you don't run ingress jobs that include taskflows associated with reference data assets to import the reference data assets into Reference 360.
To import reference data assets into Reference 360, ensure that you run a reference data import job in Reference 360.
•When an ingress job processes records that contain blank values in all fields of the root or field groups, MDM SaaS skips these records in the transform step even if source primary keys of the records are valid.
If records aren't skipped and come from a high-rank source system, the merge process might overwrite the existing master record values with blank values.
•When you configure an ingress job, ensure that the taskflows associated with the job don't contain mappings with different operations, such as update and delete, for the same set of records. If a taskflow contains mappings that perform different operations, the job processes only one mapping and ignores the other mappings.
For example, you want to update the first name and last name of an existing record and then delete the same record. When you configure an ingress job and associate a taskflow that contains two mappings for update and delete operations, the job updates the first name and last name of the record and doesn't delete the record. To perform both operations, if you create different taskflows, the job still processes only one operation and ignores the other.
To perform different operations on the same set of records, ensure that you run two separate ingress jobs.
•When you use rich text format in text fields, use only supported HTML tags and attributes. MDM SaaS removes unsupported tags and attributes for security reasons.
For more information about rich text formatting, see Rich text formatting for text fields.
Automapping source and target transformations
You can start the mapping creation process from a business entity in Business 360 Console. In Cloud Data Integration, the selected business entity is added as a target transformation. After you select a source connection, Cloud Data Integration automatically maps the fields between the source and target transformations.
1From the Explore page, open a business entity
2Click Actions, and then click Automapping.
The Automapping page appears in Cloud Data Integration.
3In Business 360 Console, on the Sources tab of the Choose sources and targets page, click Add Sources.
4 Select the packages and sources along with their objects.
You can select multiple objects. Use the Find field to search for the objects if required.
5Click Add.
The selected sources and their objects appear on the Sources tab.
6Optionally, verify the target business entity.
Note that the target is predefined and you can't configure it.
7Click Create Mapping.
The mapping appears in the mapping canvas. Save and validate the mapping.
You can configure the mapping to add one or more supported transformations.