Equivalent SP levels for NetWeaver PI 7.1 Java components
[Net] [netweaver] [SAP] [sap netweaver] [soa netweaver]
Related:
- NetWeaver BPM: Issue in SCA component generation in GLX SCDLSymptom Problem with SCA component generation in GLX SCDL: The...
- Central Note: Upgrade to Systems on SAP NetWeaver 7.0 JavaSymptom Errors in the upgrade procedure or in the upgrade...
- Support Package Stack Guide – SAP NetWeaver PI 7.1Symptom Support Package Stack Guide – SAP NetWeaver PI 7.1...
- Upgrade to SAP NetWeaver Process Integration 7.1Symptom Errors in the upgrade procedure or in the upgrade...
- Support Package Stack Guide – SAP NetWeaver 7.0Symptom Errors in the update procedure or in the Support...
- NetWeaver BPM: Improved error reporting in process historySymptom NWA Process history for suspended process instances only displays...
- SAP NetWeaver 7.0 EhP1/Business Suite 7 – IBM iSymptom ****************************************************************** * * Installation on IBM i * *...
- Central Note: Upgrade Systems on SAP NetWeaver 7.0 EHP1 SR1Symptom Upgrade to SAP Systems based on SAP NetWeaver 7.0...
Symptom
You want to upgrade to SAP NetWeaver PI 7.1 and are unsure which Support Package level you require in the target release.
If you choose a Support Package level which is too low, certain SAP components are not upgraded.You may experience the following effects:
1. During the BUILD_COMPONENT_LIST phase in PREPARE, certain SAP components on the “Component List” screen have start release versions and “scan inbox” operation instead of “deploy”, and it is not possible to continue unless you change the operation to “keep” for all of them.
2. In some cases, you may experience severe failures during the upgrade or malfunction of certain components after the upgrade.
Other terms
SAP NetWeaver Upgrade; Java upgrade; SAPJup; UPGRADE; PREPARE; BUILD_COMPONENT_LIST; BIND_SUPPORT_PACKAGES; equivalent SP levels
Reason and Prerequisites
The target release that you want to upgrade to, must have at least an equivalent Support Package level in the source release. For example, Support Package 21 for SAP NetWeaver ‘04 contains the same corrections as Support Package 05 for SAP NetWeaver PI 7.1. This means that they are equivalent. If your source release has a certain Support Package level, you cannot upgrade to a target release that does not include the equivalent Support Package.
The equivalent SP levels are at the moment not checked by the Java upgrade tool. Therefore, make sure that you have checked the table below before starting an upgrade.
Solution
SAP recommends to always upgrade to the latest Support Package level.
You need at least the equivalent SP level in your target release as specified in the following table:
SAP NetWeaver’04 SAP NetWeaver PI 7.1
——————————————–
SP20 (or lower) SP4 (or higher)
SP21 SP5 (or higher)
SP22 SP6 (or higher)
SP23 SP7 (or higher)
SP24 SP8 (or higher)
SP25………………..(TO BE RELEASED)
——————————————–
SAP NetWeaver 7.0 SAP NetWeaver PI 7.1
——————————————–
SP13 (or lower) SP4 (or higher)
SP14 SP5 (or higher)
SP15 SP6 (or higher)
SP16 SP7 (or higher)
SP17 SP7 (or higher)
SP18 SP8 (or higher)
SP19………………..(TO BE RELEASED)
——————————————–
Either use a Java DVD with the correct equivalent SP level (or higher) of SAP NetWeaver PI 7.1, or include Support Packages of the correct level for all SAP NetWeaver components during the BIND_SUPPORT_PACKAGES phase in PREPARE (”Support Packages” screen). For more information, see the Java upgrade documentation available on SAP Service Marketplace.