cancel
Showing results for 
Search instead for 
Did you mean: 

Automatic Price update in sales order

pranay_suyash
Explorer
0 Kudos

Dear Experts,

When a user creates a sales order with suppose material 'A', the pricing is determined but then the user realizes the material needs to be changed and so they change the material in the order. Now, it shows prices have been redetermined but when in the item conditions page, they have to run the update button for updating the prices. The user wants that she does not have to do this manually and this change happen automatically before saving.

Kindly suggest a way so that after changing only the material, the prices get updated automatically without pressing the update button.

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

Former Member

Hello,

Try to check program MV45AFZB on the user exit:

  • USEREXIT_NEW_PRICING_VBAP

Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.


Hope to have helped.


Regards,

Daniel Zambrini

Answers (6)

Answers (6)

prateek_dhawan18
Participant
0 Kudos

You will have to code in MV45AFZB include. The routine to use would be userexit_new_pricing_vbap.

You need to compare *vbap-matnr with vbap-matnr.

If there is a change pass new_pricing = B

pranay_suyash
Explorer
0 Kudos

HI Everyone!!

Thanks for your help. The userexit modification as suggested by Daniel, worked. I maintained that if there is change in material, carry out a new pricing and it worked.

Thanks

pranay_suyash
Explorer
0 Kudos

Hi,

While checking the pricing after updating the material, i noticed that the pricing elements shown are for the previous material itself:

Updated material in SO:

Pricing elements for previous material:

I have also checked in the system and there is no custom development related to pricing. However, pricing routine '2' is maintained for ZPR0.

Thanks

0 Kudos

Were you able to find the root cause why pricing elements are for previous material.

VeselinaPeykova
Active Contributor
0 Kudos

Is this the same behavior for everybody, including you, or only some of the users are affected?

Does it occur for all order types? If you use ZOR as standard order in the company, check with OR/CS etc, try with document types that use different pricing procedures.

Does it happen also with a single order item and even the base price condition is not updated?

Could you please share some screenshots to illustrate the problem?

VA01->enter material+quantity (get screenshot)->show conditions tab for the item (screenshot) and header (screenshot).

Please do not add manual pricing conditions at header level.

VA02->change the material (get screenshot), press enter, close the popup->show conditions tab for the item (screenshot) and for the header (screenshot).

Then reprice with option B and show conditions tab for the item (screenshot) and the header (screenshot).

What happens if you create an order with material A, change the item to material B, save, exit VA02, re-enter VA02 - do you see the correct prices? The reason for asking is because this could be some visual bug as a result of a custom development.

If even after order save NETWR,CMPRE, MWSBP are not updated correctly (check VBAK and VBAP), then this is a very serious problem. Did you check your company's documentation on activated user exits, additional developments for SD?

pranay_suyash
Explorer
0 Kudos

Dear Veselina,

I have attached the screenshots from VA01 and VA02:

VA01:

Item condition:

Header:

VA02:

Item: The value is still the same.

Header:

Condition value after using update button at item level: The value of ZPRO has changed after updating through the update button through option C but not through B although no manual entry has been done.

Kindly suggest what am i missing?

Thanks & Regards,

Pranay

VeselinaPeykova
Active Contributor
0 Kudos

Did you also try:


What happens if you create an order with material A, change the item to material B, save, exit VA02, re-enter VA02 - do you see the correct prices? The reason for asking is because this could be some visual bug as a result of a custom development.

From your screenshots I can see that this statistical condition is somehow tied to a non-statistical one, which influences NETWR, so if NETWR is not automatically updated after order save (without manual repricing), then this is indeed a very serious problem and can be abused by users.

Check the setup in your pricing procedure, transaction PRCAT can also help you in the investigation.

There is a functionality to postpone updates of header/group conditions during order entry to increase performance, but I think it was for CRM, not for ERP.

Please, somebody correct me if I am wrong about that (I don't have system access with a recent EhP at the moment).

I do not experience such behavior in my IDES sandbox (I don't have there custom logic related to pricing), so I still suspect some not very well thought out custom development. Check the VOFM routines, check the exits, ask a colleague developer to assist you if you are not comfortable with reading ABAP code.

former_member218017
Participant
0 Kudos

Why don´t you add this "changed" material into a new line, so the pricing will be carried out for this material.

Lakshmipathi
Active Contributor
0 Kudos

Have you tried hitting enter key in sale order after changing the material code?

G. Lakshmipathi

pranay_suyash
Explorer
0 Kudos

Hi,

After I change the material, i press enter and get new pricing carried out, but when i go and check the conditions, it is the same unless i press the update button.

Please suggest.

Thanks

Lakshmipathi
Active Contributor
0 Kudos

Automatic pricing updation will happen if your copy control Pricing Type is set to "B".  But here, you also need to take into consideration the fact that if you want to fetch a price from sale order and if your pricing condition record have a different price, then in that case, system will ONLY read the condition record and not the sale order price.

G. Lakshmipathi