Skip to Content

Exception message 26 with no excess


We get an exception message 26 for a PS sales order, when the requirement is 1 and the received stock is 1, there is no excess stock and no changes of quantity in the sales order:

Still, we can see that in MRP screen we get this exception message:

Maybe someone has an idea why?

Thanks a lot,


lo5w5.png (45.4 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Jun 14, 2017 at 05:32 AM

    it would be interesting to see the stock of that 72000--50000 material on requested delivery date 04.02.2016

    are you able to run MB5B and check that?

    and what was the MRP type for that material?

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      There was no stock on the requested date for this item.

      MRP type of this item was ans is PD.

      Item category group= BANC

      The MRP controller would like to see it in MRP screens in order to know if he has something which was cancelled and now he can, maybe, use it for another sale, although BANC should come with MRP type ND.

      When I look at the MRP screen I can see:

      1. Line for Cstock

      2. Line for purchase order/shipping notification, but without a line of the sales order, as for items which has item category group= NORM.

      When the GR of the PO occurs, the is no line below the Cstock and exception message 26 appears.

      How can we avoid this "26"?



      qjtfn.png (50.1 kB)
  • Jun 14, 2017 at 04:25 PM


    Can you post a screenshot of the MRP transaction where you are seeing this exception? Maybe the problem is that the sales order requirement is not relevant to MRP.



    Add comment
    10|10000 characters needed characters exceeded

    • Hello Yael

      This exception message is generated by MRP when calculating the difference between stock (plus replenishment) and requirements in the individual stock segment. If the sales order is not relevant to MRP, then there is an excess stock from the MRP perspective.

      The only option is to deactivate this exception message in customizing.