Issue with Material tax indicator in Sale order creation

[sreenivas_reddy]

Dear Experts,

My complete vat setup is working fine and deriving tax indicators/ rates correctly, but when I create sale order for X customer and with Y Material combination the condition type MWST missing due to Material tax indicator not derived automatically.

The interesting part is X customer works fine with all other materials and Y material works with other customers.

Only X and Y combination not working... badly required some expertise help here.

[sez41]

Is the field VBAP-TAXM1 not empty in database? If it is not empty, check form USEREXIT_PRICING_PREPARE_TKOMP in include MV45AFZZ to see whether something funny is over there. Debugging this user exit with two different scenarios in parallel (the one where everything's fine and the one where it's not) would be my final suggestion.

[sreenivas_reddy]

Yes Kivanc, the field is empty in VBAP-TAXM1..

[jpfriends079]

Which VBAP-TAXMx did you see this?

Means whether that is TAXM2 / TAXM3 / TAXM4 / TAXM5?

If none of that is populated, then as suggested by our Community Members take help of ABAP Team and Debug the reason.

Thanks,
JP

[jpfriends079]

This was a widely discussed topic earlier.
Can you share screenshot for Tcode OVK4 - Material Tax classification config?

In meantime, refer my post in the following:

> Difference in customer tax classification and material tax classification
> Tax Classification Issue

Even the SAP Note 872449 - Tax determination in Sales and Distribution .

Thanks,
JP

[sreenivas_reddy]

I verified the previous discussion shared by you but nothing is relevant for me. I am sharing screenshot for OVK4 and am using only classification 2 for all materials.

Please note that all my customers and materials are working fine with tax classifications except X and Y combination..

[sreenivas_reddy]

This is not a new field, same field using for all materials. As I said before its working fine with other combinations, only the issue is X and Y combination.

[tao_sun2]

Hi, thanks for the screenshot. I don't have more idea why taxm1 is missing in specific case. What I can do in this case is to debug how tkomp-taxm1 determined. Normally, during sales order creation, taxm1 will be passed from table MAEPV to VBAP, then to TKOMP. If tkomp-taxm1 is correctly filled with '2', then you can continue watch where it is removed. For example is there any custom logic in USEREXIT_PRICING_PREPARE_TKOMP(MV45AFZZ).

[tao_sun2]

Hi, please refer to SAP KBA 1456169. If this field is newly defined, you need to pass value to it with user-exit USEREXIT_PRICING_PREPARE_TKOMK or USEREXIT_PRICING_PREPARE_TKOMP in include MV45AFZZ. In standard, system will not pass value to it directly, that is why you see a yellow exclamation mark.

[JL23]

Wouldn't it make sense to share a screenshot from your material which shows that the tax classification is properly maintained?