I am pulling my hair out over this one and cant work out what the hell is actually going on and why the system is doing this……
We have been working on V2 of one of our configurators for quite a while now to massively improve it as well as automate some of the misc charges (solution for this posted on the forum).
in our PILOT system, the price writes perfectly every time, i have tested it hundreds of times and never had any issues, whatever the total price is in the configurator, when we write the price to the quote or order, it remains the same..
here is a trace from it too showing what is happening on save….this is relevent!
not a lot happens on the save, it just does what it needs to!
NOW HERES THE FUN PART………
in our live system, we have copied the configurator over, set the part, document rules etc so everything is IDENTICAL to PILOT….we know its identical because we did a copy down from live just before the upgrade to 2025.2.5
every time we are saving the configurator, the unit price is changing and it is always chaning by the value of our UOM which is 1.19
when i have done the same trace from the same point we can see its doing a calculation…..
First thing I would check is if your configurable part has the same SalesUM in Pilot as it does in Live. I’m looking at your values here… is the configurator calculation coming up with the $62.40, and then Epicor is forcing the calculation down to $52.43697, or is it the reverse?
Both systems are identical, copydown was done from Live to Pilot 4 weeks ago and no changes have been made in either system other than they are now both on 2025.2.5
And you are correct the configurator is pricing at 62.40 and the Live system is then rounding down to 52.43697
This is divided exactly by our UOM which is 1.19…but i dont understand why it is changing it based on the UOM anyway.
The UOM is set way before all the other fields and the price is set last
we sell it in widths of 1190mm, 1010mm, 1000mm, 900mm, 890mm
it is manufactured in LM but sold in M2 so we have a UOM for each width of panel we sell.
what i did find in pilot was if the UOM before doing anything was not in the part sales UOM i had pricing issues so based on that, the document rules sets the UOM to the sales UOM (1190)then does everything else it needs to do, then sets the price and finally sets the UOM to the correct one.
this has worked flawlessly in pilot during the hundreds of combinations of panel i have configured without issue and not a single error!
It was the sales uom that was wrong…because we had a full copy down from pilot to live and it was working in pilot i made a very silly assumption that both systems were the same…how wrong i was, there are Soooooo many differences when i have taken a dive into it, its actually shocking that epicor can call it a full systemml copy down!
Anyways the pricing works which is the main outcome of this!