New cost element hierarchy - how to extract

Hello,
User created new cost element hierarchy/cost element groups (KAH3).
I dont see this hierarchy in the list of available hiararchies of  data source 0COSTELMNT_0102_HIER.
Shall it appear in the list automatically or I need to do custom extraction?
Thanks

Hello,
The problem is probably caused by the fact that only the highest node of the hierarchy is displayed as available for the       
0COSTELMNT_0102_HIER datasource. This means that the cost element group which is displayed is not used in any other group.  That is probably  the reason why some of your groups are displayed as available and some of them not. You can check it in the transaction KAH3 in your OLTP system.                                                                               
Select your cost element group and press the Where used button. On the next dialog box select just 'Groups' and choose ENTER. Then the groups are displayed that contain the respective group. The highest level group should be available also in BW system.  
When you extract this group then you will see your group as a subnote. Please see the information SAP note 316976 on available hierarchies for CO InfoObjects incomplete.
Best Regards,
Des

Similar Messages

  • Needed to create a new cost element hierarchy to come in line

    needed to create a new cost element hierarchy to come in line with Victory reporting.  I went into create new group and referenced NETEXPS2.RD so that I could then edit it.
    I made all the changes required for the new hierarchy NETEXPS3.RD.  Unfortunately some of the changes I made have changed NETEXPS2.RD.
    Is this my fault for referencing?  Is there any way of going back to the original NETEXPS2.RD version and fixing it?
    Please suggest for the above.
    Regards
    Srinivas.

    In addition to Krishna if you don't want to expose all the package to the trainee, then create a new role keeping everything same as default MODELING role (open it and have a look) but in "PACKAGE PRIVILEGES" add only those package that you want to expose to the end users.
    Regards
    Kumar

  • Cost Element Hierarchy extraction  error

    I am trying to extract cost element hierarchy from the ECC using standard extractor 0COSTELMNT_0102_HIER.   It says 26 records sent and 0 received in the monitor and see the following error when I click error message button.  I would appreciate if someone can help me to resolve this problem.
    Error when updating Idocs in Business Information Warehouse
    Diagnosis
    Errors have been reported in Business Information Warehouse during IDoc update:
    No status record was passed to ALE by the applicat
    System Response
    Some IDocs have error status.
    Procedure
    Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
    Error handling:
    How you resolve the errors depends on the error message you get.

    My problem got solved.
    I went to details tab in the monitor. Look for the IDoc error, select and right click and choose option that says something like 'manual update/correct' on the IDoc.
    Rerun your extraction and it should work.
    Ram.

  • How to create new cost element catagory

    Hi,
    Can any one let me know How to create New cost element catagory other than standard cost element catagory.
    Thanks & Regds,
    Sany.....

    Hi,
    We are using one GL to post expences as well as revenue for the same. In copa primery cost elements are not allowed & if i set clem cat to revenue it wont allow me to book purchase in same GL.
    Waiting for your reply.
    Regards,
    Sany.

  • RSA2/Cost Element Hierarchy (0COSTELMNT_0102_HIER)/remove 0CO_AREAP Prefix

    Hi, gurus.
    We are using 0COSTELMNT_0102_HIER delivered infosource.  This datasource is extracting from our source system the cost element hierarchy.  When loading into BW, every element is getting a controlling area Prefix (cost element characteristics, hierarchy nodes and hierarchy name).  This is the standard behaviour.
    Our requirement is to remove Controlling Area prefix from every hierarchy node and from hierarchy name, but not from characteristic elements.
    eg......0CO_AREA........0COSTELMNT............0HIERNAME
    .........M650..................RU_SIGMA................M650RU_SIGMA
    .........M660..................RU_SIGMA................M660RU_SIGMA
    And we want to get the hierarchy name without the controlling area, so:
    ....................................................................0HIERNAME
    ....................................................................RU_SIGMA
    We can´t upload the hierarchy from a flat file cause we want to load and refresh it daily from the source system.
    We've asked in Marketplace about the missing "change" option in RSA2 transaction, cause we see 2 options to do this:
    1) Create a customer datasource for 0COSTELMNT hierarchy with RSA2 and use 2 custom function modules for extraction and hierarchy catalogs.
    2) Modify 0COSTELMNT_0102_HIER and call 2 new custom function modules for catalog and data extraction (GSBH_HIERARCHY_TRANSFER_SETS, GSBH_HIERARCHY_CATALOG_SETS)
    In any case, we would need access to RSA2 with create/modify authorization.
    They answered that RSA2 is for display only.  Here is their answer:
    "RSA2 is a display only transaction. This transaction is not released for changes in customer systems. The reason is that there would be risks due to incorrect modifications."
    I've also tryed BW07 transaction, but it is just for sets created with GS01 transaction (hierarchy class 0000), and I can´t create a custom datasource for Cost Element from this point.
    If is there another way to supress controlling area prefix??
    Our Development team don´t want the idea to modify GSBH_HIERARCHY_TRANSFER_SETS, GSBH_HIERARCHY_CATALOG_SETS function modules without an OSS note that says so.
    Thanks in advance, Leticia
    I'm having just the same problem mentioned in this thread /community

    I have created a ABAP program to download the costelementgroup from SAP R/3 into a flatfile.<br>
    Hope this helps.<p>
    &----<br>
    *& Report  Z_EXTRACT_COSTELMNTGRP_HIER<br>
    *&<br>
    &----<br>
    *&<br>
    *&<br>
    &----<br>
    <br>
    REPORT  Z_EXTRACT_COSTELMNTGRP_HIER.<br>
    <br>
    ************************************************************************<br>
    TABLES<br>
    ************************************************************************<br>
    <br>
    TABLES: SETLEAF,<br>
            CSKU,<br>
            CSKT.<br>
    <br>
    ************************************************************************<br>
    TYPES<br>
    ************************************************************************<br>
    <br>
    TYPES:  BEGIN OF T_FL_SETLEAF,<br>
            SETNAME TYPE SETLEAF-SETNAME,<br>
            LINEID TYPE SETLEAF-LINEID,<br>
            VALOPTION TYPE SETLEAF-VALOPTION,<br>
            VALFROM TYPE SETLEAF-VALFROM,<br>
            VALTO TYPE SETLEAF-VALTO,<br>
            LTEXT TYPE CSKU-LTEXT,<br>
            END OF T_FL_SETLEAF.<br>
    <br>
    TYPES:  BEGIN OF T_FL_CSKU,<br>
            KSTAR TYPE CSKU-KSTAR,<br>
            LTEXT TYPE CSKT-LTEXT,<br>
            END OF T_FL_CSKU.<br>
    <br>
    TYPES:  BEGIN OF T_FL_CSKB,<br>
            KOKRS TYPE CSKB-KOKRS,<br>
            KSTAR TYPE CSKB-KSTAR,<br>
            DATBI TYPE CSKT-DATBI,<br>
            END OF T_FL_CSKB.<br>
    <br>
    TYPES:  BEGIN OF T_FL_HIER,<br>
            NID(8) TYPE N,<br>
            IOBJ(30),<br>
            NNAME(32),<br>
            PID(8) TYPE N,<br>
            HID TYPE I,<br>
            VALC TYPE I,<br>
            DESC(60),<br>
            END OF T_FL_HIER.<br>
    <br>
    TYPES:  BEGIN OF T_FL_MKHIER,<br>
            HID TYPE I,<br>
            PID(8) TYPE N,<br>
            END OF T_FL_MKHIER.<br>
    <br>
    TYPES:  BEGIN OF T_FL_FINAL,<br>
            OUT(500),<br>
            END OF T_FL_FINAL.<br>
    <br>
    ************************************************************************<br>
    WORKAREAS<br>
    ************************************************************************<br>
    <br>
    DATA:  VFL_CSKU TYPE T_FL_CSKU,<br>
           VFL_CSKB TYPE T_FL_CSKB,<br>
           VFL_SETLEAF TYPE T_FL_SETLEAF,<br>
           VFL_HIER TYPE T_FL_HIER,<br>
           VFL_HIER1 TYPE T_FL_HIER,<br>
           VFL_MKHIER TYPE T_FL_MKHIER,<br>
           VFL_FINAL TYPE T_FL_FINAL,<br>
           VFL_SETHIER TYPE SETHIER_CO.<br>
    <br>
    DATA:  V_SETHEADER TYPE SETHEADER.<br>
    <br>
    ************************************************************************<br>
    INTERNAL TABLES<br>
    ************************************************************************<br>
    <br>
    DATA:  VIT_CSKU TYPE STANDARD TABLE OF T_FL_CSKU,<br>
           VIT_CSKB TYPE STANDARD TABLE OF T_FL_CSKB,<br>
           VIT_SETLEAF TYPE STANDARD TABLE OF T_FL_SETLEAF,<br>
           VIT_SETLEAF1 TYPE STANDARD TABLE OF T_FL_SETLEAF,<br>
           VIT_HIER TYPE STANDARD TABLE OF T_FL_HIER,<br>
           VIT_MKHIER TYPE STANDARD TABLE OF T_FL_MKHIER,<br>
           VIT_FINAL TYPE STANDARD TABLE OF T_FL_FINAL,<br>
           VIT_SETHIER TYPE SETHIER_CO OCCURS 0 WITH HEADER LINE,<br>
           VIT_SETVAL TYPE SETVAL_CO OCCURS 0 WITH HEADER LINE.<br>
    <br>
    ************************************************************************<br>
    VARIABLES<br>
    ************************************************************************<br>
    <br>
    DATA:  NID(8) TYPE N,<br>
           PID(8) TYPE N,<br>
           CSTEL(14) TYPE N,<br>
           SETCLS(4) TYPE C,<br>
           IOBJ(10) TYPE C,<br>
           HID TYPE I,<br>
           NHID(8) TYPE N,<br>
           NVALC(8) TYPE N,<br>
           OUT(500),<br>
           L_FLAG(2) TYPE N,<br>
           L_LINK(1),<br>
           L_COAREA LIKE BAPICO_GROUP-CO_AREA,<br>
           RETURN LIKE BAPIRET2.<br>
    <br>
    ************************************************************************<br>
    SELECTION SCREEN INPUTS<br>
    ************************************************************************<br>
    <br>
    SELECTION-SCREEN BEGIN OF BLOCK SS01 WITH FRAME TITLE TEXT-002.<br>
    PARAMETERS: P_SUBCLS(4) OBLIGATORY,                "Org. eenheid bepalen<br>
                P_SETNM(15) OBLIGATORY.            "Kostensoortgroep bepalen<br>
    SELECTION-SCREEN END OF BLOCK SS01.<br>
    <br>
    SETCLS = '0102'.                        "Setklasse voor kostensoortgroep<br>
    IOBJ = '0COSTELMNT'.                    "InfoObjectnaam voor kostensoort<br>
    <br>
    SELECT SETNAME LINEID VALOPTION VALFROM VALTO INTO TABLE VIT_SETLEAF<br>
           FROM SETLEAF<br>
           WHERE SUBCLASS = P_SUBCLS<br>
           AND SETCLASS = SETCLS.<br>
    <br>
    SELECT KSTAR LTEXT INTO TABLE VIT_CSKU<br>
           FROM CSKU<br>
           WHERE KTOPL = P_SUBCLS<br>
           AND SPRAS = 'NL'.<br>
    <br>
    LOOP AT VIT_SETLEAF INTO VFL_SETLEAF.<br>
    <br>
      IF VFL_SETLEAF-VALOPTION = 'EQ'.<br>
    <br>
        READ TABLE VIT_CSKU INTO VFL_CSKU WITH KEY<br>
                   KSTAR = VFL_SETLEAF-VALFROM BINARY SEARCH.<br>
    <br>
        IF SY-SUBRC = 0.<br>
    <br>
          VFL_SETLEAF-LTEXT = VFL_CSKU-LTEXT.<br>
    <br>
          IF VFL_SETLEAF-LTEXT IS INITIAL.<br>
    <br>
            SELECT SINGLE KTEXT FROM CSKU INTO VFL_SETLEAF-LTEXT<br>
                   WHERE SPRAS = 'N'<br>
                   AND KTOPL = P_SUBCLS<br>
                   AND KSTAR = VFL_SETLEAF-VALFROM.<br>
    <br>
          ENDIF.<br>
    <br>
          APPEND VFL_SETLEAF TO VIT_SETLEAF1.<br>
    <br>
        ENDIF.<br>
    <br>
        CLEAR VFL_CSKU.<br>
    <br>
      ELSEIF VFL_SETLEAF-VALOPTION = 'BT'.<br>
    <br>
        LOOP AT VIT_CSKU INTO VFL_CSKU<br>
             WHERE KSTAR GE VFL_SETLEAF-VALFROM<br>
             AND KSTAR LE VFL_SETLEAF-VALTO.<br>
    <br>
          VFL_SETLEAF-VALFROM = VFL_CSKU-KSTAR.<br>
          VFL_SETLEAF-VALTO = VFL_CSKU-KSTAR.<br>
          VFL_SETLEAF-LTEXT = VFL_CSKU-LTEXT.<br>
    <br>
          IF VFL_SETLEAF-LTEXT IS INITIAL.<br>
    <br>
            SELECT SINGLE KTEXT FROM CSKU INTO VFL_SETLEAF-LTEXT<br>
                   WHERE SPRAS = 'N'<br>
                   AND KTOPL = P_SUBCLS<br>
                   AND KSTAR = VFL_SETLEAF-VALFROM.<br>
    <br>
          ENDIF.<br>
    <br>
          APPEND VFL_SETLEAF TO VIT_SETLEAF1.<br>
    <br>
          CLEAR VFL_CSKU.<br>
    <br>
        ENDLOOP.<br>
    <br>
      ENDIF.<br>
    <br>
      CLEAR VFL_SETLEAF.<br>
    <br>
    ENDLOOP.<br>
    <br>
    CLEAR VIT_SETLEAF[].<br>
    <br>
    SORT VIT_SETLEAF1 BY SETNAME VALFROM.<br>
    <br>
    CALL FUNCTION 'K_GROUP_REMOTE_READ'<br>
      EXPORTING<br>
        setclass   = SETCLS<br>
        co_area    = L_COAREA<br>
        chrt_accts = P_SUBCLS<br>
        groupname  = P_SETNM<br>
      IMPORTING<br>
        return     = RETURN<br>
      TABLES<br>
        et_sethier = VIT_SETHIER<br>
        et_setval  = VIT_SETVAL.<br>
    <br>
    NID = 00000001.<br>
    PID = 00000000.<br>
    <br>
    LOOP AT VIT_SETHIER INTO VFL_SETHIER.<br>
    <br>
      IF NID EQ 00000001.<br>
    <br>
        HID = VFL_SETHIER-HIERLEVEL.<br>
    <br>
        VFL_HIER-NID = NID.<br>
        VFL_HIER-PID = PID.<br>
        VFL_HIER-HID = HID.<br>
        VFL_HIER-IOBJ = '0HIER_NODE'.<br>
        VFL_HIER-NNAME = VFL_SETHIER-GROUPNAME.<br>
        VFL_HIER-DESC = VFL_SETHIER-DESCRIPT.<br>
        VFL_HIER-VALC = VFL_SETHIER-VALCOUNT.<br>
    <br>
        VFL_MKHIER-HID = HID.<br>
        VFL_MKHIER-PID = PID.<br>
    <br>
        APPEND VFL_MKHIER TO VIT_MKHIER.<br>
        APPEND VFL_HIER TO VIT_HIER.<br>
    <br>
        NID = NID + 1.<br>
    <br>
        CLEAR: VFL_HIER, VFL_MKHIER.<br>
    <br>
      ELSE.<br>
    <br>
        IF HID EQ VFL_SETHIER-HIERLEVEL.<br>
    <br>
          HID = VFL_SETHIER-HIERLEVEL.<br>
    <br>
          VFL_HIER-NID = NID.<br>
          VFL_HIER-PID = PID.<br>
          VFL_HIER-HID = HID.<br>
          VFL_HIER-IOBJ = '0HIER_NODE'.<br>
          VFL_HIER-NNAME = VFL_SETHIER-GROUPNAME.<br>
          VFL_HIER-DESC = VFL_SETHIER-DESCRIPT.<br>
          VFL_HIER-VALC = VFL_SETHIER-VALCOUNT.<br>
    <br>
          NID = NID + 1.<br>
    <br>
          APPEND VFL_HIER TO VIT_HIER.<br>
    <br>
          CLEAR: VFL_HIER.<br>
    <br>
        ELSEIF HID LT VFL_SETHIER-HIERLEVEL.<br>
    <br>
          HID = VFL_SETHIER-HIERLEVEL.<br>
          PID = NID - 1.<br>
    <br>
          VFL_HIER-NID = NID.<br>
          VFL_HIER-PID = PID.<br>
          VFL_HIER-HID = HID.<br>
          VFL_HIER-IOBJ = '0HIER_NODE'.<br>
          VFL_HIER-NNAME = VFL_SETHIER-GROUPNAME<br>.
          VFL_HIER-DESC = VFL_SETHIER-DESCRIPT.<br>
          VFL_HIER-VALC = VFL_SETHIER-VALCOUNT.<br>
    <br>
          READ TABLE VIT_MKHIER INTO VFL_MKHIER<br>
            WITH KEY HID = VFL_SETHIER-HIERLEVEL BINARY SEARCH.<br>
    <br>
          IF SY-SUBRC = 0.<br>
    <br>
            VFL_MKHIER-PID = PID.<br>
            MODIFY TABLE VIT_MKHIER FROM VFL_MKHIER.<br>
    <br>
          ELSE.<br>
    <br>
            VFL_MKHIER-HID = HID.<br>
            VFL_MKHIER-PID = PID.<br>
            APPEND VFL_MKHIER TO VIT_MKHIER.<br>
    <br>
          ENDIF.<br>
    <br>
          NID = NID + 1.<br>
    <br>
          APPEND VFL_HIER TO VIT_HIER.<br>
    <br>
          CLEAR: VFL_HIER, VFL_MKHIER.<br>
    <br>
        ELSE.<br>
    <br>
          HID = VFL_SETHIER-HIERLEVEL.<br>
    <br>
          READ TABLE VIT_MKHIER INTO VFL_MKHIER<br>
            WITH KEY HID = VFL_SETHIER-HIERLEVEL BINARY SEARCH.<br>
    <br>
          PID = VFL_MKHIER-PID.<br>
    <br>
          VFL_HIER-NID = NID.<br>
          VFL_HIER-PID = PID.<br>
          VFL_HIER-HID = HID.<br>
          VFL_HIER-IOBJ = '0HIER_NODE'.<br>
          VFL_HIER-NNAME = VFL_SETHIER-GROUPNAME.<br>
          VFL_HIER-DESC = VFL_SETHIER-DESCRIPT.<br>
          VFL_HIER-VALC = VFL_SETHIER-VALCOUNT.<br>
    <br>
          NID = NID + 1.<br>
    <br>
          APPEND VFL_HIER TO VIT_HIER.<br>
    <br>
          CLEAR: VFL_HIER.<br>
    <br>
        ENDIF.<br>
    <br>
      ENDIF.<br>
    <br>
    ENDLOOP.<br>
    <br>
    LOOP AT VIT_HIER INTO VFL_HIER WHERE VALC NE 0.<br>
    <br>
      LOOP AT VIT_SETLEAF1 INTO VFL_SETLEAF WHERE SETNAME EQ VFL_HIER-NNAME.<br>
    <br>
        VFL_HIER1-PID = VFL_HIER-NID.<br>
        VFL_HIER1-HID = VFL_HIER-HID.<br>
        VFL_HIER1-IOBJ = IOBJ.<br>
        VFL_HIER1-DESC = VFL_SETLEAF-LTEXT.<br>
    <br>
        SELECT KOKRS KSTAR DATBI INTO TABLE VIT_CSKB<br>
               FROM CSKB<br>
               WHERE KSTAR EQ VFL_SETLEAF-VALFROM.<br>
    <br>
        LOOP AT VIT_CSKB INTO VFL_CSKB WHERE DATBI GE SY-DATUM.<br>
    <br>
          VFL_HIER1-NID = NID.<br>
    <br>
          CONCATENATE VFL_CSKB-KOKRS VFL_SETLEAF-VALFROM INTO CSTEL.<br>
    <br>
          VFL_HIER1-NNAME = CSTEL.<br>
          NID = NID + 1.<br>
    <br>
          APPEND VFL_HIER1 TO VIT_HIER.<br>
    <br>
          CLEAR: VFL_CSKB.<br>
    <br>
        ENDLOOP.<br>
    <br>
        CLEAR: VFL_SETLEAF, VFL_HIER1.<br>
    <br>
      ENDLOOP.<br>
    <br>
      CLEAR VIT_SETLEAF[].<br>
    <br>
    ENDLOOP.<br>
    <br>
    <br>
    LOOP AT VIT_HIER INTO VFL_HIER.<br>
    <br>
      NHID = VFL_HIER-HID.<br>
      NVALC = VFL_HIER-VALC.<br>
    <br>
      CONCATENATE VFL_HIER-NID ';' VFL_HIER-IOBJ ';' '"' VFL_HIER-NNAME '"'<br>
                  ';' ';' VFL_HIER-PID ';' ';' ';' 'N' ';'<br>
                  '"' VFL_HIER-DESC '"' ';' '"' VFL_HIER-DESC '"' ';'<br>
                  '"' VFL_HIER-DESC '"' INTO OUT.<br>
    <br>
      VFL_FINAL-OUT = OUT.<br>
      APPEND VFL_FINAL TO VIT_FINAL.<br>
      CLEAR VFL_FINAL.<br>
    <br>
    ENDLOOP.<br>
    <br>
    CALL FUNCTION 'GUI_DOWNLOAD'<br>
    EXPORTING<br>
      filename = 'hierarchy.csv'<br>
    TABLES<br>
      data_tab = VIT_FINAL<br>
    EXCEPTIONS<br>
      OTHERS   = 1.<br>
    <br>
    Edited by: Bjorn Houben on Dec 28, 2009 2:07 PM
    Edited by: Bjorn Houben on Dec 28, 2009 2:16 PM
    Edited by: Bjorn Houben on Dec 28, 2009 2:16 PM

  • BW: Cost Element Hierarchy - from R/3 plus additional node in BW

    Hi all,
    We have cost element hierarchy (say ZP14PL) which we schedule to update periodically from R/3 into BW . However we would like to add an additional sub-node under this same hierachy via RSH1.  As this subnode is only for BW use, this is not maintained in the hierarchy ZP14PL in R/3.   With the 'full update' or 'update Subtree' option in the infopackage the hierachy ZP14PL will be deleted and replaced with the latest changes thus removing the additional node which we created for BW only.
    Any suggestion as to how we could have the latest hierarchy updated from R/3 without deleting the additional subnode that we added in the same hierachy in BW?
    Appreciate all expert advice.
    Thanks and best regards,
    VC

    An easy way would be to include this link into the file using a start routine....
    you should know the child node and parent nodes for the same and since the location of the same is going to be constant - you could add it to your start routine....
    Or have a time dependent hierarchy but that would mess up your reporting...
    Also this is not the correct forum to post BI relevant questions - suggest you post the same in the BI forums for more relevant answers....
    Arun
    Message was edited by:
            Arun Varadarajan
    [message moved to BI]

  • Cost Center and Cost Element Hierarchy and Actual Cost Center

    In Bex - Right now I am displaying Cost Center and Cost Element hierarchy with 12 months of data. I want to display the actual Cost center number next to cost element hierarchy - Can I display in Bex?
    Tried to with Structure creating formula variable for Cost Center using replacement path - didn't work. Can you please suggest me how i can achieve this?
    The format should be
    CostCenter H1   CostElement H1   CostCenter   Jan  Feb ...
    Thanks in advance and appreciate for any help...

    Let me explain it clearly and hope it is clear now...
    Designed the report as like this - Cost Center Hierarchy by Cost Element Hierarchy for 12 months of data. But Business agian search in R/3 for actual cost center numbers based on above two hierarchy nodes.
    I am trying to achieve this Bex instead of going back to R/3 - so that they can understand how the dollar amount is summed up on which major cost centers.
    If I remove the hierarchy on Cost Center - it will display all the cost centers. They want to see the Cost center numbers based on CC and CE hierarchy node so that you are displaying only those cost centers. That's the reason I am trying to design the  report with CC Hier, CE hier, Cost Center number and 12 months of data.
    In my data model - have only one Cost Center, if i can create another ZCOSTCENTER same as 0COSTCENTER - May be I can achieve this. still looking for options with out changing the design.

  • Loading cost element hierarchy

    Hello experts,
    I have got 2 questions
    1)  I am trying to load cost element hierarchy and there are about a 100 hierarchies which i need to load.. do i have to manually select all of these one by one to load  or is there an easier way to do it ?? is there a way to select all the hierarchies which are showing up in the Infopackage selection.
    2) Now lets say there is a change to one of the hierarchies which i have loaded...let's say a new account group has been added to a particular hierarchy which i have already loaded? Do i have to reload that particular hierarchy manually ?? Is there anyway to automate this process ?? like loading the hierarchies automatically from time to time so that whatever changes have been made to the hierarchy in R/3 are being taken into account when the query is run.
    Thanks,
    Bose

    Hi,
    As Eric has mentioned, there is no other ways but to create 1 infopackage for each of the hierarchy. 
    However, I think there must be some relationship with the 100 hierarchies you have.  From what I know, in R3, if I have the following hierarchy
    PnL
    |- EBITDA
       |-- Net Cost
           |- Gross Operating Expenses
           |- Salary/Oncosts
       |-- Gross Margin
    And when you create an infopackage in BW for this hierarchy of characteristic 0COSTELMNT, potentially you'll be seeing hierarchies for PnL, EBITDA, Net Cost, Gross Operating Expenses etc..... So sometimes it does not mean that you have to create 1 infopackage for each of these.... you simply have to select the PnL in this case.
    Suggest that you check with you FI/CO colleague and see which is the main hierarchy...
    Hope this helps.
    Cheers,
    Gimmo

  • Webi report on OLAP Bex query -  Cost element Hierarchy not working Drill down

    Hello,
    We have a BO report on Bex query, Not on universe, we have a Hierarchy for Cost Element Group, and we are expecting the Drill down functionality for that in BO report, but it does not.
    Webi report on OLAP Bex query -  Cost element Hierarchy not working Drill down
    Any pointers how to do it please
    Thanks
    Krishna

    Hi,
    WebI reports on BEx source don't use same Drill feature as other sources, it's replaced by expland/collapse of hierarchy nodes (documented in WebI user guide in § "24.1 Drill defined"). This means you have to create query which selects all hierarchy sub-tree you plan on exploring later in report, otherwise if no data is available under a node there will be no '+/-' sign to visit this part of tree.
    You could try first to select "All members" from hierarchy in QueryPanel and see if behavior in report suits your needs. Then you should restrict hierarchy member selection to what's really needed to avoid performance issues.
    Regards,
    Loic

  • Cost element hierarchy stored in which table..

    Hi Experts,
    could you please tell me which tables are storing the cost element hierarchy, which is displayed
    in KAS3 hierarchy...like cost center group hierarchy is stored in SETNODE , which is displayed in
    KSH3 transaction.
    Thanks.

    Check these tables.
    TKZU1
    EVCE
    TPIK2
    TPIK3
    TORB1

  • AFAB asking for new cost elements not used before.

    AFAB returns error indicating a range of cost elements that was not existing in the previous system and in the new system (ECC6) as well.
    I like to know why this error when it is not being used and how to rectify to allow AFAB.

    Hi,
    Cost elements does not exsist so there is no question of validity in master data.
    It is asking to create cost elements. So, i want to know why the system is asking or from where it is picking up?
    We have not used this cost elements before.

  • Query Cost Center and Cost Element Hierarchy

    here is the problem.
    We are trying to build a query that does the following.
    Its a CCA query.
    We have Costcenter in the Filter area with a Hierarchy assigned and a hierarchy node variable attached.
    We run the report and its looks good and the user cannot drill down because nothing is in the "rows" area. Its perfect.
    Now the user has said that within that Costcenter Hierarchy we only want to see a total number based on the CostElement Hierarachy assigned. Different CostElement Hierarchys are valid for different times of the budget.
    I have created a Hierarchy variable and attached it to the CostElement.
    Here is The issue ****
    If I drop the Costelement in the "rows"area it prompts for the Hierarchy name , filters Costcenter properly and provides the extact number. Problem is the user can now drill down and that is not allowed becuase we are going to have 3 summary totals with a "grand total" at the bottom.
    So if I put the CostElement in the Filter area it now does not filter the CostCenter and I get the wrong number.
    Is there a way to prevent drill down or some how force the CostCenter to be filtered by CostElement also.
    Thanks for any help
    Richard

    Hi Richard,
    Not sure if this will help as I have not tried it out, but you can try by setting the display property of Cost Element to No Display, when it is in the Rows area. This can be done by Cost Element > Right Click > Display As > No Display.
    Hope this helps...

  • Based cost element I need to find cost element group how

    hi
    how to find the cost element assigned to which cost element group,very difficult to open each group and search, please advise me
    Regards,
    Nagesh

    Hi,
    One easier way is goto T.Code: GS03, give the top node of the Cost Element Group then, drill down for lowest level details.
    This could also be faster process.
    Regards,
    Kiron Kumar T.

  • New cost element group creation + PMCO recreation

    Hello,
    I got the request from business that subgroup GPG1OTHE should be excluded from the main cost center group GPG1OTHT1 (KAH2). Then subgroup GPG1OTHE should be assigned to newly created value category 'Other, Maintenance' (this will be done in PM SPRO)
    Request execution is not complected but wondering whether after this I should 'recreate' PMCO table using one of those reports - RIPMCO00 or RIPMS001?
    Thanks in advance for all your clues.
    Grzegorz

    Grzegorz,
      You would need to execute the report only if you want to move the costs on the old orders to this new value category.If you are only concerned with new orders then you wouldn't need to execute this report.
    Regards
    Narasimhan

  • Cost element hierarchy

    I need to create the ECC account hierarchy table for which somebody mentioned that I need to use bapi_costelementgrp_getdetail. I am using Informatica for this. Any ideas?
    thanks

    Ajay,
    Thanks for you suggestion. Unfortunately it wont work in my case. The problem I have is with Hierarchy node key value. The hierarchy key itself is in that format in R/3.
    XXXXAAA
    XXXXBBB
    Since they are compounded, I can't seperate during the load. I am trying to change the display. Every one suggested to put the controlling area in the filter section and restrict it with one value and this should work.
    I tried that, but it didn't work for me. I am not sure what I am missing. As I mentioned already I tried the option Abdul suggested.
    Thanks
    Sri
    Message was edited by: Sri Vani

Maybe you are looking for