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.

Similar Messages

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

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

Shipping data could not be determined for the material

hi all,
while creating STOs for i get a message that shipping data for the material canoot be determined for the material. the plants are maintained as customers. the shipping tab in item detail in STO order is not appearing. the shipping point is getting dertmined for sales orders from the same plant and material. am also able to ceate STOs between other pair of plants.
thnx in advance
saurabh
Message was edited by:
saurabh diwakar

Hi,
Shipping point is determined by "shipping conditions" + "loading group" + "plant".
Shipping conditions are fetched from customer master / or if maintained in the sales doument type they are fetched from there.
Loading group fetched from material master.
Plant fetched from CMIR / CMR / MMR.
You do the shipping point determination using the transaction code "OVL2" If SC or LG or PLANT are deviating from the entries in the customer or material master then also you will not get the shipping point.
Reward points if solution helps.
Regards,
Allabaqsh G. Patil

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: "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

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

Error Log: The Billing Type Could Not Be Determined

Hi Experts
I have to produce the credit note sebsequent to the return. But I am getting the "Error Log: 0084001006 0000 The billing type could not be determined". Kindly help me with the solutions
Thanks and Regards
M.Dheerendar Jain

Hi,
Please check copy control VTFL for delivery and billing type
go through the routine 350 (VAT Determination) whteher it is applied in ite category.
if yes, then you have to configure the VAT Invoice type determination.
also maintain the entries in below tables:-
J_1IDCLSDET & J_1IBILDET
Even if the above entries are already maintained then check the supplying and receiving plant entries
for the billing.
To maintain entries in table go to t-code SM30.
and put the above table in the "Table/View" it helps to determine FVAT Invoice types
Invoice types determined based on supplying and receiving plant.
Kinldy check and confirm.
Thanks & Regards,
Rahul Verulkar

"The Destination Directory Could Not Be Determined For Photo Delluxe 4.0"

I Downloaded Adobes Photoshop from thier Site.
When trying to install pdx401upus.exe,
it will open up the Installation Wizard and then I get the Following "Warning" Message....
"The Destination Directory Could Not Be Determined For Photo Delluxe 4.0"
it just gives me a box to check that says "OK", and then the Wizard Shuts down.
Im running an HP Computer with Windows 7, Tons of HD Space, Ram, Memory ect.
I love using Adobe Photoshop, but since I got this new computer,
my Adobe Photoshop install disc seemed to be too old (Windows 95),
and therefore would not load to my new Computer/Operating System.
Any pointers, Websites, Instructions would be greatly appreciated.
Although I'm not a "Computer Dummy" I know just enough to get me into trouble, so the simpler the instructions....the better.

I am sorry Wwotr but I have not observed a user who has successfully installed and used Photo Deluxe on Windows 7. Since Photo Deluxe we have released 10 versions of Photoshop Elements. I would recommend utilizing the trial of Photoshop Elements 10 and seeing if that will fullfill your needs. You can find more information at http://www.adobe.com/products/photoshop-elements.html.

Error:The grouping element could not be determined for project

Hi,
When I am trying to issue goods for a project,I am getting the following error
"The grouping element could not be determined for project 1., plant 2., and MRP group 3.."
what may be the reason for this reason.
Regards,
Raju

Hi,
You are using Automatic Requirement Grouping in your project and there is some issue with the Material Master,please check the Material Master Views.
Muzamil

VA00 condition type not getting determined for the returns order

Hi All,
I have a case where VA00 condition type not getting determined for the returns order that has been created with respect to the billing document.
When the pricing conditions are being copied from invoice it is getting copied but later it is getting deleted in the include LV61AA42.
Note:VA00 condition type is getting deleted from the internal table tkomv[].
If any one came across this scenario can you please help me.
Request your valuable inputs

Hi,
Please check the copy control setting in VTAA.
Maintain the pricing type as "D" at item category level for the respective document type .
Hope this will resolve your issue.
Regards,
Krishna O

The billing type could not be determined" .

Hi All,
When i am excuting bap BAPI_BILLINGDOC_CREATEMULTIPLE i by passing ref_doc its giving error that "The billing type could not be determined" .
Is i have to pass something else.
Regards,

Can you tell how did you resolve this?
I'm getting the same situation and have no idea
Thanks in advance.

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

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

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

IDoc type could not be determined for the IDoc in F110

Similar Messages

Maybe you are looking for