Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

Value mapping translates identifiers used differently by connected systems. It supplies an agreed correspondence, such as one system’s country code to another’s expected code.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

Integration connects applications so they can exchange information. A delivered message still needs the receiving application to understand and accept its business meaning.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP Integration Suite value mapping: Translate business identifiers deliberately
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SAP Cloud Integration value-mapping artifacts and documented ValueMappingApi/ITApiFactory interfaces. Example agency/identifier/code pairs are fictional; deployed artifact state, runtime support and reverse-default policy require tenant-specific verification.

Documentation review on 14 November 2026 using official SAP sources and indexed official excerpts where full Help text was unavailable. Scope and service or release differences are explained in the lesson. All datasets, requests and checks are illustrative; no customer SAP runtime execution or measured results are claimed.

A MANUFACTURING EXAMPLE

Translate the supplier's plant identifier correctly

Translate the business identifier

Source plant: A01. Receiver plant: 1000. Mapping pair: A01 → 1000. Context: Relevant mapping domain
What to notice: An identifier needs the agreed cross-system correspondence, not just a similar-looking text value.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Source plant
A01
Receiver plant
1000
Mapping pair
A01 → 1000
Context
Relevant mapping domain
Words you’ll meet in this guide
Message
A package of information sent between systems.
Payload
The business content carried in a request or message.
API
A defined interface for another program to use.
Receiver
The system to which a message or request is sent.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Source identifier → Agreed value mapping → Target identifier. Conceptual diagram for SAP Integration Suite value mapping: Translate business identifiers deliberately.
Apply the idea: A manufacturer's partner sends one plant code while the receiving system expects another business identifier.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Translate the supplier's plant identifier correctly

    A manufacturer's partner sends one plant code while the receiving system expects another business identifier.

  2. Translate an identifier within its business context

    Value mapping translates agreed representations of the same business concept across systems.

  3. Understand agency, identifier and value as one lookup contract

    The agency names the representation owner/context and the identifier names the kind of identifier in that context.

  4. Worked case: source plant A01 must become receiver plant 1000

    Imagine a warehouse interface receiving plant A01 from ERP_A.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.