[
https://issues.apache.org/jira/browse/OFBIZ-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202769#comment-15202769
]
Pierre Smits commented on OFBIZ-5985:
-------------------------------------
Indeed. The difference to consider herewith is association of a class (or type)
of fixed assets versus actual fixed asset association to a task in a production
run.
As an example a brewery can have multiple sizes of lager tanks (class - or type
- is lager tanks), e.g.:
* big sized lager tanks of 50 Hl capacity
* medium sized lager tanks of 10 Hl capacity
* small sized lager tanks of 5 Hl capacity
The planning mechanism should look at the available fixed assets in the class
(for the execution period) and determine the optimum when allocating
considering availability.
> Support routing task standard quantity tracking of fixed assets
> ---------------------------------------------------------------
>
> Key: OFBIZ-5985
> URL: https://issues.apache.org/jira/browse/OFBIZ-5985
> Project: OFBiz
> Issue Type: Improvement
> Components: workeffort
> Affects Versions: Trunk
> Reporter: Christian Carlow
>
> I need the ability to assign track the standard quantity that can be run by
> fixed assets for a routing task. WorkEffortFixedAssetStd contains a
> fixedAssetTypeId instead of fixedAssetId I've found no code using the entity
> other than the one that allows the entity data to be manipulated. Therefore,
> to prevent adding another entity to the model, would replacing
> fixedAssetTypeId with fixedAssetId be a worthy solution?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
