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

Similar Messages

  • 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

  • LSO_PSV2 - Create /w Resources freezing, ABAP runtime error, TIME_OUT

    Hello Experts,
    I have an individual user that is a part of a team that manages our LSO environment. He is experiencing a problem when performing a "Create with resources" on an instructor-led course.
    After choosing this option his session just spins but never enters the course details screen as expected.
    After anywhere from 15 - 30min the session returns an ABAP runtime error of "TIME_OUT". The error details state that the time out for ABAP programs is set to 3000sec (50min). The odd thing is that the program never reaches the 50 min marks but still throws the error.
    The user is able to select the "create w/o resources" option and get to the next screen as expected.
    I have run security traces (ST01) on his account and all looks fine (rc=0)
    He is one of several people that executes this transaction but is the only user that is receiving this issue. The team is assigned to the same position and shares the same PD profile. They share the same security roles and the same ABAP program is being run.These users are a third party vendor that remote in via citrix desktop.
    I have had our Basis team exam the ABAP runtime error and what is happening behind the scenes as this runs and they see no indication that the program is retrieving data even though it processes for a long time.
    Obviously this is a complex issue, I have searched for two weeks with no success. Any thoughts, suggestions are more than welcome at this point as the user is unable to perform needed work functions.

    Any solution on this one? I have the same problem with LSO_PSV2 :/

  • ABAP runtime errors    SNAP_NO_NEW_ENTR

    The following errors occured just after login, can anyone tell me how to handle it?
    ABAP runtime errors    SNAP_NO_NEW_ENTRY
           Occurred on     0000.00.00 at 13:47:44
    Runtime error: Unable to write short dump.
    What happened?
    The current ABAP/4 program " " had to be terminated because
    one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 program.
    Unfortunately, the original cause of the error cannot be determined
    because there is no suitable short dump in the table SNAP (which
    records information about the point of termination).
    termination).
    What can you do?
    Note the actions and input that caused the error.
    Inform your SAP system administrator.
    You can print out this message by choosing "Print". Transaction ST22
    allows you to display and manage termination messages, including keeping
    them beyond their normal deletion date.
    Error analysis
    Error analysis
    Unfortunately, the original cause of the error cannot be
    determined, since there is no suitable short dump in table SNAP.
    The table SNAP probably already contains a number of short dumps
    and cannot accept any more. Please check the situation using the
    system log.
    The table SNAP contains all the short dumps for the last 7 days.
    How to correct the error
    Check the system log for each cause of error.
    More space probably needs to be provided for table SNAP
    using database means.
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:

    hello,
    Check these:
    Note 495297 - DB6: Monitoring transaction log
    Re: Question. usage of transaction log
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f03d5fb8-b619-2b10-c383-c6d56872829e&overridelayout=true
    Ideally, db2diag.log should tell you this information.
    Hope it helps.
    thanks,
    Prasanna

  • ABAP runtime errors SNAP_NO_NEW_ENTRY

    The following errors occured just after login, can anyone tell me how to handle it?
    ABAP runtime errors SNAP_NO_NEW_ENTRY
    Occurred on 0000.00.00 at 13:47:44
    Runtime error: Unable to write short dump.
    What happened?
    The current ABAP/4 program " " had to be terminated because
    one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 program.
    Unfortunately, the original cause of the error cannot be determined
    because there is no suitable short dump in the table SNAP (which
    records information about the point of termination).
    termination).
    What can you do?
    Note the actions and input that caused the error.
    Inform your SAP system administrator.
    You can print out this message by choosing "Print". Transaction ST22
    allows you to display and manage termination messages, including keeping
    them beyond their normal deletion date.
    Error analysis
    Error analysis
    Unfortunately, the original cause of the error cannot be
    determined, since there is no suitable short dump in table SNAP.
    The table SNAP probably already contains a number of short dumps
    and cannot accept any more. Please check the situation using the
    system log.
    The table SNAP contains all the short dumps for the last 7 days.
    How to correct the error
    Check the system log for each cause of error.
    More space probably needs to be provided for table SNAP
    using database means.
    If the error occurred in a non-modified SAP program, you may be
    able to find a solution in the SAP note system.
    If you have access to the note system yourself, use the following
    search criteria:

    补充两句:
    1. SNAP表的Reorganization应该在后台通过定期的(每天)job执行,参看Note 16083。
    2. 如果登录系统即发生Dump,怀疑是否SNAP的table space是导致这个Dump的原因,考虑可能有其它致命错误。如果登录后还可以执行transaction,尝试执行SM21,DB02检查。

  • 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 CL_AI_CRM_OBJECT_LMDB============CP

    Dear All,
    We are setting up Solman 7.1 sp08 for VAR scenario.
    As we faced some issues with duplicated ibase components SAP suggested us to implement note 2012029.
    After following step by step and running the reporrts mentioned in above note like report AI_CRM_PRODUCT_DELETE we started getting an abap runtime error.
    SAP is telling us to re implement the note but it does not resolve our issue.
    Now we are unable to create incidents, or to run trx ib_gen.
    Because of this, job refresh_admin_data_from_support is getting cancelled.
    find attached screenshot showing dump.
    all suggestions or comments are welcome!
    regards,
    German

    Hi German,
    Looks like your report CL_AI_CRM_OBJECT_LMDB============CP is corrupted. Can you try restoring this program to original version by going to Version management in SE38?
    Regards,
    Vivek

  • 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 in FBV2 Change parked document using workflow

    Hi,
    When selecting screen template variant in tcode FBV2 change parked document, I get abap runtime error DYNPRO_NOT_FOUND
    Tcode- FBV2
    Program- SAPLF040
    Screen- SAPLF040  0310
    Main Program - SAPMF05V
    Information on were terminated.
    Program SAPLF040 - in " %_CTL_END "
    In the source code you have the termination point in line 50 of the (Include) program " <SYSINI> "
    How can we solve this error. We are on ECC6 with release 600.
    Thanks,
    Mark

    Hi Mark,
    We have this same issue in transaction F-65
    I believe that when a new screen template is configured, a new screen is generated within function group F040. A later action (applying a hotpack??) has removed this screen, but the config (in table T021D) still points the processing to the screen even though it has been removed.
    Did you find a solution? We want to get the screen back as it is still valid to use this screen template in the business
    Thanks
    Ben

  • ABAP Runtime Error at the time of saving of Document Through CV01N tcode

    Dear Experts
    We have install seprate DMS Server for storing various documents of different module.
    While saving of Document through Transaction CV01N one small screen gets pop up.Which is as follows
    Check in Document:KPro
    Storage Category   Description
    ZCITY123               DMS
    I am selecting above line from Kpro, then when i click on save system gives ABAP Runtime Error.
    Runtime Errors         CALL_FUNCTION_NOT_FOUND
    Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
    Date and Time          21.10.2008 18:35:26
    Short text
         Function module "PROJECT SYSTEM" not found.
    What happened?
         The function module "PROJECT SYSTEM" is called,
         but cannot be found in the library.
         Error in the ABAP Application Program
         The current ABAP program "SAPLSDCE" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    I am not understanding why this dump is coming.
    How i can come up from this issue.Pls guide me.If any customizing is required pls give the steps
    Thanks in Advance.
    Regards,
    Sandeep Theurkar

    There is a programming error somewhere.To get a solution quickly, do as follows:
    1. Turn off all badi's, user exits and whatever you have changed in standard SAP.
    2. Rerun - if it still fails - search in SAP notes for relevant notes
    3. If it doesnt fail - you have an error in your own programming
    4. If you are on relevant Support packages etc, send a message to SAP.
    Regards,
    Espen Leknes

  • ABAP runtime error / DDIC_STRUCLENG_INCONSISTENT

    Hi
    I got a ABAP runtime error DDIC_STRUCLENG_INCONSISTENT / short dump while creating a pricing condition record.
    The error is "accoring to the ABAP load, the structure should have been 1675 bytes long, according to information from ABAP dictionary at run time, the structure is 1756 bytes long".
    To correct the error, there was option to regenerate the program SAPMV130. There were other options to look at SAP notes.
    I tried regenerating program SAPMV130 and system is asking for access key which i don't have.
    Is there any solution?
    I am working on a standalone system.
    Thanks

    HI
    Same problem has occured for me while reversing PGI.
    I had re-activated the Data type using abaper.In runtime error,u can find data type
    First u check whether the data type is inconsistent by
    goto SE12, type ur data type then display,then goto Utilities -runtime object-display .here u can see there will be incosistent data type length
    So finally goto SE11,there will be activate button ,save
    I think ur problem will be solved
    Raghu

  • ABAP runtime errors    CONVERSION_CODEPAGE_UNKNOWN

    Hi All,
    We performed a system build. Upon validating the new system, we are encountering ABAP program errors when generating STMS import queue, viewing tables, testing RFC connections. Please refer to dump details below:
    ABAP runtime errors    CONVERSION_CODEPAGE_UNKNOWN
           Occurred on     17.11.2010 at 15:34:01
    Unable to convert from code page '1200' to code page '0120'.
    What happened?
    The current ABAP/4 program "SAPLTMSC " had to be terminated because
    one of the statements could not be executed.
    This is probably due to an error in the ABAP/4 program.
    What can you do?
    Note the actions and input that caused the error.
    Inform your SAP system administrator.
    You can print out this message by choosing "Print". Transaction ST22
    allows you to display and manage termination messages, including keeping
    them beyond their normal deletion date.
    Error analysis
    One of your chosen conversion tables (CODE PAGE) '1200' or '0120'
    is unknown to the system.
    For a list of conversion tables known to the system, see table
    TCP00. To display this, use Transaction SPAD.
    How to correct the error
    You can avoid this error by using a conversion table known
    to the system. Transaction SPAD allows you to display a
    list of these conversion tables.
    If you have modified the conversion table, use Transaction SP12
    to invalidate the code page buffer (CCC).

    Hi Nils,
    Thank you for your response. We checked the transaction SCP, unfortunately, it does not exist. Could you verify if this is the correct transaction code? With regard to kernel patch, yes we have the latest kernel patch. First, we performed kernel patch upgrade because we encountered issue during our SAP installation for V6R1. Our kernel patch level is not compatible with the said OS version. So, we performed reinstallation after the patch upgrade and we believe we are using the latest kernel for this system. Talking about the memory, we did not encounter any memory issues during the installation and after the installation of the SAP system.
    You mey refer to kernel and OS details below:
    46D patch level 2548
    OS version V6R1
    SAP version 46.C
    Could you give me further details regarding the character set? Based on the dumps, there's a problem with the conversion of character set. We already created SAP message on this matter and they want to connect into the system but unfortunately we do not have the saprouter to open the SAP connection.
    Your feedback/inputs will be greatly appreciated.
    Thank you in advance and have a great day ahead.
    Regards,
    Mark

  • Transaction IA12:ABAP runtime errors:TIME_OUT

    Hi,
    We are executing transaction IA12.We are getting ABAP runtime errors:Time_Out.
    We have searched for a SAP note to sort the issue:SAP Note 607086 - Functional location: Problems when displaying structure list.
    Please suggest what will be the option to solve the issue.
    Thanks.

    Hi,
    searching for the FORM routine where the timeout occurs ("mara_predecessor_f50") and excluding SAP notes that are modification notes or based on the implementation of modification notes, there is only one remaining note
    Note 658930 - Structure list: Configuration not considered with BOM
    for 46C up to Support Package SAPKH46C46.
    If this is still not in your system, the note may be a solution.
    If not, I'm running out of good ideas. Then also the SAP modification notes can be your last option.
    Regards,
    Klaus

  • When executing a query showing as ABAP runtime error RAISE_EXCEPTION

    Hi all,
    When i executed a query, it is showing as ABAP runtime error RAISE_EXCEPTION in the short dump.
    This is the Analysis in Short dump (ST22)...............
    Exception condition "DATE_BEFORE_RANGE" raised.   
    What happened?                                                                               
    The current ABAP/4 program encountered an unexpected  
    situation. 
    Error analysis                                                                               
    A RAISE statement in the program "SAPLSCAL" raised the exception
    condition "DATE_BEFORE_RANGE".                                  
    Since the exception was not intercepted by a superior program   
    in the hierarchy, processing was terminated.                                                                               
    Short description of exception condition:                                                                               
    Date is earlier than factory calendar definition                                                                               
    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                                                           
    "SAPLSCAL" or "LSCALU06"                                                      
    "DATE_CONVERT_TO_FACTORYDATE"                                                                               
    or                                                                               
    "SAPLSCAL" "DATE_BEFORE_RANGE"                                                                               
    or                                                                               
    "WRITEQUERY " "DATE_BEFORE_RANGE"                                                                               
    Could you pls any one tell me what could be the problem and how to reslove this issue.
    Thanks & Regards,
    Ravi Kumar.

    Hi Andre,
    Maintain your factory calendar idents Valid To year field (BJAHR) in Table TFACD
    You can do this via tcode SCAL, or navigate through SPRO.
    Most likely you have your factory calendars set with Valid To dates as 2010. You may also be encountering some load issues depending on exit routines used in transformations in determining workdays/factory days etc.
    Thanks,
    Eric Filmer

Maybe you are looking for

  • Why can't I sign into Premiere Elements 10 to use a template?

    I'm trying to select one of the templates to use for the credits of my film, but it keeps trying to get me to sign in. The signing in process begins, but it never actually signs me in or rejects me. The signing in box just remains on the screen. I've

  • TV-Out only displays text / not graphics

    I have a K7N2G-L motherboard with tv-out. When I try to setup my system to output video through the tv-out encoder I'm unable to select the TV out option under the properties dialog on the desktop for the tv-out encoder. The manual says I can do this

  • Received a phishing text message

    Today I received two phishing text messages, both with the same message body: (verizon wireless) 12/02/2014 your account will be blocked verizon wireless please log in to a web address ending with ".url.ph/" (I'm not listing the exact web address bec

  • IPhone 3G went into recovery mode after installing iTunes 9.0 and 3.1 OS

    Hi there, I recently had to waste about 2hrs time, to get a not working 3.1 OS update fixed on my iPhone 3G. This is not the kind of hassle I would expect from Apple! I am using a MacBook with OSX 10.5.6 and an iMac with SnowLeopard and iTunes 9.0. W

  • Scheduling a java code to run at a later time

    Hi, I am working on a part of a project where in when i make a request for a report to be generated from a jsp, the java code that generates the report must be scheduled to run in the night time e.g 12 AM. How do i go about doin this...?? Thanks Mess