Skip to main content

We are in the process of setting up and implementing IFS Cloud and I have a concern around purchase requisitions to purchase order behavior. 

I am running MS One Part and MRP to generate purchase requisitions. The purchase requisitions are being created as I expect. However, I have concerns about the behavior that is taking place when converting requisitions to orders. As demonstrated in the upper section of screen shots below, when a 7/23 requisition was created through MRP, and I converted it to a PO, and re-ran MRP, the 7/23 requisition was closed as expected since the need was replaced by an order for that date (7/23).

In the lower section of the screenshot, I converted a purchase requisition in the future (9/1) to a purchase order to send to my supplier as they require a lead time on orders in the future which is typical for many of our purchase parts. I expected (and need) that the 9/1 requisition would move to closed and it did do that. However, it closed the 9/1 requisition, eliminated the 7/30 requisition and reproduced the 9/1 requisition. Is this typical behavior? Am I missing a setting?

I want the requisition to maintain the original need date when converting to a PO and eliminating the original requisition date and not pulling it forward.

 

Thoughts??

 

The system is working correctly.

After MRP run #1, you converted requisition 3422 Line 1 Release 3 with a Wanted Receipt Date of 9/1 to a purchase order (call it PO 1234). This Req/Line/Release moved to Closed status. There were still Planned lines on this requisition for other dates: 3422-1-1 for 7/30, 3422-1-2 for 8/1, and 3422-1-4 for 10/1.

After MRP run #2, the calculation now sees PO 1234 as open supply to cover the requirement of 7/30, and you should have an MRP Message of Late Order for this part. But you still have the demand due 9/1 which is now to be supplied by a new requisition 3423-1-2, along with the other lines you did not act on after MRP run #1.

Keep in mind that when you converted requisition 3422 for the 9/1 date, you did not create a supply specific to that demand, you just created an open supply that MRP used in its next calculation.

Below, from the Phases of MRP, is why you no longer see a requisition for 7/30.

Phase 5: Reschedule Existing Receipts

In the process of allocating existing anticipated receipts to demands, MRP always suggests moving the dates of existing orders before recommending any new orders to cover the requirements.  Action messages are generated to indicate the planned rescheduling events, by moving the order date in if necessary to meet an earlier demand, or suggesting the order date move out if earlier than required. In the event the existing receipts exceed the demands for the part, MRP suggests additional actions to cancel those unnecessary orders and/or order quantities.

Thank you for the response. It is helpful. The next thought - based on your answer - is how/can I “create a supply specific to that demand” so the 7/30 requisition date remains open and the 9/1 requisition date closes and goes away? Appreciate the quick response and support.

 

​@PhillipMiller1212 automatic hard pegging of supply to demand is possible only through the use of DOP (Dynamic Order Processing).

Terms & ConditionsCookie settingsAccessibility statement