Tax condition type is missing when changing sales Order using BAPI_SALESORDER_CHANGE

[Former Member]

Hi Experts,

After adding one condition type and also change material using BAPI_SALESORDER_CHANGE
Tax condition is missing,but all the other condition types are in good shape.

And in SO EXIT, we set the pricing type to “G”
Does anyone meet this problem before?

[Former Member]

Hi Experts,

After adding one condition type and also change material using BAPI_SALESORDER_CHANGE
Tax condition is missing,but all the other condition types are in good shape.

And in SO EXIT, we set the pricing type to “G”
Does anyone meet this problem before?

[lenastodal]

Hi and welcome to the SAP Community!

Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend that you familiarize yourself with https://community.sap.com/resources/questions-and-answers (if you haven't already), as it provides tips for preparing questions that draw responses from our members. For example, you can outline what steps you took to find answers (and why they weren't helpful) and share screenshots of what you've seen/done. The more details you provide, the more likely it is that members will be able to assist you.
Should you wish, you can revise your question by selecting Actions, then Edit (although once someone answers your question, you'll lose the ability to edit the question -- but if that happens, you can leave more details in a comment).

Finally, if you're hoping to connect with readers, please consider adding a picture to your profile as it encourages readers to respond to you. Here's how you do it: https://www.youtube.com/watch?v=F5JdUbyjfMA&list=PLpQebylHrdh5s3gwy-h6RtymfDpoz3vDS.

Best,
Lena
SAP Community Moderator

[VeselinaPeykova]

You mentioned that you changed the material, and usually for determining the tax conditions you use the tax classification of the customer and the material.

As a first step - ask your functional SD colleague to verify that the new material is correctly maintained.

Then check the price determination analysis to find out why a condition is not determined. One common reason could be that a condition record is not maintained for the combination of the key fields that you use to determine the tax condition, or that you maintained a condition record, but not with the validity that the system expects.

There can be other reasons, too, most of which can be investigated via the pricing analysis - pricing requirement not fulfilled, or you use some z-fields that are not correctly updated when you modify the sales order

[Former Member]

Hi Veselina,Thanks for your reply, we checked that the new material is maintained correctly.

And for the pricing analysis, the checking result is below.

Condition Record Exists, But has not been set

The business background is a little bit complex, before calling BAPI to change sales order, in our program firstly we call BAPI to create material. After commit, we call BAPI to change sales order, so I bet if it’s due to the time difference.Or the method of the pricing type we set is not correct.

Thanks,

Jolina

[VeselinaPeykova]

jolinalu

in most cases where I have encountered this problem, the root cause turned out to be custom developments in SD pricing routines and exits.

Note 363212 - "Pricing analysis" mode of operation mentions why the message appears, in note 859876 - Condition is missing: Message VE 108 or VE 008 you can find some examples and places where you can start checking.

From your explanation it seems that you might have some z-fields in pricing, which are correctly determined only when you process the sales document in dialog mode, or you maybe update the value for some standard fields via an exit, but for whatever reason, the logic does not run correctly in the background. Use note 859876 as a starting point for analysis, if still no luck - there is an excellent debugging guide for SD pricing: Pricing Programs and their logic – Help for debugging. So far this guide has not failed me even once.

I find it unlikely that the time difference is causing this effect, but I suppose that you can rule this out by creating the material first (manually) and then executing the BAPI with the same parameters that you use in your program.

I am not really sure that it is correct from business perspective to redetermine only taxes when you change the material code - there may be some automatically determined conditions on material code level or on product hierarchy, and so on; the user may have entered a manual discount only because a specific material was used, or the 'old' material maybe participates in group condition calculation. Of course, this does not take into account your specific business process, it could be that using 'G' makes sense in the context of what you are doing. Still, the behavior of repricing in dialog and in background should be consistent and it is important to make it behave in the same way (even if you currently have discovered problems only with one tax condition).

[Former Member]

Hi Veselina,

Thanks for your reply,I will continue to investigate based on your recommendations,

LU.