Run time error (short dump) executing program SCAN_BW_REFERENCES in SE80

Hi experts,
I am not an ABAPer, or Basis person, rather a hybrid functional/technical Key User for our Business Warehouse system (BW 3.5, Netweaver 2004).  We have a user who cannot save BW reports to his favorites and he is getting a number of error messages.  OSS note 887002 seems to address this and indicates that I should run program SCAN_BW_REFERENCES from transaction SE80.  The program is supposed to perform the checks for BW objects assigned to the Favorites and identify situations causing terminations in BW frontend applications.  I have attempted to execute this program on several occassions and always get run-time errors (short dumps).  Here is the error:
Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time          2008.09.17 19:00:49
ShrtText
     No storage space available for extending an internal table.
What happened?
     You attempted to extend an internal table, but the required space was
     not available.
I have been informed by our Basis group that I have reached a memory limit, but they will not extend the memory paramters.  Any ideas on a work-a-round or a way to minimize the number of records this program is pulling in, in an attempt to get it to run?
Thanks,
HC

Hi,
The only response I got from Basis was that they would not extend the memory parameters because they are for all users in the system.  Not sure what that means. 
The full dump is too large to paste here.  I think what I will do is to see if our ABAPers can create a modified version of this program to include selection by user.  Typically it is for only one user that I need to run the program, and that surely would fall within the space requirements.
Thanks for your answer.
//HC

Similar Messages

  • How to debug  a run time error encountered while executing ZFunction Module

    Hi all,
    My requirement is to create a ZFunction Module that Generated a sales order
    for multiple line items and works for both Variant Configurable material and a Normal Material.
    I am using BAPI_SLSTRANSACT_CREATEMULTI in my Zfunction Module to create a
    Sales order
    My ZFunction Module works well if I give normal material as input.
    It also works well and generates a sales order if I give all Variant Configurable materials as input.
    But if I give both Variant Configurable material and a normal material it throws a run time error.
    Can some one tell me what is wrong? can some one suggest me how to debug this run time error
    Termination occurred in the ABAP program "SAPLCRM_CONFIG_OW" - in                            
    "CONFIG_TO_CBASE".                                                                          
    The main program was "RS_TESTFRAME_CALL ".                                                                               
    In the source code you have the termination point in line 63
    of the (Include) program "LCRM_CONFIG_OWF02".                                                
    Source Code Extract                                                                               
    Line SourceCde                                                                               
    |   33|                                       LT_CUXI_CUPRT                                       
    |   34|                                       LT_CUXI_CUVAL                                       
    |   35|                                       LT_CUXI_CUVK                                        
    |   36|                                       LS_CUXI_CUCFG.                                      
    37
    |   38|  PERFORM CREATE_PRICING_CSTIC USING IS_CONFIG-CUCFG-CFGINFO.                              
    39
    |   40|* set config to cbase                                                                      
    |   41|  CALL FUNCTION 'COM_CUXI_SET_SINGLE_CFG'                                                  
    |   42|       EXPORTING                                                                           
    |   43|            I_CFG_HEADER          = LS_CUXI_CUCFG                                          
    |   44|            I_ROOT_INSTANCE       = CV_INT_OBJ_NO                                          
    |   45|            I_LOGSYS              = LV_LOGSYS                                              
    |   46|       IMPORTING                                                                           
    |   47|            E_ROOT_INSTANCE       = CV_INT_OBJ_NO                                          
    |   48|       TABLES                                                                               
    |   49|            I_TAB_INSTANCES       = LT_CUXI_CUINS                                          
    |   50|            I_TAB_PART_OF         = LT_CUXI_CUPRT                                          
    |   51|            I_TAB_VALUES          = LT_CUXI_CUVAL                                          
    |   52|            I_TAB_VAR_KEYS        = LT_CUXI_CUVK                                           
    |   53|            I_TAB_RESTRICTIONS    = LT_CUXI_CURES                                          
    |   54|       EXCEPTIONS                                                                          
    |   55|            INVALID_INSTANCE      = 1                                                      
    |   56|            INTERNAL_ERROR        = 2                                                     
    57
    OTHERS                = 3.                                                        58
    |   59|  IF SY-SUBRC <> 0.                                                        
    |   60|    if sy-msgno is initial.                                                      
    |   61|      MESSAGE X010 WITH 'COM_CUXI_SET_SINGLE_CFG'.
    |   62|    else.                                                                             
    |>>>>>|      MESSAGE ID SY-MSGID TYPE 'X' NUMBER SY-MSGNO
    |   64|              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    |   65|    endif.                                                                               
    |   66|  ENDIF.                                                                               
    67
    |   68|ENDFORM.                               " CONFIG_TO_CBASE                                   

    Hey Amit...
    Can I Create a Sales order for VC and Non VC items using BAPI_SLSTRANSACT_CREATEMULTI
    Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI
    I am trying to create a Sales Order using a Zprogram. I have used BAPI_SLSTRANSACT_CREATEMULTI. If I give the input as Normal material I am able to generate a sale order. If I give the input as VC material I am able to generate a sales order. But if I give both VC and Normal material as input, I get a run time error as follows.
    Is it a limitation for BAPI_SLSTRANSACT_CREATEMULTI that we cannot create a sales order with both VC and Non-VC items or am I missing some data which I need to pass when I give both VC and Non VC items? I get this error only for my Zprogram. But if I try to create an order on screen manually I donu2019t get any error. This happens only if I create an order with my Zprogram.
    Some one please help me u2026I am just stuggling to get this doneu2026
    I dint find any posts that gives me information about this error.
    CUX1 034 u201CNo root instance found in header datau201D                                                                               
    In the source code you have the termination point in line 63                                   of the (Include) program "LCRM_CONFIG_OWF02".

  • Abap run time error during se38 new program creation

    when i try to create a new program, I get runtime error and it says start_call_sick
    details: database inconsistency : start transaction SICK.
    TRIGGER LOCATION OF RUNTIME
    PROGRAM: SAPMSYST
    INCLUDE : SAPMSYST
    ROW 1.763
    MODULE TYEP MODULE PAI
    MODULE NAME D020_SNC_CHECK_EXTID
    AND IT ALSO SAYS: KHA ( SYSTEM ID ) : SYSTEM RESTARTED
    WORK PROCESS RESTARTED
    SESSION TERMINATED.
    ANY IDEA HOW TO SOLVE THIS ERROR?????
    ITS ECC 5.0 WITH ORACEL DATABASE AND WIN 2K3 SP1 OS.
    WAITING FOR REPLY
    CHEERS
    kHALIL
    POINTS WILL BE AWARDED.

    when i try to create a new program, I get runtime error and it says start_call_sick
    details: database inconsistency : start transaction SICK.
    TRIGGER LOCATION OF RUNTIME
    PROGRAM: SAPMSYST
    INCLUDE : SAPMSYST
    ROW 1.763
    MODULE TYEP MODULE PAI
    MODULE NAME D020_SNC_CHECK_EXTID
    AND IT ALSO SAYS: KHA ( SYSTEM ID ) : SYSTEM RESTARTED
    WORK PROCESS RESTARTED
    SESSION TERMINATED.
    ANY IDEA HOW TO SOLVE THIS ERROR?????
    ITS ECC 5.0 WITH ORACEL DATABASE AND WIN 2K3 SP1 OS.
    WAITING FOR REPLY
    CHEERS
    kHALIL
    POINTS WILL BE AWARDED.

  • Run time error in Service entry sheet

    Hi Experts
    When I create a Service Purchase Order & when I enter a Service Entry sheet using ML81N, When I save it I am getting a run time error (Short dump has not been completely stored (too big) ).Could you please tell me how to overcome to this problem.
    AR
    Edited by: Amit  Rana on Jan 8, 2010 12:53 AM

    Hi Experts,
    The following error i am getting when i am doing the MIGO from PO.
    Runtime Errors MESSAGE_TYPE_X
    Date and Time 10.01.2010 10:09:56
    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).
    Error analysis
    Short text of error message:
    No RFC destination is defined for SAP Global Trade Services
    Technical information about the message:
    Message classe...... "/SAPSLL/PLUGINR3"
    Number.............. 002
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "
    Trigger Location of Runtime Error
    Program SAPLMBWL
    Include LMBWLU21
    Row 59
    Module type (FUNCTION)
    Module Name MB_POST_GOODS_MOVEMENT
    AR

  • Time_out & TSV_TNEW_PAGE_ALLOC_FAILED Run time error on MB5B

    Hi expert,
    Time_out & TSV_TNEW_PAGE_ALLOC_FAILED Run time error getting while executing Tx-MB5B.
    ECC 6.0
    oracle 10g
    HPux
    Regards,

    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    Date and Time          08.02.2012 14:50:11
    Short text
    No more storage space available for extending an internal table.
    What happened?
    You attempted to extend an internal table, but the required space was
    not available.
    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.
    Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
    If there is a temporary bottleneck, execute the transaction again.
    If the error persists, ask your system administrator to check the
    following profile parameters:
    o  ztta/roll_area            (1.000.000 - 15.000.000)
    Classic roll area per user and internal mode
    usual amount of roll area per user and internal mode
    o  ztta/roll_extension       (10.000.000 - 500.000.000)
    Amount of memory per user in extended memory (EM)
    o  abap/heap_area_total      (100.000.000 - 1.500.000.000)
    Amount of memory (malloc) for all users of an application
    server. If several background processes are running on
    one server, temporary bottlenecks may occur.
    Of course, the amount of memory (in bytes) must also be
    available on the machine (main memory or file system swap).
    Caution:
    The operating system must be set up so that there is also
    enough memory for each process. Usually, the maximum address
    space is too small.
    Ask your hardware manufacturer or your competence center
    about this.
    In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
    Restriction of memory allocated to the heap with malloc
    for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
    Restriction of memory allocated to the heap with malloc
    for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
    Extended memory area from which all users of an
    application server can satisfy their memory requirement.
    Error analysis
    The internal table "\PROGRAM=RM07MLBD\DATA=G_T_COLOR" could not be further
    extended. To enable
    error handling, the table had to be delete before this log was written.
    As a result, the table is displayed further down or, if you branch to
    the ABAP Debugger, with 0 rows.
    At the time of the termination, the following data was determined for
    the relevant internal table:
    Memory location: "Session memory"
    Row width: 76
    Number of rows: 3
    Allocated rows: 3
    Newly requested rows: 128 (in 1 blocks)
    How to correct the error
    The amount of storage space (in bytes) filled at termination time was:
    Roll area...................... 5720752
    Extended memory (EM)........... 502807584
    Assigned memory (HEAP)......... 1842267952
    Short area..................... " "
    Paging area.................... 40960
    Maximum address space.......... 4294967295
    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:
    "TSV_TNEW_PAGE_ALLOC_FAILED" " "
    "RM07MLBD" or "RM07MLBD"
    "COLORIZE_TOTALS_FLAT"
    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.

  • Run time error while running BDC for production order creation and confirmation:

    Dear Gurus,
    We have a situation, where the users are trying to do the entries creation of order or confirmation (through manual and BDC). But, if there is any kind of a deficit quantities in consumption or GR quantity, then it is going to run time error and Dumps are coming in program SAPLCORB
    and the transaction code is coming for CO11N.
    How to avoid this error to run the production system in smoothing way...Any flash lights on this will be great full
    Regards,
    Madhu.G

    Hi Madhu,
    Expert Caetano has rightly point out. Refer Note 1840705 - RAISE_EXCEPTION short dump if running CO11N in background
    Cause
    The short dump is triggered because SAP transaction CO11N contains new GUI elements that cannot always be dealt with in a background process,
    such as the confirmation texts.
    Resolution
    SAP recommends that the standard production order BAPIs, such as BAPI_PRODORDCONF_CREATE_TT, should be used to post a confirmation in background.
    If this is not feasible, the following workaround may be uses:
    Define a confirmation profile in transaction OPK0; 
    In the detail areas, remove the area "Confirmation text"; 
    Set this profile as standard, so that it is chosen automatically by the system when a batch-job
    is started; 
    Assign this confirmation profile to the batch user with transaction SU3 using parameter CORUPROF.
    Also see Note 429432 - CO11N: Batch input in background dumps if long text is maintained
    Refer to note 1154692 - Endless loop during confirmation in background if you doing Auto GR during confirmations
    Thanks & Regards,
    Ramagiri

  • Run Time Error - Timeout (QA32)

    Hi Gurus,
    Iam getting Run time error when i execute QA32 transaction. it is throwing a short dump while saving the document after entering the details in Usage decision.
    Please let me know how to go about it.
    thanking you all advance for your kind help.
    rgds

    Hi Nagesh,
    Thanks for your answer, can please let me know how to configure this. my client is using UDcode as 'UD01' and 001 Accepted. and when he is trying to save this. the system is saying performing stock posting and after sometime throws the runtime error.
    can you please give me step by step configuration for the above. i will be very much thankful to you.
    Rgds

  • GETWA_NOT_ASSIGNED run time error in LKKBLF99 include.

    Hi all,
      Thank you for viewing this thread. I am facing this run time error when I execute a ZProgram in    SAP database version. 700  version. In 4.6c it is working fine. The info in the run time error is:
    What happened?                                                                               
    Error in the ABAP Application Program                                                                               
    The current ABAP program "SAPLKKBL" had to be terminated because it has come across a statement that unfortunately cannot be executed                    
    Source code where it is getting terminated:
    2825
    2826
          FORM GEN_FIELD_OUT2                                           *
    2827
    2828
    2829
    2830
    form gen_field_out2.
    2831
    field-symbols <l_initial>.
    2832
    2833
    case gs_out-field_colcount.
    2834
    when 001.
    2835
    if gs_out_flags-slave ne 'X'.
    2836
    assign <fm01> to <field>.
    2837
    gs_fc = gs_mfc01.
    2838
    else.
    2839
    assign <fs01> to <field>.
    2840
    gs_fc = gs_sfc01.
    2841
    endif.
    2842
    when 002.
    2843
    if gs_out_flags-slave ne 'X'.
    |>>>>>|        assign <fm02> to <field>.   ""this is where the std program LKKBLF99 is getting terminated.
    The function module from which it is navigating from the ZProgram to this standard include is "REUSE_ALV_HIERSEQ_LIST_DISPLAY"
    The fieldsymbols are declared as type any in the standard program, LKKBLTOP.
    I tried to get solution from the threads posted, but couldnt arrive to a proper solution. Kindly suggest as soon as possible.                                 
    Thanks
    Sam
    Edited by: Palakodety Samyuktha on Apr 8, 2009 6:31 AM

    Hi Voros,
       Thank you for your quick reply, I tried that note but it didnt help me. As for the field symbol fs02, it is blank. But <Field> has  a value as '0000000055-Base'.
    Kindly help me further.
    In the first case, I  tried to change the value of ' gs_out_flags-slave' . I tried to find whether it is the problem with field symbols, the actual run time error without changing the values in debugging mode occurs at line 2847.
    2825
    2826
          FORM GEN_FIELD_OUT2                                           *
    2827
    2828
    2829
    2830
    form gen_field_out2.
    2831
    field-symbols <l_initial>.
    2832
    2833
    case gs_out-field_colcount.
    2834
    when 001.
    2835
    if gs_out_flags-slave ne 'X'.
    2836
    assign <fm01> to <field>.
    2837
    gs_fc = gs_mfc01.
    2838
    else.
    2839
    assign <fs01> to <field>.
    2840
    gs_fc = gs_sfc01.
    2841
    endif.
    2842
    when 002.
    2843
    if gs_out_flags-slave ne 'X'.
    2844
    assign <fm02> to <field>.
    2845
    gs_fc = gs_mfc02.
    2846
    else.
    >>>>>>        assign <fs02> to <field>.                   "this is where it is getting terminated                      |
    2848
    gs_fc = gs_sfc02.
    | 2849|      endif.
    sorry for the inconvenience caused.
    Thanks
    sam

  • ZSAPMV45A copy of sapmv45A giving run time error

    Hi ABAPERs
    I copied standard program sapmv45A (trx va31) to zsapmv45A to make few changes according to user requirement. I copied all screens as well as includes . Now when I execute this zprogram it gives me a run time error : The current ABAP program "SAPMV45A" had to be terminated because it has                      
    come across a statement that unfortunately cannot be executed.          
    Error analysis                                                                               
    The system attempted to use dynpro 0000 in program "SAPMV45A".                                |
    This dynpro does not exist.     
    Help me
    Thanks in advance

    Hi
    I don't think it was a good idea to copy that program.
    All screens to be called are managed centrally (see fm SCREEN_SEQUENCE_CONTROL), the setting is done by transaction VFBS.
    So I can suppose the setting still calls the screen of SAPMV45A.
    Also you should considere if you're in release ecc 6.00 you can risk to lose all standard enhancement of SAPMV45A, because they assigned to the program, so they can't be copied in a new program.
    So probably the best solution is to create an implicit enhancement or (if you can't do it) to change the standard program.
    Max

  • Getting run time errors while executing the copied SAP programs

    Hi folks,
    i want to copy an sap program.after coping i need to change some coding there.then i have to create a new transaction for that.
    i am just copying the sap program RQEEAL10(transaction-QA32) to Z_RQEEAL10. it has 4 include  programs.i am copying them to z programs like
    RQ00MF10 copied to z_RQ00MF10
    RQALVF14 copied to z_RQALVF14
    RQALVF16 copied to z_RQALVF16
    RQALVTOP copied to z_RQALVTOP.
    now i am executing that program Z_RQEEAL10.but i am getting run time errors as given below.
    <b>runtime error---</b>
    The termination occurred in the ABAP program "Z_RQEEAL10" in           
    "SELECT_FIELDS_MANIP2_F16".                                           
    The main program was "Z_RQEEAL10 ".                                                                               
    The termination occurred in line 257 of the source code of the (Include)
    program "RQALVF16"                                                    
    of the source code of program "RQALVF16" (when calling the editor 2570).
    --Error in ABAP statement when processing an internal table.  
    --When changing or deleting one or more lines of the internal table         
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS" or when inserting in the table   
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS", 0 was used as                  
    the line index. An index less than or equal to zero is not                
    allowed.                                                                               
    The error can occur when using the following options:                     
    1. "INDEX idx" for specifying the line number in the table                
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS"                                 
       where you want to change, insert or delete.                            
    2. "FROM idx" for specifying the start index when deleting a line         
       area from or inserting a line area into the table                      
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS".                                
    3. "TO idx" for specifying the end index when deleting a line             
       area from or inserting a line area into the table                      
    "\PROGRAM=Z_RQEEAL10\DATA=SELECT_FIELDS".                                                                               
    When the program terminated, the table had 2 lines.                       
    these r the runtime errors what i am getting.where is the problem?i have activated all interface & includes.plz advice.
    Thanks & regards

    Hi Madhu,
    I will give you one more check point where you have to give your concentration while copying the standard programs....
    Call Customer-Function (Function Exists) if any in the Program when copied will not get executed. Instead you need to call the FM Directly.
    one more is also here
    You are likely to have some problems with the text-elements and translation that may have been maintained for the original report.
    ~~Guduri

  • ABAP Run time Error whle executing the Balance sheet report in FGI0

    Hi,
    I am getting the below ABAP Run time error while executing the Balance Sheet report in FGI0.It was working before but now it is giving the error.Kindly help me in solving this.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          06/12/2009 15:17:17
    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).
    Error analysis
         Short text of error message:
         RAISE RKD_CONDITION_READ       (internal error)
         Long text of error message:
          Diagnosis
              The program was terminated because a situation occurred which
              should not have arisen.
          Procedure
              Analyze the situation and contact SAP.
         Technical information about the message:
         Message class....... "KH"
         Number.............. 299
         Variable 1.......... "RKD_CONDITION_READ"
         Variable 2.......... " "
         Variable 3.......... " "
         Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLKYPR
        Include                                 LKYPRU31
        Row                                     36
        Module type                             (FUNCTION)
        Module Name                             RKD_CONDITION_READ
    Thanks
    Supriya

    Hello,
    Please refer SAP
    Note 971535 - dump when deleting characteristic with hierarchy
    Regards,
    Ravi

  • Getting run time error when executing stanard SAP transaction

    Hi experts,
        I am trying to run the standard SAP report transaction S_ALR_87013557. but it is giving the run time error "LOAD_PROGRAM_NOT_FOUND". i also check the program name that appears in the short dump with SE38. it gives the message that no program exist.
      but when i try to run other S_ALR_ trasactions, they are running correctly.
      So can just help me in this regards.

    Check if this program GPA8PD2X83M8PML7SBUU3COEFIK exist in your system.
    if yes then see which transaction it is attached.
    if that transaction is executing properly, then functional person can tell if that's the report they are looking for.
    if no u can execute this prog from se38 & check. if that works, then you can create z transaction & attach that program.
    This will be workaround, ideally you should raise OSS ticket. SAP may release new Note .

  • 'CONVT_NO_NUMBER'  run time error in custom program of upgraded ECC system.

    Hi,
    I am getting a run time error in custom program and st22 shows 'CONVT_NO_NUMBER' as the cause.
    We have just upgraded system to ECC6 and with 4.7 we were not getting this error.
    Can you please let me know if there is any SAP note to address this ?
    Thanks,
    Avinash

    Hi Avinash,
    Please see the below link for Sap Notes:
    [Program is giving a Short Dump u201CCONVT_NO_NUMBERu201D.;
    Regards,
    Md Ziauddin

  • Run-time error while executing alv grid report

    Hi everyone
    I m trying to run a alv grid report it is giving a run time error while executing the statement CALL METHOD V_ALV->SET_TOOLBAR_INTERACTIVE.
    Actually i added 2 buttons in the toolbar.after that when i execute the report i m getting errors.
    <b>Error Analysis</b>
    An exception occurred that is explained in detail below.                     
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not    
    caught in                                                                   
    procedure "TOOLBAR_MENUS_INIT" "(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:                                             
    You attempted to use a 'NULL' object reference (points to 'nothing')         
    access a component (variable: "ME->M_CL_MENU_BUTTON_VARIANT").               
    An object reference must point to an object (an instance of a class)         
    before it can be used to access components.                                  
    Either the reference was never set or it was set to 'NULL' using the         
    CLEAR statement.

    Hi Dinesh,
    Seems you have not initialised ( Instantiated in OO ) the object and / or the parent container.
    Check if you have create object for both the parent as well as the alv object.
    So when you instatntiate the object of ALV you pass the object ( instantiated before hand ) in the parent container position.
    Also you would have to register the events to the object using method. Then only the buttons will finction.
    eg :
    IF G_CUSTOM_CONTAINER IS INITIAL.
        CREATE OBJECT CUSTOM_CONTAINER_1
               EXPORTING CONTAINER_NAME = CONTAINER_1.
        CREATE OBJECT GRID1
               EXPORTING I_PARENT = CUSTOM_CONTAINER_1.
        CALL METHOD ALV_GRID1->SET_TABLE_FOR_FIRST_DISPLAY
             EXPORTING I_STRUCTURE_NAME = 'VBAK
             CHANGING  IT_OUTTAB        = IT_VBAK.
    Reward points if useful.

  • Run time error while executing KP06

    Hello All,
    A run time error is being returned when I execute the tcode KP06. After entering all required field such as cost elements, cost center / CCgroup, then I pressed period screen / overview screen ... and it went to abap dump ...
    FYI, I have upgraded to 4.7 to ECC system.
    Regards,
    Bharath.
    Moderator message: please do more research before asking, use ST22, search for SAP notes, check your custom enhancements.
    Edited by: Thomas Zloch on Aug 22, 2011 9:58 AM

    Ok. Look at the dump in ST22 and solve your problem.

Maybe you are looking for