SAP NW 7.01 AS Java SP upgrade problem MOPZ (BP ERP05 ESS)
This time we had scheduled the upgrade of BI Portal EHP1 NW 7 AS Java SP11 to SP16 running on Linux + Oracle using SUM
System was maintained in SMSY of Solman as product version SAP EHP1 for SAP NETWEAVER 7.0 with these product instances:
- ADS
- AS Java
- BI Java
- Development infrastructure
- EP Content
- EP Core
- Enterprise portal
The system components versions were syncronized by SLD with Solman NW7.01
- steps to syncronize the NW AS Java (version 7.0x):
visual administrator of NW AS Java, Services – Data supplier – Http settings – set hostname of Solman, port of Solman Java Stack, SLDDSUSER and password.
Save and press the button Syncronize (flash icon).
After popup windows appears confirming that the syncro was successful go to Solman ABAP – tx SMSY_SETUP, select SLD and press the button to launch the update. (Y to perform non-test update)
After Job Landscape_fetch ends (you can check in tx SM37) go to tx SMSY to check the Product system and Technical system.
Everything seemed OK, so we have gone to tx DSWP (Maintenance optimizer) and generated stack for the system, but we got a problem:
BP ERP05 ESS MOPz problem
EHP Component BP ERP06 ESS 1.41 without suitable Technical usage!
Firstly we were considering the undeploy of the component, because it was installed on development system without reproducing to QAS and PROD environments.
I found on SCN this article:
http://wiki.sdn.sap.com/wiki/display/ERP6/SAP+Netweaver+7.3x+hub+systems+upgrade
which describes the steps to resolve the problem.
Basically we were missing another product version assignation at our NW AS Java – the EHP4 for ERP 6.0 / NW 7.01
So we added the product version and under the SAP ERP ENHACED PACKAGE appeared the new product version of portal. Without any product instance assignation of course.
In the document on SCN we have found out that for our component – BP ERP06 ESS we need to assign the product instance Portal Content Self Service (and add corresponding Technical system)
Than we have just saved the changes and generated the stack again, this time without any issue!