Did you ever get an answer to this? I'm seeing the same thing recently, and when I look at my Work Order Form the field is now 'Disabled' by NetSuite. When I click on the field Help I get the field definition of 'committed', including the Field ID. Very frustrating… The Committed field displays the total number of assemblies that are committed to sales on associated assembly builds.

Field ID: committed

Sorry. This one never got any traction. I feel like it would a nice option to be able to build into the assembly item record itself, but I've let this one go for the moment.

Try looking at SuiteAnswers Id: 32913

Interesting article, but the logic seems incorrect. The top paragraph contains the following statement "Note that the BuildableQuantity = Quantity – Built". This is not correct. Buildable Qty should (and does in the native field) represent the # of units that are possible to be built based on the qty available of the components. For example, I have an assembly, with 4 components, all with a qty of 1 used for the build. If I enter a work order for 100, and 3 of my components have available inventory of > 100, but the last has only 60 units available, my buildable qty would = 60. This is actually how the native field works, I'm not sure why NS support would state this incorrectly in the help document.

Thanks,

Mike

After working with NS support and trying several different work arounds, we were unable to get something like this done. Amazing that it can't be done. We even tried building new custom fields to try and source them to be able to create a saved search that shows work orders where all components of an assembly were available.

Does anyone have a solution or work around that would enable me to build….

Saved search: Work Orders

One of two options would work…

-All components included in the work order are available/quantity on hand of all components > quantity needed.

OR

-one specific component of the work order has a quantity on hand or available that is greater than the quantity needed?

Driving a production team from a list of work orders is USELESS if you cannot parse out the ones with all components available.

any updates on this? trying to do the same?

Even with building come custom fields we were unable to make it work…. which is totally absurd as it seems like a very desirable functionality. We are in the process of implementing the Netsuite package WMS (Warehouse Management System). Supposedly this add on will give us the functionality.

I have a search on the Assembly item that calculates the Buildable Quantity. Since it is not stored it is not available normally for another transaction field to source from BUT you could have a scheduled workflow update a Stored field on the Assembly record every 30 minutes and then source that to a custom transaction field on the Work Order. Not quite real time as the quantity is stored every 30 minutes but might serve your purposes.

Hey John,

Could you share how you've structured this search? Are you just looking at the min or max back ordered qty and dividing by the qty or something like that?

Thanks,

Mike

Mike,

Criteria

Member Item:Type is any of Assembly/Bill of Material, Inventory Item

Member Item:Inventory Location is Warehouse

Results

Formula (Numeric) Summary Type=Minimum Formula=FLOOR(NVL({memberitem.locationquantityavai lable}, 0)/{memberquantity})

Available Filters

Internal ID

Thanks John, I was thinking about that, but couldn't using the available # be an issue we're doing a search of WOs? If the WO already exists, depending on your commitment settings, the components are potentially already committed. In theory a work order could be completely buildable, with an available qty of 0. Am I looking at this wrong, or is it just a matter of commitment preferences?

Actually, you are correct. We default our W/O's to released and commit inventory when created (Available Quantity). Technically I teach my customers that a Sales Order not yet approved, and Work Order not released are just pieces of paper and another order can come along and commit the inventory. We also have the same logic on the Item Assembly.