cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Duplicate Purchase Requisitions

Akhi222
Discoverer
0 Kudos
724

There is a issue. The material has MRP type VB, Reorder point 1, Lot-sizing procedure HB and Maximum stock level 1.

I have run MRP run today and a purchase requisition created with qty 1 with fixed id.

The purchase requisition has been approved and converted into purchase order with qty 1.

The next day after MRP run, there is one more purchase requisition created with qty 1 and md04 available stock showing 2 with both items, which is exceeding maximum stock level.\

Where is the issue?

Accepted Solutions (1)

Accepted Solutions (1)

Caetano
Product and Topic Expert
Product and Topic Expert

Hello 

Issues where MRP generates a new purchase requisition are very often related to the rescheduling check. If your purchase order is outside the rescheduling horizon or not included in the rescheduling check, MRP might have to create a new purchase requisition to cover the reorder point. This WIKI talks about the rescheduling check:

https://help.sap.com/docs/SUPPORT_CONTENT/mrp/3138697863.html

Another possibility is that your purchase order is not relevant to MRP. If the available quantity column is blank for your PO in transaction MD04, it means that it is not relevant to MRP, and that's why a new requisition can be created.

Regards,

Caetano 

Akhi222
Discoverer
0 Kudos

Hi @Caetano , Thanks for the reply.
Also longer lead times maintained in the purchase info record. Here, we do have 168 days of Planned Delivery time in info record which is greater than the Planned Delivery time maintained in the MRP2 view of material master i.e., 1.

Also we are maintaining rescheduling horizon as 100 days at plant level. Planning horizon also as 100 days but hope this planning horizon does not have any impact on MRP Live.
Is our understanding correct that the issue is due to the longer lead time and rescheduling horizon?

Caetano
Product and Topic Expert
Product and Topic Expert
Yes, the issue is related to the long lead time. Rescheduling check will not consider the lead time from the info record to calculate the replenishment lead time, so your PO is outside the rescheduling horizon, and that is why MRP does not consider it.

Answers (0)