Hey Steve,
In Site Maintenance, in the Actions menu, there is a process to change the Cost ID. I would try it out in test to make sure it works - especially with FIFO. It does create posting entries. Try it in test first! Don’t FAFO your FIFO.
Hey Steve,
In Site Maintenance, in the Actions menu, there is a process to change the Cost ID. I would try it out in test to make sure it works - especially with FIFO. It does create posting entries. Try it in test first! Don’t FAFO your FIFO.
What Mark said!
We just moved a separate company to a site in our instance. When I was doing tests, I originally didn’t update the cost ID, and we are 100% FIFO. After the fact, I found the results were all messed up. This means costs from one site got removed as we did transactions at the other site.
Glad we fully tested before we went live…
Definitely do this in a test and see what happens. Look over the adjustments carefully and see what the stock status/trial balances show before and after.
Thanks @Mark_Wonsil yes, I saw that, and I’m trying to make a procedure for all the related activities, like do we need to adjust out to zero first Nd backnin later? Or do a count afterwards? Or, what happens in the (many) places where onhand is more than FIFO onhand in one of the sites? Etc.
I guess it’s basically hypothesis / test.
I have spent a lot of time on this issue.
We are splitting a Cost ID used by many Plants, into separate ones - one for each Plant, so that each can maintain their own costs.
Costing Workbench will copy over the records, but will only fill in the Standard Cost.
For Average and Last Cost, if you want those, you have to do it yourself.
DMT is NOT an option, simply because there is no DMT type for PartCost.
So, I have created a KILLER updatable dashboard, that lays this all out easily, including taking care of the “Quantity” field that is required as part of the Average Cost amount.
Not Cost Adjustment? Or am I missing something? Not sure I’d used FIFO for it but it seems to be here too.
Good point there Mark.
I guess the only downside is that you can’t roll or analyze anything before hand if you just make a cost adjustment.
Honestly @JevonJoseph you could probably customize the screen and make a button that runs through each row in your dataview and then runs a function to go out and grab the average cost or whatever and update that row in the dataview.
If that’s what you’re trying to do is just get those to populate?
Maybe something like this: Kinectic Application Studio - Iterate Dataview rows to update values - Kinetic ERP - Epicor User Help Forum
IMHO, it’s this:
So, for example, we use a new cost set every year. Doing a roll-up to accomplish this is off the table for me. Why? First, go ahead and criticize this as whining, but it is just too hard. I have lots of reasons. Another day. But second is that there - you lose everything historical from last year’s cost set. I hate to give that up.
To continue the diary on this, I have done this two more times - in July 2023 and 2024. It keeps hitting the same wall in one of our sites (the other two are fine). This really angers accounting.
I think I will change my procedure next year and it will address all those concerns and the ones today.
My plan is to keep the same cost set year after year as the active one, but ALSO create a new one every year to store the old costs. This should accomplish all of the goals.
The only way to populate cost sets that never get used is with a uBAQ as I describe earlier.
Agree. I was just saying there seems to be a DMT for PartCost.
Again, I’m in the camp of doing a periodic dump of the costs and save them somewhere: Cost Set, Cost Group, UD Table, wherever you’re comfortable.
There’s often a balance between using storage or processing. In the case of analyzing history, I much prefer storing the history than recalculating it. IMHO.
Agreed. We grab costs and onhand daily (at minimum) in Access and/or Excel for storing things “as of”. For us it’s quasi-practical based on our operations…but wouldn’t be for deployments with exponentially larger Part and/or PartBin counts than we have.
Right. It really depends on the value one gets out of that kind of analysis.
So @Mark_Wonsil and @JMPCONJ how do your companies do yearly standard cost updates - or do you?
Do you use the same cost set every year?
I get the archiving part, but I am asking as far as your Epicor procedure for the actual change.
For us, the biggest benefit has been the ability to get that as-of-Date-X inventory and part cost status for in a far quicker manner than grinding through PartTran records to recreate a balance. It’s one of those carryovers that I built for our old ERP…capture and store for that day when the auditors come calling, or someone blew up a part cost, etc…
We use one cost set for production. At other companies, we had an additional cost set per year after the roll up.
How many copies is determined by the value you get from it. One could dump them daily to CSV files and then load them into a Cost Set for analysis and delete them when done. Or use another tool like Excel or PowerBI to do analysis. There are lots of options - especially when one includes Lot costing.
Bulk of our stuff is average cost - parts we purchase and EITHER directly distribute OR use as components in our manufactured parts. We do standard cost rolls periodically…not on a yearly basis nor do we change cost sets.
To the original point (of this mini-thread), this is a logical need and still pretty miserably hard to accomplish, right?
I mean you can do the rollup thing and get portions of the old data, or the uBAQ I mentioned and hope it works. But the tools to do this well and easily just are not there.
I’m glad we don’t do plant-level cost IDs…but can certainly understand why the functionality would be needed especially in multisite/multinational configs. We only manufacture at one of our three US-based sites so we’ve got a pretty simple setup.
In costing work bench, In a new group, you copy from one Cost Site ID:
Then at posting time, you post to the new Site Cost ID.
Doesn’t seem very miserable to me.
I know. I wrote about it earlier. To recap:
This is not easy to me.
Screenshots:
First pass
Second pass