Value Mapping: How Global Companies Finally Standardise Master Data Across ERP Systems
Mapping old values to new ones sounds simple and is one of the most fragile parts of any ERP transformation. What goes wrong when value mapping lives in Excel, why multi-key mappings break spreadsheets, and how vise LoV-MAP turns mapping into a governed catalogue reused across waves, operating companies and targets.
· Andrzej Bartosiewicz · updated 3 November 2026
Why value mapping has become a critical problem
Every ERP transformation or carve-out starts with a commitment to clean up master data. Weeks later, finance and master-data teams are harmonising chart of accounts, cost centres, materials, plants and customers across several systems — in large spreadsheets. Mapping old values to new ones sounds simple. In practice it is often the most fragile and risky part of the project, and the risk grows with every copy-paste and every e-mail attachment.
vise LoV-MAP was built for exactly this moment: one central place to define, validate and govern mapping logic, with full traceability.
What goes wrong when value mapping lives in Excel
| Pattern | What it looks like |
|---|---|
| Multiple file versions | Mapping_final_v7_corrected_NEW(2).xlsx — and nobody is sure which one the load used |
| Conflicting mappings | One legacy cost centre assigned to two different targets |
| No dependency validation | Storage locations mapped without checking their plant |
| Hidden business rules | Exceptions live in e-mails, not in the mapping file |
| No reusability | Every project, every wave, every operating company starts from zero |
With one wave and one target the problems are survivable. With several waves, operating companies or target systems they become uncontrollable.
LoV-MAP: a single source of truth for all value mappings
LoV-MAP is a central directory for master-data mappings, connecting SAP ECC, S/4HANA, non-SAP ERPs, CRM systems, data warehouses and planning tools. It is organised around three capabilities.
Central value-mapping catalogue
Chart of accounts, materials, customers, plants, storage locations, payment terms, countries, currencies, units — all master-data objects in one place instead of scattered spreadsheets. The catalogue is the foundation for everything else.
Multiple targets and projects
Mappings are reused across migration waves and operating companies. Target-specific logic applies per destination system, and validity periods control when a mapping applies — no rebuilding the same logic for every rollout.
Versioning and approvals
Every change is recorded and auditable. Changes go through an approval step before they are used, which is what compliance and audit teams need to see.
Single-key vs multi-key mappings: where Excel still fails
Most spreadsheets assume one old value maps to one new value. Real master data depends on combinations of keys, and that is where Excel produces broken dependencies, inconsistent mappings and faulty load files.
| Mapping type | Key combination | Why Excel struggles |
|---|---|---|
| Storage location → plant | The location depends on its plant | The dependency is ignored |
| Customer + sales area | Composite key | Both parts must be mapped together |
| Material + plant | Different logic per plant | Single-column logic breaks |
Example: storage locations that belong to plants
In a real project, storage locations were mapped in Excel without checking the plant they belonged to. The consequences: incorrect stock levels, failed postings and emergency corrections during cut-over. LoV-MAP models this as a two-key mapping — (plant, storage location) → (new plant, new storage location) — validates the dependency, confirms the target combination exists, and refuses to save an inconsistent mapping.
Built for business users, trusted by IT
| Audience | What they get |
|---|---|
| Business teams | An Excel-like interface, bulk updates, clear ownership, a workflow for proposals and approvals |
| IT and migration teams | Clean export to vise DMW, vise Data Run or BODS; an API for BAU automation; strict validation that protects SAP |
Where customers use LoV-MAP today
- ERP and S/4HANA migrations. Reusable mappings across waves and operating companies instead of reinventing them per rollout.
- BAU master-data governance. One catalogue, maintained daily by the master-data team, long after the migration ends.
- Reporting and analytics. Consistent mappings across ERP, BW, planning and analytics, so reports reconcile across sources.
When LoV-MAP is the right choice
- More than one ERP, or more than one rollout wave.
- High audit and compliance requirements on master data.
- Multi-key mapping dependencies.
- Mapping files too large to manage safely in Excel.
- A need for one catalogue covering both migration and BAU.
Ready to turn mapping from a risk into an advantage?
Send us a sample mapping file — Excel, CSV or an export. We show you the same file in LoV-MAP with full validation applied, and what it would have caught. Request a LoV-MAP proof of concept.