Problem solve Get help with specific problems with your technologies, process and projects.

Upgrading is two-fold : A look at the technical and functional side

We implemented EBP 3.5 in the classic mode last year (after 1+ years of deciding). We are now looking at upgrading to SRM 4.0/EBP 5.0. What are the major improvements/benefits available to us? With EBP 3.5 going off support in June 2006, we are pulling our upgrade team together now.
I view upgrades as two fold:

Technical Upgrades: Most customers do these to attain a technology platform which provides them the opportunity to do more and gain additional stabilization (eg. NetWeaver) or to quickly get to the current release supported by SAP (case mentioned).

Functional Upgrades: Customers do to gain access to functionality that assists their organization to gain additional process strengths and a competitive advantage.

The thing with functional upgrades is that it requires a better understanding of your current environment and functionality being utilized in the existing solution. As a starting point I usually refer organizations to review the "Release notes" for the solution. SRM 4.0/EBP 5.0 has release notes available that can provide you the information on what's new. If you don't have access to one, let me know and I can send you a copy. Another resource would be the ASUG presentations.

Usually I recommend organizations to hold a half day to one day workshop to understand the functionalities available in the new release and more so co-relating the improvements with your current environment.

Dig Deeper on SAP selection and implementation

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.