Jacopo,
This is urgent for me. But first, thanks for your tips below.
Let me describe my requirements before suggesting a solution.
I have a product say PC001 that has probably millions of configurations. OFBiz handles that fine,
with the "Configurable Product" concept. PC001 remains a single product for easy administration,
since it's not possible to create millions of variants and corresponding product IDs.
I need some "product ID rules" to specify say unique "configuration IDs" for each configuration,
but I still want a single product ID "PC001".
For eg, a PC001 that has 2x256RAM and 1x2GB_HD may have "configuration ID" PC001-2AR-1AH, where
the 2nd code "2AR" specifies 2 pieces of 256RAM and the 3rd code "1AH" specifies 1 piece of 2GB
HD. So a PC001 that has 1x512RAM and 3x4GB_HD may have a config ID PC001-1BR-3BH. From this
example, you can deduce that 256RAM and 512RAM have codes "AR" and "BR", respectively. And 2GB HD
and 4GB HD have codes "AH" and "BH", respectively.
Entity GoodIdentification doesn't work for me (Product page -> IDs). It allows only 1 ID for each
type ISBN, Manufacturer (Model) Number, Model Year, SKU, etc.
What about Manufacturing rules (BOM -> Manufacturing Rules)? Will that work?
I think this has a lot to do with your intention to store individual configurations in the
database. Like you said, the entity model already caters for storing individual configurations
(via entity ProductConfigConfig). All we have to do now is to provide AUTOMATED rules for
generating the value for field ProductConfigConfig.configId. I believe this entity isn't used yet,
according to what you said. Right?
I HAVE to implement this right away. I'm calling for suggestions, instructions, guidelines to
direct my development so that what I do can be contributed verbatim back to the community.
Ideas?
Jonathon
Jacopo Cappellato wrote:
> Jonathon,
>
> Jonathon -- Improov wrote:
>> Jacopo,
>>
>> So are you planning to do the "Create multiple Production Runs for
>> Configurable Product" feature? If so, when?
>
> No, I'm sorry but I don't have plans about this at the moment.
>
>> If you want me to do it, can you bring me up to speed quickly so I can
>> put my work back here for public audit? If I were to do it, I'd
>> probably start with the "creation of new production runs based on the
>> configuration id" feature.
>
> I'd suggest looking at the ProductConfig* classes (that handle many of
> the configuration related tasks):
>
http://svn.apache.org/repos/asf/ofbiz/trunk/applications/product/src/org/ofbiz/product/config/
>
>
> In particular:
>
http://svn.apache.org/repos/asf/ofbiz/trunk/applications/product/src/org/ofbiz/product/config/ProductConfigWrapper.java
>
> is the class that represents a product configuration, so the idea is to
> add a new method to it (something like store()) to store the
> configuration in the db.
> About the data model, here are the entities involved:
> ProductConfig
> ProductConfigItem
> ProdConfItemContent
> ProdConfItemContentType
> ProductConfigOption
> ProductConfigOptionIactn
> ProductConfigProduct
> ProductConfigConfig
> ProductConfigStats
>
> Some of them are still not used by the system; in particular,
> ProductConfigConfig is the entity that should be used to store a
> particular product configuration.
> They are all defined here:
>
http://svn.apache.org/repos/asf/ofbiz/trunk/applications/product/entitydef/entitymodel.xml
>
>
> If you want to see how the demo product PC001 is persisted in the db:
>
>
http://svn.apache.org/repos/asf/ofbiz/trunk/applications/ecommerce/data/DemoConfigurator.xml
>
>
> The user interface to edit the above data is here:
>
> https://demo.dejc.com:8443/catalog/control/FindProductConfigItems
>
> During order entry, you can configure a pc both in the ecommerce and in
> the order manager application (click on the "configurable pc" category
> in the left-hand side and then select the PC001).
>
> Hope this helps,
>
> Jacopo
>
>
>>
>> You mean it takes 0.5 to 1 day of work to do the above feature? Or
>> just to do the "Copy an existing production run" feature? The above
>> feature doesn't seem easy.
>>
>
> Yes, the 1 day estimate was about the "Copy an existing production run"
> feature; the other one is not so easy, even if there is already a lot of
> stuff in place.
>
> Jacopo
>
>> Jonathon
>>
>> Jacopo Cappellato wrote:
>>> Yes, the copy of a production run is not currently implemented (but
>>> it should be a rather easy task, let's say 0.5 to 1 day of work, for
>>> a developer with a good knowledge of OFBiz).
>>> The main reason is that, usually (for non pc - type products) the
>>> production run is quickly created from the bom and the routing (that
>>> both represents the 'template' for the production run).
>>> For pc-like products, the initial plan was to store the configuration
>>> (there is already the entity for this) and then use it in the system
>>> to do various tasks, such as:
>>> - statistics of top sold configurations
>>> - pre-configured items proposed to the customers
>>> - creation of new production runs based on the configuration id (this
>>> is what you would need here)
>>> - planning
>>> - bom explosions
>>> - and, most of all, by storing the configuration there will be no
>>> need to immediately create the production run when the order is
>>> created as is now (having a more flexible system).
>>>
>>> Jacopo
>>>
>>>> Jonathon
>>>
>>>
>>>
>
>
>
