Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata
 

Contents

The following page discusses different topics regarding System dependeny. It will focus on the Upgrade Dependency Analyzer tool and answer the question what you have to check in your system landscape if you would like to perform upgrades to releases beyound SAP Business Suitde Innovations 2011.

Upgrade Dependency Analyzer

The purpose of performing an upgrade dependency analysis is to check whether the upgrade of an SAP component in your system landscape will have an impact on other SAP components in your system landscape. As you can only check a combination of two components at a time, you should perform the analysis for those combinations of components in your system landscape that have a technical and functional connection.

You can enter the SAP Upgrade Dependency Analyzer by entering “http://service.sap.com/uda”.

 

A new window will be opened where you can enter your source and target product version. As an example below there is an upgrade planned to EHP6 and we would like to check the interoperability with an existing SAP ERP 6.0 system.

 

 

There are different results. In our case there is an independent upgrade possible and we do not have to be concerned about any troubles with cross-system functionalities.

Below there is an overview with all possible results:

No known upgrade dependencies, independent upgrade possible

When upgrading to the target component, all standard cross-system functions that worked prior to the upgrade will be retained. New cross-system functions may require an upgrade of the existing component you have specified.

Independent upgrade possible, but with known restrictions

When upgrading to the target component, all standard cross-system functions that worked prior to the upgrade will be retained. If there are restrictions, you will find them in the attached SAP Note. These restrictions may comprise one or more of the following. After the upgrade:

  • Some cross-system functions may require adjustments
  • Additional SAP Support Packages may be required
  • Additional manual steps may be required

Independent upgrade not possible

After the upgrade to the target component, some or all standard cross-system functions will no longer work. It is required to also upgrade the existing component you have specified, or you may have to manually implement those cross-system functions in a different way.

No interaction

The two components you have specified have no standard cross-system functions in common or the releases specified are indicating an existing release combination with no standard cross-system functions. No direct interaction exists. You can upgrade the components independently.

Currently no statement available

The upgrade dependency information for the components you have specified is currently not available or one of the product versions you have selected is already in customer specific maintenance.

No interaction in existing release combination

The releases specified are indicating an existing release combination with no standard cross-system functions in common. No direct interaction exists before the upgrade. You can upgrade the components independently.

Loss of cross-system functions

After the upgrade to the target component, some or all standard cross-system functions will no longer work. You need to manually re-implement those cross-system functions in a different way. It is not possible or sufficient to upgrade the existing component.

The following two examples will provide an impression on how to use that tool:

 

Back to top

Strategy beyond SAP Business Suite Innovations 2011

All versions/enhancement packages for SAP Business Suite core applications (ERP, PLM, SCM, SRM, CRM) mentioned in SAP‘s Release Strategy for Large Enterprises with a Release To Customer (RTC) date from 2013 onwards will require SAP NetWeaver Systems 7.30 or higher if they are based on or operate with:

  • SAP NetWeaver Enterprise Portal (EP)
  • SAP NetWeaver Business Warehouse (BW)
  • SAP NetWeaver Process Integration (PI)

Customers wishing to utilize SAP Business Suite applications with RTC from 2013 onwards, that require one of these central SAP NetWeaver Systems, will have to upgrade their central NetWeaver Systems to 7.30 or higher before upgrading e.g. to SAP Enhancement Package 7 for SAP ERP 6.0.

You can find more information at “http://wiki.scn.sap.com/wiki/x/yAB8E”.

 

Back to top

  • No labels