[
https://issues.apache.org/jira/browse/OFBIZ-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14344447#comment-14344447 ]
Paul Foxworthy commented on OFBIZ-5985:
---------------------------------------
Hi Christian,
I think the reason you're seeing a type and not one fixed asset is that MRP will schedule and assign assets according to current requirements and priorities. Change the jobs to be done, and a different asset might be assigned to a particular WorkEffort.
I would argue your suggestion should not replace the current behaviour, and manually assigning a fixed asset to one WorkEffort defeats the purpose of MRP.
If you are having problems here, perhaps your fixed asset types are too broad. If it seems strange to have a list of types each having exactly one fixed asset, remember that tomorrow you could add a second asset of a type, re-run MRP, and jobs would automatically be spread between the two. If your WorkEfforts talk about a specific fixed asset, you will need to alter them when you get new equipment.
Hope that helps.
Paul Foxworthy
> 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)
Locked
