Jacopo,
Nice! So, with your implicit rules, I don't even have to touch the
Manufacturing Rules.
Take the example ManufacturingExampleData.xml Scott pointed out. I can actually delete the 2 rules
R01 and R02 and it'll all still work. R01 is substitutes WG-COVER-B for WG-COVER if feature is
COLOR:Black, correspondingly for R02 dealing with WG-COVER-S (Silver).
And to further delete rules R03 and R04, I can:
1. Create virtual product WG-WHEELBASE, and variants WG-WHEELBASE-3 and
WG-WHEELBASE-4 (complete with selectable features for WG-WHEELBASE and
distinguishing features for variants).
2. Create BOM for WG-WHEELBASE-3 with 3 units of WG-WHEEL-STD; 4 for
WG-WHEELBASE-4.
3. Remove WG-WHEEL-STD from BOM of WG-FRAME
4. Add WG-WHEELBASE (quantity 1) to BOM of WG-FRAME
Works!
Did you do all these, Jacopo? By the way,
http://ofbizwiki.go-integral.com/Wiki.jsp?page=Manufacturing is down.
Jonathon
Jacopo Cappellato wrote:
Jonathon,
Scott's advices are correct.
I'd like to mention that:
* if you have a virtual product with a BOM and the product has some
variants associated to it without BOM, the system will use the BOM of
the virtual product: there is no need to duplicate the BOMs from the
virtual to the variants; or you can only create the BOM of the variants
products that have a BOM different from that of their virtual
* virtual BOM are also supported: if you have a virtual product T-SHIRT
with selectable features RED, YELLOW and you create as a component for
its BOM another virtual product, CLOTH, with the same selectable
features (RED, YELLOW) and then create the variants for the CLOTH and
for the T-SHIRT, you have implemented a virtual BOM. When you'll create
a production run (or you'll run a BOM simulation) for one of the
T-SHIRT's variant, the system will automatically select the right
variant CLOTH.
* what I have described above are the 'implicit' BOM rules; as Scott
said you can also create 'explicit' rules using the Manufacturing ->
Bill of Materials -> Manufacturing Rules page; for example component
inclusion/exclusion/substitution rules can be implemented as explicit
rules; however, that part of the system should probably need a few
cleanups or improvements
There is more than this, but I don't want to add too many details...
Happy testing,
Jacopo
