Demand planning/MRP: Vendor A requires us to order...
# general
l
Demand planning/MRP: Vendor A requires us to order in multiples of 10 (10, 20, 30, etc.). Also, we aggregate POs that are needed for a period of x days (let's 5 days). Assuming the EXACT suggested quantities to order are as follows: Day 1: 26 Day 2: 37 Days 3 and 4: none Day 5: 52 We expect that NS will suggest ordering 130 (30+40+60) quantities on day 1. Orders are rounded up to the defined multiples and are aggregated on day 1 of the interval period. Order multiple and aggregation seem to be both possible BUT mutually exclusive. By using the Lot Sizing Method field in the Item record, if we choose Fixed Lot Size, we can achieve the reorder multiple. If we choose Periods of Supply, we can achieve the aggregation. But how can we achieve both if it is controlled by a single field? Any workaround solution? Isn't this scenario just normal?
r
Normal and unfortunate scenario. Could likely be handled through a customization on the PO side though, not sure if I'd want to mess with customization within the planning engine.
k
I'd script this on the po
Add a custom field to the item
If PO doesn't multiply out, round to next multiple
Using a condition where floor(qty/multiple)-(qty/multiple) is not equal to zero.
l
We actually plan to do the same but at at the Item Supply Plan and Planned Order level. So the planners will already see the actual suggested PO quantities during the supply planning and not wait until the PO is created or saved. Any issue with that?
🙌 1
By the way, thanks for the input.
k
Can that page even be scripted?
l
I believe so. I can see them in the Records Browser. I was also able to run a workflow against the Planned Order. It works perfectly fine in recalculating the suggested quantities based on the order multiple from a custom field in the same record. However, I had to schedule it every 30 minutes because it is not triggered upon creation from the Refresh Planning Repository page. I tried all the available triggers and all the contexts are selected as well. Is it normal behavior that when a transaction is created from a "bulk processing page" the triggers upon creation won't work? Thanks.