Hi
I would appreciate feedback from those who have completed a similar SRM upgrade and lessons learnt. The need of the upgrade is due more to the fact that the current version is going out of general support next year than particularly seeking certain functionality..on saying that it doesn't make sense not to take full advantage of new features offered...and going to the latest version. However the cost in time and risk of dramatic changes to the existing system needs to be taken into account e.g. impact of going to ABAP web Dynpro based screens and what that means to custom developments that have been made to existing screens etc.
The landscape looks like this...we are interested both on the consequences to the direct SRM components and upgrades to other components e.g. Portal
Current landscape SRM 4.0, XI 3.0, BW 3.5, TREX, SAPGui 7.10, ERP 2005 (using extended classic), + Portal 70( currently not used to deliver SRM functionality)
Likely Landscape to upgrade to
SRM 7.0 (NW 7.01), PI 7.1, BI 7.0. TREX 7.0...ERP2005 (possibly need to go to EHP4)...Portal 7.0 possibly part of the upgrade to EH1 for Netweaver.
in the FAQ on upgrading to SRM 7.0 it states that the Portal is now Mandatory...is this correct and if so what is delivered via the Portal?
Does ECC6 need to be on EHP4.....will EHP5 bring any significant offerings?
Again the above questions is to understand the impact that upgrading one or more components will mean on the others.
Appreciate thoughts on the catalogs and use now of MDM and how can this be intergrated into the landscape?
Trying to understand full impact accross complete landscape....the upgrade is one option...when the main driving is staying in support
Other options that should be considered ....
many thanks in advance for any advice or lessons learnt you can offer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.