Raise Exception when execute UCMON

Question

Dear all,
I need help. When we execute the transaction UCMON we have a Dump.
Erro tpo.exec.         RAISE_EXCEPTION
Data e hora            31.01.2011 17:44:30
Dump breve ABAP não está complet.gravado (demas.extenso)
TxtBreve
     Exception condition "NOT_FOUND" raised.
O que aconteceu ?
     The current ABAP/4 program encountered an unexpected
     situation.
O que pode ser feito?
     Print out the error message (using the "Print" function)
     and make a note of the actions and input that caused the
     error.
     To resolve the problem, contact your SAP system administrator.
     You can use transaction ST22 (ABAP Dump Analysis) to view and administer
      termination messages, especially those beyond their normal deletion
     date.
     is especially useful if you want to keep a particular message.
Análise do erro
     A RAISE statement in the program "CL_UC_METHOD==================CP" raised the
      exception
     condition "NOT_FOUND".
     Since the exception was not intercepted by a superior program
     in the hierarchy, 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.
as p/eliminação de erros
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system you
use the following search criteria:
"RAISE_EXCEPTION" C
"CL_UC_METHOD==================CP" or "CL_UC_METHOD==============
"CREATE_ACCOUNT"
or
"CL_UC_METHOD==================CP" "NOT_FOUND"
or
"UCUWB000 " "NOT_FOUND"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
      after the short dump. In the display, then select the function
      "System->List->Save->Local File (unconverted)".
   3. If the programs are your own programs or modified SAP programs,
      supply the source code.
      To do this, select the Editor function "Further Utilities->
      Upload/Download->Download".
   4. Details regarding the conditions under which the error occurred
      or which actions and input led to the error.
Ambiente de sistema
   SAP Release.............. "640"
   Application server....... "cpsapbwp01"
   Network address.......... "172.16.21.222"
   Operating system......... "Linux"
   Release.................. "2.6.18-238.1.1.el5"
   Hardware type............ "x86_64"
   Character length......... 16 Bits
   Pointer length........... 64 Bits
   Work process number...... 2
   Short dump setting....... "full"
   Database server.......... "bwdb"
   Database type............ "ORACLE"
   Database name............ "BWP"
   Database owner........... "SAPCSB"
   Character set............ "C"
   SAP kernel............... "640"
   Created on............... "May 2 2010 20:07:20"
Created in............... "Linux GNU SLES-10 x86_64 cc4.1.2"
Database version......... "OCI_102 "
Patch level.............. "327"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
  10.2.0.."
SAP database version..... "640"
Operating system......... "Linux 2.6"
Memory usage.............
Roll..................... 16192
EM....................... 29328992
Heap..................... 0
Page..................... 65536
MM Used.................. 23444056
MM Free.................. 1691488
SAP Release.............. "640"
Usuário e transação
    Client.............. 600
    User................ "CS096152"
    Language key........ "P"
    Transaction......... "UCWB_INT "
    Program............. "CL_UC_METHOD==================CP"
    Screen.............. "SAPLUCUM_00 1000"
    Screen line......... 3
Infos p/ponto de cancelamento
    The termination occurred in the ABAP program "CL_UC_METHOD==================CP"
     in "CREATE_ACCOUNT".
    The main program was "UCUWB000 ".
    The termination occurred in line 27 of the source code of the (Include)
     program "CL_UC_METHOD==================CM009"
    of the source code of program "CL_UC_METHOD==================CM009" (when
     calling the editor 270).
Segmento texto fonte
Linha Txt.fonte
    1 * bal080305 090305 826099 pass exception not_found to caller
    2 method CREATE_ACCOUNT .
    3
    4   data:
    5     lo_instance type ref to if_uc_cust_data,
    6     lo_account  type ref to cl_uc_account.
    7
    8   clear: eo_account, e_accid.                                 "bal080305
    9
   10   if do_account_factory is initial.
   11     do_account_factory = do_factory->get_account_factory( ).
   12   endif.
   13
   14   if i_accid is initial.
   15     call method do_account_factory->create
   16       exporting io_model    = do_model
   17       importing eo_instance = lo_instance.
   18     call method lo_instance->get_guid
   19       importing e_guid = e_accid.
   20   else.
   21     call method do_account_factory->get_instance_by_guid
   22       exporting io_model    = do_model
   23                 i_guid      = i_accid
   24       importing eo_instance = lo_instance
   25       exceptions not_found  = 1.                        "begin bal080305
   26     if not sy-subrc is initial.
>>>>>       raise not_found.
   28     endif.                                                "end bal080305
   29     e_accid = i_accid.
   30   endif.
   31   call method lo_instance->set_ffix( dt_ffix ).
   32
   33   if if_stm_timestamp = gc_true.
   34     lo_account ?= lo_instance.
   35     call method lo_account->set_task_stm_timestamp( gc_true ).
   36   endif.
   37
   38   eo_account ?= lo_instance.
   39
   40 endmethod.   31   call method lo_instance->set_ffix( dt_ffix ).
What happens?
Thanks a lot
Marilia Costa

Answer 1

Hi,
I could recollect same kind of issue in our system. In production system we were facing a short dump. however not in Development and quality.
Is it the same issue with you?
If yes. please check the single selections consistency in development & production.
thanks
Kamal