Skip to Content

Developing Applications for Integration between PI and SAP ERP in Different Network Domains or Landscapes

Recently, I encountered an interesting project with an integration scenario, which I know is possible but I have not seen it in practice.


The situation is as follow:  A company with PI wants to integrate with its trading partners, all of whom happen to have SAP ECC systems.  The integration at the partners is to be done with ABAP proxies.  The original proposal is to have PI installed at the partners’ locations.  This allows the proxies to be generated on the ECC systems from the PI’s ESR and allows the integration to be done with PI-to-PI using the XI protocol.  However, this proves to be costly, as each partner will have to obtain a PI license.  (This is good for SAP, but not so good for the partners.)  The additional expense prevented the project from going forward.

As a result, the company requires that the PI system will be able to integrate with the partners’ ECC systems without the partners having to have PI in their landscape.  This presents the following obstacles:

  1. How to generate the ABAP proxies at the partners’ ECC systems without an ESR of a PI system in the landscape?
  2. Can messages be sent from the ECC systems to the company’s PI system through the public internet and the company’s firewall?

As we all know, XI protocol is based on HTTP/S.  Therefore, there should be no problems of sending messages from the partners to the company, as almost all companies allow HTTP traffic to go out to the public internet.  But, how about the company’s firewall setup to allow the internet messages to come in?  How about the generation of the ABAP proxies when there is no ESR? 

A proof-of-concept was done to demonstrate that this is possible.  This article in the link below outlines the detailed steps needed to accomplish the integration scenario:

This article describes the process involved in the ABAP proxy generation without the presence of an ESR in partner’s landscape, and it also demonstrates a simplified firewall setup at the company’s landscape for the integration scenario.

You must be Logged on to comment or reply to a post.
  • Hi William,

    Nice blog. Very informative.
    Is PCK not an option for these kind of partners?
    Partners can install PCK and not have a full blown PI.


    Sudharshan N A

    • Well, like PI, PCK also needs a license, which means additional cost.  Also, PCK does not have an ESR to generate the ABAP proxy.


  • Bill,
    Good Blog! While theoretically this was always possible, its good to know that there are such real world requirements as well. One of the few unique implementations I guess..

    You have mentioned that a SLD is needed on the ERP as on 7.02. How about licensing of SLD? If that included by default in your ERP licensing or is that a additional cost?

    One additional point one should be careful about -> In your WebDispatcher that is used as a Reverse Proxy, URL filtering should be set up to make sure that the ERP system or any user of the ERP system does not hit your PI URL’s.