Data not rolling up to Parent Level

Working on BPC 7.5 Level 10
Member set of report are on base level.
Data Present on 2014.AUG but not rolling up to parent.

Naveen,
I am storing Data with Periodic  Measures.
Jan          Feb          Mar          Q1
100          50                              0          --- Q1 will be 0 as your ACCTYPE is AST/LEQ
Now when i change the Measures in REPORT to YTD or Keep Periodic(By default AST and LEQ account type will refer to YTD).
Jan          Feb          Mar          Q1
100          50                             0
As per the logic explained by you
--> Data present for JAN,FEB on Periodic 100,50  - Yes . But when you say Feb Data is 50 it means your value has reduced from 100 in Jan to 50 in Feb which means the periodic value of Feb is -50. Dont get confused. For AST/LEQ value of 50 in Feb means the total balance till Feb is 50. You are getting 0 in Q1 as your March value has become 0 which means your total balance at the end of March is 0 and hence your Q1 ending March shows value 0. If you post something in March then your Q1 will show the same value. 
For AST/LEQ the Q1 value is same as the March value and Year.TOTAL value is same as Dec Value.
-->Data should be when YTD JAN,FEB 100,150. For AST/LEQ ACCTYPES Measure YTD and Periodic show same values as AST and LEQ are YTD in nature by default.
Nikhil

Similar Messages

  • Entity data in alternate rollup not rolling up to parent.

    We have a number of different entity hierarchies in our application.  In our main entity hierarchy we have system rules setup to pull specific account data down to STAT accounts for particular entities and then that same STAT account data is pulled over to another entity multiplied by -1 as an offset so when the two entities rollup to a common parent the result is 0.  This offset entity exists in other hierarchies.  In the other hierarchies this offset entity STA account data does not rollup to the parent.  The data only shows up to Parent Currency Total in the value dimension.  Anything above that is empty, but viewing the parent.child combo in the main hierarchy and we can see data populated all the way up to Contribution Total, therefore roling up to the parent.  Below is the rules we have setup.
    Here in simplier terms is what we see.
    Hierarchy 1
    Entity A = $10
    Entity B = -$10
    Parent Entity C = $0
    Hierarchy 2
    Entity B = -$10 (Entity A does not exist in this hierarchy)
    Parent Entity D = $0 (should be -$10)
    Has anyone see an issue like this before?
    Rule
    If HS.Scenario.Member <> "ProForma" Then
       If HS.Value.Member <> "[Elimination]" Then
      If HS.Entity.Member() = "E261" Then
       HS.Clear "A#AC90285"
       HS.Exp "A#AC90285 = A#AC76740"
       HS.Clear "A#AC90286"
       HS.Exp "A#AC90286 = A#AC70160"
      End If
      If HS.Entity.Member() = "E271" Then
       HS.Clear "A#AC90285"
       HS.Exp "A#AC90285 = A#AC76740"
       HS.Clear "A#AC90286"
       HS.Exp "A#AC90286 = A#AC70160"
      End If
    'E103 - Corporate offset
    If YearPOV > "2013" Then
      If EntityPOV = "E103" Then
       HS.Clear "A#AC90285"
       HS.Exp "A#AC90285.I#[ICP None] = (E#E300.A#AC90285.I#[ICP Top] + E#E104.A#AC90285.I#[ICP Top]) * (-1)"
       HS.Clear "A#AC90286"
       HS.Exp "A#AC90286.I#[ICP None] = (E#E300.A#AC90286.I#[ICP Top] + E#E104.A#AC90286.I#[ICP Top]) * (-1)"
       HS.Clear "A#AC90287"
       HS.Exp "A#AC90287.I#[ICP None] = (E#E300.A#AC90287.I#[ICP Top] + E#E104.A#AC90287.I#[ICP Top]) * (-1)"
       HS.Clear "A#AC90288"
       HS.Exp "A#AC90288.I#[ICP None] = (E#E300.A#AC90288.I#[ICP Top] + E#E104.A#AC90288.I#[ICP Top]) * (-1)"
      End If
      End If

    There are trigger account rules, but not for this scenario.  This also occurred before we added those rules.  If you see below in our main hierarchy E100 we have a corporate offset for -2,695,080 which goes against the data rolling up in E104 and E300.  In the secondary hierarchy only E103 exists with one other entity E428 and for some reason that offset data does not roll up to the parent E060.

  • Inactive component cost not rolled up to top level item

    Hi
    Our scenario is as follows: we have a top level item with a BOM. And some components of the BOM  are having material status u2018inactiveu2019. Inactive means materials will not procured and sold, however we could have inventory which can be consumed in production of other materials. In other words inactive items are like old items. These inactive items already have costing value. And we donu2019t want to recost inactive items.
    Having described above scenario, the requirement here is when we run costing for top level item, system should take costing value of inactive items  and roll up into top level item costing which is NOT happening now. Client donu2019t want to recost inactive items. The reason for not recosting inactive items is the recosting could change cost of inactive items significantly.  We are using 4.7 version and standard costing.
    Would appreciate any ideas or suggestions in this regard.
    thanx
    Sunil

    Thanks Young for the reply. 
    We already set 'do not cost' indicator for inactive components. And these inactive components do have standard costs valid up 10 12/31/2999.  It seems bom explosion is excluding these materials. it is ok to exclude. However the existing standard cost of these inactive components did not roll up in to top level. when I checked the costing status log, it says material ABCDF123 in plant 3344 has material status 40: Inactive.
    I checked BOM as well and inactive component is flagged as 'relevant for costing'.
    We are using following valuation varaiant
        Strategy Sequence ->  1. Planned Price 1    2.Standard Cost
        Transfer Control - Complete Transfer
    thnx

  • Data not rolling up of a dynamic calc member for a particular entity

    Hi,
    In my planning application data is not rolling up of a dynamic calc member for a particular entity whereas it is working fine for other entity.
    Please find below the sample Smartview Retrieve
    ----------------Member_ALL---Member_None---Member Top---Member_ALL---Member_None---Member Top
    ----------------Entity 1----------Entity 1------------Entity 1----------Entity 2----------Entity 2------------Entity 2
    Acc1------------100----------------#--------------------#---------------122---------------#-------------------122
    NOTE: # denotes missing
    Member_ALL and Member_None are children of Member_Top. Both Member_ALL and Member_Top are Dynamic Calc whereas Member_None is Store.
    As shown above data is rolling upto Member Top for entity 2 while it is not getting rolled up for Entity 1.
    Request you to please help in finding the error.
    Thanks in Advance'
    Joseph

    Hi Joseph,
    Is Acct 1 Dynamic Calc? In that case will it NOT calculate the combination MemberTop->Entity1 as Member_ALL->Entity1 + Member_None->Entity1.
    I beleive it'll calculate the Acct1 member again for Member Top based on the dynamic formula (whatever the logic). If you make it Acct1 Stored, then the aggregation will be correct by first calculating and storing the Acct1 member and then AGG the Member dimension.
    Cheers,
    Abhishek

  • EVDRE- Child member values not rolling up to Parent

    Dear Freinds,
    I am using 4 Hierarchy in Account DIM.  I am facing a problem that for second hierarchy child member values not summing up to Parent.
    Dimentioned processed sucessfully.
    Thanks ! in advance.

    Have you recently implemented EHP1?
    If so there is a common issue with the hierarchy tables - refer to OSS note 1139396
    Hope this helps

  • EIS - Delete members, have data still roll up to parents

    Hello everyone on the forums! I hope everyone reading this is doing well, or at least better than me.
    So I've read through all the documentation you can imagine to no avail. I'm running 9.3.1. What I'm trying to do is create an EIS job that has the data of the children of a certain member roll up to their parent without having the children show up in the cube itself.
    For example, let's say I have a level one parent 'New York' that has three and only three children: 'Brooklyn,' 'Queens,' and 'Manhattan.' Each child has a value of 100 at the intersections in question.
    What I want to do is have New York show up in the cube with the value of 300 for that intersection (one level up) without having the children in the cube. New York would thus become level zero.
    I've read that it may be possible via drill-through reporting, but I can't seem to find the right combination of level intersections and/or columns to choose.

    The table spells it all out, and I can identify the level 0 members. However, I do not want to filter out all the current level zero members, just the ones that fall under 'New York.'
    So, if New York has a sibling, Los Angeles, and Los Angeles has three children, Hollywood, Wilshire, and San Fernando, I still want them to show up in the cube. I only want their cousins at the same level (0) Manhattan, Queens, and Brooklyn removed.
    The application for this is to remove old members (products, locations, departments, etc.) that are no longer active, but whose balances are still meaningful for some point in the past. In the example above, this could be because the 'New York' division closed all three of its retail locations, but did not go out of business and might reopen them or relocate these retail locations to the Bronx or Staten Island.
    Thank you for taking the time to read my post and respond!

  • ASO aggregation Issue. Not rolling up to parents.

    hg
    Edited by: user7805819 on Jan 13, 2011 4:08 PM

    I don't have anything open to test syntax right now but something like
    Case
    When
    currentmember([Scenario]) is [Actual] and
    currentmember([Version]) is [Fina;] and
    ISlevel([Total Product].currentmember,0)
    and Not IS([Total Product].currentmember,[XXXXX])
    Then
    20
    When
    currentmember([Scenario]) is [Actual] and
    currentmember([Version]) is [Fina;] and
    NOT ISlevel([Total Product].currentmember,0) THEN
    sum([Total Product].currentmember.children,[measure])
    End
    where measure is the member name you are performaing the calculation on (where the 20 gets put). It has been a whild so you might need additional ({}) around the tuple to make it a set

  • Base level entities data is not rollup to parent level entity for few ac's

    Hi guys,
    Can some one pls help me i am not able to consolidate the base level entitys data to parent level for few accounts.
    remaining all accounts are consolidating to parent level entity from base level.
    Accounts which are not rolling up to parent level those accounts are few flow accounts and some accounts are Dynamic accounts.
    Thanks in advance............Pls revert me earliest........
    Rama.

    Guys this is HFM Consolidation hope there is no time balance settings in accounts attributes and we have not mentioned grouplabel to parent entity if that is the case it is as group label base entities will not aggrigate to parent entity but here few accounts are not aggrigating parent entity.
    Thanks / Rama

  • How to get label of Parent level nodes, when itemOpen() event of any node in AdvancedDataGrid in Flex?

    Hi all,
              This is the code, to get the label of every one parent level nodes, when we open the parent node item in AdvancedDataGrid in Flex.
    <?xml version="1.0"?><!-- dpcontrols/adg/SimpleGroupADGMXML.mxml --><mx:Application
    xmlns:mx="http://www.adobe.com/2006/mxml">
    <mx:Script>
    <![CDATA[
    import mx.controls.Alert; 
    import mx.events.AdvancedDataGridEvent; 
    import mx.collections.ArrayCollection; [
    Bindable] 
    private var groupData:ArrayCollection = new ArrayCollection([{Computer:
    "HardWare Devices", Device:"Keyboard", Company:
    "Logitech", PriceInRupees:"500"}, {Computer:
    "HardWare Devices", Device:"Keyboard", Company:
    "Microsoft", PriceInRupees:"500"},{Computer:
    "HardWare Devices", Device:"Mouse", Company:
    "Logitech", PriceInRupees:"300"},{Computer:
    "HardWare Devices", Device:"Mouse", Company:
    "Microsoft", PriceInRupees:"300"},{Computer:
    "HardWare Devices", Device:"Monitor", Company:
    "LG", PriceInRupees:"5000"},{Computer:
    "HardWare Devices", Device:"Monitor", Company:
    "Microsoft", PriceInRupees:"5000"}]);
    //This method is used to get label of every parent lavel nodes, when we open any item 
    private function getLabel(e:AdvancedDataGridEvent):void{
    Alert.show(e.item[
    "GroupLabel"]);}
    ]]>
    </mx:Script>
    <mx:Label text="NOTE : Open the every parent level nodes here. We can get the label of every one parent level nodes."color="
    blue" fontWeight="bold"/>
    <mx:AdvancedDataGrid id="groupADG" width="
    100%" height="437" initialize="gc.refresh();" itemOpen="getLabel(event)"
    >  
    <mx:dataProvider>
    <mx:GroupingCollection id="gc" source="{groupData}">
    <mx:grouping>
    <mx:Grouping>
    <mx:GroupingField name="Computer"/>
    <mx:GroupingField name="Device"/>
    </mx:Grouping>
    </mx:grouping>
    </mx:GroupingCollection>
    </mx:dataProvider>  
    <mx:columns>  
    <mx:AdvancedDataGridColumn headerText="
    Computer"/>
    <mx:AdvancedDataGridColumn dataField="Company"headerText="
    Company"/>
    <mx:AdvancedDataGridColumn dataField="PriceInRupees" headerText="PriceInRupees"/>
    </mx:columns>
    </mx:AdvancedDataGrid>

    Dialog\ResponseTime 6585
    "The dialog response time consists of the period of time from the request of the dialog to the dispatcher through the processing, to the ending of the dialog in the dispatcher and the transfer of the data to the presentation layer"
    This is not buffered as far as I know is measured on demand
    Read,
    http://help.sap.com/saphelp_nw70/helpdata/en/31/d7843b43c8e937e10000000a11402f/content.htm
    Regards
    Juan

  • ASO members with formula not rolling up

    Hi Gurus,
    In our ASO cube we have a members which caluclate % are not rolling up to parent . Its rolling up for MTD but they are not rolling for QTD . Members are in Account dimension .Please let me know if you require more info to get the excat idea .

    These are MDX formula members, right? Is the problem that the results are recalculated at the QTD level rather than the MTD level summing up the Period dimension?
    Is Period a stored dimension? The members / formulae in dynamic dimensions or hierarchies will always be calculated after roll-up of stored dimensions / hierarchies.
    See the section on 'Calculation Order' here: http://docs.oracle.com/cd/E26232_01/doc.11122/esb_dbag/alocare.html#alocare1058144
    If that is the problem you're seeing, the only options are a) to use an ASO calculation to derive the percentages as stored values, which can then roll up in stored hierarchies, or b) calculate the percentages outside of Essbase - in a relational staging area, for example.

  • BPC75NW: DM Package runs for parent level node

    Hi,
    I have build a DM package which has a variable input on ENTITY dimension. Now while I had built and unit tested on <ALL> ENTITY members, it took only base member values from the variable input.
    But when I test this again after sometime, the ENTITY variable took parent level members as well.
    I dont understand about this change as the DM package script code, and the LGF file is NOT CHANGED.
    Can anyone suggest the possibilities of why this should have happen ?
    Thanks,
    Pankaj

    Hi Nilanjan,
    The output members are the ones that are passed through the input scope.
    The logic does not generate/append a parent level member. As mentioned previously, the ABAP logic or the LGF is NOT CHANGED.
    Regards,
    Pankaj

  • Data at base level not consolidating to the parent entity

    HI All
    I have an issue with data which exisits at the base level but do not consolidate to its parent entity.
    For example,
    2000
    2001
    2002
    2003
    Here only 2002 has data, but that is not appearing at 2000. I have checked the accounts and there we have set the IsConsolidated property.
    The consolidation happens for other entities like 1000 & 3000. The problem is only with 2000.
    Has anyone come accross this before and what is the best way to fix this?
    Thanks,
    Appu

    Is it possible that you have not activated consolidation of the entities for the period you want to consolidate? Check out the Ownership Management screens for the entity 2000. Are all child entities set to Active? Is the proper Method set? Is the PCON = 100?
    Also have you tried to select one of the child entities (e.g. 2001) and run the Force Calculate Contribution? What does this entity return at the +[Contribution]+ level?

  • Advice on inserting data at parent level

    Hi experts,
    I would need some advice on how can I enter data at parent level. As we cannot enter data at parent level I am figuring out different strategies to do so. The one I seem to like the most is to create members representing the parents where we can input the data. For example:
    - 2008.Total (Parent)
        + 2008.Generic (Leaf)
        + 2008.Jan (Leaf)
        + 2008.Feb (Leaf)
        + etc....
    I would need to do this in different dimensions in my application. So here are the questions:
    1) Is there anything wrong about doing this?
    2) Is there a better option? (what is the Best Practice in this case?)
    3) In the case of doing this for the TIME dimension, there are some properties which value is not easy to set for those members (TIMEID, YEAR and LEVEL). I don't really know where and how those properties are used and the help doesn't help me much (what is the "time format required for Analysis Services"?). So what values have you used in these properties for such members?
    Thank you very much,
    Rafael

    Hi Rafael,
    What purpose is your application designed for? In a legal consol application, would never mess with the standard time dimension setup, in particular the time dimension. The setup of the Time.Level and Time.Year properties are very sensitive in the operation of some of the business rules, particularly the opening balances & account transformation rules (where there's a time-period offset functionality). I always try to retain the standard time dimension setup there.
    This means, for example, using a seperate datasrc member (or members) if the customer insists on having "13th period" for year-end adjustments. If they don't go into December along with the standard December values, then the carry-forward opening balances for the following year can be very tricky to calculate.
    If your application is purely analytics, or for planning, then you should still understand what business rules features you want to use before deciding the time dimension design. When I've had year-total input data, I either
    1.) use a standard 12-month time dimension, and by practice always put total-year data in December. Set up input schedules appropriately, and train people appropriately. Use Dec not Jan, or else the year-total and periodic/YTD computations in the cube won't work correctly. And consider your Account.Acctype carefully.
    2.) If the data is for annual values that aren't directly part of the P&L or B/S, and are things like allocation drivers, tax rates, inflation rates, stuff like that -- which doesn't get added up along with the monthly values to come to a total-year "full picture" -- then I follow the structure from the old Outlooksoft demo. Create each of your years with the standard 12 months. Then create
    Input.Year
    xxxx Input.Quarter
    xxxxxxxx 2008.Input
    xxxxxxxx 2009.Input
    xxxxxxxx 2010.Input
    etc.
    Then set your YEAR = 2008,LEVEL=MONTH for 2008.Input, etc.
    This approach works well in logic *LOOKUPs and also keeps the dimension structure clean & intuitive for end users. If you put your 2008.Input under 2008.Q1 or 2008.Q4, then every time someone lays out or drills down in a report, they will curse the designer, since they now need to remove that extra column of the 2008.Input member.
    With the datasrc approach for the "13th month" you can control whether the year-end adjustments are there or not, for those few reports where you'll want to see them. And 99% of the time, your time dimension "looks" normal.
    I'm sure there are other approaches beyond what I've discussed, but I've never gotten into trouble using one or both of these two.
    Regards,
    Tim

  • Loaidng data to Parent level using ERPi

    Hi All,
    We have a scenario that we have to load data from GL_Balance to Planning and HFM using ERPi at Parent level, is this possible to load data at parent level using ERPi..
    SVK

    FDM does not impose any rstrictions on what you can load into HFM it just respects the load constraints of the target system i.e. if you can't do something directly in HFM you won't be able to do it via FDM. In HFM data can only be loaded to base level members not parents, parents are calculated and are not stored i the HFM database. Therefore you will not be able to load to parent level members in HFM. You can sometimes have excptoions to this but only if the HFM developer has written specific rules to allow this.

  • Header data not getting updated in line item level

    Hi,
    We are trying to update Pricing date at header level but it is not gettting copied to item level.
    getting an message "The header business data does not apply to item xxxx"
    i have checked the item category and "business item" field is checked. and for the same sales order previously we were able to change the pricing date at header level and it got applied to item level but this time is is not getting applied.
    kindly suggest.

    If there are multiple line items which are having different data; in your case, Pricing Date, then in that case, when you try to change at header level, system will pop up this message.
    You can also have a look at the following note:-
    Note 336660 - Message V1403 in sales order with article order no
    G. Lakshmipathi

Maybe you are looking for