Hi everyone! I’m looking to create a variance calculation field in the Part application. The variance is displayed directly in the Costing Workbench report as the difference between the old standard and new standard, but I couldn’t find any database fields named ‘variance’ or anything related to the old and new standards. Does anyone know how I could achieve this? I’ve attached a screenshot of the report where the variance is auto-calculated and displayed. Any tips on how to track down where this calculation happens in the system?
1 Like
If you make a BAQ to the costpart table there are fields called:
You can add those up and that should total the “old” unit cost. Then you can do the difference between those and these to get the variance.
As long as the original cost doesn’t get modified you should be good.
I did a similar change to this report and even added Inventory On Hand, to estimate the total impact of the delta valuation. Unfortunately I don’t have that RDL in my files. From what I can remember you could easily do this at the SSRS report builder, add a calculated field that gives you the var Old vs New.
1 Like
If you want I have an idea for that:
Make a Group Edit List for Costing | Epicor Kinetic Ideas Portal
1 Like
Hi, I don’t want to edit the report itself. I just want to create something that will display the variance within the Part application. I’m having trouble figuring out how to achieve this. From what I’ve seen, there isn’t a field that stores variance; it’s calculated as a difference using multiple fields. I want to display only the variance field within any part. Do you have any ideas on how to do this?
Not an easy task, since your variance is a calculated field between the old and the new cost. When ever there is a cost adjustment or cost roll up that value changes. Unless you create a custom table to store historical variances and a custom that will update your custom table when ever there is a cost roll up.
Should be able to get this intel via PartTran ADJ-CST transactions…when the cost rolls, there’s a reduction of inventory OH at the old cost, restoration of it at the new cost and generates records even if onhand is zero.
Yes you are right, that’s also an option, but I can see that overloading your baq really fast, since you’ll be picking every Cost ADJ for each part, so the design of the baq should be really specific to dates and likely need to setup a reason code to be able to identify between ROLL UP ADJ-CST and the rest of ADJ-CST transactions
Good point - guess I need to start thinking on a larger scale than what we operate under (limited number of parts, plants, etc.). PartTran.TranReference does carry a value of “Standard Cost roll-up” on them.
