SRM/Portal upgrade

[Former Member]

we are migrating from SRM 3/EBP2.0/Requisite/EP6 SP2 to SRM5.0/SRM Server5.5/CCM2.0/Portal NW2004s/Solution Manager4.0. Only the shopping cart scenario is implemented and there is minimal customization (the login page has been modified to fit the client look and feel).

Does anyone have experience with this type of migration? we need to understand:

- the timelines required for the migration (assuming this is a pure technical migration, no new functionality added). A detailed activity list would be helpful to have if one exists.

- what are the potential roadblocks, lessons learned etc.

thanks in advance.

[Former Member]

Hi kirk,

Can you please tell me how is it that you did the customisation of the login page? ( Which is the Par file that needs to be modified for this and its location)

I have the same requirement. Infact i got no replies for my post - /thread/155342 [original link is broken]

Please can you help me out.

Regards,

Ashwini

[Former Member]

Hi,

Can you please tell me how is it that you did the customisation of the login page? ( Which is the Par file that needs to be modified for this and its location)

I have the same requirement. Infact i got no replies for my post - /thread/155342 [original link is broken]

Please can you help me out.

Regards,

Ashwini.

[Former Member]

Hi Kirk,

First of all I don't understand your product version: You said you're on SRM 3.0 and EBP 2.0. In fact SRM 3.0 corresponds to EBP 4.0.

If you're really moving from EBP 2.0 to SRM Server 5.5, then be aware of the fact that all SC transactions and programs have been changed: So be carefull, <b>ALL YOUR STANDARD MODIFICATIONS WILL BE OBSOLETE, YOU'LL HAVE TO REDO IT ALL</b>.

ANother point is about the architecture, main changes are:

-IPC is now mandatory for standalone and Extended Classic scenario

-Integrated ITS can be used instead of External ITS

-SAP XI is now the EAI used for SRM in SRM and CCM scenario. It is shipped with pre designed scenarii for SRM and Catalog flows

-You have to choose how you'll install the CCM add-On: My recomandation would be to install the CCM add-on on the SRM Server (on the same client than the SRM to share the basis data)

-No migration tool exists from Requisite Products (BugsEye and Emerge) to CCM product

NB: If you need an SRM expert for your project preparation, please feel free to contact me directly (see my SDN Business Card).

Regards.

Vadim

[Former Member]

Hi Vadim,

in fact you are right, we are on SRM 3.0/EBP4.0/EP6 SP2.

When upgrading to SRM5/CCM2.0/Portal NW2004s, what is the recommended option:

a) to install a fresh copy of NW2004s and then apply the latest SRM business packages or

b) to upgrade Portal from EP6 SP2 to NW2004s?

also, if all SRM components are local, do we still need XI?

what is the role of the CCM add-on?

[Former Member]

Hi Kirk,

1- EP Upgrade

It totally depends on your actual use of your EP version: If you only use SRM BP, then, the fresh install can be more efficient, and even if I'm not an EP specialist, I heard the version 6 of EP has been quite enhanced.

2- XI in SRM

XI is used in SRM scenarios for

-XML Catalog Upload

-Catalog Upload with separated CAT and CSE clients or systems (not your case as I understand)

-SRM SUS exchanges

-PO, POR, ASN, IV Exchanges with Suppliers

Hope it Helps.

Vadim