Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Informatica Platform Mapping

Informatica Platform Mapping

Create a mapping in Informatica Developer (the Developer tool) that generates primary keys. The mapping must trim white spaces around the customer IDs and concatenate the values with the
constant. Also, the mapping must add the
constant to the address type.
You set up the C_LD_LGC_CUSTOMER source data with the sample input data. Create a mapping with a physical data object, a mapplet, and a logical data object. The physical data object connects to the source data. The mapplet contains the transformation to generate primary keys. The logical data object writes to the staging table. You cleanse and move data directly from the source to the target staging table without the need for an ETL process.
The following image shows the mapping in the Developer tool:
A mapping, which contains a data source and a target staging table, and a mapplet that contains the Expression transformation.
The following image shows the mapplet that you use in the mapping in the Developer tool:
A mapplet, which contains an Expression transformation with expressions to trim and concatenate source data.
The mapping that you create contains the following objects:
Object Name
The physical data object that you create to represent the data source.
Reads data from the data source.
The mapplet that is created during the synchronization process.
You add the Expression transformation to the mapplet.
Expression transformation to cleanse and standardize data.
Contains the following ports:
  • CUST_ID. Pass-through port to pass customer IDs from the data source.
  • OP_CUST_ID_TRIMMED. Output port that returns customer IDs after it trims white spaces with the
  • OP_PKEY_SRC_OBJECT. Output port that returns primary keys after it concatenates the |Billing constant to the customer ID with the
  • OP_BILLINGTYPE. Out put port that returns the BILL constant that is added to the address type output with the
  • TRIMMEDCUSTID. Variable port that returns the customer IDs after it trims the white spaces to the right and the left of the customer IDs with the
The logical data object that is created during the synchronization process. Represents the target staging table, LGC Party to Billing Address Stg, and writes the cleansed and standardized data to the staging table.


We’d like to hear from you!