I’m wondering if anyone can help point me in a direction here. To begin with, here’s a little info on the foundation of this problem:
We have some configurable quotes powered by a custom built website. Our site allows for us to export these quotes out to Epicor / Kinetic once a user is ready. We do this using the REST API. I won’t bore anybody with the details about the quoting setup unless it becomes relevant. What is important to know is that we charge a certain fee based on the expected ship date of an order to account for material price increases. For that, we create what we call an Escalation line. When using REST to create the lines in Epicor we get our data coming through as expected on the quote entry screen. However, we have an issue that refuses to go away where the line pricing changes to incorrect values when converted to a sales order.
I’ve attempted for over 2 years to have official support give me any idea as to what could cause this, but I’ve consistently gotten the same two answers of either “Do a stack trace, the REST implementation is the same logic”, or “That’s custom code pay someone for a fix.” Instead I guess I’ll try my luck here. All I’m really hoping for is that someone might be able to tell me what fields could cause data to be ignored or changed incorrectly when converting between a quote and an order. I imagine that I’ve simply glossed over something that Epicor considers to be an important field, and as a result the order gets created with invalid data instead of pulling it correctly from a quote line. Any assistance is much appreciated. If needed I can post some example data, but again I’m really looking mostly for an understanding of the quote / order fields and how they correlate rather than troubleshooting my code. What type of flags would cause prices to change or re-pull from somewhere else, etc.