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...

Similar Messages

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

Parent member values in Fact tables

Hello,
I want to understand something, as far as I know, we can only send data to base level members, right ?
Then how come we find rows of data that have parent member values in the Fact tables ? (assuming we do not play manually with the database of course), I thought that this can be due to an import with the data manager, can this be right ?

nilanjan chatterjee wrote:
Hi,
>
> The data for the parent members should be available in the SQL tables.
> For example, 2011.TOTAL is parent member. You should not have any data for this member in your database. If it is there, it might have come somehow (may be an import). But this is not right. You might want to remove these records. But be sure that you dont delete the records for the base level members.
>
> Hope this helps.
I guess you meant should not, right ?

How can I create a dimension member formulas involving parent member?

Hi everyone,
I'm trying to learn BPC- Planning and I've got the following issue:
Behind each key figure is a calculated formula which will not be calculated in the aggregated parent member ( Energie Kosten). It's a IF formula based on percentage. As far as I understood it's not possible in BPC NW 10. to store values at parent level and parent member doesn't aggreagte child values that are calculated members. What can I do to solve the problem? The only solution will be the logic scripts?
Any input is appreciated.
Thank you!

Hi Vadim,
thank your for your answear.
Here it's my formula:
IIF([KENNZAHL].[S_PSTROM] = 0 , [KENNZAHL].[E_PSTROM] ,[KENNZAHL].[S_PSTROM] * ([KENNZAHL].[BELGES] *[KENNZAHL].[TAGEMON] ))
where: S_PSTROM = percentage key figure
         E_PSTROM = manual input key figure
         BELGES = allocation
         TAGEMON= days per month
The formula is used to calculate the energy. If there are adjustments used then will be calculated using the percentage if there are no adjustment needed that should take automatically the manually entered values.
It's used only a hierarchy- PARENTH1. And only the dimension without calculated members are calculated in nodes.
Thank you a lot!

Lookup on values (parent member) of other model

Hi everybody,
I have to get a value from one model within my application to save it in another model.
I tried to use the Lookup functionility of BPC but this doesn't work. I'm allways getting Zeros when I run the script.
Here is the code I used:
*LOOKUP MODELA
*DIM DATASRC = DS.TOTAL //Parent member
*DIM COMPANY = CO.2000 //Basemember
*DIM CURRENCY = USD //Basemember
*DIM MAC: A_ACCOUNT = A.N001 //Parent member
*ENDLOOKUP
*LOOKUP MODELB
*DIM MBC: COMPANY = CO.2000 //Basemember
*DIM MBC: CURRENCY = USD //Basemember
*DIM MBC: DATASRC = DS.TOTAL //Parent member
*DIM MBC: B_ACCOUNT = B.N001 //Parent member
*DIM MBC: RANK = RA.N001 //Parent member
*DIM MBC: NATIONALITY = NA.N001 //Parent member
*ENDLOOKUP
*SELECT(%CPTLF%,ID,CATEGORY,RUN_LOGIC = Y AND CALC = N)
*SELECT(%CPTPC%,ID,PROFIT_CENTRE,CALC = N)
*SELECT(%CPTFC%,ID,TIME,ACT_FOR = F AND LEVEL = MONTH AND CALC = N)
*XDIM_MEMBERSET A_ACCOUNT = A.1M406 //Specific Account
*XDIM_MEMBERSET PROFIT_CENTRE = %CPTPC%
*XDIM_MEMBERSET CATEGORY = %CPTLF%
*XDIM_MEMBERSET TIME = %CPTFC%
*XDIM_MEMBERSET COMPANY = CO.NA
*XDIM_MEMBERSET CURRENCY = USD
*XDIM_MEMBERSET DATASRC = CALC
*WHEN A_ACCOUNT
*IS A.1M406
*BEGIN
*REC(FACTOR = -(LOOKUP(MAC)+LOOKUP(MBC)),
DATASRC = CALC,A_ACCOUNT = A.10002,COMPANY = CO.2000)
*END
*ENDWHEN
When I run this script out of Model A everything seems to be working. But the Problem is that the lookup values for Model B are allways Zero. The strange thing is that this code worked last year correctly. This year the script doesn't calculates correctly. The difference is that we did a patch Level upgrade.
Regards
Derk

Hi Derk,
Now it's clear!
First of all - you script is executed in OPERATIONS - then first LOOKUP is better to replace with tuples! Like:
*LOOKUP MANNING
*DIM CPT: COMPANY = CO.2700
*DIM CPT: CURRENCY = USD
*DIM CPT: DATASRC = DS.TOTAL
*DIM CPT: MA_ACCOUNT = MA.N001
*DIM CPT: RANK = RA.N001
*DIM CPT: NATIONALITY = NA.N001
*ENDLOOKUP
*SELECT(%CPTLF%,ID,CATEGORY,RUN_LOGIC = Y AND CALC = N)
*SELECT(%CPTPC%,ID,PROFIT_CENTRE,CALC = N)
*SELECT(%CPTFC%,ID,TIME,ACT_FOR = F AND LEVEL = MONTH AND CALC = N)
*XDIM_MEMBERSET OP_ACCOUNT = OP.1M406 //Cost Pass Thru Income Type
*XDIM_MEMBERSET PROFIT_CENTRE = %CPTPC%
*XDIM_MEMBERSET CATEGORY = %CPTLF%
*XDIM_MEMBERSET TIME = %CPTFC%
*XDIM_MEMBERSET COMPANY = CO.NA
*XDIM_MEMBERSET CURRENCY = USD
*XDIM_MEMBERSET DATASRC = CALC
*WHEN OP_ACCOUNT
*IS * //already scoped to OP.1M406
*REC(FACTOR = -(([OP_ACCOUNT].[OP.N006],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+([OP_ACCOUNT].[OP.N011],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+([OP_ACCOUNT].[OP.N014],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+([OP_ACCOUNT].[OP.N034],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+([OP_ACCOUNT].[OP.N035],[COMPANY].[CO.2700],[DATASRC].[DS.TOTAL])+LOOKUP(CPT)),DATASRC = CALC,OP_ACCOUNT = OP.10002,COMPANY = CO.2700)
*ENDWHEN
Also it's necessary to understand which values can be missing in the cube... then different logic may be required!
Vadim

How to aggregate until parent member?

Hello all, How to calculate the parent member of the current member? Background: I want to offer users a limited dimension aggregation option. This to reduce the calculation time. Users are most interested in calculation of the level just above the input level. Therefore, I want to create the possibility to calculate the parent of the current member which is given with a prompt in Business Rules. I have been exploring the possibility of @PARENT or @ANCESTOR but I could not find a possibility (since I can not use them in a Fix statement). Do you see a possibility here? Philip Hulsebosch Trexco 

We perform YTD calculations via member formulas in our Period (time) dimension as follows.
P01YTD
"P01";
P02YTD
IF(@ISDESC("Headcount") OR @ISMBR("Exchange Rate"))
@AVG(SKIPNONE,"P01":"P02");
ELSEIF(@ISACCTYPE(FIRST))
"P01";
ELSEIF(@ISACCTYPE(LAST))
"P02";
ELSE
@SUM("P01":"P02");
ENDIF
(same logic used for P03YTD thru P11YTD)
and finally, P12YTD is simply
"Full Year";
Retrieve performance isn't great on monster spreadsheets, but otherwise it works reasonably well.
Hope this helps.

Error "Parent Member is found in dimension from selection"

Hi,
while running the export transaction data package we are getting the error " Parent Member is found in Dimension from selection".
We cannot manually select each member as there are around 64K records which will have to manually selected. Is there a work around for the same?
Regards
Varun

Hi Varun,
The first thing is that if you are using the standard export DM package, then you should not be able to select any parent members. If you look at the advanced script of this package, the first statement will be SELECTINPUT. This will restrict the selection only to base level members. Technically, you should not select the parent members, because, the parent lelve members doesnt hold any data.
Hope this helps.

Selecting a shared structure parent member

Good day,
With a calcscript im trying to select the parent member of a shared structure using commands @SANCESTVAL or @SPARENTVAL, however it works correctly for the 1st shared structure and it dosent work for the 2nd shared structure i have in the OTL. Does somebody knows if this is an expected behavior? Or a workaround?
Kind Regards,
P.d I can´t move the shared structures order, since i also have that type of calculations for the 1st structure.
P.d.2. I have essbase ver 11.1.1.3
Edited by: user618861 on Aug 30, 2010 1:53 AM

Hi,
We found the solution, we where doing something wrong, i will explain so this helps to somebody else.
I have 1 dimension "Products" with 3 Childrens; "Total_Product", "Brand_Segment", "Total_SupplyPoint", where the store structure is "Total_Product" and the others are shared structures.
We were trying to select Level 1 members of the "Total_Supply Point" with the following Script.
FIX(&Load_Mth, &Load_Year,&Load_Scenario, "Working", @REMOVE(@RELATIVE("Total_SupplyPoint",0), @LIST("SRC_KK01", "SRC_PMB3", "SRC_SF02")), "NA_Customer","YTD_Input")
"CM_YearEndBonus" = ("CM_COGS_Allocation" / @SANCESTVAL("Products", -1, "CM_COGS_Allocation")) * @SANCESTVAL("Products", -1, "CM_YearEndBonus");
ENDFIX
The correct calculations is as follows, where the only change is for SANCESTVAL Instead of "Products" know we have "Total_SupplyPoint"
FIX(&Load_Mth, &Load_Year,&Load_Scenario, "Working", @REMOVE(@RELATIVE("Total_SupplyPoint",0), @LIST("SRC_KK01", "SRC_PMB3", "SRC_SF02")), "NA_Customer","YTD_Input")
"CM_YearEndBonus" = ("CM_COGS_Allocation" / @SANCESTVAL("Total_SupplyPoint", -1, "CM_COGS_Allocation")) * @SANCESTVAL("Total_SupplyPoint", -1, "CM_YearEndBonus");
ENDFIX
The literature saids,
@SANCESTVAL (rootMbr,genLevNum [, mbrName])
Where rootMbr: Defines a member that is used to search for the nearest occurrence of an ancestor of a shared member.
I hope is helpful for somebody else
Edited by: Pavel Moreno on Aug 30, 2010 9:10 AM
Edited by: Pavel Moreno on Aug 30, 2010 9:11 AM

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

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

.

How to write parent member (TOTAL) to basemember?

Hi experts!
This code doesn't work. Why? Task is - write "TOTAL" member to another member.
*XDIM_MEMBERSET CATEGORY=ACTUAL
*XDIM_MEMBERSET MEASURES=PERIODIC
*XDIM_MEMBERSET RPTCURRENCY=USD
//KBO1000000 is parent node,ZCX1000000 is basemember
*XDIM_MEMBERSET KB_ACCT=KBO1000000,ZCX1000000
//TOTAL MEMBERS G100,E100 are parent nodes,EMPTY are basemembers which not included to G100 or E100
*XDIM_MEMBERSET P_CC=BAS(G100),EMPTY
*XDIM_MEMBERSET P_ENTITY=BAS(E100),EMPTY
*XDIM_MEMBERSET P_TIME=2010.JAN.01
*WHEN P_TIME
*IS 2010.JAN.01
*WHEN CATEGORY
*IS ACTUAL
*WHEN P_ENTITY
*IS E100
*WHEN P_CC
*IS G100
*WHEN KB_ACCT
*IS KBO1000000
*REC(EXPRESSION=%value%,KB_ACCT=ZCX1000000,P_TIME=2010.JAN.01,P_ENTITY=EMPTY,P_CC=EMPTY)
*ENDWHEN
*ENDWHEN
*ENDWHEN
*ENDWHEN
*ENDWHEN
*COMMIT

Tuple expression is used to write parent member to base member. try below code.
*XDIM_MEMBERSET CATEGORY=ACTUAL
*XDIM_MEMBERSET MEASURES=PERIODIC
*XDIM_MEMBERSET RPTCURRENCY=USD
//KBO1000000 is parent node,ZCX1000000 is basemember
//*XDIM_MEMBERSET KB_ACCT=KBO1000000,ZCX1000000
*XDIM_MEMBERSET KB_ACCT=ZCX1000000
//TOTAL MEMBERS G100,E100 are parent nodes,EMPTY are basemembers which not included to G100 or E100
//*XDIM_MEMBERSET P_CC=BAS(G100),EMPTY
//*XDIM_MEMBERSET P_ENTITY=BAS(E100),EMPTY
*XDIM_MEMBERSET P_CC=EMPTY
*XDIM_MEMBERSET P_ENTITY=EMPTY
*XDIM_MEMBERSET P_TIME=2010.JAN.01
*WHEN_REF_DATA=MASTER_DATA
*WHEN KB_ACCT
*IS ZCX1000000
*REC(EXPRESSION= ([KB_ACCT].[KBO1000000],[P_ENTITY].[E100],[P_CC].[G100]),P_ENTITY=EMPTY,P_CC=EMPTY)
*ENDWHEN
*COMMIT

Input in Parent Currency Level

Hi,
Is it possible to open input (without journal) in value other than "<Entity Currency"> ? For what dimension is it possible to open input? For what I know, it is possible to input in Entity. Is it possible also to open input in parent account , value other than <Entity Currency> (without journal), parent custom dimesion?
Thanks

Hi,
In HFM it is not possible to open input for parent members of any dimension. Regarding the Value dimension you can input numbers (other than journal) only in <Entity Currency>. Few exceptions exist:
1. You can input at the parent entity level (only in <Entity Currency>) provided that you write an Input() rule to activate specific point of view for input
2. You can also setup input to parent members of the Period dimension.
You can not input numbers in any parent account, parent ICP or parent custom.
--Kostas

GET 1 parent member

Hi expert,
in my script:
*XDim_Memberset Product = <ALL>
This will scan all of my children product only when i use WHEN/ENDWHEN...
but now i want include 1 parent member call : PD_SHEET only one !!
I dunt want use: *CALC_DUMMY_ORG Product=PARENTH1
because this will make my system scan all the parent member ..and i have 100++ parent member..
is there any idea??

Hi Chiam,
Since you're quite certain you only wanted to grab the value of 1 particular parent, i.e. PD_SHEET, i suggest that you hardcode the filtering of the PD_SHEET's children. I assume the necessary *SELECT and *XDIM_MEMBERSET statements have been done accordingly.
For example, assuming the children of PD_SHEET are:
1. PD_SHEET_Child1
2. PD_SHEET_Child2
3. PD_SHEET_Child3
Then in your script logic, you can do the following:
*WHEN PD_SHEET.ID
*IS "PD_SHEET_CHILD1","PD_SHEET_CHILD2","PD_SHEET_CHILD3"
*REC(EXPRESSION=%VALUE% ......)
*ENDWHEN
I believed you can also do the following:
*WHEN PRODUCT.PARENTH1
*IS "PD_SHEET"
*REC(EXPRESSION+%VALUE%......)
*ENDWHEN
You'll have to experiment with the last one, since the property PARENTH1 doesn't work with in some aspects of BPC, for example "Insert Member" in BPC Excel the last i checked, but in anycase the first logic though appearing clumsier, should work.
Cheers,
Lip Chean

Reporting: Parent entity level not able to view(Legal consol)

Hi friends,
Working on intercompany elimination using AUtomatic adjustments. Eliminations are happening correclty.
can it be possible to see data at consolidate entity/Parent level.
Rows: c_ACCT dim - BS items(Amount due from IC, Amount due to IC, IC elimination of ARAP)
Column1: Enity - 1000,1020,E_CG1000
column2: Group - G_CG1000
With above expansion, able to see elimination perfectly.
But when i try to include parent enity(CG1000) in column1 memberset, values are disappearing in EVDRE datarange.
i.e.Column1: Enity - CG1000,1000,1020,E_CG1000
How can see data in above fashion?
Properly defined hierarchy using dynamic hierarchy editor.
Groups dim.
ID | EVDESCRIPTION               | CuRRENCY_TYPE | ENTITY | GROUP_CURRENCY | PARENT_GROUp |     STORE_ENTITY     STORE_GROUP_CURR     CONSO_TYPE     DATASRC_LEVEL
G_CG1000 |SPA Group Consolidated | G |     E_CG1000          |USD             |     G_H1|     Y |     Y
G_CG1040 |SPA Ausi Consolidated      | G |     E_CG1040       |AUD             |G_CG1000 |     Y |     Y
G_H1 |Investments                | G |     E_H1               | USD                |     Y     Y |     Y     2010.DEC     Y
NON_GROUP |NOT A Consolidation Group Member (Used for Input data)|     N
Entity DIM
ID     |EVDESCRIPTION|           PARENTH1 |     CURRENCY|     ELIM |     INTCO     |ENABLEJRN     ELIMFILTER
E_H1     Investments               USD
H1     Investments               USD
CG1000     SPA Limited Group     H1     USD             Y
E_CG1000 SPA Limited Group Con CG1000     USD             Y
1000     SPA Limited            CG1000     USD                  IC1000     Y     Y
1010     SPA USA Inc            CG1000     USD                  IC1010     Y
1020     SPA Europe BV            CG1000     EUR                  IC1020     Y     Y
Regards,
Naresh

replaced old librfc32.dll file with new file..
issure resolved.

How to maintain the dimension member that had large amount (over 10K)

Hi, all,
I am now doing a Project Planning using BPC and had some questions as follows:
1. the total amount of the project memeber is huge (exceeding 10K in total). it will be crazy for the Administrator to maintain it only by himself. Is it possible that we can find a workaround method to let the end user to do the restricted work of administrator. in another word, can we find a way that prevent the end user to enter the Administration interface but can add the member themselves through the front end. the process work can be done in shcedule or by manually by the administrator? Anybody had the experience on this? Or do you have any alternative and workaround way to solve the problem?
2. the project memeber adding is not finished within one time. that means, in the first time, maybe only add the highest level. and later, adding the members under it. how can we manage it? Dynamic Hierachy or the others?
Thanks

You could also have the end user update a regular excel spreadsheet with the same column format as a membersheet. Easiest would be to save off the membersheet in another location accessible to the end user. Then it can be modified using excel. Or have the end user maintain a delimited flat file containing all the information included in a membersheet.
Using the bpc makedim package as a starting point, you can create a custom version that takes the user updated document as input and updates the bpc sql mbr table for that dimension then process the dimension. As long as the member list does not exceed the excel limitations, I would also suggest updating the membersheet in bpc. In previous implementations this has meant taking a copy of the membersheet, deleting it, coping a template with the correct columns, then adding the members into it. Updating excel spreadsheets from SSIS can be challenging if you have to deal with deleted members.
Also if you have the potential of deleted members that might have associated facts, I have another post concerning that issue, but have not had time to try any of the suggestions.
Now, the end user is responsible for updating the member list without having access to BPC Admin tool, but someone with access to run datamanager packages would have to execute the datamanager package to process the dimension.

How to copy data from parent member to children members?

Hello,
I'm entering data on a parent level in a form, and I'm running a rule to copy the data to the below children of the selected member.
It's running, but it's taking very long time. As I'm writing a normal member range having the children, and inside the script its having an equation of account=account->parent.
I know that the system template is very fast, but it copies only to one member. Can we use this copy template or any similar fast way to copy from each parent to the below children ?
Thank you.

Here below the script, it was working in 3 seconds before adding the copying to the "DIMX" dimension, although the parent i selected in the form contains only 7 children, so I don't know why it made things harder.. so, that's why I'm thinking of using something like the copy template or something.
The commands in the standard set used are:
SET LCOKBLOCK HIGH;
SET CACHE HIGH;
SET UPDATECALC OFF;
SET CLEARUPDATESTATUS OFF;
SET CALCPARALLEL 3;
SET AGGMISSING ON;
SET CREATENONMISSINGBLK ON;
%Script(name:="Standard Set Commands",application:="PRJ",plantype:="Plan1")
FIX
(/*DIM:Account*/"601010002","601010003","601010004","601010005","601010006","601010007","601010010","601010011","601010012","601010013","601010014","601010015","601010017","601010018","601010019","601010020","601010021","601020003","601020004","601020005","601030001","601030002","601030004","601030005","601030006","601030007","601030008","601030009","601030010","601030011","601030012","601010003","601010016","601030003",/*DIM:Entity*/@Relative({RTP_Entity},0),/*DIM:Currency*/"AED",/*DIM:DIMX*/@Relative({RTP_DIMX},0),/*DIM:Dim_Custom*/"DIM_7001")
FIX ( /*DIM:Periods*/&V_First_Forecast:&V_Last_Forecast,/*DIM:Years*/&V_CURRENT_YEAR, /*DIM:Scenario*/"Forecast")
/*STARTCOMPONENT:SCRIPT*/
Version
&V_WORKING_VERSION = &V_TARGET_VERSION->{RTP_Entity}->{RTP_DIMX};
/*ENDCOMPONENT*/
ENDFIX
FIX ( /*DIM:Periods*/&V_First_Budget:&V_Last_Budget,/*DIM:Years*/&V_BUDGET_YEAR, /*DIM:Scenario*/"Budget")
/*STARTCOMPONENT:SCRIPT*/
Version
&V_WORKING_VERSION = &V_TARGET_VERSION->{RTP_Entity}->{RTP_DIMX};
/*ENDCOMPONENT*/
ENDFIX
ENDFIX
Awaiting your feedback.
Thank you.
Edited by: user7304950 on Sep 14, 2012 7:41 AM

Parent member level rollups of amount

Similar Messages

Maybe you are looking for