Reference data management
Mapping Datasets
Make code translations between systems explicit and maintainable.
Different systems often use different codes for the same business concept.
An ERP, CRM, data warehouse or reporting platform may classify customers, products or cost centres differently.
A mapping dataset records those relationships as governed reference data so every consumer uses the same translation.
WH_LOCAL→B2BWH_INTL→B2BRETAIL→B2CDefinition
What is a mapping dataset?
A mapping dataset stores the relationship between values used by different systems.
It allows integrations, applications and reports to consistently translate one code into another.
- ERP → CRM
- Legacy → New Platform
- Internal Code → External Standard
- Cost Centre → Reporting Segment
Where it breaks
Why mappings end up in code
Mappings often start as spreadsheets, lookup tables or hard-coded transformations.
Over time, different systems start using different translations for the same value.
- Different results
- Different mappings
- Hidden business logic
- Unknown ownership
- No review process
- Difficult auditing
Hidden mappings
WHEN WH_LOCAL THEN B2Blookup.xlsxmapping.jsonetl_config.ymlDeterministic lookup
One source code, one answer
Each source value appears once.
Every consumer receives the same answer for the same lookup.
Many source codes can deliberately map to the same target, but a source code never produces competing answers within one publication.
WH_LOCAL→B2BWH_INTL→B2BWH_LOCAL→B2BWH_LOCAL→SMBEvery source code resolves to one published answer.
Visible exceptions
What happens when a new code appears?
Most mapping problems begin when a source system introduces a value that does not yet exist in the mapping.
That decision should be reviewed explicitly rather than hidden in integration code.
When the source dataset gets a new version, the mapping draft shows which codes are new and not yet mapped, and which were removed from the source.
Controlled change
Manage mappings through a controlled process
Mapping changes move through the same review and publication process as other governed reference data.
Base the mapping on a source dataset
Select the published source values and the field that identifies each code.
Review matches and exceptions
Confirm each translation and keep missing targets visible.
Publish the agreed crosswalk
Create an immutable mapping version with a release note and effective date.
Let consumers use the publication
Applications and integrations retrieve the same crosswalk through the API.
Effective dating
Publish mapping versions with effective dates
Mappings change over time.
A new business classification or migration may require a different translation in the future.
Both mapping versions remain available, so consumers can use the translation that applied on a particular date.
WH_LOCAL→B2BWH_LOCAL→SMBClear scope
A mapping dataset is not field mapping
Field mapping answers:
Which input column populates which field?
Mapping datasets answer:
Which business value corresponds to which business value?
Examples
Common mapping dataset examples
ERP to CRM
Translate customer and segment classifications.
SAP Cost Centres to Salesforce Territories
Map organisational structures across applications.
Legacy to New Platform
Support migrations while preserving meaning.
Cost Centre Mapping
Relate operational and reporting structures.
Internal Codes to Industry Standards
Map business classifications to industry standards.
Warehouse Dimensions
Align reporting data across sources.
Why refrncr
Why teams use refrncr for mapping datasets
- Published crosswalks
- One source code, one answer
- Review workflows
- Missing mappings remain visible
- Effective dates
- Version history
- Audit trail
- API access
Start with real data
Start with one mapping that changes too often in code
Choose a mapping currently maintained in spreadsheets, ETL jobs or application code.
Replace hidden translations with a single published mapping dataset and make it available through the API.