Runtime error:  DBIF_REPO_SQL_ERROR

Hi All,
I am getting the above mentioned error along with the error text :
Database error text........: "ORA-01654: unable to extend index SAPR3****  
  by 8192 in tablespace PSAP****"
What exactly does this error indicate? how can it be resolved?
Many thanks.

>
Neha Nagrani wrote:
> Hi All,
>
> I am getting the above mentioned error along with the error text :
>
> Database error text........: "ORA-01654: unable to extend index SAPR3****  
>   by 8192 in tablespace PSAP****"
> 
>
> What exactly does this error indicate? how can it be resolved?
>
> Many thanks.
Ask your BASIS team to extend tablespace  +"PSAP*** "+*

Similar Messages

  • Runtime error DBIF_REPO_SQL_ERROR in production server

    Hello All,
    I am recieving the following running time error in my Production system. Any help would be really appreciated.
    Runtime Error          DBIF_REPO_SQL_ERROR
           Occurred on     06.09.2009 at   19:16:45
    *SQL error 3114 occurred when accessing program*
    What happened?
    The system is no longer linked to an ORACLE instance.
    No further operations can be performed on the database.
    What can you do?
    You cannot eliminate this error yourself.
    Please inform your database administrator.
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your
    SAP system administrator.
    With transaction ST22, for dump analysis, you can see and manage
    termination messages and, in particular, save them for longer periods of
    time.
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    The system attempted to access an ORACLE instance to which it is
    no longer linked.
    This can occur if the ORACLE instance has been stopped due to an
    error or an external operation.
    How to correct the error
    Database error text........: "ORA-03114: not connected to ORACLE"
    Triggering SQL statement...: "CX_SY_OPEN_SQL_DB=============CP "
    The current status of the ORACLE instance cannot be determined.
    It may still be inactive or the database administrator may have
    restarted it.
    In any case, all systems that have accessed the ORACLE instance
    must be restarted after the ORACLE instance has been restarted.
    If you were working on a central system, inform
    your system administrator.
    If you were working on an external local system, inform
    the person responsible for this system.
    If you were working on your own local system, restart
    the system yourself.
    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:
    "DBIF_REPO_SQL_ERROR" C
    "SAPLSALA" or "LSALAU01"
    "SALA_UPDATE_TRANS_SPEZ_MON"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    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:
    "DBIF_REPO_SQL_ERROR" C
    "SAPLSALA" or "LSALAU01"
    "SALA_UPDATE_TRANS_SPEZ_MON"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
    Please check the entries in the system log (Transaction SM21).
    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:
    "DBIF_REPO_SQL_ERROR" C
    "SAPLSALA" or "LSALAU01"
    "SALA_UPDATE_TRANS_SPEZ_MON"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    Already we have checked the SAPnotes 534729, 135942 and 112266 advice to configure all network
    components on the same fixed speed and full-duplex, instead of using the auto-negotiating.
    Please suggest... thanks in advace.
    Regards,
    Suresh
    Edited by: Suresh Kalagarla on Sep 9, 2009 11:27 AM

    I'd say the dump tells you what you need to do:
    > -
    > What happened?
    > -
    >
    > The system is no longer linked to an ORACLE instance.
    > No further operations can be performed on the database.
    >
    > -
    > What can you do?
    > -
    >
    > You cannot eliminate this error yourself.
    > Please inform your database administrator.
    > Make a note of the actions and input which caused the error.
    > -
    >
    > To resolve the problem, contact your
    > SAP system administrator.
    >

  • Runtime errors  DBIF_REPO_SQL_ERROR

    Hi All ,
    When i am creating source system selected Replicate as well opition ,its giving runtime error
    "DBIF_REPO_SQL_ERROR".
    Short Text :SQL error "-1000" occured when accessing the program

    Dear Venkat,
    When we were gettting an error like DBIF_REPO_SQL_ERROR it was mostly related to the Table Space issue. Hope this helps.
    Regards
    Vijay

  • Getting Runtime Error while Activating Characteristics in BW sandbox system

    Hi, i m getting  runtime error while activating Characteristics. Error as All InfoObjects Already Saved(locked)
    Short Text
    SQL error 1691 occurred when accessing program "GP4H8Z73D1WOGH7XBIZ54N5GXEG "
       Runtime Errors         DBIF_REPO_SQL_ERROR
    even if creating a new Characteristics same error is comming.
    Key Figures are getting created successfully but problems is comming only with Characteristics. Please Help...
    Edited by: kush kumar on Mar 23, 2010 11:56 AM

    Hi,
    Follow bellow steps:
    a) Once check the Lock entries by useing SM13.
    Goto SM13--> Select your object lock entries --> Select delete.
    b). Acitvate the Infoobject.
    Regards.

  • Runtime error SQL error 3114 occurred when accessing program CX_ w

    Hi Friends,
    Iam in a big mess . I have one query based on one my Zinfocube.This query ia attached in the workbook .. Previuolsy all was fine , but now whever iam executing this query it is throwing me the exception
    Query 0: Runtime error SQL error 3114 occurred when accessing program CX_ with parallel processing via RFC.
    and
    Beim Lesen der Daten sind Fehler aufgetreten. Navigation ist möglich
    I am not able to get the cause of error ..
    Can anybody help me in this regrd as its a bit urgent.
    Thanks in advance..

    Hi , thanks for replying ,
    I have tried running query through RSRT also , its not working still it is giving me the same error .
    In st22 it is showing me the follwing dump.
    DBIF_REPO_SQL_ERROR
    Short text
        SQL error 3114 occurred when accessing program
    What happened?
        The system is no longer linked to an ORACLE instance.
        No further operations can be performed on the database.
    What can you do?
        You cannot eliminate this error yourself.
        Please inform your database administrator.
        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.
        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.
    Error analysis
        The system attempted to access an ORACLE instance to which
        it is no longer linked.
        This situation may arise because the ORACLE instance
        has been stopped due to an error or an external operation.
    How to correct the error
        Database error text........: "ORA-03114: not connected to ORACLE"
        Triggering SQL statement...: "CX_SQL_EXCEPTION==============CP "
        The current status of the ORACLE instance cannot be determined.
        It may be still inactive or the database administrator may have
        restarted it.
        In any case, all systems that have accessed the ORACLE instance
        must be restarted after the ORACLE instance has been restarted.
        If you were working on a central system, inform
        your system administrator.
        If you were working on an external local system, inform
        the person responsible for this system.
        If you were working on your own local system, restart
        the system yourself.
        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_REPO_SQL_ERROR" " "
        "CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
        "NEXT_PACKAGE"
        If you cannot solve the problem yourself and want to send an errornotification 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.
    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_REPO_SQL_ERROR" " "
    "CL_SQL_RESULT_SET=============CP" or "CL_SQL_RESULT_SET=============CM006"
    "NEXT_PACKAGE"
    Thanks in Advance..

  • Runtime error in starting Lightroom

    I receive the following message when I try to start Lightroom:
    Microsoft Visual C++ Runtime Library
    Runtime Error!
    Program:...Files\Adobe\Adobe Photoshop Lightroom 1.2\lightroom.exe
    This application has requested the Runtime to terminate it in an unusual way.
    Please contact the application's support team for more information.
    Lightroom ran well for several days and then failed to open with the above message.
    I have tried everything I know to do (uninstalled and reinstalled the application, restored the computer to a restore point before Lightroom was originally installed, etc.) and do not know were to go from here. Suggestions would be appreciated.
    I am using Windows XP sp2 and have 4 GB of ram and 250 GB of hard disk space.
    Thanks,
    Cliff Culp

    Aha! A fix! Please look at this...
    http://www.adobeforums.com/cgi-bin
    bob frost, "Help! Runtime error after Lightroom 1.1 install!" #10, 27 Jun 2007 6:54 am

  • Runtime error while executing rule

    Hello All,
      While executing the DTP for a cube, im facing the error as Runtime error while executing rule -> see long text .
      For this source is another Cube, where im loading the data from Cube to Cube.
    Error Description are as follows:-
    Error Location: Object Type    TRFN
    Error Location: Object Name    0T9SCR6Q4VWS1SOPNRRBOY1YD51XJ7PX
    Error Location: Operation Type ROUTINE
    Error Location: Operation Name
    Error Location: Operation ID   00034 0000
    Error Severity                 100
    Original Record: Segment       0001
    Original Record: Number        557
    and Also descripton is :-
    Diagnosis
        An error occurred while executing a transformation rule:
        The exact error message is:
        Division by zero
        The error was triggered at the following point in the program
        GP4H0CW3MLPOTR3E8Y93QZT2YHA 4476
    System Response
        Processing the data record has been terminated.
    Procedure
    The following additional information is included in the higher-level
    node of the monitor:
       Transformation ID
       Data record number of the source record
       Number and name of the rule which produced the error
    Let me know ur valuable suggestions on these error...
    thanks.

    Hello,
    I have checked all the transformation and End Routines.All are working fine.Yesterday i have loaded some data into it, but today its gettting errored out.
    Checked completely in the forum for threads related to this, but couldnt find proper thread which had solutions....
    thanks,
    srinivas.

  • Could someone help me with a Runtime Error while saving a PDF file?

    While saving a 28 page PDF file in Illustrator today, I got a window saying, "This application has requested the "Runtime" to terminate it in a unusual way." It said to contact the applications support team for more information. I keep getting the same thing each time I try it. Does anyone know how to fix this issue or how I contact the applications support team ?
    Thank you for any insight.
    Pam

    It is a 13.5x11 inch calendar. There are 14 pages with images on them and
    some text. The other pages have text, a grid and a colored background with a
    gaussian blur. I saved each page as an "outline".
    The printer I am using requested I save all pages in a pdf file. I was
    successful in saving all but about six pages, now I can't even open the
    file.
    What happens is... I open Illustrator
                                   I open the pdf file
                                   A window appears that says... Runtime Error,
    This application has requested the Runtime to terminate it in an unusual
    way. Please contact the application's support team for more information.
                                   I select ok
                                   then a window appears that says... Adobe
    Illustrator CS5 has stopped working. A problem caused the program to stop
    working correctly. Windows will close the program and notify you if a
    solution is available.
                                   Then the program closes.
    So far I have not been notified of anything.
    Please let me know if you need more details.
    Thank you so much for helping me with this.
    Pam

  • RunTime Error while saving a Sales Order

    Hi All,
    When i am saving a Sales Order, the system is throwing a Runtime Error.
    The ABAP Code in the Runtime Error screen as follows.
              select * from (t681-kotab) appending table <cond_tab>
                     up to 1 rows
                     where kappl  = se_kappl
                     and   kschl  = se_kschl
                     and   datbi >= se_date
                     and   datab <= se_date
                     and   (coding_tab).
    Till these days, there was no such error while saving a Sales Order.
    How to resolve this issue?
    Regards
    Pavan

    Hi,
    The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
    select * from (t681-kotab) appending table <cond_tab>
    up to 1 rows
    where kappl = se_kappl
    and kschl = se_kschl
    and datbi >= se_date
    and datab <= se_date
    and (coding_tab).
    The reason could be is someone has screwed up the entries in T681 table. Check that out.
    Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
    Let me know if you are still stuck up.
    If you can send me the ST22 dump of the run time error, i might be able to help you more  on this.
    Hope this helps.
    Thanks,
    Balaji

  • WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR

    hi to all experts,
    whenever i try to delete a particular sale order im getting a runtime error
    stating that
    Short text
        Screen: Illegal message
    What happened?
        The current screen processing action was terminated since a situat
        occurred where the application could not continue.
        This is probably due to an error in the ABAP program or in the cur
        screen.
    Error analysis
        The program attempted to issue a " " message during "Exit Command" processing.
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    Trigger Location of Runtime Error
        Program                                 SAPMV45A
        Include                                 MV45AFZZ
        Row                                     370
        Module type                             (FORM)
        Module Name                             USEREXIT_SAVE_DOCUMENT
    SourceCde
                  message e001(zm) WITH text-335 ltab-kunnr text-334.
                else.
                  if ktab-jkunnr <> ltab-kunnr.
                    ktab-jkunnr = ltab-kunnr.
                    jobsitecode = ltab-kunnr.
                    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                    EXPORTING
                      input  = jobsitecode
                      IMPORTING
                      output = jobsitecode.
                    SELECT SINGLE * FROM kna1 WHERE kunnr = jobsitecode.
                    IF sy-subrc = 0.
                      ktab-jname1 = kna1-name1.
                      ktab-jstras = kna1-stras.
                    ENDIF.
                    chg_flg = 'X'.
                  endif.
                endif.
              else.
                message e001(zm) WITH text-336.
    * Validation for relationship between Sold-to Party and Ship-to Party
    *          if ktab-ckunnr+0(4) NE ktab-jkunnr+0(4).
    *            message e001(zm) WITH text-335 ktab-jkunnr text-337 ktab-ckunnr.
    *          endif.
              custcode1 = ktab-ckunnr.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = custcode1
                IMPORTING
                  output = custcode1.
              jobsitecode1 = ktab-jkunnr.
              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input  = jobsitecode1
                IMPORTING
                  output = jobsitecode1.
              SELECT SINGLE * FROM knvp
              WHERE kunnr = custcode1
                AND vkorg = vbak-vkorg
                AND vtweg = vbak-vtweg
                AND spart = vbak-spart
                AND parvw = 'WE'
    Error analysis
        The program attempted to issue a " " message during "Exit Command"
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    Trigger Location of Runtime Error
        Program                                 SAPMV45A
        Include                                 MV45AFZZ
        Row                                     370
        Module type                             (FORM)
        Module Name                             USEREXIT_SAVE_DOCUMENT

    Hi,
    Seems there is some problem with the user exit USEREXIT_SAVE_DOCUMENT..
    Put a breakpoint and see.
    Regards,
    Nagaraj

  • WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR " Screen: Illegal message"

    Hi Experts,
    While deleting a sales order giving run time error.  PFB runtime error details.
    If you know any OSS message, please let m know. I tried, but there is no luck.
    Short text
        Screen: Illegal message
    What happened?
        The current screen processing action was terminated since a situation
        occurred where the application could not continue.
        This is probably due to an error in the ABAP program or in the current
        screen.
    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.
    Error analysis
        The program attempted to issue a " " message during "Exit Command" processing.
        This is an illegal operation.
        The program was terminated.
        Screen name.............. "SAPMV45A"
        Screen number............ 4001
    How to correct the error
        The program must be modified to correct the error.
        The modification must be made in "Exit Command" processing.
        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)".
    Source Code Extract
    Line  SourceCde
        1 *---------------------------------------------------------------------*
        2 *       FORM YVBEP_LESEN                                              *
        3 *---------------------------------------------------------------------*
        4 *       Lesen der Tabelle YVBEP (nicht sortiert)                      *
        5 *---------------------------------------------------------------------*
        6 FORM YVBEP_LESEN USING US_POSNR
        7                        US_ETENR
        8               CHANGING CH_TABIX.
        9
       10   YVBEP = SPACE.
       11   YVBEP-MANDT = VBAK-MANDT.
       12   YVBEP-VBELN = VBAK-VBELN.
       13   YVBEP-POSNR = US_POSNR.
       14   YVBEP-ETENR = US_ETENR.
       15   READ TABLE YVBEP.
       16   IF SY-SUBRC > 0.
       17     MESSAGE E506 WITH US_POSNR US_ETENR.
       18   ENDIF.
    >>>>>   CH_TABIX = SY-TABIX.
       20
       21 ENDFORM.
    Could you please help on this issue.
    Thanks
    Srinu

    Hi Srinu,
    it looks like you got the error message Schedule line &1 &2 is missing in table YVBEP while deleting the sales order.
    It seems, that there are no SAP notes regarding this issue. Do you have this issue with all orders or with a single order?
    If only a single order causes this issue, maybe something was wrong during an update.
    If you get this error for many orders, then custom code (modification, enhancement, user exit in MV45AFZZ, ...) may be the reason for it.
    If you have no custom code in module pool SAPMV45A, then contact SAP for this issue.
    Regards,
    Klaus

  • Portal runtime error while selecting page layout in WPC editor

    Hello,
    in web page composer, editing page, when i click on "select page layout" I have a portal runtime error popup.
    The logfile shows the following :
    #1.5 #005056834112005E0000000C00000FA800048E28A94966CC#1282205196819#com.sap.portal.prt.runtime#sap.com/irj#com.sap.portal.prt.runtime#1016#149##n/a##7ff9c93eab6811dfa9c70000003307de#SAPEngine_Application_Thread[impl:3]_15##0#0#Error##Java###10:06_19/08/10_0010_3344350
    [EXCEPTION]
    #1#com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error occurs during the rendering of jsp component
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: Error in java compiling
    Caused by: com.sapportals.portal.prt.servlets_jsp.server.compiler.CompilingException: E:
    usr
    sap
    EPD
    JC00
    j2ee
    cluster
    server0
    apps
    sap.com
    irj
    servlet_jsp
    irj
    root
    WEB-INF
    portal
    portalapps
    com.sap.netweaver.bc.util
    lib
    bc.util.public_api.jar(com/sapportals/wcm/WcmException.java):24: class WcmException is public, should be declared in a file named WcmException.java
    (source unavailable)
    1 error
    I have the same by clicking on "check assignments"
    Any help ?
    Thanks

    Hello Jego.
    We faced the same issue after upgrade to EHP1 SP07 last week and managed to solve it by modification of layout.jsp and com.sap.nw.wpc.layoutmanager.LayoutBean within com.sap.nw.wpc.designtime.par. SAP's code requires an additional catch handler, so it is better to rise an OSS message.
    As a workaround you may change a default layout for wpc main page (good for new pages) or manually edit output.xml for existing pages.
    Best regards,
    Aliaksandr Zhukau

  • Runtime Error when installing Adobe Creative Suite 5.5 Production Premium

    I am trying to install Adobe Creative Suite 5.5 Production Premium, but I keep getting a 'Runtime Error!':  This application has requested the Runtime to terminate it in an unusual way.  Please contact the application's support team for more information.
    What should I do?  Any help greatly appreciated!  I am running Win 7, Service Pack 1, 64 bit.

    We cannot know. Your information is hugely insufficient. Check Your Windows Event Viewer and tell us the "fault module" plus provide detailed specs for your computer. Runtime errors usualyl mean that A DLL is missing, a security tool is blocking critical functions or that the processor is not compatible in teh first place. Just as well this could be a driver issue with your SATA bus or whatever.
    Mylenium

  • Runtime error in enhancement spot-' mereq_topline does  not exists.'

    Hi all,
    I have implemented an implicit enhancement spot in ME53n.
    When i applied break point in enhancement spot and control goes to ebhancement spot in debugging mode, i got purchse requisition number in mereq_topline.
    When i tried to use this structure value in code i get runtime error-
    ' mereq_topline does  not exists.'
    Can you please guide how to resolve  this runtime error.
    thanks.
    Edited by: Sanjay_lnt on Sep 20, 2010 8:52 AM

    Sanjay,
    try to delete the enhancement and recreate it
    Thanks
    Bala Duvvuri

  • Runtime Error in ALV Tree Output

    Dear All, I am trying to create a ALV Tree using Class cl_gui_alv_tree. The Report Shows the Output with the first Node but when i try to expand it is dumping with a runtime error GETWA_NOT_ASSIGNED in class CL_ALV_TREE_BASE and method SET_ITEMS_FOR_COLUMN. The Reason being the data which was copied in the initial node display to mt_outtab is getting refreshed.
    Can any one of you help me the reason for the table getting refreshed. Do i need to pass any data.
    I am doing the following steps.
    1. Create Container,
    2. Create Tree Class object
    3. Generate the Field Catalog.
    4. Set table for first display  " With empty internal table
    5. Generate the Hierarchy
    6. Call the Method Frontend Update.
    Let me know if i had missed any steps in the process.
    Thank you,
    Regards,
    Swaroop Patri

    One reason for getting this error is using local defined tables for it_outtab parameter in the below code:
    To get rid of the dump, define two distinct output tables globally: one is an empty table which you will pass to the below method, other one is your real output table whose size increases dependently.
      CALL METHOD go_tree->set_table_for_first_display
          EXPORTING
            is_hierarchy_header = ls_hier_header
          CHANGING
            it_outtab           = gt_data_e "Empty table
            it_fieldcatalog     = gt_fcat_tree.

Maybe you are looking for