Hi all

I hope you will never need this block.

Such a communication is not fine and Sender must change his API.

But all of us know the sentence: On 7.1 it works but now on AEX not ….

 

Below you see the screens how to handle JCO communication by using IDOC_AEE adapter with ThirdPartyJCO-Systems.

BR
Daniel






To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Vikas Kumar Singh

    Hi Daniel,

    A good pick to write about. It is an interesting use case to connect with IDOC_AAE considering many other options available to connect a JCO system  with AEX.

    Is there any open non-sap jco system with which we can test this?

    Regards,
    Vikas

    (0) 
  2. Daniel Güntner Post author

    Hi Vikas

    To play with JCO you have to download the library and then you can easily create your own application.

    There are good samples delivered in the download.

     

    But as I wrote, this kind of connection should not be used in future.

    All non-SAP systems can handle File, SOAP, … so this will be the future.

     

    This Jco solution is only the worst case if the Sender/Receiver system will not be able to communicate with File, SOAP … and only Jco.

     

    Also we PI developer must learn to say goodbye to IDOCs L

    If the clients go to S4 it is important that we all learn to handle and understand the SAP SOA Enterprise Services.

     

    Daniel

     

    (0) 
  3. Prathi T

    Hi Daniel,

    Good guide, Thank you!

    I am working on the similar requirement, sending the IDOCs to non-SAP system through PI. I am following your blog along with the below. I have created a RFC destination for non-SAP in PO system. While pinging the RFC, I am getting an error like “Program “XXXX” not registered. Can you please guide me how to register the program id in PO java stack? Do I need to create a JCo RFC provider with the program id name?

    and also where do we have to maintain the non-SAP system details in PO to identify the non-SAP system?

    https://blogs.sap.com/2014/02/17/idoc-aae-non-sap-communication/

    Thank you in Advance!

     

     

    (0) 
  4. Daniel Güntner Post author

    Hi Prathi

    On your Jco server you have to fill parameter called: jco.server.progid and this must match with the value of NWA Destination parameter jco.client.tpname.

     

    Daniel

     

    (0) 

Leave a Reply