[
https://issues.apache.org/jira/browse/OFBIZ-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505062#comment-14505062
]
Christian Carlow commented on OFBIZ-6085:
-----------------------------------------
Pierre,
TimeEntry was extended to act as InventoryItemDetail does for InventoryItem.
The quantityProduced and quantityRejected fields allow for the entry to be
reverted similar to InventoryItemDetail and have it update the corresponding
task quantityProduced and quantityRejected. InventoryItemDetail alone is
insufficient for providing the WorkEffort details. If the user doesn't choose
a facilityIdTo in the declaration form then only the TimeEntry is created
without tiggering the inventoryTransfer that creates the InventoryItemDetails.
The timeEntryId field was added to InventoryItemDetail so the transfer
information could be determined. For example, if a declaration time entry was
created to move 1 from A to B and a second to move 2 from A to C,
InventoryItemDetail.timeEntryId allows the second move to be reverted from C to
A. InventoryItemDetail.workEffortId is insufficient because it doesn't
support such reversion functionality nor the ability to determine which
timeEntry and therefore party was responsible for the move.
I'm not very familiar with OFBiz OLAP but am willing to dedicate time to
extending this functionality to it such as the ProductionRunFact entity.
However, it seems the existing functionality is still needed regardless.
As for potential confusion of operators/users of OFBiz, this patch simply adds
another form at the bottom of the page that lists the details of each
declaration at the bottom of the page. It basically allows for the old
functionality to work exactly the same it just creates timeEntries for each
declaration. Perhaps a more acceptable solution would be to make the timeEntry
functionality optional?
> Add support for production run inventory tracking
> -------------------------------------------------
>
> Key: OFBIZ-6085
> URL: https://issues.apache.org/jira/browse/OFBIZ-6085
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Trunk
> Reporter: Christian Carlow
> Assignee: Pierre Smits
> Attachments: OFBIZ-6085.patch
>
>
> Production run inventory tracking seems worthy of support so that production
> managers can get an idea of the department work load. InventoryItemDetails
> should be created during production run declarations so that the material
> that was stocked out for the production run can be tracked while it is being
> manufacturing into the good. Essentially is would be like stock moves or
> inventory xfers occuring within the production runs for the task fixed asset
> facilities/locations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
