Skip to end of metadata
Go to start of metadata

1) Technical prerequisites. Check below if the upgrade between Netweaver Portal and Business Suite products is supported.

** Check information from note 2200904 - Official Violation of Version Interoperability for Business Suite 7i2016 and standard limitations for ERP 6.0 EHP0-EHP3 which are not part of Business 7

  • SAP CRM 7.0 EHP4 (CRM Application Server JAVA only) not possible to be installed on NW 7.31 AS JAVA and NW 7.40 AS JAVA
  • SAP CRM 7.0 EHP0-3 (CRM Application Server JAVA only) not possible to be installed on NW 7.50 AS JAVA
  • SAP SCM 7.0 EHP0-4 (WCL and Store UI JAVA Applications only) not possible to be installed on NW 7.40 AS JAVA and NW 7.50 AS JAVA
  • SAP ERP 6.0 EHP8 (SAP XECO only) not possible to be installed on NW 7.31 AS JAVA and NW 7.40 AS JAVA
  • SAP ERP 6.0 EHP4-EHP7 (SAP XECO only) not possible to be installed on NW 7.50 AS JAVA
  • Standard Limitation: SAP ERP 6.0 EHP0-EHP3 (SAP XSS (Self Services), SAP XECO, SAP FSCM – Biller Direct, SAP Learning Sol-Frontend CP, Portal Content) not possible to be installed on NW 7.30+

All the entries in yellow requires the minimum SP stack of the ABAP backend system which supports the specific Portal version if SAP Standard Portal Content or Applications are used.

Business Suite 7 Innovations 2016 (BS7i2016), e.g. EHP8 for SAP ERP 6.0, EHP4 for SAP SRM 7.0, EHP4 for SAP SCM 7.0, EHP4 for SAP CRM 7.0 and SAP Industry Solutions.
Business Suite 7 Innovations 2013 (BS7i2013), e.g. EHP7 for SAP ERP 6.0, EHP3 for SAP SRM 7.0, EHP3 for SAP SCM 7.0, EHP3 for SAP CRM 7.0 and SAP Industry Solutions.
Business Suite 7 Innovations 2011 (BS7i2011), e.g. EHP6 for SAP ERP 6.0, EHP2 for SAP SRM 7.0, EHP2 for SAP SCM 7.0, EHP2 for SAP CRM 7.0 and SAP Industry Solutions.
Business Suite 7 Innovations 2010 (BS7i2010), e.g. EHP5 for SAP ERP 6.0, EHP1 for SAP SRM 7.0, EHP1 for SAP SCM 7.0, EHP1 for SAP CRM 7.0 and SAP Industry Solutions.
Business Suite 7 (BS7), e.g. EHP4 for SAP ERP 6.0, SAP SRM 7.0, SAP SCM 7.0, SAP CRM 7.0 and SAP Industry Solutions.

Example: You have a Netweaver Portal system with the following Portal Content/SAP-XSS Self Services/SRM Business packages and you want upgrade the system to Netweaver 7.3.

BP_ERP5DCO 1.0 - BP ERP05 DEV COLLABORATION 1.0

BP_ERP5ESS 1.0- BP ERP05 ESS 1.0

SAPPCUI_GP 600 - SAP PCUI_GP 600

SAP_ESS 600 - SAP ESS 600

BP_SRM 5.0 - BP for SRM 5.0

These components are installed in version Portal Content/SAP XSS/BP SRM => SAP ERP 6.00 and SAP SRM 5.0, this is not supported and the upgrade of Netweaver 7.3 will fail. 

2) Check notes below. These notes contain detailed information about compatibility between ABAP and Portal Systems. Check the pdf's carefully.


1468349 SAP Business Suite 7 for SAP NetWeaver 7.3 hub systems => Details_BS7EnableNW73_2012CW22.pdf

1615463 SAP Business Suite 7i 2010 for SAP NetWeaver 7.3 hub systems => Details_BS7i2010EnaNW73_2012CW32.pdf

1698276 SAP Business Suite for SAP NetWeaver 7.31 hub systems => Details_BS_EnableNW731_2012CW42.pdf

1874939 SAP Business Suite for SAP NetWeaver 7.4 hub systems => Details_BS_EnableNW74_2013CW44.pdf

2304435 SAP ERP for SAP NetWeaver 7.5 hub systems => Details_ERP_EnableNW750_2016CW14.pdf

Example) You have a Portal system 7.00 with these Business packages below from SAP ERP 6.0 EHP4 and SAP SRM 7.0 and you would like to upgrade the Portal system to Netweaver 7.3. Check note 1615463.

BP ERP05 DEV COLLABORATION 1.0 (This component didn't change the version in from SAP ERP 6.0 to EHP4 for SAP ERP 6.0)

BP ERP05 ESS 1.41

SAP PCUI_GP 603

SAP ESS 603

BP_SRM 7.0 - BP for SRM 7.0

It's possible to upgrade this system to Netweaver 7.3 because all Business packages of SAP ERP 6.0 and SAP SRM 7.0 are compatible with Netweaver 7.3.

These notes “SAP Business Suite for SAP NetWeaver 7.XX hub systems” mainly describes which Business Suite component runs on NW 7.3X/7.4/7.5.

3) Check SAP_UI webdynpro runtime.

Furthermore, the UI Component has been upgraded recently and the old 7.40 component has been getting out of maintenance as of Dec 31st, 2017. An alternative is SAP_UI 7.50, but it comes with prerequisites.

It makes sense to check note 

2476416 End of Mainstream Maintenance for UI Add-On 1.0 and SAP_UI 740

and to eventually upgrade the respective component(s). This will be of importance especially when upgrading a portal having backend systems connected (possible design issues when handing over Portal style sheets to backends).

4) Solution Manager: Points to be checked.

After you fulfill the minimum prerequisites to execute an upgrade to Netweaver 7.3, you must generate the mopz transaction to upgrade to Netweaver 7.3X/7.4/7.5.

  • For ABAP/JAVA systems with:

Business Suite 7 Innovations 2011 (BS7i2011), e.g. EHP6 for SAP ERP 6.0, EHP2 for SAP SRM 7.0, EHP2 for SAP SCM 7.0, EHP2 for SAP CRM 7.0 and SAP Industry Solutions.

Business Suite 7 Innovations 2010 (BS7i2010), e.g. EHP5 for SAP ERP 6.0, EHP1 for SAP SRM 7.0, EHP1 for SAP SCM 7.0, EHP1 for SAP CRM 7.0 and SAP Industry Solutions.

Business Suite 7 (BS7), e.g. EHP4 for SAP ERP 6.0, SAP SRM 7.0, SAP SCM 7.0, SAP CRM 7.0 and SAP Industry Solutions.

You need at least Solution Manager 7.01 SP23 or higher ( You can use MOPZ or Maintenance Planner)


  • For ABAP/JAVA systems with:

Business Suite 7 Innovations 2013 (BS7i2013), e.g. EHP7 for SAP ERP 6.0, EHP3 for SAP SRM 7.0, EHP3 for SAP SCM 7.0, EHP3 for SAP CRM 7.0 and SAP Industry Solutions.

You need at least Solution Manager 7.1 SP10 or higher (MOPZ)

OR

You need at least Solution Manager 7.01 SP23 or higher (Maintenance Planner)


  • For ABAP/JAVA systems with:

Business Suite 7 Innovations 2016 (BS7i2016), e.g. EHP8 for SAP ERP 6.0, EHP4 for SAP SRM 7.0, EHP4 for SAP SCM 7.0, EHP4 for SAP CRM 7.0 and SAP Industry Solutions.

You need at least Solution Manager 7.01 SP23 or higher (Maintenance Planner) 

  • Check note 1887979 for MOPZ and note 2239589 for Maintenance Planner.

Example of complete LMDB configuration of a Portal system connected with ERP and SRM backend

System 1) System JAS Netweaver 7.0 with Portal Content ERP, SAP XSS Self Services and Portal Content SRM components.

  • BP ERP05 DEV COLLABORATION 1.0 (This component didn't change the version in EHP4)
  • BP ERP05 ESS 1.41
  • SAP PCUI_GP 603
  • SAP ESS 603
  • BP_SRM 7.0 - BP for SRM 7.0

System 2) ABAP SRM 7.0 SLS  

System 3) ABAP ERP 6.0 EHP4 SLR

Definition of the instances.

BP ERP05 DEV COLLABORATION 1.0 (This component didn't change the version from SAP ERP 6.0 to EHP4) PORTAL CONTENT (SAP ERP 6.0 and EHP4 for SAP ERP 6.0)

BP ERP05 ESS 1.41 PORTAL CONTENT SELF SERVICES (EHP4 for SAP ERP 6.0)

SAP PCUI_GP 603 SAP XSS (SELF SERVICES)  (SAP ERP 6.0 and EHP4 for SAP ERP 6.0)

SAP ESS 603 SAP XSS (SELF SERVICES)  (SAP ERP 6.0 and EHP4 for SAP ERP 6.0)

The required standalone instances by installed EHP instance should also be marked as relevant/installed.

 For example. PORTAL CONTENT of EHP4 for SAP ERP 6.0 requires SAP NW - EP Core of SAP ERP 6.0.

ATTENTION SAP NW - EP Core' instance of 'SAP ERP 6.0' is required by the 'Portal Content', please also mark this instance as relevant for EPD (for product version 'SAP ERP 6.0'), otherwise MOPZ would delete 'Portal Content' instance in pre-calculation check.

BP_SRM 7.0 - BP for SRM 7.0 PORTAL CONTENT SRM (SAP SRM 7.0)

Configuration of ABAP backend systems

Transaction LMDB => Product system (Not technical system) => SLS => Edit =>  Assigned Technical systems => Add => Select "Technical System Type" Application Server JAVA and Extended System ID JAS => In "Select By" choose Product Version => "SAP SRM 7.0 / NW 7.01" and mark instance "Portal Content SRM"

The result will be the following

System SRM SLS connected with JAS


Transaction LMDB => Product system (Not technical system) => SLR => Edit =>  Assigned Technical systems => Add => Select "Technical System Type" Application Server JAVA and Extended System ID JAS => In "Select By" choose Product Version => "SAP ERP 6.0" and mark instances "SAP NW - EP Core" and "SAP XSS (Self Services)", now select product version EHP4 for SAP ERP 6.0 / NW 7.01 and select instances Portal Content, Portal Content Self Services and SAP XSS Self Services.

The result will be the following: System ERP SLR connected with JAS

Configuration of JAVA Portal system 

Transaction LMDB => Product system (Not technical system) => JAS => Edit =>  Assigned Technical systems => Add => In "Select By" choose Product Version => "SAP Netweaver 7.0" and mark instances "Application Server Java", "BI Java". "EP Core" and "Enterprise Portal" (These instances are just an example, in your Portal system you could have more or less installed instances).

The result will be the following: Portal system JAS

One of the most common issues in JAVA upgrades is outdated components that generate message errors like this:

[Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Validation of deployment queue completed with error: The stack does not match the system. Probably the system was changed after the stack was generated. Synchronize the system with SAP Solution Manager and then generate a new stack.

Software component <software component name> is found on the system but not in the list of expected system components in the stack.

OR

[Error ]: The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Validation of deployment queue completed with error: The stack does not match the system. Probably the system was changed after the stack was generated. Synchronize the system with SAP Solution Manager and then generate a new stack.

Software component <software component name> with version XXXXXX is found on the system but in the stack it is listed with version YYYYYY

Before start the upgrade, ensure that this date is updated and it's not older than 24 hours, otherwise ensure that you updated the information in SLD/LMDB.

Now you can create mopz transactions or Maintenance Planner transactions to update the ERP ABAP, SRM ABAP and the Portal Systems without issues.

More Information

It's strongly recommended check the following documents at http://wiki.scn.sap.com/wiki/x/VIwqCw:

SAP strongly recommends the use of Landscape Verification to check product versions and instances: chapter 4.5 - Verifying Product System Information






  • No labels