SAP MDG · DATA MODEL UI
How should maintenance status (PSTAT) be handled in SAP MDG-M?
Maintenance status (PSTAT) in MDG-M must be aligned with the governed fields, material-type departments, and release-specific logic. Up to SAP S/4HANA 2022, MDG uses minimum-status determination with OMSR/OMS9 and optional Z-field/SMT approaches; as of SAP S/4HANA 2023, the Unified Product API and CDS-node logic determine PSTAT, and customer Z-fields are no longer considered.
Maintenance status (PSTAT) in MDG-M must be aligned with the governed fields, material-type departments, and release-specific logic. Up to SAP S/4HANA 2022, MDG uses minimum-status determination with OMSR/OMS9 and optional Z-field/SMT approaches; as of SAP S/4HANA 2023, the Unified Product API and CDS-node logic determine PSTAT, and customer Z-fields are no longer considered.
Maintenance status in SAP MDG-M is not just a display attribute; it drives usability and mandatory-field behavior during change request processing and activation. The key best practice is to align field maintenance status, department/view mapping, and material-type Customizing, then apply the correct release logic: minimum-status handling up to SAP S/4HANA 2022, or Unified Product API-based determination from SAP S/4HANA 2023 onward.
Process flow
- Determine the SAP S/4HANA release first.
- Identify the governing entity, table, and affected fields.
- Map the field or node to its maintenance-status character.
- Check material-type departments/statuses in OMS9.
- Check field maintenance-status Customizing in OMSR.
- Align MM01 and MM02 field properties.
- For up to S/4HANA 2022, decide whether Z-field, ZZPSTAT, or SMT Complex Transformation is needed.
- For S/4HANA 2023+, use Unified Product API/CDS-node logic and supported validation approaches only.
OMS9General material-type department/status assignment
Defines which maintenance-status departments are allowed for the material type and influences the minimum status result.
Field maintenance-status Customizing
Controls field properties for MM01/MM02 and helps prevent editable fields from being ignored or becoming unexpectedly mandatory.
MDGIMGGeneral Settings → Data Modeling → Extend Mappings → Extend Mappings
Used up to SAP S/4HANA 2022 to extend SMT mappings such as MDG_BS_MAT_MAP_2PP for maintenance-status influence scenarios.
Referenced tables
| Object | Purpose |
|---|---|
MARA | Material master general data segment used in maintenance-status determination. |
MARC | Plant-level material master segment used in maintenance-status determination. |
MARD | Storage-location material master segment used in maintenance-status determination. |
MBEW | Valuation-related material master segment used in maintenance-status determination. |
T130F | Used in the source example for assigning a single maintenance status to a Z-field scenario. |
The remaining configuration, implementation details, and testing guidance continue from this answer more…
Related questions and keywords
Alternative questions
- What is maintenance status in SAP MDG Material?
- Why is PSTAT important in MDG-M?
- What problem does the maintenance status guide solve?,
Possible questions
- How do I determine maintenance status up to SAP S/4HANA 2022?
- What changed for PSTAT as of SAP S/4HANA 2023?
- How do departments and material views map to PSTAT?
- How do I avoid mandatory-field issues caused by maintenance status?
- How do I influence PSTAT with Z-fields or SMT up to S/4HANA 2022?
- Which validation options are recommended in S/4HANA 2023+?