All "Leg" work orders have 0 actual Cost?
It has become increasingly important in the company to report actual costs for various Work Order Legs. In the knowledge base, there is an article that claims you can use the Act_burden_cost, Act_Material_Cost etc in the Work order table in order to report costing information for legs (source: www.inforxtreme.com/.../1355266.asp If the article is accurate, my problem would be easily solved.
In our database, however, work orders that have a sub ID <> 0 have a cost of 0 (costs for all legs are summed and put into the main header). I have got around this "feature" in the past by summing the actual cost fields in the operation table for a given leg. This works great, as long as there aren't legs coming off of other legs. As soon as a leg contains a sub-leg, I do not know of a way to pull the operations in that sub-leg to get its costs totaled for the part.
Does anyone else see all leg work orders have an actual cost of 0? Is there a way to report on total leg cost without having to go through some sort of recursion to find all operation costs in sub legs?
[Updated on 3/26/2013 6:23 PM]
In our database, however, work orders that have a sub ID <> 0 have a cost of 0 (costs for all legs are summed and put into the main header). I have got around this "feature" in the past by summing the actual cost fields in the operation table for a given leg. This works great, as long as there aren't legs coming off of other legs. As soon as a leg contains a sub-leg, I do not know of a way to pull the operations in that sub-leg to get its costs totaled for the part.
Does anyone else see all leg work orders have an actual cost of 0? Is there a way to report on total leg cost without having to go through some sort of recursion to find all operation costs in sub legs?
[Updated on 3/26/2013 6:23 PM]
0
Comments
-
That document you reference, 1355266 is poorly written and sure looks inaccurate to me. Unless there is some setting to stop leg costs from rolling up to the main part that I don't know about. The doc mentions costs being in the requirement table for sub id's but that does not appear to be true either.
My method for determining leg costs has been to use the labor tickets. It's a nuisance though.0 -
Your labor ticket approach is similar to my operation approach, but would not include the costs of materials and services (which i need).
Are you pulling labor tickets for one leg at a time, or are you able to pull information for a leg, and all of its "sub-legs"?
Essentially, my problem here is my inability to relate "sub-leg" operations to a "parent-leg" work order without doing some sort of recursion on the requirement table. Leg costs are rolled up correctly in the "Info/Costs" area of a Work Order in Visual, so I am hoping to pull that information into a report.0 -
Depending on how you create your report or query you could have labor ticket data for each individual leg, or have it roll up however you wanted it. Typically our legs do not have material costs so I see your dilemma; you'd have to pull matl costs for legs based on quantities issued and their value from the inventory transactions; it just gets complicated fast.
You're right about the Info/Costs; since Infor can present that data correctly there must be way for us to do it too. Have you contacted Infor?0 -
This was my first stop, since I figured Infor would just point me to the knowledge base article. Since you agree that the article is not correct, I will contact them. Thanks for your help!0
-
Chris,
Have you thought about not using legs at all? If you want to be able to deal with the "part" made with the leg, give it the part number and make it on its own work order. You have total cost visibility as well as scheduling.
Jim0
Categories
- All Categories
- 3 General Posts
- 6 Public Sector
- 5.8K Developer Community
- Migrated Forums
- Cloud Migration
- 5 Community News
- 2 User Groups
- 4 Featured Content
- Featured Developer
- Featured Public Sector
- 4 Featured Forums
- Featured Healthcare
- 2 Announcements
- Customer Bulletins
- In the Birst Space
- Legacy Blog Posts
- 132 RMS News
- Site News