cancel
Showing results for 
Search instead for 
Did you mean: 

MOPZ_MSG_DELTA_CALC063 stack for CRM7.0 EHP2 NW7.03

Former Member
0 Kudos

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....

Accepted Solutions (1)

Accepted Solutions (1)

Miguel_Ariño
Advisor
Advisor
0 Kudos

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

Former Member
0 Kudos

Miguel,

I understand SMSY isn't the place to look, but it's still there and does get updated and I'm just used to looking there.

OK, I did look at LMDB and fixed my landscape vertification issue with GRC product.

Now I have a new error.  For some reason my ABAP stack SLD is sending conflicting data related to the products:

SAP TDMS 3.0

SAP TDMS 4.0

We have TDMS 4.0 which we upgraded from 3.0 about 6 months ago.  So my source ABAP system, CDM, sends it's SLD data RZ70 / and SLD data supplier to our PI system , called PDM.

That, in turn, syncs with our Central SLD which then syncs with LMDB.

The "incorrect" TDMS 3.0 data is being listed in the PI system PDM, and then it is sending that to the central SLD and on to the LMBD.  As a result, now in MOPZ, I see this:

System CDM: Predecessor Product Version SAP TDMS 3.0 defined in SLD!

The system definition in the Solution Manager is not up to date.

I've beat my head against the wall on this too much.  I need HELP!  Can you please tell me what the best component would be to open a OSS message so I can get to the correct person to help me??

Thanks man,

NICK

Miguel_Ariño
Advisor
Advisor
0 Kudos

Hello,

The SLD information is transferred from the product registry in the system PDM.

If you go to the ABAP stack and check with function module OCS_GET_INSTALLED_SWPRODUCTS, you should see as output a few entries in table ET_SWFEATURES.

TDMS 3.0 has product code 01200314690900000368 . If you see such an entry, you need to delete it. This is done with function module OCS_SET_INSTALLED_SWPRODUCTS.

In table IT_DEL_SWPRODUCTS, you need to enter the product code 01200314690900000368 in the field version, go back and run.

If this is too complicated, then we can do it in a support message.

Best regards,

Miguel Ariño

Former Member
0 Kudos

Miguel,

OK, I executed that first FM you listed on my CRM system.  And I see this:

ID  PROD_ID              NAME     VERSION    DESCRIPT

1   01200615320900001853 SAP CRM    7.0    SAP CRM 7.0 / NW7.01: CRM Application Server ABAP
1   01200615320900003225 SAP NETWEAVER    SAP EHP2 FOR SAP NETWEAVER 7.0 SAP EHP2 FOR SAP NETWEAVER 7.0: Application Server ABAP
1   01200615320900003527 SAP CRM ENHANCE PACKAGE  705    EHP1 FOR SAP CRM 7.0: CRM Application Server ABAP
4   01200314690900000368 SAP TEST DATA MIGRATION SERVER SAP TDMS 3.0    SAP TDMS 3.0: TDMS for ABA 7.0X

So, then, you are saying I can run the other FM to remove the TDMS 3.0 entry.  But just to be clear, I execute the other FM on the CRM system?  or on the PI system where it sends the SLD data or both?

Interesting that TDMS 4.0 isn't listed anywhere in that FM, but oh well.  Thanks for your help so far.

NICK

Miguel_Ariño
Advisor
Advisor
0 Kudos

The OCS_GET... and OCS_SET.... function modules have to be executed in the system where the TDMS addon is installed. I guess that is the CRM system.

Best regards,

Miguel Ariño

Former Member
0 Kudos

Hey Miguel,

OK, I executed FM OCS_SET_INSTALLED_SWPRODUCTS in my CRM system that has the incorrect entry for TDMS 3.0

I then went to IT_DEL_SWPRODUCTS table and put 01200314690900000368 into the "VERSION" field.  Then went "back" and executed.

I didn't notice any errors when it returned.  But still, when I execute FM OCS_GET_INSTALLED_SWPRODUCTS I still see the TDMS 3.0 entry. 

So it doesn't appear to have done anything.

--NICK

Former Member
0 Kudos

Miguel,

Never mind.  I put the full entry for all fields into:

IT_DEL_SWPRODUCTS

IT_DEL_SWFEATURES

then executed again and that took care of it.

Now to see if the SLD gets updated!!

NICK

Miguel_Ariño
Advisor
Advisor
0 Kudos

Hi,

How did it go with the SLD update?

Best regards,

Miguel Ariño

Former Member
0 Kudos

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

Answers (0)