MD04 Exception message 15 for shipping notifications

[former_member581721]

Hi,

I need help to understand how Exception Message 15 affect Shipping Notifications in MD04.

We are talking about Purchase Schedule Agreement Shpg Notifications..

Since Shipping Notifications has supposed to be confirmed dates, I do not get why MRP rises an exception for them.

In detail the issue is the fact that MRP suggest exception 15 (pospone operation) on the Shipping Notification row,

while proposes to anticipate (exception 10) normal schedule line.

I read some threat explaining the Exception 15 is carried on by the OPPR and OPPQ settings over the re-scheduling tolerances. By the way.. in OPPQ shipping notification are excluded by re-scheduling and even if I set empty the tolerance value for displacement, no changes after mrp run.

In OPPR I checked the rescheduling horizon for the material mrp group, but it is empty too..

Anyone can solve my doubts? Is this a standard behaviour or it can be driven by customising?

Thanks in advance,

Francesco

[DominikTylczyn]

Hello fra88fg1

Refer to the following notes for details of MRP rescheduling and exception 10:

25388 - MD01, MD02, MD03: Rescheduling proposals: Documentation

2609209 - Rescheduling exception message 10 and 30 in t-code: MD04

The way I understand is that first MRP tries to rescheduled firmed elements i.e. those marked with * (star). In your case it's the schedule line of 750 pc at 02.02.2021. The system is proposing to expedite it so it covers earlier requirements. Then the system follows with rescheduling of non-firmed elements, which would explain why the schedule line of 1050 pc at 25.11.2020 is to be postponed.

What's odd here is the rescheduling proposal date of the schedule line of 750 pc to 19.11.2020. It seams to early from your screen shots; you have enough stock on that day. However I can't be sure without looking at your master data e.g. good receipt time, safety time etc.

Best regards

Dominik Tylczynski

[former_member581721]

Thanks for your sharing

unfortunately the shipping note is fixed too ..

so MRP should check it.

I verify the mrp type, safety stock, mrp group, fixed horizon, lot size procedure and configuration for control confirmation.. nothing seems to be involved in this behavior..

Plus, there is also a case in which MRP suggest to postpone the shipping nt even if there is need for stock:

I looked for Z*MD* Badi and implementation or for CMOD user exit, but there is nothing linked to MRP.

Honestly, if this is a standard behavior I don't get the logic..

[DominikTylczyn]

Hello fra88fg1

First, let's look at the documentation of MRP exception 15:

15: Reschedule out (U2)

Message no. MD420

Diagnosis

In the rescheduling check, the system calculated a date to which the receipt is to be moved out (rescheduled out) to avoid high warehouse stock at the wrong time.

The date displayed is the date by which the receipt is to be available for MRP. This includes the goods receipt processing time. If this is not zero, this is displayed as well as the required goods receipt date.

System Response

This exception is displayed in the MRP list, and in the stock/requirements list.

Procedure

Check whether the receipt can be postponed.

Now look at the stock situation depicted on your first screen shot. On 24.11.2020 you are going to have 1.093 PC of stock. Thus you don't really need to delivery additional 1.050 PC on 25.11.2020. That's exactly what exception 15 tells you, to postpone that till 09.12.2020, when the delivery is actually needed. It really doesn't matter here the shipping notification features confirmed dates - you're simply getting too much stock in.

Best regards

Dominik Tylczynski

[former_member581721]

Yes, but why MRP suggest to move up the shedule line below from Febrauary 2nd 2021 to November 19th 2020 considering the confirmed date by vendor would provide more quantity in few days and considering on 19th I already have enough quantity to cover the requirement?