Assign Segment Hierarchy Nodes to 0GLACCEXT_T011_HIER

Dear All,
In Below link
http://help.sap.com/search/highlightContent.jsp
i have assigned
Segment Hierarchy Header
But not able to do
Segment Hierarchy Nodes
please tell me the steps to assign Segment Hierarchy Nodes
for DataSource: 0GLACCEXT_T011_HIER      BS/P&L item
Please provide me your inputs.
Regards
SSMS

Hi,
In the change mode of the infosource, at the top you have the segment you will have to change the segment from the drop down from header to nodes and do the mapping and then activate the transfer rules.
Assign points if useful
regards
Venkata Devaraj

Similar Messages

  • Reassignment of hierarchy nodes dynamically

    Hi Experts,
    I have a requirement wherein I need to re-assign the hierarchy node for an account based on Functional area.
    Currently, we load 0ACCOUNT info object with hierarchy defined in KDH3 transaction in R/3. Here, the account 650000000 is defined under local accounts node of the hierarchy. Hence, when we use the 0account infobject in BEx with hierarchy activated, all the records in transaction data with account no. 650000000 are aggregated under local accounts node.
    However, the user wants us to check the functional area for each of the record with 65000000 account and re-assign it to a different node of the hierarchy. For example, if the transaction data has account number 65000000 and functional area 400, then the record needs to be aggregated under a different node in hierarchy, say overhead costs. Similarly, if there is another record with account 650000000 and functional area 300, then the record needs to be aggregated under Sales & marketing.
    How do we handle such conditional assignment of hierarchy nodes?
    Regards,
    SS

    Hi,
    I really doubt if dynamic reassignment of hierarchy nodes is possible in BW, but could be wrong.
    Alternatives which you can consider
    a. A flat hierarchy modeled in the dimension of the cube i.e. higher levels of 0ACCOUNT can be filled during transformations based on functional area. Major disadvantage here is that any change to the hierarchy or assignment could require reloads depending on your requirement i.e. touch history data or not
    b.Customized Hierarchy created by combining the original hierarchy and the assignment details
    for eg 
    Leaf Node: 650000000_400 under parent Overhead Costs
    Leaf Node: 650000000_300,under parent Sales & Marketing
    Regards,
    Advait

  • Assignment of documents to hierarchy nodes???

    Hi,
    We are using a NW2004s BI system.  After executing a query (BEx Launcher) and when the "Comments" button is selected, we receive the following error:
    ===========================================================
    Assignment of documents to hierarchy nodes is not supported in current KM repository for BU documents (/bw_document/InfoProviderData).
    Document will be created without assignment for characteristic OPROFIT_CTR.  Migrate documents to a CM repository
    ===========================================================
    Any hints/directions would help me a lot as we are nearing go-live.
    Thanks in advance.
    Best Regards,
    Praveen

    The problem is that the KF is not assigned to the hierarchy. We ran in exactly same problem. We solved it by assigning the hierarchy to the KF of which you want to create the document even though you are not showing the hierarchy.
    By the way, it seems that we are both using documents .. do you know how to change the assignment template of the document. WHere to customise the document settings ?!
    Mikkel Søndergaard

  • Locking hierarchy node

    Hi everybody,
    i have a problem with locking hierarchy nodes in the BEx (integrated planning). I have to show a certain hierarchy in the rows and i also have to select a certain node of this hierarchy before. Therefore i create an editable variable for this charactristic. After selecting a certain node of this hierarchy all nodes of this hierarchy will be locked so that nobody else is able to plan on this hierarchy. In my opinion it is not a normal reaction of the system. I really expect that only the selected hierarchy node and all the nodes assigning to this node must be locked, but not all the nodes of the hierarchy. Am i right? Has someone had the same experience? Is it probably a bug?
    I really look forward to getting an answer.
    Thanks in advance.
    Ali

    Hi Ali,
    locks depend on the selection used in the filter of the query (or restrictions in structure members). So make sure that your restrictions are in the filter (the default values play no role). In the filter you can use select options or hierarchy nodes (this is then called a selection hierarchy).
    If you are only using a presentation hierarchy this has not effect on locks.
    Remarks: If a selection hierarchy is used in a filter the characteristic values with respect to the hierarchy base characteristic will be resolved, i.e. in RSPLSE you will see (maybe long) lists of single values.
    Regards,
    Gregor

  • Hierarchy node variable in BPS planning level

    Hi gurus,
    I have a set of planning levels and packages that are meant for all users. The users currently are segregated by 0costcenter hierarchy nodes, i.e. groups of users are belonging to different nodes within the 0costcenter hierarchy. These group of users each have its respective authorisation profile assigned based on hierarchy node.
    The planning levels and packages are configured so that 0costcenter is one of the header characteristics in the layout.
    Is there a way for the characteristic 0costcenter in the planning level and packages to derive the cost centers from the authorisation profiles ?
    Advice appreciated.
    Thanks.

    You may consider any of the following:
    1. BPS variables with authorization replacement type.
    2. BPS variables with user defined values replacement type.
    Ravi Thothadri

  • Customer Exit variable on Hierarchy Node

    Hello Experts
    I am in the process of creating a Customer Exit variable on a Hierarchy node. This will be populated at run time based on the value of a Characteristic variable.
    The Hierarchy is activated and included in the roes of the report. I would like the end result to be exactly the same as it would if I had manually entered a variable in Hierarchy node variable
    I have written exits before for Characteristic variables, however, I am unable to get this to work for Hierarchy Node variables. Please find below the code I have prepared so far. I follow the approach of creating a seperate executable program for each Customer Exit variable. This Program will be called by the Exit.
    DATA: l_s_range TYPE rrrangesid.
      DATA:l_s_var_range TYPE rrrangeexit.
      FIELD-SYMBOLS : <fs_var_range> TYPE rrrangeexit.
      IF i_step = 2.
        READ TABLE i_t_var_range
        ASSIGNING <fs_var_range>
        WITH KEY vnam = 'ZMO_WBS_LVL2'.  " Characteristic variable
        IF sy-subrc = 0.
          l_s_range-low = <fs_var_range>-low.
         l_s_range-high = '0HIER_NODE'.*
          l_s_range-sign = 'I'.
          l_s_range-opt = 'EQ'.
          APPEND l_s_range TO e_t_range.
        endif.
      endif.
    I would be obliged if anyone can help me understand what is being overlooked. The Query is presently returning "No Applicable data found"
    Thanks in advance
    Regards
    Zubin Kurian

    Hello
    I have made the changes. Please refer the Code below for reference. This code will function display only those Nodes at and below the WBS element(s) that were entered into the variable ZMM_WBS_ELEMT
    IF i_step = 2.
      SORT i_t_var_range BY VNAM.
        LOOP AT i_t_var_range ASSIGNING <fs_var_range>
             WHERE
                  VNAM = 'ZMM_WBS_ELEMT'. " Multiple Value, & Mandatory
           IF <fs_var_range> IS ASSIGNED.
             CLEAR: l_s_range.
                l_s_range-low  = <fs_var_range>-low.
                l_s_range-high = '0WBS_ELEMT'.
                l_s_range-sign = 'I'.
                l_s_range-opt  = 'BT'.
                APPEND l_s_range TO e_t_range.
                ZVAR_COUNT = 1.
           ENDIF.
        ENDLOOP.
    Edited by: Zubin Kurian on May 10, 2011 4:38 PM

  • 0GLACCEXT hierarchy nodes description not displaying

    Hi Gurus,
    Dear Moderator , Please close / delete this thread , I've posted this thread in EIM >> EDW >> General *
    Edited by: Nehabibo on Dec 14, 2010 4:40 PM
    Edited by: Nehabibo on Dec 14, 2010 5:17 PM

    Hi Ganesh,
    Please follow below mentioned steps to to get correct values in Balance sheet report ie for Assets and Liabilities.
    Double click on Transfer Rules of 0GLACCEXT (Hierarchy)
    Check Below mentioned fields are mapped correctly or no
    0HIENM  -
    HIENM
    0HIER_VERS----
    VERSION
    0DATETO----
    DATEFROM
    0DATEFROM----
    DATETO
    next Pls follow below mentioned steps carefully
    In the same screen First u can see Info source----
    0GLACCEXT
    Next You can find Segment -
    Hierarchy Header just beside that you will find  small symbol pls click on that and select Hierarchy Node and pls map fields as below
    0HIER_NODE----
    NODENAME
    SIGNCH----
    RSIGN
    0BAL_DEPEND----
    PLUMI
    0GLACCEXT----
    GLACCEXT
    Please map the fields as I have mentioned and load the data and check.
    Regards
    Albaik
    Edited by: albaik on Mar 15, 2010 7:01 AM

  • PLEASE HELP....Hierarchy Node Variable

    Hi All:
    I have a BPS Hierarchy Node Variable based on the Profit Center Hierarchy that was created in BW.  The problem is when I set this variable to a node...only one profit center in this node gets displayed.  Does anyone know what I am doing wrong here?  I need to show data for all profit centers within this node.
    Thank you very much.

    Hi Jane,
    planning is only possible for one single characteristic combination. If you want to plan data for profit centers you need to plan on a single one.
    Using a hierachy in a planning level means: All profit center in the node are selected, filled into the buffer and can be planned in one step BUT every value must be exactly assigned to a single profit center.
    When you open the layout, the first profit center of the hierachy node can be planned. You can switch to other profit centers by icons at the top of the layout. So there is always one "active" profit center in the header of the layout.
    Thomas

  • Calculation in hierarchy nodes

    BW Experts,
    We have a situation where an account can appear in an account hierarchy twice (i.e. an account is assigned to 2 nodes in the hierarchy).  When we run the BEx report, the subtotals for the 2 nodes which contain the account are calculated correctly, but the parent node of the 2 subtotal nodes only includes the value of the account once, and not twice.  For example,  assume that we have 2 accounts with the following amounts:
    Account  Amount
    A10         100
    A20         200
    and a hierarchy structure with 2 subtotal nodes, one containing A10 and one containing A10 and A20.  So the hierarchy looks like this:
    Total
       Subtotal 1
          A10
       Subtotal 2
          A10
          A20
    In BEx, the report displays the following result:
    Total                      300
       Subtotal 1           100
          A10                 100
       Subtotal 2           300
          A10                 100
          A20                 200
    So BEx is not adding the A10 amount in to the Total node twice, which would give an answer of 400 instead of 300. 
    I did read in the BW Documentation that in cases like this, BEx recognizes that there is a duplicate entry in the hierarchy and so removes it from the totalling.  But in our case we do not want the amount to be removed, we want it to be counted twice. 
    I have tried to use the link node function, but it returns the same result.
    Does anyone know how to include a leaf in multiple nodes in a hierarchy and have BEx include the key figure amount in the all higher level nodes, even if it means doubling, tripling, etc. of the key figure amount?
    Thanks very much for any help.

    Hi Alberto,
    Would you please post the resolution of the issue with the hierarchy node calculation? I too have a simillar requirement. It would be helpful if you share the solution for tha issue that you had.
    Saravana

  • How to determine partner according to higer hierarchy node?

    Hi Experts:
    I need to determine a partner in a sales document according to partner in higher (pricing) hierarchy node.
    I user access sequence wizard and hierarchy was not available as source for determination.
    I tried sourc CRM_PARTNER_G assigning it manually to access sequence. But it does not work.
    Any idea??
    Best regards,
    Cristina

    Any idea????
    Edited by: Cristina Martillo on Nov 18, 2010 9:30 PM

  • Bapi_costelementgrp_create and hierarchy nodes

    Hi to all,
    I need an algorythm in order to fill the internal table hierarchynodes (def. like bapiset_hier ) to pass to the bapi_costelementgrp_create.
    The hierarchy nodes will be uploaded from a file with two fields: "father node" and "child node" like the following:
    TESTJR     TESTJR2
    TESTJR2   TESTJR3
    TESTJR     TESTJR4
    in the internal table the hierlevel shoul be like the following schema:
    TESTJR is level 0
    TESTJR2 have to assigned to TESTJR (hierlevel 1)
    TESTJR3 have to assigned to TESTJR2 (hierlevel 2)
    TESTJR4 have to assigned to TESTJR (hierlevel 1)
    Any ideas and suggestions?
    Thanks in advance.
    Andrew

    Hello Andrew,
    Try the code below.  However, you should test it thoroughly.  WARNING:  Make sure first record in internal table pertains to the root node.  The internal table lt_hier is the internal table that you assign parameter "hierarchynodes" when calling BAPI_COSTELEMENTGRP_CREATE.
    Kind Regards,
    Rae Ellen Woytowiez
    * Types, internal table, and structures for input file
    TYPES:  BEGIN OF input,
              groupname1 TYPE bapiset_groupname,
              groupname2 TYPE bapiset_groupname,
            END OF input.
    TYPES:  input_tt TYPE TABLE OF input.
    DATA:  lt_input TYPE input_tt,
           ls_input TYPE input.
    TYPES:  BEGIN OF input_numbered,
              groupname1 TYPE bapiset_groupname,
              groupname2 TYPE bapiset_groupname,
              rrn TYPE i,
            END OF input_numbered.
    TYPES:  input_numbered_tt TYPE TABLE OF input_numbered.
    DATA:  lt_input_numbered TYPE input_numbered_tt,
           ls_input_numbered TYPE input_numbered.
    * Types, internal tables, structures used to help
    * determine hierarchy level.
    TYPES:  BEGIN OF group_level_numbered,
              level TYPE bapiset_level,
              rrn TYPE i,
              groupname TYPE bapiset_groupname,
            END OF group_level_numbered.
    TYPES:  group_level_numbered_tt TYPE TABLE OF group_level_numbered.
    DATA:  lt_group_level_numbered TYPE group_level_numbered_tt,
           ls_group_level_numbered TYPE group_level_numbered.
    * Types, internal table, structures for function module.
    TYPES:  bapiset_hier_tt TYPE TABLE OF bapiset_hier,
            bapi1113_values_tt TYPE TABLE OF bapi1113_values.
    DATA:  lt_hier TYPE bapiset_hier_tt,
           lt_values TYPE bapi1113_values_tt,
           ls_hier TYPE bapiset_hier,
           ls_values TYPE bapi1113_values.
    DATA:  count TYPE i.
    DATA:  level TYPE i.
    START-OF-SELECTION.
      count = 1.
      LOOP AT lt_input INTO ls_input.
        CLEAR:  ls_input_numbered.
        ls_input_numbered-groupname1 = ls_input-groupname1.
        ls_input_numbered-groupname2 = ls_input-groupname2.
        ls_input_numbered-rrn = count.
        APPEND ls_input_numbered TO lt_input_numbered.
        count = count + 1.
      ENDLOOP.
    * Build hierarchy
      SORT lt_input_numbered BY groupname1 rrn.
      level = 0.
      LOOP AT lt_input_numbered INTO ls_input_numbered.
        PERFORM process_group
                    USING
                       ls_input_numbered
                    CHANGING
                       level.
      ENDLOOP.
    * derive table to be used in FM
      SORT lt_group_level_numbered BY rrn.
      LOOP AT lt_group_level_numbered INTO ls_group_level_numbered.
        ls_hier-groupname = ls_group_level_numbered-groupname.
        ls_hier-hierlevel = ls_group_level_numbered-level.
        ls_hier-DESCRIPT = ls_group_level_numbered-groupname.
        APPEND ls_hier TO lt_hier.
      ENDLOOP.
    FORM process_group USING value(ps_input_numbered) TYPE input_numbered
                       CHANGING value(pv_level) TYPE bapiset_level.
      DATA:  groupname1_subrc TYPE sysubrc,
             groupname1_tabix TYPE sytabix.
      DATA:  groupname2_subrc TYPE sysubrc,
             groupname2_tabix TYPE sytabix.
    * Check and if necessary add groupname1.
      CLEAR ls_group_level_numbered.
      READ TABLE lt_group_level_numbered INTO ls_group_level_numbered
                 WITH KEY groupname = ps_input_numbered-groupname1
                 BINARY SEARCH.
      groupname1_subrc = sy-subrc.
      groupname1_tabix = sy-tabix.
      IF groupname1_subrc <> 0.
        ls_group_level_numbered-groupname = ps_input_numbered-groupname1.
        ls_group_level_numbered-level = pv_level.
        ls_group_level_numbered-rrn = ps_input_numbered-rrn.
        INSERT ls_group_level_numbered INTO lt_group_level_numbered
               INDEX groupname1_tabix.
      ELSE.
        pv_level = ls_group_level_numbered-level.
      ENDIF.
    * Check and if necessary add groupname2.
      CLEAR ls_group_level_numbered.
      READ TABLE lt_group_level_numbered INTO ls_group_level_numbered
                 WITH KEY groupname = ps_input_numbered-groupname2
                 BINARY SEARCH.
      groupname2_subrc = sy-subrc.
      groupname2_tabix = sy-tabix.
      IF groupname2_subrc <> 0.
        ls_group_level_numbered-groupname = ps_input_numbered-groupname2.
        ls_group_level_numbered-level = pv_level + 1.
        ls_group_level_numbered-rrn = ps_input_numbered-rrn.
        INSERT ls_group_level_numbered INTO lt_group_level_numbered
               INDEX groupname2_tabix.
      ENDIF.
    * Check for childs for groupname2.
      pv_level = pv_level + 1.
      LOOP AT lt_input_numbered INTO ls_input_numbered
                         WHERE groupname1 = ps_input_numbered-groupname2.
        PERFORM process_group
                    USING
                       ls_input_numbered
                    CHANGING
                       level.
      ENDLOOP.
    ENDFORM.
    Edited by: Rae Ellen Woytowiez on Apr 15, 2011 7:24 AM
    Edited by: Rae Ellen Woytowiez on Apr 15, 2011 7:26 AM
    Edited by: Rae Ellen Woytowiez on Apr 15, 2011 7:26 AM

  • How to filter hierarchy node in BEX query designer

    Dear experts
    We are working on FI balance sheet with hierarchy infoobject 0GLACCEXT. Example of our balance sheet is as follow:
    Parent Node A = 20
         Sub-parent Node A1 = 10
             Leaf A11 = 5
                 Leaf A12 = 5
    Parent Node B = 20
         Sub-parent Node B1 = 10
                   Leaf B11 = 5
                   Leaf B12 = 5
    We require only:
        Sub-parent Node A1 = 10
        Leaf B12 = 5
    So I filter those out in BEX restriction;  however, after we examine the report in tcode RSRT, "Sub-parent Node A1" is not shown in BEX Report, and the result is as follow：
    Parent Node B = 5
         Sub-parent Node B1 = 5
                 Leaf B12 = 5
    Are there solutions for us to show merely A1 and B12 ?

    Hi Chu
    Try the following steps.
    Initial Output
    In this example I will restrict the query for only displaying Node 8603 and leaf 9000
    Proceed to restrict the Characteristic. Please be aware of the difference between hierarchy nodes and leaf characteristic values. Also set the Hierarchy display properties to expand up to level 1.
    Execute the query again:
    Please be aware that users will still be able to expand node 8603 and see the lower level nodes/leaf. In order to restrict users from doing this set up users authorizations.
    Regards,
    Carlos

  • DSO or ODS "Insert New Hierarchy Nodes" under Data Fields

    When you insert info objects under the Data Fields in DSO right mouse click on the Data Fields icon and you will find Insert New Hierarchy Nodes . I created a hierarchy node with infoobjects associating with it which will be visible under the Filters Folder in BEx Query designer as a seperate folder. I can add them to the infoobjects from this folder into the query. I did not know how to apply this functionality in Queries and what it really does. My guess was you can create dynamic hierarchy using characteristic infoobjects from transactional data.Any ideas or links to documentation. This option was available from 7.X in DSO's and i think even in 3.x ODS.

    Hi,
    May help you:----
    http://help.sap.com/saphelp_nw70/helpdata/en/4a/e71f39488fee0ce10000000a114084/content.htm
    You could feel the flexibility of using this hierarchial display in the Query. Try to create any Query on this DSO.
    Regards,
    Suman

  • Drilldown to hierarchy nodes in VC..

    Hi..
    I want drilldown functionality in VC..
    1. my Query has a hierarchy
    2. my VC application has a table attached to this query.
    3. In Output the hierarchy nodes are displayed
    4. i ve taken a button Drilldown on my table
    5. on selection of a node and onclick of button all the hierarchy nodes get expanded(drilled down)
    Problem : i do not want all the nodes to get drilled down..only the selected node should get drilled..
    Plz help me out for the same...
    Thanks in advance..
    Bhavna.

    Hi,
    Just check out in hierarchy attribute setting... what is the start node for the drill down..
    Regards,
    Viren.

  • Issue with hierarchy node variable and multiple SAP hierarchies

    Hello experts,
    We are currently facing an issue when using two SAP hierarchies in Web Intelligence and one of them is restricted with a hierarchy node variable.
    The systems we use are a SAP BI 7.01 (SPS 05) and a Business Objects Enterprise XI R3.1 SP2 (fix pack 2.3). I want also to point out that the fix pack 2.3 has been applied to all BOE related components: the SAP integration Kit, client tools, and enterprise (server and client).
    The universe used in our scenario is based on a BEX Query with two hierarchies (non-time dependent hierarchies, intervals allowed) loaded on their corresponding characteristics. One of these characteristics is restricted with a hierarchy node variable (manual input, optional, ready for input, multiple single values allowed). 
    Prerequisites for replicating the problem:
    1)     When building the web intelligence query select several levels from both hierarchies (they have seven levels each) and    the   only amount of the InfoCube that the BEX query (that was used to create our universe) relies on.
    2)     In the hierarchy node variable prompt select a hierarchy node entry (not an actual InfoObject value that exists as transactional data in the InfoCube )
    By executing the query built above, all characteristics are returned null (no value) and the key figure with value u201C0u201D. No error messages, no partial results warnings.  Now if we go back to u201CEdit queryu201D and select levels of only one of any of the two hierarchies the query runs normally (by selecting the exact same value for the hierarchy node variable prompt).
    Any ideas on the matter?
    Regards,
    Giorgos

    Hi,
    Have you ever got a solution for this problem?
    I have a similar one.
    Thanks,
    regards, Heike

Maybe you are looking for