Data mapping
Data mapping defines how source data enters a target structure. Field names, meaning, units and error handling all need to fit.
Data mapping describes how source data is assigned to a target structure. It defines which source field populates which destination field and what transformations are required. Identical field names alone do not prove identical meaning.
In a hypothetical transfer, weight_kg contains 1.5 kg. The destination expects grams in weight_g, meaning 1500 g. Merely renaming the field and copying the number would be wrong. Conversion and the treatment of missing or invalid values belong in the rule.
A mapping can execute correctly while transferring incorrect source information. The business meaning therefore needs confirmation alongside technical implementation. A table of specific identifier pairs can be part of a solution; it does not replace rules for units or error cases.
Sources
Related terms
- Mapping tableA mapping table stores specific correspondences, such as identifier pairs from two systems. It makes a confirmed link reusable.
- Master dataMaster data describes core business entities such as customers or products. It is reused across processes and can still change over time.
- 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