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

["Swapnil Shah (JIRA)" <ji...@apache.org>]

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

Swapnil Shah edited comment on OFBIZ-5985 at 3/19/16 1:20 PM:
--------------------------------------------------------------

[~paul_foxworthy] [~pierre smits]
I reckon, It is possible at times that resource(fixed asset) capacity varies from one resource to another even if they are of same type. 

So for planning (MRP) purpose it could be more accurate if it has specific resource's capacity to consider while processing. Whereas for execution purpose the production/floor manager should always have option to switch over the resources unless the operation(routing task) is not completed. Over the production run screen system at best can suggest the list of alternate resources available on basis of eligible types during execution phase so as to facilitate user to select the right ones. 

Apart from it the resource (fixed asset) amendments made during execution phase shouldn't affect the planning (MRP) run as its more often than not going to be periodic and well sparse in time bucket than execution cycle.  Also, as far as MRP run is concerned all the changes already made during operational phase during production run execution would be always accounted for and capacity plan should reflect the same.


was (Author: swash78):
[~paul_foxworthy] [~pierre smits]
I reckon, It is possible at times that resource(fixed asset) capacity varies from one resource to another even if they are of same type. 

So for planning (MRP) purpose it could be more accurate if it has specific resource's capacity to consider while processing. Whereas for execution purpose the production/floor manager should always have option to switch over the resources unless the operation(routing task) is not completed. Over the production run screen system at best can suggest the list of alternate resources available on basis of eligible types during execution phase so as to facilitate user to select the right ones. 

Apart from it the resource (fixed asset) amendments made during execution phase shouldn't affect the planning (MRP) run as its more often than not going to be periodic and well sparse in time bucket than execution cycle.  Also, as far as MRP run is concerned all the changes made during operational phase would be always accounted for and capacity plan should reflect the same.

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