I am trying to update over 15,000 parts from AVG Cost to STD. Our company is switching from AVG Cost to STD Cost. I have a DMT that I am using to update the PART Maintenance record to update the cost method from A to S and I have added the column UpdatePartPlant and set it to true. None of the sites with update. Is this an issue with E10? Specifically, 10.2.500? If I cannot get the sites to update, then our trial balance will be all wrong and this will be all for naught. Epicor is no help. I am hoping someone out there can help.
Do you have parts on hand in these bins? If so i donāt believe you can change the cost method on parts with an inventory on hand.
No, No inventory. I made sure of that before updating the Cost Method. There are parts in WIP but that should not matter. I do know that there are parts in inspection, and they did not update to STD. Which I did read needs to be fixed before updating cost method. The Part Record itself updates just fine, but the site record will not. Hereās the kicker. I can go in and manually change it and it prompts me if I want to change the site and it will change it but not through the DMT.
What if you just run a separate DMT for the PartPlant? So, update the Part and then run the PartPlant? Or is that what you already tried?
Already did that, system wonāt let you gives you an error.
Part Sites with different cost methods within the same Cost ID is not allowed.
Have you changed you Site Cost record yet?
And your company default cost?
Yes. Changed it after I qty d everything out and then changed the cost method on the company config. Updated the part before doing a roll-up
Also, The system will not allow me to change just the site record. I have to change it on the part record and then when it prompts to change the site I have to hit. Yes. If I go to the site record and try and update it, it gives me the site records cannot be updated due to different site cost IDs.
We only have one site cost
Mark, the error is you cannot have different site cost within the same cost ID. I have tried updating via DMT, didnāt work. Gave that error. I can manually change the cost method on the part and when prompted to update the sites,I hit yes and the sites get updated. I cannot manually update the sites. Do I need to have a different cost ID per site?
Not if moving to standard cost as you originally posted (and I read more carfully this time). If you were going to Lot costing, thereās some layer settings at the site. Iām wondering why youāre getting that error. Itās been awhile, usually during an implementation, where Iām pretty sure we did this using DMT.
Try a DMT using the Part Combined template:
Columns:
Company, PartNum, CostMethod, PartPlant#Plant, PartPlant#CostMethod, PartWhse#WarehouseCode
I just tried it and it worked for me.
My parts are all FIFO⦠but I was able to switch these two records to Standard with the following:
Just curious and stating what I think everyone already follows, but
- One cost ID assigned to multiple sites
- Sites are set to Average cost
- Want to change all sites to standard cost (for certain parts)
- System requires all sites on that cost ID to be the same costing method
- Canāt change them one at a time
- Canāt change them all at once either
Yeah thatās rough. Itās like the only option is to have an intermediate cost ID for the transition.
Well I hope what @dcamlin just posted will work.
The DMT field is named POORLY, but in addition to UpdatePartPlant being set to true, also use UpdatePartPlantOverride and set that to TRUE as well. In my test system I donāt have Site Cost IDs, so that may still throw a monkey wrench into the works, but worth a shot.
Curious why it appears to have worked for the first two parts, but not the 3rd. You only had 3 errors out of the 8 lines you imported.
It didnāt like UpdatePartPlantOverride, said it is an invalid column
for the first two, they were already set to āSā. I change the last three from āAā to āSā fpr the DMT and thatās the error I get every time.
Check the Template file for the Part DMT upload. Type āPlantā in the search box⦠possibly it wasnāt in your version, maybe it is spelled differently.