Skip to Content
Author's profile photo Former Member

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)


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)

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      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!

      Author's profile photo Former Member
      Former Member

      Interesting. You are right Dogboy but how come I don't see table MDTC in the structure of DBM?

      Author's profile photo Former Member
      Former Member


      how come I don't see table MDTC in the structure of DBM?

      Don't know.  Don't much care either, so long as it works.....

      Author's profile photo Mangalraj Senthamaraikannan
      Mangalraj Senthamaraikannan

      Dear Arun,

      Excellent one,and thanks for this wonderful sharing.



      Author's profile photo Dibyendu Patra
      Dibyendu Patra

      Very good work arun kumar...

      Nice explain about MRP DBM..

      Author's profile photo Graham Harrison
      Graham Harrison

      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.



      Author's profile photo Anthony Dellarte
      Anthony Dellarte

      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!