NetSuite MRP - Work Orders Scheduling Way Too Earl...
# accounting
j
NetSuite MRP - Work Orders Scheduling Way Too Early Getting planned work orders scheduled months before demand. Example: • Planned WO: 10/9/2025 (today) • Pegging shows demand: 4/10/2026 (6 months away) Happening across all items. Transfer orders calculate correctly with proper dates, only work orders are wrong. Setup: Multi-location supply chain, 1-day transfer lead times, 0 lead time on assemblies. Anyone seen this? What causes MRP to ignore demand dates and schedule WOs immediately?'
b
There are a lot of datapoints that could be doing this, can you screenshot the location level supply planning fields ?
j
yes so for some context to why we are setting some of the values we're setting: our production structure is outsourced, the way we capture cost of production is a PO for the WIP item (inventory item for cost of production that gets used on FG build). I was having some issues because i need MRP to make my WO available in full on end date as opposed to how it was calculating: making inventory available starting on the WO start date. To mitigate this i have no lead time on my assembly items, and i instead set it on the WIP items. This way MRP reads my FG inventory as available on the date it is completed, and i know to place the PO for the WIP item using the lead time. this PO <> WO timing is correct, the Storage > Fulfillment location transfer timing is correct. The only thing that is showing up wrong is the end date of the FG WO. with that context in mind i am setting location sublist fields via script using some settings i have on a configuration record for item collections. • WIP is getting lead time in manufacturing location • FG is getting MOQ in manufacturing location and safety stock in Fulfillment/Storage locations • both types are getting: ◦ past due forecast days = 1 ◦ late days period = 1 ◦ backwards/forwards consumption days = 14 ◦ demand time fence,planning time fence = null
b
What does your purchase pegging for the WIP item look like?
And you aren't using the Outsourced MFG feature at all right? You are rolling the cost of the component and the cost for a third party to manufacture into the wip item cost?
j
correct we are not using outsourced manufacturing. when i inherited this account we were set up this way and i tried to move us to it, but there were some internal reasons to keep the current structure. on correction we are only using WIP as the cost to manufacture, the actual raw ingredients are used on the revision as expected. pegging on the WIP is looking weird actually. i don't remember it looking like this earlier. now i see that my actual WIP PO is pegged to the planned WO and the planned WIP PO is pegged to my actual WO. are things getting thrown off because the actual PO/WO are needed for transfers that are due before they're set to be completed?
okay so my issue is that for example: i have a work order due 10/18, but i have demand that is not covered 10/10 - 10/17, to get this demand covered MRP is creating a planned work order due 10/10 to get that week covered. but really that's not what i want it to do. i want MRP to say, okay this week the demand will be late, but it's within x days of an actual WO so that's fine we'll let it be late and use the WO i tried messing with rescheduling and demand fence settings but nothing can get this working the way i want it to. but if i change the WO from 10/18 to 10/10 everything calculates "correctly" meaning the planned order is created for april as expected
b
What about planning time fence? I think that will suppress signals if you are within that fence.
I think your assessment is correct about the demand from 10/10 giving you a signal for a new work order. This creates a pegging mismatch to the PO AND a major timing problem because of the existing work order. It seems that this is a casualty of 2 things. 1. the work order has no lead time and MRP doesn't care about inventory levels when signaling for planned work orders. It assumes that the inventory is in place because you are following the purchase signals. 2. because of this you have some date mis-matches. first, the real po is late for the real work order supply (demand date could be moved and should be if the po expected receipt date is actually 10/18) second, if you want to leave your dates on the demand the same then you have correctly moved the work order end date to cover off the late demand.
or late supply rather
it really does feel like this is a prime case for outsourced manufacturing.
j
but outsources manufacturing won't solve the issue of the uncovered demand between 10/10 - 10/17 right? it will only fix the pegging issue right? which i would like to fix, but i'm more concerned about the timing of the planned order. my real WO and PO both have a 10/18 end date so those are aligned, the issue is that before 10/18 it wants me to squeeze in a new WO because i don't have any supply on the assembly to get the planned transfers before 10/18. so the mismatch of the planned PO to the real WO is just due to the timing of the planned WO. how do we get MRP to ignore that the next week we will not be able to supply the demand and just accept the lateness and use the real WO instead?
okay so demand fence to 0, planning fence to 14 got us there. is this going to cause other issues? like are we going to be ignoring things we shouldn't ?
b
I mean, you won't see any planned work orders less than 2 weeks out. It should try to aggregate at the 15th day out any supply signals that fell within that window.
but really it is the demand on this week that is triggering the signal to build. I think best practice is that if your components won't arrive in time to build you should adjust the SO or Item Demand plan dates to align.