If consolidation/aggregation on level 0 members depends on his property in storage?

Similar Questions

• Any idea which function Essbase or a combination of function can be used to get the level zero members of a list of members.

  Any idea which function Essbase or a combination of function can be used to get the level zero members of a list of members. I know that @RELATIVE or @DESCENDANTS cannot be used.

  If you want to fix on all level 0 members in a member set, then maybe @ILDESCENDANTS will work for you.  Something like: @ILDESCENDANTS (@LIST (members), 0)

• Check the model of level 0 members and remove data

  Hi all

  I stuck everything by a script. Would appreciate any help.

  Here is the cost center hierarchy:

  -CC_NL

  -CC_NL_1

  -NL_10

  -NL_11

  -CC_NL_2

  -NL_20

  -NL_21

  -CC_NL_3

  -CC_NL_4

  --

  --

  --

  Now my requirement is:

  I have to check if Member of level 0 of CC_NL begins with CC_NL (i.e. CC_NL *), then delete this member of level 0 data. As in the hierarchy above CC_NL_1 and CC_NL_2 are not members of level 0 so no need to do anything other than CC_NL_3 and CC_NL_4 are members of level 0, so we need to delete the data present in it.

  I tried the above condition to the code below:

  FIX ("CC_NL")

  @MATCH ((@RELATIVE("CC_NL",0)), "CC_NL *")

  ENDFiX

  but it did not work as 'MATCH' fn require a member name and for that Member and its descendants, it will search the model. so above @RELATIVE("CC_NL",0) will not work because it will take members of level 0 and by definition Match fn does not work like that

  Appreciate pointers to solve the problem.

  Thank you

  How about you match and parent?

  Fix (@LEVMBRS(Market,0) AND @MATCH("Market","New*"))

  Concerning

  Celvin

• use of aggregation at level of the RPD

  Hello
  
  I would like to know one thing
  During the creation of the RPD, there is an option of aggregation for a column.
  
  But everything by creating a report, also if we drag the column and then change formula, we can do the same thing.
  
  So what is the advantage of making the RPD level?
  
  as I use a separate account for a column at the level of the RPD, but then I can do the same thing at value also
  
  I use obiee 11.1.1.5
  Thank you

  Hello

  Aggregate data at the level of the RPD will be aggregate data instead of having the data and their aggregation and in the responses. His suspected flush of good practices and the optimal implementation of aggregation to the RPD.
  And as said before, this column can be used in many reports in a single report.

  Hope this clears your doubt.

  Concerning
  Lajmi.

• Level 2 Funcitionally dependent and non-compliant

  I'm trying to create a dimension table, but get the following error when I try to add a dimension of the child:
  
  CPCI PS end Analyitcs MODEL BUSINESS:
  [nQSError: 15001] Could not load the navigation for CPCI PS end Analyitcs subject area.
  [nQSError: 15019] Table PeopleSoft END node tree depends functionally to level level 1 hierarchy of nodes, but a more detailed level of child associated with the columns of the same table or a more detailed picture.
  
  Here's the situation. I have a single physical table (table A), which contains the data that make up a hierarchy. This is the key of the fields: name of the node (1), (2) node levels (1 top - 9 low) and the name of the node (3). I want to create a dimension that allows me to come down from level 1 to level 9 for details of the node. Initially, I tried to put up to the drill just down from level 1 to level 2.
  
  What I did:
  (1) created two aliases Table A: 1a and 1B in the physical layer
  (2) created a complex join between tables 1a and 1B, where the Parent of 1 b node name = name of 1A and 1 b = 2 node level.
  (3) created a logical table and left the three fields (from above) table 1A for the logical table.
  (4) in the source of the logical table, I added the table 1 b as a new table and joined it, to 1, using a left outer join
  (5) added 3-column 1B to logic table
  Selected (6) create the logical table size
  
  This has created a dimension with 3 fields (6 in total) of 1A and 1B on the first level. I'm doing a consistency check on him past. However, I really want the 3 fields of 1 b to a dimension of the child.
  
  (7) I create a child dimension and drag the 3 fields level 1 to level 2 (child level) 1.
  (8) check consistency and I get the message at the top.
  
  I don't know why I can't do that. If you can help with this problem or provide an alternative, it would be useful.
  
  Thank you...

  Hello

  As I mentioned earlier your logical table key should be the level of your hierarchy. There is no need to do it as a key to the hierarchy. But we must add the lowest level. Add keys to the logical table to level down the hierarchy and checking the other things mentioned in the link provided in the previous post.

  Kind regards
  Sandeep

• How to get the consolidation at the level of the year-month?

  Hi experts,
  
  I have a column Date and quantity in the RPD. I created the column aggregated in RPD with aggregation Sum (the sum Qty)
  My report is to come in this format...
  
  Date of... Sum (Qty)
  -----------------------------------
  1/1/2009...5
  1/2/2009...4
  1/6/2009...10
  2/3/2009...2
  2/4/2009...6
  
  But I need the report like this...
  
  Year - my... Sum (Qty)
  ------------------------------------
  2009-01-19
  2009-02-8
  
  Help, please

  Hi bob,

  (1) create a logical column yyyy/mm format using col date

  CAST (EXTRACT (YEAR OF "Sample". » ». "" "" Samplesales '. "" Dim-Date '. (("" Start date ") as a CHARACTER (4)). '/' ||  BOX WHEN EXTRACT (MONTH OF "Sample". » ». "" "" Samplesales '. "" Dim-Date '. ("" Start date ") BETWEEN CAST and THEN 10 AND 12 (EXTRACT (MONTH OF"Sample". » ». "" "" Samplesales '. "" Dim-Date '. (("" Start date ") as a CHARACTER (2)) ELSE ' 0'.  CAST (EXTRACT (MONTH OF "Sample". » ». "" "" Samplesales '. "" Dim-Date '. (("" Start date ") as a CHARACTER (1)) END

  (2) to adjust the level of the aggregate/content on this column format (yyyy/mm) to the fact table

  Thank you
  saichand.v

• Date attribute error

  Hello

  I have 2 attributes of the dimension of type Date, and I entered the members in DD-MM-YYYY format like 01/07/1990.

  I made sure that the settings of Applications is now updated to DD-MM-YYYY and preferences is DD-MM-YYYY and even tried to restart the services but I always get the following error message when you try to validate/deploy the application:

  Error details

  =============

  Error: Validation failure 'Date of PlanningAttributeMember"Dimension"Opening Date"for the following reasons: Date of level 0 members should join the property of date format defined in the settings of the Application.

  Error: Failure of Dimension 'Closing Date' validation 'Date of PlanningAttributeMember' for the following reasons: Date of level 0 members should join the property of date format defined in the settings of the Application.

  No idea how to solve this problem, because it seems that the changes appear or something!

  Hello

  Is this an EPMA application? If so, have you checked the setting in the library of Dimension? If you select the application, it will show you the settings in the Properties window.

  Kind regards

  Philip Hulsebosch

• MDX function to return the descendants of level 0 for a list of members to ASO

  Hi all

  I'm having trouble writing MDX query to generate a list of the members of the level 0 members in a cube ASO. For the generation of the members of level 0 from a member of the same cube, I used DESCENDANTS([XXXXXX],10,LEAVES), but the problem using DESCENDANTS is that it can take only one member as a parameter. I'm looking for is an equivalent of @ILDESCENDANTS (from BSO) at ASO?

  Would appreciate any help.

  Thank you

  You can do this with Generate and Descendants.  It is similar to @EXPAND in OSB - take all members (tuples technically, but whatever) in a value and apply a second set-based operation.

  For example:

  {} SELECT ON COLUMNS.

  Generate ({[100], [200]}, Descendants ([Product].) CurrentMember, [Product]. Levels (0), SELF)) ON the LINES

  OF Sample.Basic;

• ASO level 0 member Consolidation ownership issue

  Hello
  
  I have a question in the codification of the ASO
  
  I have a dimension in this format
  
  Entity
  -100
  ----------------100-10 (+)
  ----------------100-20 (~)
  ----------------100-30 (+)
  
  -200
  ----------------200-10 (+)
  ----------------200-20 (~)
  ----------------200-30 (+)
  
  
  To provide "~" property of consolidation at a zero level member Aso, I need to implement the storage property parent as label only if I put in place as the label only it does not consolidate other children in this dimension. How should I deal with this issue
  
  Current value of 100 is equal to zero, but it must be a value equal to the sum of 100-10 and 100-30.
  
  What is the best way to achieve
  
  Thank you
  RK

  You can do this in a hierarchy of stored. You can do if you do the dynamic hierarchy, but bringing potentially a loss of performance.

  See also this thread for some suggestions on how to manage; someone else had a similar problem recently: Re: dérirez slow time in excel with ASO using 9.3.1

• DIFFICULTY level zero dimension dynamic Calc members

  According to the Guide of the Oracle: "dynamic calc members are ignored in a statement to FIX." If the only member in a statement to FIX is a dynamic member calc, an error message appears indicating that the FIX statement cannot contain a member dynamic calc. »
  
  However, I want to FIX on level zero members in the dimension of accounts: FIX("Accounts",0). If this dimension of accounts is dynamic calc (but 0 level accounts are STORED), this statement fix would work by running certain calculations level zero members account?
  
  JT

  Yes, as long as your HOTFIX includes at least a dynamically calculated member not that works perfectly.

  Either way, sometimes there may be no point for fixation on all members stored a dimension of dense - see my post in this thread (and more importantly, the post of Network54 related to it): Re: confusion of the theories of computation

• Input data of level 0 in planning Webform members

  I use the v11 planning. I created a form in line with "Account" (Dense) dimension in the column and scenario members online. All other dimensions are POV with members of level 0.
  
  
  When to open the online form to enter data, only level 0 members are editable.
  
  Y at - it an option where I can also an entry for the Non-niveau 0 members?
  
  
  Thank you
  Mathieu

  Hello

  Consult the following link: -.

  http://docs.Oracle.com/CD/E17236_01/EPM.1112/hp_admin_11122/frameset.htm?launch.html

  http://docs.Oracle.com/CD/E17236_01/EPM.1112/hp_admin_11122/frameset.htm?launch.html

  Go to Version of Dimension, select / Create the version to which you enter data on the level not zero members, click on edit and select 'Standard target' Version.

  I hope this helps.

  Concerning
  -SM

• Calculation of low level members

  Hi all
  I want to add the formula for low level member and I want to keep the storage as dynamic calculation type
  so that its values can be calculated from the meber of high level.
  
  But during this operation, I get this error
  "Data storage cannot be set to label only, dynamic Calc or dynamic Calc and store for periods in Multicurrency."
  
  and the members of lower level storage type is automatically changed to store.
  
  Can anyone suggest me how can I calculate the value of the Member at a lower level by using the values of members toplevel?
  
  Thank you

  Hi, Mirka, what version of hyperion and what OS are you using?

  Thank you.

• Parent of the values of the Member, not of compensation after removal of the child and running aggregations

  Dear users of Hyperion, we worked on a realignment of store, we are cut and paste shops from one region to the other. We moved all stores except X 1 parent 2 & X 2, so the total of these parents should now be zero. We have updated the cube and'd calc, however Parents always have $ values in them.  Can you please advise how we can fix this because it's doubly adding those numbers in our total entity level. Is there a problem with the type of the members of X 1 and X 2. If it's store or never share then, will not be clearly amounts even after aggregation? It can happen while in the case of stored or never share type of the members of the total still is there on the X 1 and X 2 parents? I'm trying to understand why the values do not go to zero once we got all out of these original parents and stores even after the execution of the aggregation? Please specify. Thank you. Regards, Praveen.

  Hey Praveen

  Glenn has practically put the nail on the head; We stumbled upon this specific scenario a few months back.

  Initially you had children less of X 1 and X 2 so both of these members hold securities aggregated and both of these members have a stored property.  You have moved the children in outline, the X 1 and X 2 have the same aggregated values stored against them.  You run an agg... because there is no child under X 1 and X 2, there is nothing grouped upward to clear the values of these two members and grouped together so the same values are always stored against them.

  Glenn's suggestion for the fix is the same approach that we had to take to resolve it.

  JB

• The label only at the Parent level

  Hello
  
  If we maintain the symbol of aggregation for all the level zero members as Addition and its parent company as the label only, then the aggregation occurs at the level parent?
  
  Thank you.

  Label should just show only the first child, so in theory, you should see the value for entrevues1

  See you soon

  John
  http://John-Goodwin.blogspot.com/

• Aggregation in the Calc Script

  Hello
  
  Can we gather (with the command of the AGG) any size up to a level? For example, if we have 5 divisions in the entity dimension, and these divisions are level 2 members in the dimension, then how can we obtain values aggregated at the level of the division rather than use AGG (Entity)?
  
  Thank you.

  Try

  DIFFICULTY (Jan FY10 forecast, Final,@IDESCENDANTS(Account,0), HSP_InputValue, Local)
  AGG (entity);
  @IDESCENDANTS (Seg01);
  ENDFIX