BOM Attribute Match
This module addresses the BoM case where the product to manufacture has one attribute with tens or hundreds of values (usually attribute “color”, eg: “Configurable Desk” can be produced in 900 different colors).
Creating a dynamic BoM currently requires adding one BoM line for each attribute value to match component variant with attribute value (eg: component “Desk board (Green)” to be applied to variant “Green”).
This has 3 downsides:
BoM lines proliferation (more error prone)
Difficult to update in case a new attribute value (new color paint) is added
Difficult to update in case base component changes.
This module allows to use a product template as component in BoM lines, automatically matching component variant to use in MO line with the attribute value selected for manufacture.
Eg: Product template “Desk Board” is added to BoM line for product “Configurable Desk”; match is made on attribute “Color”. In MO, if product to manufacture is “Configurable Desk (Steel, Pink)”, MO line will have component “Desk Board (Pink)”.
Using the same BoM, if product to manufacture is “Configurable Desk (Steel, Yellow)”, MO line will have component “Desk Board (Yellow)”.
The flow is valid also if the Component (Product Template) has more than one attribute matching the product to manufacture; in this case, on MO line the component variant will be the one matching multiple attribute values for the product to manufacture.
Various checks are in place to make sure this flow is not disrupted:
user cannot add a product in field “Component (Product Template)” which:
does not have matching attributes with product to manufacture
has a different variant-generating attribute than the product to manufacture
Adding a new variant-generating attribute to a product used as “Component (Product Template)” raises an error if the attribute is not included in all the products to manufacture where component is referenced.
Removing an attribute used for BoM attribute matching from product to manufacture raises an error.
On a BoM line with Component (Product Template) set, an attribute value of attributes referenced in “Match on attribute” field cannot be used in field “Apply to variant”.
If attribute value for matching attribute in manufactured product is not present in component (product template), the BoM line is skipped in MO.
Table of contents
Usage
Using this module you can have dynamic components of a BOM. It will allow you to have only 1 line in the BOM if you have hundreds of attribute values for manufacturing product and hundreds of attributes values of component (material).
How to use
Create a product to produce e.g. Desk.
Set 1 attribute (e.g. Color). And select possible values for it.
Create a component product (material) e.g. Plastic.
Set 1 attribute (Color). And select possible values for it.
Create a BOM.
Select a manufacturing product Desk.
Add a BOM line. Select Component (product template) Plastic.
You will see Color attribute appeared in the Apply On Attribute field.
Save the BOM.
Create Manufacturing Order. Select Desk with e.g. Red color to produce and BOM you created.
You will see in the component list Plastic added with corresponding (red) color.
Consider, that to use this feature component must have only 1 attribute. And a values of this attribute of a manufacturing product should be available for a component.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Ooops404 <https://ooops404.com>
Ilyas
-
Iván Todorovich <ivan.todorovich@camptocamp.com>
-
Eugenio Micó <eugenio@studio73.es>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/manufacture project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-mrp-bom-attribute-match 18.0.1.1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_mrp_bom_attribute_match-18.0.1.1.0.3-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_mrp_bom_attribute_match-18.0.1.1.0.3-py3-none-any.whl |
Release files / odoo_addon_mrp_bom_attribute_match-18.0.1.1.0.3-py3-none-any.whl
| Download URL | odoo_addon_mrp_bom_attribute_match-18.0.1.1.0.3-py3-none-any.whl |
|---|---|
| Size | 48.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
41413d42eeb9d954e1ada9c5e14e5c13b126e253f15a89b5374c6aa5602e1f02
|
|
BLAKE2b-256 checksum How to use checksums |
d7b9c464acbd2b83b19dab2d5c6170e9e23e2bfc8084f01de9acfa4e808ff741
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-mrp-bom-attribute-match 18.0.1.1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
