Skip to Content

In a SAP ERP landscape, if customers are using a lot of PROXY interfaces and performing SAP Process Integration (PI) to SAP Process Orchestration (PO) migration, In which they are upgrading middleware from dual to single stack and they may have a situation during go-live phase. In which they can’t go live with all the PROXY interfaces at once which may have some business impact if for some reason go-live is not successful. This situation occurs more in a landscape where there is an inconsistency with respect to Dev, QA, and PROD environment due to implementation flaws and the customer can’t afford to have a development freeze period during a migration project. In such scenarios, you will have a lot of moving targets and also testing is a big hassle if the landscape is not consistent. I had worked on a project in recent past with similar landscape. After the migration from dual to a single stack, the customer decided to phase-out PROXY interfaces as they were not confident that everything works because of inconsistency in the landscape and lack of testing. So I had to come up with a solution using which we could successfully phase out the PROXY interfaces and have multiple go-lives.

The question may be asked if this a good practice? Answer is NO the reason being if we go with above approach we end up having 2 middleware PROD system in the landscape and supporting 2 systems and monitoring them will be tedious and is not SAP best practice but taking this approach customer will have some sort of relief that go-live can be done in multiple phases and no need to rush to complete migration. It can be done using internal staff which would reduce the project cost to some extent but quality may be compromisedJ

In this blog, I will show the steps which need to be followed to route the PROXY interfaces to both dual and single stack PI and PO systems at the same time.

Step1: In order to run PROXY interfaces we need following connections.

  • RFC connection type H to connect ECC ERP ABAP stack to PI ABAP stack
  • RFC connection type G to connect ECC ERP ABAP stack to PO Java stack

Above mentioned connections needs to be created in SAP ERP system pointing to respective PI and PO systems.

Step2: Execute SXMB_ADM in SAP ERP system and make sure the connection is pointing to PI dual stack as shown in the screenshot below.


Step3: Enter into an edit mode in above screenshot and have the parameter RUNTIME IS_URL which is dynamic URL pointing to dual stack PI system and shown in the screenshot below.


Step 4: Use new G-type connection which you have created in step1 and configure it against the namespaces which you need to route to PO system as shown in the screenshot below.

Note: in the new PO system all the PROXY scenarios are converted into Integrated Configuration Objects (ICO).


Once all the above configurations are completed. Trigger the proxy program from SAP ERP system for both the classical and ICO scenarios and the messages will route through PI dual and PO single stack systems respectively.

Hope this helps!

See you in my next blog!

To report this post you need to login first.

Be the first to leave a comment

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

Leave a Reply