A modernization mapping file is an XLS or XLSX file that includes details about the objects in the MDM Hub and MDM SaaS. MDM SaaS generates mapping files by using its configuration and the MDM Hub configuration files you upload.
After you generate mapping files, review them thoroughly to understand the objects in MDM SaaS and the MDM Hub.
You can use the following mapping files to modernize the objects in the MDM Hub:
•Reference data mapping file. Contains details of lookup tables and Reference 360 code lists.
•Data model mapping file. Contains details of base objects and their columns or business entities and their fields.
A mapping file contains multiple sheets with object details from MDM SaaS and the MDM Hub.
The following table describes the sheets that you can find in a mapping file:
Sheet Name
Description
M-Index
Provides an overview of the mapping file and the uploaded file.
M-SourceEntities
Lists the lookup tables, base objects and their columns, or business entities and their fields from the change list XML file. The objects vary based on the mapping file.
M-OnPremise-BE
Lists all business entities in the MDM Hub. Applicable only for the data model mapping file.
<Name of a Code list> | <Name of a lookup table>
Lists all code lists from Reference 360 as individual sheets. Applicable only for the reference data mapping file. You can also include sheets for all the look tables in the MDM Hub.
The lookup tables and their columns, base objects and their columns of the MDM Hub appear as drop-down values in the source columns of these sheets.
<Name of a Business Entity>
Lists all business entities from MDM SaaS as individual sheets. Applicable only for data model mapping file.
The business entities and their fields of the MDM Hub appear as drop-down values in the source columns of these sheets.
M-Exceptions
Lists the business entities and their fields that aren't mapped in the target and source columns of the mapping file.
This sheet appears after you upload the mapping file. The modernization process validates the mapping file and populates the sheet with business entities and their fields that aren't mapped.
You can review the details in the sheet and map the required ones.
Error
Lists validation errors in the mapping file, such as field mapping missing in a column or field type mismatch.
This sheet appears after you upload the mapping file. The modernization process validates the mapping file and populates the sheet with validation errors.
After you resolve the errors in the field mappings, upload the mapping file again to proceed with modernization.
Reference data mapping file
A reference data mapping file includes multiple sheets. Each sheet represents a code list from Reference 360. If you select to include lookup tables when you create a mapping file, the mapping file also includes sheets for all lookup tables.
The source columns in each sheet display lookup tables and their columns as drop-down values. You can map the attributes of code lists, such as Name, Code, and Description, with the columns of a lookup table.
During modernization, if you don't have a corresponding code list for a lookup table, the modernization process can create a code list for the lookup table.
Note:
You can't manually add custom attributes of a code list to the sheets in the reference data mapping file. After modernization, you can add custom attributes to the code lists.
Each code list sheet in the mapping file displays the following details:
Column Name
Description
<Reference Codelist>
Name of the code list to which you want to map a lookup table.
<Name of a lookup table>
Name of the lookup table in the MDM Hub that was included in the mapping file. The sheet name uses the name of the lookup table.
Dependent Codelist Parent
Name of the parent code list. For example, the Country code list is the parent of the State code list.
Applicable only when the code list related to the sheet is a dependent code list.
Target R360 Reference Set
A list of default attributes of the code list related to the sheet, including their data types. The default attributes are Name, Code, and Description.
Source MDM Lookup
Placeholder to map a lookup table and its column for each attribute.
The following image shows a sample sheet in a reference data mapping file:
Sheets for lookup tables
By default, a mapping file contains sheets for all the code lists in Reference 360. These sheets allow you to map lookup tables to every code list.
You can also include sheets for all the lookup tables in the MDM Hub. The modernization process uses these sheets to create code lists in Reference 360.
For example, if the MDM Hub has 50 lookup tables and Reference 360 has 30 code lists, you can map 30 lookup tables to the 30 code lists. For the remaining 20 code lists, you don't have equivalent code lists in Reference 360, but you have a requirement for them in MDM SaaS.
To modernize them, you can choose to add sheets for all the lookup tables. Using these sheets, you can create code lists for these lookup tables in Reference 360 during modernization. You can delete other irrelevant sheets created for lookup tables that you don't need. The sheets that are created for the lookup tables use the following naming format:
LU<Name_of_the_lookup_table>
The following image shows a sheet created for a lookup table:
In the Custom column, enter X to indicate that the code list and its attributes need to be created in Reference 360.
Data model mapping file
A data model mapping file contains details of base objects and their columns or business entities and their fields. The mapping file includes separate sheets for each business entity in MDM SaaS.
You can either generate a data model mapping file based on the base objects or business entities of the MDM Hub.
A data model mapping file based on base objects uses the base objects and their columns of the MDM Hub for mapping. A data model mapping file based on business entities uses the business entities and their fields of the MDM Hub for mapping. Within a sheet, map each business entity field of MDM SaaS to a business entity field or a base object column of the MDM Hub.
If an application has more than one business entity with the same name, the sheet names include a number suffix. For example, if Customer 360 has three business entities named Person, the mapping file contains the Person, Person2, and Person3 sheets. To find the business entity that a sheet maps to, check the business entity name in cell E1 of the sheet.
If business entities in MDM Hub include fields that don’t exist in MDM SaaS, you can create those fields as custom fields. For example, consider a business entity called Account in the MDM Hub that contains additional fields, such as Loan_Account and Loan_Type. When you start mapping the fields in the mapping file, you realize that MDM SaaS doesn't have equivalent fields to map with them. You can manually add these fields as custom fields in the mapping file and then map them to a column of a base object or business entity field in the MDM Hub.
Note:
For existing projects, you can still upload mapping files that you downloaded in earlier releases. When you download a mapping file again, the first row of each sheet contains the name of the MDM SaaS business entity.
The following image shows a sample sheet in a data model mapping file based on base objects:
The following image shows a sample sheet in a data model mapping file based on business entities:
Adding custom fields and field groups
If business entities in MDM SaaS don’t include certain fields or field groups present in the MDM Hub, you can add them as custom fields or field groups.
When adding custom fields, prefix the attribute name with either X_ or x_ to indicate that it's a custom field. Also, ensure that you mark custom fields with the character X in the Custom column to indicate that they are custom fields.
Similarly, you can also add custom field groups to the mapping file. When you add a custom field group, ensure that you prefix the character X_ to the name of the field group. For example, when you add a custom PostalAddress field group, ensure that you prefix the character X_ in the following format:
c360.person.X_PostalAddress
Note:
Ensure that you don't delete or add sheets in a data model mapping file.
The following image shows custom fields added to the data model mapping file:
The following table describes the headers included in a sheet related to a business entity of MDM SaaS:
Column Name
Description
On Premise Root BE
A root business entity from the MDM Hub. For example, if the sheet name is Person, you can select Individual as a root business entity from the MDM Hub.
Placeholder to map a base object and its column or a business entity and its field to each attribute of the business entity in MDM SaaS.
Note:
After you map picklist fields in a data model mapping file, ensure that the corresponding lookup tables are mapped in the reference data mapping file. If you miss to map a lookup table that a business entity field or a base object column uses, the modernization process returns validation errors.
You can insert new rows to the data model mapping file with the field details, such as name and type and then map them to the corresponding MDM Hub fields. When you add the field name, ensure that you prefix the name with the character X or x to indicate that it's a custom field. Also, ensure that you mark the Custom column with the character X or x to indicate a custom field. You must prefix the field group name with character X or x to indicate a custom field group. You can't create custom fields for smart fields, such as address, phone, and email.
After modernization, the custom fields mapped in the mapping file uses the field properties of the MDM Hub including the display name. However, the predefined MDM SaaS fields uses only the privileges from the MDM Hub.
Mapping on-premises root node
In the MDM Hub, the root node is the uppermost node in a business entity. You can add multiple child nodes to a root node within a business entity.
The child nodes within the business entity are equivalent to the field groups in MDM SaaS. For example, a Person root node in the MDM Hub can include Contact Address, Telephone, and Email Address as child nodes. In MDM SaaS, a business entity can include field groups, such as Address, Phone Number, and Email Address.
Generating mapping files
You can generate mapping files based on the configuration details of the MDM Hub and the data model of MDM SaaS. After you download them, you can map the MDM Hub objects with the MDM SaaS objects.
If you choose to map the fields manually, you can generate separate mapping files for reference data and data model objects. If you choose to create business entities in the MDM Hub automatically in MDM SaaS, you can generate a mapping file only for reference data objects.
You can also regenerate mapping files for changes in the data model of MDM SaaS after the initial mapping file generation. For more information about modernization mapping files, see Modernization mapping files.
Step 1. Generate reference data mapping file
By default, a reference data mapping file includes separate sheets for each code list in MDM SaaS.
1To create separate sheets for all the lookup tables in the MDM Hub, on the Map Fields page, select Include lookup tables from the MDM Hub in the mapping file.
Note:
For more information about lookup table sheets, see Sheets for lookup tables
2Click Generate Mapping File.
3Select the file format, and click Download.
4Open the downloaded mapping file, and map the fields.
You can add or remove any of the sheets and upload the mapped file.
5To upload the mapped reference data mapping file, click Browse, and select the mapped file.
Note:
You can't upload a mapped file that's associated with a different project or an older version of the mapping file.
6Click Upload.
After you generate a mapping file, if the reference data is updated in Reference 360, you can regenerate the mapping file to reflect the changes.
7To regenerate a reference data mapping file, click Regenerate Mapping File in the Reference Data section.
8To download the latest version of the reference data mapping file, click Download latest reference list.
Step 2. Generate data model mapping file
If you select manual mapping during project definition, you can generate a data model mapping file to map business entity attributes from MDM SaaS with base object columns or business entity fields from the MDM Hub.
1In the Data Model section, select one of the following options:
- Base Object. Indicates to include base objects of the MDM Hub and their columns in the mapping file.
- Business Entity. Indicates to include business entities of the MDM Hub and their fields in the mapping file.
2Click Generate Mapping File.
The Download Mapping File dialog box appears.
3Select the file format, and click Download.
Note:
If a data model mapping file contains more than 255 base objects, ensure that you download the mapping file as an XLSX file.
4Open the downloaded mapping file, and map the fields.
For more information about mapping fields in a data model mapping file, see Data model mapping file
Note:
You can't add or remove any of the sheets.
5To upload the mapped data model mapping file, click Browse, and select the mapped mapping file.
Note:
You can't upload a mapped mapping file that's associated with a different project or an older version of the generated mapping file.
6Click Upload.
After you upload a mapping file, if the data model is updated in MDM SaaS, you can regenerate the mapping file to reflect the changes.
7To regenerate a data model mapping file, click Regenerate Mapping File in the Data Model section.
8To download the latest version of the data model mapping file, click Download latest entity list.
9Click Next.
The Modernize page appears.
Guidelines for mapping objects in modernization mapping files
When you map objects in the modernization mapping files, consider the following guidelines:
•You can add or remove sheets from the reference data mapping file before uploading it. However, you can't add or remove sheets from the data model mapping file.
•Don't modify the names of code list attributes or business entities and their data types in the mapping files. The modernization process doesn't process these changes.
•Ensure that the lookup table columns mapped with business entity fields in the data model mapping file are also mapped in the reference data mapping file.
•If you don't want to modernize hierarchies and relationships, ensure that you don't map any business entity to the On Premise Root BE field in the data model mapping file.
•Regenerating modernization mapping files resets the existing mappings. After regenerating, you need to remap the fields and upload the mapping files. If you re-upload the configuration files or if MDM SaaS includes configuration changes, you must regenerate mapping files.
•Don't map MDM SaaS field types if their length is shorter than that of the corresponding MDM Hub object fields.
