Skip to Content
author's profile photo Former Member
Former Member

MOPZ_MSG_DELTA_CALC063 stack for CRM7.0 EHP2 NW7.03

Experts,

We have an existing CRM 7.0 EHP1 / NW7.02 dual stack system. We want to use Maint OPTZ to go to CRM 7.0 EHP2 / NW7.03 stack.

The CRM abap stack patch levels:

SAP_BASIS 702 0010 SAPKB70210

SAP_ABA 702 0010 SAPKA70210

PI_BASIS 702 0010 SAPK-70210INPIBASIS

ST-PI 2008_1_700 0006 SAPKITLRD6

SAP_BS_FND 702 0008 SAPK-70208INSAPBSFND

SAP_BW 702 0010 SAPKW70210

GRCPINW V1000_700 0008 SAPK-10308INGRCPINW

SAP_AP 700 0026 SAPKNA7026

WEBCUIF 701 0007 SAPK-70107INWEBCUIF

BBPCRM 701 0007 SAPKU70107

DMIS 2011_1_700 0002 SAPK-11302INDMIS

DMIS_CNT 2011_1_700 0002 SAPK-11302INDMISCNT

BIZRDEE 400 0000 -

OTEXBAS 1000_700 0001 SAPK-30401INOTEXBAS

OTEXCRM 1000_500 0000 -

OTEXRL 1000_700 0001 SAPK-30501INOTEXRL

OTEXRLC 1000_700 0001 SAPK-50501INOTEXRLC

ST-A/PI 01P_700 0000 -

TRILLIUM 818 0000 -

Also, we are on Solman 7.1 SP6, which is where I am executing MOPZ.

Solman patch levels:

SAP_BASIS 702 0011 SAPKB70211

SAP_ABA 702 0011 SAPKA70211

CTS_PLUG 200 0002 SAPK-20002INCTSPLUG

PI_BASIS 702 0011 SAPK-70211INPIBASIS

ST-PI 2008_1_700 0006 SAPKITLRD6

GW_CORE 200 0004 SAPK-20004INGWCORE

SAP_BS_FND 702 0009 SAPK-70209INSAPBSFND

SAP_BW 702 0011 SAPKW70211

IW_GIL 100 0000 -

SAP_AP 700 0027 SAPKNA7027

WEBCUIF 701 0008 SAPK-70108INWEBCUIF

BBPCRM 701 0008 SAPKU70108

BI_CONT 706 0004 SAPK-70604INBICONT

CPRXRPM 500_702 0008 SAPK-50008INCPRXRPM

IW_BEP 200 0004 SAPK-20004INIWBEP

IW_FND 250 0004 SAPK-25004INIWFND

ST 710 0006 SAPKITL706

ST-BCO 710 0004 SAPK-71004INSTBCO

RTCISM 100 0000 -

SOCO 101 0002 SAPK-10102INSOCO

ST-A/PI 01P_700 0000 -

ST-ICO 150_700 0033 SAPK-1507XINSTPL

ST-SER 701_2010_1 0014 SAPKITLOSE

Our satellite CRM system (CDM) is completely registered in SLD / LMDB / SMSY / Managed system setup, etc.

I'll get to the step 2.3 "Choose Add-on Production" in MOPZ but then I get this error and cannot move forward:

Add-on instance SAP PROCESS CONTROL 10.0 - Plug-in on SAP BASIS 7.00 is not compatible

Drilling further into the error, I see this:

Add-on instance SAP PROCESS CONTROL 10.0 - Plug-in on SAP BASIS 7.00 is not compatible

CL_FREETEXT_MESSAGE

Add-on instance SAP PROCESS CONTROL 10.0 - Plug-in on SAP BASIS 7.00 is

not compatible

Message no. MOPZ_MSG_DELTA_CALC063

Our SLD registration looks OK.

SMSY looks , OK to me

Actually, looks like it may be missing the GRC component, when I compared to another of our CRM systems at the same patch level

.

I was thinking about using the Landscape verification inside LMDB to possibly "fix" this issue. 

Thoughts? I'd rather not open a message if I can get some help here!



Thanks



NICK

PS. I tried to attach some screen shots in .png format but was not allowed. Anyway....

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Nov 30, 2012 at 10:41 AM

    Hello,

    SMSY is irrelevant in Solution Manager 7.1 SP6, you have to look at LMDB.

    The error message appears because of GRCPINW V1000_700, it is not covered by the currently assigned product instances in LMDB.

    To cover GRCPINW V1000_700, you need to add product version SAP ACCESS CONTROL 10.0 and mark as installed product instance Plug-in on BASIS 7.00.

    Then, when you run a new Maintenance Optimizer , please make sure that on step 2.3, addon selection, SAP ACCESS CONTROL 10.0 is chosen.

    Best regards,

    Miguel Ariño

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Miguel Angel Arino Clarke

      Hey Miguel,

      Finally finished doing dev/qa/prod/training. It was much more work that I thought. Just running those SE37 FMs was easy. But what I found was that the old TDMS stuff was still hanging around in the LMDB and I could not find a way to remove it. It kept saying "data in SLD...." or something. So this is what I ended up doing to get back to the point where I could run MOPZ:

      1. 1 blow away the SLD on the corresponding PI system. Make sure that also blows away central SLD entries that the LMDB uses.

      2. 2 Re-run RZ70 / SLD Data supplier from my CRM system.

      3. 3 Go to PI SLD and ADD the products for CRM EHP1, NW EHP2 and TDMS (abap), and do java similar. It was all empty after that RZ70 / SLD data supplier push

      4. 4 Go back to LMDB and re-assign technical system, production system info, and associated abap/java stacks.

      For some reason, all that gets messed up after blowing away SLD and re-doing the products in the SLD.

      Then MOPZ will actually work.

      I do have a follow up question,and please let me know if I should create a new thread.

      in SLD we still have entries floating around SLD/LMDB for various product systems around CRM like this:

      SAP CRM 7.0 / NW7.01

      EHP1 FOR SAP CRM 7.0

      SAP CRM 7.0

      By that I mean, if I look in SLD for a particular CRM system, I may see any one of the above Products. Or in LMDB, a product version by that name associated with my related product instance. And at some point MOPZ gets upset when you see "SAP CRM 7.0 / NW7.01" versus

      "SAP CRM 7.0". Some of that may be because we started at CRM2007, then upgraded to CRM7.0 then moved to ehp1. And it seems like some of those old versions get stuck along the way. But it is hard to tell sometimes which name the LMDB really wants to see.

      Anyway, not sure I really asked a question, but a small rant that wreaks havok when all I want to do is download some software.

      NICK

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.