IDoc adapter inbound channel: Error Fehler beim Le

Hello,
I have a BIG problem. I want to use IDOC - XI - IDOC. I have configured the connections. But when I send the Idoc to the XI. it returns a code in the SM58 "IDoc adapter inbound channel: Error Fehler beim Le" The Message comes cut, it doesn't return all the message. In the XI doesn't give me any error, nothing. The IDOC says thta it has been sent correctly (Code 3). How can I trace the IDOC from de sender to the XI?
I wanted to use the IDOC HRMD_A06 but now i'm trying with SYIDOC to see if it passes.
Can Someone help me?
Caller       Function module               Target system Date       Time     Status text
SRGEN13      IDOC_INBOUND_ASYNCHRONOUS     RHXCLNT013    07.04.2006 10:06:46 IDoc adapter inbound channel: Error Fehler beim Le
Thank you
PM

I want to know if the Connections have to have SNC?
I have read this in the note http://help.sap.com/saphelp_nw04/helpdata/en/ca/fafaf6dbc8b240b1cf4a88c40379b2/frameset.htm
Inbound and outbound connections should be secured by Secure Network Communication (SNC).
Is that correct? maybe that's why it says the that error
PM

Similar Messages

  • IDoc adapter inbound channel: Error Error when reading Exchange Profile

    Hello Experts,
    Currently i am working on an IDOC to file scenario, in which Data will be sent from ECC server (IDOC) to an FTP server via SAP PI, but when i try to send IDOC to PI, i am getting the following error
    in Transaction SM58:-
    'IDoc adapter inbound channel: Error Error when reading Exchange Profile for system XID and
    client 401 occurred in the IS pipeline' .
    Can anyone please help me on this.
    Thanks & Regards,
    Amit Naik

    Hello Experts,
    Let me explain to you the whole scenario, We have two servers of PI, 7.1 & 7.0. Now the Java Stack of 7.0 is not working & Cache update of 7.1 is not happening.
    Thats why we have linked ABAP stack of 7.0 with Java stack of 7.1. Now we can see the objects created under Java 7.1 in ABAP stack of 7.0 (SXI_CACHE).
    Now we have done all the settings to create an IDOC to file scenario. All the RFCs are working fine, but when we send an IDOC from the ECC system to ABAP 7.0, we are getting the following error 'Error while reading exchange profile for system NW' in SM58 .
    Now can anyone tell me what exact settings i have to change in the Exchange profile (Java stack of 7.1), so that the Java 7.1 & ABAP 7.0 connection is setup or do i need to change anything else.
    Thanks & Regards,
    Amit Naik

  • IDoc adapter inbound channel: Error Error while read

    Dear All
    I am sending idoc from SAP 4.6C to PI. But on SM58 I am getting an error
    IDoc adapter inbound channel: Error Error when reading
    Which is not complete because field length is 50 characters , double clicking on this message is asking for message class. How can i see the complete message.
    Can any one send me configuration detail of receiving IDOC at PI end , I don't want send to it forward from PI.

    Please clear these points.
    In PI system:
    1. Create RFC destination of type 3 pointing to R/3 system.
    2 . create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system.
    3. Using IDX2 import the IDOC meta data in to your PI system.
    RFC destination to which direction , towards sender of IDOC ?
    Port of which system sender system or receiver system?
    What about configuration in Integration Directory , is there any configuration required on integration repository and on integration directory.
    What will be the procedure of seeing complete message on SM58.
    -->In PI system while ur creating the RFC destination of type 3 give the hostname and system number of ur R/3 system ie SAP 4.6 c.
    -->In PI create Port using the IDX1 t-code port name should be SAP + SYSTEM ID OF R/3 system and in that RFC destination option, maintaine the destinatination name which we created using sm59.
    -->coming to IR you need to create the:
                        1. Receiver data type.
                        2. receiver message type
                        3. receiver message interface. No need to create the above 3 for sender.
                       4.while mapping source is your Idoc and target is your receiver message type.
                       5. while interface mapping source is Idoc and target is receiver interface.
    -->Coming to ID no need to create sender communication channel and no need to create sender agreement.
    -->create receiver communication channel and receiver agreement.
    --->create Interface determination.
    -->create receiver determination.
    -->If message got stuck in SM58, unlock it by using double click or activate the selected message.
    Thanks

  • IDoc adapter inbound channel: Error Connection err

    Hi,
    We are trying to push an IDoc from R3, it's status is green in WE02. However, the IDoc is not reaching PI.
    In tcode SM58 in R3 we are getting an error "IDoc adapter inbound channel: Error Connection err". I have gone through the SAP note 940313 but was not able to figure out the exact cause of error.
    Any help would be appreciated.
    Regards
    Pravesh

    Hi,
    Please check the steps for Idoc posting to SAP PI system from R/3. Probably you are missing some configuration.
    Few Checks -
    1. did you created Logical System using BD54?
    2. Create RFC destination Type 3 for PI
    3. create partner profile using we20
    In Pi
    Check following
    1. Create RFC destination of type 3 pointing to R/3 system.
    2 . create Port using the IDX1
    3. Using IDX2 import the IDOC meta data
    Regards
    Aashish Sinha

  • SM58 - IDoc adapter inbound: IDoc data record table contains no entries

    Trying to send Idocs from SAP ECC6.0 via PI 7.0 up until 2 days ago there was no problem.
    Since yesterday, only one specific type of Idoc does not make it into XI (PI). In the Idoc monitor (WE02) the idocs that were created gives status 3 which is good. But all Idocs of that specific type (ZRESCR01) does not go to XI. I can only find them bakc in SM58 where it gives the following message:
    IDoc adapter inbound: IDoc data record table contains no entries
    I have checked SAP notes 1157385 and also 940313, none of them gives me any more insight into this error. I have also checked all the configuration in WE20, SM59, and in XI (repository and directory) and in XI IDX1, IDX2 but could not find anything that would cause this. I can also not think of anything that changed since 2 days ago.
    Please point me in the right direction.

    hi,
    i think in sm 58 u can find entries only when there is some failure in login credential .
    if there is change in IDoc structure than you have to reimport the idoc metadata defination at IDX2.otherwise not requird.
    please check the logical system name pointing to the your requird target system....
    please also verify thet your port should not be blocked.
    pls find the link it may help
    Monitoring the IDOC Adapter in XI/PI using IDX5
    regards,
    navneet

  • Issue about IDoc Adapter Receiver Channel's Performance

    Hi Everyone,
    Currently, I am working on a scenario of File -Integration Process - IDoc in XI 3.0 with patch level 16. The scenario works fine when it process one/two/three files in parallel, and the IDocs arrive R/3 system quite fast. But when I try four files in parallel, the whole XI server blocks, I can not do anything even logon Integration Builder, and the IDocs arrive R/3 brokenly, sometime with the invterval to 10 minutes. When the XI comes back, I found all the four integration processes finish successfully and each transaction works fine and fast. What's more, after I change the IDoc Adapter receiver channel to a File Adapter receiver channel, it works fine for even 20 files in parallel. So I think it is some issue about IDoc Adapter receiver channel. Does anyone have the same experience as me? Any comments will be appreciate.
    Regards,
    Nick

    Hi Nick,
    Can you check this Blog-
    /people/sreekanth.babu2/blog/2005/01/05/delayed-xi-message-processing
    May be useful.
    How are you picking the files .. You can try with EOIO options while picking the file.
    But if you use BPM, it is not applicable. It will act as a EO only.
    Check this SAP Note- 833740
    Thanks,
    Moorthy

  • ALERT MAIL FOR FILE ADAPTER COMMUNICATION CHANNEL ERRORS

    Hi,
    I need to send an alert by mail to a list of configured receivers if any error( Application as wel as System Errors ) occurs in the FILE ADAPTER Communication Channel .
    Please suggest how to do it......
    Regards,
    Sriparna

    Can anything be configured in the communication channel to run a mail unix script if the communication channel is throwing
    error.Other than alert rule can we configure this.
    Why do you intend to use script? Define Alert....create Rule....set parameters using SCOT.....you will get the alert as email (if you need it)
    Can you please help with how do I create this rule specific to File Adapters only ?
    Other than selecting FILE as Adapter Type in RWB --> Alert Rule definition we dont do anything special....this setting should help.
    Regards,
    Abhishek.

  • Idoc adapter- communiccation channel

    Hi
              When we do an Idoc to file scenario sender communication channel is not required. Because Idoc is the sender adapter. but while doing a File to Idoc case why do we neeed a receiver communication channel. Here also we use Idoc so why use a communication channel ?

    Hi,
    You do not need A Sender IDOC Adapter. IDoc's are sent directly to XI's Integration Engine and so no need of Sender IDOC adapter and therby Sender Agreement as well.
    Yes, the port will be a TRFC port and you will use the RFC destination created in SM59 in this port.
    Idoc Metadata gets loaded automatically when your scenario is run. You can also do it manually, by going to IDX2 and probiing the Port and the Basic Type of the idoc whose metadata you want to load.
    but when we go for a fileto IDOC the file does not contain a standard structure
    for that reason we need to create the receiver IDOC adapter .
    pls chk this links
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    if found worth pls do the req
    Thanx
    Sampath

  • IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

    Hello SDN Gurus,
    The scenario I am working on is IDOC(PAYEXT & EUPEXR) --> XI (ABAP Mapping) --> Flat File (IDOC Structure).
    The IDOCS produced in Appl system may be in the following order
    PAYEXT
    PAYEXT
    EUPEXR
    PAYEXT
    PAYEXT
    PAYEXT
    EUPEXR
    I need them to be processed in the same order into flat file.
    The scenario is working good except for the serialization. So I did the following
    Created two entries in IDXQUEUE one for each message type with the same Queue name in XI system.
    Created a new rule for the queue and an associated function module. Used this rule in partner profile for both the message types.  I used the following link to create the above two steps.
    /people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
    The SAP system in based on WAS 6.4.
    I can see the queue name & EOIO in the inbound message header.
    I am getting a mapping error in ABAP program. If I inactivate the queue(in Appl system SAP ECC), I don't get any error.
    Does anybody had this problem earlier? Please advice.
    Thanks
    Srini Vaidyam

    I found an OSS note to resolve my issue. The note number is 1057573.
    Whenever the queue is activated, the sender system will not send the <TABNAM> field value in EDI_DC40 structure. This note addresses this problem.
    I found out this by comparing the results from SXI_MAPPING_TEST individually for the message that failed after queue is activated and the message that was successful if the queue is inactivated.
    Only thing I noticed now is even if you selected the radio button "Trasfer Immediately" in Partner profile of Appl. system, the messages are not sent. They are getting collected. So we need to manually push them out using WE14.
    This forum Rocks.
    Thanks. 
    Srini Vaidyam

  • Sender Soap Adapter communication channel  error

    Dear Experts,
    When i see Sender soap adapter status in Communication channel monitoring.I am getting the status as:
    "Processing Errors in the Last 50 Minutes"
    Thanx in advance

    Aamir,
    My other interface is working fine by giving the following url:
    http://kpmgvm015:8001/XISOAPAdapter/MessageServlet?channel=:KPMG_AU_ALL:RetrieveOpportunityRecord_SOAP_Sender
    I am not using the propsed url.
    Moreover when  i try to give this url in the browser . It is asking of user id and password.
    I am  giving user as : PIAPPLUSER.It gives message servelet is ok.
    In my communication channel monitoring the corresponsing communication channel:
    RetrieveclientRecord_SOAP_Sender is in Red - Processing Errors In the Last 40 Minutes
    Error meesage in Webclient:
      java.security.AccessControlException: PIAPPLUSER has no permission for accessing binding com.sap.aii.af.service.cpa.Binding@d046043a

  • Receiver JMS Adapter Communication channel Error

    Hi Experts,
    The Error is given below
    Cannot connect because class 'com.ibm.mq.jms.MQQueueConnectionFactory' is missing: ensure that JMS Provider library 'aii_af_jmsproviderlib.sda' contains all required resources.
    when i searched SDN , i found the MQ JMS  Library need to deployed in XI/PI . For clarification check SAP NOTE  1138877 is given .
    What should I do ?
    pls advice
    Regards,
    Jude

    Hello Experts,
    I am encountering the same error that you faced. I am using PI 7.0 and MQ adapter 6.0. I would like to know where to get the following jar files:
    CL3Export.jar
    CL3Nonexport.jar
    com.ibm.mq.jar
    com.ibm.mqjms.jar
    connector.jar
    dhbcore.jar
    rmm.jar
    I know that I am supposed to add the above files to aii_af_jmsproviderlib.sda on the PI server. As I not a basis person, it'll be great if you could direct me to some detailed instructions. I am trying to follow SAPNote: 747601.
    Please correct me if I am wrong.
    Thanks,
    Bhanu.

  • JDBC Adapter Communication Channel error

    I am getting this error for a JDBC Adapter, I waondering if anybody could point me in the right direction.
    I have installed the driver:
    JDBC Driver: oracle.jdbc.driver.OracleDriver
    Connection: jdbc:oracle:thin:@146.146.78.74:1521:ts1
    Error:
    Error when attempting to get processing resources: com.sap.aii.af.service.util.concurrent.ResourcePoolException: Unable to create new pooled resource: DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@146.146.78.74:1521:ts1': SQLException: Io exception: The Network Adapter could not establish the connection
    Any help would be appreciated.

    The driver has been deployed into the XI server, I just deployed the testing tool from OSS note 1085539.
    I am still getting this error.
    Exception Occurred : Io exception: The Network Adapter could not establish the connection
    Exception Stack Trace : java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)
         at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:387)
         at oracle.jdbc.driver.PhysicalConnection.(PhysicalConnection.java:420)
         at oracle.jdbc.driver.T4CConnection.(T4CConnection.java:165)
         at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
         at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
         at java.sql.DriverManager.getConnection(DriverManager.java:559)
         at java.sql.DriverManager.getConnection(DriverManager.java:189)
         at com.sap.util.TestJDBCUtil.testDriverManagerConnect(TestJDBCUtil.java:52)
         at com.sap.tests.TestJDBCConnectionServlet.processRequest(TestJDBCConnectionServlet.java:41)
         at com.sap.tests.TestJDBCConnectionServlet.doPost(TestJDBCConnectionServlet.java:74)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:215)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Any suggestions?

  • IDOC Adapter error while load balancing

    Folks,
    I am facing an issue when I am switching on Load balancing button in RFC destination while sending IDOC in sender system . The sender system shows this error in SM58
    <u><b>IDoc adapter inbound channel: Error Error when rea</b></u>
    Thanks,
    Manish

    Hi Manish...
    This is from F1 on Traget host field in SM59..Check part in bold..
    Name of target host  
         Name of the target host as displayed by the UNIX command 'hostname'.    
         <b>If you are using load balancing, the target host must be the host name  
         of the message server of the SAP System. This is defined in the profile 
         parameter 'rdisp/mshost' of the target system. If you have any further  
         questions, consult your system administrator.                           </b>
         You can specify host names as                                           
             -   Normal host names                                               
             -   Host names in DNS format (if DNS available)                     
             -   IP addresses                                                    
             -   SAProuter names (in the form /H/.../S/.../H/.../S/... )        
    Notes                                                                      
         If you enter the host name (for example, hs0311) as the target host in 
         an RFC destination, its IP address is stored internally in the database
         table RFCDES (destination administration). This speeds up the RFC      
         connection initiation, since the host name does not need to be converted
         into its IP address.                                                   
         However, problems occur if the IP address of the target host changes.  
         For this reason, you must adjust the RFC destinations if the IP address
         of the target host changes.                                            
         If you specify the host name as a SAProuter name (/H/hs0311 instead of 
         hs0311), it is not converted into its correspondidng IP address.       
         Instead, it is stored in its SAProuter form in table RFCDES.

  • Metadata EDISDEF not maintained  - Idoc adapter error

    hi,
    In our scenario, SenderParty->XI->R/3, we are using custom idoc to post into R/3. The idoc adapter throws an error, Metadata EDISDEF for port SAPXXX, IDoc type ZKAGXXX and CIM type not maintained, but when i use standard idoc, i don't get this error. We even applied oss note 837595 to fix authorization issue, but it didn't help.
    Any ideas or suggestions.
    Thanks
    Pandari

    One LAST suggestion.  Looking at Note 837595, it doesn't seem to specify a value for authorization group (DICBERCLS).  Try authorization group 'SS' (without quotes).  So:
    Object: S_TABU_DIS
    Activity: 03
    Auth. Group: SS
    I recall now that a customer recently had this issue and (for them), this helped.
    Jin

  • IDOC adapter and number of tRFC records

    We have idoc inbound scenario file -> XI -> idoc -> R/3.
    For each file record an IDOC is created.
    Can somebody explain, why only one tRFC record is created containing all IDOCs? Can you influence with interface config how many tRFC records are created? Does settings ' exactly once ' / ' exactly once in order ' have something to do with how many tRFC entries are created?
    We faced a situation with our interface scenario that file unexpectedly contained huge number of records causing huge number of idocs generated in XI. However only one tRFC entry was created that contained all idocs. As consequence the receiving system had performance problems and the tRFC call had to be cancelled.
    As workaround we splitted the source file in file adapter to interval of 1000recs, thus causing multiple tRFC records created and performance was ok in background system.
    Is XI trying to keep IDOCs created out of each incoming message in one "LUW" and send them alltogether in one tRFC call to R/3? Or is there a config parameter that each created IDOC could be sent independent of other idocs still to be created?
    br: Kimmo

    Kimmo,
    There will be one TRFC call per message from XI.
    The whole input file is treated as a XI message.
    The Receiver IDOC Adapter call the SAP system via ONE TRFC call and posts the message.
    By mentioning Exactly Once in the Receiver Idoc Adapter Communication Channel, XI guarantees the delivery of that message.
    One way is to split the file into multiple Messages.
    You can do this via BPM. But this is not advisable for large files.
    We had the same problem for very large files.
    We used XI to just pass through the file from Source system and post as file in the Application Server of SAP.
    We defined a LSMW project for Periodic Processing, which would take this file and post as Idocs in the SAP System.
    Our Scenario
    File -> XI -> File.
    In the Receiver File Adapter, use the Execute Operating System Command to trigger event sapevt in the SAP system.
    You can define events for Background jobs.
    So when XI posts the file in the Application server of SAP, XI will trigger the background event defined in the Communication Channel.
    The LSMW project which has been scheduled to listen to this background event will kick off.
    Hope this helps.

Maybe you are looking for