extraction of metadata (shared members) of essbase

Similar Questions

• Essbase do not move members but creates rather shared members

  Suddenly, this problem appeared for the November statement. I've never met before.
  
  Updated structures from flat files using rule Essbase files do not move members to their new parents but creates rather shared members.
  Previously, Essbase moved members.
  
  In the rules file, we have the 'Allow moves' disabled option because some shared members need to be created. If we choose this no shared members are created since Essbase moves key members at the locations of where the shared members are supposed to be.
  
  Any help would be appreciated.

  That's why you need two sources of metadata:
  (1) only members. Linking to a modified charge rule allowing movements.
  (2) only members with their shared summaries. Use the same rule of ancient office which does not allow for movements and thus pushing them towards a shared hierarchy.

  I still wonder how it still worked. Something changed - what is it?

  Kind regards

  Cameron Lackpour

• Essbase dimension build shared members

  Hello

  I will have questions and he drives me crazy!

  I'm building a dimension using parent child references. The first generation of dimension puts members stored in place. The second generation implements the shared members. I am not getting any errors and still 'shared' members are not being built with shared member label. Documentation, I was under the impression that essbase should realize that they are shared and mark them accordingly during the generation of dimension?

  I can go through and manually set the shared in EA after than the build... but it kind of defeats the object.

  I feel I missed something just really hehe. Any help would be appreciated.

  Thank you

  Russell

  The only time where the outline you would save with members not be labeled as hared, is that if you have names of members in double lit in the sketch, otherwise you will get errors.  One thing you can check in the generation of dimension properties is that you do shared members is more verified and allow moves is not checked

• When exporting data to essbase with L0 members, shared members are also get exported.

  Hi, when exporting data to essbase with L0 members, shared members are also get exported.

  But I don't want to export another hierarchy!

  Example:

  project

  XYZ +.

  ABCD +.

  P00001 +.

  p00002 +.

  GFE +.

  p00003 +.

  p00004 +.

  all the xyz (Label only)

  ABCD (shared member)

  EFG (shared member)

  I want data to be exported only with P00001, 2, 3, 4.

  I think that the OP cannot use Level0 in DATAEXPORTOPTIONS, because not all dimensions are zero-level.

  Cameron, thanks - Yes, it's the behavior of the OP is seen (and disliking).  The share of 'level zero' which is in fact not level zero (in the primary hierarchy) is included in the output.  I think it's the problem rather than replication / repetition.

• Issue of journal error Essbase for shared members

  I'm loading Shared members in a dimension custom in Essbase.
  
  Error log is created is as below.
  
  \\Record #1 - WARNING: account only of attributes can be defined in dimensions non-comptes
  PR0011, APP_PR, shared members,
  
  But this specific member is to take.
  
  I am only a member shared in this charge of loading and all records are displayed in form of get rejected even if most of them is to take. It is initially questions in discovering the real releases.
  
  -app

  Hi, check this box

  http://oraclebizint.WordPress.com/2008/12/14/Hyperion-Essbase-931-OBE-series-designing-Essbase-databases-BSO-outlines-data-load-global-schema-part-2-building-dimensions/

  When the generation of dimension set no parameters allow property moves and use parent/child references

  I tested it and it works

  Concerning

• Moving shared members

  Gurus,

  Background:

  I update the metadata in application of ASO using loading rules. We use 2 rules of loading for a dimension

  1. for principal members of updating\creating (movements to allow is enabled)

  2. for members shared (Allow moves is OFF, as when turned on, it will move members)

  I have a single source file and how these rules of 2 load the distinction between primary & shared members is by checking 'StorageField' in the source file. (Select / option in the State of load rejection)

  v (11.1.2.2)

  Question:

  I need to move the members in the hierarchy. 'Allow the movement' moves the main members of the place where I want to create shared members.

  Please let me know if there is a way to move the members shared through charge rule above scenario or I have to do it manually.

  Thank you

  ~ RN.

  In the first rule load are reload you the hierarchy full (excluding the shared members), if you are then you could use delete option not specified in the rule of the load then it will remove all members not to load and you can rebuild shared members.

  See you soon

  John

• shared members disappear automatically after the deployment of the ASO cube

  Hello

  What we were doing as below:

  
  the memerbers dimension are loaded by source for epma odi, and then, we deploy the aso and epma bso cubes.

  and the process type in the profile to load dimension members is defined as "merge as primary.

  
  

  the question as below:

  (1) initially, the hierarchy of the dimension as it:

  size AA:

  A

  A1

  A2

  A3

  This dimension is aso and aso cube deployed successfully.

  (2) the users change the hierarchy of the source table.

  changed to below: (just add a parent for A1 and A2 under A initial parent.

  A

  A'

  A1

  A2

  A3

  AFTE, this changes, and members are responsible for epma once again, the hierarhy of dimension in epma is as below:

  A

  A'

  A1

  A2

  A1 (Shared)

  A2 (Shared)

  A3

  and this process of loading and applications deploy processes run automatically overnight pocess.

  I thought that I delete the A1 A2 shared hierarchy and deploy the cube again after overnight charge and deploy processes.

  But what I saw in the structure of the aso cube after the party deployed the process is also that:

  There no common A2 A1 in the sketch, but just below members in the cube hierarchy in essbase.

  A

  A'

  A1

  A2

  A3

  It's really weird, why shared members disappear automatically after deploy and make different hierarchy between epma an essbase outline

  can you help me?

  I have no idea...

  EPMA is ASO-> size is set to "multiple hierarchies enabled" otherwise please turn on and then try to deploy.

  Thank you

  ~ KKT ~.

• Alias for the shared members in Smartview

  Hi gurus,

  I use Oracle EMP 11.1.2.3. I've migrated a planning 11.1.2.2 EPMA demand 11.1.2.3. The Alias for the shared members are not displayed when I go via Smartview, instead, is to show as [Parent]. [child]. But when I access the same application in 11.1.2.2, I can see the Alias.

  How to solve this problem?

  He was identified as a bug reading of this Oracle - Hyperion... Labs: Smart View issues with another hierarchy - Surprises in the fifth part of Essbase

  Concerning

  Celvin

  http://www.orahyplabs.com

• Creating shared members through EAS load rule with duplicates allowed

  I'm building my first Essbase cube where I need to activate "allow duplicate member name" in the outline. I have trouble finding a way to get the shared members added to the outline via a rule of the load. I tried to run my load of rules that I used before I activated the "allow duplicates" setting, but it does not work now. It creates members in double, which makes sense to me. I don't see a setting that I can turn to get the shared members added via load rules however.
  
  Help?
  
  Thank you...
  
  Bill

  In your workload file, you will need to use full qualified member names or load rule allows to transform members to the full qualified member names.

  Go to this link and read the sections below

  http://download.Oracle.com/docs/CD/E10530_01/doc/EPM.931/html_esb_dbag/frameset.htm?dotdimb.htm

  Strengthening of the members to double outlines
  Identifies the members via the rules file
  File qualified member names through the rules of construction

• Multiple hierarchies with shared members

  Hello
  
  is it just a common practice to have single parents for hierarchies that are built on the same size of Essbase, or it is a restriction of system-level?
  Only in Hyperion Planning, or this is true also on Essbase level?
  
  Is it true that only the terminal nodes can be shared members?
  
  (automatic shared members are created on levels higher for parents with 1 child, then why the other shared not allowed?)
  
  Thank you for your answer!

  I'm not sure I follow your question completely, but for running sums of shared member, the lowest level of the rollup shared can be one zero level or upper limb or from another dimension. The condition is that a shared member can not have descendants in the shared rollup, it would be the level low.
  For example if I have the cumulative following primer

  Geography
  East
  NJ
  NY
  PA
  West
  It
  OR
  WA

  I have a cumulative alternamte as

  Total of Bob
  NY (shared)
  West (shared)

  You see thar NY is a level zero member and the West is a member of level 1, but under the cumulative replacement are both level zero members

• How do you get a @PARENTVAL in another hierarchy of shared members?

  Easy I know, but I couldn't find it.   I am looking for a way to get a @PARENTVAL in another hierarchy of shared members.  If I'm correct or check if the CURRMBR is a member of the alternative hierarchy, ancestor references will only be in this area?

  Yes, it is not the largest element of documentation ever.

  This is perhaps a more useful example.  In Sample.Basic, I created two members dynamic calc:

  "Sales of parent" formula: =@PARENTVAL ("product", "Sales");

  "Power Parent Sales" formula: =@SPARENTVAL ("Diet", "Sales");

  Results:

  

  'Régime' is another hierarchy.  Look at the values for the products below.  You can see that with @PARENTVAL, I always get the primary parent of hierarchy, but with @SPARENTVAL I choose the parent sales in a specified hierarchy.  Interesting to note that if the Member is not at all a part of the hierarchy 'Diet' @SPARENTVAL just gets the value of the hierarchy of the main.  It is perhaps which means that the ILO "closest to the basis of events '...  I expect a little #Missing if I ask @SPARENTVAL ("Diet", "Sales") for a product that does not appear in the hierarchy "Diet", but this isn't how it works, of course.

• 'Shared members' travel between parents

  Hello everyone:

  I know that it is possible to move the main members when using profiles to load dimensions of tables of the Interface. 'Merge as move' should be used to manage it. But, is it possible to configure a profile to move "members Shared" rather than "Main members"?. I have a main fixed hierarchy and another where 'Shared members' change its parent on a regular basis.

  How can I achieve this?

  Thank you

  Concerning

  Hello

  "Merge as Move" option will run only members who to true "IsPrimary.

  For your case, define the members of the hierarchy, replacing "IsPrimary' property as" true "and the main hierarchy as 'False'.» So for all parents to change on a regular basis for the hierarchy of the other, so that replacing the members of the hierarchy will be executed and moved to parent specified in the load file.

  I hope this helps.

  Kind regards
  Foudil

• Shared members and the consolidation process

  Hi guys,.
  
  I work to give support to a HFM application and I need some advice, because I'm a bit confused. I have 4 different graph of entities:
  
  (1) ComConsol
  (2) legal
  (3) BGroups
  (4) alternate
  
  I was trying to lock the ComConsol data in a grid when I realized that the status is CN. I have run the consolidation and status changed by OK. However, legal, BGroups and Deputy changed their status to CN. When I run the legal consolidation, then ComConsol must be consolidated again.
  I think it might be related to some shared members, but I'm not sure.
  Any advice?
  
  Thank you, guys.

  It seems to me that you run all consolidate them with data or consolidate all instead of consolidating on the parent entity? Other options, you force calculated a base entity or a rule executed affecting the State of one or more basic entities.

• Restrict users to shared members

  Hello
  
  We have a structure of dimension entity with another hierarchy. Users use excel component plug-in software to view the reports where they can see the base of these two members as well as the shared member. How we can prevent users to display shared members, because it is confusing to see two members at the same time.
  
  Thank you.

  Try:
  http://download.Oracle.com/docs/CD/E17236_01/EPM.1112/hp_admin/ch03s05s04.html

• Shared members

  Is it better to use members shared in the hierarchy of accounts or use the calculation rule.

  It is always best to handle all possible calculations using alternate hierarchies and shared in the account dimension members. Predetermined spare and shared members provide that visibility also reduces calculation time considerably