Mopz giving warnings when generating stack file for EHP6 from ERP6 EHP5

[former_member286941]

HI,

We have set the SMSY, LMDB, and product system selections according to our current applied software components of ERP6 EHP5.  But still we are facing the issue when generating the stack file,

13:17:40  Evaluate failed for product Instance Process Integration (PI/XI) (SAP EHP2 FOR SAP NETWEAVER 7.0)

13:17:40  Evaluate failed for product Instance BI Content Extension (SAP EHP2 FOR SAP NETWEAVER 7.0)

13:17:39  Evaluate failed for product Instance Business System 6.20 PI/XI (SAP EHP2 FOR SAP NETWEAVER 7.0)

13:17:39  Evaluate failed for product Instance Mobile Infrastructure (MI) (SAP EHP2 FOR SAP NETWEAVER 7.0) 

13:17:35  Evaluate failed for product Instance Business Intelligence (SAP EHP2 FOR SAP NETWEAVER 7.0) 

Tried adding them in LMDB but these are giving same warnings again.

The below are the wanings which can’t be ignored, 

Later at OS/DB select files phase this is giving error in proceeding these are showing as errors.

Also these are the warnings:

Product registration of installed Add-Ons is missing! 
Display Help
Java Instance AS Java of ERP product system is not marked as relevant! 
Display Help
EHP Component BP ERP05 QUALITY INSPECT 1.31 without suitable Technical Usage!
EHP Component BP ERP05 INT SALES REP 1.2 without suitable Technical Usage!
EHP Component BP ERP05 HR ADMINISTRATOR 1.11 without suitable Technical Usage!
EHP Component BP ERP05 ESS 1.41 without suitable Technical Usage!
EHP Component BP ERP05 COMMON PARTS 1.31 without suitable Technical Usage!
EHP Component SAP PCUI_GP 603 without suitable Technical Usage!
EHP Component SAP ESS 603 without suitable Technical Usage!
EHP Component IS FS ICM APP 603 without suitable Technical Usage!
EHP Component BPERPESSWDA1.50 without suitable Technical Usage!
EHP Component BP ERP05 MSS 1.31 without suitable Technical Usage!

We have already done this for one test sytem in this landscape, but this dev system seems having some more components therefore we are trying to generate this one. Please suggest if someone got this error earleir.

Regards

Munish

[Miguel_Ariño]

Hello,

The 'evaluate failed' error messages generally speaking mean that the product instance is not installed but it is marked.

They are warning messages, not error messages, so they should not stop you.

Best regards,

Miguel Ariño

[former_member286941]

Hello Miguel,

Now there is more problem regarding this, I have replied in the Above post of Surojit, Could you please check there.

[Miguel_Ariño]

If your Solution Manager is on SP4, then Maintenance Optimizer uses SMSY information, not LMDB. So the important part is the SMSY definition.

If your system is ABAP only, then you can go to SMSY, and look for the button 'read system data remote'. This will read the software component levels directly from the system through an RFC, and make sure it is correct. This cannot be done with Java software component information .

You can also ignore LMDB verification checks if the SLD information is wrong, as wrong SLD information throws off the product instance detection.

You have to check whether the software component information tab in SMSY for your system has got the software components comprised by the product instances in the 'evaluate failed...' warning messages:

BI Content Extension -> BI CONT EXT FOR BI CONT 7.0x

Process Integration (PI/XI) -> if you don't have a Java part for your system, you don't have PI.

Business System 6.20 PI/XI -> APPINT 200_620

Mobile Infrastructure (MI) -> MI ADMINISTRATION 7.02, MI CLIENT 7.02, MI DRIVERS 7.02, MI WD LAPTOP 7.02

Business Intelligence ->  SAP NW 7.0 BI CONT ADDON 7.0x

If the software components listed for each product instance are not in your system, you should unmark that product instance from the Product Instance Selection tab in SMSY.

[Former Member]

Hello Munish,

Seems those instances are not pushed correctly from SLD to LMDB. Try to delete product system from LMDB including logical components and solution.

And try to create product system again.

Which SOLMAN you are using? Release and SPS??

Is your system is dual stack?? If yes you need to split ABAP and JAVA part into two different SID's using Dual stack split tool delivered with SL Toolset 1.0 and upgrade then individuality.

Regards,

Surojit

[former_member286941]

Hello Surojit,

You are right SLD components  not pushed correctly in LMDB.

I have tried sycn from SLD to LMDB. but it again given wrong product instances in LMDB which are of older ERP EHP releases like EHP2, EHP3 instead of correct EHP5 ones.

I also tried to sycn data from SMSY to LMDB, but could not possible.

Then I have manually Deleted the old product instances which were not valid and added the valid instances along with the correct software components under them.

But still these warnings are coming which I raised in my initail message.  I don't know from where its picking the below entries, eventhough I have unselected from SMSY where it was checked in box earlier.

13:17:40  Evaluate failed for product Instance Process Integration (PI/XI) (SAP EHP2 FOR SAP NETWEAVER 7.0)

13:17:40  Evaluate failed for product Instance BI Content Extension (SAP EHP2 FOR SAP NETWEAVER 7.0)

13:17:39  Evaluate failed for product Instance Business System 6.20 PI/XI (SAP EHP2 FOR SAP NETWEAVER 7.0)

13:17:39  Evaluate failed for product Instance Mobile Infrastructure (MI) (SAP EHP2 FOR SAP NETWEAVER 7.0) 

13:17:35  Evaluate failed for product Instance Business Intelligence (SAP EHP2 FOR SAP NETWEAVER 7.0) 

These above componets are throughing error when in OS/DB selection phase of MOPZ.

Its definatly some issue in the LMDB or SMSY side, which is causing this.

My solman release is 7.1 SP4.

Regards

Munish

[Former Member]

Hello Munish,

Can you check in SLD whether your data is correct is there itself or not? Means all the instances are visible in SLD??

In SLD you can check in Comprised Components tab.

If not we need to made few modifications in system itself.

Regards,

Surojit

[karthikeyan_natarajan4]

Hi Munish,

when there is a conflict between SLD and LMDB, first check SLD CR content version and model version - update to the latest one, while applying make sure you are not jumping the release.

Regards

karthik

[Former Member]

hi,

have you executed landscape verification check in sm 7.1 sp04, this could help to correct product version, Please check.

Regards,

Jansi

[former_member286941]

This message was moderated.

[former_member286941]

This message was moderated.

[former_member286941]

This message was moderated.

[Former Member]

http://wiki.sdn.sap.com/wiki/display/SM/Troubleshooting+of+Maintenance+Optimizer

Thanks&Regards

M.Syed

[former_member286941]

HI Althaf,

this is good link but didn't solve my purpose which I am facing.

Thanks for your reply.

Regards

Munish.