cancel
Showing results for 
Search instead for 
Did you mean: 

Querry regarding SRM 5.0 to 7.0

Former Member
0 Kudos

Hi,

We intend to upgrade our SRM 5.0 system to 7.0 version.

Current SRM System package levels are as:-

Software Component Release Level Highest Version

SAP_BASIS 700 0014 SAPKB70014

SAP_BW 700 0016 SAPKW70016

1) Our ECC system is at SAP ERP Central Component 5.0

Current ECC System package levels are as:-

Software Component Release Level Highest Version

SAP_BASIS 640 0019 SAPKB64019

SAP_BW 350 0019 SAPKW35019

As per the above info is it feasible or the SRM 5.0 to 7.0 upgrade compatible with ECC remaining at 5.0 (we plan for ECC upgrade later) or first ECC needs to be upgraded to 7.0 level and the SRM can be upgraded?

2) We don't have PI, XI and Trex in our SRM system as of now .... will they be needed in case we upgrade our SRM to 7.0 or can they be treated as optional.

3) Is there any specific hardware requirements 9in terns of compatibility for higher SRM version). Can you help in suggessting some document link to check for pre-requisites before starting this upgrade or if you could post them here itself.

Thanks a lot!!

Regards,

Ashish Robinson

Accepted Solutions (0)

Answers (1)

Answers (1)

peter_novoth
Active Contributor
0 Kudos

Hi Ashish,

1) The SRM 7.0 is compatible with the ECC release 5.0, so you don't need to upgrade the ECC in the same time.

2) From the EhP 4 of the ECC 7.0 backend system, the 60% percent of the communication is based on the ESOA technology. Without XI you cannot use the system.

3) Please check the link: https://websmp209.sap-ag.de/sizing

Regards,

Peter

Former Member
0 Kudos

Hello Peter,

A question regarding remark 2. Although ECC EHP4 'requires' ESOA for communication this feature can still be disabled as with any feature contained in an EHP? Also SAP promised to deliver non E-SOA communication for SAP SRM as per EHP1 release, correct?

Kind regards,

Tim

peter_novoth
Active Contributor
0 Kudos

Hi Tim,

I have no information about a non-ESOA technology plans.

Theoretically it would be possible to use the old drivers, but in this case you will need to develop a lot (you need to change the PO driver, the contract driver etc.) because the standard will use ESOA.

Regards,

Peter