Sales price master updation

[former_member534382]

Dear All:

When the sales order creation, the sales price can't be updated from condition master automaticlly, need to click the uodate price to carry out.

The condition table include Sales.ord/Sold-to customer/Material/Usage(VBAP-VKAUS) . I guess this is related to the filed 'Usage'.

Is there any solution for this?

Thanks.

Stephen

[VeselinaPeykova · Accepted solution]

If I understood you correctly, this is what you do when you create an order: you enter the customer, then materials, after that you change the usage at item level.

On the other hand, if you do the steps in the following sequence: enter customer, set usage at header level, enter materials then the condition is determined, but that is of no use for you, because you need VKAUS at item level only and you may have different values for usage for the items in the document.

I made a test in a sandbox with a brand new condition table, access sequence, condition type, condition record, I created the document after all master data was correctly configured and the behavior is as you described - a change of VKAUS does not trigger automatically pricing condition redetermination for existing items.

I do not know for certain what is the intended behavior of VKAUS in order pricing - at least I could not find a SAP note describing this in more detail. The only one that I found was that for existing items ABRVW is not transferred to VKAUS for existing items, but my understanding is that this is a different case that is not relevant for your scenario.

Other than manual repricing that you already use, the only other workaround that I could think of was adding a bit of code in MV45AFZB userexit_new_pricing_vbap (for test purposes), which is most likely the worst way to approach the problem.

If you manage to find at a later time some note or other official source describing how VKAUS should behave in pricing, please post an update - I will be interested in reading it.

[former_member534382]

Some coding in userexit MV45AFZB resolve this problem,thanks.

[Lakshmipathi]

You still have not answered to my question why Usage is being used when the most specific material code is used. Normally, system would trigger the said error message in the following cases:-

1. Pricing was carried out again
2. Condition record is deleted manually
3. Condition record is created later

For more detailed information on Pricing works in SD, have a look at OSS note 24832

[Lakshmipathi]

Did you check in the Analysis tab where you can see the reason for this ? Moreover, when the price is maintained for material itself which is most specific, what is the need to have Usage ?

[former_member534382]

Yes, I check the Aanlysis tab,the condition recored exist, but has not been set in the document