SAP’s Base-Overlay – Best Practices

The Base–Overlay concept provides an efficient way to manage variations across multiple business partners who use the same message formats. It eliminates redundant work by allowing you to maintain one standard mapping while accommodating partner‑specific differences such as date formats or item‑level details.

In the past year, I’ve spent a lot of time working with and perfecting the set-up of my Base-Overlay mappings, which has helped me to create quality mappings at a much quicker pace. In this blog, I wanted to share some of my tips & tricks for setting up the Base-Overlay MAGs.  Use Naming Conventions

Before you create the Base MIGs for your Base mapping, make sure to use a reasonable naming convention, so that you can filter and immediately find the corresponding MIGs and MAGs, in case you need to make changes to these in the future. I personally use the following naming conventions:

MIGs: “Base-Overlay_TypeSystem_MessageType_TypeSystemVersion”

Base MAG: “(Source) Base-Overlay_TypeSystem_MessageType_TypeSystemVersion_TO_(Target) Base-Overlay_TypeSystem_MessageType_TypeSystemVersion”

Overlay MAG: “PARTNER_“(Source) Base-Overlay_TypeSystem_MessageType_TypeSystemVersion_TO_(Target) Base-Overlay_TypeSystem_MessageType_TypeSystemVersion”

Qualify your MIGs

Qualifying your MIGs helps to run a formal, system-enforced validation that proves the MIG is structurally correct, semantically valid, and fully compliant with the message standard (ex. EDIFACT, X12, XML, IDOC) – it also helps significantly with your MAG message mapping, making it easier to map and eliminating any coding-related mapping errors.

** Note: You can keep qualifying your Base-Overlay MIGs to your new partner’s requirements even after you have created the Base and Overlay mappings for other partners. Updating the Base and Overlay mappings with added qualifications does not disturb what is already mapped.

** Note: Qualifying a segment will automatically create a 0:1 cardinality. Make sure that this is the desired cardinality for each qualified occurrence.

Use Consistent MIG Structures to Avoid Matching Errors

Avoid unnecessary structural changes in your MIG, including segment group renumbering, moving segments, deleting any qualified segments, deleting any used MIG codelists, etc. You can always add to your Base-Overlay MIG, but never delete or change already existing logic and elements that are used in your Base-Overlay MAGs. This will immediately destroy those fields upon MAG versioning.

Design the Base MAG as a “Golden Standard”

Your Base MAG is going to consist of the mappings that occur for the majority of your partners and it will be generic. Avoid any partner‑specific logic, date formats, or conditional rules in the Base – this will be addressed in your Overlay. Only use global parameters and shared code in the Base if they apply universally (these will be inherited automatically in your Overlays). If you include an envelope in your mapping, make sure the partner-specific identifiers are left out in your Base MAG – these will be added in your Overlay MAG. This is the same for any partner-specific segments, like free-text or payment conditions. A clean Base ensures Overlays inherit a stable foundation.

Test Base MAG Thoroughly Before Creating Overlays

It goes without saying that it’s always important to test any changes made in your mapping. Test every scenario to ensure the correct outcome before you start creating Overlay MAGs - validate the Base with multiple different payloads and ensure all common mappings behave correctly.

** Note: if you do wish to add additional common mappings to your Base mapping after you’ve created several Overlay mappings this is possible, but your Overlay mappings will be updated upon versioning! Make sure that if an addition or change is not desired in other existing Overlay mappings, to go in and exclude those additional mappings or changes. Partner-Specific Details Are in the Overlay MAGs

You can add your partner-specific details in your Overlay MAGs. Here, you see I include my global parameters for the partner identifiers in my envelope. In the Overlay MAG, you can always exclude (remove) any unused mappings from your Base MAG and include any partner-specific mappings like free-text, maybe an additional header party, or reference. You have an overview of all included, excluded, and used mappings in your Overlay MAG, where you can also re-add any excluded mappings, if necessary.

Version-Control Your Base MAG Carefully

Changes to the Base MAG automatically propagate to Overlay MAGs, so be really careful and start off with a well-planned, well-tested Base MAG before creating Overlay MAGs. Once again, if you do wish to add additional common mappings to your Base MAG after you’ve created several Overlay MAGs this is possible, but make sure to go in and exclude those additional mappings or changes that you don’t want in your Overlay MAGs. Otherwise, you might just make this addition to the necessary Overlay MAGs.

  Summary

The Base–Overlay model lets you maintain one standard Base mapping for a shared message format while adapting to partner‑specific differences through Overlays. A Base MAG holds all common logic, and each Overlay MAG inherits that logic and adjusts it as needed—removing, modifying, or adding mappings for a specific partner.

Start with clear naming conventions for MIGs and MAGs, so related artifacts are easy to find later.

Always qualify your MIGs: qualification ensures structural and semantic correctness and prevents mapping errors, making your Base–Overlay set-up more stable.

Keep your MIG structures consistent—extend them when needed, but avoid deleting or restructuring elements already used in mappings.

Treat the Base MAG as your “golden standard”: no partner‑specific rules or identifiers belong there. Test the Base thoroughly with multiple payloads before creating Overlays to ensure all shared logic behaves correctly.

Use Overlay MAGs for partner‑specific details like envelope identifiers, free‑text segments, or additional parties. You can exclude inherited mappings that don’t apply and add new ones as needed.

Finally, version your Base MAG carefully. Any change propagates to all Overlays, so plan updates deliberately and review each Overlay to accept or exclude new logic where appropriate.

For more information about the creation of Base-Overlay MAGs, please check out my blog: The Art of Mapping: Navigating SAP’s Base-Overlay Framework.

Want to know more? Feel free to contact us.