[ 
https://issues.apache.org/jira/browse/OFBIZ-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255365#comment-14255365
 ] 

Scott Gray commented on OFBIZ-5704:
-----------------------------------

Yes it is an established pattern for cases where a many-to-many relationship to 
Party is needed, but there's also plenty of examples where many-to-one is all 
that is needed so this pattern isn't followed (and some models use both 
approaches).  When I read through this ticket I was ready to comment in favor 
of your suggestion the same as everyone else, but then I couldn't come up with 
an additional association to Party to use as an example of why your design was 
needed so I decided to discuss that.  

My understanding of lots/batches is that a reseller needs to track the lot id 
for product recalls and for product returns (determining if a lot has abnormal 
QC issues).  Manufacturers using lots in OFBiz don't really need to track 
information using the Lot entity because the production run and inventory item 
models should capture everything that needs to be known about the lot.

Getting mad about the discussion or resorting to ad hominem arguments doesn't 
do anything to further the issue.  I thought it would be straightforward to get 
a use case that makes sense so that we could go with your approach and get on 
with life.  I couldn't care less who is right and who is wrong, I just want our 
designs (particularly data model) to match known/likely use cases.

> 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, Screen Shot 
> 2014-09-03 at 13.52.47.png
>
>
> 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.3.4#6332)

Reply via email to