Skip to main content

Notifications

Business Central manufacturing sub assembly scenarios ︎

JAngle Profile Picture JAngle 33,157

A common scenario with manufacturing implementations to explain to a customer. There a a few ways to attack the overall topic, however I want to narrow in on how sub assemblies can show on production orders. This completely boils down to how an item and the subsequent sub assembly items are configured. Take this post as a showcasing of a way possibilities as opposed to how to use these in best practice. Let’s start from what the views on the production orders are and then work backwards to how you set things up for that. I’ve taken the good old Cronus Bicycle and generated a BMX item and a Mini BMX item. These items will have differing setups to achieve the desired views.

In principal there are two primary ways to display sub assemblies in production orders:

Here we can see all the required sub assemblies on indented lines within the same production order. Note that the 4th and 5th line are indented to the 2nd and 3rd lines because they are sub assemblies to those lines. This is a neat and tidy way to review the data in the web client
Here is the other format, where you have an order per “Source No.” – which in this case is items. How do you know they are sub assemblies?

Assuming you created the production order (supply) from the planning worksheet then you would have an inclination that they are sub assemblies from the components of the finished good item – i.e. the Mini BMX. The below shows that there are reservations in place and they are for the other production orders:

Aesthetics don’t carry much weight in a situation like this. Instead let’s review why BC displays the data like this.

The BMX item – which had all the lines on one production BOM – has the above structure of items to make it up. They all have a specific set of setups in place to make them appear on one production order together.

– Replenishment System: Prod. Order
– Manufacturing Policy: Make-to-Order
– Reordering Policy: Order
Each item in the sequence shown above, which needs to be manufactured, have these settings against either the item card or the SKU card. How does it look on the planning worksheet you ask?
You get all the detail on the planning worksheet in terms of what will be on a production order. It will just use the same “Ref. Order No.” for each of the requisition lines. Once the action is carried out they are bundled together on the same production order.

The Mini BMX item I used in the other scenario therefore uses a mix of setups across each of the different items which need to be manufactured.

Only difference on this sub assembly item is the “Manufacturing Policy”.

It could well be that you have a variation on the theme explained here, by having a few as individual production orders and other items on the same production order. All to be determined by the customer scenario you are trying to solve. For long drawn out production processes I can see good merit in having 1 production order housing most of the data – this is much more likely to be a scenario where “Make-to-Stock” is less likely. I’d say that is the core driver on why the single production order isn’t that common for projects I’ve worked on at least.

How does it work with some of the other permutations like project orders or item families? The data flows through to a production order in the exact same way as shown earlier:


This was originally posted here.

Comments

*This post is locked for comments