cancel
Showing results for 
Search instead for 
Did you mean: 

Tax Procedure- Plants Abroad- 2 legal Entities

Former Member
0 Kudos

Hi,

We have a company code (8001), sales org 8001, in the UK with Plant (1001) in DE with Plants Abroad functionality activated in SAP.

We also have one more legal entity in DE (8002), sales org 8002 with a Plant (1002) assigned to it in DE.

We are using tax procedure TAXDE where we created tax codes with different naming conventions for each company code.

Since the tax procedure is shared across the 2 company codes, how can we prevent one company code using the tax codes that belong to the other, when updating MWST condition records?

Eg:

When updating condition record in VK11 for MWST, the system is allowing the same tax code to be used for different companies:

Co code: 8001, sales org: 8001, country: DE, destination country: DE, valid from 01.01.2014, valid to: 31.12.9999, tax code X1

Co code: 8002, sales org: 8002, country: DE, destination country: DE, valid from 01.01.2014, valid to 31.12.9999, tax code X1 (should be Y1)

How to prevent updating X1 for company code 8002? Is there an alternative to use a different tax procedure?

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member198650
Active Contributor
0 Kudos

Hi Olga,

You have to define a validation for the tax code for specific co.code in GGB0.

Regards,

Mukthar

Former Member
0 Kudos

Hi Mukthar,

thanks for your reply. We had also considered that option but put it aside because the validation won't be called when we maintain VK11 or when the sales order is raised, but only when the financial postings are done. Is there something we're missing? At what level would the validation be done?

Thanks

Regards

former_member198650
Active Contributor
0 Kudos

Hi Olga,

You cannot restrict the tax code at company code level. However you cannot create separate tax procedure because both company codes are in same country. So there is only one option that is define validation at line item level and restrict it through FI level.

Regards,

Mukthar

Former Member
0 Kudos

Hi Mukthar,

yes you're right regarding the limitations we are facing.

Sorry for insisting on this point but would you know how to create the validation in a way that it would restrict the user when updating MWST condition records?

If I create it at FI line item level, no validation will be triggered before the creation of the invoice, meaning that MWST condition record update and sales orders creation could be wrong.

Thanks

Regards

Olga