MRP exceptions could be identified from transaction MD06, but, often it has been noticed MD06 is ignored due to lack of clarity in terms of data interpretation. As a work around, logical database DBM could be utilized to identify materials based on MRP exception message keys (Say, A1 – Stock fallen below safety stock level, U3 – Cancel process, S1 – No BOM exists)
Step1: Tcode: SQVI (Logical Database: DBM)
Step2: Field Exception Message key, would be playing a key role in determining the output based on MRP exceptions
Step3: Selection criteria
Step4: Report output
-------------------------------------
Functionality of the report, could be leveraged in terms of setting up of nightly batch job and emailing output to key business users for taking appropriate
action (ABAP development effort is required for email functionality)
- SAP Managed Tags:
7 Comments
