0028543: BOM and Multi Level BOM functionality does not work properly in sales orders

Description

When creating and selling a BOM product:
- The main product and it's components appear on the sales order. This is very confusing, a product with 3 parts will show up as 4 order lines.
- Multi level BOM bug: When a product is assembled from parts using the simple BOM production (warehouse management - transactions - bill of materials production- function, AND the product is also combined in a sales kit

Example: Sales Kit with three items
Product 1 (With BOM, consisting of multiple small parts)
Product 2 (non-BOM)
product 3 (non BOM)

The system goes wack, creating two shipping documents for a single order, and creating a lot of order lines when exploding the BOM.

Steps To Reproduce

1.Create a "production BOM product" (which is intended to be assembled only, not sold as a kit)

2. Create a sales KIT product, with contents:
One or more production BOM products
One or more accessories

Proposed Solution

1) Allow multiple BOMS per product, which can be identified as Sales BOM or Production BOM (see Compiere, Adempiere)
2) Allow multi-level BOMS up to X levels
3a) Create an optional field "show detailed BOM lines on invoice" (boolean)

3b) Create an optional field "show detailed BOM lines on packing list" (boolean)
or create option to generate a packing list and a separate warehouse picking list for parts.

3c) Create an optional field "show detailed BOM lines on sales order"(boolean)

4) In the reports, use the boolean parameters shown under 3, to switch detailed line reporting on or off.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
(0077583) dmiguelez (developer) 2015-05-19 17:53	Hi, Based on the description of the issue, we consider that a re-design of the BOM functionality is required to consider all the suggestions made by the reporter. If this is the case, this issue will be categorized as a feature request and it will be taken into account in our roadmap. If there is a more specific issue though, we would appreciate more detailed steps to reproduce it. Based on this assumption, the severity has been lower from critical to major. Regards.

Issue History
Date Modified	Username	Field	Change
2015-01-08 14:30	pascalvp	New Issue
2015-01-08 14:30	pascalvp	Assigned To	=> dmiguelez
2015-01-08 14:30	pascalvp	Web browser	=> Mozilla Firefox
2015-01-08 14:30	pascalvp	Modules	=> Core
2015-01-08 14:30	pascalvp	Triggers an Emergency Pack	=> No
2015-05-19 17:53	dmiguelez	Web browser	Mozilla Firefox => Mozilla Firefox
2015-05-19 17:53	dmiguelez	Note Added: 0077583
2015-05-19 17:53	dmiguelez	Assigned To	dmiguelez => Triage Finance
2015-05-19 17:53	dmiguelez	Priority	urgent => high
2015-05-19 17:53	dmiguelez	Severity	critical => major
2016-08-30 20:19	nonofrancisco	Assigned To	Triage Finance => rqueralta
2016-09-06 17:13	rqueralta	Assigned To	rqueralta => Triage Finance