I am trying to create a WF or a series of WFs and ...
# suiteflows
Sam
12/03/2023, 7:12 PMI am trying to create a WF or a series of WFs and a custom record for lot tracking. The process will, if possible, mimic a lot tracking record, but the client does not want the rigidity of NS lot tracking. Does any one have experience with this in general? Scripts are an option but would like to exhaust WFs and customization options before scripting the solution.
More specifically, how would one Create a custom Lot record when a lot number is added to a Item Line on a PO. Then populate the record with the item name and some basic PO and vendor details.
đź‘€ 1
m
MGBC
12/04/2023, 4:40 PMYes you can use the Create Record action in the Items sublist of the PO (or SO)
MGBC
12/04/2023, 4:41 PMMake a custom record called "lot number" Then use the Create record action in the item Sublist Aciton Group to create an instance of this lot number record when a PO is created/edited/saved (whatever your criteria is)
MGBC
12/04/2023, 4:41 PMMGBC
12/04/2023, 4:42 PMIn this example we are making a "task" record for each sublist line, but you could easily update this example to make a custom "lot number" record instead of the task
s
Sam
12/05/2023, 6:40 PMWow this is great @MGBC. Thanks. I will let you know how it goes!
m
MGBC
12/05/2023, 6:56 PMđź‘Ť
a
Andrew Altringer
12/09/2023, 6:24 PM@Sam - What type of industry is the client in? Just wondering if they have a use case for controlled inventory or how controlled it needs to be.
Andrew Altringer
12/09/2023, 6:39 PM@Sam - I have always used a U/E script for this use case. Then used a custom field that sits on the PO that temporarily stores the Lot Number when the PO is created. Then design the script to generate the Lot Number to whatever sequential design the client wants and source it back to the native Lot Number field.
This way you don’t need a custom record to reinvent the wheel for Lot Numbering. You are also able to bypass NetSuite’s rigid Lot Numbering scheme and get control over it by assigning your own numbering scheme at the start of the Lot Number’s useful life. I get this request quite often from clients and they are basically asking for Lot Number tracking without using the Lot Number tracking setup. NetSuite’s design might be rigid, but it works extremely well once you get control over the Lot Number creation and assigning at the start of the process.
l
Luis
12/10/2023, 7:54 AM@Andrew Altringer can it handle multiple lot numbers per line?
a
Andrew Altringer
12/10/2023, 9:13 PM@Luis - I am assuming because you want to assign a new Lot Number for every line (new part) on the PO correct? The answer is yes of course. Normally what I have seen work best is you develop your Lot Numbering system to be the current (today's) date and then code the script to assign the Date and then a sequential number that resets every 24 hours.
I included 2 different examples below. Ex. 1 has the Lot Number with the current date and a sequential number. Ex. has the Lot Number with the current date, the first 3 letters from the Vendor, and the sequential number. I have done numbering systems for this with the Julian Date as well. You would want to have this setup on your PO's and either your Work Order (if using WIP) or your Assembly Build to assign Lot Numbers to built products before they go out the door at the Assembly (Parent) level. This provides you your traceability back to your original components on your BOM. There are some pretty cool ways to enforce it as well if it is an FDA or strictly inventory controlled environment.
PO #1000
Line 1 | Item: ABC | Qty 50 | Lot Number: 121023-001
Line 2 | Item: DEF | Qty 100 | Lot Number: 121023-002
Line 3 | Item: GHI | Qty 200 | Lot Number: 121023-003
PO #1000 | Vendor: Test Company
Line 1 | Item: ABC | Qty 50 | Lot Number: 121023-TES-001
Line 2 | Item: DEF | Qty 100 | Lot Number: 121023-TES-002
Line 3 | Item: GHI | Qty 200 | Lot Number: 121023-TES-003
2 Views