SAP MDG · COMMUNITY
How do I handle maintenance status best practice in SAP MDG-M?
In SAP MDG-M, maintenance status (PSTAT) controls which material views and mandatory fields become relevant during change requests and activation. Best practice is to align field status, material-type departments, and MM01/MM02 field properties; for releases up to SAP S/4HANA 2022 you can influence PSTAT with Z-field/ZZPSTAT/SMT logic, while from SAP S/4HANA 2023 onward the Unified Product API and CDS-node-based logic apply.
In SAP MDG-M, maintenance status (PSTAT) controls which material views and mandatory fields become relevant during change requests and activation. Best practice is to align field status, material-type departments, and MM01/MM02 field properties; for releases up to SAP S/4HANA 2022 you can influence PSTAT with Z-field/ZZPSTAT/SMT logic, while from SAP S/4HANA 2023 onward the Unified Product API and CDS-node-based logic apply.
Maintenance status in SAP MDG-M is not just a display value: it drives which material views become relevant and which fields turn mandatory during processing and activation. The key best practice is to align field-level status, entity/segment status, material-type departments, and MM01/MM02 field properties. Release matters: up to S/4HANA 2022, PSTAT can be influenced with Z-field, ZZPSTAT, or SMT approaches; from S/4HANA 2023 onward, the Unified Product API and CDS-node logic determine the status.
Process flow
- Identify the SAP S/4HANA release first.
- Understand whether the entity is standard or customer-extended.
- Check field maintenance statuses and the target material-master table/segment.
- Check material-type department assignment in OMS9.
- Check maintenance-status Customizing in OMSR.
- Ensure new field statuses fit the entity's intended status.
- Verify whether new status characters trigger additional mandatory fields.
- Align MM01 and MM02 field properties in OMSR to avoid activation mismatches.
OMS9Material Master -> Departments
Check which departments/statuses are assigned to the material type, because the source says this affects whether status characters are retained or lost during determination.
Material Master -> Field selection / maintenance-status customizing
Check and align field maintenance-status settings for MM01 and MM02, and configure fields as optional where appropriate to avoid unwanted mandatory-field checks.
Complex Transformation for MDG-M mapping
Up to SAP S/4HANA 2022, use complex transformation to influence PSTAT, for example to add E when Purchasing Group is maintained or to control valuation status logic.
T130FField status / maintenance-status assignment for fields
Assign a single maintenance status to a custom field such as ZPURCH in the source example.
Referenced tables
| Object | Purpose |
|---|---|
MARA | Material master general data table; used in the source example for custom field/status influence and for mapping material-related fields such as MPROF. |
MARC | Plant data table used in source examples for status determination, including EKGRP, DISMM, PSTAT, and the Z field mapping example ZZPSTAT. |
MARD | Storage location data table mentioned in the source as one of the segments whose minimum status is considered. |
MBEW | Valuation data table mentioned in the source as one of the segments whose minimum status is considered. |
T130F | Customizing table referenced in the source for assigning a single maintenance status to a field. |
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?','How does maintenance status affect material governance?','What exactly is a maintenance status?','Where does material maint
Possible questions
- How do I determine PSTAT in SAP MDG-M?
- What is the mapping between Material Master views and PSTAT characters?
- How do I avoid mandatory-field errors caused by maintenance status?
- How do I influence PSTAT before SAP S/4HANA 2023?
- What changes in maintenance status logic as of SAP S/4HANA 2023?