VKM1 Triggers new price check on sales order

[Former Member]

When a user manually changes a pricing condition on a sales order and VMK1 is done at times the VKM1 will trigger a new price check like if doing 'Update' B - Carryout new pricing. So it changes the pricing condition back to its condition record value and does not use the manually changed value. It then shows in the SO change log as having been done via VKM1. What was done was the credit status on the order was changed from B to A using VKM1. Why would this trigger a new price check on the SO?

[Former Member]

Hi Sumanth,

Can you give more information where I would look to check if the "critical fields" control is activated?

[Shiva_Ram]

The critical fields can be seen in t.code OVA8.

You can also try to use Deviation % and Number of days fields in the same t.code and check the results.

Regards,

[Former Member]

Check if the "critical fields" control is activated or deactivated & then revert back.

Rgds

Sumanth.G