[jira] [Commented] (OFBIZ-5985) Support routing task standard quantity tracking of fixed assets

["Pierre Smits (JIRA)" <ji...@apache.org>]

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

Pierre Smits commented on OFBIZ-5985:
-------------------------------------

Firstly, if you're the only one needing the functionality you could solve this in your own working copy.

Apart from that, this is a valid improvement issue. Assignments of fixed assets to production run tasks based on tasks associated to production schemas (automatic assignment as opposed to manual assignment after the production run has been created) should be possible on more criteria than just the fixedAssetTypeId. 

We have, therefor, in our setup for our customers extended the WorkEffortFixedAssetStd with not only fixedAssetId (for assignments of specific fixed assets) but also on classEnumId. In subsequent functionality we assess availability of the associated fixed assets (based on the criteria provided in WorkEffortFixedAssetStd) and register the suggestion as association to the production run (when it concerns only one and specific fixed asset or combo). If it concerns multiple fixed assets (multiple variants or multiple combo variants) the users must select the appropriate one.

> 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)