Mapping and reference values

A steward/admin guide to the mapping surfaces that shape export output.

Cleansing, mapping, and data review

Use this when users ask why a column mapped, why a target value defaults to the source, or how to reuse mappings across projects.

Different upload paths expose different mapping surfaces.

Single-file uploads use the Smart Mapping Wizard; Agent bundles auto-apply mappings during ingestion.
Custom field decisions are a hard export gate until every group is Map, Extend, or Drop.
MC field coverage is a read-only preflight, not a separate export gate.

Code mappings are stage-scoped and depend on target reference data.

ECC-only bundles default target codes to the same value as source when no S/4HANA reference exists.
Refine from S/4HANA reference remaps identity defaults after a target snapshot is active.
Mapping content packs package confirmed mappings and approved reference values for reuse.

Each guide is a compact operating view. Use it to act, then continue into the related workflow page when you need the next step.

1ScanRead the section headings and confirm you are in the right guide for the role or moment.
2ActUse the bullets as the checklist for the extraction, review, approval, or handoff task.
3ContinueJump to a related guide when the work moves into upload, mapping, governance, or security.

Use these when the workflow moves to the next handoff point.