Welcome
Interface Mapping Adoption Guide
How to Choose the Right Target Table
Use this decision guide when you are unsure which CDM entity to target. Work through the questions from top to bottom and stop at the first match.

HCL MaxAI CDM Documentation
Release Notes
Installation Guide
User Guide
Ops Guide
Interface Mapping Adoption Guide
- Introduction
  This Adoption Guide explains, in plain language, how to perform that mapping exercise end-to-end, from understanding your source data all the way to validated, signed-off mapping rows ready for metadata loading and ETL generation.
- Why Interface Mapping Matters
  A CDM onboarding project can only succeed if the mapping exercise is done well. Poor mapping has cascading effects across data quality, ETL generation, analytics, compliance, timeline, and MaxAI readiness.
- Where It Fits in CDM Onboarding
  CDM onboarding follows a structured lifecycle. The interface mapping exercise sits at the heart of the Discovery and Design phase — after source understanding and before any ETL or DDL is generated.
- Roles and Responsibilities
  The mapping exercise requires involvement from five key roles, each bringing specific expertise and perspective to ensure the exercise is complete and correct.
- Pre-requisites Before Mapping Starts
  Do not open the MID until the following artefacts have been collected from the client. Attempting to map without these leads to guesswork and rework.
- Understanding CDM Subject Areas
  You do not need to know the full CDM model in detail before starting. Use the subject area guide to identify which family of LDZ tables your source data likely belongs to.
- Mapping Principles
  These principles must guide every mapping decision. Violating them leads to data quality problems, ETL complexity, and rework.
- Step-by-Step Mapping Method
  Follow all eight steps in sequence for each source system in scope. Do not skip steps to save time — each step produces decisions that the next step depends on.
- How to Choose the Right Target Table
  Use this decision guide when you are unsure which CDM entity to target. Work through the questions from top to bottom and stop at the first match.
- Common Mapping Patterns
  The following patterns appear in almost every CDM onboarding engagement. Recognising the pattern early saves significant time.
- Worked Examples
  The following worked examples use a fictional retail bank, "Horizon Bank", which is onboarding its core banking data into CDM.
- Data Quality and PII Guidance
  Every mapping row in the MID should have at least one data quality rule. Every source column containing personally identifiable information must be flagged in the PII column.
- Handling Gaps and Extensions
  Not every source field will have a direct target in the standard CDM model. Follow a hierarchy of options before raising an extension request.
- Review and Sign-off Process
  The mapping is not complete until all three sign-off gates have been passed. The order matters — do not request engineering sign-off before business sign-off.
- Debugging and Validation Steps
  After the first ETL run, use the following structured debugging checklist to validate that data has loaded correctly from source to LDZ. Work through each check in sequence.
- Common Errors and FAQ
  This section addresses frequently encountered issues during the mapping exercise and provides remediation approaches.
- Final Checklist
  Use this checklist to confirm that the mapping exercise is complete and the MID is ready for handoff to engineering. Every item must be checked before sign-off.
CDM Redbook

How to Choose the Right Target Table

Use this decision guide when you are unsure which CDM entity to target. Work through the questions from top to bottom and stop at the first match.

Table 1. Target Table Selection Guide
If the source data describes...	Start with this subject area	Primary LDZ candidate
A person, customer, lead, or prospect as an individual	Party	ldz_party_demographic
A verified identity document (passport, PAN, national ID)	Identity	ldz_party_identity
A way to contact a party (email, mobile, social)	Contact	ldz_party_contact / ldz_contact_dtl
A physical location associated with a party or branch	Address	ldz_party_address_det / ldz_address_det
A formal financial or service account	Account	ldz_account_dtl
Who owns or is linked to an account and in what role	Account–Party Relationship	ldz_account_party
Account balances at a point in time	Account Balances	ldz_account_balances
A product in a catalogue	Product	ldz_product_dtl
A loan and its terms	Product – Loan	ldz_loan_dtl
A credit card and its limits/terms	Product – Credit Card	ldz_creditcard_dtl
A deposit holding	Product – Deposits	ldz_deposits_details
A financial movement or transaction	Transaction	ldz_acct_party_trans / ldz_loan_trans / ldz_creditcard_trans
A marketing campaign or execution record	Campaign	ldz_campaign / ldz_treatment_execution
Consent or regulatory preference	Consent	ldz_party_consent / ldz_party_gdpr_consents
A digital session, device, or clickstream event	Event	ldz_party_session_dtl / ldz_device_party_events
A relationship between two parties (parent–child, household)	Party Relation	ldz_party_relation
A branch or geographical unit	Branch	ldz_branch_dtl