Hi,
As such EHP5 upgrade does no have any dependency on underlying NW version of portal system. But since you are using ESS/MSS and ESS/MSS business packages are installed on portal. You should upgrade your ESS/MSS component to same version as your ERP system.
Thanks
Sunny
Hi,
Suggest you to check SAP Note 1324838.
Incase your Portal system (with ESS and MSS) is connected only to the ERP 6.0 ABAP system (which is to be updated to EhP5), then the NW Portal system is referred to as a Local Sidecar. If this is the case, then you need to update the Netweaver part as well as the ERP Java applications on the Portal to SAP ERP EhP5 levels.
However, if the Portal having ESS and MSS, is supporting multiple business applications and connects to mutiple backends like SAP SRM, SAP ECC etc - then you could keep the Netweaver part untouched - referring to as the Hub system.
Check the usage of your Portal system and proceed accordingly.
Regards,
Srikishan
Thanks Sunny and Srikishan.
Alright, in my scenario, EP works as local sidecar where it merely connected to ERP6 for ESS/MSS.
If EP (web as java) runs as local sidecar, should i assign it as a technical system for ERP system?
Thanks,
Nicholas Chang
Edited by: Nicholas Chang on Nov 28, 2011 3:44 PM
Hi,
No, You should not mark it as Technical ERP system. Mark it as SAP Netweaver only, but in system definition you can mark Self Service as relevant instance and you can get the packages.
Thanks
Sunny
Hi Sunny,
Thanks for the clarification. However, LMDB is really giving me headache where i can't edit using SMSY. Previously, working in SMSY took me 5-10 mins but LMDB takes me few hours just for simple product assignment.
My problem is everything's fine in SLD but however, in SMSY, my EP6 instance is automatically assigned as "JAVA" system. I've changed it to SAP NW7 in LMDB, however, the changes doesn't implicate to SMSY, where i believe it should sync once it detects any changes. Due to this reason, i can't assign my EP6 to any logical component and generate the MOPZ.
fyi, we're on SOLMAN 7.1 SP03, latest note applied and CIM and CR content upgraded to latest.
Any idea?
Thanks,
Nicholas Chang
HI,
Your system is EP6, so you cannot define it as NW 7 system because it is NW 2004 system.
Thanks
Sunny
Hi,
As per below link:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/MaintenanceofProductintheSystemLandscape#MaintenanceofProductintheSystemLandscape-GenericRulesforproductassignment
It states as below for Generic Rules for product assignment:
Application Server Java: Technical Systems of type Application Server Java are also created automatically via SLD content synchronization. Similar to type AS ABAP the product version and product instance information need to be maintained manually for all Technical Systems running on Netweaver prior 7.02.
Thanks
Sunny
Yes, Sunny, i've went thru the wiki and manually assigned the product instance. However, the changes doesn't sync from LMDB to SMSY.
I'm currently running a full sync from SLD to LMDB once more and see how it goes.
Thanks for the help!
Cheers,
Nicholas Chang
Hi,
As per LMDB guide, LMDB does not support sync from SLD of release lower than EHP2. So, you need to manually assign the product version in LMDB editor. Following is the path to do this:
In SAP Solution Manager u2013 Work Center (transaction SOLMAN_WORKCENTER), choose SAP Solution Manager Administration Landscape Define New Query and select a system. Then choose System Operations Display System.
Thanks
Sunny
Thanks Sunny, i've went thru the wiki earlier.. however, i manager to solve part of the problem and i've created a new thread under solman section.
LMDB + landscape verification really complicate my life and giving me headache.... especially we need to generate MOPZ for correct component.......
Thanks everyone for the help!
Cheers,
Nicholas Chang
Hi All,
Couple of weeks back we too had the same issue. In solman 7.1 sps03, the bg jobs to configure/sync the SMSY / LMDB / MOPZ data run for days. Previously it used to take 60 minutes!
Regards,
Srini
