Go/No go criteria for an Upgrade Project.

[former_member723628]

Can someone please provide information on Go/No go criteria for any Upgrade Projects. What are the key factors which should be considered for any Upgrade project?

Regards,

Gajendra Bhatt

[Former Member · Accepted solution]

The main issue with any upgrade is how many of my key critical processes are custom developed. If I have too many custom developed objects in the system, if I altered SAP standard too much, can I upgrade and in a timely manner? How much of time can I spend on testing thoroughly the upgraded system to check if I broke any of my key processes? How much disruption can I afford in my live production system, to roll out the upgrade? If I don't upgrade, will I risk running out of support?

These are some of the questions one should ask before making a go/no go decision. Of course, will I meet the deadline, and will I meet the budget are two other factors. Do I have resources to do the upgrade, testing etc.

[former_member723628 · Accepted solution]

Hi Srinivas,

Thanks for the reply. Actually I'm looking for checklist for Go/No Go for an upgrade project.

Regards,

Gajendra Bhatt

[Former Member]

Here are some of the key factors that force TO GO to Upgrade Project:

1. Current version that the customer is having. If it is

3.X version, then the customer might have implemented

very long back and his support contract would be

getting expired. It would be difficult for the customer

to maintain the system without SAP support. If customer

go for Upgrade then SAP would extend the support in the

new contract. This would be a major factor for the

decision of TO GO to Upgrade.

2. Customer business expansion plans/business prospects

with different kind of systems like R/3, R/2, web based

etc., systems which will force to go Upgrade. Because

new versions of SAP is having different flavors of

interacting with other systems. So this would save

more man hours in the future, if they can upgrade

their central R/3 system.

3. The amount of customization they did in the current

version, which would be automatically coming in the

new versions. This would be like credit card process

in sales etc. This switch over will make them more

maintenance free system that reduces the future costs.

These are some of the factors that will force the customer

to go for an Upgrade.

Not to go scenarios would be

1. If the customer is already in the nearer version and

most of the new features are already available, then

it would not be required.

2. If the project the duration is going to be very long

as per their processes, which would increases the cost

3. If more customization process has been implemented

which would not be available in the newer versions

Hope these would be helpful for your analysis.

Regards,

Sivapratap Reddy

[Former Member]

I have the same sitution for a Life Science client who wants to upgrade to ECC6.0 If you received the Go/No go criteria can you share the document with me.

Rick Washington