Help me understand how to hold subassemblies in "inventory" for a parent part that is built out later

I am trying to utilize subassemblies, and it works really well to start, but then I get stuck on how to process a sub assembly after it is complete.

This might have something to do with everything being a ghost part to be fair since you can’t “inventory” it. , but I want to know if there is another way.

Here is the example of what I am trying to do.

I estimate a project in quote entry, and create a ghost part number called “SJ-boulder bomb truck adds”

This part is built out with an operation to allow our shop technicians time to install some materials into a vehicle and a graphics application operation to apply graphics.

Because we can produce those graphics ahead of time, and because I really don’t want to add it as a stock-able part, I add a sub-assembly with a new ghost part number called “GP-boulder bomb truck ghost”. I add a design and production operation to that sub assembly as well as the material used to create it. The intent is that they can produce that sub assembly before the vehicle actually comes in for the install and application.

That works great. Estimates well, and pushes to the job appropriately.

Here is where I am stuck. After the graphics shop completes the sub assembly, I don’t know how to “hold it” in the system in a specific bin. Do i receive it somehow? or is it a move? I have not found the right way to do it.

In the future, when the parent part can be complete (which might be weeks later), I need to be able to find where we put that subassembly and essentially “issue” it to the parent, but technically it is WIP so i assume it will be a move? I just don’t know how to hold and organize that sub assembly.

Anyone doing something similar and have a good workflow for it?



We used to set up our fastener kit subassemblies as non-stock / plan-as-assembly, with their primary bin a generic “prod-in” bin.

MRP creates linked child jobs and when the child job is executed, the subassembly goes into inventory in “prod-in” until the parent job’s picking op is executed.

1 Like

So we have finish good parts where the finishes can be different every time, so I created what we call “Template” parts that are Non-Stock, non-Quantity Bearing. It has a method behind it for all the operations and materials with “Generic” finish materials. All the Sub-assembly parts are set as PULL-AS-ASSEMBLY. This allows the sales person to swap out the Generic material with an actual spec’d material to generate a true cost on the Quote. It also allows all the sub-assemblies to be created under one job, and the sub-assemblies can be worked on and completed at different times. All activity is WIP, none of the sub-assemblies go into inventory. We also utilize the Material Request Queue. I believe this is part of the Advanced Material Management module. If the method is set up correctly with related operations for the sub-assemblies, the Material Request Que will default to the Input Warehouse and Bin for the related operation’s Resource Group, or Resource, however it is set up. If the sub-assembly is not immediately being stored at that Input WH-Bin, the user can select an alternative location before saving the transaction in the Queue. When you are ready to do the operation on the parent job, you can see where the WIP location is for that sub-assembly. Depending if you are using back-flushing or manually issuing materials to jobs, you may have to perform a MOVE-WIP to get the Sub-Assembly material into the back-flush WH-BIN of the next operation in order for it to “consume” the sub-assembly, and apply costs to the job.