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

Similar Messages

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

Getting an error "Customer could not be determined" for IDOCs in SCM 7.0

Hi Friends,
I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
I have noticed that 2 things .
1. E1ADRE1 field is NOT being sent by the ECC system .
2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
Has anybody faced this problem before ?
I look forward to replies.
Detailed error is given below.
Regards,
Ranjini.
Customer could not be determined
Message no. /SAPAPO/EDI010
Diagnosis
The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
The section was not available in the processed IDoc.
System Response
The system cancels processing.
Procedure
Configure the EDI convertor in such a way that the corresponding section has a value.

Hi Ranjini,
Please look into the following
1) Customer master data is fully maintained
2) Customer number ranges are fully defined in customisation
3) Customer address details are maintained
4) Is there any special characters used while defining customer data or customer
number like $, #,[ etc.,?
5) Customer int models are active in SCM side prior to IDOC processing (including
customer, demand, stocks etc)
Please confirm your findings
Regards
R. Senthil Mareeswaran.

Report RSMIPROACT gives Customer could not be determined for IDOCs

Hi Friends,
I am executing the report RSMIPROACT in ECC 6.0 system to publish Demand and Stocks into the SCM 7.0 system.
The IDOC is processed without any errors in ECC 6.0 . However, in the SCM 7.0 system , the IDOC fails with the error.
I have noticed that 2 things .
1. E1ADRE1 field is NOT being sent by the ECC system .
2. I get the same error even if I manually add this field and add value 300 or 301 for the qualifier field.
Has anybody faced this problem before ?
I look forward to replies.
Detailed error is given below.
Regards,
Ranjini.
Customer could not be determined
Message no. /SAPAPO/EDI010
Diagnosis
The system must determine the customer number from the IDoc data in order to update stock and sales figures for customers. It uses the additional section E1ADRE1 with the qualifier '300' or '301' in the vendor address section to do this. The customer number stored here should have a valid customer number in the APO System.
The section was not available in the processed IDoc.
System Response
The system cancels processing.
Procedure
Configure the EDI convertor in such a way that the corresponding section has a value.

Hi,
i'm facing the same problem. Could you solve it?
Regards

IDoc type could not be determined for the IDoc

I am trying to Post the payment run through the transaction F110.
In the payment run log i get the following message:
"IDoc type could not be determined for the IDoc"
But in fact the IDoc is generated and it is displayed in We05.
I have configured the Message type PAYEXT-PEXR2002 and EUPEXR-IDCREF01 both for the partner.
Has anybody Idea about why this error is coming and how i can resolve this?
This is important because in Payment run log, they need to know the IDoc number generated for that run, else it may become difficult for user to identify which IDoc was created for a particular payment run.
Would appreciate if anyone can please help on the same.
Thanks & Regards,
Narayanan

Hi,
If you are paying the payment through F110, if the payment exceeds the limit what you are spefied in available amounts in FI12 screen. First Please check this screen.
still if you are having any problem
Check in the below path:
IMG- Financial Accounting (New) - Accounts Receivable and Accounts Payable - Business Transactions - Release for Payment - 1. Create Workflow Variant for Release for Payment
2. Assign Release Approval Procedure for Release for Payment
3. Define Users with Authorization to Payment Release
Thanks
Chandra

IDoc type could not be determined for the IDoc in F110

Dear All,
The below mentioned error is encountered by us in F110.We have check all the setiing and not able to find the solution for this error.
Now our heads has gone for a toss....can anyone kindly suggest what and where we have missed out.
The system is not creating the IDOC file.....
IDoc type could not be determined for the IDoc
Message no. B1090
Diagnosis
The IDoc passed to the ALE layer could not be processed. The specifications passed in the control record were not correct.
The basic IDoc type (field EDIDC-IDOCTP on the outbound side or EDI_DC-IDOCTYP on the inbound side)has not been specified for this IDoc.
The attempt to read the basic IDoc type from table EDIDO also failed. No table entry was found for IDoc type from field DOCTYP.
Procedure
Possible error sources:
- The calling program did not provide values for the fields specified above correctly. Make a note of the transaction in which this error occurred and consult your ALE administrator.
- The IDoc type is not known in your system and must be maintained.
Kindly do the needful.
Regards

If you want to create IDocs from the proposal run, outbound parameters (we20) with the 'Test' flag are required in addition.
see OSS note 504230 : Message EUPEXR forms the logical unit around the individual payment messages (PAYEXT IDocs). The E1IDRD1 segments contain the IDoc numbers of the payment messages in field DOCNUM. Segment E1IDRS1 contains check sums (total of all amounts, account numbers, bank numbers, number of payment messages). This information is provided for the EDI subsystem. Set up EUPEXR In Transaction WE20 for the partner profile for the house bank, create the outbound parameters for message type EUPEXR with IDoc type IDCREF01. If you want to create IDocs from the proposal run, outbound parameters with the 'Test' flag are required in addition.

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

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

Error "codepage could not be determined for the receiver-system"

Hi,
we use the idoc-adapter to send message from mySAP ERP to PI.
All worked fine.
So, this morning I have changed the datatype of the messageId from "char" to "int" in mySAP ERP in the customizing menue (install param). So, no message received in SAP PI.
When I start transction "we05" in mySAPERP" I get the following error:
"codepage could not be determined for the receiver-system" status 02.
I have changed the datatyp to "char" but the same probleme
Can anybody help me please?
Regards
Stefan

This error shouldn't occur unless there is some modification at the OS level codepages.
Please check the entried in the RFC destination for connecting to the XI system. Unicode settings.
Regards,
Prateek

Customer/vendor could not be determined for intermediate document

does any one know how to solve this problem, i got this error for an inbound idoc 820 (remmitance advice).

Hi rob,
Message no. FD017
This is the following message:
Customer/vendor could not be determined for intermediate document 0000000000047039
Message no. FD017
Diagnosis
Several procedures are defined for determining the partner (customer or vendor):
1. The customer/vendor can send his/her account number (the account
   number in our system) in the address segment.
2. The customer/vendor can send his/her account number (our number at
   the customer or vendor) in the address segment.
3. Only the name in the address segment clearly identifies the
   customer/vendor. In this case you can create an allocation within
   intermediate document customizing (IDoc base -> Control -> Forward
   inbound).
4. The customer/vendor is determined using his/her bank details (only
   for the "INVOIC01" intermediate document type).
5. The customer/vendor is taken from the control record of the
   intermediate document.
For 1.-3.: One of the address segments with the partner functions
           "II", "RS", "SU", 'SE' ("INV_ID01"), or "RS" or
           "LF" ("INVOIC01") is used for determining the
           customer/vendor.
Procedure
Create the customer or vendor within Financial Accounting or maintain his/her bank details.
Create customer         - Proceed
Customer bank details   - Proceed
Create vendor           - Proceed
Vendor bank details     - Proceed
If the customer/vendor can only be determined using his/her name, create a record within intermediate document customizing with
logical address = name, application = "FI" or "MM" and physical target in the SAP system = customer number/vendor number.
Proceed

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

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.

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

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

Company code is not set up for electronic tax return

hi dear
what is the configuration of e-return salea/purchase .
The system cannot execute the taxes on sales/purchases settlement within electronic communication with authorities.
when i excute F.12 then message coming Company code is not set up for electronic tax return
please guide me.
regards
purushottam
Regards

Hi,
if you start report via SE38. program name RFUMSV00 you can read the program documentation. In here it states what is needed:
...In addition, the report provides data for the electronic advance return
for tax on sales/purchases. The administration report for electronic tax
returns (FOT_B2A_ADMIN) then directly sends the return to your relevant
tax authority.
To use the electronic advance return for tax on sales/purchases, make
the necessary settings in the screen area Posting Parameters under
Electronic Advance Tax Return.
For more information, see the SAP Library under Financials -> Financial
Accounting (FI) -> Financial Accounting General Topics -> Taxes
(FI-AP/AR) -> Taxes on Sales/Purchases, Sales Taxes, and Additional
Taxes -> Electronic Advance Return for Tax on Sales/Purchases.
Hope this gives you a beginning.
Hein

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

Similar Messages

Maybe you are looking for