[
https://issues.apache.org/jira/browse/OFBIZ-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121086#comment-14121086
]
Pierre Smits edited comment on OFBIZ-5704 at 12/21/14 10:02 AM:
----------------------------------------------------------------
The uses cases are straight forward:
The user must (in case the product has the flag stating lot management is
mandatory) or shoud (in case the product has the flag stating lot management is
optional) provide all necessary details to do proper tracking and tracing.
In the case of registering inbound deliveries from external parties (suppliers
et. al) this means he has to provide the partyID of the manufacturer and its
batch reference.
This is more complicated in the case of manufacturing as there are options
possible:
# automatically from productionRunId for each production run
# manually (user defined)
# based on some custom (integrated) batch reference determination program
# automatically from productionRunId from the parent production run
With respect to manufacturerId this should by default come from the partyID of
the associated party with roleTypeId="MANUFACTURER".
The inventory item registration process should then check whether a lot record
exists with the parameters partyID (of the manufacturing party) and the batch
reference. If and when such a lot exists that lotID must be referenced in the
inventory item record. If no lot record exists, the process should create a new
lot record with those details. And the lotID of that newly created lot record
should be referenced in the inventory item.
We have to keep in mind that everything done in relation to the lot record is
executed through the processes related to inventory items. This also applies to
tracking and tracing.
was (Author: pfm.smits):
The uses cases are straight forward:
The user must (in case the product has the flag stating lot management is
mandatory) or shoud (in case the product has the flag stating lot management is
optional) all necessary details to do proper tracking and tracing.
In the case of registering external deliveries this means he has to provide the
partyID of the manufacturer and its batch reference. With respect to the batch
reference this is more complicated in the case of manufacturing as there are
options possible:
# automatically from productionRunId for each production run
# manually (user defined)
# based on some custom (integrated) batch reference determination program
# automatically from productionRunId from the parent production run
With respect to manufacturerId this should by default come from the partyID of
the associated party with roleTypeId="MANUFACTURER".
The inventory item registration process should then check whether a lot record
exists with the parameters partyID (of the manufacturing party) and the batch
reference. If and when such a lot exists that lotID must be referenced in the
inventory item record. If no lot record exists, the process should create a new
lot record with those details. And the lotID of that newly created lot record
should be referenced in the inventory item.
We have to keep in mind that everything done in relation to the lot record is
executed through the processes related to inventory items. This also applies to
tracking and tracing.
> 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)
