Skip to main content
Question

Invntory reception during MRP's snapshot creation

  • July 23, 2026
  • 1 reply
  • 32 views
yohbrousse85
Do Gooder (Customer)
Forum|alt.badge.img+1

We have issue regarding the MRP Snapshot.

Actually, we have for a part, a Shop Order to produce the part SO#1 for Part#9.

During the night, the MRP is running and start by the Snapshot.

We have production team that is working during the night.

First snapshot : Inventory. No Part#9 in stock. (duration 5 minutes)

During this Snapshot, we close the SO#1 and receipt Part#9 in inventory.

Second snapshot : Shop orders - Customer Orders….(duration 5 minutes)

 SO#1 has been closed so no Shop Order.

 

The result is : 

MRP didnt see the Inventory, and didnt see the Shop Order.

So, he will propose a Shop Order Req to produce Part#9.

And we have Shop Order process type that will transform the SO Req into SO just after MRP.

 

Is there a way to : 

  • Pospone rception during the Mrp calculaton and record it after ?
  • Forbid reception  during the MRP Calculation ?

 

Actualy , our workaround solution is : 

  • Quick Report to identify the Parts that have been received during the snapshot
  • Relaunch Part MRP on these parts 
    • Generaton of MRP Action proposals : Early Orders
    • Cancel SO
    • Delete SO Req 

1 reply

majose
Hero (Employee)
Forum|alt.badge.img+15
  • majose
  • Hero (Employee)
  • August 10, 2026

Hi ​@yohbrousse85,

Yes you are right about this. Long time ago it was even worse.

  1. When we in the MRP Process snapshot inventory information these days we just get the parts and inventory part planning data and then we commit this to the MRP working tables
  1. Then we remove Requisitions from the previous MRP execution that has not been converted to Supply Orders. And commit the data
  1. Hereafter we load Inventory Onhand information and commit date for all parts on the site.
  1. Then we continue with taking the snapshot of open supply and demand orders. Within this process we start with capturing Shop Order Supply and Demand data, which is good, because that is typically the most dynamic order supply demand data during the nights. For example it would not be that clever if we start with loading exploded demand of master scheduled parent parts.

But still there is a gap in time between c and d, which could cause the problem you describe.

I don’t know if it is practical, but at the time of snapshot of open supply and demand orders, then it is good if the inventory transaction activity could be as low as possible.

Once MRP start its Main execution, which is the most time consuming part, the MRP data is “safe” and there no problem executing shop orders.

Best Regards,

Mats

Terms & ConditionsAccessibility statement