Common Mapping Patterns

The following patterns appear in almost every CDM onboarding engagement. Recognising the pattern early saves significant time.

Pattern A: Customer Master → Multiple CDM Entities (1 source → many targets)

Most client systems store a "Customer Master" or "Party Master" table that combines what CDM considers three or four distinct entities. This is the most common pattern in banking, telco, and retail deployments.

Source columns in CUSTOMER_MASTER CDM target entity
CUST_ID, FIRST_NAME, LAST_NAME, DATE_OF_BIRTH, GENDER, MARITAL_STATUS, OCCUPATION ldz_party_demographic
CUST_ID, PAN_NUMBER, PASSPORT_NUM, AADHAAR_ID ldz_party_identity
CUST_ID, EMAIL_ADDRESS, MOBILE_NUMBER, HOME_PHONE ldz_party_contact
CUST_ID, ADDRESS_LINE1, ADDRESS_LINE2, CITY, STATE, PIN_CODE ldz_party_address_det

Pattern B: Multiple Source Tables → One CDM Entity (many sources → 1 target)

A client may have identity data split across two systems: a CRM with PAN numbers and a KYC platform with passport and biometric data. Both need to populate ldz_party_identity.

Source table Source columns CDM target entity
CRM_IDENTITY CUST_ID, PAN_NUMBER, INCOME_BRACKET ldz_party_identity
KYC_REGISTRY KYC_REF, PARTY_ID, PASSPORT_NUM, EXPIRY_DATE, KYC_STATUS ldz_party_identity
Important: When multiple sources feed one target, document the business key reconciliation explicitly. How is CUST_ID in CRM_IDENTITY linked to PARTY_ID in KYC_REGISTRY? If there is no direct join, a lookup table or master reconciliation mapping is required.

Pattern C: Account + Relationship (2 tables → 2 targets)

A source ACCOUNT table contains the account attributes. A separate ACCT_CUST_LINK table records which customers hold which accounts and in what role. These map to two distinct CDM entities:

Source table CDM target entity Why separate?
ACCOUNT_MASTER ldz_account_dtl Contains account attributes — what the account is
ACCT_CUST_LINK ldz_account_party Contains the account–party relationship — who holds it and in what role

Pattern D: Transaction Ledger → Multiple Transaction Targets

A general-purpose TRANSACTIONS table in the source may contain mixed transaction types. In CDM, these are separated by product type:

Source TXN_TYPE filter CDM target entity
TXN_TYPE IN ('DEBIT','CREDIT','TRANSFER') ldz_acct_party_trans
TXN_TYPE IN ('LOAN_EMI','PREPAYMENT','PENALTY') ldz_loan_trans
TXN_TYPE IN ('CC_PURCHASE','CC_PAYMENT','CASHBACK') ldz_creditcard_trans
TXN_TYPE IN ('SERVICE_FEE','ANNUAL_FEE','PROCESSING_FEE') ldz_fees_trans