Hi all. Is anyone running ***Supply Allocation + l...
# suitescript
p
Hi all. Is anyone running ***Supply Allocation + lot-numbered items + NetSuite WMS*** cleanly? We have a distributor with light manufacturing and order-specific customised stock, and we keep hitting the same things: • A wave's FEFO pick picks a lot that's already fully committed elsewhere, and the IF fails with
Inventory numbers are not available [On Hand:N, Committed:N+1]
• The Order Allocation Schedule pulls stock out from under released waves (we turned it off) • WO components and SOs fight over the same lots • There's no way to reserve stock for one specific order without Inventory Status We sandbox-tested one thing: an Allocate Orders pass took 9 of 10 units off an unfirmed committed line, but a firmed line wasn't even offered as a candidate, even with "Commitment Confirmed Stops Allocation on Order Line" unchecked on the strategy. So firm is the brake, and the question becomes when and how you firm. How are you handling it: firm on commit or on wave release, a SuiteApp (FEFO Lot Assignments, RF-SMART), your own committer, or a process rule? The full write-up is here: reddit.com/r/Netsuite/comments/1wrsa80
a
Ohh man I think you may be in for a very nice ride. Back in 2016 (right before Oracle purchased NetSuite), they had: Average, FIFO (First In First Out), LIFO (Last In First Out), Standard Costing (this was relatively new). I can't explain how hard it was for companies to understand and embrace Standard Costing (most companies still don’t get it). With all that being said; Inventory, Work Orders (Manufacturing), Allocation (Forecasting and Demand Planning) are three (or fourth) different specialties that NetSuite and some WMS (Warehouse Management Systems) have tried to put together for decades. It is hard… Your best bet would be with RF-Smart to be honest. (Is not cheap). Other than that it will be custom… or or or… NetSuite support case (10 years from now to be resolved)…