Phantom BOMs and/or Kitting

spena
Member Posts: 45
Hi,
We have a manufacturing environment where we have several make to order items. The make to order items have production boms with several standard components. For example, a bike is the make to order item and has components of tires, a frame, and a seat.
However, there are also "optional" components that can be selected and configured with the make to order items. These optional items are phantom boms in the sense that they have components and labor, but they are not tangible items (not subassemblies). For example, there is an option item made up of screws, nuts, and bolts, plus a routing for some labor. The screws, nuts, and bolts are needed to attach a basket to a bike.
We can't have the options as phantom boms on the production boms, because we won't know what the option is until the item is configured by the customer. This would entail creating several new part number just to represent the amount of options that can be included on the bike.
We could conceivably create a production bom and routing for the options, since the option will be reserved to the sales order line. However, this will increase the amount of work orders by at least five times, so this isn't a viable solution either.
Also, we need to show the option on a sales order as a separate line item.
Does anyone have any suggestions on how this can be handled? I see we can create Assembly BOMs on a sales order and explode the components (assuming we could modify the sales order to only print the assembly while compressing the components). This could conceivably work, but we wouldn't be able to use work center labor, so this isn't a great option either.
Any ideas would be much appreciated!
Thanks,
Steve
We have a manufacturing environment where we have several make to order items. The make to order items have production boms with several standard components. For example, a bike is the make to order item and has components of tires, a frame, and a seat.
However, there are also "optional" components that can be selected and configured with the make to order items. These optional items are phantom boms in the sense that they have components and labor, but they are not tangible items (not subassemblies). For example, there is an option item made up of screws, nuts, and bolts, plus a routing for some labor. The screws, nuts, and bolts are needed to attach a basket to a bike.
We can't have the options as phantom boms on the production boms, because we won't know what the option is until the item is configured by the customer. This would entail creating several new part number just to represent the amount of options that can be included on the bike.
We could conceivably create a production bom and routing for the options, since the option will be reserved to the sales order line. However, this will increase the amount of work orders by at least five times, so this isn't a viable solution either.
Also, we need to show the option on a sales order as a separate line item.
Does anyone have any suggestions on how this can be handled? I see we can create Assembly BOMs on a sales order and explode the components (assuming we could modify the sales order to only print the assembly while compressing the components). This could conceivably work, but we wouldn't be able to use work center labor, so this isn't a great option either.
Any ideas would be much appreciated!
Thanks,
Steve
0
Best Answer
-
It sounds like you could benefit from a configuration add-on, something that generates the components and routing on the production order based on selections done at order entry.
That would be my recommendation if you don't want order entry to involve changing components and operations on production orders.Olof Simren - Microsoft Dynamics NAV Expert | Founder of Naviona
My Dynamics NAV Blog: olofsimren.com
My Google Plus Profile
Naviona - My Dynamics NAV Partner5
Answers
-
It sounds like you could benefit from a configuration add-on, something that generates the components and routing on the production order based on selections done at order entry.
That would be my recommendation if you don't want order entry to involve changing components and operations on production orders.Olof Simren - Microsoft Dynamics NAV Expert | Founder of Naviona
My Dynamics NAV Blog: olofsimren.com
My Google Plus Profile
Naviona - My Dynamics NAV Partner5 -
I would agree with Olof there, I used variplus add-on by orderbase in these cases earlier.
http://www.orderbase.de/oc/modul/nav/variplus_dynamics_nav/?lang=en0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions