Mapping table
A mapping table stores specific correspondences, such as identifier pairs from two systems. It makes a confirmed link reusable.
A mapping table records specific correspondences in tabular form. In an integration, it can store which customer record in the source system belongs with which record in the destination. It is one possible implementation of part of a data mapping.
In the hypothetical example, CRM:A-10 is linked to ERP:C-10. System name and identifier are recorded together so that an identical number from another system is not accidentally given the same mapping. The business must define which relationships are allowed.
The table's existence alone does not create a correct link. Entries need a reliable basis and rules for changes and deletion. A missing mapping cannot be treated as confirmed. An identifier pair does not automatically grant access rights either.
Sources
Related terms
- Data mappingData mapping defines how source data enters a target structure. Field names, meaning, units and error handling all need to fit.
- Duplicate detectionDuplicate detection finds records that might describe the same entity. A match is initially only a suspected duplicate, not an automatic decision to merge.
- Transactional inboxA transactional inbox uses durable message records to protect local processing against duplicate deliveries.
- Message acknowledgementA message acknowledgement tells the broker that a delivery has been received or processed according to the agreed rule.
- Retry jitterRetry jitter varies waiting times randomly to spread retries and reduce simultaneous requests from many clients.
- Test tenantA logically bounded customer context of a multitenant application, configured for testing.
Articles on this topic
APIs & Integration with ASES
ERP, CRM and shop cleanly connected