[
https://issues.apache.org/jira/browse/OFBIZ-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551726
]
Jacopo Cappellato commented on OFBIZ-1453:
------------------------------------------
Bilgin,
first of all I'd like to clarify that I'm really happy to see that you are
enhancing and completing the AGGREGATE product implementation.
It would be great to get others' opinion on the best way to manage
"configurations" in the system, but unfortunately it is a very complex and
important decision and I'd say we should wait some more time to let other to
elaborate and express the best solution.
It is a difficult one and in fact, even if I'm expressing here some of my
opinions, I have to admit that I'm not totally sure about the best solution.
About the need to manage the configurations in inventory (InventoryItem): this
could happen if we get a return from a customer; or if we assemble some
products and then we can't ship them (for example because the order is
cancelled); but there are possibly other scenarios. However, I know that for
each of the above situations there are many alternative 'organizational'
solutions and not necessarily we will need to store the configId in the
InventoryItem.
By the way, here is a possible alternative solution:
1) the configuration is store exactly as you already did
2) instead of adding the configId field to the Order*, Inventory* etc entities,
we will add it to the Product entity
3) when an order is created for a new configuration: the configuration is
stored with a configId, a new special product is created with the configId set
and it is associated to the AGGREGATE product (Product and ProductAssoc); this
new productId will be used everywhere (orders, returns, inventory, production
runs etc...)
4) it is probably ok to add the configId to the Quote, CustRequest,
ShoppingList because we will create the new product only when a real order is
created for the configuration
Jacopo
> store/load possibility for AGGREGATED product configurations
> ------------------------------------------------------------
>
> Key: OFBIZ-1453
> URL: https://issues.apache.org/jira/browse/OFBIZ-1453
> Project: OFBiz
> Issue Type: Improvement
> Components: order, product
> Affects Versions: SVN trunk
> Reporter: Bilgin Ibryam
> Priority: Minor
> Fix For: SVN trunk
>
> Attachments: aggregated.patch, aggregated_full_for_review.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
