ABAP Runtime Analysis

Hello,
We have very poor performance on your ERP ECC 6.0 EHP 3 system. We are using MaxDB 7.7.
We have done a abap runtime analysis (SE30) on transaction code FD03.
The result is the following:
http://img13.imageshack.us/img13/659/fd03.png
How can we solve this? And why is the system and abap execution time equal to zero?
Regards,
Vrmr

Hi,
Please perform SQL trace using ST05. Look at the action in SM50 where it is taking more time.
Check the CPU/MEMORY bottleneck issue at DB Server using ST02 and ST06.
Also refer the following useful links to get more info.
[FAQ's, intros and memorable discussions in the Performance and Tuning Forum|FAQ's, intros and memorable discussions in the Performance and Tuning Forum]
[SAP ABAP Runtime Analysis - SE30|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30864e70-77b9-2c10-449b-e0e584f73e8c?quicklink=index&overridelayout=true]
[SE30 -Measurement Overview|http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617d2ae68c11d2b2ab080009b43351/frameset.htm]
Regards,
Bhavik G. Shroff

Similar Messages

  • Program not in Library -- In ABAP Runtime Analysis SE30.. Plz Guide me guys

    Dear all,
    I have to execute one report program in SE30 ABAP Runtime Analysis tool. 
    So I have entered my program name in the SE30 but I have got 1 error  " Program ( pgm name ) not in Library ".
    Guys plz guide me on this asap.
    Edited by: PI User on Nov 26, 2010 11:14 AM
    Moderator message: too basic, too much SMS speak, too much "asap", thread locked, points removed.
    [Rules of engagement|http://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
    Edited by: Thomas Zloch on Nov 26, 2010 12:33 PM

    Hi
    The error message is clear: the program you're trying to test by SM30 is not SAP (your SAP system of course)
    Now try to check if you can see that program by SE38, but if you think the program is in SAP, prehaps you're running SM30 in another system:
    For example:
    the program was created in development system and you run SM30 in quality and that program hasn't been transported yet: so the program is in development but not in quality.
    Max

  • Can we perform runtime analysis(SE30) on Abap Webdynpro component..?

    hi,
    Greetings!!!
    Can we perform runtime analysis(SE30) on Abap Webdynpro component..?
    Thanks in Advacne.
    Regards,
    Kranthi.

    for sure !
    have a look here [https://wiki.sdn.sap.com/wiki/display/WDABAP/Performance%20Tuning%20for%20SAP%20%20Web%20Dynpro%20ABAP|https://wiki.sdn.sap.com/wiki/display/WDABAP/Performance%20Tuning%20for%20SAP%20%20Web%20Dynpro%20ABAP]

  • Runtime Analysis - ABAP, Database, System

    Hi All,
    The runtime analysis (SE30) of a program shows that the ABAP runtime is 96.1%; Database is 3.7% and system is 0.2% making an overall 100%.
    Is it good performance? the ABAP bar is shown in red color.
    Can you please explain about this.

    Hi,
    Yes i feel its good performance, generally if the control is most of the time with the application server, rather than in the database server then it considered good performance.
    According to you it is ABAP runtime is 96.1%; Database is 3.7% and system is 0.2%.
    We can see major time is in ABAP runtime and only few calls to database. So it is a good performance.
    Thanks & Regards,
    Navneeth K.

  • ABAP Runtime Error while executing planning folder

    Hi experts.
    We have a situation where I can access our planning folders but that's not the case for one of our user. She encountered with an ABAP Runtime Error as follow:
    Appreciate if anyone can help me out with this.
    Runtime Error          RAISE_EXCEPTION
    Date and Time          20.04.2007 16:50:23
    ShrtText
    Exception condition "X_MESSAGE" raised.
    What happened?
    The current ABAP/4 program encountered an unexpected
    situation.
    What can you do?
    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.
    Error analysis
    A RAISE statement in the program "SAPLRSSBR" raised the exception
    condition "X_MESSAGE".
    Since the exception was not intercepted by a superior program
    in the hierarchy, processing was terminated.
    Short description of exception condition:
    Cancel
    For detailed documentation of the exception condition, use
    Transaction SE37 (Function Library). You can take the called
    function module from the display of active calls.
    How to correct the error
    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:
    "RAISE_EXCEPTION" C
    "SAPLRSSBR" or "LRSSBRU03"
    "RSSB_AUTHORITY_IOBJVL_CHECK"
    or
    "SAPLRSSBR" "X_MESSAGE"
    or
    "UPB_PM_CUST_START " "X_MESSAGE"
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
    To obtain this, select in the current display "System->List->
    Save->Local File (unconverted)".
    2. A suitable printout of the system log
    To obtain this, call the system log through transaction SM21.
    Limit the time interval to 10 minutes before and 5 minutes
    after the short dump. In the display, then select the function
    "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
    supply the source code.
    To do this, select the Editor function "Further Utilities->
    Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
    or which actions and input led to the error.
    System environment
    SAP Release.............. "640"
    Application server....... "S53KJ165"
    Network address.......... "10.1.53.165"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C3A11F4C00"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 3
    Short dump setting....... "full"
    Database server.......... "S53KJ170"
    Database type............ "ORACLE"
    Database name............ "BWP"
    Database owner........... "SAPBWP"
    Character set............ "en_US.ISO8859-1"
    SAP kernel............... "640"
    Created on............... "Oct 29 2006 20:42:11"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "155"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    Memory usage.............
    Roll..................... 16128
    EM....................... 16759712
    Heap..................... 0
    Page..................... 57344
    MM Used.................. 10079624
    MM Free.................. 2487240
    SAP Release.............. "640"
    User and Transaction
    Client.............. 350
    User................ "S51643"
    Language key........ "E"
    Transaction......... "UPSPL "
    Program............. "SAPLRSSBR"
    Screen.............. "SAPLUPB_PM_ALV 1000"
    Screen line......... 2
    Information on where terminated
    The termination occurred in the ABAP program "SAPLRSSBR" in
    "RSSB_AUTHORITY_IOBJVL_CHECK".
    The main program was "UPB_PM_CUST_START ".
    The termination occurred in line 416 of the source code of the (Include)
    program "LRSSBRU03"
    of the source code of program "LRSSBRU03" (when calling the editor 4160).
    Source Code Extract
    Line
    SourceCde
    386
    l_s_range-low  = l_activity.
    387
    APPEND l_s_range TO l_sx_auth_check_detail-range.
    388
    INSERT l_sx_auth_check_detail INTO TABLE <l_sx_auth_check>-auth_check_detail.
    389
    390
    CALL FUNCTION 'RSSB_AUTHORITY_IOBJVL_REDUCED'
    391
    EXPORTING
    392
    i_infocube              = g_sx_iobjvl_check-infocube
    393
    i_uname                 = l_uname
    394
    i_th_hierarchy          = g_sx_iobjvl_check-hierarchy
    395
    i_message               = i_message
    396
    i_activity_force_check  = i_activity_force_check
    397
    CHANGING
    398
    c_tsx_auth_check_detail = <l_sx_auth_check>-auth_check_detail
    399
    c_tx_no_auth            = l_tx_no_auth
    400
    c_ts_auth_tlevel        = e_ts_auth_tlevel
    401
    EXCEPTIONS
    402
    user_not_authorized     = 1
    403
    auth_check_failure      = 2
    404
    auth_check_error        = 3
    405
    inherited_error         = 4
    406
    x_message               = 5.
    407
    IF sy-subrc = 0.
    408
    REFRESH l_tx_no_auth.
    409
      CR 20050826 HW873685 SP29 Part 2/3 begin
    410
      SY-SUBRC = 2 means Auth-Obj missing in users profiles, we need this later
    411
    ELSEIF sy-subrc = 2.
    412
    ao_missing = rs_c_true.
    413
    e_subrc = 2.
    414
      CR 20050826 HW873685 SP29 Part 2/3 end
    415
    ELSEIF sy-subrc = 5.
    >>>>>
    RAISE x_message.
    417
    ELSE.
    418
    e_subrc = 2.
    419
    ENDIF.
    420
    421
      correct the kid now
    422
    LOOP AT l_tx_no_auth INTO l_sx_no_auth.
    423
    l_sx_no_auth-kid = <l_sx_auth_check>-kid.
    424
    APPEND l_sx_no_auth TO  e_tx_no_auth.
    425
    ENDLOOP.
    426
    427
    ENDLOOP.
    428
    429
    End LOOP: Check all SUBNR (FEMS)
    430
    431
    432
    CR 20050826 HW873685 SP29 Part 3/3 begin
    433
    If an Auth-Obj. is missing, no SUBNR can be authorized. Due to OLAP-logic
    434
    this means empty no_auth table
    435
    IF ao_missing = rs_c_true.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    5
    SY-INDEX
    1
    SY-TABIX
    0
    SY-DBCNT
    0
    SY-FDPOS
    1
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    210
    SY-UCOMM
    SELECT
    SY-TITLE
    Execute All Cost Element
    SY-MSGTY
    E
    SY-MSGID
    R7
    SY-MSGNO
    057
    SY-MSGV1
    0CO_AREA
    SY-MSGV2
    A
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    40 FUNCTION     SAPLRSSBR                           LRSSBRU03                             416
    RSSB_AUTHORITY_IOBJVL_CHECK
    39 FORM         SAPLRSDRC                           LRSDRCF15                             113
    AUTHORITY_CHECK
    38 FORM         SAPLRSDRC                           LRSDRCF27                              57
    BASIC_QUERY_DATA_GET_ROLAP
    37 FUNCTION     SAPLRSDRC                           LRSDRCU05                              44
    RSDRC_BASIC_QUERY_DATA_GET
    36 FUNCTION     SAPLRSDRC                           LRSDRCU15                             189
    RSDRC_BASIC_CUBE_DATA_GET
    35 FORM         SAPLRSDRC                           LRSDRCF25                             373
    DATA_GET
    34 FUNCTION     SAPLRSDRC                           LRSDRCU02                             249
    RSDRC_CUBE_DATA_GET
    33 FUNCTION     SAPLRSDRI                           LRSDRIU01                             352
    RSDRI_INFOPROV_READ
    32 FORM         /1SEM/UPCBW_350TMWPA01              UPC_BWINTERFC__FIX                    174
    DATA_READ
    31 FUNCTION     SAPLUPCBW                           LUPCBWU06                              56
    UPC_BW_DATA_READ
    30 FUNCTION     SAPLUPC1                            LUPC1U06                               67
    UPC_DATA_READ
    29 METHOD       /1SEM/CL_DATA_350TMWPA01======CP    UPC_DATA_READ_DB                       25
    /1SEM/CL_DATA_350TMWPA01=>IF_SEM_DATA_INTERNAL~READ_DB
    28 METHOD       /1SEM/CL_BUFFER_350TMWPA01====CP    UPC_BUFFER_GET                        167
    /1SEM/CL_BUFFER_350TMWPA01=>IF_SEM_BUFFER~GET
    27 METHOD       /1SEM/CL_BUFFER_350TMWPA01====CP    UPC_BUFFER_READ                         5
    /1SEM/CL_BUFFER_350TMWPA01=>IF_SEM_BUFFER~READ
    26 METHOD       /1SEM/CL_DATA_350TMWPA01======CP    UPC_DATA_READ                          46
    /1SEM/CL_DATA_350TMWPA01=>IF_SEM_DATA~READ
    25 FORM         45AJEHYBGH37F61DTX80Q9ZFP           UPP_PLAN                              395
    READ_TRANSACTION_DATA
    24 FORM         45AJEHYBGH37F61DTX80Q9ZFP           UPP_PLAN                              561
    GET_DATA
    23 FORM         45AJEHYBGH37F61DTX80Q9ZFP           UPP_PLAN                              800
    EC500_SELECT_DATABASE
    22 FORM         SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELF97                     575
    SELECT_DATABASE
    21 FORM         SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELF97                     464
    SELECT_AND_FIND_HEADER_COMBI
    20 FORM         SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELF97                     217
    LOGICAL_SCREEN_FILL_HEADER
    19 FORM         SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELF97                      60
    LOGICAL_SCREEN_FILL
    18 FUNCTION     SAPLUPP_PP_KERNEL                   LUPP_PP_KERNELU01                     114
    UPP_PP_KERNEL_CONSTRUCTOR
    17 METHOD       CL_UPB_PL_ALV=================CP    CL_UPB_PL_ALV=================CM01E   176
    CL_UPB_PL_ALV=>CONSTRUCTOR
    16 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF01                        623
    OUTPUT_CREATE
    15 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF01                        202
    OUTPUT_INIT
    14 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF01                       1062
    OUTPUT_PROCESS
    13 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF01                       1225
    OUTPUT_SWITCH_TO_LAYOUT
    12 FORM         SAPLUPB_PM_ALV                      LUPB_PM_ALVF05                        748
    INIT_CONTROLS
    11 MODULE (PBO) SAPLUPB_PM_ALV                      LUPB_PM_ALVO01                         13
    STATUS
    10 FUNCTION     SAPLUPB_PM_ALV                      LUPB_PM_ALVU01                         24
    UPB_PM_ALV_START
    9 METHOD       CL_UPB_PM_APPLC===============CP    CL_UPB_PM_APPLC===============CM00A    88
    CL_UPB_PM_APPLC=>EXECUTE_PM
    8 METHOD       CL_UPB_PM_ADMIN===============CP    CL_UPB_PM_ADMIN===============CM00L    76
    CL_UPB_PM_ADMIN=>PAI_ONE_NODE
    7 METHOD       CL_UPB_PM_ADMIN===============CP    CL_UPB_PM_ADMIN===============CM00L    23
    CL_UPB_PM_ADMIN=>PAI_ONE_NODE
    6 METHOD       CL_UPB_PM_ADMIN===============CP    CL_UPB_PM_ADMIN===============CM003   121
    CL_UPB_PM_ADMIN=>PAI
    5 FORM         SAPLUPB_PM                          LUPB_PMF04                             80
    USER_COMMAND_0210
    4 MODULE (PAI) SAPLUPB_PM                          LUPB_PMI04                             11
    USER_COMMAND_0210
    3 FUNCTION     SAPLUPB_PM                          LUPB_PMU22                             86
    UPB_PM_MAIN
    2 FORM         UPB_PM_CUST_START                   UPB_PM_START_ADMIN                    251
    PM_START
    1 EVENT        UPB_PM_CUST_START                   UPB_PM_START_ADMIN                     14
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.      40 Ty.          FUNCTION
    Name  RSSB_AUTHORITY_IOBJVL_CHECK
    I_ACTIVITY
    03
    33
    03
    I_ACTIVITY_FORCE_CHECK
    2
    0
    I_MESSAGE
    X
    5
    8
    I_SX_IOBJVL_CHECK
    ZCTMWMA05                                                                                ####
    5454544332222222222222222222222222222222222222222222222222222222222222222222222222222222220000
    A34D7D1050000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    I_UNAME
    S51643
    533333222222
    351643000000
    E_SUBRC
    0
    0000
    0000
    E_TS_AUTH_TLEVEL
    Table[initial]
    E_TX_NO_AUTH
    Table[initial]
    RSSB_C_AUTH_KEYFIGURE
    1KYFNM
    3454442222
    1B96ED0000
    SY-REPID
    SAPLRSSBR
    5454555452222222222222222222222222222222
    310C233220000000000000000000000000000000
    SYST-REPID
    SAPLRSSBR
    5454555452222222222222222222222222222222
    310C233220000000000000000000000000000000
    %_SPACE
    2
    0
    RS_C_RANGE_SIGN
    IE
    44
    95
    SY-SUBRC
    5
    0000
    0005
    L_TX_NO_AUTH
    Table[initial]
    SY-XFORM
    CONVERSION_EXIT
    444545544454545222222222222222
    3FE65239FEF5894000000000000000
    SYST
    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. ###################################################à##############
    0000000000000000000000000002000000000000000000000000000000000000000000000000000E00000000000000
    0001000000000000000000000000000000000000000000010001000000010000000000000000000000000000000000
    L_SX_NO_AUTH
    ############ÿÿÿÿ
    000000000000FFFF
    000000000000FFFF
    L_SX_NO_AUTH-KID
    Table[initial]
    <L_SX_AUTH_CHECK>-KID
    Table IT_33029[1x4]
    FUNCTION-POOL=RSSBRDATA=G_SX_IOBJVL_CHECK-AUTH_CHECK[1]-KID
    Table reference: 2052
    TABH+  0(20) = 07000000908D2FD0000000000000000000000000
    TABH+ 20(20) = 00000804000081050000000100000004FFFFFFFF
    TABH+ 40(16) = 040002F1000003480001432821000000
    store        = 0x07000000908D2FD0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 2052  (0x00000804)
    label        = 33029 (0x00008105)
    fill         = 1     (0x00000001)
    leng         = 4     (0x00000004)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000003
    occu         = 1     (0x00000001)
    access       = 2     (ItAccessSorted)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 1     (ItUnique)
    keyKind      = 2     (table_line)
    cmpMode      = 5     (cmpSingle)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000908E0CC8
    pghook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    refCount     = 1     (0x00000001)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 1     (0x00000001)
    lineAlloc    = 1     (0x00000001)
    store_id     = 6998  (0x00001B56)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    No.      39 Ty.          FORM
    Name  AUTHORITY_CHECK
    I_TH_SFC
    Table IT_32090[14x128]
    FUNCTION=RSDRC_BASIC_CUBE_DATA_GETDATA=L_TH_SFC
    Table reference: 1757
    TABH+  0(20) = 070000009052D8F8070000009081372800000000
    TABH+ 20(20) = 000006DD00007D5A0000000E00000080FFFFFFFF
    TABH+ 40(16) = 040002DB000017C80010839401000000
    store        = 0x070000009052D8F8
    ext1         = 0x0700000090813728
    shmId        = 0     (0x00000000)
    id           = 1757  (0x000006DD)
    label        = 32090 (0x00007D5A)
    fill         = 14    (0x0000000E)
    leng         = 128   (0x00000080)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000099
    occu         = 16    (0x00000010)
    access       = 4     (ItAccessHashed)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 1     (ItUnique)
    keyKind      = 3     (user defined)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000090811F18
    pghook       = 0x0000000000000000
    idxPtr       = 0x070000009052D950
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 6872  (0x00001AD8)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0700000090813588
    hsdir        = 0x0000000000000000
    ext2         = 0x0000000000000000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    CL_RSO_REPOSITORY=>P_C_BAL_LOG_SUBOBJEC_INST
    SY-REPID
    SAPLRSDRC
    5454554542222222222222222222222222222222
    310C234230000000000000000000000000000000
    L_S_RANGE-LOW
    1ROWCOUNT
    354544545222222222222222222222222222222222222222222222222222
    12F73F5E4000000000000000000000000000000000000000000000000000
    <L_S_SFK>-KYFNM
    1ROWCOUNT
    354544545222222222222222222222
    12F73F5E4000000000000000000000
    RSDRC_C_QUERYMODE-CUMULATIVE
    C
    4
    3
    S_S_COB_PRO
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_SX_SELDR-RANGE+8(8)
    Table IT_32110[2x136]
    FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_SX_SELDR
    Table reference: 1902
    TABH+  0(20) = 0700000090813D10000000000000000000000000
    TABH+ 20(20) = 0000076E00007D6E0000000200000088FFFFFFFF
    TABH+ 40(16) = 040002DB00001AA00010254421000000
    store        = 0x0700000090813D10
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 1902  (0x0000076E)
    label        = 32110 (0x00007D6E)
    fill         = 2     (0x00000002)
    leng         = 136   (0x00000088)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000112
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 2     (table_line)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000908800F8
    pghook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    refCount     = 1     (0x00000001)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 6876  (0x00001ADC)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    L_S_RANGE
    IEQ1ROWCOUNT
    4453545445452222222222222222222222222222222222222222222222222222222222222222222222222222222222
    95112F73F5E40000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_TSX_SELDR
    Table IT_32094[13x120]
    FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_TSX_SELDR
    Table reference: 1870
    TABH+  0(20) = 0700000090813AE007000000908DF36800000000
    TABH+ 20(20) = 0000074E00007D5E0000000D00000078FFFFFFFF
    TABH+ 40(16) = 040002DB000018A8000C4B9C01000000
    store        = 0x0700000090813AE0
    ext1         = 0x07000000908DF368
    shmId        = 0     (0x00000000)
    id           = 1870  (0x0000074E)
    label        = 32094 (0x00007D5E)
    fill         = 13    (0x0000000D)
    leng         = 120   (0x00000078)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000103
    occu         = 12    (0x0000000C)
    access       = 2     (ItAccessSorted)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 1     (ItUnique)
    keyKind      = 3     (user defined)
    cmpMode      = 3     (cmpSingleMcmpU)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x070000009087FB40
    pghook       = 0x0700000090813D68
    idxPtr       = 0x0700000090813DA0
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 36    (0x00000024)
    lineAlloc    = 36    (0x00000024)
    store_id     = 6875  (0x00001ADB)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x07000000908DED00
    hsdir        = 0x0000000000000000
    ext2         = 0x0000000000000000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    L_SX_SELDR
    00001KYFNM                          ########300   0     ####ÿÿÿÿ####  0 ########        ####ÿÿ
    333334544422222222222222222222222222000000003332223222220000FFFF0000223200000000222222220000FF
    00001B96ED00000000000000000000000000000000003000000000000000FFFF0000000000000000000000000000FF
    G_RUNNING
    0
    0000
    0000
    L_BASICCUBE
    ZCTMWMA05
    545454433222222222222222222222
    A34D7D105000000000000000000000
    L_TH_FREE
    Table IT_32093[6x30]
    FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_TH_FREE
    Table reference: 1763
    TABH+  0(20) = 0700000090813760000000000000000000000000
    TABH+ 20(20) = 000006E300007D5D000000060000001EFFFFFFFF
    TABH+ 40(16) = 040002DB00001B800010831401000000
    store        = 0x0700000090813760
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 1763  (0x000006E3)
    label        = 32093 (0x00007D5D)
    fill         = 6     (0x00000006)
    leng         = 30    (0x0000001E)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000116
    occu         = 16    (0x00000010)
    access       = 4     (ItAccessHashed)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 1     (ItUnique)
    keyKind      = 2     (table_line)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x07000000908137B8
    pghook       = 0x0000000000000000
    idxPtr       = 0x07000000908139B0
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 6874  (0x00001ADA)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    SYST-REPID
    SAPLRSDRC
    5454554542222222222222222222222222222222
    310C234230000000000000000000000000000000
    L_SX_IOBJVL_CHECK
    ZCTMWMA05                                                                                ####
    5454544332222222222222222222222222222222222222222222222222222222222222222222222222222222220000
    A34D7D1050000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    L_ACTIVITY
    03
    33
    03
    SY-UNAME
    S51643
    533333222222
    351643000000
    S_MULTICUBE
    222222222222222222222222222222
    000000000000000000000000000000
    E_SUBRC
    0
    0000
    0000
    %_VIASELSCR
    0
    4
    S_CHANM
    222222222222222222222222222222
    000000000000000000000000000000
    I_RAISE_EXCEPTION
    X
    5
    8
    RS_C_TRUE
    X
    5
    8
    SCREEN
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.      38 Ty.          FORM
    Name  BASIC_QUERY_DATA_GET_ROLAP
    E_T_DATA
    Table[initial]
    E_END_OF_DATA
    2
    0
    C_FIRST_CALL
    X
    5
    8
    S_S_QPARAM
    XX 0 ##ÿÿÿÿ####DB-VIEW                                               R ###dABAP-TABLE
    25523200FFFF0000442544522222222222222222222222222222222222222222222222520006444525444422222222
    08800000FFFF000042D6957000000000000000000000000000000000000000000000002000041210D412C500000000
    C_S_QPARAM-AUTHORITY_CHECK
    R
    5
    2
    RSDRC_C_AUTHCHK-NONE
    2
    0
    RSJOBINFO
    00000000000000                                  ####
    222222222222222222222222222222223333333333333322222222222222222222222222222222220000
    000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RSD_C_DPANM
    0REQUID                       0CHNGID                       0RECORDTP                     0IOB
    3545544222222222222222222222223444444222222222222222222222223544454552222222222222222222223444
    025159400000000000000000000000038E794000000000000000000000000253F244000000000000000000000009F2
    SPACE
    2
    0
    I_BASICCUBE
    ZCTMWMA05
    545454433222222222222222222222
    A34D7D105000000000000000000000
    I_TH_SFC
    Table IT_32090[14x128]
    I_TH_SFK
    Table IT_32091[2x128]
    FUNCTION=RSDRC_BASIC_CUBE_DATA_GETDATA=L_TH_SFK
    Table reference: 1767
    TABH+  0(20) = 0700000090887AC00700000090813CD800000000
    TABH+ 20(20) = 000006E700007D5B0000000200000080FFFFFFFF
    TABH+ 40(16) = 040002DB000018380010839421000000
    store        = 0x0700000090887AC0
    ext1         = 0x0700000090813CD8
    shmId        = 0     (0x00000000)
    id           = 1767  (0x000006E7)
    label        = 32091 (0x00007D5B)
    fill         = 2     (0x00000002)
    leng         = 128   (0x00000080)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000101
    occu         = 16    (0x00000010)
    access       = 4     (ItAccessHashed)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 1     (ItUnique)
    keyKind      = 3     (user defined)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x0700000090884C90
    pghook       = 0x0000000000000000
    idxPtr       = 0x0700000090827A98
    refCount     = 1     (0x00000001)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    store_id     = 6857  (0x00001AC9)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0700000090813B38
    hsdir        = 0x0000000000000000

    Have you check or trace Authorization??
    In DUMP:
    Information on where terminated
    The termination occurred in the ABAP program "SAPLRSSBR" in
    "RSSB_AUTHORITY_IOBJVL_CHECK".
    The main program was "UPB_PM_CUST_START ".

  • ABAP RUNTIME ERROR WHILE DOING MIRO

    Runtime Errors                                                       MESSAGE_TYPE_X                              
    Date and Time                                                       23.02.2011                    17:07:24          
    Short dump has not been completely stored (too big)                                                                                     
         Short text                                                                                
                   The current application triggered a termination with a short dump.                                                                      
         What happened?                                                                                
                   The current application program detected a situation which really                                                                      
                   should not occur. Therefore, a termination with a short dump was                                                                      
                   triggered on purpose by the key word MESSAGE (type X).                                                                      
         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                                                                                
                   Short text of error message:                                                                      
                   Error creating the document in Profitability Analysis                                                                      
                   Long text of error message:                                                                      
                    Diagnosis                                                                      
                        An error was found while the system was processing the FI/CO                                                                      
                        document in Profitability Analysis.                                                                      
                    System Response                                                                      
                        The document cannot be processed any further.                                                                      
                    Procedure                                                                      
                        Contact your system administrator.                                                                      
                   Technical information about the message:                                                                      
                   Message class....... "KE"                                                                      
                   Number.............. 476                                                                      
                   Variable 1.......... " "                                                                      
                   Variable 2.......... " "                                                                      
                   Variable 3.......... " "                                                                      
                   Variable 4.......... " "                                                                      
         How to correct the error                                                                                
                   Probably the only way to eliminate the error is to correct the program.                                                                      
                   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:                                                                      
                   MESSAGE_TYPE_X " "                                                                      
                   RK2RF001 or "RKEVRK2R_FIX"                                                                      
                   MOVE_VALUE_FIELDS_FI                                                                      
                   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 701                                                                      
                   Application server... "FPELECCPRD"                                                                      
                   Network address...... "192.168.0.24"                                                                      
                   Operating system..... "Windows NT"                                                                      
                   Release.............. "6.0"                                                                      
                   Hardware type........ "16x AMD64 Level"                                                                      
                   Character length.... 16 Bits                                                                      
                   Pointer length....... 64 Bits                                                                      
                   Work process number.. 1                                                                      
                   Shortdump setting.... "full"                                                                      
                   Database server... "FPELECCPRD\FTP"                                                                      
                   Database type..... "MSSQL"                                                                      
                   Database name..... "FTP"                                                                      
                   Database user ID.. "ftp"                                                                      
                   Terminal.......... "PUNE143"                                                                      
                   Char.set.... "C"                                                                      
                   SAP kernel....... 701                                                                      
                   created (date)... "Feb 24 2009 23:27:20"                                                                      
                   create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"                                                                      
                   Database version. "SQL_Server_8.00 "                                                                      
                   Patch level. 32                                                                      
                   Patch text.. " "                                                                      
                   Database............. "MSSQL 9.00.2047 or higher"                                                                      
                   SAP database version. 701                                                                      
                   Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows                                                                      
                    NT 6.0"                                                                      
                   Memory consumption                                                                      
                   Roll.... 16192                                                                      
                   EM...... 29328880                                                                      
                   Heap.... 0                                                                      
                   Page.... 221184                                                                      
                   MM Used. 20281392                                                                      
                   MM Free. 664288                                                                      
         User and Transaction                                                                                
                   Client.............. 900                                                                      
                   User................ "FABUPLO"                                                                      
                   Language key........ "E"                                                                      
                   Transaction......... "MIRO "                                                                      
                   Transactions ID..... "1C413FE0E2E7F1C88D54E61F1346F073"                                                                      
                   Program............. "RK2RF001"                                                                      
                   Screen.............. "SAPLMR1M 6000"                                                                      
                   Screen line......... 34                                                                      
         Information on where terminated                                                                                
                   Termination occurred in the ABAP program "RK2RF001" - in                                                                      
                    "MOVE_VALUE_FIELDS_FI".                                                                      
                   The main program was "SAPLMR1M ".                                                                      
                   In the source code you have the termination point in line 2749                                                                      
                   of the (Include) program "RKEVRK2R_FIX".

    Hi
    Normally what we understand is we should not have a COPA doc in case of MIRO unless and untill one has got the Purchase Price Variance in the entry  and for the same the OKB9 setting has been made while the GL account either doesnot have cost element for the period or the PA structure is not complete.
    The above can be the probable reason for the dump. I hope if you try to investigate the problem on the above line you will find out the solution to the problem
    regards
    Debashis

  • ABAP runtime error while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N

    Dear All Expert,
    I am facing problem while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N,
    Please find the below ABAP Runtime Error.
    Runtime Errors         LOAD_TYPE_VERSION_MISMATCH
    Date and Time          10.02.2011 11:13:07
    Short text
         Change of a Dictionary structure at runtime of a program.
    What happened?
         Runtime error
         The current ABAP program "CL_IM_WRF_MM_PROC_PO==========CP" had to be
          terminated because one
         of the statements could not be executed at runtime.
    What can you do?
         Restart the program.
         If the error persists, contact your SAP administrator.
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    Error analysis
         The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY"
          changed
         during the flow of the transaction.
         As the type was already used in the old version
         and in the new type should be used in the same transaction in the new
          version, the transaction had to be cancelled to avoid inconsistencies.
    How to correct the error
        Try to restart the program.
    System environment
        SAP-Release 700
        Application server... "iqe"
        Network address...... "172.25.0.85"
        Operating system..... "Linux"
        Release.............. "2.6.9-55.ELsmp"
        Hardware type........ "x86_64"
        Character length.... 16 Bits
        Pointer length....... 64 Bits
        Work process number.. 0
        Shortdump setting.... "full"
        Database server... "iqe"
        Database type..... "ORACLE"
        Database name..... "IQE"
        Database user ID.. "SAPSR3"
        Terminal................. "MUMJML5727"
        Char.set.... "C"
        SAP kernel....... 700
        created (date)... "Dec 26 2010 20:17:07"
        create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
        Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 285
    Patch text.. " "
    Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
    SAP database version. 700
    Operating system..... "Linux 2.6"
    Memory consumption
    Roll.... 16192
    EM...... 25139088
    Heap.... 0
    Page.... 40960
    MM Used. 8038136
    MM Free. 4528408
    User and Transaction
    Client.............. 600
    User................ "JKMM"
    Language key........ "E"
    Transaction......... " "
    Transactions ID..... "4D524AD1FD7A42F9E1000000AC190055"
    Program............. "CL_IM_WRF_MM_PROC_PO==========CP"
    Screen.............. " "
    Screen line......... " "
    Information on where terminated
        The termination occurred during generation of the ABAP/4 program
         "CL_IM_WRF_MM_PROC_PO==========CP".
        The termination occurred in line 213
        of the source code of program "CL_IM_WRF_MM_PROC_PO==========CM007" (when
         calling the editor 2130).
    Source Code Extract
    Line  SourceCde
      183   DATA: l_flag TYPE wrf_pbas_boolean.
      184
      185   CALL FUNCTION 'WRF_POHF_MSG_READ_PREVIEW_FLAG'
      186     IMPORTING
      187       e_preview_flag = l_flag.
      188
      189   IF NOT l_flag IS INITIAL.
      190
      191     DATA: l_header TYPE REF TO cl_po_header_handle_mm.
      192
      193     MOVE im_header ?TO l_header.
      194
      195     CALL METHOD l_header->if_output_mm~preview( ).
      196
      197     CALL FUNCTION 'WRF_POHF_MSG_RESET_PREV_FLAG'.
      198
      199 ***$ Widening Cast for printing information.
      200 **    CALL FUNCTION 'WRF_POHF_STORE_PRINT_INFO_SET'
      201 **      EXPORTING
      202 **        im_header = l_header.
      203
      204 * Printing Preview
      205 * IF NOT gv_preview IS INITIAL.
      206 *    CALL METHOD l_header->if_output_mm~overview( ).
      207 *    CALL METHOD l_header->if_output_mm~preview( ).
      208 * clear gv_preview.
      209   ENDIF.
      210
      211 *  ENDIF.
      212
    >>>>> ENDMETHOD.
    Internal notes
        The termination was triggered in function "ab_RxDdicStruShareFailed"
        of the SAP kernel, in line 2539 of the module
         "//bas/700_REL/src/krn/runt/abtypload.c#11".
        The internal operation just processed is " ".
        Internal mode was started at 20110210111306.
        Name of the changed type......: "WRF_POHF_KOMP_STY"
        New version of the type.......: 20070508193207
        Old version of the type.......: 20070508193207
        New user......................: "Type" "WRF_POHF_KOMP_STY"
        Version of the new user.......: 20070508193207
        Old user......................: "???" "???"
        Version of the old user.......: "???"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (CTrcStack2+0x78)[0x6cbb78]
    (CTrcStack+0xb)[0x6cc17b]
    (ab_rabax+0x3be5)[0xb8d985]
    (_Z24ab_RxDdicStruShareFailedPKtm4RUDIS0_S1_S0_+0x163)[0xb16823]
    (_Z19ab_GetDdicTypeIndexPKtm4RUDI+0x1f6)[0xb0dbb6]
    (_Z11ab_LoadViewPtjPKtPK11PROGRAMHEADPj+0x27e)[0xb16ede]
    (_Z18ab_GetDdicTypeLoad4RUDI+0x6e)[0xb1705e]
    (ab_GetView+0xc1d)[0xb0ee1d]
    (_Z20CompressInitRcByDatajPK6CG_DIRjjS1_jj4RUDIPKhj+0x60d)[0xe32b2d]
    (_Z21cg_CompressStackFrameP4TRIGjj+0x169)[0xe33399]
    (_Z8cg_blkleP3ENV+0x75f)[0xe4779f]
    (_Z9sc_cblklePKt8ENV_KINDP7SC_INFO+0x394)[0xe90024]
    (sc_blkle+0xdd)[0xec6e4d]
    (rs_oper_abap1729+0x37)[0x10eb237]
    (rs_expan_abap+0xa1996)[0xfd7a2a]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_inclu+0x5fa)[0xe0d50a]
    (rs_oper_abap2160+0x3a)[0x1115d6a]
    (rs_expan_abap+0xcd41d)[0x10034b1]
    (_Z8sc_expanj+0x76d)[0xe1d55d]
    (_Z5parsejPi+0x258)[0xe19998]
    (sc_check+0xb9c)[0xe1857c]
    (sc_checkStart+0x41)[0xe1ac51]
    (cg_generate+0xb65)[0xe57755]
    (ab_gabap+0x14a)[0xb01a5a]
    (dy_gen_abap+0x63c)[0x74428c]
    (ab_genprog+0x13d3)[0xb03d13]
    (_Z17ab_LoadProgOrTrfoPKtjPj+0xb56)[0x8f9ab6]
    (_Z11ab_LoadProgPKtj+0x11)[0x8f9ca1]
    (_Z15LoadGlobalClassPKtjjj9ClasState+0x24c)[0x958c2c]
    (_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x214)[0x957404]
    (_Z11ab_FillCfixtj+0x65)[0x957ae5]
    (_Z26ab_CrefToCladId_ActivateOKtPh+0x7d)[0x957b6d]
    (_Z8ab_jaboov+0x623)[0x959793]
    (_Z8ab_extriv+0x607)[0x8ba9c7]
    (_Z9ab_xeventPKt+0x1c1)[0xa1c021]
    (_Z8ab_triggv+0x9c)[0xa1c77c]
    (ab_run+0x97)[0xbde5c7]
    (N_ab_run+0x9)[0x736359]
    (dynpmcal+0x669)[0x7333b9]
    (dynppai0+0x8eb)[0x734d9b]
    (dynprctl+0x3e9)[0x733db9]
    (dynpen00+0x4a5)[0x726eb5]
    (Thdynpen00+0x359)[0x541bd9]
    (TskhLoop+0xc49)[0x54d999]
    (ThStart+0x20f)[0x55b29f]
    (DpMain+0x2da)[0x4bd49a]
    (nlsui_main+0x9)[0x4910c9]
    (main+0x33)[0x491103]
    /lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x3cde51c3fb]
    Please help me to resolve the issue.
    Thanks & Regards
    SKK

    read this part again:  The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY" changed during the flow of the transaction. As the type was already used in the old version and in the new type should be used in the same transaction in the new version, the transaction had to be cancelled to avoid inconsistencies. How to correct the error Try to restart the program
    how often had you restarted ME21N before you posted this message?
    In best case this message appears only once, because the program / or dictionary was changed while you executed ME21N
    If many times, then contact your ABAPer, because then he probably did not transport all objects that were changed, or the objects have to be regenerated in your system.

  • ABAP runtime errors    COMPUTE_BCD_OVERFLOW

    ABAP runtime errors    COMPUTE_BCD_OVERFLOW
           Occurred on     12/08/2010 at 06:44:17
    >> Short dump has not been completely stored. It is too big.
    Error analysis
    An overflow has been determined in the current arithmetical operation
    containing operands of type P. Possible causes include:
    1.  The results field of type P is to small and the result does not fit
        into it.
        places.
    2.  The result or partial result has more than 31 decimal places.
    How to correct the error
    You may need to define the result field to be larger, if it is still
    possible to do so.
    It may be possible to split the current process so that only smaller
    values occur.
    Eine Vorablösung zu dem aufgetretenen Fehler findet sich vielleicht
    If the error occurred in one of your own programs or in an SAP program
    that you modified, try to correct it yourself.
    If you require an interim solution to this error, you can look in the
    SAP note system. If you have access to
    the SAP notes system yourself, enter the following search strings:
    "COMPUTE_BCD_OVERFLOW"
    "BCD_FIELD_OVERFLOW" (By release 4.0a, this error has been remedied at this
    point)

    Hi Ganapati,
    Check this thread COMPUTE_BCD_OVERFLOW in Database Performance collector.
    Note 543749 - ABAP runtime error COMPUTE_BCD_OVERFLOW
    It may helps you.

  • ABAP Runtime Error : STRING_LENGTH_TOO_LARGE In Solution Manager 7.0

    Hi All,
    In SolMan 7.0 when i am using T-code Solution_Manager->Business process Monitoring tab System is give as give below ABAP DUMP . Please Share your idea to resolve this issue.
    Runtime Errors                                                       STRING_LENGTH_TOO_LARGE
    Except.                                                       CX_SY_RANGE_OUT_OF_BOUNDS
    Date and Time                                                       24.11.2009                    12:16:08
         Short text
                   Illegal access to a string (length too large)
         What happened?
                   Error in the ABAP Application Program
                   The current ABAP program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP" had to be
                    terminated because it has
                   come across a statement that unfortunately cannot be executed.
         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 that is explained in detail below.
                   The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
                    caught in
                   procedure "IF_HTTP_EXTENSION~HANDLE_REQUEST" "(METHOD)", nor was it propagated
                    by a RAISING clause.
                   Since the caller of the procedure could not have anticipated that the
                   exception would occur, the current program is terminated.
                   The reason for the exception is:
                   In the running program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP", part of a string was
                    about to be accessed
                   with an explicitly specified length.
                   However, this length (8) exceeded the current length of the string
                   (5).
                   This kind of access is illegal.
         How to correct the error
                   Reduce the length with which to access the string.
                   If the error occurred in your own ABAP program or in an SAP
                   program you modified, try to remove 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:
                   "STRING_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"
                   "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP" or "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004"
                   "IF_HTTP_EXTENSION~HANDLE_REQUEST"
                   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.
                   The exception must either be prevented, caught within proedure
                   "IF_HTTP_EXTENSION~HANDLE_REQUEST" "(METHOD)", or its possible occurrence must
                    be declared in the
                   RAISING clause of the procedure.
                   To prevent the exception, note the following:
         System environment
                   SAP-Release 701
                   Application server... ".........."
                   Network address...... ""
                   Operating system..... "Windows NT"
                   Release.............. "5.2"
                   Hardware type........ "8x AMD64 Level"
                   Character length.... 16 Bits
                   Pointer length....... 64 Bits
                   Work process number.. 0
                   Shortdump setting.... "full"
                   Database server... "................."
                   Database type..... "ORACLE"
                   Database name..... "SM7"
                   Database user ID.. "SAPSR3"
                   Terminal.......... ".............."
                   Char.set.... "C"
                   SAP kernel....... 701
                   created (date)... "Oct 12 2008 23:34:32"
                   create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
                   Database version. "OCI_10201_SHARE (10.2.0.2.0) "
                   Patch level. 15
                   Patch text.. " "
                   Database............. "ORACLE 9.2.0.*.*, ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*"
                   SAP database version. 701
                   Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
                    NT 6.0"
                   Memory consumption
                   Roll.... 16192
                   EM...... 4189840
                   Heap.... 0
                   Page.... 0
                   MM Used. 1513920
                   MM Free. 2673296
         User and Transaction
                   Client.............. 100
                   User................ 182836
                   Language Key........ "E"
                   Transaction......... " "
                   Transactions ID..... "09C5D8DE506DF14DB42D001E682F27BB"
                   Program............. "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP"
                   Screen.............. "SAPMHTTP 0010"
                   Screen Line......... 2
                   Information on Caller ofr "HTTP" Connection:
                   Plug-in Type.......... "HTTP"
                   Caller IP............. "10.226.33.101"
                   Caller Port........... 8080
                   Universal Resource Id. "/sap/bc/solman/defaultUser/graphic/solmangraphic.htm"
         Information on where terminated
                   Termination occurred in the ABAP program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP" -
                    in "IF_HTTP_EXTENSION~HANDLE_REQUEST".
                   The main program was "SAPMHTTP ".
                   In the source code you have the termination point in line 130
                   of the (Include) program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004".
                   The termination is caused because exception "CX_SY_RANGE_OUT_OF_BOUNDS"
                    occurred in
                   procedure "IF_HTTP_EXTENSION~HANDLE_REQUEST" "(METHOD)", but it was neither
                    handled locally nor declared
                   in the RAISING clause of its signature.
                   The procedure is in program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP "; its source
                    code begins in line
                   6 of the (Include program "CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004 ".
         Source Code Extract
         Line               SourceCde
           100               *     url of its for WebGUI links (extension for portal cfs)
           101                     WHEN 'its'.
           102                       lv_its = ls_param_fields-value.
           103               *     name of transaction for WebGUI links (extension for portal cfs)
           104                     WHEN 'trans'.
           105                       lv_trans = ls_param_fields-value.
           106               *     name of transaction parameter for WebGUI links
           107               *     (extension for portal cfs)
           108                     WHEN 'trans_keyname'.
           109                       lv_trans_keyname = ls_param_fields-value.
           110               *     info block
           111                     WHEN gc_parameter_name-io.
           112                       lv_io = ls_param_fields-value.
           113               *     portal base url
           114                     WHEN gc_parameter_name-base_url.
           115                       lv_base_url = ls_param_fields-value.
           116
           117               * Note 834787-- Headers of Infoblocks are not translated in Fact sheet
           118               * display set the language
           119                     WHEN 'sap-language'.
           120                       try.
           121                           set locale language ls_param_fields-value.
           122                         catch CX_SY_LOCALIZATION_ERROR.
           123               * No language with this code is installed.
           124               * use the default one
           125                           SET LOCALE LANGUAGE SPACE.
           126                       endtry.
           127
           128                     WHEN OTHERS.
           129               *       additional types for selection
         >>>>>                       IF ls_param_fields-name(8) EQ 'sel-type'.
           131                         CLEAR ls_sel_param.
           132                         MOVE ls_param_fields-value TO ls_sel_param-name.
           133                         lv_num = ls_param_fields-name+8(*).
           134                         CLEAR lv_key.
           135                         CONCATENATE 'sel-value'
           136                                     lv_num
           137                                INTO lv_key.
           138                         READ TABLE lt_param_fields WITH KEY name = lv_key
           139                              INTO ls_param_fields.
           140                         IF sy-subrc = 0.
           141                           MOVE ls_param_fields-value TO ls_sel_param-value.
           142                         ENDIF.
           143                         APPEND ls_sel_param TO lt_sel_param.
           144                       ENDIF.
           145                   ENDCASE.
           146                 ENDLOOP.
           147
           148               * HTML error message if no business partner
           149                 IF bp IS INITIAL.
         Contents of system fields
         Name                         Val.
         SY-SUBRC                         0
         SY-INDEX                         1
         SY-TABIX                         3
         SY-DBCNT                         1
         SY-FDPOS                         17
         SY-LSIND                         0
         SY-PAGNO                         0
         SY-LINNO                         1
         SY-COLNO                         1
         SY-PFKEY
         SY-UCOMM
         SY-TITLE                         HTTP Control
         SY-MSGTY
         SY-MSGID
         SY-MSGNO                         000
         SY-MSGV1
         SY-MSGV2
         SY-MSGV3
         SY-MSGV4
         SY-MODNO                         0
         SY-DATUM                         20091124
         SY-UZEIT                         121608
         SY-XPROG
         SY-XFORM
         Active Calls/Events
         No.               Ty.                              Program                                                            Include                                   Line
                        Name
             4               METHOD                              CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP                                                            CL_CRM_CCKPT_CFS_SERVICE_HTTP=CM004                                     130
                        CL_CRM_CCKPT_CFS_SERVICE_HTTP=>IF_HTTP_EXTENSION~HANDLE_REQUEST
             3               METHOD                              CL_HTTP_SERVER================CP                                                            CL_HTTP_SERVER================CM00G                                     574
                        CL_HTTP_SERVER=>EXECUTE_REQUEST
             2               FUNCTION                              SAPLHTTP_RUNTIME                                                            LHTTP_RUNTIMEU02                                     942
                        HTTP_DISPATCH_REQUEST
             1               MODULE (PBO)                              SAPMHTTP                                                            SAPMHTTP                                      13
                        %_HTTP_START
         Chosen variables
         Name
                   Val.
         No.                   4                    Ty.                         METHOD
         Name               CL_CRM_CCKPT_CFS_SERVICE_HTTP=>IF_HTTP_EXTENSION~HANDLE_REQUEST
         SERVER
                   {O:2*\CLASS=CL_HTTP_SERVER_NET}
                 F0000000
                 D0002000
         LS_PARAM_FIELDS-NAME
                   _appl
                 56776
                 F100C
                 00000
                 00000
         SY-REPID
                   CL_CRM_CCKPT_CFS_SERVICE_HTTP=CP
                 4454545444555445554554445455534522222222
                 3CF32DF33B04F363F3526935F8440D3000000000
                 0000000000000000000000000000000000000000
                 0000000000000000000000000000000000000000
         SPACE
                 2
                 0
                 0
                 0
         GC_PARAMETER_NAME-BASE_URL
                   ep_base_url
                 67566765776
                 50F2135F52C
                 00000000000
                 00000000000
    Regards
    Suresh
    Edited by: Suresh Kumar on Nov 24, 2009 3:21 PM

    Hi Naveen,
    Please find given below BBPCRM & SAP_BW version..
    BBPCRM     500     0013     SAPKU50013     BBPCRM     BBP/CRM Supp. Pack.
    SAP_BW     701     0003     SAPKW70103     SAP Business Warehouse     Component Supp. Pkg.
    This problem is not only with  Bussiness process tab (T-Code: Solution_manage) also System monitoring Still i searching solution for this But once we are restarting System that time this problem is not occuring but after some time system is giving this DUMP
    Regards,
    Suresh

  • ABAP RunTime Error  for tcode : TS01

    Hi Friends,
    Actually we are getting the run time error while creating the standard security transaction using TS01.
    After entering the data in the first screen -- click on the enter -- enter the details inside & click on save button--then it will go run time error.
    Here while calling the method, we are getting the run time error.
    call method cl_class_position_op_trs=>trs_flows_calculate_tax
          exporting
            im_tab_flow         = L_TAB_FLOWS
            im_company_code     = l_company_code
            im_security_account = l_security_account
            im_security_id      = l_security_id
          receiving
            re_tab_flow         = RE_TAB_FLOWS
          exceptions
            failed = 1
            others = 2.
      if sy-subrc <> 0.
         MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
                  RAISING FAILED.
      endif.
    Actuallly here the problem with the class becuase the class  cl_class_position_op_trs itself has error.
    In the class , in the local classes they are calling again the class cl_class_position_op_trs. becasue of this reason it was going to run time error.
    So we are getting the run time error.
    We have OSS note for the same problem.But i am unable to implement that.
    Please guide me how to implement the OSS note 751947.(Note 751947 - TRS: Syntax error due to ABAP Compiler)
    please find the error details:
    Runtime Errors         SYNTAX_ERROR
           Occurred on     03/12/2008 at 00:26:57
    Syntax error in program "CL_CLASS_POSITION_OP_TRS======CP ".
    What happened?
    The following syntax error occurred in the program
    CL_CLASS_POSITION_OP_TRS======CP :
    "Components of classes declared using "CLASS CL_CLASS_POSITION_OP_TRS D"
    Error in ABAP application program.
    The current ABAP program "CL_CLASS_POSITION_TRS=========CP" had to be
    terminated because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "CL_CLASS_POSITION_OP_TRS======CP
    You can also perform the syntax check from the ABAP/4 Editor.
    If the problem persists, proceed as follows:
    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.
    Error analysis
    The following syntax error was found in the program
    CL_CLASS_POSITION_OP_TRS======CP :
    "Components of classes declared using "CLASS CL_CLASS_POSITION_OP_TRS D"
    Regards.
    Lakshmi
    Edited by: lakshmi podile on Mar 14, 2008 8:08 AM

    Did you go through the steps in the note?
    Use transaction SE24 to distribute the local classes into new include structures as follows:
    Call transaction SE24 for the class CL_CLASS_POSITION_OP_TRS.
    Select the following menu option:
    Goto --> Class-local types --> Local Class Definitions/Types
    Confirm the message that proposes conversion into the new structures.
    Choose Utilities --> Regenerate sections from the menu.
    Activate the class and all changed objects.
    Try and do this, and see what happens.
    Good luck.

  • ABAP Runtime Error in [VL01N]

    HI All,
    Kindly suggest some line for the followings
    While doing PGI (Posting Goods Issue) in delivery at t.code [VL01N] there is an ABAP Runtime Error
    And some part of the analysis is
    Information on where terminated:
    Termination occurred in the ABAP program "SAPLMBWL" - in "MB_POST_GOODS_MOVEMENT".
    The main program was "SAPMV50A".
    In the source fode you have the termination point in line 59 of the (Include) program "LMBWLU21".
    Let me know
    Being a SD consultant what I can do
    And how I can proceed to complete the sd-cycle by working on ECC6.0
    Guide me soon please Gurus..........

    Termination occurred in the ABAP program "SAPLMBWL" - in "MB_POST_GOODS_MOVEMENT".
    The main program was "SAPMV50A".
    Go to SE80,choose Program and enter SAPMV50A ,check does it contain your Inlcude LMB* if not check other SAPLMBWL pgm ,n check..
    go to the include ,this might be a FM also.. so check properly and than put a break point.

  • ABAP runtime error in ME2N Transaction

    Hi All,
    I am getting an ABAP runtime error when i run transaction ME2N and then click on th Account Assignment Button.
    This is the error i get.
    Runtime Errors         GETWA_NOT_ASSIGNED
    Date and Time          06/01/2009 16:35:59
    Short text
    Field symbol has not yet been assigned.
    The section of the code which is creating problem is
    2326|*... ... find the row that holds the first requested cell                                   |
    2327
    loop at ct_stin assigning <ls_stin>
    2328
    where start_indx le i_start.
    2329
    l_start = sy-tabix.
    2330
    endloop.                       "Y6DK065306
    >>>>>
    if <ls_stin>-filled eq abap_false.
    2332
    lt_delete_row-low    = <ls_stin>-row_pos.
    2333
    lt_delete_row-sign   = 'I'.
    2334
    lt_delete_row-option = 'EQ'.
    2335
    insert lt_delete_row into table lt_delete_row.
    2336
    endif.
    | 2337|         
    the internal table ct_stin is not gettin any data in Runtime.
    Can anybody help me out in analysing this.
    Saurabh

    As I understand you have modify the standard SAP program. The problem is when the internal table
    ct_stin does not have data the field symbol <ls_stin> does not have any assign. to correct this 
    LOOPAT CT_STIN ASSIGNING <LS_STIN>
    WHERE START_INDX LE I_START.
      L_START = SY-TABIX.
    ENDLOOP.                                                    "Y6DK065306
    Check <LS_STIN> IS Assigned.
    IF <LS_STIN>-FILLED EQ ABAP_FALSE.
      LT_DELETE_ROW-LOW = <LS_STIN>-ROW_POS.
      LT_DELETE_ROW-SIGN = 'I'.
      LT_DELETE_ROW-OPTION = 'EQ'.
      INSERT LT_DELETE_ROW INTO TABLE LT_DELETE_ROW.
    ENDIF.

  • Analysing details of SQL trace and runtime analysis for a report.

    Hi,
    I am trying to tune the performance of a Z ABAP report for target group export. A brief overview of what is done in the report is the retrieval of BP details present in the Target group including BP general, address, marketing attributes, person responsible and contact person details. As the target groups can be quite huge (around 6000 BPs), the report gives performance issues. I want to understand on how to analyse the details which I obtained from the run time analysis and SQL trace and on how to take it forward.
    Any inputs in this regard would be helpful.
    Thanks in advance,
    Anushree

    In Runtime analysis Look for
    ABAP -  In your ABAP code
    DATABASE  -  It shows the performance of your SELECT statements in your program.
    Just check how much % it is showing for both.
    Check for following in your code.
    1) Avoid SELECT *
    2) Clear internal tables values which are not required at the ending of program, as it saves memory
    etc.

  • Reg : Daily i got 120 ABAP Runtime Error with in 40 Mins(Early Morning)

    Dear Friends,
    I got following errors regularly. when i run t.code RSBTCDEL and RSSNAPDL. what can i do? then Regularly morning i got same morethan 120 Error. User is SAPSYS 000 Client. How can avoid this type of ABAP Runtime Error.
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          10.06.2009 15:04:23
    Short text
         SQL error in the database when accessing a table.
    What can you do?
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrator
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    How to correct the error
         Database error text........: "[601] Could not continue scan with NOLOCK due to
          data movement."
         Internal call code.........: "[RSQL/FTCH/TBTCO ]"
         Please check the entries in the system log (Transaction SM21).
         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:
         "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
         "SAPLBTCH" or "LBTCHF19"
         "EXECUTE_BP_JOB_SELECT"
    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 u2192 List u2192 Save u2192 Local File u2192 (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. The exception must either be prevented, caught within proedure
    "EXECUTE_BP_JOB_SELECT" "(FORM)", or its possible occurrence must be declared
    in the RAISING clause of the procedure. To prevent the exception, note the following:
    Client.............. 400
    User................ "BASIS"
    Language key........ "E"
    Transaction......... "SE38 "
    Transactions ID..... "D7A155DEA42EF1EEB52A000423BF7C3A"
    Program............. "SAPLBTCH"      ( Run a Sap Standard Report RSBTCDEL)
    Screen.............. "SAPMSSY0 1000"
    Regards
    keshav

    Hi Juan,
    My System is
    ECC 6.0
    Database : MS SQL Server 2005
    OS - Windows 2003 server
    SAP Patches level is Basis - SAPKB70016
                                   ABAP - SAPKA70016
                                   Kernel patch level - 185
    when i has update the kernel patches after only i got this error morethan 120 like early morning 4.40 AM to 5.18 AM regularly. what can i do?
    Regards
    keshav

  • UNCAUGHT_EXCEPTION is the ABAP Runtime error

    Hi all,
    Our Production System BI7.0 with oracle 10g running on Unix . The UNCAUGHT_EXCEPTION is the ABAP Runtime error exists in ST22.
    Please find the Error analysis from ABAP Dump of UNCAUGHT_EXCEPTION.
    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
    Thanx,
    Peter

    Hi Peter,
    You shared pool might be too small
    Read,
    SAP Note 869006 - Composite SAP note: ORA-04031
    Regards
    Juan

Maybe you are looking for

  • How to change the default operators in sap web ui Search screen?

    How to change the default operators in sap web ui Search screen? For eg. Using advance search option , I have some fields with default operators like equals, contains,is between, is less than and is greater than. I don't need all these operators for

  • Pricing on item group

    Hi All, We require item prices to be mentioned on item group level rather than on the item level. is there some workaround without having to add user table. Thanks Rahul Jain

  • Weak signal on AX extending time capsule

    I just extended my network with an AX, using a new Time Capsule as the base station. Airport Utility sees the correct setup, Time capsule as the base creating the network and the AX as extending the same network. When I move to a range close to the A

  • Set time in Java

    How can I set the system time in Java?

  • ERROR IN OUTPUR  ALV GRID DISPLAY

    Dear all,          can any one please analyse this below code and tell me where i did mistake, i am getting output only from it_tab1, please any one solve this problem. Thanks, sujith. <Garbled code removed> Edited by: Suhas Saha on Aug 7, 2011 11:20