Sending  IDOC from XI to R/3

Hi All,
I have created an IDOC - XI side here i am sending IDOC  XI to R/3 it is showing Red Flag in SXMB_MONI but it is not showing any errors what will happend...? can any body suggest me the solution..?
Thanks
Sudheer

I hope you followed these steps for posting the idoc out of r/3.....
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Sending System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code  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 Using transaction Using Transaction (IDX2)
a)  Create new
b)  IDOC Message Type
c)  Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code  (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.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(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)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Outbound Parameters (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
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details  for Receiving port, Pack size=1 and Basic type
I)   save
4)   In Transaction SALE, Create Logical System
a).  Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
5)   Create Customer Distribution model in the transaction code BD64
1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3)   Save the Distribution model
    Generate Partner Profiles
Click on Menu Item ‘Generate Partner Profiles’
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
4)   Distribute Customer Distribution Model
    In the menu item  GO to Edit->Modal View-> ‘Distribute’ to the destination client
    Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed

Similar Messages

  • Message SR 053 when i send idoc from SAp R/3 4.6C to PI 7

    Hi,
    I try to send idoc from SAP r/3 4.6C to PI 7. I had made  ALE configuration in my sender system ( SAP 4.6C) but idocs are not sent to PI. In SM58 i have message "Name or password is incorrect (repeat logon)". Yet i'm sure that user and password are correct because if i test RFC destination using SM59 , test is OK.
    Is somebody can help me ?

    Hi,
    In R/3 :
    my RFC destination is type 3 and point to XI. The port in the partner profile  point to this RFC destination. ( all seems good !).
    In Xi : i created a port and i load manually idoc in idx2 to be sure that RFC destination was OK. Nothing in IDX5.
    When i send idoc MATMAS using BD10 from R3 to Xi i have something very strange: first the message B1 038  "1 master IDocs set up for message type MATMAS" and just after
    the XI logon screen  appears !! Then message "1 communication IDoc(s) generated for message type MATMAS" and this idoc stay in SM58 with message "Name or password is incorrect (repeat logon)".
    Somebody can give me requires caracteristics for XI user used in R/3 RFC destination ?

  • Send IDoc from External System to SAP system

    Hi Folks,
        I have a requirement to send IDocs from an external system to the SAp system. Basically the external system is a subsystem which is able to send & receive idocs. The external system is currently able to send idocs to SAP system through the ALE layer but now we have to replace it by PI. Now the external system has to send teh IDocs to the SAP ECC system through the SAP PI 7.0.
       Kindly let me knowq how I can achieve it.
    Regards,
      Santosh

    Hi Satish,
    You can achieve this requirement
    1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel  to  send IDoc.
    or
    2)Use proxy program ,implement the same ALE logic in PI.
      or
    3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
    Regards,
    raj

  • Sending IDoc from R/3 to XI -ongoing

    Hi,
    With reference to my previous errors while sending IDoc to XI from R/3 system. I have resolved errors with help of Seshagiri and Kummari advise and help. But now I am getting new kind of error, while sending IDoc from R/3 its getting passed from R/3, but while checking it in XI throug SXMB_MONI I am getting below error:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_POCreateIdoc_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_POCreateIdoc_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Can any one advise me on this?
    Thanks & Regards
    Manish

    Hi,
    There were so many Mapping Objects under different Namespaces and under that different Message Mapping trees.
    Under one tree I have tested the XML message and found the below error:
    Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd Cannot produce target element /ns0:MT_POFile/POItem/Price. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    Kindly check if this is the correct error I am getting related to SXMB_MONI error message.
    Regards,
    Manish

  • Sending IDOC from R/3 to MII error

    Hi,
    We are trying to send IDOC from R/3 4.7 to MII 12.1 (SP8 patch 9 on NW CE 7.11).
    We followed the guide below:
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3861e693-0e01-0010-e791-9b44d2693e6c
    Connection of message listener to R/3 works fine.
    RFC connection test from R/3 to message listener was successful.
    But when we try to do model distribution we get this error " - Communication error occured. Server repository could not create function template for 'MODEL_VIEW_REPLICATE'.
    Maybe someone encountered this error and can help to resolve it.
    Thanks in advance.

    Hi Michael,
    What do you mean by "manually registered the ProgID"? The message listener configuration property is as below:
    ProgramID:  MII_IDOC_CONNECT_5
    MaxReaderThreadCount:  1
    SAPClient:  800
    UserName: GAOMX
    Password: xxxxxxxx
    Language:  EN
    ServerName:  blade01a.memc.com
    PortNumber: 00
    BindingKey:  XMIIIDOC
    And also, following is error message found from LOG VIEWER of the MII server:
    here is one
    Message: not supported FunctionModule MODEL_VIEW_REPLICATE for IDocActivationSpec
    Date: 2011-07-21
    Time: 15:30:18:060
    Category: /System/Server/Connector/Rfc
    Location: com.sap.mw.jco.jra
    Application: sap.com/sapjra~xMIIIDOC05
    Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
    Data Source: j2ee/cluster/server0/log/system/server_00.log
    and another one
    Message: Server repository could not create function template for 'MODEL_VIEW_REPLICATE' caused by: java.lang.RuntimeException: not supported FunctionModule MODEL_VIEW_REPLICATE used with IDocActivationSpec registered for MII_IDOC_CONNECT_5 on system blade04a_MIT_00
    Date: 2011-07-21
    Time: 15:30:18:061
    Category: /System/Server/Connector/Rfc
    Location: com.sap.conn.jco
    Application: sap.com/sapjra~xMIIIDOC05
    Thread: Thread[Managed_Application_Thread_20,5,Managed_Application_Thread]
    Data Source: j2ee/cluster/server0/log/system/server_00.log
    Thanks,
    Mike

  • Error sending IDOC from external Java application to Sap ERP system

    Hi Experts!
    When I try to send Idoc from Java application to XI an error occurs : no service for system CLNTJAVA, client in Integration Server.
    My question is: What value the setSenderPort() is excepting?The Java third party business system's logical name or the ERP business system's logical name where the JCO can be found?I tried both of them, but still have the problem.
    Please help. I read all threads about this error, but non of those can help me.
    My relevant java sourcecode:
                doc.setSenderPort("CLNTJAVA");
    The XI documentation says that:In the case of non-SAP senders, the entry in the SNDPOR field is interpreted as a logical system name, and the corresponding business system is searched for in the runtime cache.
    Both case(third party business sytem and erp business system) I have configured the ID    i think correctly. I  made a business systems,I configured the adapter specific identifies,I  made the IDX1 port,I made the RFC destination,I polled the IDOC type with IDX2 transaction, I have made full cache refresh,I configured the INTEGRATION_DIRECTORY_HMI rfc destination,but I do not made any communication channels, receiver determinations, receiver agreement.
    My configurations if it can help for you.
    Hostname:sapsp5
    System name: NE2
    Clients:
    000 ERP
    001 Integration Server
    <b>SLD configurations:</b>
    Third Party Technical system name: Java_sytem
    Business System:CLNTJAVA
    Logical system name: CLNTJAVA
    <b>ID configurations:</b>
    Business System:CLNTJAVA
    adapter-specific identifiers:logical system:CLNTJAVA, <u>the rest is initial</u>,because I cant change it.
    IDX1 port name: CLNTJAVA the client is 001. the rfc destination is client_001.
    I think the IDX1 port and the adapter specific identifiers are wrong. is it?
    my java source if the sender is the JCO
    doc.setSenderPort("INTSERV");
    My configurations if the sender is the JCO.
    <b>SLD configurations:</b>
    Technical system name: NE2
    Business System:INTEGRATION_SERVER_NE2
    Logical system name: INTSERV
    <b>ID configurations:</b>
    Business System:INTEGRATION_SERVER_NE2
    adapter-specific identifiers:logical system:INTSERV,system NE2,client 001.
    IDX1 port name: INTSERV the client is 001. the rfc destination is client_001.
    Could this error be an autorization error?I tired to connect to the xi from the Java, with the user PIISUSER extended with PISUPER roles.
    Thank very much.

    Hi!
    My SNDPOR already set to my source business system's logical name if you check my configurations(JAVACLNT), so there is another problem unfortunately. I set SNDPRN to JAVA, but it still does not work.
    Check this configuration please(posted here:
    No service for system ... in Integration Directory)
    doc.setMessageType("ACC_DOCUMENT");
    doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set
    doc.setRecipientPartnerType("LS");
    doc.setRecipientPartnerNumber("SE1CLNT500");
    <b>doc.setSenderPort("SAP3MA");</b>
    doc.setSenderPartnerType("LS");
    <b>doc.setSenderPartnerNumber("TREMACLNT");</b>
    doc.setClient("100");
    Inside XI configuration integration builder
    <b>Business Service: Service: TREMACLNT</b>
    Under the menu Service - Adapter specific identifiers
    Idoc Adapter Logical system: TAPPMAN (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
    IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA
    Client: 100
    In IDX1 trans
    <b>Port: SAP3MA</b> (Note that the 3MA here is matched against the IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA)
    (a not so well documented feature)
    Client: 100
    RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
    I guess that your idx1 port name is the same as the SNDPOR value. I think it should be, because the XI is whatching the IDOC traffic in the idoc adapter port, so you should send the IDOC from external system to the adapter port. Is it right?
    My idx1 port is the same as my SNDPOR value in Java,but still came the error.

  • Issue in sending IDOC from BODS to SAP

    I am getting issue while sending IDOC from BODS to SAP.
    Job is getting failed with error : "No authorization to send Idoc with message type CREMAS"
    I have checked last authorization in SU53 and it is Successful !!
    What would be reason because of which job is getting failed with Authorization error?

    Go to sm58-->Select IDOC_INBOUND_ASYNCHRONOUS this function module, in menu mar select edit--> execute LUW.
    or take help from sap basis team, can you please check user in the source system have authorizations profile. 'S_BI-WX_RFC' for this u can refer sap note :150315.
    if you need more information refer this document:
    How to check a BW - SAP source system connection - SAP NetWeaver Business Warehouse - SCN Wiki

  • Sending IDocs from R/3 to XI

    Hello,
    I try to connect a R/3 system to an XI system. I have made the SLD configuration, created RFC destinations, ports and so on. Sending IDoc from XI to R/3 was successful.
    No I would like to send IDocs from R/3 to XI. I did the necessary steps at R/3 as described in several blogs etc.:
    SM59 rfc dest to XI
    WE21 tRFC port
    I also read about this step: Create receiver sys as logical system in BD54. What is this for? I am not sure if this step was done in my case, cannot check it at the moment.
    I am trying to send an IDoc via transaction WE19 (Idoc Test tool). I think there is no need to create a partner profile?
    Now I am wondering: Which values must be set in the control record? I inserted the port pointing towards XI, but I am not sure about the other fields.
    I know there are several blogs on this topic but for me there are some details missing. I am also interested in some kind of explanation not just WHAT steps have to be done, but WHY they have to be done.
    Thanks in advance, point will be awarded.
    CHRIS

    > 1. The process is like this: The Logical system is
    > defined (as its name suggest ) just for Logical
    > definition of the communicting parties. The technical
    > details are not provided here.
    > 2. Then RFC Destination is maintained where actual
    > connection parameters r maintained.
    > 3. Port here act as the medium through which the
    > transmission is done.
    > 4. To identify ur particular message, Partner Profile
    > is maintained.
    >
    > Now in we19 test tool, the port provides the medium
    > where the data should be sent. Through this medium,
    > the connection to the receiver is checked via RFC
    > destination.
    Also thanks to you. I understand that the message is sent to a port, which points to a certain RFC destination. But still I don't get it: I thought thats exactly what WE19 is for: To send IDocs for testing purposes to ports, while there is no partner profile needed? I thought there is no partner profile necessary as I can set all fields manually in the control record (receiver port, sender port, message type, receiver type and so on).
    Kind regards
    CHRIS

  • How to send IDocs from a non-SAP system to a SAP system

    Hi everyone i am new to SAP R/3 System.
    Currently i am required to send IDocs from a non-SAP system to a SAP R/3 System.
    There is a guide on Cost-Effective and Quick Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface. But its from a SAP system to a non-SAP system and i am able to do that.
    Is there any step by step guide where they teaches you how to send IDocs from a non-SAP system to SAP system via similar method?
    Thank You!

    Hi,
    I hope this link may help you......
    http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.ds.entpak.sapr3.use.doc/topics/c_pack_r3_Introduction.html

  • Send IDOC from Business Connector to SAP faster

    Hi Developer!
    I need to send a very lot of IDOC converted from XML files from the Business Connector to SAP. The XML files are in different directories pro business partner, but they have a same type (ISU_MSCONS).
    My problem, that the import take a lot of time. Only in every 3 seconds (IDOC creation time) gets (or works up?) the SAP one IDOC. I start diferent services pro partner at the same time to import the IDOCs, but I couldnt short the 3 second work time in the SAP. So you can count it easy, that in 1 minute I can import 20, in 1 hour 1200, in 1 day 28800 IDOCs instead of 100.000.
    It is really parallel import? Have anybody any idea to make the import more faster. I know (asked the SAP Administrator) so, one BC - SAP connection (Program_ID) has more pools (= threads) in the SAP at the same time.
    Thanks any help,
    Charlie

    Hi Satish,
    You can achieve this requirement
    1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel  to  send IDoc.
    or
    2)Use proxy program ,implement the same ALE logic in PI.
      or
    3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
    Regards,
    raj

  • How to send IDOC from nonSAP to SAP

    Hi ;
    I need to send IDOC from nonSAP to SAP. I have experience it with XI and BC..but now I need sending IDOC to SAP directl without these tools..
    Can you explain it via sample? (I know already how to create port , define LP from we20,we21 ).
    Firstly Do I need to create a RFC destination ? and I want to send IDOC as XML by HTML post method..Which port must I send?
    Must this port point to this RFC? 
    Thanks.

    Hi,
    Here you have to generate an IDOC and convert into XML format and put at required server
    third party will accept the IDOC XML not the IDOC.
    Just check with ur third party in which format the data is accepted.
    if its IDOC XML then u can use the file receiver adapter and place the IDOC XML file on 3rd party folder.
    You use the IDoc adapter to have IDocs (intermediate documents) processed by the Integration Engine. IDocs from SAP systems Release 3.1x or higher are supported. You can also use the IDoc adapter to connect non-SAP systems to the Integration Engine.
    The IDoc adapter converts the IDocs to IDoc XML format so that they can be processed by the Integration Server pipeline.
    You can also transfer XML in IDoc format received from the Integration Server to connected systems. The Integration Server pipeline must convert the received XML to IDoc XML, and then transfer this IDoc XML to the IDoc adapter. The IDoc adapter converts the IDoc XML to native IDoc format and sends the IDoc to the identified receiver system using the standard IDoc interface.
    Regards,
    Shamma

  • Problem when sending IDOC from ECC to MII 12.0

    Hi all,
       I have followed the document "[How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50775783-6cb1-2b10-90b0-e6bc2c0b8563]" to configure the scenario to send IDOC from SAP ECC 6.0 to MII 12.0.
       But when sending 53 IDOCs by Tcode POIT to MII, I have problem as below:
       - 53 IDOCS were successfully outbounded (list in WE02).
       - 8 IDOCs were successfully sent to MII IDOC listener (these 8 IDOCs messages exist in list of Message Monitor).
       - 45 IDOCS were error with message in SM58: "Bean IDOC_INBOUND_ASYNCHRONOUS not found on host xxx, ProgId=yyy".
       I'm wonder why some IDOCs were successful while some others were error. If the bean  IDOC_INBOUND_ASYNCHRONOUS don't exist in EJB, why some IDOCs successful found this bean?
       I have another wonder: in this scenario document, all IDOC message type (SYNCH, LOIPRO) is configured in outbound parameters of RECEIVER (receiver logical system), why they weren't configured them in outbound parameters of SENDER (sender logical system)?
       If some have the same problem and know how to resolve it, could you please help me?
    Thank a lot in advance,
    Vinh Vo

    Hi Vinh,
    Please read the following document:
    [IDOC Listener|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/bpx-community/manufacturing/how%20to%20send%20an%20idoc%20from%20sap%20ecc%20to%20the%20sap%20mii%20idoc%20listener.pdf]
    If you explicitly defined a Prog ID in NW, then you have done an extra step and are confusing NW with the real destination.  
    In basic terms, you set up an RFC destination (with an assigned ProgID) in ERP, then configure MII to point to it. 
    I suggest that you follow the document completely and do nothing else to set up a new listener. 
    If you are not using ECC 6.0, you may find the paths are different,  but the transactions codes are generally the same.  However, you may want to check with some of the older installation instructions regarding specific modifications.  Look in the Wiki for MII under Connectivity.
    Good luck,
    Mike

  • Sending IDoc from ERP to PI

    Hi all,
    I am trying to sent IDoc's from the ERP (SAP ECC) side to PI. But the IDocs are not arriving at the PI side. In ECC tc:we05 they seem to be successfully sent.
    The Partner Type in we20 is "LI". I added the IDoc to the Outbound parameters and set the PORT to the Port we use for PI. But unfortunately it is not working.
    Any idea why?

    When sending IDoc from ECC System to PI.
    some settings needed on ECC System & PI System
    On ECC System
    Create Port in WE21 type LS (Logical System) use RFC Destination TYPE ABAP in that port.
    Create Partner Profile using PORT in WE20.
    Add the Idoc as Outbound in that Partner Profile.
    Now on PI System
    PI System does not have structure / matadata of IDoc.
    Create Port in IDX1.
    Import IDoc Matadata in IDX2 use Port created in IDX1.
    Create complete scenario & send IDoc from ECC, it will reach at PI System, if successful at ECC.

  • Send idoc from one version of R/3 to different version

    Hi All,
    I have a scenario to send idocs from one R/3 system to another (both have different versions) .Can anyone tell me the step by step way to configure. Do I need to program anywhere to send or receive idocs Any help is really appreciated
    Thanks
    Michael

    Hi michael,
         The version change technique allows you to exchange idocs with systems using the older version of idocs.
    For this v have to configure the sending system to generate back level idoc for receiving system using the partner profile. configuring the partner profile is enough to send idocs in this scenario.
    Regards....
    Arun.
    Reward pts if useful.

  • Sending Idocs from SAP-R/3 to XI, bundle and map them to one XML-file

    Hi All,
    We need to send IDoc's (DEBMAS06) from R/3 to XI and  bundle and map them to a single xml-file. Please help us with your suggestions on how to proceed using a simple solution (probably need of BPM).
    Regards,
    Theo

    Hi Theo,
    there is an example in SAP Library: <a href="http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/frameset.htm">Collecting and Bundling Messages - One Interface</a>. Plz post us your detailed quetions.
    Regards,
    Udo

  • Error sending IDOC from JCO Client to PI AEX 7.3.1

    Hi All
    We have a requirement to send an IDOC from a non SAP System to our ECC via PI AEX :
    JCO.Client --> PI AEX --> SAP ECC
    At this time, we are testing this scenario with a JAVA Client with JCO Library (3.0.10).
    Destination to PI is OK
    Destination to our SAP ECC (for IDocRepository) is OK
    But by sending the IDOC to PI we are getting the following error, Exception is raised on the PI System and sent back to the JCO Client :
    com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: while trying to invoke the method java.lang.Object.hashCode() of an object loaded from local variable 'key' (raised by system <extern>|PiSystem)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:670)
        at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.execute(MiddlewareJavaRfc.java:1881)
        at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:1120)
        at com.sap.conn.jco.rt.ClientConnection.execute(ClientConnection.java:953)
        at com.sap.conn.jco.rt.RfcDestination.execute(RfcDestination.java:1465)
        at com.sap.conn.jco.rt.AbapFunction.execute(AbapFunction.java:319)
        at com.sap.conn.idoc.jco.JCoIDoc.send(JCoIDoc.java:323)
        at com.sap.conn.idoc.jco.JCoIDoc.send(JCoIDoc.java:353)
        at sap_connector_examples.IDocClientExampleToJavaPO_pbs.main(IDocClientExampleToJavaPO_pbs.java:97)
    Caused by: RfcException: [<extern>|PiSystem]
        message: while trying to invoke the method java.lang.Object.hashCode() of an object loaded from local variable 'key'
        Return code: RFC_SYS_EXCEPTION(3)
        error group: 104
        key: RFC_ERROR_SYSTEM_FAILURE
    Exception raised by <extern>|PiSystem
    PI Destination:
    jco.destination.repository_destination=ABAP_AS_WITHOUT_POOL
    jco.client.gwhost=PiSystem
    jco.client.gwserv=sapgw01
    jco.client.tpname=XI_IDOC_DEFAULT_PID
    jco.client.type=E
    ECC Destination: (ABAP_AS_WITHOUT_POOL)
    jco.client.lang=en
    jco.client.client=100
    jco.client.passwd=****
    jco.client.user=User
    jco.client.sysnr=00
    jco.client.ashost=ECCSystem
    We have already set the PI VM System parameter  jco.allow_non_abap_partner to 1
    ECC User has S_RFC Rolle
    I will be thankful for any advise.
    Thank You
    Regards
    Stéphane

    Hi
    InboundRA (Resource Adapter) is green (Fully available).
    What do you mean by maintaining JCO RFC Destination in PI ?
    We have set the inboundRA Properties has follow :
    ProgramID : XI_IDOC_DEFAULT_PID
    DestinationName : XI_IDOC_DEFAULT_DESTINATION
    Local: true
    mutliRepository : ED1=XI_IDOC_DEFAULT_DESTINATION_ED1;ES4=XI_IDOC_DEFAULT_DESTINATION_ES4;MD1=XI_IDOC_DEFAULT_DESTINATION_MD1;ES1=XI_IDOC_DEFAULT_DESTINATION_ES1;PD1=XI_IDOC_DEFAULT_DESTINATION_PD1;
    GatewayServer and Service are pointing to our PI System
    BindingKey : PI_AAE_IDOC
    And for each Repository we created a destination in NWA pointing to the corresponding ECC System.
    (target host pointing to the ECC System and the Gateway host  pointing to the PI System)
    Our Installation isn't new but it is the first time we are configuring the System for this scenario:
    JCO.client --> PI AEX
    Regards
    Stéphane

Maybe you are looking for