Exception message 30

[former_member647551]

Hello,

I have used the MRP type P1 in my material, so the procurement proposal was created after the end of the planning time fence. as result a got an exception message 30 (See the screen shot below)

mrp3.png

How is it possible to solve the issue ?

Thank you in advance

[DominikTylczyn]

You missed the screen shot.

[DominikTylczyn · Accepted solution]

Hello omaima

The system is working as expected. The material is planned with the MRP type P1, which is MRP with firming type 1:

Firming type 1 means that if there is already a procurement proposal within the planning time fence, the proposal gets fixed. If a new proposal needs to be created inside the planning time fence, it's move outside the fence. MRP with firming types are used to protect the procurement plans (mainly production plans) from unexpected changes.

Of course, as the procurement proposal is moved outside of the planning time fence, requirements within the fence can't be covered fully. Hence the MRP exception 30:

I suppose that the planned independent requirement (MPR element VSF) of 12.000 on 01.11.2021 has been created very recently. So it felt into the planning time fence and according to your planning rules that requirement can't be covered. Otherwise, if the November requirement had been created in advance, it would have been covered before it had fallen within the planning time fence.

Best regards

Dominik Tylczynski

[Caetano]

Hello

Exception message 30 is displayed as a result of the rescheduling check. Even though you are using a time fence, the requirement date is different than the replenishment proposal date, therefore, a rescheduling exception message is correctly triggered, in order to inform the planner about this difference in the dates.

Check this wiki where I explain what is the rescheduling check and how it works:

https://wiki.scn.sap.com/wiki/display/ERPMan/What+is+rescheduling+and+how+does+it+work

Regards,
Caetano

[RickK]

Hi,

When you use MRP type P1 with a planning time fence, exception message 30 informs you that the planned order is planned over the end of the planning time fence. Once these planned order proposals come within the PTF, they will be firmed automatically. This blog contains multiple examples of the behavior of MRP type P1.

Kind regards,