MOPZ Issue

Question

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

Answer 1

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