Configuration Guide

10.3 HotFix 3
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

MDM Hub Cleanse Mapping

The MDM Hub sample Operational Reference Store (ORS) contains the mapping that generates primary keys. To generate the primary keys, the mapping trims white spaces around the customer IDs and concatenates the values with the

|Billing

constant. Also, the mapping adds the

BILL

constant to the address type.

To see the LGC Party to Billing Address mapping that generates primary keys, open the mapping in the Mappings tool from the MDM Hub sample ORS. The mapping includes the LGC Customer landing table and the LGC Party to Billing Address Stg staging table. The LGC Customer landing table is populated from the source through an ETL process.

The following image shows the LGC Party to Billing Address sample mapping in the MDM Hub Mappings tool:

A cleanse mapping, which contains a landing and a staging table, the Trim and the Concatenate functions, and constants.

The mapping that you create contains the following objects:

Component Name	Description
LGC Customer	Landing table that contains the source data that is populated from the source through an ETL process.
LGC Party to Billing Address Stg	Staging table to which the MDM Hub loads the cleansed and standardized data.
String function	The mapping contains the following string functions that cleanse and standardize data: Concatenate. Concatenates the customer ID with a string value. Trim. Removes white spaces around the customer ID.
Constant	The mapping contains the following constants: \|Billing. Constant that is concatenated to the customer ID. BILL. Constant that appears as the address type of the customer.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

MDM Hub Cleanse Mapping

MDM Hub Cleanse Mapping