EHP 7 upgrade & Mopz in Solman 7.1 SP 8

[Former Member]

Hi Everyone,

I am currently working on EHP 7 upgrade for my ECC 6 EHP 6 system. I began my work in ECC with SLD data push and SMSY, LMDB config, in Solman now moved on with MOPZ config to download EHP SPS. I have a query here, is it important to have the entire system data updated with SMSY and LMDB in Solman? i understand that MOPZ checks the current system Patch level from SMSY/LMDB and based on our target selection it calculates and recommends. just wondering how exactly it happens!. Bacause we have our BO system and few other non SAP systems in the landscape that are not updated with the SMSY/LMDB but they also should be considerd for the upgrade to check if there are dependencies.

so my question is, do we have to push data from non sap also and maintaine in SMSY and LMDB before we perform EHP SPS download from MOPZ?

other question is, if we perform upgrade in a ECC Sandbox environment (usually a copy of Production), it is not necessary to have sandbox for Portal, PI and other systems. so what is the recommended approach here? do we have to select the Developement  ECC system from MOPZ so that we will have other Dev systems (PI, Portal.,..etc) present in the SMSY & LMDB and MOPZ recommendation will be perfect?

please help me understand this

Thanks,

Shiv

[bxiv · Accepted solution]

There is a guide on the SDN/SCN that explains how to have BO submit its data to the SLD, but its not as easy as an ABAP or Java stack system; keep in mind that BO has to be on certain SP levels of its own for some things to work correct (CTS+ as an example).

For your initial testing upgrades in Sandbox, run mopz for your Prod systems and when you generate your stack.xml file, open the file with notepad (or your favorite editor) and replace your hostname, sql server hostname, SID (this are typically the 3 that changed when you use the same stack file for each environment).  When you run through SUM it will inform you of a problem if something was missed in the stack for your replacements.

This is also the importance of the solution groupings in SolMan, the solution will validate every Prod system with requirements; in my company's case we had to upgrade PI from 7.11 to 7.3 or higher in order to interface with ECC Ehp7.

Now the most important part is to ensure your landscape data is consistent across your landscapes, if you have various SPs installed and have different levels or snotes in some systems that don't exist in other systems; its in your best interest to fix those before attempting upgrades or you will potentially face different upgrade problems every time. 

If you need to quickly validate landscape data I suggest you review 'Config Validation' under the RCA work center; this will query all systems that you submit and show you all the information for SPs, snotes, custom information if you build it, etc.

[Former Member · Accepted solution]

Hi Billy,

Thank you for sharing such a useful information with me. Futher , I have 2 requests to make

     1. Currently, in SMSY , under the 'Landscape Components' -> 'Product system', i got SAP ERP, SAP ERP Enhancement package, SAP Netweaver, SAP Solman and Successfactor and so on. More Importanatly my ERP system (ECC 6 EHP6 SPS3) is listed in "SAP ERP", "SAP Enhancement Package" and "SAP Netweaver" product Systems. This is confussing because, while choosing EHP Product version from MOPZ, i got this message "SAP ERP6.0 will be updated to related stack SAP ERP 6.0 SPS 25". But my existing system is already at EHP 6 SPS3. i am not sure where am I making mistakes in SLD data push.Also, while choosing "Logical component" for "Solution landscape" under "system groups and logical coomponents", there was no "ERP EHP" listed. so I would seek your assistance in configuring 'Solution grouping' too..

2. I checked dependency throguh UDA and found that there are no dependencies for Portal 7.3, PI but could not check the dependency for BO as this is not listed in Product/Product version/Product Instance. May i know How can i check if there is any dependency for BO system while going for EHP 7 upgrade. also i could not see PO (Process Orchestration) listed in there.

thanks,

Shiv

[Former Member · Accepted solution]

Did you get a chance to look at my queries ?

thanks,

shiv

[bxiv · Accepted solution]

Instead of reviewing SMSY, you should switch over to the LMDB as it is the future for system data in SolMan.

The reason its telling you ERP 6.0 SPS25 is because it is not taking into account your Ehp, SAP still has to support customers who haven't taken the Ehp (perhaps unicode issues, 32 bit to 64 bit, etc) so this is a way to compare.  I found a bar graph that explained this in a very simple picture, however I can't find it online and leads me to believe I read/saw it in a book.  Also think of this my company is currently updating ECC from Ehp 5 SPS 4 to Ehp7 SPS 4, the SPS are the same due to the Ehp change and resetting the SPS counter back to 0, but in mopz I believe it shows SPS 28 or 29 for ECC 6.0; so essentially there is nothing you can or need to fix for the system data.  If this is still confusing I will try to track down the bar graph example I saw.

As for logical components you can create your own (and is advised to do so as SAP could remove entries on you during a SolMan upgrade) so you could list it as z_ERP or zEhpERP or z_ECC; however it makes sens to you and your co-workers/customer, when you manage the system and the button that allows you to configure the system, the first section in the new window stays red until you assign a logical component to the system.  So you might already have something assigned to the system(s).

SAP doesn't list it as BO, and I'm not sure if you can run a successful mopz on BO systems; if you leverage the PAM at SAP you can track down dependencies.  I also believe Process Orchestration is only 7.3/7.31/7.4 which is compatible with Ehp 7.

SAP PAM:  http://service.sap.com/pam

As for BO, do you have the following under the SWDC?

Installations and Upgrades - B" SBOP BI platform (former SBOP Enterprise)" SBOP BI PLATFORM (ENTERPRISE)" SBOP BI PLATFORM 4.1

[divyanshu_srivastava3]

MOPZ does calculate dependencies when you have define the landscape pattern in LMDB. Also, if technical systems are related to other product systems, like ECC and Portal, MOPZ consider the dependencies between them

Divyanshu

[Reagan]

I am not an expert on Solution Manager, but my understanding is that MOPZ will generate a stack file for a particular system. If Technical systems have relation to other systems how will MOPZ identify the dependencies involved ? Just curious to know.

Regards

RB

[divyanshu_srivastava3]

Hi RB,

Have a look at this note.

1903447 - Hub systems - What they are and how to define them in LMDB and SMSY

The consideration is only made when the landscape patter is define and a technical system is part of another product system.

Divyanshu

[Matt_Fraser]

Divyanshu is correct, however, it depends on how you have defined your solution landscape within SolMan.  If you create just one "solution" and put ECC, Portal, BI, PI, etc, all into it, and define various "hub" and "sidecar" systems as appropriate, then MOpz should calculate Minimum dependencies.  This makes the solution much more complex to maintain in SolMan, of course, and it's certainly possible to have these systems all in separate solutions, in which case MOpz will not consider dependencies but will assume each one is standalone.

Also, it isn't necessary to only define production systems in SolMan.  You can have your DEV and QA systems in there as well; you just mark the production systems as such in the solution definition.  This way MOpz will create stack files for all the systems, not just PRD, so manual editing of the XML file shouldn't be necessary.  Billy is correct, however, that if your DEV, QA, and PRD systems aren't in alignment with regard to support pack levels especially, and applied notes secondarily, then you are going to have problems.

As for whether it's necessary to have sandbox portal, PI, etc, matched to your sandbox ECC, no.  You certainly can, and maybe should, but you don't have to.

Regards,

Matt

[Reagan]

Thanks Matt and Divyanshu.

I wasn't aware of this information.

Regards

RB

[Reagan]

Hello

Bacause we have our BO system and few other non SAP systems in the landscape that are not updated with the SMSY/LMDB but they also should be considerd for the upgrade to check if there are dependencies.

MOPZ is not going to calculate the dependency of the system with the other systems (SAP/Non-SAP).

MOPZ takes care of the dependencies of the components installed on the system to be upgraded.

If you want to know the upgrade dependencies with connected systems then you need to make use of the UDA tool.

other question is, if we perform upgrade in a ECC Sandbox environment (usually a copy of Production), it is not necessary to have sandbox for Portal, PI and other systems. so what is the recommended approach here? do we have to select the Developement  ECC system from MOPZ so that we will have other Dev systems (PI, Portal.,..etc) present in the SMSY & LMDB and MOPZ recommendation will be perfect?

Again, MOPZ is executed against a system to create a stack file for the system to be upgraded. It is not going to check the dependencies with other connected systems.

Regards

RB

[Former Member]

Hi,

can somebody help on this?

Thanks

[divyanshu_srivastava3]

Hi Shiv,

Depends on the systems that is interlinked with your ECC system. For eg. XI 7 won't be supported with EHP7. Portal goes in sync with ECC. Non-sap system linked with ecc through add-ons or connectivity needs to be checked from sap and its vendor.

On an whole,  you understand your system integration better than anyone else. So, you have to check before upgrade.

And yes, not all, but all sap products connected with ECC should be their in LMDB with landscape pattern, if you won't to consider other products too.

Divyanshu