Posting details could not be determined

Hi Experts
I got this error when i was trying to post payment Advice automatically.
Can you let me know what was missing in the configuration.
Posting details not found (entry AOLI 1 )
Message no. F8106
Diagnosis
No posting details could be determined for the specified account determination keys.
During determination of the posting details, a step by step masking of the account determination keys is carried out with unsuccessful attempts, providing this is possible. The values AOLI 1 specified here correspond to those of the last read attempt.
Procedure
Check whether a posting details is specified for masked account determination keys ("+").
Thanks
Rajanikanth.

Hi Rajanikanth,
Please, check the customizing in the transaction OPID.
Regards,
Paulo

Similar Messages

Error while J1INCHLN - Business Place for document could not be determined

Dear All Experts,
I am getting below error while running J1INCHLN Business Place for document could not be determined. For updating Business Place & Section Code I am running J1INPP Update Business Place information in FI document.
So I am getting error Document is incomplete.
Further I decided to update this in BSEG manually from SE16N. I am getting two errors :
1 ) Entry XX does not exist in T059Q ( Check Entry)
2 ) Entry C1 does not exist in T059Q ( Check Entry)
I have posted TDS to with these Tax Codes and same maintained in Vendor Master as well. But I am not getting these entries IN T059Q.
I got way to maintain via View Maintainence. But I would like to know the significance of these details.
Experts guidance will be helpful.
Regards,
Revati Joshi.

Dear Expert,
You might have not maintained a number range intervals for Remittance Challan for current year,
Step-1:
It is in Path: F.A(New) -- F.A.G.S(New) -- Withholding Tax --- Extended Withholding Tax --- Posting --- India --- Remittance Challans --- Maintain Number Groups -- Provide your company code, Section Code, Official W/H Tax Key and Number Group - 001
Step-2:
It is in Path: F.A(New) -- F.A.G.S(New) -- Withholding Tax --- Extended Withholding Tax --- Posting --- India --- Remittance Challans --- Assign Number Ranges to Number Groups --- Provide Number Group - 001 and Internal Number Range - 01
Step-3:
It is in Path: F.A(New) -- F.A.G.S(New) -- Withholding Tax --- Extended Withholding Tax --- Posting --- India --- Remittance Challans ---Maintain Number Ranges --- Select Maintain Groups button and select the 001 Check box and menu -- interval -- maintain and provide company code, and then select insert interval button and provide Calendar Year and Intervals
after configuring this steps, try posting the documents by entering business place and section code in the accounting document and Create Remittance Challan in T-Code: J1INCHLC - Create Remittance Challan and next for Bank Challan T-Code: J1INBANK - Enter Bank Challan and next for printing Withholding Tax Certificate T-Code: J1INCCERT - Print
Try this steps.. it will met your requirement..
Regards,
GOPI KRISHNA YANDRA
SAP FI/CO CONSULTANT

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

Withholding tax -number could not be determined for numbering group ID0017

While positing the FB60 transaction with withholding tax for country Indonesia, the below error is coming:
A number could not be determined for numbering group ID0017
Message no. 7Q630
"The system could not determine a certificate number for the numbering
group.
Withholding tax types exist that are relevant to numbering. The system
cannot determine a certificate number because the Customizing settings
are incomplete.
Sysem Response
Payment cannot be made.
Procedure
Check the number ranges in the numbering group."
Already seen the wothholding tax number range and it is coorec. Please advise how to resolve.

Dear,
Please check whether you have assigned the number range to the number group in the below setting
Spro
Financial Account Global Setting> Withholding Tax> Extended Withholding Tax> Posting> India> Remittance Challan> Assign Number Range to Number Groups

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

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

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

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

BDC Error - Codepage could not be determined

Hello Gurus,
We are having a problem with BDC in transaction VF01.
The return message is FES-025 "Codepage could not be determined".
First of all the details and what have been done so far:
- The funcion module with BDC is called by an EDI message that is send on the creation of the SD Invoice.
- In Online mode, no errors are raised;
- The errors are only raised when the program runs in background - Manual processing of EDI message via T-Code WE19 (online mode) runs with no problems;
- In DEV enviroment, everything runs smoothly (both online and background modes) and we achieve the required result;
- In QAS enviroment, with exacly the same versions of code, the background process fails;
- Both DEV and QAS work on the same physical machine, on different instances.
I've searched quite a lot about this error and most results talk about the usage/call of GUI_UPLOAD or GUI_DOWNLOAD. We are NOT using this type of funcions in our code (or something that would connect to the client).
Any ideias?
Thanks in advance, best regards,
João Argêncio

Some additional informations:
- The sistem is non-unicode;
- The EDI message source and destination are the same machine (inter-company process);
- The user assiciated in IDoc Config has SAP_ALL privileges;
- Both systems are in the same release levels (ECC 5);
- All IDoc configuration is equal in both DEV and QAS instances.
If you need any additional information just let me know.
Thanks oin advance, best regards,
João Argêncio

Business Place for document could not be determined

Hi,
When I am posting Remittance challan I am getting this following error,
"Business Place for document could not be determined".
Could any body please help me to solve this problem.
I maintained the following settings in system
1. T-Code: J_1IEWTNUMGR
UN04 SC04 194C 02
2. T-Code: J_1IEWTNUM
02 02
3. T-Code: J_1IEWTNO
Maintained Number ranges
I posted vendor document and I gave Business place and Section code also. Even After all the settings I am getting this problem. Please let me know is there any steps I missed are any thing I have to maintain in system.
Best Regards
Raj

Hi Pavan,
Thanks for you replay. I checked in table, data available in the table J_1IEWTNUMGR against Company code, Business place and Off Key.
One more question is whether we need to give Business place or Section code while creating TDS challan using J1INCHLN. It will appear like "Business Place/Section Code" in the screen. If I select from drop down It is taking Section code. Is it possible to change the logic from Section code to Business place.
Thanks & Regards
Raju.

Additional account assignments could not be determined in inbound idoc

Hi Gurus,
Iam getting the error for inter company billiing idoc .
Direction         2     Inbox
Current status    51 --> Application document not posted
Basic type        INVOIC01
Extension         ZINVOIC2
Message type      INVOIC
Partner No.       I0107IC
Partn.Type        LI
Port              P12INTERCP
Error is : Item: 002 - additional account assignments could not be determined
                Message no. FD171
Please let me know where we can assign the additional account assignment for intercompany billing .
Thanks in advance
RameshG

Check Note 137686 - ALE_INVOIC01: Internal allocatn Customizing in FI
thanks
G. Lakshmipathi

Error in CRM WEB UI : Item category could not be determined.

Hi,
I am trying to create Service Confirmation. I got an error sayin for line item 20: Item category could not be determined. Conversion Factors are invalid.
Can you please tell me, when such type of error comes?
Do we need to check any configuration for this?
Thanks,
Sandeep

Hi Sandeep,
Such type of errors generally comes when the customizations are not maintained properly in the system. Every One Order transaction has a Transaction Type and one or more Item Categories associated to it. And in the Item Category determination you need to associate all the Item Categories and the Transaction Type.
In this case, it looks like the Item Category is not properly configured. And also the Item Category Determination is not happening properly.
The best way to trouble shoot this kind of error is to get in touch with the Functional Consultant who has configured the Transaction. Alternatively, you cal also have a look at the standard transactions which are delivered by SAP to have a feel of all the places where there might be potential errors.
You can check this in the IMG Customization. Refer to this link for a complete detail: [Business Transaction|http://help.sap.com/saphelp_crm70/helpdata/en/92/8269126d1547578aab640f097de32c/frameset.htm]
Hope this helps.
Thanks,
Samantak.

ITunes cannot sync apps to the iPhone because the apps installed on the iPhone could not be determined

There are dozens of reports on this bug on the forums, and not one of the suggestions worked for me. After reading slocks post at https://discussions.apple.com/message/17157627#17157627, I noticed that iTunes did indeed back up different apps each time I quit, restarted, and re-attempted sync, and that it always failed on the same one (USA Today in my case). I deleted USA Today from my phone, quit and restarted iTunes, and synced again. iTunes reinstalledUSA Today for some reason, but the sync completed then successfully, and all subsequent syncs also complete successfully. I then noticed that the App Store was promptimg me to update USA Today, which I did fully expecting that the update would cause the problem to recurr, but it did not. So it appears a corrupt app is causing this problem, and deleting the app from your phone may resolve it.
If you are getting this error, my suggestion is to watch during the sync, and note which application is being copied when the sync fails. Delete that app from your iPhone, and try to sync again. Please post the results here. Thanks!

For me app wasn't the problem, the problem was the app needed updating. I updated all in my iPhone, but that wasn't doing it. I followed what someone else did and updated my apps "in iTunes" and it was perfect!
W Buchanan
Re: iTunes cannot sync... apps installed on the iPhone could not be determined.
Nov 21, 2011 5:40 PM (in response to jp_ofarrell)
Confirmed!
I was getting the same error message. After reading your post, I updated all my apps in iTunes. Sync worked as normal after that. Now we'll have to see if this happens again when other apps are updated.

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

Posting details could not be determined

Similar Messages

Maybe you are looking for