[
https://issues.apache.org/jira/browse/OFBIZ-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106920#comment-14106920
]
Pierre Smits edited comment on OFBIZ-5704 at 8/22/14 2:59 PM:
--------------------------------------------------------------
The rationale behind all this is twofold:
# The manufacturer determines the lot id or the batch Id. This is used in
communications and mentioned in orders, invoices and other documents. The
business reason behind this is the aspect of tracking and tracing with respect
to a.o. health issues. If the supplier is the manufacturer, he will use this in
his communications. Thus this is the ID that needs to be registered. If such a
product is bought by a wholesaler who breaks up the shipment in smaller
quantities (e.g. 1 pallet containing 100 sacks of weedkiller), this wholesaler
will - in general - not create his own lot id but use that of the manufacturer
when he sells. Because creating his own lot ids would mean that he is also
responsible for creating the correct documentation when health (or safety)
issues occur, and he has a fargoing obligation to inform customers.
# Assigning your own lot ids to products bought can be done (OOTB in current
feature set), but would create somewhat similar issues as the wholesaler has.
Mapping manufacturer communications to your own lot ids means extra work.
Besides you already have inventory ids to find the products in the warehouse.
And it is inventory items that you scrap when told to.
In the aspect of self manufacturing (of products) using components or
ingredients that have assigned lot ids (by their manufacturers), you need to be
able to trace the affected and used lot of the component via the production
runs to the deliveries to the customers delivery addresses. As the manufacturer
of such products you define and assign your own lot ID to the products you
make, and use that in your communications to your customers.
Actually, manufacturerLotId would be a better name for this field.
I am open to suggestions.
was (Author: pfm.smits):
The rationale behind all this is twofold:
# The manufacturer determines the lot id or the batch Id. This is used in
communications and mentioned in orders, invoices and other documents. The
business reason behind this is the aspect of tracking and tracing with respect
to a.o. health issues. If the supplier is the manufacturer, he will use this in
his communications. Thus this is the ID that needs to be registered. If such a
product is bought by a wholesaler who breaks up the shipment in smaller
quantities (e.g. 1 pallet containing 100 sacks of weedkiller), this wholesaler
will - in general - not create his own lot id but use that of the manufacturer
when he sells. Because that would mean he is also responsible for creating the
correct documentation when health (or safety) issues occur.
# Assigning your own lot ids to products bought can be done (OOTB in current
feature set), but would create somewhat similar issues as the wholesaler has.
Mapping manufacturer communications to your own lot ids means extra work.
Besides you already have inventory ids to find the products in the warehouse.
And it is inventory items that you scrap when told to.
In the aspect of self manufacturing (of products) using components or
ingredients that have assigned lot ids (by their manufacturers), you need to be
able to trace the affected and used lot of the component via the production
runs to the deliveries to the customers delivery addresses. As the manufacturer
of such products you define and assign your own lot ID to the products you
make, and use that in your communications to your customers.
Actually, manufacturerLotId would be a better name for this field.
I am open to suggestions.
> 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)
