Master Data Management
Shared codes mean the same thing in every system.
Units, materials, statuses and country codes are small lists with large consequences. Autonera governs them as controlled vocabularies, maps them to each system and manages change with impact review.
How it works
Govern a code list and its mappings
Translate an incoming supplier or ERP code to the governed value. Deprecate a code to see its impact and choose a replacement; the deprecated code then translates automatically.
| Code | Label | ERP | Supplier | Commerce | Status | Action |
|---|---|---|---|---|---|---|
| SS316 | Stainless steel 316 | V4A | 316SS | 316 stainless | Active | |
| SS304 | Stainless steel 304 | V2A | 304SS | 304 stainless | Active | |
| CS | Carbon steel | ST37 | C-STEEL | carbon steel | Active | |
| SS-GEN | Stainless steel (unspecified) | VA | SS | stainless | Deprecated → SS304 |
TRANSLATE AN INCOMING CODE
Governed code SS304 (via deprecated SS-GEN)
GOVERNED CHANGE
Select Deprecate on a code to see its impact. Codes are never deleted; deprecated codes translate to their replacement.
The capability
Small lists that every other process depends on
Reference data is the set of codes and terms other data relies on: units of measure, material grades, country and region codes, lifecycle statuses, hazard classes. The ERP calls a unit ST, the supplier PC and the website each. Without a governed list and mappings, every integration contains its own translation table, and they disagree.
Reference Data Management holds each list as a controlled vocabulary with an owner, definitions and alignment to a standard where one applies. Crosswalks map each governed code to its representation in ERP, supplier, commerce and partner systems, so integrations translate codes consistently.
Codes change, but they are not deleted. Deprecating a code requires a replacement and shows how many records and which systems are affected before the change is approved. Incoming deprecated codes then translate to their replacement, and unknown codes are routed to the list owner rather than loaded.
Problems it solves
Where this work usually breaks down
Translation tables in every integration
Each interface maps unit and material codes differently.
Free-text where codes belong
Material written as stainless, SS, 304 or V2A breaks filters and comparisons.
Deleting codes in use
Removing an obsolete code orphans thousands of records.
No owner for shared lists
Anyone can add a value, so lists grow with near-duplicates.
Functional capabilities
What Reference Data Management includes
- Controlled vocabularies
- Govern code lists with definitions, owners and status.
- Standards alignment
- Align lists with external standards where they apply, such as unit-of-measure codes.
- Cross-system crosswalks
- Map each governed code to ERP, supplier, commerce and partner representations.
- Incoming code translation
- Translate codes on intake and route unknown codes to the list owner.
- Deprecation with replacement
- Retire codes without deleting them, translating to an approved replacement.
- Change impact review
- Show affected records and systems before approving a change.
In industrial operations
A distributor rationalizes material codes
Material appears in 14 spellings across ERP, supplier files and the website, including an unspecified stainless value.
- A controlled material vocabulary is defined with an owner and definitions.
- Crosswalks map ERP and supplier codes to governed values.
- The unspecified stainless code is deprecated after reviewing its 312 affected records.
- Incoming files now translate material codes on intake; unknown ones are routed to the owner.
Result: Material values are consistent across systems and filters, and changes to the list are reviewed before they apply.
Autonomous operations
How autonomous execution changes reference data management
Agents translate codes on every exchange and propose mappings for new values; list owners decide additions, deprecations and replacements.
Agents carry out
- Translate incoming codes
- Propose mappings for unknown values
- Measure usage and deprecation impact
- Update records after an approved replacement
People decide
- Own each code list
- Approve new codes and mappings
- Approve deprecations and replacements
Evidence recorded
- List versions and change history
- Mapping approvals
- Records updated by each replacement
Related capabilities
Works alongside
Multi-Domain Master Data Management
Product, supplier, customer and location masters connected through one model.
Feature guideIndustrial Classification & Standards Mapping
Crosswalk local classes and features to ETIM, ECLASS and UNSPSC.
Feature guideData Mapping & Transformation
Source-to-target mappings and transformations you can preview and validate.
Feature guideValidation & Completeness
Category-specific rules, severities and completeness scores with clear explanations.
Capability areaMaster Data Management
See where Reference Data Management fits in the wider Master Data Management capability.
Buyer FAQs
Questions evaluators ask
What counts as reference data?
Shared codes and controlled terms: units, materials, countries, statuses, hazard classes and similar lists.
Do you supply standard code lists?
Lists can be aligned to standards you use. Licensed standards and their specific versions are confirmed during evaluation.
Can codes be deleted?
Codes are deprecated with a replacement rather than deleted, so history and references remain valid.
How does this differ from industrial classification?
Classification standards organize products into classes. Reference data governs the code lists that attributes and systems share.
Who can add a new code?
Each list has an owner. New codes and mappings can require approval.
Your next step
See Reference Data Management on data like yours.
Bring a real file, catalog or record set. We will walk through how Autonera would handle it and where your team keeps the final say.
Book a Demo