Skip to Content

What is the approach to switch interfaces in PI connected to R/3 system, to upgraded ECC system ?

Certain interfaces in PI are connected to a SAP R/3 system. Now, the R/3 system is being upgraded to ECC system. Therefore, what is the approach to be followed in PI to route all corresponding interfaces from old R/3 server to new ECC server?

Add comment
10|10000 characters needed characters exceeded

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Feb 27, 2017 at 12:26 AM

    Well that purely depends on how PI is configured. You would need to update all communication channels that are connecting the the R/3 server to connect to the ECC server. If you are on single stack PI you will need to update your SLD and NWA to make sure the appropriate server and clients are maintained for your technical/business system. If you are not using the advanced adapter engine the likelihood is you can maintain each communication channels connection details individually.

    You will also need to create a logical system to PI, Partner Profile, Port and RFC Destination to PI, within the new ECC system (WE21, WE20, SM59). You may also need to maintain a distribution model (BD64) for any ECC outbound IDocs.

    Add comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 27, 2017 at 12:38 AM


    In our case we are doing the same while we execute an enhancement pack upgrade from EhP4 to EhP8. We have a QA SLD which we are using for unit testing and we have simply adjusted the business system configuration in that SLD to point the proper business system to the new technical system while updating the SLD cache in the Integration Directory. With a QA SLD, we can flip back and forth as required with some level of coordination but if you are only restricted to one SLD then you would likely be stuck with creating duplicates of all configurations.


    Ryan Crosby

    Add comment
    10|10000 characters needed characters exceeded