SAP reference for materials¶
This page complements materials. The mapping authority is the
current public Community/Enterprise contract, not the legacy planning-*
codebase. Confirm final availability in the deployed edition and OpenAPI.
Nearby mapping¶
| OpsFactor | Nearby SAP field | Common SAP tables | Note |
|---|---|---|---|
id |
MATNR |
MARA |
Preserve leading zeroes and do not add plant to the global material ID |
description |
MAKTX |
MAKT |
Choose and document the language |
active |
deletion/status indicators | MARA, MARC |
Derive through a rule; there is no single equivalent Boolean |
lifecycleStage, dates |
status and discontinuation data | MARA, MARC |
Require a translation policy into the OpsFactor lifecycle |
defaultUomId |
MEINS |
MARA |
Base unit |
salesUomId |
sales unit | MVKE, MARM |
May vary by sales organization |
transferUomId |
chosen logistics unit | MARM |
Define which alternative unit represents transfer |
Plant-specific SAP data in MARC normally belongs to the material/location
combination or planning configuration. Do not create duplicate OpsFactor
materials merely because one MATNR exists in multiple plants.
ID and transactions¶
Use canonical MATNR, for example 000000000000123456, when it is unique in
the integrated scope. If multiple SAP systems share the integration, add a
governed source prefix such as S4BR-000000000000123456.
MM01,MM02, andMM03: create, change, and display material;- Fiori apps and Product/Material Master APIs may replace direct table reads in SAP S/4HANA.