Glossary · System coordination, integration and orchestration
Data mapping
Also known as: field mapping, schema mapping
German: Datenabbildung
In data integration, data mapping is the specification of how data elements of a source structure correspond to data elements of a target structure, including field correspondences, unit and format conversions and rules for missing or unmapped values.
- System integration
In one sentence
Data mapping specifies how fields of a source data structure correspond to fields of a target structure, including conversions and default rules.
Example
The mapping maps the ERP field “MATNR” to the MES field “MaterialId” and converts the order quantity from boxes to pieces.
How it applies
- Integration: Mappings are where semantics are lost or preserved. Map units, time zones, status codes and empty values explicitly; a silent default can turn “unknown” into “zero.”
- Engineering: Maintain mappings as versioned artifacts with test data, not only as code in an integration tool. Review them when either side changes its schema (see Schema (data)).
- Documentation: A mapping table (source field, target field, rule, example) is a valuable part of the interface documentation and helps support teams trace wrong values back to their source.
Data mapping vs. data transformation
Data mapping defines what corresponds to what. Data transformation is the execution that converts actual data according to mappings and further rules such as aggregation or enrichment.