Hierarchy used in "People in Hierarchy" screen (Manager Actions)

Hi All
Which hierarchy is used in "People in Hierarchy" screen (Manager Actions)
I tried the following.
Create a position hierarchy and created a security profile as follows
View Employees - Restricted
View CWK - Restricted
View Applicants - Restricted
View Contacts - Restricted
View Candidates - All
Organization Tab
Security Type: View All Organizations (no security) -- not adding any thing
Positions
Position Hierarchy : Test Position Hierarchy (Name of hierarchy)
Radio button checked for "Use the User's assignment(s) as the top position.
Checked boxed checked for "Include Top Position"
Rest of the tabs are blank.
Attached this profile to the responsibility Manager Self Service through which I am accessing Manager Actions Function.
When I go to Manager Actions screen I found that both supervisory AND position hierarchy are applied. If a person is in position hierarchy and supervisory hierarchy only then it will get displayed there.
Is it possible that I can use only position hierarchy at that place.
I am on Apps R11i, Family Pack K,
Thanks
Gaurav

Hi Gaurav,
It depends on the responsibilities assigned to employee. That means
If an employee has
"Manager Self Service" with profile "Position Hierarchy" and "HRMS Manager" with profile "Supervisor Hierarchy", then both will be applied.
So, check and make sure that only one security profile is available at any point of time.

Similar Messages

Unable to see any people in people in hierarchy on MSS appraisal

Hi,
Can someone advice how to debug this issue, if one of the manager is unable to see to see any people in people in hierarchy on Manager Self Service appraisal screen. I checked all these employee has this manager as their supervisor in assignment table.
Please advice.
Regards,
AJ

You need to checked whether respective plan is published for these employee and Manager also.
Functionally you can checked with using Plan Moniter using "Performance Management Plan" Function.
Technically you can checked PER_APPRAISALS table whether corresponsding records has been created for respecitve employee/manager for that plan.
Thanks

Upload hierarchy using flatfile

Hi,
I need to upload the HR hierarchy from PeopleSoft. PeopleSoft delivers the hierarchy as a flatfile, but not in the BW structure.
The file is delivered as follows:
Level1              Level2             Level3             Level4              Level5
NCC_002100   NCC_002101   NCC_002102   NCC_002103   NCC_002104
NCC_002100   NCC_002101   NCC_002102   NCC_002103   NCC_002105
NCC_002100   NCC_002200   NCC_002202   NCC_002203   NCC_002204
NCC_002100   NCC_002200   NCC_002210   NCC_002211   NCC_002212
NCC_002100   NCC_002200   NCC_002210   NCC_002211   NCC_002213
NCC_002100   NCC_002300   NCC_002310   NCC_002311   NCC_002312
How can I get this into the right BW structure for a Hierarchy upload.
Thanks.
Regards,
Paul

Hello,
Please go through the following links : http://help.sap.com/saphelp_nw70ehp1/helpdata/en/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm http://help.sap.com/saphelp_nw70/helpdata/en/b0/ab8e3cb4340b14e10000000a114084/content.htm Pls refer the following link, it will explain step by step with screen. /people/prakash.bagali/blog/2006/02/07/hierarchy-upload-from-flat-files Procedure to create Hierarchies: 1. In the Data Warehousing Workbench under Modeling, choose the InfoObject tree. 2. If you have assigned the hierarchy basic characteristic to an InfoObject catalog, select the corresponding InfoObject catalog for an InfoArea. If the hierarchy basic characteristic does not belong to an InfoObject catalog, choose the InfoArea Non-Assigned Nodes and the InfoObject Catalog Non-Assigned Characteristics. 3. Select the characteristic for which you want to create a hierarchy and choose Create Hierarchy from the context menu. The Create Hierarchy dialog box appears. The InfoObject name appears by default. 4. Enter a hierarchy name and description (short, medium, long). Other fields may be displayed, depending on which hierarchy properties were selected for the hierarchy basic characteristics Fields used to enter the Validity (valid to, valid from) for the hierarchy property Total Hierarchy Time-Dependent Fields used to specify the Hierarchy Version for the hierarchy property Hierarchies Version-Dependent. 5. Confirm your entries. The Maintain Hierarchy screen appears. You can define the structure of a hierarchy here. 6. To create a hierarchy node, you first need to choose an insertion mode: Insert as First Child or Insert As Next Neighbor (see Hierarchy Editing Functions). 7. Choose the type of node you want to create: Text Node, Characteristic Node, or Interval (see Hierarchy Nodes) 8. Repeat this procedure until the hierarchy structure has been set. For more information, see Modeling Nodes and Leaves. A hierarchy can contain 50,000-100,000 leaves at most. If your hierarchy is larger, you should insert a level that is used as a navigation attribute or preferably as a separate characteristic in the dimension table. 9. You can use Level Maintenance and Hierarchy Attributes to set how the hierarchy is to be displayed and processed in reporting (see Level Maintenance and Hierarchy Attributes). 10. Save the hierarchy. 11. Activate the hierarchy. See Editing Hierarchies. For more info http://help.sap.com/saphelp_nw70/helpdata/EN/80/1a6736e07211d2acb80000e829fbfe/content.htm http://help.sap.com/saphelp_nw70/helpdata/EN/e6/951d102a6c11d5b2e40050da4c74dc/content.htm http://help.sap.com/saphelp_nw04/helpdata/en/3d/320e3d89195c59e10000000a114084/frameset.htm Thanks. With regards, Anand Kumar Edited by: kur5rt on Oct 13, 2009 10:47 AM Edited by: kur5rt on Oct 13, 2009 10:49 AM

Not able to view Characteristic Hierarchy using Tcode KES3

Hi everyone,
I need to view the Characteristic Hierarchy using T-code KES3 in CO-PA. Ideally, once we are into KES3 screen, we need to select the characteristic and variant to display the hierarchy. But, when I select the characteristic and variant, it says that "Hierarchy doesn't exist".
However, when I create a report for that particular characteristic using T-code KE31, I am able to view the hierarchy for that characteristic there.
Can anyone please help me in this regard that why the characteristic hierarchy is not available in KES3, while it's picking up the hierarchy at the time of report creation.
Thanks.
Regards,
Gaurav Tibrewal

Hi Nikolas,
I want to see the hierarchy of "Business Unit" characteristic. This characteristic is being maintained under "Referenced Characteristic" in T-code KE31. This characteristics is being maintained in Profitability Analysis (T-code KEA5).
Also, I am not able to derive the source where the hierarchy is being maintained for that characteristic. Because, if hierarchy is coming while creating CO-PA reports. they must be maintained somewhere.
Please let me know if you need any further input.
Regards,
Gaurav

ALV Tree Hierarchy using OOPS

Hi all,
I have developed a program for ALV Tree Hierarchy using OOPs.I followed the SAP demo program.I am not able to get the values in the output.Please can anyone guide me where to correct my program. I am placing the entire code so that you all can also debug and see what is wrong.
*& Report ZZHIERARCHY_TEST1
REPORT zzhierarchy_test1.
DATA : alv_container TYPE REF TO cl_gui_custom_container,
       alv_tree      TYPE REF TO cl_gui_alv_tree,
       gt_fcat          TYPE lvc_t_fcat,
       gt_vbrk TYPE vbrk OCCURS 0.                             "Output Table
DATA : gs_hirarchy_header TYPE treev_hhdr.
START-OF-SELECTION.
END-OF-SELECTION.
CALL SCREEN 9100.
*&      Module STATUS_9100 OUTPUT
MODULE status_9100 OUTPUT.
SET PF-STATUS 'ALV_TREE'.
IF alv_container IS INITIAL.
    PERFORM tree_dev.
ENDIF.
ENDMODULE.                 " STATUS_9100 OUTPUT
*&      Form tree_dev
      text
FORM tree_dev .
DATA lv_container_name(20) TYPE c.
lv_container_name = 'ALV_TREE'.
CREATE OBJECT alv_container
    EXPORTING
      container_name              = lv_container_name
    EXCEPTIONS
      cntl_error                  = 1
      cntl_system_error           = 2
      create_error                = 3
      lifetime_error              = 4
      lifetime_dynpro_dynpro_link = 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 OBJECT alv_tree
    EXPORTING
      parent                      = alv_container
      node_selection_mode         = cl_gui_column_tree=>node_sel_mode_single
      item_selection              = 'X'
      no_toolbar                  = ''
      no_html_header              = 'X'
    EXCEPTIONS
      cntl_error                  = 1
      cntl_system_error           = 2
      create_error                = 3
      lifetime_error              = 4
      illegal_node_selection_mode = 5
      failed                      = 6
      illegal_column_name         = 7
      OTHERS                      = 8.
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 build_hirarchy_header CHANGING gs_hirarchy_header.
PERFORM buid_fieldcatalog.
CALL METHOD alv_tree->set_table_for_first_display
    EXPORTING
      is_hierarchy_header = gs_hirarchy_header
    CHANGING
      it_outtab           = gt_vbrk               "Table Must be Empty
      it_fieldcatalog     = gt_fcat.
PERFORM create_hierarchy.
CALL METHOD alv_tree->frontend_update.
ENDFORM.                    " tree_dev
*&      Form build_hirarchy_header
     <--P_GS_HIRARCHY_HEADER text
FORM build_hirarchy_header CHANGING p_gs_hirarchy_header TYPE treev_hhdr.
p_gs_hirarchy_header-heading   = 'Company Code'(001).
p_gs_hirarchy_header-tooltip   = 'Comapny Code'(002).
p_gs_hirarchy_header-width     =   35.
p_gs_hirarchy_header-width_pix =   ''.
ENDFORM.                    " build_hirarchy_header
*&      Form buid_fieldcatalog
FORM buid_fieldcatalog .
DATA ls_fcat TYPE lvc_s_fcat.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
   EXPORTING
     i_structure_name             = 'VBRK'
    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.
LOOP AT gt_fcat INTO ls_fcat.
    CASE ls_fcat-fieldname.
      WHEN 'NETWR'.
        ls_fcat-do_sum = 'X'.
        ls_fcat-h_ftype = 'MAX'.
    ENDCASE.
    MODIFY gt_fcat FROM ls_fcat.
ENDLOOP.
ENDFORM.                    " buid_fieldcatalog
*&      Form create_hierarchy
FORM create_hierarchy .
DATA : lt_vbrk TYPE TABLE OF vbrk,
         ls_vbrk TYPE vbrk.
DATA : top_key     TYPE lvc_nkey,
         company_key TYPE lvc_nkey,
         bzirk_key   TYPE lvc_nkey.
DATA : lv_bukrs     TYPE bukrs,
         lv_bukrs_prv TYPE bukrs,
         lv_bzirk     TYPE bzirk,
         lv_bzirk_prv TYPE bzirk.
SELECT * FROM vbrk INTO TABLE lt_vbrk UP TO 500 ROWS.
SORT lt_vbrk BY bukrs .
CALL METHOD alv_tree->add_node
    EXPORTING
      i_relat_node_key     = ''
      i_relationship       = cl_gui_column_tree=>relat_last_child
      i_node_text          = 'Company Code'
    IMPORTING
      e_new_node_key       = top_key
    EXCEPTIONS
      relat_node_not_found = 1
      node_not_found       = 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.
LOOP AT lt_vbrk INTO ls_vbrk.
    lv_bukrs = ls_vbrk-bukrs .
    lv_bzirk = ls_vbrk-bzirk .
    IF lv_bukrs <> lv_bukrs_prv.
      lv_bukrs_prv = lv_bukrs.
      PERFORM add_node USING lv_bukrs
                             top_key
                    CHANGING company_key.
    ENDIF.
    IF lv_bzirk <> lv_bzirk_prv.
      lv_bzirk_prv = lv_bzirk.
      PERFORM add_posnr USING lv_bzirk
                              company_key
                     CHANGING bzirk_key.
    ENDIF.
ENDLOOP.
ENDFORM.                    " create_hierarchy
*&      Form add_node
     -->P_LV_BUKRS text
     -->P_TOP_KEY text
     <--P_COMPANY_KEY text
FORM add_node USING    p_lv_bukrs    TYPE bukrs
                        p_top_key     TYPE lvc_nkey
               CHANGING p_company_key TYPE lvc_nkey .
DATA: l_node_text TYPE lvc_value,
        ls_vbrk TYPE vbrk.
l_node_text = 'Company' .
CALL METHOD alv_tree->add_node
    EXPORTING
      i_relat_node_key     = p_top_key
      i_relationship       = cl_gui_column_tree=>relat_last_child
      is_outtab_line       = ls_vbrk
      i_node_text          = l_node_text
    IMPORTING
      e_new_node_key       = p_company_key
    EXCEPTIONS
      relat_node_not_found = 1
      node_not_found       = 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.
ENDFORM.                    " add_node
*&      Form add_posnr
      text
     -->P_LV_POSNR text
     -->P_COMPANY_KEY text
     <--P_POSNR_KEY text
FORM add_posnr USING    p_lv_bzirk    TYPE bzirk
                         p_company_key TYPE lvc_nkey
                CHANGING p_bzirk_key   TYPE lvc_nkey.
DATA ls_vbrk TYPE vbrk.
CALL METHOD alv_tree->add_node
    EXPORTING
      i_relat_node_key     = p_company_key
      i_relationship       = cl_gui_column_tree=>relat_last_child
      is_outtab_line       = ls_vbrk
      i_node_text          = 'Sales District'
    IMPORTING
      e_new_node_key       = p_bzirk_key
    EXCEPTIONS
      relat_node_not_found = 1
      node_not_found       = 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.
ENDFORM.                    " add_posnr
*&      Module USER_COMMAND_9100 INPUT
MODULE user_command_9100 INPUT.
CASE sy-ucomm.
    WHEN 'BACK' OR 'EXIT' OR 'CANCEL'.
CALL METHOD alv_container->free.
LEAVE PROGRAM.
ENDCASE.
ENDMODULE.                 " USER_COMMAND_9100 INPUT

Check this forum there are many threads on this.

Downloaded my hierarchy using the program z_sap_hierarchy_download

hi
I want download downloaded my hierarchy using the program z_sap_hierarchy_download but I have any problem when I using idoc method, I have this message:
Node [00001350, 00001580]: Leaf 'E010000000' already exists as child of node 00001501
Best regard
Francoise

hi
The problem is that 2 id differents has the same description.
my program is:
begin
SAP Consulting BW Tools:
Download hierarchy into a flat file. The file has the correct format
Text elements:
P_DATES Include from/to dates
P_DATETO Valid-to date
P_FNAME File name
P_HIENM Hierarchy name
P_INTER Include from/to leaves
P_IOBJNM InfoObject
P_LANGU Language
P_VERS Hierarchy version
REPORT z_sap_hierarchy_download.
TYPE-POOLS: rs, rsdm, rrh1.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS:
p_iobjnm TYPE rsdiobjnm MEMORY ID rsc.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME.
PARAMETERS:
p_hienm TYPE rshiedir-hienm,
p_vers TYPE rshiedir-version,
p_dateto TYPE rshiedir-dateto,
p_langu TYPE rshiedirt-langu.
SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME.
PARAMETERS:
p_fname LIKE rlgrap-filename,
p_dates AS CHECKBOX DEFAULT 'X',
p_inter AS CHECKBOX DEFAULT 'X'.
SELECTION-SCREEN END OF BLOCK b3.
File structure
TYPES:
No dates/intervals
BEGIN OF y_s_hierfile_1,
nodeid TYPE rshienodid,
iobjnm TYPE rsiobjnm,
nodename TYPE rsnodename,
tlevel TYPE rstlevel,
link TYPE rslink,
parentid TYPE rsparent,
childid TYPE rschild,
nextid TYPE rsnext,
langu TYPE langu,
txtsh TYPE rstxtsh,
txtmd TYPE rstxtmd,
txtlg TYPE rstxtlg,
END OF y_s_hierfile_1,
y_t_hierfile_1 TYPE STANDARD TABLE OF y_s_hierfile_1,
With dates
BEGIN OF y_s_hierfile_2,
nodeid TYPE rshienodid,
iobjnm TYPE rsiobjnm,
nodename TYPE rsnodename,
tlevel TYPE rstlevel,
link TYPE rslink,
parentid TYPE rsparent,
childid TYPE rschild,
nextid TYPE rsnext,
dateto TYPE rsdateto,
datefrom TYPE rsdatefrom,
langu TYPE langu,
txtsh TYPE rstxtsh,
txtmd TYPE rstxtmd,
txtlg TYPE rstxtlg,
END OF y_s_hierfile_2,
y_t_hierfile_2 TYPE STANDARD TABLE OF y_s_hierfile_2,
With intervals
BEGIN OF y_s_hierfile_3,
nodeid TYPE rshienodid,
iobjnm TYPE rsiobjnm,
nodename TYPE rsnodename,
tlevel TYPE rstlevel,
link TYPE rslink,
parentid TYPE rsparent,
childid TYPE rschild,
nextid TYPE rsnext,
leafto TYPE rsleafto,
leaffrom TYPE rsleaffrom,
langu TYPE langu,
txtsh TYPE rstxtsh,
txtmd TYPE rstxtmd,
txtlg TYPE rstxtlg,
END OF y_s_hierfile_3,
y_t_hierfile_3 TYPE STANDARD TABLE OF y_s_hierfile_3,
With dates/intervals
BEGIN OF y_s_hierfile_4,
nodeid TYPE rshienodid,
iobjnm TYPE rsiobjnm,
nodename TYPE rsnodename,
tlevel TYPE rstlevel,
link TYPE rslink,
parentid TYPE rsparent,
childid TYPE rschild,
nextid TYPE rsnext,
dateto TYPE rsdateto,
datefrom TYPE rsdatefrom,
leafto TYPE rsleafto,
leaffrom TYPE rsleaffrom,
langu TYPE langu,
txtsh TYPE rstxtsh,
txtmd TYPE rstxtmd,
txtlg TYPE rstxtlg,END OF y_s_hierfile_4,
y_t_hierfile_4 TYPE STANDARD TABLE OF y_s_hierfile_4.
Hierarchy definition
DATA:
g_s_hiesel TYPE rsndi_s_hiesel,
g_s_hiedir TYPE rsndi_s_hiedir,
g_subrc TYPE sy-subrc,
g_t_hiedirt TYPE TABLE OF rshiedirt,
g_s_hierstruc TYPE rssh_s_htab,
g_t_hierstruc TYPE TABLE OF rssh_s_htab,
g_s_thiernode TYPE rsthiernode,
g_t_thiernode TYPE TABLE OF rsthiernode WITH KEY langu hieid objvers
nodename,
g_s_hierintvl TYPE rssh_s_jtab,
g_t_hierintvl TYPE TABLE OF rssh_s_jtab WITH KEY hieid objvers nodeid,
g_s_message TYPE rsndi_s_message,
g_t_message TYPE TABLE OF rsndi_s_message,
g_s_chavlinfo TYPE rsdm_s_chavlinfo,
g_t_chavlinfo TYPE rsdm_t_chavlinfo.
File
DATA:
g_fname TYPE string,
g_struct_s TYPE string,
g_struct_t TYPE string,
gr_s_file TYPE REF TO data,
gr_t_file TYPE REF TO data.
FIELD-SYMBOLS:
<g_langu> TYPE ANY,
<g_s_file> TYPE ANY,
<g_t_file> TYPE STANDARD TABLE.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_iobjnm.
CALL FUNCTION 'RSD_IOBJ_F4'
    EXPORTING
      i_show_cha    = rs_c_true
      i_objvers     = rs_c_objvers-active
      i_hietabfl    = rs_c_true
    CHANGING
      c_iobjnm      = p_iobjnm
    EXCEPTIONS
      illegal_input = 1.
CHECK sy-subrc = 0.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_hienm.
DATA:
l_s_hiertxt TYPE rrh1_s_hiertxt,
l_t_hiertxt TYPE rrh1_t_hiertxt.
CALL FUNCTION 'RRH1_HIERARCHY_HELP_VALUES_GET'
    EXPORTING
      i_iobjnm          = p_iobjnm
      i_dateto          = p_dateto
      i_hienm           = p_hienm
      i_version         = p_vers
    IMPORTING
      e_t_hiertxt       = l_t_hiertxt
    EXCEPTIONS
      no_f4_available   = 1
      dialogue_canceled = 2
      OTHERS            = 3.
CHECK sy-subrc = 0.
READ TABLE l_t_hiertxt INTO l_s_hiertxt INDEX 1.
CHECK NOT l_s_hiertxt IS INITIAL.
p_hienm = l_s_hiertxt-hienm.
DATA:
l_s_dynpfields TYPE dynpread,
l_t_dynpfields TYPE STANDARD TABLE OF dynpread.
CLEAR: l_t_dynpfields, l_s_dynpfields.
l_s_dynpfields-fieldname = 'P_VERS'.
WRITE l_s_hiertxt-version TO l_s_dynpfields-fieldvalue.
APPEND l_s_dynpfields TO l_t_dynpfields.
l_s_dynpfields-fieldname = 'P_DATETO'.
WRITE l_s_hiertxt-dateto TO l_s_dynpfields-fieldvalue.
APPEND l_s_dynpfields TO l_t_dynpfields.
CALL FUNCTION 'DYNP_VALUES_UPDATE'
    EXPORTING
      dyname     = sy-repid
      dynumb     = sy-dynnr
    TABLES
      dynpfields = l_t_dynpfields.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
DATA:
l_filename1 TYPE string,
l_filename2 TYPE string,
l_path TYPE string,
l_fullpath TYPE string,
l_action TYPE i.
l_filename1 = p_fname.
CALL METHOD cl_gui_frontend_services=>file_save_dialog
EXPORTING
window_title = 'Select Download File'
default_extension = 'txt'
default_file_name = l_filename1
file_filter = 'All Files (.)|.|Text files (.txt)|.txt'
CHANGING
filename = l_filename2
path = l_path
fullpath = l_fullpath
user_action = l_action
EXCEPTIONS
cntl_error = 1
OTHERS = 2.                                               "#EC NOTEXT
CHECK sy-subrc = 0.
CALL METHOD cl_gui_cfw=>flush.
IF l_action = 0.
    p_fname = l_fullpath.
ENDIF.
INITIALIZATION.
GET PARAMETER ID 'RSC' FIELD p_iobjnm.
START-OF-SELECTION.
Check input
CHECK NOT p_fname IS INITIAL.
IF p_langu IS INITIAL.
    p_langu = sy-langu.
ENDIF.
IF p_dateto IS INITIAL.
    p_dateto = '99991231'.
ENDIF.
Read hierarchy
CLEAR g_s_hiesel.
g_s_hiesel-objvers = rs_c_objvers-active.
g_s_hiesel-hienm = p_hienm.
g_s_hiesel-version = p_vers.
g_s_hiesel-iobjnm = p_iobjnm.
g_s_hiesel-dateto = p_dateto.
CALL FUNCTION 'RSNDI_SHIE_STRUCTURE_GET'
    EXPORTING
      i_s_hiesel        = g_s_hiesel
      i_no_nodenm_table = rs_c_true
    IMPORTING
      e_s_hiedir        = g_s_hiedir
      e_subrc           = g_subrc
    TABLES
      e_t_hiedirt       = g_t_hiedirt
      e_t_hierstruc     = g_t_hierstruc
      e_t_thiernode     = g_t_thiernode
      e_t_hierintvl     = g_t_hierintvl
      e_t_message       = g_t_message.
IF g_subrc <> 0.
    READ TABLE g_t_message INTO g_s_message INDEX 1.
    IF sy-subrc = 0.
      MESSAGE ID g_s_message-msgid TYPE 'I' NUMBER g_s_message-msgno
      WITH g_s_message-msgv1 g_s_message-msgv2
      g_s_message-msgv3 g_s_message-msgv4.
    ELSE.
      MESSAGE ID 'RSBO' TYPE 'I' NUMBER 899
      WITH 'Hierarchy read error'.
    ENDIF.
    EXIT.
ENDIF.
Defined output structures
IF p_dates IS INITIAL AND p_inter IS INITIAL.
    g_struct_s = 'Y_S_HIERFILE_1'.
    g_struct_t = 'Y_T_HIERFILE_1'.
ELSEIF p_dates = 'X' AND p_inter IS INITIAL.
    g_struct_s = 'Y_S_HIERFILE_2'.
    g_struct_t = 'Y_T_HIERFILE_2'.
ELSEIF p_dates IS INITIAL AND p_inter = 'X'.
    g_struct_s = 'Y_S_HIERFILE_3'.
    g_struct_t = 'Y_T_HIERFILE_3'.
ELSE.
    g_struct_s = 'Y_S_HIERFILE_4'.
    g_struct_t = 'Y_T_HIERFILE_4'.
ENDIF.
CREATE DATA gr_s_file TYPE (g_struct_s).
ASSIGN gr_s_file->* TO <g_s_file>.
CREATE DATA gr_t_file TYPE (g_struct_t).
ASSIGN gr_t_file->* TO <g_t_file>.
Nodes
REFRESH <g_t_file>.
LOOP AT g_t_hierstruc INTO g_s_hierstruc.
    CLEAR <g_s_file>.
    MOVE-CORRESPONDING g_s_hierstruc TO <g_s_file>.
Texts for nodes
    READ TABLE g_t_thiernode INTO g_s_thiernode WITH TABLE KEY
    langu = p_langu
    hieid = g_s_hierstruc-hieid
    objvers = rs_c_objvers-active
    nodename = g_s_hierstruc-nodename.
    IF sy-subrc = 0.
      MOVE-CORRESPONDING g_s_thiernode TO <g_s_file>.
    ELSE.
Texts for characteristic values
      REFRESH g_t_chavlinfo.
      CLEAR g_s_chavlinfo.
      g_s_chavlinfo-c_chavl = g_s_hierstruc-nodename.
      APPEND g_s_chavlinfo TO g_t_chavlinfo.
      CALL FUNCTION 'RSD_CHAVL_READ_ALL'
        EXPORTING
          i_iobjnm                  = g_s_hierstruc-iobjnm
          i_langu                   = p_langu
          i_dateto                  = p_dateto
          i_check_value             = space
          i_sid_in                  = space
          i_hieid                   = g_s_hiedir-hieid
          i_objvers                 = g_s_hiedir-objvers
        CHANGING
          c_t_chavlinfo             = g_t_chavlinfo
        EXCEPTIONS
          info_object_not_found     = 1
          routines_generation_error = 2
          check_table_not_existing = 3
          text_table_not_existing   = 4
          OTHERS                    = 5.
      IF sy-subrc = 0.
        READ TABLE g_t_chavlinfo INTO g_s_chavlinfo INDEX 1.
        IF sy-subrc = 0.
          MOVE-CORRESPONDING g_s_chavlinfo-e_chatexts TO <g_s_file>.
          ASSIGN COMPONENT 'LANGU' OF STRUCTURE <g_s_file> TO <g_langu>.
          IF sy-subrc = 0.
            <g_langu> = p_langu.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDIF.
Intervals
    IF g_s_hierstruc-intervl = 'X' AND p_inter = 'X'.
      READ TABLE g_t_hierintvl INTO g_s_hierintvl WITH TABLE KEY
      hieid = g_s_hierstruc-hieid
      objvers = rs_c_objvers-active
      nodeid = g_s_hierstruc-nodeid.
      IF sy-subrc = 0.
        MOVE-CORRESPONDING g_s_hierintvl TO <g_s_file>.
      ENDIF.
    ENDIF.
    APPEND <g_s_file> TO <g_t_file>.
ENDLOOP.
Download output table
g_fname = p_fname.
CALL FUNCTION 'GUI_DOWNLOAD'
    EXPORTING
      filename                = g_fname
      write_field_separator   = space
    TABLES
      data_tab                = <g_t_file>
    EXCEPTIONS
      file_write_error        = 1
      no_batch                = 2
      gui_refuse_filetransfer = 3
      invalid_type            = 4
      no_authority            = 5
      unknown_error           = 6
      header_not_allowed      = 7
      separator_not_allowed   = 8
      filesize_not_allowed    = 9
      header_too_long         = 10
      dp_error_create         = 11
      dp_error_send           = 12
      dp_error_write          = 13
      unknown_dp_error        = 14
      access_denied           = 15
      dp_out_of_memory        = 16
      disk_full               = 17
      dp_timeout              = 18
      file_not_found          = 19
      dataprovider_exception = 20
      control_flush_error     = 21
      OTHERS                  = 22.
IF sy-subrc = 0.
    MESSAGE ID 'RSBO' TYPE 'I' NUMBER 899
    WITH 'Hierarchy download successful!'.
ELSE.
    MESSAGE ID sy-msgid TYPE 'I' NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
end

How to use File Adapter with hierarchial Structure?

Hi,
How to use File Adapter with hierarchial Structure like..
Data:
--Header Details:
Line Item Details:
Data
Bcoz I am getting a Flatfile in a hierarchial way as shown below.
Header Details :1
Line Item a
Line Item b
Header Details :2
Line Item c
Line Item d
Kishore

Hey Kishore,
In order to create a structure you need to use the file with convertion mode on the sending communication channel of the file adapter.
check the link for the needed configuration paramters.
If the structure is more complexed you can use the Contetnt master(CM) from itemfield which allows to ceate XML file from complex flat files and more.
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm">File sender adapter</a>
If you have any question i'll be more than happy to assist.
Nimrod Gisis

Building Tree hierarchy Using nested loops and class cl_gui_column_tree

Hello gurus,
I want to create a tree report using custom container and class cl_gui_column_tree. I have read and understood the standard demo report which SAP has provided i.e. SAPCOLUMN_TREE_CONTROL_DEMO. But in this report all the levels nodes are created as constants and hardcoded. I want to create hierarchy using nested loops. For this i took one example of a hierarchy of VBAK-VBELN->VBAP-POSNR Like One sales order has many line items and each line item can have number of line items in billing plan.
I have done some coding for it.
FORM build_tree USING node_table TYPE treev_ntab
                                       item_table TYPE zitem_table.              " i created the zitem_table table type of mtreeitm in SE11.
DATA: node TYPE treev_node,
             item TYPE mtreeitm.
node-node_key = root.
CLEAR node-relatkey.
CLEAR node-relatship.
node-hidden = ' '.
node-disabled = ' '.
CLEAR node-n_image.
CLEAR node-exp_image.
node-isfolder = 'X'.
node-expander = 'X'.
APPEND node TO node_table.
item-node_key = root.
item-item_name = colm1.
item-class = cl_gui_column_tree=>item_class_text.
item-text = 'Root'.
APPEND item TO item_table.
item-node_key = root.
item-item_name = colm2.
item-class = cl_gui_column_tree=>item_class_text.
item-text = 'Amount'.
APPEND item TO item_table.
LOOP AT it_vbeln INTO wa_vbeln.
    node-node_key = wa_vbeln-vbeln.
    node-relatkey = root.
    node-relatship = cl_gui_column_tree=>relat_last_child.
    node-hidden = ' '.
    node-disabled = ' '.
    CLEAR node-n_image.
    CLEAR node-exp_image.
    node-isfolder = 'X'.
    node-expander = 'X'.
    APPEND node TO node_table.
    item-node_key = wa_vbeln-vbeln.
    item-item_name = colm1.
    item-class = cl_gui_column_tree=>item_class_text.
    item-text = wa_vbeln-vbeln.
    APPEND item TO item_table.
    item-node_key = wa_vbeln-vbeln.
    item-item_name = colm2.
    item-class = cl_gui_column_tree=>item_class_text.
    item-text = wa_vbeln-netwr.
    APPEND item TO item_table.
    LOOP AT it_posnr INTO wa_posnr.
    node-node_key = wa_posnr-posnr.
    node-relatkey = wa_vbeln-vbeln.
    node-relatship = cl_gui_column_tree=>relat_last_child.
    node-hidden = ' '.
    node-disabled = ' '.
    CLEAR node-n_image.
    CLEAR node-exp_image.
    node-isfolder = ' '.
    node-expander = ' '.
    APPEND node TO node_table.
    item-node_key = wa_posnr-posnr.
    item-item_name = colm1.
    item-class = cl_gui_column_tree=>item_class_text.
    item-text = wa_posnr-posnr.
    APPEND item TO item_table.
    item-node_key = wa_posnr-posnr.
    item-item_name = colm2.
    item-class = cl_gui_column_tree=>item_class_text.
    item-text = wa_posnr-netpr.
    APPEND item TO item_table.
    ENDLOOP.
ENDLOOP.
ENDFORM.
Now this program compiles fine and runs till there is only one level. That is root->vbeln. But when i add one more loop of it_posnr it gives me runtime error of message type 'X'. The problem i found was uniqueness of item-item_name as all the sales order have posnr = 0010. What could be done? I tried giving item_name unique hierarchy level using counters just like stufe field in prps eg. 10.10.10, 10.10.20,10.20.10,10.20.20,20.10.10 etc.. etc.. but still i am getting runtime error when i add one more hierarchy using nested loop. Plz guide.
Edited by: Yayati6260 on Jul 14, 2011 7:25 AM

Hello all,
Thanks the issue is solved. The node key was not getting a unique identification as nodekey. I resolved the issue by generating unique identification for each level. Thanks all,
Regards
Yayati Ekbote

Is there possibility to add dimension value into hierarchy using dml or spl

1 Is there possibility to add dimension value into hierarchy using dml or spl?
If such possibility exists how to do that.
2 Is it possible to sort dimension values inside one branch of the hierarchy?

What version of OLAP are you using and how did you create your AW (e.g., AWM)?
Assuming that you're used either AWM or the Java API for AWs in 10g, there isn't an OLAP DML for adding a dimension member to a dimension (and have all the meta data kept in sync); you must load dimension members using AWM the Java API for AWs.
So, make your changes in the the dimension table and process that table.
For sorting, you can add a sort attribute to the dimension. Add the sort attribute to the model, indicate that it's used for sorting, add the sort attribute to your dimension table and maintain the dimension.

Network - subnetwork hierarchy using std networks.

I want to create network / subnetwork hierarchy using std. networks.
How is it done in PS.

Create standard Network > Create Activities in Standard Network > Assign Milestone in Std NW > Define Milestone functions/Parameters > Now with the help of this Std network number you can create Sub Network as you wants [In CN21 Transaction code input Std NW number then automatically system will create all subnetwork from that Std Network
Swapnil Kharul

Customer Hierarchy using MDM

Hi,
We would like to build customer Hierarchy using MDM that would match the DUNS hierarchy. Is this possible to Model this using MDM?
Thanks,
Sanjay

Hi Sanjay,
I never tried to analyze the DUNS hierarchy. But, hope you know that MDM supports different table types and Hierarchy table is one among them.
Regards,
Rajani Kumar

Adjacency Matrix in MDS using a recursive derived hierarchy

Hello everyone!
I'm looking for some great examples of how to do an adjacency matrix in Master Data Services while using the recursive derived hierarchy. Is this even possible or do I need to use an explicit hierarchy?
I'd really like to avoid using the explicit hierarchy because I'd like to be able to define the matrix and enforce adjacency relationship with that matrix.
I hope I'm making sense here...

Gersh,
It works now. I have implemented the below code (ENTITY needed to contain the variable as well). The relationship profitcenter and entity is very important as it derives the relevant profitcenters from the profit center hierarchy (e.g. all profitcenters under the legalentity node).
//ALLOCATION PROCEDURE CONVERSION RATE
//=====================================
*FOR %ENT% = %ENTITY_SET%
*RUNALLOCATION
*FACTOR=1
*DIM SEBACCOUNT WHAT=CONV_RATE; WHERE=<<<; USING=<<< ; TOTAL=<<<
*DIM PROFCENT WHAT=DUMPC; WHERE=BAS(BPC_%ENT%);USING=<<<; TOTAL=<<<
*DIM CATEGORY WHAT=FCSTCUR; WHERE=<<<; USING=<<< ; TOTAL=<<<
*DIM ENTITY WHAT=%ENT%; WHERE=<<<; USING=<<<; TOTAL=<<<
*ENDALLOCATION
*NEXT
Thanks
Nico

How to migrate VIs to LabVIEW 8.0 (do not use Save As Duplicate Hierarchy!)

As with any move to a new version, you should make backup copies of your VIs before saving them in LabVIEW 8.0.
Warning: There is a feature in LabVIEW 8.0 that saves an entire hierarchy (File>>Save As>>Duplicate Hierarchy) but it does NOT work for opening VIs from a previous version and saving copies for 8.0.
Duplicate Hierarchy will save the original VIs before making a copy. It is useful for distributing a copy of your 8.0 VIs, but it does not work for migrating VIs to 8.0.
To migrate VIs, make copies on disk or use "Save with Options" in your previous version of LabVIEW. "Save with Options" does not exist in LabVIEW 8.0.
Christina Rogers, Senior Software Engineer and UX Technical Lead, LabVIEW R&D

Thanks, this is good to know.
LabVIEW Champion . Do more with less code and in less time .

Can you use apple tv as second screen? Kun je apple tv gebruiken als 2e beeldscherm?

Can you use apple tv as second screen (on a Philips 32PFL8404H/12)? Thanx!
Kun je apple tv gebruiken als 2e beeldscherm (op een Philips 32PFL8404H/12)? Bedankt!
Sander

currently no
but some people say that airparrot can though it does not rely on the gpu for realtime encoding so performance would be worse
with the next version of osx you are suppose to be able to do what you ask though

Find "configuration" in the screen "Manage"

Problem:
Where can I find the "configuration" in the screen "Manage"?
http://technet.microsoft.com/en-us/library/jj193512.aspx

The first step says to right click on Computer in the start menu and pick manage. Since you are using Server 2012 there is no start menu. In the Server Manager dashboard in your screenshot click on the Tools menu and select 'Services'. You
will see the same list of services that you would see in the Technet instructions. The path is just a little different in Server 2012.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Hierarchy used in "People in Hierarchy" screen (Manager Actions)

Similar Messages

Maybe you are looking for