on 10-23-2015 12:21 PM
Hi guys,
We have a member formula in the account dimension as follows:
Iif([OBC_ORG_HIER].CURRENTMEMBER.PROPERTIES("GR_LINE")="301370",[SC_TOTAL],SUM(DESCENDANTS([OBC_ORG_HIER].CURRENTMEMBER,10,LEAVES),Iif([OBC_ORG_HIER].CURRENTMEMBER.PROPERTIES("GR_LINE")="301370",[SC_TOTAL],0)))
Basically we look at our current selection for org_hier (entity dimension) and we look for an attribute to be equal to 301370. If that's correct, then sum all transactions for that org member. Otherwise, look at all descendents of that member and sum the value for the leaves that verify this same condition.
This works fine on reports when you bring all org units that have this attribute = 301370. But when you bring a mix of org hier members on the report that make this condition true and false.... then it crashes giving us this error:
Any help on this guys?
Regards,
Iago
The logic of the member formula is strange and not clear... I recommend to use additional hierarchy in entity dimension instead of using property! Hierarchy is used for aggregation, not property!
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vadim
That wouldn't work. Imagine that in the entity dimension (OBC_ORG_HIER) we have Node A, Node B and Node C. Only node C is tagged with REP_LINE = 301370 and Node A is parent for B and C. When we report on Node A and Account= Account_Capex (the account with the member formula), we want to see the value for Node C. If we have a separate hierarchy, only Node C would be in that separate hierarchy and if we report on Node A, the result would be 0.
thanks anyways
The reason is that we need to aggregate from one account in one model to another aggregated account (GR_LINE) but based on this property in the entity dimension. We could do it with scriptlogic/abap when moving data from one cube to another, but they want to be able to report on the lower detail cube with GR_LINE as they have also other dimensions that are not included in the aggregated model. I assume the only solution here would be to include a logic in the default logic to calculate this.
User | Count |
---|---|
6 | |
5 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.