[
https://issues.apache.org/jira/browse/OFBIZ-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106890#comment-14106890 ]
Christian Geisert commented on OFBIZ-5704:
------------------------------------------
I think implementing the wanted functionality this way isn't a good idea.
I'm sure there are companies who handle their lot ids like this (use vendor lot id), but others want to have their own lot id AND record the vendor lot id.
This change would further require to extend InventoryItem with lotPartyId (or Role...), which isn't something I would call a good databse design.
I think the best way to implement this is to add an new field vendorLotId (or maybe LotAttributes/LotFeatures).
> Extend lot entity to include party Id of manufacturer
> -----------------------------------------------------
>
> Key: OFBIZ-5704
> URL:
https://issues.apache.org/jira/browse/OFBIZ-5704> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing, product, workeffort
> Affects Versions: Release Branch 11.04, Release Branch 12.04, Release Branch 13.07, Trunk
> Reporter: Pierre Smits
> Attachments: OFBiz-5704-Product-EntityModel-Lot.patch
>
>
> Rationale
> Lot or batch management affects two places, namely the outbound process (and its functionalities) and inbound.
> It is possible that multiple parties have the same ID for the batch or the lot. Howver, in current feature set there is no discrimination between lots from supplier A, supplier B, or even the primary (internal) company in OFBiz.
> Therefore the entity 'Lot' should be extended with another key, namely that of the partyId of the manufacturer (or supplier).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Locked
