Symptom
- While creating or changing material in MM01/MM02, an error indicates the Availability Check field is mandatory.
- The Availability Check field is configured as mandatory for a material type in OMSR.
- The Availability Check is stored in MARC but is not part of the MARCBASIC entity; it is in the MARCATP entity in the MDG data model.
- When plant data is maintained in MARCBASIC and MARCATP is not maintained, no Availability Check error is raised.
- If any value is maintained in MARCATP and the Availability Check is left empty, an error occurs.
- In class CL_MDG_BS_MAT_ACCESS, method CHECK_MANDATORY_FIELDS, validation loops only through entities extended in the MDG Change Request (staging). Dependent entity validations (such as MARCATP) fail if not explicitly extended.
- OMSR validates mandatory fields at the MARC table level, but dependent entity validations are not automatically considered when only MARCBASIC is extended.
Read more...
Environment
- SAP Master Data Governance
- SAP S/4 HANA
Product
SAP Master Data Governance 9.1 ; SAP Master Data Governance 9.2 ; SAP S/4HANA 1709 ; SAP S/4HANA 1809 ; SAP S/4HANA 1909 ; SAP S/4HANA 2020 ; SAP S/4HANA 2021 ; SAP S/4HANA 2022 ; SAP S/4HANA 2023
Keywords
availability check, mtvfp, omsr, marc, marcbasic, marcatp, mdg material, mandatory validation, change request, staging, cl_mdg_bs_mat_access, check_mandatory_fields, mm01, mm02, plant data , KBA , CA-MDG-APP-MM , MDG Material , Known Error
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview