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:

The following image shows the mapplet that you use in the mapping in the Developer tool:

The mapping that you create contains the following objects:

Object Name	Description
Read_C_LD_LGC_CUSTOMER	The physical data object that you create to represent the data source. Reads data from the data source.
C_SG_ LGC_PTY_BILL_ADDR_Mapplet	The mapplet that is created during the synchronization process. You add the Expression transformation to the mapplet.
Exp_LGCPartytoBilingAddress	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 TRIMMEDCUSTID expression. OP_PKEY_SRC_OBJECT. Output port that returns primary keys after it concatenates the |Billing constant to the customer ID with the CONCAT(TRIMMEDCUSTID,'|Billing') expression. OP_BILLINGTYPE. Out put port that returns the BILL constant that is added to the address type output with the 'BILL' expression. 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 LTRIM(RTRIM(CUST_ID)) expression.
Write_C_SG_LGC_PTY_BILL_ADDR_LDO	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.