[
https://issues.apache.org/jira/browse/OFBIZ-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215892#comment-15215892
]
Swapnil Shah edited comment on OFBIZ-5985 at 3/29/16 12:52 PM:
---------------------------------------------------------------
I believe Production Manager generally weigh in all the pros and cons by
accounting for all these factors while setting up the association between
primary resource(fixed asset) and its possible alternates w.r.t to a given
operation(routing task). System can facilitate by providing a way to assign the
priority amongst all possible alternatives say under
WorkEffortFixedAssetStdAlt.
Such prioritization can then be honored both during planning run (via MRP
engine) or during production run execution phase in order to provide better
suggestions to floor managers/operators to achieve the optimal mix.
was (Author: swash78):
I believe Production Planning Manager generally weigh in all the pros and cons
by accounting for all these factors while setting up the association between
primary resource(fixed asset) and its possible alternates w.r.t to a given
operation(routing task). System can facilitate by providing a way to assign the
priority amongst all possible alternatives say under
WorkEffortFixedAssetStdAlt.
Such prioritization can then be honored both during planning run (via MRP
engine) or during production run execution phase in order to provide better
suggestions to floor managers/operators to achieve the optimal mix.
> 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)
