Error during SC creation - Jurisdiction code could not be determined

Hi All,
For testing purpose , I have set up one user id. While creating SC with that ID, I am getting one error, it says "Jurisdiction code could not be determined ".
Plant , company code everything enetred in the SC is perfect.
On another hand, I can create SC with my id without any error..
Attibutes are identical of both the user ids.
Can someone help me to know the reason for this particular case
Regards,
Sheetal

Hi
Jurisdiction code is determined based on Ship to Address data of the shopping cart and the country code. Pl check if the ship to address in the shopping cart is correct. It might be missing mandatory informations like Postal code, city, District.
Regards,
Sanjeev

Similar Messages

Error "Jurisdiction code could not be determined" in so create bapi

I am using the bapi "SO_NEW_DOCUMENT_ATT_SEND_API1" for creating the sales order,
it gives the error "Jurisdiction code could not be determined" Sometimes there are two juridiction code maintained in the system .
1) During the ship to party address change at sales order , city , country and postal code fields determine the Juridiction codes. Sometimes there are two juridiction code maintained in the system for one city and in such cases BAPI fails to create an order.
2)When the ship to party is foreign country then we do not need Juridiction code in sales order. In such cases also the BAPI fails to create sales orders and writes an error log , saying juridition code could not be determined.
Proposed Soltuion.
We have to modify the BAPI to force the values of ship to address as it is from the text file without exiting the sales order creation.
Thank You,
Ganesh

hi ,
u need to give the right postal address. If it is then it won't give the warning message.
Regards,
Rose.

Po check error (Jurisdiction code could not be determined)

Hello everybody.
I am in SRM 5.0 and in Brazil we use jurisdiction code too, all notes for jurisdiction codes are applied and the calculation is occurring in R/3 in the moment of Po creations, the problem is that when the po are created and I need to display and check the PO the system displays an error message " JURISDICTION CODE COULD NOT BE DETERMINED" and aproval can't be done too.
Someone that uses jurisdiction code knows what could be done to solve.
Thanks
Nilson

Hi
Please go through the following links ->
Jurisdiction code could not be determined - ECS
Re: Jurisdiction code could not be determined ?
Re: Tax jurisdiction in R/3
Jurisdiction code could not be determined
SUS - Jurisdiction Code not determined
Re: Tax code T1 does not exist for jurisdiction code error in shopping basket
Re: You are not allowed to enter a tax jurisdiction code for country US msg
Re: Tax Jurisdiction Error in SRM
Tax error while posting an invoice in SRM
Tax setting in Extended Classic Scenario
You are not allowed to enter a tax jurisdiction code for country US
Hope this will help.
Regards
- Atul

Unable to create shopping cart - Jurisdiction code could not be determined

Hi,
I've found several threads here asking about tax jurisdiction code but none of them seem to solve my problem.
When we create shopping carts for our north american back end R/3 system we cannot save them because of an error with the jurisdiction code "Jurisdiction code could not be determined ". Our ship-to address is correctly maintained with the city, country, post code, etc. I have tried maintaining the jurisdiction code on our organisational business partner but this makes no difference. For info, we use Taxware to create the jurisdiction code in the back end.
We looked at applying oss note 436760 but apparently this note is only valid for SAP Basis Component 4.6 and 6.1 but we are on 7.00. Do you think it is necessary for us to implement a BADI?
Thanks in advance for any help.
Roo

Hi All,
Please see my answer to similar concern raised in the thread:
[BAdI BBP_CATALOG_TRANSFER - Material Group Mapping issue;
Your question is that initially it was working with Jurisdiction code and now not? Why?
Because, the backend system is either connected to the third party Tax engine such as Taxware, and doing so, some of the addresses (Country, Region, City and Pin Code combination) may have more than one Jurisdiction code, in such cases, SRM gets confused of which code to select, and hence the error.
Use the BAdI and get going!
Thanks for reading!
Ashok Kawa

Company code could not be determined for IDoc #.......

I was trying to generate an IDoc manually by using the tcode WE19. I have manually keyed the data in to the respective segments for the basic type PEXR2002 and message type REMADV. After this while processing, the IDoc is getting generated, but not posted OK. I am getting the following two error messages 51 stating:
'Company code could not be determined for the IDoc #....'
'Customer/vendor could not be determined for the IDoc #.'
Can any one give some inputs on this issue?
Shaji
Message was edited by: Shaji Thomas

Hi Shaji,
You may look at the OSS note 316811.
Thanks
Vinod

Error during EA16manual billing ' AH632 - Tax code could not be determined'

Hi,
During manual billing t code EA16, we are getting following error.
'Tax code could not be determined'
Actually there is no tax code given in configuration for the subtransaction which I am using for manual billing. Whether anyone has any clue?
Regards,
Jayant

Hello,
2 reasons
1. Check any where in the Bill/Invoice you have selected tax code <either directly or indirectly>
2.Assuming that Tax code is mandatory, why do not you assign a 0% tax code <either A0 or V0> in EK02?
Hope this helps
Rgds
Rajendra

Shopping cart error--Tax code could not be determined

We are using classic extended scenario.
When i am trying to create a shopping cart i am getting two error messages " tax code could not be determined" and Not possible to calculate tax.
have checked in the SPRO in EBP System->
Tax calculation->Determine system for tax calculation which is set to R/3.
SPRO->Tax calculation->Enter tax code -V0 -zero rate
 V1-VAT 17.5
 V3-Non recoverable.
SPRO->Determine tax code for country/product category->Domestic -GB -P146-V0
SPRO->Determine tax code for country/product category->International -GB -P146-V1.
I have checked the transaction FXTP in R/3-
Procedure attache to this is TAXGB.
Could you please suggest me how to eliminate the error.
Points will be rewarded.
Edited by: imam uddin on Jul 18, 2008 2:48 PM

Hi
It's recommended to have the same Tax related configuration data replicated in SRM system from R/3 as well.
I don't recommeded you to go with Hard-coding of tax codes.
We have faced similar issues with Delivery address and we have to solve it using our custom logic inside the BBP_DOC_CHANGE_BADI and BBP_CREATE_PO_BACK BADIs.
Anyways, send the detailed business requirements to my mail which are already having with you. )
I will definitely help you out.
Please refer to following threads as well.
sales tax gurus
How to display country related tax codes in SRM
e-Invoice tax calculation.
Tax code T1 does not exist for jurisdiction code error in shopping basket
Drill down facility not working for Tax codes ....Urgent!!!!!
Tax Issue
Tax Calculation
Tax setting in Extended Classic Scenario
Withholding Tax in SRM5.0
IDOCS for Tax Information
Taxes in Bid Invitation
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

PY error message - EE's salary group could not be determined for Plan Life

We are running through Payroll errors when there is a Separation action being carried :
u201DEmployeeu2019s salary group could not be determined for plan LIFEu201D.
On IT0168 the costs are u20180u2019
This has to be resolved ASAP. Any inputs/ advise is greatly appreciated.

During the "Separation" action, does the employee change WT on IT0008?
If so, it could be that the Life Plan's Calculation Base does not include that WT (and check the IMG under Payroll > Benefits Integration > Define WageTypes for Benefit Plans)

Error message while CREATING PO - PGrp could not be determined

Hi all,,.
We are on SRm 7. ECS.
The issue we are facing is:
WHen I click on CREATE PURCAHSE ORDER trasnaction,I get this message "Purcahsing group could not be determined;Inform system administrator".
Edited by: nmsrm1234 on Nov 10, 2011 2:09 AM

Hello,
The error is coming because to create PO directly you have to be a Purchaser,you need to belong to a purchasing group in SRM.In PPOMA_BBP Assign your user id below a purchasing group directly or right click the present position and go to 'Assignment-->Purchaser Assignment', select a purchasing group and save.
Then Try creating now a purchaser order directly .
Regards,
Neelima

Error message: the appropriate pricing procedure could not be determined

Hi SAP friends,
What does this error message means please?
The appropriate pricing procedure could not be determined because no entry with keys 'M100 20 P1' 'A' '1' exists in table 683V.
Tcode: VA01 (sales order).
Regards,
Bahia.

Hi Bahia,
This error means the pricing procedure has not been done.To assign your pricing procedure to sales area go to the transaction "OVKK" and specify sales org/dist channel/div/document pricing procedure/customer pricing procedure and the defualt condition type. This would solve your problem.
Regards
Ram Pedarla

Error during the creation of a delivery note

Hi,
While creating the delivery, an error is produced when i saw the log . It was as follows
"An Item with no delivery quantity is not permitted. Item will be deleted"
The material is unrestricted, not reserved for any other orders except my PO .
any idea about this error?
Thanks and regards

Hi. The issue was solved. It was related with an incorrect value in the material master record (availability check field).
Thanks and regards

Customer/vendor could not be determined for IDOC

Hi all,
Am trying to post incoming payments through EDI ..
IDOC Information
IDOC type: PEXR2002
Message type: REMADV
Function Module: IDOC_INPUT_REMADV
Process code: REMA
Am getting these 2 errors :
Customer/vendor could not be determined for intermediate document
Company code could not be determined for intermediate document
Has anyone encountered this problem, if yes can anyone suggest the solutions, any help regarding this is highly appreciated.
Thanks.

Hi,
Currently I am facing with the same type error when trying to post incoming payments through EDI.
IDOC Information
IDOC type: PEXR2002
Message type: REMADV
Function Module: IDOC_INPUT_REMADV
Process code: REMA
I am getting the below error:
1. Company code could not be determined for intermediate document
I have maintained record records for partner type and partner number in OBCA.
Please advice what are the other configuration changes do I need to maintain.
Your assistance would be highly appreciated.
Thanks.
Edited by: Victor Collins on Feb 27, 2009 9:31 PM

SRM 5.0 - Tax could not be determined.

Hello Team,
We are using classic scenario SRM 5.0. The issue is while creating SC in EBP for foreing vendors we are getting error tax code could not be determined ? For the domestic vendor this is working fine.
As per customization all tax calculation is occuring in backend.
Request your helpful hint on this.
With Regards,

Hello,
Take a look at:
IMG: ->SRM Server ->Cross-Application Basic Settings
      ->Tax Calculation
      ->Determine Tax Code for Country/Product Category
In the IMG documentation the following is stressed:
- If you set up a product category, you also have to enter a country.
- If you leave the "Country" field empty, you cannot specify a Category ID"
Also, in
IMG: ->SRM Server ->Cross-Application Basic Settings
        ->Tax Calculation ->Determine System for Tax Calculation
If for example, tax calculation takes place in R/3 'Tax Calculation Occurs in R/3' should be selected.
- If you created another international entry for country XX, for example, be aware that a corresponding entry must also exist in R/3 Backend, otherwise the mapped tax code can not be found and field tax code remains blank in the shop transaction.
In the customizing entry for determine tax code for country/Product category, remove the '*' and replace with just a space to assign a tax code for all product categories.
I hope this helps.
Kind regards,
Ricardo

Screen sequence number could not be determined

Hi, All,
After client copy, I ran MM03, but got an error as below:
screen sequence number could not be determined.
How to solve it?

You need an ABAPER to debug the issue. Also check the logs for more details
Regards
Juan

Error: "Transaction type could not be determined" during PO Creation fromSC

Hi all,
I'm working on SRM 5.5 with ECS.
During the creation of a PO I want to add a SC as an item of PO.
But when I chose the SC and click on the button Add to PO I recive the error:
Transaction type could not be determined
In the organizational unit I set the attribute BSA and DP_PROCT_TY.
there are other steps I have to do to join the transaction type of SC and PO?
rgs
enzo

Hi Enzo,
First check if the attribute BSA and DP_PROC_TY have the same value.
Then in the attribute value for BSA, change the source system for the document type to your SRM system.
Create a new PO and a shopping cart.
Try changing the PO by adding the shopping cart
Hopefully your problem may get resolved.
Thanks
Sanjeev

Error during SC creation - Jurisdiction code could not be determined

Similar Messages

Maybe you are looking for