UNCAUGHT_EXCEPTION       'CX_BBP_PD_ABORT

We get the following error when we try and ammend a P.O
Has anyone come accross this

Hi,
See the  following SAP OSS Notes ->
OSS Note 673372 Short dumps UNCAUGHT_EXCEPTION in SRM 3.0, 4.0, and 5.0
Note 833442 Data inconsistency due to termination when you save
Note 831594 Purchase order: Termination when you write a new version
Note 828356 Duplicate items when changing ordered purchase orders
Note 526831 EBP: Missing currency in the limit results in termination
Note 724316 Purchase order: Short dump in case of vendor deletion
Note 671481 Exception: CX_BBP_PD_ABORT in pricing
BR,
Disha.
Pls reward points for useful answers.

Similar Messages

  • Error when signing on SRM portal

    Hi, i have this problem, when user signs on in the SRM portal (SRM 3.0) and the shopping cart page suppossed to appears (after enters user and pwd), the following error displays:
    ITS System Information
    Interpreter Failed
    The Internet Transaction Server failed to generate the response for current request.
    Please contact the system administrator.
    Internal error code: 0x2101
    In an already existent imlementation for badi BBP_DOC_CHECK_BADI i've added this code  just to check some error messages from the document and if founded, add a custom message to the internal table
    Data declaration
    Variable
    data:
      lv_guid  type CRMD_ORDERADM_H-GUID.
    Constants
      constants:
        lc_slash(1)  type c value '/',
        lc_015       type bbp_pds_messages-msgno value '015',
        lc_000       type bbp_pds_messages-msgno value '000',
        lc_fmavc     type bbp_pds_messages-msgid value 'FMAVC',
        lc_zebp      type bbp_pds_messages-msgid value 'ZEBP'.
    Internal tables & Structures
      data:
        ls_messages type          bbp_pds_messages,
        lt_messages type table of bbp_pds_messages.
    First, check the SC
        call function 'BBP_PD_SC_CHECK'
          exporting
            i_guid     = lv_guid
         TABLES
           E_MESSAGES  = lt_messages.
    Look for the right message
      read table lt_messages into ls_messages with key msgid = lc_FMAVC
                                                       msgno = lc_015.
      if sy-subrc = 0.
    Message founded, build custom message
    Add the message to table
      read table it_account into wa_account index 1.
        wa_error-msgty = 'E'.
        wa_error-msgid = lc_zebp.
        wa_error-msgno = lc_000.
        concatenate wa_header-posting_date+0(4)  " Year
                    lc_slash
                    wa_account-funds_ctr         " Funds center
                    lc_slash
                    wa_account-fund              " Fund
                    lc_slash
                    wa_account-func_area         " Functional area
                    lc_slash
                    wa_account-cmmt_item         " Commitment item
               into wa_error-msgv1.
        APPEND wa_error TO et_messages.
      endif.
    but in the call for 'BBP_PD_SC_CHECK' the systems generates a dump, if i comment the fm call, the page displays correctly, the parameters for fm are the right type.
    The dump appears as follows:
    Errores tiempo ejec.   UNCAUGHT_EXCEPTION
    Excepción              CX_BBP_PD_ABORT
           ocurrido el     26.12.2007 a  19:42:04
    Es ist eine Ausnahme aufgetreten, die nicht abgefangen wurde.
    ¿Qué ha sucedido?
    Die Ausnahme 'CX_BBP_PD_ABORT' wurde ausgelöst,
    sie wurde aber entlang der Aufrufhierarchie nirgendwo abgefangen.
    Da Ausnahmen Fehlersituationen darstellen und auf diesen Fehler nicht
    adäquat reagiert wurde, mußte das laufende ABAP-Programm 'SAPLBBP_PDH'
    abgebrochen werden.
    ¿Qué puede hacer?
    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ál.errores
    Es ist eine Ausnahme aufgetreten, die weiter unten näher erläutert wird.
    Die Ausnahme, der die Klasse 'CX_BBP_PD_ABORT' zugeordnet ist,
    wurde nicht abgefangen und führte deshalb zu einem Laufzeitfehler.
    Der Grund für die Ausnahme ist:
    Übernehmen
    Notas para corregir errores
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "UNCAUGHT_EXCEPTION" CX_BBP_PD_ABORTC
    "SAPLBBP_PDH" or "LBBP_PDHU08"
    "BBP_PD_ABORT"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    Entorno sistema
    SAP-Release.............. "620"
    Applikationsserver....... "ebpqas"
    Netzwerkadresse.......... "144.127.70.32"
    Betriebssystem........... "SunOS"
    Release.................. "5.9"
    Hardwaretyp.............. "sun4u"
    Zeichen-Länge............ 8 Bits
    Pointer-Länge............ 64 Bits
    Workprozess-Nummer....... 0
    Kurzdump-Einstellung..... "full"
    Datenbankserver.......... "ebpqas"
    Datenbanktyp............. "ORACLE"
    Datenbankname............ "EBQ"
    Datenbank-User-Id........ "SAPEBP"
    Zeichensatz.............. "es"
    SAP-Kernel............... "640"
    hergestellt am........... "Jul 4 2005 21:14:29"
    hergestellt auf.......... "SunOS 5.8 Generic_108528-16 sun4u"
    Datenbankversion......... "OCI_920 "
    Patch-Level.............. "80"
    Patch-Text " "
    Unterstützte Umgebung....
    Datenbank ............... "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP-Datenbankversion..... "640"
    Betriebssystem........... "SunOS 5.8, SunOS 5.9, SunOS 5.10"
    Usuario, transacción....
    Mandant............. 010
    Benutzer............ "CRARIABR"
    Sprachenschlüssel... "S"
    Transaktion......... "BBPSC02 "
    Programm............ "SAPLBBP_PDH"
    Dynpro.............. "SAPLBBP_SC_UI_ITS 2000"
    Dynprozeile......... 4
    Info posición de cancelación
    Der Abbruch trat im ABAP-Programm "SAPLBBP_PDH" auf, und zwar in
    "BBP_PD_ABORT". Das Hauptprogramm war "SAPLBBP_SC_UI_ITS ".
    Im Quelltext befindet sich die Abbruchstelle in Zeile 67
    des (Include-)Programms "LBBP_PDHU08".
    (bei Anwahl des Editors: 670) der ABAP-Source "LBBP_PDHU08".
    Detalle código fuente
    000370                   LS_CALLSTACK1-EVENTNAME LS_CALLSTACK1-PROGNAME
    000380                   INTO LV_MSGARG2 SEPARATED BY SPACE.
    000390
    000400     READ TABLE LT_CALLSTACK INTO LS_CALLSTACK2 INDEX 4.
    000410     CONCATENATE   '/' LS_CALLSTACK2-EVENTTYPE
    000420                   LS_CALLSTACK2-EVENTNAME LS_CALLSTACK2-PROGNAME
    000430                   INTO LV_MSGARG3 SEPARATED BY SPACE.
    000440
    000450     CALL FUNCTION 'BBP_ALERT_INTERNAL_OT'
    000460       EXPORTING
    000470         MSGID   = GC_MSGID_BBP_PD
    000480         MSGNO   = 047
    000490         MSGARG1 = LV_MSGARG1
    000500         MSGARG2 = LV_MSGARG2
    000510         MSGARG3 = LV_MSGARG3.
    000520
    000530     MESSAGE ID GC_MSGID_BBP_PD TYPE C_MSGTY_I NUMBER IV_MSG_NO
    000540             WITH LS_CALLSTACK1-EVENTTYPE
    000550                  LS_CALLSTACK1-EVENTNAME
    000560                  LS_CALLSTACK1-PROGNAME.
    000570
    000580   * get the messages from the application log
    000590     TRY.
    000600         CALL FUNCTION 'BBP_PD_LOG_GET_MESSAGES'
    000610           TABLES
    000620             E_MESSAGES = LT_MESSAGES.
    000630       CATCH CX_BBP_PD_ABORT.
    000640         REFRESH LT_MESSAGES.
    000650     ENDTRY.
    000660
        RAISE EXCEPTION TYPE CX_BBP_PD_ABORT EXPORTING
    000680         WORKED_ON_DOCUMENT = LV_GUID
    000690         T100_MSGID = GC_MSGID_BBP_PD
    000700         T100_MSGNO = IV_MSG_NO
    000710         T_APPL_LOG_MESSAGES = LT_MESSAGES.
    000720
    000730   ENDFUNCTION.
    Thanks in advance for your help.

    Hi
    It seems some mandatory System configuration settings are missing.
    For time-being, please Try de-activating the active customer implementations of the BADIs BBPDOC_CHANGE / BBP_DOC_CHECK_BADIs and then try again the Shop process._
    Please try to look into RZ20, ST22, RZ10, and SLG1 transactions for any error logs generated.
    Also, Please Check the SAP OSS Notes ->
    Note 673372 - Short dumps UNCAUGHTEXCEPTION in SRM 3.0, 4.0, and 5.0_
    Note 833442 Data inconsistency due to termination when you save
    bbp_pd_sc_check_is_pd
    "Buffer table not up to date"
    Re: ITS Template not found
    Re: CX_BBP_PD_ABORT error selection itens in SC
    DUMP with transaction BBPSC02 :'UNCAUGHT_EXCEPTION      CX_BBP_PD_ABORT'
    Re: Error while adding items to shopping cart
    Note 851825 Copying a reference without ship-to address ==> error
    Note 847427 Error when you copy template without ship-to address
    Note 746569 CX_BBP_PD_ABORT in routine CHECK_CF_QUANTITY
    Note 651994 PO with several hierarchy levels causes termination
    Hope this will definitely help. Do let me know.
    Regards
    - Atul

  • Dump while adding a shopping cart in work area in Carryout Sourcing

    Hi Experts,
    We are getting dump while adding a shopping cart to the work area in Carryout Sourcing.
    We want to replicate the Purchase Requisition from R/3 to SRM. And SC contains the limit item with free text service.
    The dump details are as follows :
    The exception 'CX_BBP_PD_ABORT' was raised, but it was not caught anywhere
    along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program 'SAPLBBP_PDH' has to be
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
        therefore caused a runtime error.
        The reason for the exception is:
        Buffer table not up to date
    How to correct the error
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"
        "SAPLBBP_PDH" or "LBBP_PDHU08"
        "BBP_PD_ABORT"
    Information on where terminated
        Termination occurred in the ABAP program "SAPLBBP_PDH" - in "BBP_PD_ABORT".
        The main program was "SAPLBBP_SOCO_UI_ITS ".
        In the source code you have the termination point in line 73
        of the (Include) program "LBBP_PDHU08".
      READ TABLE lt_callstack INTO ls_callstack2 INDEX 4.
      CONCATENATE   '/' ls_callstack2-eventtype
                    ls_callstack2-eventname ls_callstack2-progname
                    INTO lv_msgarg3 SEPARATED BY space.
      CALL FUNCTION 'BBP_ALERT_INTERNAL_OT'
        EXPORTING
          msgid   = gc_msgid_bbp_pd
          msgno   = 047
          msgarg1 = lv_msgarg1
          msgarg2 = lv_msgarg2
          msgarg3 = lv_msgarg3.
      MESSAGE ID gc_msgid_bbp_pd TYPE c_msgty_i NUMBER iv_msg_no
              WITH ls_callstack1-eventtype
                   ls_callstack1-eventname
                   ls_callstack1-progname.
      rollback work.
    get the messages from the application log
      TRY.
          CALL FUNCTION 'BBP_PD_LOG_GET_MESSAGES'
            TABLES
            e_messages = lt_messages.
        CATCH cx_bbp_pd_abort.
          REFRESH lt_messages.
      ENDTRY.
      RAISE EXCEPTION TYPE cx_bbp_pd_abort EXPORTING
          worked_on_document = lv_guid
          t100_msgid = gc_msgid_bbp_pd
          t100_msgno = iv_msg_no
          t_appl_log_messages = lt_messages.
    ENDFUNCTION.
    Could you please help me on this, how to rectify the dump ?
    Thank you very much in advance.

    Hello,
    I have seen this dump many times because the ERP version defined in table BBP_BACKEND_DEST was not correct.
    Please, check the following note related to this configuration:    
    1230789 - Dump: BBPSOCO01 at include LBBP_PDH_TEOF0B               
    Kind regards,
    Ricardo

  • Dump adding template SC to PO

    Hi,
    i´m having a short dump when adding a SC template to a Purchase Order.
    "UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"
    "SAPLBBP_PDH" or "LBBP_PDHU08"
    "BBP_PD_ABORT"
    I think this is due to a modification in the structures of the SC tables or the PO tables. Does any one know any FM ou program to check consistency of data copy beetween the two?
    If i add just one of the lines of the SC all goes good, if i pick more than one dump is raised.
    Best Regards,
    HT

    Hi,
    In the Call Structure of the dump you will see what Function Modules/Forms were called during this copy of data. This normally
    points to where the issue lies. Please check this.
    If you need further assistance. Please paste the last 10 calls form the call structure to this message.
    Kind Regards
    Lisa

  • Getting error as Buffer table not up to date

    Hi SRM gurus,
    We have one order which is created in the EBP side and the same is replicated in the backend also. Also confirmations and invoices are posted for this local PO. These confirmations and invoices are also carried over to backend. However very recently when we open this order in EBP and when we click either check button (or) change button we get the error indicating that Buffer table not up to date. I have pasted the error message below. We have also checked the ST22 and observed that exception occurred CX_BBP_PD_ABORT and is not caught any where. When do not have any issues with other orders. We have checked the recent changes and we could not observe any recent changes to the order.
    Note
    The following error text was processed in the system  : Buffer table not up to date
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Function: BBP_PD_ABORT of program SAPLBBP_PDH
    Form: ABORT of program SAPLBBP_PD
    Form: CHECK_VENDOR_ERS of program SAPLBBP_PD
    Form: HEADER_CROSS_CHECKS of program SAPLBBP_PD
    Form: PROCDOC_DB_CHECK of program SAPLBBP_PD
    Form: PROCDOC_CHECK of program SAPLBBP_PD
    Function: BBP_PROCDOC_CHECK of program SAPLBBP_PD
    Function: BBP_PD_PO_CHECK of program SAPLBBP_PD_PO
    Form: CHECK_PO of program SAPLBBP_PO_APP
    Form: PROCESS_EVENT of program SAPLBBP_PO_APP
    iN BBP_PD the status of this PO is as below.
    Stats:                                                          
                       Status            Description                             Inactiv
    HEADER     I1015          Awaiting Approval                      X      
    HEADER     I1021          Created                               
    HEADER     I1038          Complete                              
    HEADER     I1043          Ordered                               
    HEADER     I1080          In Transfer to Execution Syst.    X      
    HEADER     I1120          Change was Transmitted                
    HEADER     I1180          Document Completed                    
    0000000001 I1021          Created                               
    0000000002 I1021          Created      
    Please suggest / advice on this.              
    Thanks & Regards
    Psamp1

    Hi
    It is difficult to diagnoise the issue
    Note 1180477 - PO processing terminates with buffering table error
    see the symptoms in the note
    Symptom
    You have opened a purchase order using "Process Purchase Order" (BBP_POC). You change some data of this purchase order and then choose "Output" at header level. The system may display error message BBP_PD 001 "Buffer table not up to date", and an entry "UNCAUGHT_EXCEPTION" , "CX_BBP_PD_ABORT" is in transaction ST22
    Try to recreate the same issue in develpoment and make ensure that which data is causing this issue.
    What is the status of PO ? any archiving done recently on this PO or any data changes in the PO check history to know more information
    check SRM-EBP-POR for more related notes. you need to identify which data is causing thie issue
    Muthu

  • Dump in production system :Incorrect status in pricing

    Hi All,
    We have patched out SRM5.5 server system recently with  15 and  16 patch.
    After the patch we are getting  many dums in production system.
    When i check in the ST22 ,the error syaing that
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
        therefore caused a runtime error.
        The reason for the exception is:
         *Incorrect status in pricing*
    How to correct the error
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"
        "SAPLBBP_PDH" or "LBBP_PDHU08"
        "BBP_PD_ABORT"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
    and  i have checked the IPC ,it is also active only,.
    We have got his issue all of suddenlly,
    Can any one tell us what could be the issue.
    Regards
    cb

    Hi All,
    thanks a lot for your response ,
      I have done the  Simulation which shows everything is fine  and i have chcked with BBP_CND_CUSTOMIZING_CHECK  t-codes even that is also correct  only .
    we are plannning for rasing the issue with SAP.
    Besides that the system might have activated the BADI simple pricing active (or something like that). This would give trouble as well with the IPC (they can't both be active).
    @Robin which the badi we can check.
    once agina thanks a lot for your replys.
    Regards
    cb

  • PO output in SRM

    Hi chaps,
    We are running ECV. I'm getting an error, 'unable to interpret C1 as a number'. When I click on Preview Output for a PO. Anyone come across this error and knows what it means??
    Regards
    TV

    Atul,
    SRM Extended Classic Version 5.0.
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_BBP_PD_ABORT
    Date and Time          26.11.2007 12:18:06
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_BBP_PD_ABORT
    Date and Time          26.11.2007 12:18:06
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_BBP_PD_ABORT' was raised, but it was not caught anywhere
    along the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program 'SAPLBBP_PDH' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    Übernehmen
    to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"
    "SAPLBBP_PDH" or "LBBP_PDHU08"
    "BBP_PD_ABORT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
        SAP-Release 700
    User and Transaction
        Client.............. 400
        User................ "SPHILBIN"
        Language Key........ "E"
        Transaction......... "BBP_POC_EDIT "
        Program............. "SAPLBBP_PDH"
        Screen.............. "SAPLBBP_PO_UI_ITS 1000"
        Screen Line......... 4
    Information on where terminated
        Termination occurred in the ABAP program "SAPLBBP_PDH" - in "
        The main program was "SAPLBBP_PO_UI_ITS ".
        In the source code you have the termination point in line 73
        of the (Include) program "LBBP_PDHU08".
    Rgds
    TV

  • Screen Field

    Hello,
    I added a manufacturer part number in the item level of the shopping cart and I did it so by adding the fields in the two structures INCL_EEW_PD_ITEM_CSF and INCL_EEW_PD_ITEM_CSF_SC. Now I can see this field in the shopping cart. When I enter a manufacturer part number in this field I shud populate the product in the item level based on the number entered in this manufactuer part field. For that I had did the BADI implementation in BBP_DOC_CHANGE_BADI and did the code as follows in BBP_SC_CHANGE
    METHOD if_ex_bbp_doc_change_badi~bbp_sc_change.
      DATA lv_matnr type matnr.
      DATA wa_item TYPE bbp_pds_sc_item_icu.
      data ws_item type BBPS_SC_ITEM_BADI.
      LOOP AT it_item INTO wa_item.
        IF wa_item-zmro_item1 NE ' '.
          CALL FUNCTION 'Z_RFC_MANUPN'
            DESTINATION 'CLNT134'
            EXPORTING
              mfpnr = wa_item-ZMRO_ITEM1
            IMPORTING
              matnr = lv_matnr.
          wa_item-product = lv_matnr.
          IF lv_matnr NE ' '.
            MODIFY it_item FROM wa_item TRANSPORTING product.
          ENDIF.
        ENDIF.
      ENDLOOP.
    ENDMETHOD.
    Now when I try to run this It results in anerror. Can any one tell  me what is the error. The error is of type..<b> The exception 'CX_BBP_PD_ABORT' was raised, but it was not caught anywhere
      along
    the call hierarchy.</b>
    Please help me..
    Viky

    ATUL,
    Here is the dump Details..
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_BBP_PD_ABORT
    Date and Time          04/30/2007 22:36:08
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_BBP_PD_ABORT' was raised, but it was not caught anywhere
    along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program 'SAPLBBP_PDH' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    Übernehmen
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"
    "SAPLBBP_PDH" or "LBBP_PDHU08"
    "BBP_PD_ABORT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "NGCNSW01"
    Network address...... "192.168.206.199"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "NGCNSW01"
    Database type..... "MSSQL"
    Database name..... "DS1"
    Database user ID.. "ds1"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Nov 13 2006 00:10:30"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 85
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 16192
    EM...... 16759360
    Heap.... 0
    Page.... 770048
    MM Used. 12705920
    MM Free. 4050144
    User and Transaction
    Client.............. 150
    User................ "CONTRACT01"
    Language Key........ "E"
    Transaction......... "BBPSC02 "
    Program............. "SAPLBBP_PDH"
    Screen.............. "SAPLBBP_SC_UI_ITS 2000"
    Screen Line......... 44
    Information on Caller ofr "HTTP" Connection:
    Plug-in Type.......... "HTTP"
    Caller IP............. "10.1.30.240"
    Caller Port........... 8000
    Universal Resource Id. "/sap/bc/gui/sap/its/bbpsc02/~flNUQVRFPTI3ODMyLjAwOC4wNi
    4wMQ=="
    Information on where terminated
    Termination occurred in the ABAP program "SAPLBBP_PDH" - in "BBP_PD_ABORT".
    The main program was "SAPLBBP_SC_UI_ITS ".
    In the source code you have the termination point in line 73
    of the (Include) program "LBBP_PDHU08".
    Source Code Extract
    Line
    SourceCde
    43
    44
    READ TABLE lt_callstack INTO ls_callstack2 INDEX 4.
    45
    CONCATENATE   '/' ls_callstack2-eventtype
    46
    ls_callstack2-eventname ls_callstack2-progname
    47
    INTO lv_msgarg3 SEPARATED BY space.
    48
    49
    CALL FUNCTION 'BBP_ALERT_INTERNAL_OT'
    50
    EXPORTING
    51
    msgid   = gc_msgid_bbp_pd
    52
    msgno   = 047
    53
    msgarg1 = lv_msgarg1
    54
    msgarg2 = lv_msgarg2
    55
    msgarg3 = lv_msgarg3.
    56
    57
    MESSAGE ID gc_msgid_bbp_pd TYPE c_msgty_i NUMBER iv_msg_no
    58
    WITH ls_callstack1-eventtype
    59
    ls_callstack1-eventname
    60
    ls_callstack1-progname.
    61
    62
    rollback work.
    63
    64
    get the messages from the application log
    65
    TRY.
    66
    CALL FUNCTION 'BBP_PD_LOG_GET_MESSAGES'
    67
    TABLES
    68
    e_messages = lt_messages.
    69
    CATCH cx_bbp_pd_abort.
    70
    REFRESH lt_messages.
    71
    ENDTRY.
    72
    >>>>>
    RAISE EXCEPTION TYPE cx_bbp_pd_abort EXPORTING
    74
    worked_on_document = lv_guid
    75
    t100_msgid = gc_msgid_bbp_pd
    76
    t100_msgno = iv_msg_no
    77
    t_appl_log_messages = lt_messages.
    78
    79
    ENDFUNCTION.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    1
    SY-DBCNT
    1
    SY-FDPOS
    40
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SC_CHECK
    SY-TITLE
    Shop in 3 Steps
    SY-MSGTY
    S
    SY-MSGID
    BBP_PD
    SY-MSGNO
    008
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20070430
    SY-UZEIT
    223608
    SY-XPROG
    SAPLSCSMROUTE
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    13 FUNCTION     SAPLBBP_PDH                         LBBP_PDHU08                            73
    BBP_PD_ABORT
    12 FORM         SAPLBBP_PD                          LBBP_PDF0P                             10
    ABORT
    11 FORM         SAPLBBP_PD                          LBBP_PDF3G                             81
    BUDGET_SC_CHECK
    10 FORM         SAPLBBP_PD                          LBBP_PDF1C                            782
    PROCDOC_CROSS_CHECKS
    9 FORM         SAPLBBP_PD                          LBBP_PDF10                            265
    PROCDOC_DB_CHECK
    8 FORM         SAPLBBP_PD                          LBBP_PDF0Q                             77
    PROCDOC_CHECK
    7 FUNCTION     SAPLBBP_PD                          LBBP_PDU05                             17
    BBP_PROCDOC_CHECK
    6 FUNCTION     SAPLBBP_PD_SC                       LBBP_PD_SCU07                          11
    BBP_PD_SC_CHECK
    5 FORM         SAPLBBP_SC_APP                      LBBP_SC_APPF55                         11
    SC_CHECK
    4 FUNCTION     SAPLBBP_SC_APP                      LBBP_SC_APPU02                        236
    BBP_SC_APP_EVENT_DISPATCHER
    3 FORM         SAPLBBP_SC_UI_ITS                   LBBP_SC_UI_ITSF05                      37
    APP_EVENT_HANDLER
    2 FORM         SAPLBBP_SC_UI_ITS                   LBBP_SC_UI_ITSF02                      32
    SC_EVENT_DISPATCHER
    1 MODULE (PAI) SAPLBBP_SC_UI_ITS                   LBBP_SC_UI_ITSI01                       3
    SC_EVENT_DISPATCHER
    Chosen variables
    Name
    Val.
    No.      13 Ty.          FUNCTION
    Name  BBP_PD_ABORT
    IT_MESSAGE
    Table[initial]
    IV_MSG_NO
    001
    333
    001
    000
    000
    C_IS_CONTACT_PERSON
    BUR001
    455333
    252001
    000000
    000000
    LT_MESSAGES
    Table IT_15839[1x1002]
    FUNCTION=BBP_PD_ABORTDATA=LT_MESSAGES
    Table reference: 899
    TABH+  0(20) = 10F69157FE07000050D36E57FE07000000000000
    TABH+ 20(20) = 83030000DF3D000001000000EA030000FFFFFFFF
    TABH+ 40(16) = 04970000003B000001000000C1248401
    store        = 0x10F69157FE070000
    ext1         = 0x50D36E57FE070000
    shmId        = 0     (0x00000000)
    id           = 899   (0x83030000)
    label        = 15839 (0xDF3D0000)
    fill         = 1     (0x01000000)
    leng         = 1002  (0xEA030000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000300
    occu         = 1     (0x01000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x00BE4157FE070000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 10628 (0x84290000)
    refCount     = 1     (0x01000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 1     (0x01000000)
    lineAlloc    = 1     (0x01000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 2     (0x02000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xB0548057FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xE0902C57FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    SYST-REPID
    SAPLBBP_PDH
    5454445554422222222222222222222222222222
    310C220F04800000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SY
    ######################(##################################################### #####ÿ#####XC####
    00000000000000000000002000000000000000E0000000002000000000000000000000000000208000F000BF540000
    00001010000000000000108010001000000000A000000000C030100000000000000000000000000000F0000F830100
    00000000000000000000000000000000000000000000000000000000000000000000000000000000000000BF000000
    000000000000000000000000000000000000003000000000100000000000000000000000000000000000009F00000C
    %_EXCP
    5000A000
    1000E000
    LV_GUID
    22222222222222222222222222222222
    00000000000000000000000000000000
    00000000000000000000000000000000
    00000000000000000000000000000000
    GC_MSGID_BBP_PD
    BBP_PD
    44555422222222222222
    220F0400000000000000
    00000000000000000000
    00000000000000000000
    No.      12 Ty.          FORM
    Name  ABORT
    %_DUMMY$$
    2222
    0000
    0000
    0000
    No.      11 Ty.          FORM
    Name  BUDGET_SC_CHECK
    LT_BUDGET_LINES
    ########DS1CLNT150
    000000004534445333222222222222222222222222
    000000004313CE4150000000000000000000000000
    000000000000000000000000000000000000000000
    000000000000000000000000000000000000000000
    C_DATA_SOURCE_PO
    0SRM_TD_PO
    355455455422222222222222222222
    032DF44F0F00000000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    LT_ITEM_PR-BE_LOG_SYSTEM
    DS1CLNT150
    4534445333
    4313CE4150
    0000000000
    0000000000
    %_SPACE
    2
    0
    0
    0
    C_INVOICE
    BUS2205
    4553333222
    2532205000
    0000000000
    0000000000
    C_CONTACT
    0007
    3333
    0007
    0000
    0000
    LV_OWN_LOGSYS
    DS1CLNT100
    4534445333
    4313CE4100
    0000000000
    0000000000
    C_A_OR_TRANS_CHA
    ORAU
    4545
    F215
    0000
    0000
    C_A_LA_PUBLISH
    LAPU
    4455
    C105
    0000
    0000
    C_A_CTR_RENEW_FINISH
    CTRF
    4554
    3426
    0000
    0000
    GC_OBJECTNAME_REPORTING
    CL_CRM_REPORT_EXT_ACTIVITY_H  CL_CRM_REPORT_SET_APPOINTMENT CL_CRM_REPORT_SET_APPOINT_I   CL_C
    4454545545455545554454545554224454545545455554554554445444524454545545455554554554445542224454
    3CF32DF250F24F584F13496949F8003CF32DF250F24F354F100F9E4D5E403CF32DF250F24F354F100F9E4F90003CF3
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    C_DATA_SOURCE_PO_ACC
    0SRM_TD_PO_ACC
    355455455454442222222222222222
    032DF44F0FF1330000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    IT_ORGDATA[]
    Table IT_15324[0x124]
    FUNCTION-POOL=BBP_PDFORM=PROCDOC_CROSS_CHECKSDATA=LT_ORGDATA[]
    Table reference: 906
    TABH+  0(20) = 0000000000000000D0248157FE07000000000000
    TABH+ 20(20) = 8A030000DC3B0000000000007C000000FFFFFFFF
    TABH+ 40(16) = 047E00006032000010000000C1248001
    store        = 0x0000000000000000
    ext1         = 0xD0248157FE070000
    shmId        = 0     (0x00000000)
    id           = 906   (0x8A030000)
    label        = 15324 (0xDC3B0000)
    fill         = 0     (0x00000000)
    leng         = 124   (0x7C000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000254
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0x3098C957FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x209BD757FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    IT_ORGDATA
    0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.
    22200000000000000002222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000000000
    00000000000000000000000000000000000000000000000000000000000000
    SY-REPID
    SAPLBBP_PD
    5454445554222222222222222222222222222222
    310C220F04000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    C_SUBTYPE_IV
    IV
    45
    96
    00
    00
    LT_ITEM_PR-GUID
    9#Ä# y#F¼#_#²íÏÆ
    31C02704B850BECC
    9F420986C2F32DF6
    C_SUBTYPE_IV_OLD
    22
    00
    00
    00
    C_OFF
    2
    0
    0
    0
    C_CFR_QUEUEID
    CFR
    445
    362
    000
    000
    SY-SUBRC
    0
    0000
    0000
    SYST-REPID
    SAPLBBP_PD
    5454445554222222222222222222222222222222
    310C220F04000000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    C_XMLDISPATCHER
    XDP
    545
    840
    000
    000
    LT_ITEM_PR
    ############CONTRACT01  ####CONTRACT01  BUS2121001FF                                      #
    2223C20B5BC07144445544533220714444554453322455333333344222222222222222222222222222222222222229
    0009408CF2F20043FE42134010020043FE42134010025321210016600000000000000000000000000000000000000F
    000107480EC0522000000000000052200000000000000000000000000000000000000000000000000000000000000B
    000F29623D6003C000000000000003C000000000000000000000000000000000000000000000000000000000000001
    LT_BUDGET_LINES-TARGET_OBJECT
    2222222222
    0000000000
    0000000000
    0000000000
    C_DATA_SOURCE_BIDDER
    0SRM_TD_BIDDER
    355455454444452222222222222222
    032DF44F2944520000000000000000
    000000000000000000000000000000
    000000000000000000000000000000
    C_A_AUCTIONING
    AUGO
    4544
    157F
    0000
    0000
    C_A_CS_TEMPLATE
    SCVO
    5454
    336F
    0000
    0000
    No.      10 Ty.          FORM
    Name  PROCDOC_CROSS_CHECKS
    LT_LIMIT[]
    Table IT_15323[0x342]
    FUNCTION-POOL=BBP_PDFORM=PROCDOC_CROSS_CHECKSDATA=LT_LIMIT[]
    Table reference: 898
    TABH+  0(20) = 0000000000000000605B6E57FE07000000000000
    TABH+ 20(20) = 82030000DB3B00000000000056010000FFFFFFFF
    TABH+ 40(16) = 047E00000032000010000000C1308001
    store        = 0x0000000000000000
    ext1         = 0x605B6E57FE070000
    shmId        = 0     (0x00000000)
    id           = 898   (0x82030000)
    label        = 15323 (0xDB3B0000)
    fill         = 0     (0x00000000)
    leng         = 342   (0x56010000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000252
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0x400C5457FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x404BD257FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    LT_LIMIT
    0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1. ####     ########
    2220000000000000000000020000222220000000022222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000C0000C000000000000000000000000000000000000000000000000000000000000000000
    L_HEADER
    ########1000000257SHC 20070430CONTRACT01 04/30/2007 22:33             EDS1CLNT150SRM_SE 550
    2229EFF90CA33333333335442333333334445544533233233233332333332222222222222445344453335545542333
    000F93834F510000002573830200704303FE4213401004F30F2007022A33000000000000054313CE415032DF350550
    000B2D44B7100000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0001090E4F700000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LV_SC_BUDGET_CHECK
    X
    5
    8
    0
    0
    SY-XPROG
    SAPLSCSMROUTE
    5454545454554222222222222222222222222222
    310C333D2F545000000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    C_PRINTCONVERSION
    PCO
    544
    03F
    000
    000
    %_PRINT
    000                                                                                0###
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LT_ITEM[]
    Table IT_15322[1x5848]
    FUNCTION-POOL=BBP_PDFORM=PROCDOC_CROSS_CHECKSDATA=LT_ITEM[]
    Table reference: 904
    TABH+  0(20) = 903A9757FE070000900E2D57FE07000000000000
    TABH+ 20(20) = 88030000DA3B000001000000D8160000FFFFFFFF
    TABH+ 40(16) = 047E0000502D000002000000C1308401
    store        = 0x903A9757FE070000
    ext1         = 0x900E2D57FE070000
    shmId        = 0     (0x00000000)
    id           = 904   (0x88030000)
    label        = 15322 (0xDA3B0000)
    fill         = 1     (0x01000000)
    leng         = 5848  (0xD8160000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000227
    occu         = 2     (0x02000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xD01CD857FE070000
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 10300 (0x3C280000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 2     (0x02000000)
    lineAlloc    = 2     (0x02000000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xA026C957FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xE03AD257FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    LT_ITEM
    ############CONTRACT01  ####CONTRACT01  BUS2121001FF                                      #
    2223C20B5BC07144445544533220714444554453322455333333344222222222222222222222222222222222222229
    0009408CF2F20043FE42134010020043FE42134010025321210016600000000000000000000000000000000000000F
    000107480EC0522000000000000052200000000000000000000000000000000000000000000000000000000000000B
    000F29623D6003C000000000000003C000000000000000000000000000000000000000000000000000000000000001
    LT_ACC[]
    Table IT_15320[0x816]
    FUNCTION-POOL=BBP_PDFORM=PROCDOC_CROSS_CHECKSDATA=LT_ACC[]
    Table reference: 905
    TABH+  0(20) = 0000000000000000C007B557FE07000000000000
    TABH+ 20(20) = 89030000D83B00000000000030030000FFFFFFFF
    TABH+ 40(16) = 047E0000302F000010000000C1308001
    store        = 0x0000000000000000
    ext1         = 0xC007B557FE070000
    shmId        = 0     (0x00000000)
    id           = 905   (0x89030000)
    label        = 15320 (0xD83B0000)
    fill         = 0     (0x00000000)
    leng         = 816   (0x30030000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000237
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xE0147957FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x109AD757FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    LT_ACC
    ##################0000      ########                                   0000000000
    2220000000000000000003333222222000000002222222222222222222222222222222222233333333332222222222
    00000000000000000000C0000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LT_ACC_ACTVAL[]
    Table IT_15321[0x152]
    FUNCTION-POOL=BBP_PDFORM=PROCDOC_CROSS_CHECKSDATA=LT_ACC_ACTVAL[]
    Table reference: 908
    TABH+  0(20) = 00000000000000004062D257FE07000000000000
    TABH+ 20(20) = 8C030000D93B00000000000098000000FFFFFFFF
    TABH+ 40(16) = 047E0000903E000010000000C1308001
    store        = 0x0000000000000000
    ext1         = 0x4062D257FE070000
    shmId        = 0     (0x00000000)
    id           = 908   (0x8C030000)
    label        = 15321 (0xD93B0000)
    fill         = 0     (0x00000000)
    leng         = 152   (0x98000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000319
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0x90262A57FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x409DD757FE070000
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    LT_ACC_ACTVAL
    0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.   ################################
    0000000000000000000000000000000000002220000000000000000000000000000000022222
    0000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000
    00000000000C000C000C000C000C000C000C000000C000C000C000C000C000C000C000C00000
    LT_PARTNER[]
    Table IT_15325[0x4212]
    FUNCTION-POOL=BBP_PDFORM=PROCDOC_CROSS_CHECKSDATA=LT_PARTNER[]
    Table reference: 920
    TABH+  0(20) = 000000000000000070E32C57FE07000000000000
    TABH+ 20(20) = 98030000DD3B00000000000074100000FFFFFFFF
    TABH+ 40(16) = 047E0000C02F000002000000C1308001
    store        = 0x0000000000000000
    ext1         = 0x70E32C57FE070000
    shmId        = 0     (0x00000000)
    id           = 920   (0x98030000)
    label        = 15325 (0xDD3B0000)
    fill         = 0     (0x00000000)
    leng         = 4212  (0x74100000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000240
    occu         = 2     (0x02000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)

  • Activity stream not up to date ?

    After upgrading to Lightroom CC on my iMac 27" late 2013 the activity stream in Creative Cloud displays old activity 400 days ago.
    I have logged out and in again and still no change.
    It is not a problem and everything is working perfect - but if anyone knows why, I´d like to fix it.
    Regards
    Lars C.
    Denmark

    Hi Peter,
    Thanks for you answer.
    In ST22 I can see the error Uncaught_exception, CX_BBP_PD_ABORT. It looks like it terminated in the program SAPLBBP_PDH with main program SAPLBBP_PO_UI_ITS.
    If I look at Internal errors in RZ20 I can see the following:
    ABORT: FORM CHECK_PARTNER_EXISTENCE SAPLBBP_PDBUP/ FORM
    PDBUP_MAINTAIN_ALL SAPLBBP_PDBUP
    Sincerely
    Anders

  • UNCAUGHT_EXCEPTION runtime errors when changing the PO

    Hi everyone,
    We are facing the problem which is when changing the PO short dump UNCAUGHT_EXCEPTION is occurred then it will display "The page cannot be displayed"
    I don't know what is the exactly that cause of this problem
    Anyone who facing the same problem before, pls help on this. Hope anyone can help us on this.
    Thanks,
    quare

    Hi Disha,
    I found that only this PO cannot be change. Others are ok. There is an error in ST22 which is as below:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Except.                CX_BBP_PD_ABORT
    Error analysis
        An exception occurred. This exception is dealt with in more detail below
        . The exception, which is assinged to the class 'CX_BBP_PD_ABORT', was not
         caught,
        which led to a runtime error.
        The reason for this exception is:
        Übernehmen
    After further search of error there is also message that relates to this error:
    Buffer table not up to date
    Message no. BBP_PD001
    Diagnosis
    In FORM CHANGE_VERSION_MAP_ORG (function group SAPLBBP_PDCV) an inconsistent status was discovered.
    Procedure
    Start the transaction again. If the error occurs again, create an OSS message.
    To analyze the error, you can set a breakpoint in the function module 'BBP_PD_ABORT' and look at the call-up hierarchy in debugging mode.
    I wondering what is the problem. Since it occurs not for all PO but certain PO only.
    Please help.
    Thanks,
    quare

  • Early watch alert Dump:UNCAUGHT_EXCEPTION+ CX_DSVAS_API_CONTEXT_INSTANCE

    Hello All,
    I am facing issue while generating the early watch alert :
    In DSWP its showing ,DATA is available ;SAP earlywatch alert Session number :<>
    After processing button :  Start service processing
    Job schduling and getting failed Job Log:
    Job log overview for job:    SM:EXEC SERVICES 000000106120000 / 10520300
    Date       Time     Message text                                                                                Message class Message no. Message type
    02-06-2012 10:52:03 Job started                                                                                00           516          S
    02-06-2012 10:52:03 Step 001 started (program RDSMOPBACK_AUTOSESSIONS, variant &0000000000558, user ID BASISUSER)           00           550          S
    02-06-2012 10:52:03 MemSize Begin = 1368192   Bytes                                                                         DMD          000          I
    02-06-2012 10:52:05 Solution <000000106120000> "SID..." is being edited (Operations)                                       DSWP          438          S
    02-06-2012 10:52:05 <000000106120000> "SID..."(Operations)                                                                  DMD          000          I
    02-06-2012 10:52:05  ( EW_ALERT ) Session 2000000001331 for 02-13-2012 created (QDV)                                       DSWP          506          S
    02-06-2012 10:52:05 Difference "Create_Periodic_Services" = 278528                                                          DMD          000          I
    02-06-2012 10:52:05 Trying to perform session EC2000000001313                                                              DSWP          492          S
    02-06-2012 10:52:08 MODEL_KEY: SID <Installation Number> HANDLE: 6  MODEL_MODE: E  MODEL_VERSNR 00001 MODEL_CLASS: EWA Data Model      DMD          000          I
    02-06-2012 10:52:43 Internal session terminated with a runtime error (see ST22)                                             00           671          A
    02-06-2012 10:52:43 Job cancelled                                                                                00           518          A
    St22: Dump Log:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_DSVAS_API_CONTEXT_INSTANCE
    Date and Time          02-06-2012 10:52:43
    Short text
         An exception occurred that was not caught.
    What happened?
         The exception 'CX_DSVAS_API_CONTEXT_INSTANCE' was raised, but it was not caught
          anywhere along
         the call hierarchy.
         Since exceptions represent error situations and this error was not
         adequately responded to, the running ABAP program 'SAPLDSVAS_PROC' has to be
         terminated.
    Please post your valubale suuggestions and how to proceed further.
    Thanks
    Nekkalapu

    HI Arjun,
    Earlier (upto jan15th ) its working fine no issues generating earlywatch alerts .
    After 15th onwards i am facing this issue i have not done any chnages in configuration part.
    As per your suggestion I have checked the below points:
    1)transaction AGS_UPDATE is up to date ?
    Answer:AGS_UPDATE is updated (ALL availeble updates are downloaded) and its showing green color 3 options .
    2)able to connect to your satellite system via Trusted RFC or able to create sessions?
    Answer: Yes its generating sessions probelm while running dswp t code genarating sessions only.
    3)RTCCTOOL showing all green ?
    Answer:
    Five are showing in red and two are showing green
    Red:
    Addon upgrade ST-A/PI 01N_700SOL
    ST-A/PI Addon Supportpackage SP01
    Proc. after addon impl.
    Switch on digital content verification
    ST-PI Support Packages
    Green:
    Addon ST-PI 2008_1_700
    Collectors and TCOLL
    Kindly please suggest how to proceed further.
    Thanks
    Nekkalapu

  • Error while executing query on portal-SAPMSSY1 method : UNCAUGHT_EXCEPTION

    Hello all,
    I have created a quey and executed it on portal and everything just works fine. The query has few input varaibles at the start like fiscal year and some other inputs. I saved the query in my Portal favorites and then when I try to excute it from there it gives me a runtime BI error.
    Termination message sent ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION  MSGV1: SAPMSSY1  MSGV3: UNCAUGHT_EXCEPTION
    I guess it errors out because of the variable input part at the start of query.
    We already have note "950992" in the system so wonder what next now.
    Any inputs appreciated.
    Thanks,
    Kiran

    We are having the same issue too - we are SP13. Our query is built on a Infoset, and the problem comes with 0FISCPER variable, when we try to do a input help (F4) in Bex. this happens only when I use fiscper on queries bulit on INFOSETS, and it works perfectly alright with all other cubes.
    <i>System error in program CL_RSMD_RS_SPECIAL and form
    IF_RSMD_RS~READ_META_DATA-02 (see long text)
        Message no. BRAIN299
    Diagnosis
        This internal error is an intended termination resulting from a program
        state that is not permitted.
    Procedure
        Analyze the situation and inform SAP.
        If the termination occurred when you executed a query or Web template,
        or during interaction in the planning modeler, and if you can reproduce
        this termination, record a trace (transaction RSTT).</i>
        For more information about recording a trace, see the documentation for
        the trace tool environment as well as SAP Note 899572.
    and in portal, it gets to the point of variable screen and then throws a error msg.
    <i>ABEND RSBOLAP (000): Program error in class SAPMSSY1 method : UNCAUGHT_EXCEPTION
      MSGV1: SAPMSSY1
      MSGV3: UNCAUGHT_EXCEPTION</i>
    Message was edited by:
            voodi
    Message was edited by:
            voodi

  • Runtime Errors UNCAUGHT_EXCEPTION and Exception CX_RSR_COB_PRO_NOT_FOUND

    Hi ,
    When i tried to load data into my standard cube the following short dump error occure.
    The data was updated to PSA but while updating to further data target (my standard cube) the following error occured:
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_RSR_COB_PRO_NOT_FOUND
    Date and Time          2010.12.13 10:20:48
    Short text
         An exception occurred that was not caught.
    What happened?
         The exception 'CX_RSR_COB_PRO_NOT_FOUND' was raised, but it was not caught
          anywhere along
         the call hierarchy.
         Since exceptions represent error situations and this error was not
         adequately responded to, the running ABAP program
          'CL_RSR========================CP' has to be
         terminated.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_RSR_COB_PRO_NOT_FOUND', was not
         caught and
        therefore caused a runtime error.
        The reason for the exception is:
        0REQUEST is not a valid characteristic for InfoProvider

    Please check the infoobject 0REQUEST, whether it is in active state, if not acivate it.
    Check for 0REQUEST Object in Infocube level at characteristics tab, if it is not available try to add this characteristic to cube.
    if 0REQUEST is not available, install it from the content and include it in the cube.
    rgds, Ghuru

  • Runtime Error : UNCAUGHT_EXCEPTION

    Hi Solman Experts,
    While downloading softwares through Maintenace Optimizer ( Solution Manager ),I am getting below error..
    First Error :
    Function module /SDF/AL_MAP_TRANSID_LOGH does not exist.
    The Maintenance Optimizer can automatically determine which files you require to update the ABAP and Java software components of your systems.
    The search is performed for all instances of the selected systems flagged as relevant.
    I have already checked in service market place and apply the SAP note 1135893 and we have activate the some components (BC Set)
    See Note 898614 after that i am getting big problem.
    Second Error : ( ABAP Dump )
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SOCM_NOT_IMPLEMENTED
    Date and Time          31.03.2008 15:04:31
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_SOCM_NOT_IMPLEMENTED' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_CHM1_CHANGE_REQU_INSTANCE==CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_SOCM_NOT_IMPLEMENTED', was not
    caught and
    therefore caused a runtime error.
    The reason for the exception is:
    An exception occurred
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    *"UNCAUGHT_EXCEPTION" "CX_SOCM_NOT_IMPLEMENTED"
    "CL_CHM1_CHANGE_REQU_INSTANCE==CP" or "CL_CHM1_CHANGE_REQU_INSTANCE==CM009"
    "IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION"*
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "ALBE0510"
    Network address...... "10.201.180.10"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "ALBE0510"
    Database type..... "MSSQL"
    Database name..... "SP0"
    Database user ID.. "sp0"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Oct 23 2007 00:33:51"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQL_Server_8.00 "
    Patch level. 133
    Patch text.. " "
    Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 16192
    EM...... 41898400
    Heap.... 0
    Page.... 40960
    MM Used. 33604960
    MM Free. 4099184
    User and Transaction
    Client.............. 001
    User................ "KONS222"
    Language key........ "E"
    Transaction......... "DSWP "
    Transactions ID..... "AE21FFDCBA44F199AB15005056836080"
    Program............. "CL_CHM1_CHANGE_REQU_INSTANCE==CP"
    Screen.............. "RDSMOP_MAIN 0100"
    Screen line......... 5
    Information on where terminated
    Termination occurred in the ABAP program "CL_CHM1_CHANGE_REQU_INSTANCE==CP" -
    in "IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION".
    The main program was "RDSMOP_MAIN ".
    In the source code you have the termination point in line 612
    of the (Include) program "CL_CHM1_CHANGE_REQU_INSTANCE==CM009".
    Source Code Extract
    Line
    SourceCde
    582
    conditions_ok =  cl_socm_integration=>false.
    583
    ENDIF.
    584
    ENDIF.
    585
    586
    WHEN 'S_USER_CHECK'.
    587
    conditions_ok =  cl_socm_integration=>true.
    588
    CALL METHOD cl_sm_base_sender=>get_assigned_suser
    589
    EXPORTING
    590
    i_no_dialogue      = 'X'
    591
           IMPORTING
    592
             e_suser            = e_suser
    593
             e_partner_no       = lv_parnr
    594
    EXCEPTIONS
    595
    no_user_assigned   = 1
    596
    no_customer_number = 2
    597
    OTHERS             = 3.
    598
    IF sy-subrc  = 1 OR sy-subrc = 3.
    599
    conditions_ok =  cl_socm_integration=>false.
    600
    ENDIF.
    601
    WHEN 'NO_CRTCL_OBJ'.
    602
    conditions_ok = me->check_crtcl_obj( ).
    603
    WHEN '0NO'.
    604
    conditions_ok =  cl_socm_integration=>false.
    605
    WHEN '0YES'.
    606
    conditions_ok =  cl_socm_integration=>true.
    607
    WHEN '0BREAK'.
    608
    BREAK-POINT.                                         "#EC NOBREAK
    609
    WHEN space.
    610
    avoid exception since it is the default in table   TSOCM_COND_MAPP
    611
    WHEN OTHERS.
    >>>>>
    RAISE EXCEPTION TYPE cx_socm_not_implemented.
    613
    ENDCASE.
    614
    615
    ENDMETHOD.
    Please suggest. Thanks in Advance...
    Regards,
    Suresh Kumar

    Hi Ruben,
    I have Implemented  both notes now i am getting differt error...
    Error is : Error No customer numbers in transaction AISUSER ...
    Message Number: SOLMAN_SAP_BACKEND016
    Diagnosis
    There are no entries with a customer number in the 'Customer Number' field in the table AISUSER.
    System Response
    You cannot get customer number-specific RFC destinations.
    Procedure
    Maintain these entries manually or start the report
    SMBI_AISUSER_VAR_MIG to copy any existing customer number from the table AISDK_CF_OSS_USR.
    Please suggest..
    Thanks in Advance..
    Regards,
    Suresh Kumar
    Edited by: suresh k on Apr 15, 2008 3:15 PM

  • ABAP/4 processor: UNCAUGHT_EXCEPTION while activation

    Hi All,
    I am getting this error "ABAP/4 processor: UNCAUGHT_EXCEPTION" while the activation of DSO. I am attaching the dump
    Runtime Errors         UNCAUGHT_EXCEPTION
    Exception              CX_SDB_ORA_PROGRAM_ERROR
    Date and Time          19.12.2008 03:02:53
    Short text
    An exception occurred that was not caught.
    What happened?
    The exception 'CX_SDB_ORA_PROGRAM_ERROR' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CL_SDB_ORA_UPDATE_STATS=======CP' has to be
    terminated.
    What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
    Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
    caught and
    therefore caused a runtime error.
    The reason for the exception is:
    An error occurred in the program:
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
    "CL_SQL_STATEMENT==============CP",
    specifically in line 31 of the (include) program
    "CL_SQL_STATEMENT==============CM002".
    The cause of the exception was:
    ORA-04031: unable to allocate 62208 bytes of shared memory ("shared
    pool","DBMS_STATS","PL/SQL MPCODE","BAMIMA: Bam Buffer")
    ORA-06508: PL/SQL:
    could not find program unit being called: "SYS.DBMS_STATS"
    ORA-06512: at line 1
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_SDB_ORA_PROGRAM_ERROR"
    "CL_SDB_ORA_UPDATE_STATS=======CP" or "CL_SDB_ORA_UPDATE_STATS=======CM00I"
    "UPDATE_STATS"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "gwpsapci"
    Network address...... "10.220.136.60"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "0005E935D600"
    Character length.... 8 Bits
    Pointer length....... 64 Bits
    Work process number.. 30
    Shortdump setting.... "full"
    Database server... "de08u1642"
    Database type..... "ORACLE"
    Database name..... "GWP"
    Database user ID.. "SAPR3"
    Char.set.... "en_US.ISO8859-1"
    SAP kernel....... 700
    created (date)... "Aug 24 2008 21:05:40"
    create on........ "AIX 2 5 005DD9CD4C00"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 175
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"
    Memory consumption
    Roll.... 16128
    EM...... 25139520
    Heap.... 0
    Page.... 24576
    MM Used. 12500304
    MM Free. 4256248
    User and Transaction
    Client.............. 950
    User................ "ZZSUPPORT"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "494AFB8FEB5A00D6E10080000ADC883C"
    Program............. "CL_SDB_ORA_UPDATE_STATS=======CP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    Termination occurred in the ABAP program "CL_SDB_ORA_UPDATE_STATS=======CP" -
    in "UPDATE_STATS".
    The main program was "RSPROCESS ".
    In the source code you have the termination point in line 40
    of the (Include) program "CL_SDB_ORA_UPDATE_STATS=======CM00I".
    The program "CL_SDB_ORA_UPDATE_STATS=======CP" was started as a background job.
    Job Name....... "BI_PROCESS_ODSACTIVAT"
    Job Initiator.. "E442207"
    Job Number..... 03030600
    Source Code Extract
    Line
    SourceCde
    10
    i_tablnm      = i_tablnm
    11
    i_signi       = i_signi
    12
    i_thresh_mod  = i_thresh_mod
    13
    i_degree      = i_degree
    14
    i_histo       = i_histo
    15
    i_granularity = i_granularity
    16
    i_cascade     = i_cascade
    17
    i_force       = i_force
    18
    i_flush       = i_flush
    19
    i_connection  = i_connection.
    20
    21
        Update Statistics
    22
    IF l_r_upd_stats->p_skip_upd IS initial.
    23
    CASE l_r_upd_stats->p_granularity.
    24
    WHEN 0. " DEFT
    25
    IF l_r_upd_stats->global_update_stats( ) = 'NO'.
    26
    l_r_upd_stats->part_update_stats( ).
    27
    ENDIF.
    28
    WHEN 1. " ALL
    29
    l_r_upd_stats->global_update_stats( ).
    30
    WHEN 2. " GLOBAL
    31
    l_r_upd_stats->global_update_stats( ).
    32
    WHEN 3. " PART
    33
    l_r_upd_stats->part_update_stats( ).
    34
    WHEN OTHERS. " AUTO
    35
    l_r_upd_stats->global_update_stats( ).
    36
    ENDCASE.
    37
    ENDIF.
    38
    39
    CATCH cx_sql_exception INTO l_r_exception.
    >>>>>
    RAISE EXCEPTION TYPE cx_sdb_ora_program_error
    41
    EXPORTING previous = l_r_exception.
    42
    CLEANUP.
    43
    TRY.
    44
    CATCH cx_sql_exception INTO l_r_exception.
    45
    RAISE EXCEPTION TYPE cx_sdb_ora_program_error
    46
    EXPORTING previous = l_r_exception.
    47
    ENDTRY.
    48
    ENDTRY.
    49
    50
    ENDMETHOD.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    0
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    Process Variant Run
    SY-MSGTY
    E
    SY-MSGID
    DA
    SY-MSGNO
    300
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20081219
    SY-UZEIT
    030252
    SY-XPROG
    SAPCNVE
    SY-XFORM
    CONVERSION_EXIT
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    6 METHOD       CL_SDB_ORA_UPDATE_STATS=======CP    CL_SDB_ORA_UPDATE_STATS=======CM00I    40
    CL_SDB_ORA_UPDATE_STATS=>UPDATE_STATS
    5 FUNCTION     SAPLRSDU_UTIL_ORA                   LRSDU_UTIL_ORAU01                      86
    RSDU_ANALYZE_TABLE_ORA
    4 FUNCTION     SAPLRSDU_UTIL                       LRSDU_UTILU01                          38
    RSDU_ANALYZE_TABLE
    3 FUNCTION     SAPLRSSM_PROCESS                    LRSSM_PROCESSU30                     1476
    RSSM_PROCESS_ODSACTIVATE
    2 METHOD       CL_RSSM_ODSACTIVATE===========CP    CL_RSSM_ODSACTIVATE===========CM007   117
    CL_RSSM_ODSACTIVATE=>IF_RSPC_EXECUTE~EXECUTE
    1 EVENT        RSPROCESS                           RSPROCESS                             144
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       6 Ty.          METHOD
    Name  CL_SDB_ORA_UPDATE_STATS=>UPDATE_STATS
    I_TABLNM
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    I_SIGNI
    5775488
    0
    0
    I_THRESH_MOD
    0
    0000
    0000
    I_DEGREE
    3
    0000
    0003
    I_HISTO
    2
    0
    I_GRANULARITY
    0
    0000
    0000
    I_CASCADE
    0
    0000
    0000
    I_FORCE
    2
    0
    I_FLUSH
    X
    5
    8
    I_CONNECTION
    222222222222222222222222222222
    000000000000000000000000000000
    SPACE
    2
    0
    L_R_UPD_STATS
    |
    | 0000000F |
    | 80000027 |
    | %_DUMMY$$ |
    |  |
    | 2222 |
    | 0000 |
    | SY-REPID |
    | CL_SDB_ORA_UPDATE_STATS=======CP |
    | 4455445454555445455545533333334522222222 |
    | 3CF342FF21F504145F34143DDDDDDD3000000000 |
    | SY-XFORM |
    | CONVERSION_EXIT |
    | 444545544454545222222222222222 |
    | 3FE65239FEF5894000000000000000 |
    | L_R_EXCEPTION |
    |
    E0000001
    80000037
    SYST
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    SY
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    %_EXCP
    E0000001
    70000038
    %_SPACE
    2
    0
    SYST-REPID
    CL_SDB_ORA_UPDATE_STATS=======CP
    4455445454555445455545533333334522222222
    3CF342FF21F504145F34143DDDDDDD3000000000
    No.       5 Ty.          FUNCTION
    Name  RSDU_ANALYZE_TABLE_ORA
    I_ALL_COLUMNS
    2
    0
    I_FORCE_ESTIMATE
    X
    5
    8
    I_FORCE_STATISTICS
    2
    0
    I_PERCENTAGE
    1
    0000
    0001
    I_PERCENTAGE_SPECIFIED
    X
    5
    8
    I_TABLNM
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    I_TEMP_TABLE
    2
    0
    I_T_TABLNM
    Table[initial]
    C_PROCESSED
    2
    0
    SY-REPID
    SAPLRSDU_UTIL_ORA
    5454554555544545422222222222222222222222
    310C2345F549CFF2100000000000000000000000
    <L_TABLNM>
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    SYST-REPID
    SAPLRSDU_UTIL_ORA
    5454554555544545422222222222222222222222
    310C2345F549CFF2100000000000000000000000
    %_SPACE
    2
    0
    SY
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    %_DUMMY$$
    2222
    0000
    L_SIGNI
    5775488
    0
    0
    L_PARALLEL_DEGREE
    3
    0000
    0003
    L_HISTO
    2
    0
    L_FLUSH
    X
    5
    8
    SY-ONCOM
    S
    5
    3
    No.       4 Ty.          FUNCTION
    Name  RSDU_ANALYZE_TABLE
    I_FORCE_ESTIMATE
    X
    5
    8
    I_FORCE_STATISTICS
    2
    0
    I_PERCENTAGE
    1
    0000
    0001
    I_TABLNM
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    I_TEMP_TABLE
    2
    0
    I_T_TABLNM
    Table[initial]
    SYST-REPID
    SAPLRSDU_UTIL
    5454554555544222222222222222222222222222
    310C2345F549C000000000000000000000000000
    RSDU_C_OBJTYPE-VIEW
    VIEW
    5445
    6957
    L_DBFUNC
    RSDU_ANALYZE_TABLE_ORA
    554554444554554444545422222222
    2345F1E1C9A5F412C5FF2100000000
    SY-XFORM
    CONVERSION_EXIT
    444545544454545222222222222222
    3FE65239FEF5894000000000000000
    L_PERCENTAGE_SPECIFIED
    X
    5
    8
    %_VIASELSCR
    0
    4
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_PROCESSED
    2
    0
    RS_C_FALSE
    2
    0
    SY-SUBRC
    0
    0000
    0000
    SCREEN
    %_17NNS0000194530_%_%_%_%_%_%_
    2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
    5F17EE30000194530F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
    SY-REPID
    SAPLRSDU_UTIL
    5454554555544222222222222222222222222222
    310C2345F549C000000000000000000000000000
    L_MESSAGE
    222222222222222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000000000000000
    No.       3 Ty.          FUNCTION
    Name  RSSM_PROCESS_ODSACTIVATE
    I_CRT_ACTIVATION
    2
    0
    I_DROP_CREA_SEC_IND
    2
    0
    I_INSTANCE
    ODSA_4C7HUKHW8WV06KLJFFYZP95BW
    445453434544535533444445553345
    F431F43785B8787606BCA669A09527
    I_JOBNAME
    BI_PROCESS_ODSACTIVAT
    44555444555445445454522222222222
    29F02F3533FF43134961400000000000
    I_LOG_ID
    4C7HSJQKN58AR2DG5NSOGNB5O
    3434545443345344345444434
    43783A1BE58122475E3F7E25F
    I_NO_CONDENSE
    2
    0
    I_ODSOBJECT
    OD13ITM3
    443345432222222222222222222222
    F41394D30000000000000000000000
    I_PARENT_BATCH_ID
    222222222222222222222222222222
    000000000000000000000000000000
    I_SERIALIZE
    2
    0
    I_T_REQUEST_SEL
    Table[initial]
    I_VARIANT
    OD13ITM3_ACTIVATE
    443345435445454542222222222222
    F41394D3F134961450000000000000
    I_WITH_COMMIT
    X
    5
    8
    E_ERROR
    2
    0
    E_RNR
    ODSR_4C7HULKAVPVJRPAS8MAP3IYWS
    445553434544455545545344534555
    F432F43785CB1606A20138D1039973
    E_T_ACTIVATE_RNR
    Table[initial]
    E_T_ERROR_RNR
    Table[initial]
    E_T_MSG
    Table IT_18345[3x704]
    CLASS=CL_RSSM_ODSACTIVATEMETHOD=IF_RSPC_EXECUTE~EXECUTEDATA=L_T_MSG_PROC
    Table reference: 123
    TABH+  0(20) = 07000000A05FD4B0000000000000000000000000
    TABH+ 20(20) = 0000007B000047A900000003000002C0FFFFFFFF
    TABH+ 40(16) = 0400012500000D40001024C401800000
    store        = 0x07000000A05FD4B0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 123   (0x0000007B)
    label        = 18345 (0x000047A9)
    fill         = 3     (0x00000003)
    leng         = 704   (0x000002C0)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000050
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000A05750F0
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 10517 (0x00002915)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    E_T_ODSR_RNR
    Table[initial]
    L_LINES
    0
    0000
    0000
    %_DUMMY$$
    2222
    0000
    SCREEN
    %_17NNS0000194530_%_%_%_%_%_%_
    2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
    5F17EE30000194530F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
    SY-REPID
    SAPLRSSM_PROCESS
    5454555455544455222222222222222222222222
    310C233DF02F3533000000000000000000000000
    SY-MSGID
    DA
    44222222222222222222
    41000000000000000000
    G_CHANGED
    2
    0
    SPACE
    2
    0
    SY-MSGNO
    300
    333
    300
    SY-MSGV1
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV2
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV3
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    SY-MSGV4
    22222222222222222222222222222222222222222222222222
    00000000000000000000000000000000000000000000000000
    L_PERFORMED_ANALYZE
    2
    0
    G_R_ALV_GRID
    F0000000
    F0000000
    RS_C_TRUE
    X
    5
    8
    L_S_ODSTABNAME-M_TAB
    /BIC/AOD13ITM340
    244424443345433322222222222222
    F293F1F41394D34000000000000000
    SYST
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    <%_TABLE_RSDS>
    RSAU_C_PROTCLASS
    1234
    3333
    1234
    SYST-REPID
    SAPLRSSM_PROCESS
    5454555455544455222222222222222222222222
    310C233DF02F3533000000000000000000000000
    G_BUTTON_REQUDEL
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_SPACE
    2
    0
    No.       2 Ty.          METHOD
    Name  CL_RSSM_ODSACTIVATE=>IF_RSPC_EXECUTE~EXECUTE
    I_VARIANT
    OD13ITM3_ACTIVATE
    443345435445454542222222222222
    F41394D3F134961450000000000000
    I_EVENT_START
    RSPROCESS
    55554445522222222222222222222222
    2302F353300000000000000000000000
    I_EVENTP_START
    4BO77YTX6F8UVLQ22AEHHYIPO
    3443355534355453344445454222222222222222222222222222222222222222
    42F7794866856C1221588990F000000000000000000000000000000000000000
    I_JOBCOUNT
    03030600
    33333333
    03030600
    I_BATCHDATE
    20081218
    33333333
    20081218
    I_BATCHTIME
    030306
    333333
    030306
    I_T_PROCESSLIST
    Table IT_123[18x528]
    PROGRAM=RSPROCESSDATA=G_T_PROCESSLIST
    Table reference: 37
    TABH+  0(20) = 07000000A02596D8000000000000000000000000
    TABH+ 20(20) = 000000250000007B0000001200000210FFFFFFFF
    TABH+ 40(16) = 040000740000116800102CC421800000
    store        = 0x07000000A02596D8
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 37    (0x00000025)
    label        = 123   (0x0000007B)
    fill         = 18    (0x00000012)
    leng         = 528   (0x00000210)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000069
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000A0262CF0
    pgHook       = 0x07000000A0258600
    idxPtr       = 0x07000000A0259788
    shmTabhSet   = 0x0000000000000000
    id           = 93    (0x0000005D)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32    (0x00000020)
    lineAlloc    = 32    (0x00000020)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    I_LOGID
    4C7HSJQKN58AR2DG5NSOGNB5O
    3434545443345344345444434
    43783A1BE58122475E3F7E25F
    I_T_VARIABLES
    Table[initial]
    I_SYNCHRONOUS
    2
    0
    I_SIMULATE
    2
    0
    I_REPAIR
    222222222222222222222222222222
    000000000000000000000000000000
    I_BATCHID
    222222222222222222222222222222
    000000000000000000000000000000
    E_INSTANCE
    ODSA_4C7HUKHW8WV06KLJFFYZP95BW
    445453434544535533444445553345
    F431F43785B8787606BCA669A09527
    E_STATE
    2
    0
    E_EVENTNO
    00
    33
    00
    E_HOLD
    2
    0
    SY-REPID
    CL_RSSM_ODSACTIVATE===========CP
    4455554544544545454333333333334522222222
    3CF233DFF4313496145DDDDDDDDDDD3000000000
    <%_L003>-RNR
    L_T_REQUESTS
    Table[initial]
    L_S_REQUESTS
    222222222222222222222222222222
    000000000000000000000000000000
    SY-SUBRC
    0
    0000
    0000
    SYST-REPID
    CL_RSSM_ODSACTIVATE===========CP
    4455554544544545454333333333334522222222
    3CF233DFF4313496145DDDDDDDDDDD3000000000
    ICON_GREEN_LIGHT
    @08@
    4334
    0080
    L_JOBNAME
    BI_PROCESS_ODSACTIVAT
    44555444555445445454522222222222
    29F02F3533FF43134961400000000000
    L_S_SELE-NO_CONDENSE
    2
    0
    L_S_ODS-OBJECT
    OD13ITM3
    443345432222222222222222222222
    F41394D30000000000000000000000
    L_S_SELE-ODSACTSERIAL
    2
    0
    L_ERROR_PROC
    2
    0
    L_T_MSG_PROC
    Table IT_18345[3x704]
    L_T_MSG
    Table[initial]
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    G_VARIANT
    OD13ITM3_ACTIVATE
    443345435445454542222222222222
    F41394D3F134961450000000000000
    G_TYPE
    ODSACTIVAT
    4454454545
    F431349614
    %_DUMMY$$
    2222
    0000
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    G_OBJECT
    CL_RSSM_ODSACTIVATE
    445555454454454545422222222222
    3CF233DFF431349614500000000000
    G_INSTANCE
    222222222222222222222222222222
    000000000000000000000000000000
    SY
    #######################################################A#######ÿ###############(##############
    000000000000000000000000000000000000000000000000000000040000000F000000000000000200000000000000
    000000000000000100000000000000000000000000000000000100010001000F000000000000000800000000000000
    %_SPACE
    2
    0
    %_REPAIR_%_APP_%
    222222222222222222222222222222
    000000000000000000000000000000
    G_STATE
    2
    0
    G_EVENTID
    RSPROCESS
    55554445522222222222222222222222
    2302F353300000000000000000000000
    G_HOLD
    2
    0
    G_EVENTPARM
    4BO77YTX6F8UVLQ22AEHHYIPO
    3443355534355453344445454222222222222222222222222222222222222222
    42F7794866856C1221588990F000000000000000000000000000000000000000
    G_JOBCOUNT
    03030600
    33333333
    03030600
    G_BATCHDATE
    20081218
    33333333
    20081218
    G_EVENTNO
    00
    33
    00
    G_BATCHTIME
    030306
    333333
    030306
    G_T_VARIABLES
    Table[initial]
    G_T_PROCESSLIST
    Table IT_123[18x528]
    %F007017_1000
    Log ID (Internal Use Only)
    46624422467676662576246672222222222222222222222222222222222222222222222222222222222
    CF7094089E452E1C05350FEC99000000000000000000000000000000000000000000000000000000000
    G_LOGID
    4C7HSJQKN58AR2DG5NSOGNB5O
    3434545443345344345444434
    43783A1BE58122475E3F7E25F
    G_CHAIN
    ZLIS_13_VDITM
    5445533554454222222222222
    AC93F13F6494D000000000000
    G_REPAIR
    222222222222222222222222222222
    000000000000000000000000000000
    G_BATCHID
    INFO_4C7HUKA7PY9ANY239LWNF76M4
    444453434544355344533345443343
    9E6FF43785B170991E9239C7E676D4
    Internal notes
    The termination was triggered in function "raiseExcp"
    of the SAP kernel, in line 2099 of the module
    "//bas/700_REL/src/krn/runt/abexcp.c#7".
    The internal operation just processed is "EXCP".
    Internal mode was started at 20081219030246.
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    => 64 bit R/3 Kernel
    => 64 bit AIX Kernel
    => Heap limit      = unlimited
    => Stack limit     = unlimited
    => Core limit      = 1073741312
    => File size limit = unlimited
    => Heap address  = 0x1154fc6a0
    => Stack address = 0xfffffffffffb080
    => Stack low     =  0xfffffffffffb080
    => Stack high    =  0xffffffffffff880
    => Stack Trace:
         AixStack() at 0x1000a2474
         CTrcStack2() at 0x1000a256c
         rabax_CStackSave__Fv() at 0x1000d0e3c
         ab_rabax() at 0x1000cd81c
         raiseExcp__F6HeadId() at 0x100429ba0
         ab_jexcp__Fv() at 0x100428d30
         ab_extri__Fv() at 0x10038e6dc
         ab_xevent__FPCc() at 0x100ab5cc4
         ab_trigg__Fv() at 0x100ab59b0
         ab_run() at 0x1014d42dc
         N_ab_run() at 0x100ed3f4c
         dynpmcal() at 0x100ed2d40

    HI karthik..
    The Error Msg is due to insufficient memory while storing the Data in Database(i,e ODS) and this error UNCAUGH EXCEPTION will come due to " like there is an exception raised but no code to catch it(to activate the ODS)".
    so chk the problem with the Basis People... those guys can give clear info pertaining to this kind of  problems...
    Genereally in our case we raise ticket to Basis people..
    hope useful....
    cheers
    Sukhai..

Maybe you are looking for

  • Ignore alarms not working on subscribed-to shared calendar

    My wife shared her MobileMe calendar with me.  It shows up in my iCal as expected.  I see all the changes, updates, etc. However, I have checked "Ignore Alarms" on the Info pane and I still get alarms for all her appointments. Any ideas?

  • Standalone Weblogic deployment not working for ADF Table

    Hi All, I have create one application using JDeveloper 11g R3. I have taken one ADF Rich Table When i run application in Jdeveloper it runs fine. Now issue is when i deployee the same in standalone Weblogic server it is not running(Page gets open but

  • Font size too small on some sites on nokia 5230

    I have nokia 5230. Some pages like m.youtube.com display small font size even when font size is set to large. Why is that? IF YOU FIND POSTS HELPFUL HIT THE BIG GREEN BOX TO THE LEFT WITH THE WHITE STAR IN IT THANKS

  • What does "inkjet" mean/refer to?

    Hello, I am wondering what exactly "inkjet" means/refers to.  I am shopping used printers and am just a rube in need of a little education.  Thank you. This question was solved. View Solution.

  • Manufacturer Part Number on PM Work Order

    Hi experts, is there a way to put manufacturer part number on the PM work order?  We can do that on purchase order, but got an error on work order.  We want to use work order to create purchase requistion.  Thanks a lot!!!