[Janine Breton]

We are preparing to launch AX2012R3 and are running into an issue where the sales order line price is overwritten by the base sale price from the item detail.  This behavior is when a sales order line price is determined via price override, or is discounted via a source code driven by retail offer.  No problem.  However, when a processed order is modified in some way, or a return order received, the original pricing from the sales order line reverts to the base retail price.  There must be some setup we are missing since it is consistently happening, even when a gift card order comes in from our website (back to zero!).  Has anyone run into this or have a suggestion of where to start?  Parameter settings, retail discounts, price groups, or something about associating a lot id number… All input on so many possible things going on it’s hard to narrow down.  Thanks so much for any direction you can offer!

NOTE: we did find this thread that describes the issue – anyone have updates that are not a “modification”?

https://community.dynamics.com/ax/f/microsoft-dynamics-ax-forum/151219/unit-price-on-sales-order-lines-update-automatically-when-any-data-is-changed    

Best Regards,

——————————
Janine Breton
Business and Reporting Analyst
America’s Gardening Resource
Burlington VT
——————————

[Daniel Walter]

I don’t have an answer but possibly a direction to look.  I recall our company having a similar issue when processing returns (RMA’s).  The sales price would be the current one instead of what was on the original sales order.  We fixed this by using marking, so that the RMA was “Marked” to the original sales order so that the price would be driven from that order and not the current price.  
I don’t recall where this setup is for that but hopefully some googling on marking return orders will lead you in the right direction.

——————————
Daniel Walter
IT Project Manager
New Sunshine LLC
Indianapolis IN
——————————
——————————————-

[Tony Zeigler]

?Download this white paper from Microsoft – it goes over when/how the prices are overridden. There is some config, and there is some training in how your sales staff responds to pop-up’s from the system. Also, you’ll need to understand what the source setting is on the lines that are changing. Ie., was the price created from an interface, copied from another order, input manually, etc. This impacts the config the controls the pop-ups.

Trade Agreement Evaluation Policies (White paper)

Microsoft		remove preview
Trade Agreement Evaluation Policies (White paper) This white paper explains implementation considerations for the Trade agreement evaluation (TAE) policies in Microsoft Dynamics AX 2012. TAE policies are used in the context of purchase orders, sales orders, and sales quotations. The policies prevent the system from accidentally evaluating and overwriting information in price and discount fields that is entered manually or by an external source. View this on Microsoft >

——————————
Tony Zeigler
Senior Consultant
Strategic Solutions NW, LLC
Beaverton OR
——————————
——————————————-