Parent level rollups of amount

I have dimension formula in base level members of account and values are properly being calculated in base level.
But these values are not being properly rolled up in to parent account in the report.
Is someone is experiencing same issue in BPC7NW.
This issue is not in BPC5.1, What is the solution for this?
Is there any workaround.
Appreciate your inputs..

Hi,
This is one of big diference between Microsoft version and NW version.
Any dimension formula will not be propagate to parenth.
I mean
A1 is parenth for A2 and and A2 has a formula then the value from A2 will not be propagate to A1.
The work around is to move the dimension formula into script logic.
In this way actually the value will be stored and it wil be propagate to parenth.
I suggest you to input into default logic a formula that every time when a member from formula will be changed then you have to run the calculation for this member and to post data into database.
In this way this member (which previous had dimension formula) will be calculated all the time and always you will have the good value into this member but also into parents of this member.
Regards
Sorin Radulescu

Similar Messages

Parent member level rollups of amount

I have dimension formula in base level members of account and values are properly being calculated in base level.
But these values are not being properly rolled up in to parent account in the report.
Is someone is experiencing same issue in BPC7NW.
This issue is not in BPC5.1, What is the solution for this?
Is there any workaround.
Appreciate your inputs..

The issue closed...

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

Essbase parent level aggregation business rule for end users

Can someone provide me the basic syntax of a business rule to allow end users within Planning to run a run time prompt business to aggregate their responsibility level within a dimension like Cost Center? So for example, I want to allow a cost center manager to pick his parent level cost center and then run the aggregation script to rollup only his cost center expenses. I've tried to include AGG and CalcDim commands with various global variables to enable them to select the cost center fix point, but the aggregation doesn't seem to produce the right results. Anyone have a workable syntax for this?

If you are just trying to agg the children up to the parent it is even simplier I'll assume you are trying to roll up the company to some intermediate level
Say you have the outline
company
---East
------NY
-----NJ
---West
-----Ca
-----Az
and you want to roll up East you could do something like
FIX (FY10, Final, Actual)
@IDESCENDANTS("East");
ENDFIX
Of course I would add more into the fix to do the least work possible
The command Idescendants really means calculate all of the descendants of the selected member. I guess if you wanted to make it more efficient you could add the level command into it
like @idescendants("East"",-1) that would avoid looking for anything to do on the level zero members

Different way to aggregate Essbase: Cannot aggregate to parent level

Hi,
I used to use the following statement in BR to aggregate dimensions:
FIX("Segment Allocation Base")
FIX(@IDESCENDANTS("YearTotal"))
@IDESCENDANTS("Total Company"); /*Total Company is member of spare dimension: Market Segments */
ENDFIX
ENDFIX
The tree structure is like this:
Market Segments (Never Share)
|__ No Market Segments (Never Share)
|__ Total Company (Never Share)
|__Total Market Segments (Dynamic Calc)
|__SC (Store) -> Level 0
|__SE (Store) -> Level 0
1. However, I found that the parent level cannot be aggregated. After I enter a value for Total Company (I think I am creating a block for Total Company), the above BR works.
2. If I change the BR to the following statement, it works. I don't need to create the block first.
FIX("Segment Allocation Base")
FIX(@IDESCENDANTS("YearTotal"))
AGG("Market Segments");
ENDFIX
ENDFIX
Any gurus knows the difference about the above 2 different ways to aggregate? What's wrong with the first one?
Thank you in advance.
Casper

Unless you wrote the first statement wrong. The reason the first one doesn't calculate is because it does absolutely nothing
@idescendant is a declaration not a calculation
Definition of @idescendant is: Returns the specified member and either (1) all descendants of the specified member or (2) all descendants down to a specified generation or level. You can use this member set function as a parameter of another function, where that parameter is a list of members.
AGG is a calculation.
So unless I'm reading it wrong you declare the children of Total Company and then do absolutely nothing. Therefore it has nothing to do with dense/sparse or blocks existing or not.

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"?><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

Loading to Parent level Period using multiload template

Hi Experts,
Is it possible to load data to Parent level period using the FDM multiload template to HFM? Does multiload template allow loading of only the leaf level period?
Thanks
Kannan.

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.

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

VF03-- Header Level Cash Discount - Amount i.e. say, 3%, Where stores?

Hi Experts,
I am looking to pull the data of,
<b>VF03-----> Header Level Cash Discount - Amount i.e. say, 3%</b>
So, Where Can I get the Header level,
Cash Discount Amount data e.g. 3%
Thank you,

.

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

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.

ERPI: how to load only parent level metadata to Planning from EBS

Hi, experts.
Can we load only parent level metadata of EBS R12 to Planning using ERPI 11.1.2.2 ?
And can we make selections on which members to load its metadata to Planning ?
Thanks a lot.
Eddy

Hi,
     I m going with forecast in Step 5. But have to cross a pair of radio button in Step 3 as 'All Items' or 'Selected Items'.
     I m explaining my requirement again. I ll use the 'All Items' radio button and in the last step the recommendations are displayed for the expected child items along with the materials which are not in that specific BOM but has the demand.
     Though the other materials may have demand, it is not to be displayed in my order recommendation because I have not created the forecast for that items which I used in my MRP WIzard.
Hope you got my problem.
Thanks
Karthik

WRITE_BACK BADI for Parent Level Data Save

Hi Experts,
I am using write back badi for Parent level data saving in BPC 10, but my requirement is to save data at parent level for time period 2007.Q1 without segregating at corresponding base members level.
Is it possible so? if yes , please suggest.
I will highly appreciate for your quick response.
Regards,
Dipesh Mudras

Hi Dipesh,
BPC NetWeaver related questions should be posted in the corresponding forum, cf.
SAP Planning and Consolidation, version for SAP NetWeaver
Regards,
Gregor

System status TECO only on parent level.

Hi,
Following is my scenario.
This is how my project structure looks.
Level1 WBS1
Level2 WBS1.1
Level3 WBS1.1.1
Level3 WBS1.1.2
Now I had to make the system status TECO on level 1 i.e WBS1 but not on the child level.What I mean to say that I had to only make the System status TECO on parent level not on the child level.
Is there any function module where I had to make any enhancement or is there any configuration.I don't want to use User ststus here.
Regards,
Gagan

Mr.Mehra wrote:
make the System status TECO on parent level not on the child level.
I do not think it is possible, as TECO system status is a standard functionality. If you are looking for some business requirements then either use user status or some validation to achieve this.

Highlighting parent level navigation

Hi,
Can someone help me on how to highlight the parent level navigation when child level navigation is selected using idoc script?
Thank you,

Do you mean within Site Studio?
If I remember correctly...
SiteStudioNavNodes resultset should contain the list of all the nodes in the hierarchy.
So as you iterate through the navigation and build your markup you need to change the CSS class depending on this.
Tim

Parent level rollups of amount

Similar Messages

Maybe you are looking for