Any dependency on SAP PI to upgrade ECC to EH6 or EH7

[former_member183908]

Hello All,

Good Day.

Need few clarifications on ECC upgrade from EH5 to EH6 or EH7

We are on ECC6 EH5 and hundreds of interfaces(nearly 500+ both outbound and inbound) are connected from ECC to PI711 SP11 and now we have the plan to upgrade our ECC servers to either EH6 or EH7.Do we need to upgrade SAP PI version parallely along with ECC upgrade to support for the runtime components of both SAP ECC and SAP PI?

Appreciate your help in advance.

Thanks

Pawan

[Former Member · Accepted solution]

Yes. Our PI version is 7.31 PO. And yes, we have ECC EHP6.

You should be possible to deploy SAP APPL 6.06 ESR content on PI 7.11. The only pre-requisite is that you have the SLD content available (maybe you need to update the SLD content). Then you can import the SWCVs from SLD into ESR. In ESR you then can import the content to the correct SWCV and you will also see those proxies in the correct SWCV on your ECC backend system (in SAP_APPL 6.06 for example).

The PI version should be independent. The version of the backend systems and the SLD content should be the two relevant parts.

[former_member183908 · Accepted solution]

Thanks For the reply Harald.

I was confused regarding the SLD content which you mentioned.Do i need to import SAP_APPL 6.06 from SLD or do i need to import .TPZ file(XI content which will be downloaded from market place) into my ESR?

The only pre-requisite is that you have the SLD content available (maybe you need to update the SLD content). Then you can import the SWCVs from SLD into ESR. In ESR you then can import the content to the correct SWCV and you will also see those proxies in the correct SWCV on your ECC backend system (in SAP_APPL 6.06 for example).

[Former Member · Accepted solution]

You can do both. ´However there is a slight difference:

1. Import the .TPZ file without the existence of the SWCV in SLD:

When you do this only a local SWCV will be created in ESR. This cannot be transported to a target system (for example from DEV to QA).

2. Check that the SWCV is available in SLD and import it into ESR from there before you do the .TPZ import. Then you have a SWCV containing the ES content which can also be transported in the landscape.

Best Regards

Harald

[nabendu_sen · Accepted solution]

Hi Pavan,

Either you can create Local SWCV or you can import SWCV from SLD (SLD option is better approach). Under the SWCV, you need to import Standard Content. Find the below document where its clearly described:

http://wiki.scn.sap.com/wiki/display/XI/How+to+import+SAP+content+into+the+PI+ESR

Regards,

Nabendu.

[Former Member · Accepted solution]

Correct. But still: Local objects of a local SWCV cannot be transported

Please check this link:

http://wiki.scn.sap.com/wiki/display/XI/Local+Software+Component+Versions

Best Regards

Harald

[former_member183908 · Accepted solution]

Thanks to both of you.Looks like based on your comments it was clear there is no dependency on SAP PI version for the ECC upgrade either to EH6/EH7.

Wondering when we had a initial discussion of ECC upgrade SAP suggested to upgrade SAP PI version as well since the runtime components(NTW components) of both SAP ECC and SAP PI are interdependent(Still not clear whether it is related to only proxy environment or others like IDOC or RFC).

Any of you guys had an environment like SAP ECC6(EH6/EH7) with SAP PI711.Please reply to this thread.I will keep you guys posted on this with the info which i received from SAP.

Very much appreciated

[Former Member]

Hi Pawan,

Are you using standard ES Content from SAP? Then you maybe need to check for not anymore existing software components and its content (i.e. SAP APPL or SAP BASIS could change based on the EHP you are installing).

On ECC therefore you maybe do not see your proxies anymore since the SWCV containing the proxies is not existing on the ECC system anymore.

Best Regards

H.

[former_member183908]

Thanks For the reply.Yes we have standard XI content (SAP APPL 6.03 and SAP APPL 6.04 and FINBASIS 603 and FINBASIS 604)deployed in SAP PI for FSCM interfaces which will communicate through client and server proxies.Are you talking about this ES content?however how does this creates dependency.

Are you taking about the proxies related to standard ES content or the proxies which were generated on service interfaces which were created in SAP PI.

Please help me in detail

Thanks

[Former Member]

Hi Pavan,

Yes correct. Each ES Content (which is based on proxies) is assigned to a specific Software Component Version. In my example below this is SAP APPL 6.06.

The problem is, that you see in ECC only the Software Component Versions which are installed on the system. See below, in tx SPROXY:

If you install a new EHP you should eventually import that SWCV also in ESR and in ID and then change the assigned SWCV for each integration scenario manually.

All the other interfaces based on your own SWCV should not be a problem.

Best Regards

H.

[former_member183908]

As per the above screen shot 1(ICO object) I can understand your PI version 7.3X it can be either AEX or PO and per screen shot 2 looks like your ECC in on ECC6 EH6.Please correct me if i am wrong.

Cant i deploy SAP APPL 6.06 ESR content in SAP PI 711 SP 11?Which will support for proxy communication from SAP ECC6 EH6 to SAP PI711.

Thanks