Migrate a SolMan incident from one SolMan to another SolMan

[KentP]

     Hello SolMan experts,

We are in the process of Setting up a new solution Manager 7.1 to replace an older Version 7.0

We have only one incident that was already sent to SAP in the older release and we would like to migrate it from the old SolMan to the new one.

I tried using the program AI_CRM_IM_UPDATE_FROM_SAP to create a new incident in the new SolMan, but it does not find the message in SAP Marketplace.

Is there a way to migrate this message from old SolMan to the newer Version without too much Manual Labor?

Thanks for any advice!

Best regards,

Kent Kleinsteuber

[rishav54 · Accepted solution]

Hi Kent

Can you check in SLG1 once and check the error.

You need to give the subobject AI_CRM_IM_UPD_SAP if you are getting any error there.

Further can you check the note 894279.

further check the

1795608

AI_CRM_IM_UPDATE_FROM_SAP: new incidents can not be created

Thanks

Rishav

[KentP · Accepted solution]

Hi Rishav,

Thanks for the quick Response.

Yes, I have checked the SLG1. The program does not find the message in SAP Marketplace. It finds several other Messages that belong to the same customer number and Installation number, but not the message that I am looking for.

I am assuming that SAP marks the message as coming from a solution Manager and does not Offer it for creation in another solution Manager. That is just an assumption, as I have not read that anywhere.

Any other ideas?

Best regards,

Kent

[rishav54 · Accepted solution]

Hi Kent

Please can you confirm that in the report you are giving the installation number, customer number and SAP message number that is linked to your incident number and when you execute it is not picking the message number.

Thanks

Rishav

[KentP · Accepted solution]

Hi Rishav,

yes, I can confirm that. When I just used the customer number and Installation number, it found another message that is also listed under the same Installation number. I should have found both Messages though.

Best regards,

Kent

[rishav54 · Accepted solution]

Hi Kent

Ok, if you had run the report first time so current settings are like that you will get the messages for current date minus 100 days.

Please can you run the report

AI_CRM_IM_SET_UPDATE_TMSTMP for older messages than 100 days.

Thanks

Rishav

[KentP · Accepted solution]

Thank for the hint, but that still does not solve the Problem.

Just for your Information, the message that was found was about 3 years (over 900days) old.

Best regards,

Kent

[rishav54 · Accepted solution]

Hi Kent,

Ok, If you had already given the time frame in the report as well,

Please can you share the sp level for your solution manager so that we can help you better.

Thanks

Rishav

[KentP · Accepted solution]

Good morning Rishav,

our system SolMan 7.1 SP13

SAP_BASIS    702    0016

SAP_ABA    702    0016

CTS_PLUG    200    0015

PI_BASIS    702    0016

ST-PI    2008_1_700    0011

BI_CONT    707    0010

GW_CORE    200    0008

IW_BEP    200    0008

SAP_BS_FND    702    0014

SAP_BW    702    0016

UISAPUI5    100    0010

UI_INFRA    100    0010

IW_FND    250    0008

IW_GIL    100    0004

SAP_AP    700    0032

WEBCUIF    701    0013

BBPCRM    701    0013

CPRXRPM    500_702    0013

ST    710    0013

ST-BCO    710    0012

RTCISM    100    0000

SOCO    101    0003

ST-A/PI    01R_700    0002

ST-ICC    200    0000

ST-ICO    150_700    0044

ST-SER    701_2010_1    0026

Hope this gives you enough information. Thanks again!

Best regards,

Kent

[rishav54 · Accepted solution]

Hi Kent

Strange the corrections had delivered in this version,  Please can you check the type of incident being created (is it SMIN, SMIS etc)

If SMIS you may need to use below report

AI_CRM_IM_UPDATE_FROM_SAP_ISV

Thanks

Rishav

[KentP · Accepted solution]

Hi Rishav,

We are using transaction type ZMIN (copy of SMIN) and not SMIS.

I have also imported the OSS Notes:

SNOTE: 2191925 - CX_SY_RANGE_OUT_OF_BOUNDS stops the whole

SNOTE: 2313800 Job AI_CRM_IM_UPDATE_FROM_SAP_ISV bricht bei

The message is still not found in SAP

Best regards,

Kent Kleinsteuber

[KentP · Accepted solution]

Hello Rishav,

I was finally able to migrate the ticket.

It seems that the OSS Note 2191925 - CX_SY_RANGE_OUT_OF_BOUNDS stops the whole needed to be imported and the last update had to be backdated early enough to find the ticket.

Thanks for the support and hints!

Best regards,

Kent