cancel
Showing results for 
Search instead for 
Did you mean: 

Jurisdiction code could not be determined ?

Former Member
0 Kudos
3,840

Hi,

I am Using the EBP4.0 classic scenario. when i tried to create the SC with particular plant in ITS then it is givng error message like "Jurisdiction code could not be determined ". But in R/3 this error message is not coming.

The error messages only getting for particular plants only not all the plants.

Can any one help in this..

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

my self

Former Member
0 Kudos

Can anyone help me on this.We are facing only one plant.

Thanks & Regards,

Prashanth P.

Former Member
0 Kudos

Hi

You need to maintain the Tax jurisdiction codes in R3 and SRM.

Check in R3: SPRO-Financial Accounting-tax on sales and purchases-basic settings-define tax jurisdictions.

I think, this has to be assigned to plants when you define them.

Same tax jurisdiction codes has to exist in SRM as well.

Check in SRM: SPRO-cross application components-SAP business partner-business partner-basic settings-tax jurisdictions-define structure of tax jurisdiction codes.

Once you define this, you should be able to create SC, I suppose.

Rgds

Reddy

Former Member
0 Kudos

Hi,

Thanks for your response. There are TAx jusrisaiction maintained in R/3. But there is no TAX jurisdiction in SRM.

We are using VERTEX for tax caluclation.

Can u please help on this...

Former Member
0 Kudos

Hi

I didnt worked with external tax systems, but check the foll settings in SRM:

1. You should have defined the RFC destination for the vertex in the path:SPRO-cross application components-SAP business partner-business parnter-basic settings-tax jurisdictions-using non SAP software-define RFC

2.SPRO-cross application components-SAP business partner-business parnter-basic settings-tax jurisdictions-using non SAP software-assign RFC destination to the country.

In this you need to maintain the mapping for your R3 Tax jurisdiction code to the vertex tax system. <b>For more help, read the activity documentation.</b>

Hope this might help you.

Rgds

Reddy

Former Member
0 Kudos

Hi,

Since you are using classic senario, I suggest that you turn off tax calculation in SRM and do that in R/3 at the time of PO creation.

J Rathinam

Former Member
0 Kudos

Hey John,

Just curious, what should one do if one is getting the same Jurisdiction code could not be dtermined in extended classic scenario. Currently the Vertex is connected to R/3. As soon as the tax code is passed to R/3 along with teh PO, teh vertex system is called to calculate teh tax. The config settings as of now is Tax is calculated at the backend and a default tax code is maintained. Am I missing something? As of now teh shopping is throwing the Jurisdiction Code error. Please advice