Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 3 of 6

Mapping guidelines and proposals you can defend

11 min

Listen to this lesson

0:00 / 8:09

A mapping guideline (MAG) connects a source MIG to a target MIG and documents how each target node is filled: mapping lines, functions, conditions, constants and code value mappings. SAP Help calls it the runtime artifact you use in the mapping step of an integration application. For Great Lakes, the MAG GLFS_850_to_ORDERS05 maps the 850 MIG to Contoso's ORDERS05 MIG (the extended IDoc from lesson 1).

Three kinds of MAG

  • Graphical MAG: Standard holds the core mapping rules; once created it carries the label Base.
  • Graphical MAG: Overlay inherits every element of a base MAG and lets you retain, delete or override elements for one partner or use case. Changes to the base flow into overlays automatically.
  • XSLT MAG is uploaded as a finished XSLT file instead of drawn.

Create one under Design > MAGs > Create: choose the source MIG, the target MIG, then confirm name, summary and the source and target business context. The new MAG is Draft version 1.0. You can also copy a MAG alone, or copy it with its referenced MIGs.

Drawing the mapping

In the Mapping tab you drag a source node onto a target node. Mapping a group to a group creates one target instance per source instance, so mapping the PO1 loop to the E1EDP01 segment gives one IDoc item per X12 line. Mapping leaves without their groups lets the target structure follow the leaves. Supported cardinalities include 1:1 leaf-to-leaf, group-to-group and leaf-to-group, N:1 leaf-to-leaf, group-to-leaf, and 0:1 constants. Create 1:1 Mappings links identical nodes in two selected subtrees.

The core of the Great Lakes MAG: qualified instances on both sides map one to one, and the PO1 loop maps group to group so every X12 line becomes an IDoc item.
The Sign-Off Table · thesignofftable.com/academy/sap-pim-206

Most of the value comes from the details. Value transformations include date-time conversion (BEG05 CCYYMMDD to the IDoc date), string processing, code value mappings (unit EA to Contoso's PCE, local or as a reusable global code value mapping), and functions written in XSLT or XPath, which can be saved as shared code. A conditional mapping uses an XPath condition to control whether a target instance is created. Constants fill fields the partner never sends, such as sales organization 1710, distribution channel 10 and division 00 in E1EDK14. Global parameters read values set outside the mapping, for example headers from the EDI Splitter in Cloud Integration.

Sometimes the two structures are too different to map line by line, for example when the source nests data in a hierarchy the target flattens. For that case Integration Advisor offers pretransformation of the source MIG: a pretransformation script reshapes the source structure at design time so it can be mapped in the MAG, and it supplies a matching runtime artifact so the payload is reshaped the same way when the flow runs. Use it sparingly; most X12-to-IDoc mappings don't need it.

The proposal service

In edit mode, Proposals: Get Proposals flags target nodes for which other users have mapped similar MIGs in a similar business context; Proposals: Select Best Proposal accepts all top proposals at once, or you tick single ones in the mapping list. SAP's data collection page explains what feeds it: when a MIG or MAG is activated, structural content goes anonymously into a knowledge base: node properties, selected code values, qualifications, mapping lines, constants, code value mappings, and XSLT not marked confidential. Names, notes, example values, MIG codelists, administrative data and confidential XSLT stay out.

How proposals flow: they come from other users' activated guidelines, and Contoso's activated MAG feeds the same knowledge base in turn.
The Sign-Off Table · thesignofftable.com/academy/sap-pim-206

Proposals are a fast first draft, not a verdict. Other companies' Great Lakes-like partners may map N1 [ST] to a different IDoc partner function, or carry the buyer's part number where Contoso needs its own. Theo's rule: accept a proposal only when the developer can point to the line in the partner's spec that supports it, and record the reason in the mapping element's documentation. For the Great Lakes MAG, proposals filled 41 of 58 target fields; review rejected 6, including one that mapped PO107 (Great Lakes' own part number) to the material field instead of PO109 (Contoso's number under qualifier VP).

  1. Does the partner spec support the proposed source and target?Yes → next question · No → reject and note the spec line it contradicts
  2. Is the target qualified instance the right one (AG versus WE, 001 versus 002)?Yes → next question · No → reject, map the correct instance by hand
  3. Does it need a code value mapping, date format or function the proposal lacks?Yes → accept and complete the transformation · No → accept as is
  4. Is there a test payload that exercises it?Yes → done · No → add one before activation
Theo's four questions for every proposal, accepted or not.
The Sign-Off Table · thesignofftable.com/academy/sap-pim-206

Administrators can turn the proposal service off under Settings > MIGs and MAGs > Administrative Settings with Enable Proposal Service. Switching it off stops data collection from then on and removes proposals for the tenant; it doesn't delete data already collected. Nadia, Contoso's security and GRC lead, reviewed the data collection page and accepted the service, with one condition: any XSLT function that embeds partner-specific logic is marked confidential.

What would you do?

Proposals filled most of the Great Lakes MAG. One proposal maps N1 [ST] to E1EDKA1 with partner function AG (sold-to). The developer says it has a high score and the deadline is Friday. What should Theo decide?

Key points
  • A MAG maps a source MIG to a target MIG; standard, overlay and XSLT MAGs serve different needs.
  • Group-to-group mapping drives target instances; constants, code value mappings and functions do the detailed work.
  • Proposals come from anonymized structure of other users' activated MIGs and MAGs.
  • Accept a proposal only with a spec reference; record rejections and reasons.
  • The only Integration Advisor AI feature SAP documents is MIG & MAG Proposals; label any gen-AI mapping claim as unverified.

Check your understanding · not graded

Lesson check

  1. 1. Mapping the PO1 loop to the E1EDP01 group (group to group) has which effect?

  2. 2. Which content goes into the proposal knowledge base when Contoso activates a MAG?

  3. 3. Where does an overlay MAG get most of its mapping elements?

  4. 4. How should the course describe generative-AI mapping in Integration Advisor as of October 2026?