connection settings for ECC system to PI

[Former Member]

We have ECC in our landscape. Single stack PI is connected to it. ECC is used in sender, receiver and also in standard content scenarios.

They have decided to change the Client number from 140 to 180

They want all the scenarios to be working in 180

IN PI single stack, I will have to create all the configuration objects again?

Also do I have to create RFC destinations again in Client 180 to connect with PI

Are RFC destinations client specific?

I have many type G connections in 140.

what are he steps for this

[iaki_vila · Accepted solution]

Hi Midhun,

IN PI single stack, I will have to create all the configuration objects again?

There is not need in the most cases, because they are not client specific.

Are RFC destinations client specific?

If you are using RFC communication channels, these are client specific.

Also, you have to pay attention if you are using ABAP proxies, because ABAP proxy configuration is client specific as well.

Regards.

[Former Member · Accepted solution]

I am saying for connecting ECC system to PI single stack. I need to create an RFC Destination of SAP_PROXY_ESR. I have creatd it as we have lots of ABAP proxy scenarios

Will I have to create this again in client 180?

2) Is it possible to create this with the same name? When you create SAP_PROXYESR, will it say that the RFC connection already exist?

3) is it possible to use same name in both client 140 and 180?

[former_member186851 · Accepted solution]

Hello Midhun,

I guess RFC destinations are not client independent.

you can access the same destinations across clients.

[pvishnuvardan_reddy]

Midhun,

just to add here, you need to create a business system for the new ECC client in the SLD of PI system. And you need to import it to ID and arrange the corresponding objects under it.

As you might have know, this is a good practice always, so that any one who looks at the business components will come to know the overview of the interface flow.