Skip to Content

MRP Exception Messages via Logical Database DBM

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)

Picture1.1.JPG

Step1: Tcode: SQVI  (Logical Database: DBM)

Picture1.2.JPG

Step2: Field Exception Message key, would be playing a key role in determining the output based on MRP exceptions

Picture1.3.JPG

Step3: Selection criteria

Picture1.4.JPG

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)

7 Comments
You must be Logged on to comment or reply to a post.
  • Sweet!  I had always assumed that this LDB would not work if MDTB was not populated, but in reviewing the LDB code, it extracts data from MDTC as well, when MDTB is not being used.  Thanks for the heads-up!

  • I found this very useful thanks! I was able to create an SQVI report to list MRP supply elements with the rescheduling dates and Message Key…   would be great to include the MRP exception number (rescheduling message code 10,15,20 etc) together with the vendor linked to the MRP element (PO vendor for example)

    If anyone knows how I can achieve this with SQVI only, please advise.

     

     

  • I’m wondering the same.  It would be nice to have the MRP exception number (10, 15, 30, 52, etc) included.  If anybody knows if this is possible please advise!