Navigation Example Tree ( How to fill it? )

Dear Gurus,
I would like to make a tree of company structure by using com.sap.pct.pdk.navigation.NavigationExample1 iView. I have two questions?
1. How can I put my own datas to fill the tree?
2. How can I change the title inside? (Navigation Component Example)
Do you have any better idea for solution?
Thanks:
Levente

Hi Levente,
why do you want to use the NavigationExample?! If you want to develop a tree to visualize a hierarchical structure, why not just using HTMLB Tree element?
Hope it helps
Detlev
PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

Similar Messages

  • How to fill or bind data using Value Node in Tree Node

    Hi Gurus,
    Can anybody help me on how to fill data or bind data using Value Node in Tree Node View. I know how to create Tree Node but not able to show value on the UI in Tree View.
    Can u please let if anybody has done it?
    Thanks in advance.
    Madhusudan

    continued...
    TRY.
              lv_child = me->node_factory->get_proxy(
                        iv_bo = lv_value_node
                        iv_parent_proxy = me
                        iv_proxy_type = 'ZL_CLASS_CN02' ).
              lv_child->is_leaf = 'X'.
              APPEND lv_child TO rt_children.
            CATCH cx_sy_move_cast_error cx_sy_ref_is_initial.
          ENDTRY.
      In the above code iv_bo , lv_value_node will be the actual object of the second node or leaf node here, which will have the same structure of parent node along with data. After/before this, you would need to build table and refresh in do-prepare_output of IMPL class.In the above code iv_bo , lv_value_node will be the actual object of the second node or leaf node here, which will have the same structure of parent node along with data. After/before this, you would need to buid table and refresh in do-prepare_output of IMPL class.
    ztyped_context->resultlist->build_table( ).
      IF ztyped_context->resultlist->node_tab IS INITIAL.
        ztyped_context->resultlist->refresh( ).
      ENDIF.
    Also the EH_ONEXPAND has to be implemented and event handled in DO_HANDLE_EVENT. But this expand event has to be delegated to context node directly as CL_BSP_WD_CONTEXT_NODE_TREE will already have the implementation.
    ztyped_context->resultlist->expand_node( lv_event->row_key ).
    Where in result list is the node ZL_CLASS_CN00.
    After typing the whole content , i found this blog :). There are few things i have written more that in the blog.  /people/poonam.assudani/blog/2009/06/24/create-a-tree-view-display-in-crm-web-ui
    Regards,
    Karthik

  • SharePoint 2013---How to convert current left Navigation into tree view

    Hi All,
    I want to convert current left navigation into tree view in SharePoint 2013. When we click on Modify Navigation and set headers and links; I need that should be convert into tree view. All headers should be expandable to thier links.
    I just want tree view on navigation headers and links. not for all site and subsites which we can enabled from site settings --> Modify All Site settings --> Tree view
    Please help me Master Page editing on Navigation Generation.. Thanks in advance!
    Regards,
    Anna

    Hi Anna,
    If you want to replace the Quick Launch part with the custom treeview web part in master page, you can comment out or remove the quick launch code block "<!--SPM:<SharePoint:SPNavigationManager id="QuickLaunchNavigationManager.....>....<>-->",
    then insert the custom web part snippet code in proper location in seattle master page, then all pages inheriting the seattle master page will have this web part.
    Note, please back up the master page before customizing the original master page for recovery.
    http://msdn.microsoft.com/en-us/library/office/jj862341(v=office.15).aspx
    http://www.sharepointpals.com/post/Add-snippets-in-Page-layout-using-design-manager
    Thanks,
    Daniel Yang
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] 
    Daniel Yang
    TechNet Community Support

  • How to fill a hashed table ?

    Hi,
    In my last thread i had asked about the ways of deleting the cube contents selectively using a job/FM and i was suggested this by one of you.
    CALL FUNCTION 'RSDRD_SEL_DELETION'
    EXPORTING
    I_DATATARGET = 'YOUR_CUBE'
    I_THX_SEL = L_THX_SEL
    I_AUTHORITY_CHECK = 'X'
    I_THRESHOLD = '1.0000E-01'
    I_MODE = 'C'
    I_NO_LOGGING = ''
    I_PARALLEL_DEGREE = 1
    I_NO_COMMIT = ''
    CHANGING
    C_T_MSG = L_T_MSG.
    Although the FM is the correct one the structure L_THX_SEL is a hashed table structure and i am not aware how to fill values into it. My requirement is to give a condition for the 0CALDAY info-object i.e 0CALDAY < 30 days. Please suggest me.
    Regadrs,
    Pramod M

    HI,
    Internal Tables
    Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.
    Data Type of an Internal Table
    The data type of an internal table is fully specified by its line type, key, and table type.
    Line Type
    The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the structure is a column in the internal table. However, the line type may also be elementary or another internal table.
    Key
    The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify whether the key should be UNIQUE or NON-UNIQUE. Internal tables with a unique key cannot contain duplicate entries. The uniqueness depends on the table access method.
    At tables with structured row type, the standard key is formed from all character-type columns of the internal table. If a table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty. At tables with non-structured row type, the standard key consists of the entire row. If the row type is also a table, an empty key is defined.
    The user-defined key can contain any columns of the internal table that are no internal table themselves, and do not contain internal tables. References are allowed as table keys. Internal tables with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember this, for example, if you intend to sort the table according to the key.
    Table type
    The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:
    Standard tables have an internal linear index. From a particular size upwards, the indexes of internal tables are administered as trees. In this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table. The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.
    Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the table index or the key. The response time for key access is logarithmically proportional to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique or non-unique. When you define the table, you must specify whether the key is to be UNIQUE or NON-UNIQUE. Standard tables and sorted tables are known generically as index tables.
    Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.
    Generic Internal Tables
    Unlike other local data types in programs, you do not have to specify the data type of an internal table fully. Instead, you can specify a generic construction, that is, the key or key and line type of an internal table data type may remain unspecified. You can use generic internal tables to specify the types of field symbols  and the interface parameters of procedures . You cannot use them to declare data objects.
    Internal Tables as Dynamic Data Objects
    Internal tables are always completely specified regarding row type, key and access type. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.
    Choosing a Table Type
    The table type (and particularly the access method) that you will use depends on how the typical internal table operations will be most frequently executed.
    Standard tables
    This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPENDstatement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option (BINARY) with key access, the response time is logarithmically proportional to the number of table entries.
    Sorted tables
    This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERTstatement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHEREcondition.
    Hashed tables
    This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.
    If help full please give me max Reward

  • How to fill the values in List Box?

    Hi Experts,
    Can anyone explain me how to fill the values in the List Box such that the value should be from the table?
    For Example : Fill the EmpID from table T1 into the ListBox?
    Thanks in Advance,
    Regards,
    Raghu

    hi,
    and u doing it through report means from se38 than here is code...
    DATA : BEGIN OF itab OCCURS 0,
            matnr LIKE mara-matnr,
           END OF itab.
    DATA : ok_code LIKE sy-ucomm.
    CALL SCREEN 0200.
    *&      Module  STATUS_0200  OUTPUT
          text
    MODULE status_0200 OUTPUT.
      SET PF-STATUS 'Z200'.
    ENDMODULE.                 " STATUS_0200  OUTPUT
    *&      Module  USER_COMMAND_0200  INPUT
          text
    MODULE user_command_0200 INPUT.
      CASE ok_code.
        WHEN 'BACK' OR 'UP' OR 'CANC'.
          LEAVE PROGRAM.
      ENDCASE.
    ENDMODULE.                 " USER_COMMAND_0200  INPUT
    *&      Module  mat_val  INPUT
          text
    MODULE mat_val INPUT.
      SELECT matnr FROM mara INTO CORRESPONDING FIELDS OF TABLE itab
        WHERE matnr BETWEEN '000000000000000101' AND '000000000000000109'.
        CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
          EXPORTING
            retfield               = 'MATNR'
           VALUE_ORG              = 'S'
          tables
            value_tab              = itab
        IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
    ENDMODULE.                 " mat_val  INPUT
    <b>And this is flow logic..</b>
    PROCESS BEFORE OUTPUT.
      MODULE status_0200.
    PROCESS AFTER INPUT.
      MODULE user_command_0200.
    PROCESS ON VALUE-REQUEST.
      FIELD itab-matnr MODULE mat_val.

  • How to Fill value in Input fields before displaying ADOBE FORM

    Hi to all,
    Please can anyone tell me how to fill the entry in ADOBE FORM before displaying?
    I have written a program to generate ADOBE FORM, but I need while displaying ADOBE FROM some input field should already be filled by value and can not be changed.
    Please can anyone tell me how to do that in program?
    Below is the program.
    DATA: fm_name           TYPE rs38l_fnam,
            fp_docparams      TYPE sfpdocparams,
            fp_outputparams   TYPE sfpoutputparams.
    Parameters: p_pdf_form_name type fname.
      fp_docparams-langu   = 'E'.
      fp_docparams-country = 'IN'.
      fp_outputparams-preview = 'X'.
      CALL FUNCTION 'FP_JOB_OPEN'
        CHANGING
          ie_outputparams = fp_outputparams
        EXCEPTIONS
          cancel          = 1
          usage_error     = 2
          system_error    = 3
          internal_error  = 4.
      CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
        EXPORTING
          i_name     = p_pdf_form_name
        IMPORTING
          e_funcname = fm_name.
      E_INTERFACE_TYPE           = E_INTERFACE_TYPE
      CALL FUNCTION fm_name
        EXPORTING
          /1bcdwb/docparams        = fp_docparams
      IMPORTING
        /1BCDWB/FORMOUTPUT       = fp_outputparams
        EXCEPTIONS
          usage_error           = 1
          system_error          = 2
          internal_error           = 3.
      CALL FUNCTION 'FP_JOB_CLOSE'
       IMPORTING
        E_RESULT             =
        EXCEPTIONS
          usage_error           = 1
          system_error          = 2
          internal_error        = 3
          OTHERS               = 4.
    I shall be thankful to you for this.
    Regards
    Pavneet Rana
    Edited by: pavneet rana on Jul 25, 2011 2:57 PM

    Hello,
    you need to provide the information via the interface, which you create for the Adobe form.
    And then pass this values via the following function module inside your generation report.
    CALL FUNCTION fm_name
    check standard report : FP_EXAMPLE_01 as an example!

  • How to fill internal table with selection screen field.

    Hi all,
    i am new to sap . pls tell me how to fill internal table with selection screen field.

    Hi,
    Please see the example below:-
    I have used both select-options and parameter on the selection-screen.
    Understand the same.
    * type declaration
    TYPES: BEGIN OF t_matnr,
            matnr TYPE matnr,
           END OF t_matnr,
           BEGIN OF t_vbeln,
             vbeln TYPE vbeln,
           END OF t_vbeln.
    * internal table declaration
    DATA : it_mara  TYPE STANDARD TABLE OF t_matnr,
           it_vbeln TYPE STANDARD TABLE OF t_vbeln.
    * workarea declaration
    DATA : wa_mara  TYPE t_matnr,
           wa_vbeln TYPE t_vbeln.
    * selection-screen field
    SELECTION-SCREEN: BEGIN OF BLOCK b1.
    PARAMETERS : p_matnr TYPE matnr.
    SELECT-OPTIONS : s_vbeln FOR wa_vbeln-vbeln.
    SELECTION-SCREEN: END OF BLOCK b1.
    START-OF-SELECTION.
    * I am adding parameter value to my internal table
      wa_mara-matnr = p_matnr.
      APPEND wa_mara TO it_mara.
    * I am adding select-options value to an internal table
      LOOP AT s_vbeln.
        wa_vbeln-vbeln =  s_vbeln-low.
        APPEND  wa_vbeln TO  it_vbeln.
      ENDLOOP.
    Regards,
    Ankur Parab

  • How to fill internal table dynamically

    Hi All,
       how to fill internal table dynamically.
    for example:
    begin of itab occurs 0,
    empid like pa0000-pernr,
    empname like pa0001-ename,
    grade(5),
    end of itab.
    now i want to append dynamically field itab-grade along with rest fields.
    is this possible?? if yes kindly let me know how to do that.
    Regards,
    Kiran I

    Hi kiran,
    To fill and create and internal table dynamically you can use this code.
    TYPE-POOLS: slis.
    DATA: it_fcat TYPE slis_t_fieldcat_alv,
          is_fcat LIKE LINE OF it_fcat.
    DATA: it_fieldcat TYPE lvc_t_fcat,
          is_fieldcat LIKE LINE OF it_fieldcat.
    DATA: new_table TYPE REF TO data.
    DATA: new_line  TYPE REF TO data.
    FIELD-SYMBOLS: <l_table> TYPE ANY TABLE,
                   <l_line>  TYPE ANY,
                   <l_field> TYPE ANY.
    is_fieldcat-fieldname = 'FIELD1'.
    is_fieldcat-ref_field = 'MATNR'.
    is_fieldcat-ref_table = 'MARA'.
    APPEND is_fieldcat TO it_fieldcat.
    is_fieldcat-fieldname = 'FIELD2'.
    is_fieldcat-ref_field = 'SPRPS'.
    is_fieldcat-ref_table = 'PA0001'.
    APPEND is_fieldcat TO it_fieldcat.
    is_fieldcat-fieldname = 'FIELD3'.
    is_fieldcat-ref_field = 'BEGDA'.
    is_fieldcat-ref_table = 'PA0002'.
    APPEND is_fieldcat TO it_fieldcat.
    Create a new Table
    CALL METHOD cl_alv_table_create=>create_dynamic_table
      EXPORTING
        it_fieldcatalog = it_fieldcat
      IMPORTING
        ep_table        = new_table.
    Create a new Line with the same structure of the table.
    ASSIGN new_table->* TO <l_table>.
    CREATE DATA new_line LIKE LINE OF <l_table>.
    ASSIGN new_line->* TO <l_line>.
    Test it...
    DO 40 times.
      ASSIGN COMPONENT 'FIELD1' OF STRUCTURE <l_line> TO <l_field>.
      <l_field> = '12345'.
      ASSIGN COMPONENT 'FIELD2' OF STRUCTURE <l_line> TO <l_field>.
      <l_field> = 'X'.
      ASSIGN COMPONENT 'FIELD3' OF STRUCTURE <l_line> TO <l_field>.
      <l_field> = '20030101'.
      INSERT <l_line> INTO TABLE <l_table>.
    ENDDO.
    LOOP AT <l_table> ASSIGNING <l_line>.
    ASSIGN COMPONENT 'field1' OF STRUCTURE <l_line> TO <l_field>.
      WRITE  / <l_line>.
    ENDLOOP.
    regards,
    Aashish Garg

  • In a tree how to increase length of node_key ?

    Hi All,
    While creating  a tree structure, how do we increase the size og the node_key?
    I want the node_key with the same length as MATNR (i.e. >12 characters)
    How to achieve this ?
    Regards,
    Ashish

    Hello Ashish
    I am not yet sure about how to fill the List Header column yet at least the sample report ZUS_SDN_LIST_TREE_MODEL_DEMO_1 gives you a flavour of how tree models work.
    *& Report  ZUS_SDN_LIST_TREE_MODEL_DEMO_1
    *& Thread: In a tree how to increase length of node_key ?
    *& <a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="1148884"></a>
    *& Flow logic of screen '0100' (contains no screen elements):
    **  PROCESS BEFORE OUTPUT.
    **    MODULE STATUS_0100.
    **  PROCESS AFTER INPUT.
    **    MODULE USER_COMMAND_0100.
    REPORT  zus_sdn_list_tree_model_demo_1.
    CLASS cl_gui_column_tree DEFINITION LOAD.
    CLASS cl_gui_cfw DEFINITION LOAD.
    TYPE-POOLS: abap, shlp.
    DATA: gt_node_table   TYPE treemlnota,
          gt_item_table   TYPE treemlitac.
    TYPES: BEGIN OF ty_s_key.
    TYPES: nkey       TYPE lvc_nkey.
    TYPES: parent_key TYPE lvc_nkey.
    TYPES: END OF ty_s_key.
    TYPES: BEGIN OF ty_s_outtab.
    INCLUDE TYPE knvv AS data.
    INCLUDE TYPE ty_s_key AS key.
    TYPES: END OF ty_s_outtab.
    TYPES: ty_t_outtab    TYPE STANDARD TABLE OF ty_s_outtab
                          WITH DEFAULT KEY.
    DATA: gt_outtab    TYPE ty_t_outtab.
    DATA:
      gd_okcode        TYPE ui_func,
      gd_repid         TYPE syst-repid,
      gt_fcat          TYPE lvc_t_fcat,
      gs_layout        TYPE lvc_s_layo,
      gs_variant       TYPE disvariant,
      go_docking       TYPE REF TO cl_gui_docking_container,
      go_listtree      TYPE REF TO cl_list_tree_model.
    *       CLASS lcl_eventhandler DEFINITION
    CLASS lcl_eventhandler DEFINITION.
      PUBLIC SECTION.
        CLASS-METHODS:
        handle_item_double_click
          FOR EVENT item_double_click OF cl_list_tree_model
          IMPORTING node_key
                    item_name,
        handle_checkbox_change
          FOR EVENT checkbox_change OF cl_list_tree_model
          IMPORTING node_key
                    item_name
                    checked.
    ENDCLASS.                    "lcl_eventhandler DEFINITION
    *       CLASS lcl_eventhandler IMPLEMENTATION
    CLASS lcl_eventhandler IMPLEMENTATION.
      METHOD handle_item_double_click.
        MESSAGE 'Event=Double-Click on Item' TYPE 'I'.
        CALL TRANSACTION 'VA03'.
      ENDMETHOD.                    "handle_item_double_click
      METHOD handle_checkbox_change.
        DATA: ls_outtab     TYPE ty_s_outtab.
        BREAK-POINT.
    **    IF ( fieldname = 'LOEVM' ).
    **      CALL METHOD go_tree->get_outtab_line
    **        EXPORTING
    **          i_node_key     = node_key
    **        IMPORTING
    **          e_outtab_line  = ls_outtab
    ***          e_node_text    =
    ***          et_item_layout =
    ***          es_node_layout =
    **        EXCEPTIONS
    **          node_not_found = 1
    **          OTHERS         = 2.
    **      IF sy-subrc <> 0.
    ***       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    ***                  WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    **      ENDIF.
    **      ls_outtab-loevm = checked.
    **      MODIFY gt_outtab FROM ls_outtab
    **        TRANSPORTING loevm
    **        WHERE ( nkey = node_key ).
    **    ENDIF.
        " Trigger PAI
        CALL METHOD cl_gui_cfw=>set_new_ok_code
          EXPORTING
            new_code = 'REFRESH'
    *        IMPORTING
    *          rc       =
      ENDMETHOD.                    "handle_checkbox_change
    ENDCLASS.                    "lcl_eventhandler IMPLEMENTATION
    START-OF-SELECTION.
      PERFORM init_controls.
      gd_repid = syst-repid.
      CALL METHOD go_docking->link
        EXPORTING
          repid                       = gd_repid
          dynnr                       = '0100'
    *      container                   =
        EXCEPTIONS
          cntl_error                  = 1
          cntl_system_error           = 2
          lifetime_dynpro_dynpro_link = 3
          OTHERS                      = 4.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      CALL SCREEN '0100'.
    ** NOTE: no elements on screen
    **  PROCESS BEFORE OUTPUT.
    **    MODULE STATUS_0100.
    **  PROCESS AFTER INPUT.
    **    MODULE USER_COMMAND_0100.
    END-OF-SELECTION.
    *&      Module  STATUS_0100  OUTPUT
    *       text
    MODULE status_0100 OUTPUT.
      SET PF-STATUS 'STATUS_0100'.
    *  SET TITLEBAR 'xxx'.
    ENDMODULE.                 " STATUS_0100  OUTPUT
    *&      Module  USER_COMMAND_0100  INPUT
    *       text
    MODULE user_command_0100 INPUT.
      TRANSLATE gd_okcode TO UPPER CASE.
      CASE gd_okcode.
        WHEN 'BACK'  OR
             'EXIT'  OR
             'CANC'.
          SET SCREEN 0. LEAVE SCREEN.
        WHEN 'REFRESH'.
    **      CALL METHOD go_tree->update_calculations
    ***        EXPORTING
    ***          no_frontend_update =
        WHEN 'SELECTED_NODES'.
          PERFORM get_selected_nodes.
        WHEN 'DISPLAY'.
          PERFORM display.
        WHEN OTHERS.
      ENDCASE.
      CLEAR: gd_okcode.
    ENDMODULE.                 " USER_COMMAND_0100  INPUT
    *&      Form  init_controls
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM init_controls .
    * define local data
      DATA: ls_hierarchy_header   TYPE treemhhdr,
            ls_list_header        TYPE treemlhdr.
    * Create docking container
      CREATE OBJECT go_docking
        EXPORTING
          parent = cl_gui_container=>screen0
          ratio  = 90
        EXCEPTIONS
          OTHERS = 6.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      ls_hierarchy_header-heading = 'Hierarchy Column'.
      ls_hierarchy_header-width   = 70.
      ls_list_header-heading = 'List Column'.
    * create tree control
      CREATE OBJECT go_listtree
        EXPORTING
          node_selection_mode         = cl_gui_column_tree=>node_sel_mode_single
    *      hide_selection              =
          item_selection              = 'X'
          with_headers                = 'X'
          hierarchy_header            = ls_hierarchy_header
          list_header                 = ls_list_header
        EXCEPTIONS
          illegal_node_selection_mode = 1
          OTHERS                      = 2.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    **  PERFORM add_nodes_and_items.
      CALL METHOD go_listtree->create_tree_control
        EXPORTING
    *      lifetime                     =
          parent                       = go_docking
    *      shellstyle                   =
    *    IMPORTING
    *      control                      =
        EXCEPTIONS
          lifetime_error               = 1
          cntl_system_error            = 2
          create_error                 = 3
          failed                       = 4
          tree_control_already_created = 5
          OTHERS                       = 6.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * create hierarchy
      PERFORM create_hierarchy.
    * register events
      PERFORM register_events.
    ENDFORM.                    " init_controls
    *&      Form  BUILD_FIELDCATALOG
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM build_fieldcatalog .
      DATA: ls_fcat   TYPE lvc_s_fcat.
      REFRESH: gt_fcat.
      CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
        EXPORTING
    *     I_BUFFER_ACTIVE              =
          i_structure_name             = 'KNVV'
    *     I_CLIENT_NEVER_DISPLAY       = 'X'
          i_bypassing_buffer           = 'X'
    *     I_INTERNAL_TABNAME           =
        CHANGING
          ct_fieldcat                  = gt_fcat
        EXCEPTIONS
          inconsistent_interface       = 1
          program_error                = 2
          OTHERS                       = 3.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      DELETE gt_fcat FROM 10.
      ls_fcat-tech = 'X'.
      MODIFY gt_fcat FROM ls_fcat
        TRANSPORTING tech
        WHERE ( key = 'X' ).
      ls_fcat-edit = 'X'.
      MODIFY gt_fcat FROM ls_fcat
        TRANSPORTING edit
        WHERE ( key NE 'X' ).
      READ TABLE gt_fcat INTO ls_fcat
           WITH KEY fieldname = 'LOEVM'.
      IF ( syst-subrc = 0 ).
        ls_fcat-checkbox = 'X'.
        ls_fcat-edit     = 'X'.
    **    ls_fcat-hotspot  = 'X'.
        MODIFY gt_fcat FROM ls_fcat INDEX syst-tabix.
      ENDIF.
      READ TABLE gt_fcat INTO ls_fcat
           WITH KEY fieldname = 'ERNAM'.
      IF ( syst-subrc = 0 ).
        ls_fcat-hotspot  = 'X'.
        MODIFY gt_fcat FROM ls_fcat INDEX syst-tabix.
      ENDIF.
    ENDFORM.                    " BUILD_FIELDCATALOG
    *&      Form  SET_LAYOUT_AND_VARIANT
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM set_layout_and_variant .
      CLEAR: gs_layout,
             gs_variant.
      gs_variant-report = syst-repid.
      gs_variant-handle = 'TREE'.
    ENDFORM.                    " SET_LAYOUT_AND_VARIANT
    *&      Form  create_hierarchy
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM create_hierarchy .
      DATA: ls_knvv     TYPE sflight,
            ld_idx      TYPE i,
            ls_outtab   TYPE ty_s_outtab,
            lt_outtab   TYPE ty_t_outtab.
    * get data
      SELECT * FROM knvv INTO CORRESPONDING FIELDS OF TABLE lt_outtab
                            UP TO 20 ROWS .                 "#EC CI_NOWHERE
      SORT lt_outtab BY kunnr vkorg.
    * add data to tree
      DATA: ld_root_key  TYPE tm_nodekey,
            ld_kunnr_key TYPE tm_nodekey,
            ld_vkorg_key TYPE tm_nodekey,
            ld_last_key  TYPE tm_nodekey.
      ld_idx = 0.
      LOOP AT lt_outtab INTO ls_outtab.
        AT FIRST.
          PERFORM add_root_line USING    ls_outtab-data
                                  CHANGING ld_root_key.
          ADD 1 TO ld_idx.
          ls_outtab-nkey       = ld_root_key.
          ls_outtab-parent_key = space.
          MODIFY gt_outtab FROM ls_outtab INDEX ld_idx
            TRANSPORTING key.
        ENDAT.
        ON CHANGE OF ls_outtab-kunnr.
          PERFORM add_customer_line USING    ls_outtab-data
                                             ld_root_key
                                  CHANGING ld_kunnr_key.
          ADD 1 TO ld_idx.
          ls_outtab-nkey       = ld_kunnr_key.
          ls_outtab-parent_key = ld_root_key.
          MODIFY gt_outtab FROM ls_outtab INDEX ld_idx
            TRANSPORTING key.
        ENDON.
        ON CHANGE OF ls_outtab-vkorg.
          PERFORM add_salesorg_line USING    ls_outtab-data
                                             ld_kunnr_key
                                  CHANGING ld_vkorg_key.
          ADD 1 TO ld_idx.
          ls_outtab-nkey       = ld_vkorg_key.
          ls_outtab-parent_key = ld_kunnr_key.
          MODIFY gt_outtab FROM ls_outtab INDEX ld_idx
            TRANSPORTING key.
        ENDON.
        PERFORM add_complete_line USING  ls_outtab-data
                                         ld_vkorg_key
                                CHANGING ld_last_key.
        ADD 1 TO ld_idx.
        ls_outtab-nkey       = ld_last_key.
        ls_outtab-parent_key = ld_vkorg_key.
        MODIFY gt_outtab FROM ls_outtab INDEX ld_idx
          TRANSPORTING key.
      ENDLOOP.
    * calculate totals
    **  CALL METHOD go_tree->update_calculations.
    * this method must be called to send the data to the frontend
    **  CALL METHOD go_tree->frontend_update.
    ENDFORM.                    " create_hierarchy
    *&      Form  add_customer_line
    *       add hierarchy-level 1 to tree
    *      -->P_LS_SFLIGHT  sflight
    *      -->P_RELEATKEY   relatkey
    *     <-->p_node_key    new node-key
    FORM add_root_line USING     us_data TYPE ty_s_outtab-data
                                 ud_relat_key TYPE tm_nodekey
                         CHANGING  cd_node_key TYPE tm_nodekey.
      DATA: l_node_text TYPE lvc_value,
            ls_data TYPE ty_s_outtab-data.
    * set item-layout
      DATA: lt_item_table  TYPE treemlitab,
            ls_item        TYPE treemlitem.
    **  ls_item-t_image = '@3Q@'.  " icon_overview
      ls_item-item_name = '1'.
      ls_item-class   = cl_list_tree_model=>item_class_text.
      ls_item-style   = cl_list_tree_model=>style_intensifd_critical.
      ls_item-text = 'Overview: Sales Areas'.
      ls_item-length = 25.
      APPEND ls_item TO lt_item_table.
      cd_node_key = 'ROOT'.
    * add node
      CALL METHOD go_listtree->add_node
        EXPORTING
          node_key                = cd_node_key
    *     relative_node_key       =
    *      relationship            =
          isfolder                = 'X'
    *      hidden                  =
    *      disabled                =
    *      style                   =
    *      no_branch               =
    *      expander                =
    *      image                   =
    *      expanded_image          =
    *      drag_drop_id            =
    *      last_hitem              =
    *      user_object             =
    *      items_incomplete        =
          item_table              = lt_item_table
        EXCEPTIONS
          node_key_exists         = 1
          node_key_empty          = 2
          illegal_relationship    = 3
          relative_node_not_found = 4
          error_in_item_table     = 5
          OTHERS                  = 6.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                               " add_root_line
    *&      Form  add_customer_line
    *       add hierarchy-level 1 to tree
    *      -->P_LS_SFLIGHT  sflight
    *      -->P_RELEATKEY   relatkey
    *     <-->p_node_key    new node-key
    FORM add_customer_line USING     us_data TYPE ty_s_outtab-data
                                     ud_relat_key TYPE tm_nodekey
                         CHANGING  cd_node_key TYPE tm_nodekey.
      DATA: l_node_text TYPE lvc_value,
            ls_data TYPE ty_s_outtab-data.
    * set item-layout
      DATA: lt_item_table  TYPE treemlitab,
            ls_item        TYPE treemlitem.
      ls_item-t_image = '@A0@'.  " icon_customer
      ls_item-item_name = '1'.
      ls_item-class   = cl_list_tree_model=>item_class_text.
      ls_item-style   = cl_list_tree_model=>style_intensifd_critical.
      ls_item-text = us_data-kunnr.
      ls_item-length = 15.
      APPEND ls_item TO lt_item_table.
      cd_node_key = us_data-kunnr.
    * add node
      CALL METHOD go_listtree->add_node
        EXPORTING
          node_key                = cd_node_key
          relative_node_key       = ud_relat_key
          relationship            = cl_list_tree_model=>relat_last_child
          isfolder                = 'X'
    *      hidden                  =
    *      disabled                =
    *      style                   =
    *      no_branch               =
    *      expander                =
    *      image                   =
    *      expanded_image          =
    *      drag_drop_id            =
    *      last_hitem              =
    *      user_object             =
    *      items_incomplete        =
          item_table              = lt_item_table
        EXCEPTIONS
          node_key_exists         = 1
          node_key_empty          = 2
          illegal_relationship    = 3
          relative_node_not_found = 4
          error_in_item_table     = 5
          OTHERS                  = 6.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                               " add_customer_line
    *&      Form  add_salesorg_line
    *       add hierarchy-level 1 to tree
    *      -->P_LS_SFLIGHT  sflight
    *      -->P_RELEATKEY   relatkey
    *     <-->p_node_key    new node-key
    FORM add_salesorg_line USING     us_data TYPE ty_s_outtab-data
                                     ud_relat_key TYPE tm_nodekey
                         CHANGING  cd_node_key TYPE tm_nodekey.
      DATA: l_node_text TYPE lvc_value,
            ls_data TYPE ty_s_outtab-data.
    * set item-layout
      DATA: lt_item_table  TYPE treemlitab,
            ls_item        TYPE treemlitem.
    **  ls_item-t_image = '@A0@'.  " icon_customer
      ls_item-item_name = '1'.
      ls_item-class   = cl_list_tree_model=>item_class_text.
    **  ls_item-style   = cl_list_tree_model=>style_intensifd_critical.
      CONCATENATE 'Sales Organisation:' us_data-vkorg
        INTO ls_item-text
        SEPARATED BY space.
      ls_item-length = 25.
      APPEND ls_item TO lt_item_table.
      CLEAR: ls_item.
      ls_item-item_name = '2'.
      ls_item-class   = cl_list_tree_model=>item_class_text.
      ls_item-text = us_data-vtweg.
      ls_item-length = 5.
      APPEND ls_item TO lt_item_table.
      CLEAR: ls_item.
      ls_item-item_name = '3'.
      ls_item-class   = cl_list_tree_model=>item_class_text.
      ls_item-text = us_data-spart.
      ls_item-length = 3.
      APPEND ls_item TO lt_item_table.
      CONCATENATE ud_relat_key us_data-vkorg
        INTO cd_node_key
        SEPARATED BY ' : '.                                     " > 12 char
    * add node
      CALL METHOD go_listtree->add_node
        EXPORTING
          node_key                = cd_node_key
          relative_node_key       = ud_relat_key
          relationship            = cl_list_tree_model=>relat_last_child
          isfolder                = 'X'
    *      hidden                  =
    *      disabled                =
    *      style                   =
    *      no_branch               =
    *      expander                =
    *      image                   =
    *      expanded_image          =
    *      drag_drop_id            =
    *      last_hitem              =
    *      user_object             =
    *      items_incomplete        =
          item_table              = lt_item_table
        EXCEPTIONS
          node_key_exists         = 1
          node_key_empty          = 2
          illegal_relationship    = 3
          relative_node_not_found = 4
          error_in_item_table     = 5
          OTHERS                  = 6.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                               " add_salesorg_line
    *&      Form  add_cmplete_line
    *       add hierarchy-level 3 to tree
    *      -->P_LS_SFLIGHT  sflight
    *      -->P_RELEATKEY   relatkey
    *     <-->p_node_key    new node-key
    FORM add_complete_line USING     us_data TYPE ty_s_outtab-data
                                     ud_relat_key TYPE tm_nodekey
                         CHANGING  cd_node_key TYPE tm_nodekey.
    **  DATA: l_node_text TYPE lvc_value,
    **        ls_data TYPE ty_s_outtab-data.
    *** set item-layout
    **  DATA: lt_item_table  TYPE treemlitac,
    **        ls_item        TYPE treemliten.
    **  ls_item-node_key = ud_relat_key.
    ****  ls_item-t_image = '@A0@'.  " icon_customer
    **  ls_item-item_name = '3'.
    **  ls_item-class   = cl_list_tree_model=>item_class_text.
    ****  ls_item-style   = cl_list_tree_model=>style_intensifd_critical.
    **  CALL METHOD cl_abap_container_utilities=>fill_container_c
    **    EXPORTING
    **      im_value               = us_data
    **    IMPORTING
    **      ex_container           = ls_item-text
    **    EXCEPTIONS
    **      illegal_parameter_type = 1
    **      others                 = 2.
    **  IF sy-subrc <> 0.
    ***   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    ***              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    **  ENDIF.
    **  ls_item-length = 100.
    **  APPEND ls_item TO lt_item_table.
    **  CALL METHOD go_listtree->add_items
    **    EXPORTING
    **      item_table          = lt_item_table
    **    EXCEPTIONS
    **      error_in_item_table = 1
    **      OTHERS              = 2.
    **  IF sy-subrc <> 0.
    ***   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    ***              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    **  ENDIF.
    ENDFORM.                               " add_complete_line
    *&      Form  register_events
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM register_events.
    * define the events which will be passed to the backend
      DATA: lt_events TYPE cntl_simple_events,
            l_event TYPE cntl_simple_event.
    * define the events which will be passed to the backend
    *  l_event-eventid = cl_list_tree_model=>eventid_expand_no_children.
    *  APPEND l_event TO lt_events.
      l_event-eventid = cl_list_tree_model=>eventid_checkbox_change.
      APPEND l_event TO lt_events.
    **  l_event-eventid = cl_gui_column_tree=>eventid_header_context_men_req.
    **  APPEND l_event TO lt_events.
    **  l_event-eventid = cl_gui_column_tree=>eventid_node_context_menu_req.
    **  APPEND l_event TO lt_events.
    **  l_event-eventid = cl_gui_column_tree=>eventid_item_context_menu_req.
    **  APPEND l_event TO lt_events.
    **  l_event-eventid = cl_gui_column_tree=>eventid_header_click.
    **  APPEND l_event TO lt_events.
    **  l_event-eventid = cl_gui_column_tree=>eventid_item_keypress.
    **  APPEND l_event TO lt_events.
      l_event-eventid = cl_list_tree_model=>eventid_item_double_click.
      APPEND l_event TO lt_events.
      CALL METHOD go_listtree->set_registered_events
        EXPORTING
          events                    = lt_events
        EXCEPTIONS
          illegal_event_combination = 1
          unknown_event             = 2
          OTHERS                    = 3.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * set Handler
      SET HANDLER:
        lcl_eventhandler=>handle_item_double_click FOR go_listtree,
        lcl_eventhandler=>handle_checkbox_change   FOR go_listtree.
    ENDFORM.                               " register_events
    *&      Form  DISPLAY
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM display .
      DATA: ls_outtab   TYPE ty_s_outtab,
            ls_line     TYPE ty_s_outtab,
            ld_msg      TYPE bapi_msg.
      BREAK-POINT.
      LOOP AT gt_outtab INTO ls_outtab
              WHERE ( loevm = 'X' ).
        CONCATENATE 'Checkbox:'
                    ls_outtab-kunnr
                    ls_outtab-vkorg
                    ls_outtab-vtweg
                    ls_outtab-spart
                    ls_outtab-loevm
          INTO ld_msg SEPARATED BY space.
        MESSAGE ld_msg TYPE 'I'.
      ENDLOOP.
      IF ( syst-subrc NE 0 ).
        MESSAGE 'No marked checkboxes found' TYPE 'I'.
      ENDIF.
      PERFORM get_selected_nodes.
    ENDFORM.                    " DISPLAY
    *&      Form  GET_SELECTED_NODES
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM get_selected_nodes.
    * define local data
      DATA: ld_msg        TYPE bapi_msg,
            lt_nodes      TYPE lvc_t_nkey,
            ls_outtab     TYPE ty_s_outtab,
            ld_nkey       TYPE lvc_nkey,
            lt_items      TYPE lvc_t_layi,
            ls_item       TYPE lvc_s_layi.
    **  CALL METHOD go_tree->get_selected_nodes
    **    CHANGING
    **      ct_selected_nodes = lt_nodes
    **    EXCEPTIONS
    **      cntl_system_error = 1
    **      dp_error          = 2
    **      failed            = 3
    **      OTHERS            = 4.
    **  IF sy-subrc <> 0.
    ***   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    ***              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    **  ENDIF.
    **  CHECK ( lt_nodes IS NOT INITIAL ).
    **  BREAK-POINT.
    **  LOOP AT lt_nodes INTO ld_nkey.
    **    CALL METHOD go_tree->get_outtab_line
    **      EXPORTING
    **        i_node_key     = ld_nkey
    **      IMPORTING
    **        e_outtab_line  = ls_outtab-data
    ***        e_node_text    =
    **        et_item_layout = lt_items
    ***        es_node_layout =
    **      EXCEPTIONS
    **        node_not_found = 1
    **        OTHERS         = 2.
    **    IF sy-subrc <> 0.
    ***     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    ***                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    **    ENDIF.
    **    LOOP AT lt_items INTO ls_item
    **                     WHERE ( chosen = 'X' ).
    **      CONCATENATE 'Item:'
    **                  ls_outtab-kunnr
    **                  ls_outtab-vkorg
    **                  ls_outtab-vtweg
    **                  ls_outtab-spart
    **                  ls_outtab-loevm
    **        INTO ld_msg SEPARATED BY space.
    **      MESSAGE ld_msg TYPE 'I'.
    **    ENDLOOP.
    **  ENDLOOP.
    ENDFORM.                    " GET_SELECTED_NODES
    Regards
      Uwe

  • How to fill zeros in data

    Hi
    How to fill zeros into data?
    For example, from "123" to "123000"
    I tried to use to_char (data, 999000) but it doesnt work. Does anyone know how to do it in SQL?

    Maybe this will help...
    -- This is just to test my "conversion" logic...
    DECLARE
      v_num  NUMBER := 123;
    BEGIN
      v_num := RPAD(TO_CHAR(v_num), 6, '0');
      dbms_output.put_line(v_num);
    END;
    -- Put the "conversion" logic into a SQL statement
    SELECT RPAD(TO_CHAR(number_column), 6, '0')
      FROM my_table;Dan

  • Navigation or tree structure is possible Adobe Interactive?..

    Hi,
    Navigation or tree structure is possible is Adobe Interactive form?.
    Like
    Header
    >   ( When they navigate this arrow head, there is some record.. When you expand there may be record with which give again    navigation)
    > A
       B
       C
    >
    >
    Is it possible?
    Thanks
    GJ

    Hello again,
    of course that is possible. But there is not standard component for this. Build you can build your own and add it into your LCD library as a custom field/ object. In case you didn´t read my blog about how to do that, check it here: /people/otto.gold/blog/2010/01/12/adobe-forms-about-the-custom-components
    Back to the tree control:
    - lets create a subform which will be the root for the component
    - inside the subform (which has direction top to bottom with flowed content) create a header (you can create this as a static text or as a text field or something)
    - again inside the subform, create another subform (X2), this will hold all the content of the header node, what means: when clicking on the header node, all this will dissappear.
    - inside the subform X2 you can create as many sub-root as you wish and follow all that once more - recursively
    - now you need to write a script into the header field/ text onclick event. This script will check if the X2 subform is present (presence = visible) and if it is, it will set the presence to hidden and vice versa...
    Regards Otto

  • How to add fields to already loaded cube or dso and how to fill records in

    how to add fields to already loaded cube or dso and how to fill  it.can any one tell me the critical issues in data loading process..?

    This is sensitive task with regards to large volumes of data in infoproviders.
    The issue is to reload of data in case of adjusted structures of infoproviders.
    Indeed there are some tricks. See following:
    http://weblogs.sdn.sap.com/cs/blank/view/wlg/19300
    https://service.sap.com/sap/support/notes/1287382

  • How to fill internal table with no data in debugging mode

    Hi all,
             I modified one existing program.Now I want to test it.I am not given test data.So in the middle of my debugging, I found that one internal table with no data.My problem is how to fill that internal table with few records in that debugging mode just as we change contents in debugging mode.If I want to proceed further means that internal table must have some records.
    Please I dont know how to create test data so I am trying to create values temporarily in debugging mode only.
    Thanks,
    Balaji

    Hi,
    In the debugging do the following..
    Click the Table button..
    Double click on the internal table name..
    Then in the bottom of the screen you will get the buttons like CHANGE, INSERT, APPEND, DELETE..
    Use the APPEND button to insert records to the internal table..
    Thanks,
    Naren

  • How to fill dropdown list in Adobe form

    Hi Experts,
                  I am new to adobe form.Please tell me ,how to fill drop down list in adobe form?
    Thanks,
    Hans

    Hello Arafat,
    I am using a drop down list in Adobe Interactive Form for Web Dynpro ABAP.
    The form is of ZCI type layout and the form interface is of XML schema-based interface type and the XML schema source is set to "Generated".
    I have included the following code in WDDOINIT method of the view:
    data: handle1 type ref to if_wd_context_node,
    begin of zstruct,
    zktokd type kna1-ktokd,
    end of zstruct,
    zitab type table of zsttxecr.
    handle1 = wd_context->get_child_node( name = 'DATA.NODE1' ).
    select ktokd from kna1 into corresponding fields of zstruct.
    append zstruct to zitab.
    endselect.
    handle1->bind_table( new_items = zitab ).
    In the Adobe Form Designer, i have binded the node NODE1 to the enumerated drop down list from native web dynpro library. Still the drop down box is not getting populated.
    Please let me know what is missing.
    Thanks and Regards.

  • Looking for a simple example of how to query all the accounts

    I'm new to the web service model in oracle crm and have been trying to just get a list of the accounts in the system. I generated a .cs class from the account wsdl and added it to my asp.net project. I'm able to get a handle on the account class but not sure the right syntax to make a call out.. As a fyi - i also have been able to login thru the service and obtain a session id.. so I'm that far..
    Are they any existing code examples on how to query this? This is what I have so far but i throws an exception -
    Account act = new Account();
    act.Url = "https://"+dbcon.serverName+"/Services/Integration;jsessionid="+ sID;
    AccountWS_AccountQueryPage_Input qbe = new AccountWS_AccountQueryPage_Input();
    AccountWS_AccountQueryPage_Output qRet;
    qbe.ListOfAccount = new Account1[1];
    qbe.ListOfAccount[0] = new Account1();
    qbe.PageSize = "20";
    qbe.StartRowNum = "0";
    qbe.ListOfAccount[0].AccountId = "";
    qbe.ListOfAccount[0].Description = "";
    //act.CookieContainer = .... is this line needed?
    qRet = act.AccountQueryPage(qbe);
    return qRet.ToString();
    Thanks in advance for your help - Todd
    Edited by: user11139473 on May 6, 2009 6:33 PM

    Hi,
    I am doing the same thing but I am not sure what is Account1 in your case. Can you show me the implementation of Account1 class?
    Account act = new Account();
    act.Url = "https://"dbcon.serverName"/Services/Integration;jsessionid="+ sID;
    AccountWS_AccountQueryPage_Input qbe = new AccountWS_AccountQueryPage_Input();
    AccountWS_AccountQueryPage_Output qRet;
    qbe.ListOfAccount = new Account1[1]; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< qbe.ListOfAccount = new ListOfAccountQuery();
    qbe.ListOfAccount[0] = new Account1(); <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    qbe.PageSize = "20";
    qbe.StartRowNum = "0";
    qbe.ListOfAccount[0].AccountId = ""; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    qbe.ListOfAccount[0].Description = ""; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
    //act.CookieContainer = .... is this line needed?
    qRet = act.AccountQueryPage(qbe);
    return qRet.ToString();
    On the right is my line of code. The ListOfAccount member of AccountQueryPage_Input has datatype ListOfAccountQuery. In my case, a NULL is returned after the call.
    Did you code work in the end?
    Thanks

Maybe you are looking for

  • Saving Files from Word 2010 into SharePoint 2010 document library deployed as a sandbox solution gives "Web page no longer exist" Error 410

    Created a new SharePoint 2010 List Definition project, Sandbox deployment option. List Definition type: Documents Library. When attempting to save into the document library from Microsoft Word 2010 I get "The webpage no longer exists" error in the Fi

  • Graphics between windows 8 and 8.1

    Hi guys i am having a pc with two os xp and 8 . In xp my graphics memory is 128 mb and 8 my graphics is 830 mb if i am update 8.1 means what about my graphics memory ? Will it increase or not ?

  • Search Help with Structure Display

    Hi, I want to create a search help which should display my output in the structure format base on the different levels. I have already written a test program which display all the values in proper structure format. But I wanna do the same in the sear

  • Can display image from PixGrabber

    hi i try to grab pixels from an image to an array , biuld it as a new image object and draw it to the screen . i test that the array get the values and it does , and i dont recieve any exception. it just problem with displaing the image here is the c

  • Limited options for VGA display

    When I connect my new intel MBP to a monitor it does not give me the resolution options to fill the screen fully. On my older G4 Mini Mac, and an earlier model intel MBP (running 10.4) I was able to set the resolution to 1440 by 900 and it would give