cancel
Showing results for 
Search instead for 
Did you mean: 

MOPZ Issue

Former Member
0 Kudos

Dear Guru's,

After configuring the MOPZ, if we try to approve the added SP in solution manager. When I click "Confirm Files in Download Backet" under t-code solution_manager -> Change Management -> Maintenance Optimizer -> Transaction ID -> its throwing a Runtime Errors which has been mentioned below.

=====================================================================================================

Runtime Errors RAISE_EXCEPTION

Date and Time 23.12.2008 15:48:49

Short dump has not been completely stored (too big)

Short text

Exception condition "NOT_FOUND" raised.

What happened?

The current ABAP/4 program encountered an unexpected

situation.

Error analysis

A RAISE statement in the program "CL_SM_DATA_SENDER_RFC=========CP" raised the

exception

condition "NOT_FOUND".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

Trigger Location of Runtime Error

Program CL_SM_DATA_SENDER_RFC=========CP

Include CL_SM_DATA_SENDER_RFC=========CM003

Row 24

Module type (METHOD)

Module Name GET_DESTINATION

=====================================================================================================

OS : AIX 5.3

DB : DB2 9.5

SAP : Solution Manager 7.0

Suggestion appreciated.

regards,

Guna

Accepted Solutions (0)

Answers (4)

Answers (4)

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Guna,

What is the release SP level of your Solution Manager, would it be R 4.0 SP 15 by any chance?

Please advise, thank you.

Regards,

Paul

Former Member
0 Kudos

Hi,

Sorry, I forgot to mention this.

OS - AIX 5.3

DB - DB2 9.5

SAP - Solution Manager 7.0 SP14

regards,

Guna

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear Guna,

Examining this thread, you have stated that you see 3 column in AISUSER, but only have a single customer number and you are not maintaining multiple customer numbers.. If that is the case, 3 columns indicated the AISUSER table has been activated for

multiple customer numbers. If you are not using multiple customer numbers then this would explain the error.

If you are certain that you are not using multiple customer numbers then I suggest you look at SAP Note 1140822 and perform step 2, which should fix this problem.

Regards,

Paul

Former Member
0 Kudos

Dear Paul,

Thanks for your suggestion.

In the previous thread itself I mentioned that it has been done, still we are facing the same problem.

regards,

Guna

Miguel_Ariño
Advisor
Advisor
0 Kudos

Hello,

The common notes for Maintenance Optimizer start with SP15, SP14 is more difficult to maintain. Also, you need at least SP15 for EHP installations.

I would recommend, if it fits your upgrade schedule and you can commit some time to it, to update to at least SP17 (if you don' t want to go up to EHP1 for Solution Manager).

Best regards,

Miguel Ariñ

Miguel_Ariño
Advisor
Advisor
0 Kudos

Hello,

Do you use only a SAP customer number or several? Do you have two columns in AISUSER or three?

If you have three columns in AISUSER and you use only one customer number , then your system has got the RFC BAdIs activated and they should not be.

Best regards,

Miguel Ariñ

Former Member
0 Kudos

Dear All,

Thanks for your suggestions...

Mr. Gagan Deep Kaus suggestion won't applicable, coz we have 3 columns in AISUSER t-code.

Mr. Paul, 1140822 has been implemented and also sub-notes mentioned also implemented.

Mr. Miguel Ariño, yes your rite we have 3 columns and I use only one customer number and also that Badi deactivated.

Still I'm facing the runtime errors and also its showing System messages in solution_manager t-code,

-

-


System Messages:

Error No destination for SAP customer number 20405164

-

-


-

-


Runtime Errors RAISE_EXCEPTION

Date and Time 03.05.2010 20:53:36

Short text

Exception condition "NOT_FOUND" raised.

What happened?

The current ABAP/4 program encountered an unexpected situation.

Error analysis

A RAISE statement in the program "CL_SM_DATA_SENDER_RFC=========CP" raised the exception condition "NOT_FOUND".

Since the exception was not intercepted by a superior program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

Trigger Location of Runtime Error

Program CL_SM_DATA_SENDER_RFC=========CP

Include CL_SM_DATA_SENDER_RFC=========CM003

Row 24

Module type (METHOD)

Module Name GET_DESTINATION

-

-


Could anyone suggest me a solution to close this issue.

regards,

Guna

Paul_Babier
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Guna,

If the above doesn't resolve you might want to have a look at SAP Note 1140822 to see if it applies to your Release/SP level.

Regards,

Paul

Former Member
0 Kudos

Hi,

Most prob this might be the issue

Regards