File to IDoc scenario - IDoc received with Errors

Hi,
I tried to send send IDoc from a file to SAP R\3. The communication channels are working fine, and I get the IDocs in R\3 but with status 56. When I examine the received IDoc structure in transaction "WE19", I see that the receiver port(SAP + SID of sap server) is blank with no values. I tested the IDoc adding the receiver port, and the IDoc got successfully posted...
I wonder why the receiver port that I specified in payload file content, does not reflect during runtime. I'm using the downloaded MATMAS IDoc structure with sender and receiver details as the input from file....
Please help me out!
Thanks!!
-Ajitha

Rodrigo/Sarvesh/Ravi/Haseeb,
Thanks for the inputs!! I have checked in IDX1 and the port name is the same. Also "Apply control records values from payload" checkbox is selected. I guess there was some problem with cache. It started working fine, when I started a new session
Thanks for your time and inputs!!!

Similar Messages

Web Service to IDoc scenario: No receiver could be determined error

Hi. I am working on a web service to IDoc scenario. I am receiving this error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I've taken the XML message being sent to me and tested the mapping and I've completed the test configuration in the IB. Both work fine. Any ideas? I've been looking into this for a couple of days, so I've been through all the previous posts I could find.
Thank you.
Nicole

hi,
This is not related to receiverdetermination ,whether you creaeted or not.
It is somthing related to receiver systemwhich was configured in Receier determination.
check the target BS is correct or not or the inbound interface.
Did you configured the proper receiver technical system..
OR
Check the Receiver Determination is configured correctly. i.e R/3
Verify all the configurations like SM59, Partner Profile/Logical systems. etc. Also check in SM58 of R/3 system.Make sure that All the objects are activated in the Directory.Refresh the cache.Verify is the business system is pointing to correct R/3 system . Go to Business system/Service->Menu->Adapter specific identifiers in the directory
You can test your configuration with sample
payload.
In ID goto to TOOLS -
> Test Configuration for testing.
Hope in this way you can still find at which point the interface goes wrong.

PI 7.0: IDOCs struck in IDX5 with error "Time Limit Exceeded".

Hi All,
We have a File to IDOC scenario in PI 7.0. After mapping the IDOCs are posted from PI to ECC System.
On a normal day this interface works good, yesterday we received a huge file which resulted in the creation of about 25000 IDOCs from one single file. The mapping went fine, however the IDOCs created were not posted into ECC System. When we monitor the IDOCs using transaction code IDX5 in PI system, we found the error message as "Time limit exceeded", the user shown was "PIAFUSER". To overcome this error, we increased the time limit of PIAFUSER from default to about 1500 seconds.
Now, I want to push these IDOCs from PI into ECC System. Could you please let us know, how to push these IDOCs sitting in PI system to ECC?
We do not want to reprocess the file from the beginning. Please let us know if it is possible to push the IDOCs without processing the file? If yes, how to reprocess?
Thanks in advance.
Regards,
Manohar Dubbaka.

Hi,
the help documentation is as follows:
Check the tRFC Status
Use
tRFC calls which transfer IDocs use the function module IDOC_INBOUND_ASYNCHRONOUS at reception (before release 4.0: INBOUND_IDOC_PROCESS).
If an IDoc in the sending system has been passed to tRFC (IDoc status "03"), but has not yet been input in the receiving system, this means that the tRFC call has not yet been executed.
Activities
To check the status of the tRFC calls, choose Tools ® IDoc Interface/ALE ® Administration ® Monitoring ® Troubleshooting ® RFC Queue (SM58) and specify any additional selection criteria.
The program RSARFCEX restarts unsuccessful tRFC calls.
You cannot choose the option is being executed in background processing.
Best Regards,
Erik Hubers

File to IDoc Scenario: Idoc Status 50

Hello,
I have a problem in doing a File to IDoc Scenario with a simple XML file mapped to IDoc "CREMAS.CREMAS03". In the beginning, I got a status 56:"IDoc with errors added". Then I added a logical system (LS name of my sender)manually in "Display IMG";however, it didn't work. So I simply changed the logical system name of my sender to XI_00_800 which already exists in R/3. I tried the scenario again, then I got the status 50:"IDoc added". Looked like the IDoc still hadn't been correctly inserted as a record. May I ask what other steps or configurations do I need to do to get this scenario to work? Thank you.

Steve,
<i>Moreover, I didn't create any partner profile. The "XI_00_800" partner profile is in the system all along. Should I create a whole new partner profile and point that to my sender business system?</i>
You need not create it once again as it already exists. Normally , ALE configurations on an R3 system are the responsibiltis of the Functional Team. For instance , on our projects we are never given access to the End r3 systems and the Partner profile are created by the F'nal team itself.
Like I mentioned, ask your F'nal team why you are getting this issue. From XI side , there is nothing more you need to do.
Regards,
Bhavesh

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Thanks,
Satya

PI 7.3 receiver AAE idoc scenario-No receiver comm channel found in ICO

Hi,
I am working in PI 7.3 receiver AAE idoc scenario.When I try to configure Integrated Configuration(ICO),I am not able to see the receiver comm channel in receiver agreement.
What is the reason for this??I have configured the communication channel,but still its not shown in reciver agreement dropdown.
Please help.
Regards,
Sriparna

Hi Sriparna,
In PI 7.3 there is are two separate IDoc adapters: "standard" IDoc adapter and one that is dedicated for AAE (ICO). Make sure that you have used the right one - most probably not, which is why you cannot see the channel in the dropdown list.
Hope this helps,
Grzegorz

Getting Error 26 in ALE IDOC scenario .- EDI Syntax Check Error...

Hi..
i am working in ALE Idoc scenario...I am getting Status 3 as well as status 26 in we02 transaction in my custom IDOC scenario for outbound process..
The error is 'EDI- SYntax Check'..
How to remove this error..
Pls help.

ya, there is only one segment available in IDOC..named i.e zseg_a .
So , error in postion is avoided..
How to find syntax error then?

File to RFC Scenario - Not working with AAE

I have a File to RFC Scenario (calling RFC /POSDW/CREATE_TRANSACTIONS_EXT) using AAE but it is failing with following error in PI .
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
But When I run the same scenario using IE instead of AAE, it is successful from PI. So probably there is nothing wrong in RFC channel configuration.
There's an OSS note-730870 on this error ,it says the XML document sent to RFC Adapter may not be RFC-XML but as I am using AAE, payload generated after technical routing cannot be viewed.
Could you all please suggest why this error is coming and solution for the same?
Thanks,
Ankit

Hi Debashish,Monica,
Thanks for your help, I checked this SAP note its question 16 do describe my problem but do not provide solution and as I am using AAE it does not allows me to see the target structure generated whereas if I use IE the target structure generated is sucessfully getting posted.
Also, the functional module is present in target system. I have reimported the RFC also.
Is there some AAE related configuration required to enable AAE with RFC which could be missing?
This is what I get in log as the RFC reciever is called..
06.09.2011 14:15:31 Information MP: entering1
06.09.2011 14:15:31 Information MP: processing local module localejbs/RfcAFBean
06.09.2011 14:15:31 Error MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
06.09.2011 14:15:31 Error Adapter Framework caught exception: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>
06.09.2011 14:15:31 Error Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: functiontemplate from repository was <null>.
Thanks,
Ankit

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

IDoc basic type FIDCCH01 with error F5866

Iu2019m trying to create an iDoc with basic type FIDCCH01 and message type FIDCCH type. Iu2019m getting error F5866 u201CWhen calling up the interface to financial accounting, no entry was made in the transfer parameter "Application key" when I process the idoc. I do not see an idoc value by this name. What am I missing in my config?
Thanks,
Stan

Stan,
First, I'd like to mention that you determine where the error message F5866 is used by entering this message in transaction SE91 and pressing the where-used function. This won't show you any of the dynamic message calls, but it does indicate that function modules FI_DOCUMENT_CHANGE and FI_DOCUMENT_CHECK_CHANGE are both possible origins for the message you received. These function modules are part of the FI Interface which I am assuming is called during the processing of your IDoc.
ACCHD-AWREF is one of the values passed to the FI Interface function modules, and message F5866 is returned when that field is blank. This is why I assume that the IDoc in question is missing a value for the AWREF field.
Based on that assumption, I checked the definition for the IDoc type that you mentioned, FIDCCH01, via area menu WEDI. This IDoc type contains a segment E1FIREF with field AWREF. You can use transaction WE02 to display the IDoc causing the error and check to see if the actual data for E1FIREF-AWREF is blank (ultimately leading to the blank ACCHD-AWREF value and error F5866).
Cheers,
Jamie

JDBC to IDOC scenario - Mapping problem with E1FIBSEG

Hi friends,
I have problem when generate multiple Idocs (FIDCC1) an multiple positions based on an External Definition for a SQL Server table. I have selected all fields from this table from a SELECT into the JDBC configuration.
My mapping is like this:
DWCAJA.ResultSet 1..1
     IDOC.
Thats ok and generate n IDOCs by every change of PK.
The problem is when i want to map positions because i dont have any field in source message to identify the number of positions to map with E1FISEG.
If I have two differents Pks and n rows, the result of testing is as folow:
FIDCC1
IDOC
     E1FIKPF
         E1FISEG
         E1FISEG
IDOC
        E1FIKPF
I cant obtain n BSEG segments according PK. I've mapped and all fields of row segment but those are created in the first IDOC node only,
Any suggestions?
Regards,
Pablo.-

Important: Primary key : DWSucCod + DWCajSec
Payload:
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100001</DWCtaConCo>
<DWRecImp>100</DWRecImp>
</row>
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100002</DWCtaConCo>
<DWRecImp>200</DWRecImp>
</row>
Result:
IDOC
   E1FIKPF
     E1FISEG
         hkont :1100001
         dmbtr : 100
     E1FISEG
          hkont :1100002
         dmbtr : 200
Payload:
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100002</DWCtaConCo>
<DWRecImp>200</DWRecImp>
</row>
- <row>
<DWSucCod>12</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100003</DWCtaConCo>
<DWRecImp>300</DWRecImp>
</row>
Result:
IDOC
   E1FIKPF
     E1FISEG
         hkont :1100002
         dmbtr : 200
IDOC
   E1FIKPF
     E1FISEG
         hkont :1100001
         dmbtr : 300
Payload:
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100001</DWCtaConCo>
<DWRecImp>100</DWRecImp>
</row>
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100002</DWCtaConCo>
<DWRecImp>200</DWRecImp>
</row>
- <row>
<DWSucCod>12</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100003</DWCtaConCo>
<DWRecImp>300</DWRecImp>
</row>
Result:
IDOC
   E1FIKPF
     E1FISEG
         hkont :1100001
         dmbtr : 100
     E1FISEG
         hkont :1100002
         dmbtr : 200
IDOC
   E1FIKPF
     E1FISEG
         hkont :1100003
         dmbtr : 300

CRM to PI outbound IDOC scenario : IDOC ALE config

Hi folks,
I have a scenario: CRM-> PI
CRM system posts an IDOC to PI,
I have done all the necessary ALE configs:
1. comm. id on PI
2. RFC Destination on CRM to PI
3. Port on CRM. we21
4.Logical SYsm on CRM
5. Partn Prof on CRM
now, when i try to push out an idoc out of CRM , it fails in CRMs TRFC queu(SM58)
with this error:
Transaction IDX1: Port SAPDX1, client 500, RFC destination contain error
I have no clue why it failed with this error.
1. No idea from where it picked up this port as well.
2. Port i created to PI was an autogenerated Port and not SAPDX1, don't knw how it picks this up.
Would appreciate any help with respect to this.
Thanks,
Hank

Also, for your reference just double check if the following steps are completed properly for outbound processing:
1.Define Logical Systems and Assign Client to Logical System u2013 Transaction SALE
2.Maintain RFC Destinations u2013 Transaction SM59
3.Define Ports u2013 Transaction WE21
4. Maintain Distribution Model u2013 Transaction BD64
5.Generate/Create Partner Profile u2013 Transactions BD82/WE20
6.Distribute Model View u2013 Transaction BD64
    -Select the Model View
     -Go to menu path Edit -> Model View -> Distribute
     -Result log will be displayed on the next screen
Hopefully it should work now.
Puneet

Clustered File share Permissions won't set (with error)

I have a s2012r2 cluster with a file server. When i go to create a new share it creates with read only permissions and i cannot change it to full or read/write. it is just the share permissions that won't set. when i create a share the error i get is "The
Cluster Resource could not be found." if i try to edit the share permissions the error is "Error Occurred while update an SMB share: The cluster resource could not be found" the admin share is working perfectly and the folder permissions are
accurate.
The only solution to this problem i have found online that worked for someone is to destroy the cluster and rebuild it. I really don't want to do that.

Hi RaVell(Pinki),
This error typically occur when
we have added the Disk from Available Storage to the File Share Server Group, please refer the following KB solution to avoid this action.
You may receive error messages when you share a folder in a Windows Server 2008 failover cluster
http://support.microsoft.com/kb/947051
More information:
Advanced resource configuration in Windows Server 2008 failover clusters
http://support.microsoft.com/kb/947050
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Regarding error in XI File to IDoc scenario

Hi,
when i was doing file 2 idoc scenario i got this error "Unable to convert sender service to an ALE logical system". please resolve my issue as early as possible.

Uday,
Please go through these threads:
Unable to convert the sender service to an ALE logical system
How to convert Sender Party/Service to a Logical System?
Unable to convert the sender service to an ALE logical system
BR,
Alok
Edited by: Alok Sharma on Jan 31, 2008 12:39 PM

File to idoc scenario problem

I am trying to do FILE TO IDOC scenario, i am getting error called, UNABLE TO CONVERT SENDER SERVICE TO AN ALE LOGICAL SYSTEM.?
could anybody solve this problem?

Murali,
You get this error when Adapter specific attributes are missing..
Maintain Adapter Specific Attributes for business system in Integration directory.
Select your business system...Then select Service-->Adpater Specific identifiers.
from right hand window..
Set Logical System ID(of R/3 system), R/3System ID and client.
Let us know if you need more details.
Nilesh

File to IDoc scenario - IDoc received with Errors

Similar Messages

Maybe you are looking for