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
Tags: Business Intelligence
Similar Questions
-
'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 -
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
-
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 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 ~.
-
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
-
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
-
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.
-
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.
-
extraction of metadata (shared members) of essbase
Hi all
We try to extract metadata from essbase to oracle using the knowledge "LKM Hyperion essbase metadata to sql" module.
It works very well but we are unable to extract members shared this way, even if include us idescendants-, and then tap the top member in the dimension.
is there a way to extract the shared members?To extract, use ' ' LKM Hyperion essbase metadata SQL ' KM, I kept all of the default settings.
See you soon
John
http://John-Goodwin.blogspot.com/ -
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 -
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
-
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.
-appHi, 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
-
Hi all
I am trying to build a dimension with members of base and shared as well members. Now, I have disabled "permit already moves". But, when I launched the construction of the dimension, I end up adding the same members of the outline by replacing hierarchy but not marked as "shared member.
For example,.
I'm currently building below.
-Parent1
-Child1
-Parent2
-Child1(Shared Member)
wherever I get this.
-Parent1
-Child1
-Parent2
-Child1
Please suggest me what to do.
TIA,
Gerard.Hi Thr,
(1) you can use the Parent - Child as a method of generation, it will be autimatically creates a shared member that references the original member.
(2) If you use generation Buid and build level
(a) create a secondary hierarchy to the level of the parents of the shared members.
(b) in a seprate dimension version, add members shared down the hierarchy.
(these limits to the method where you can add share your hierarchies of members)Make sure:
(1) you have not selected DO NOT share in the Buid Dimesnion settings.
(2) your file is located in the Parent-child form.See you soon...!
Published by: Renu on May 31, 2010 08:20
-
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...
BillIn 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
Maybe you are looking for
-
I lost the shortcut for mozzila. How do I use it?
I accidentally lost the Mozilla application after creating a shortcut is pinned to the taskbar. I wanted to add to my startup. Please let me know how to solve this problem. I tried to reinstall, but who has not generated the actual application. I che
-
I try to send e-mail from wise direct to customers, but the emails only go to my Inbox. When I check every email they are sent to the customer using their email address and in the box of my address email is listed. I think I need to adjust the settin
-
You do not know if this is the right forum or not, but don't see anything similar to it. I am running Win 7, IE 8, and Norton 2010 on a HP s5310f... I tried several times to backup my computer to get rid ot reminders alert and constant, but nothing w
-
I've just upgraded to Ultimate, need help of activation, wants the different product ID?
-
DBMS_STREAMS_ADM. ADD_SCHEMA_RULES is blocked without any error
I encountered a problem that DBMS_STREAMS_ADM. ADD_SCHEMA_RULES has not returned for too long and I can't do any mistake when I use DBMS_STREAMS_ADM. ADD_SCHEMA_RULES to generate the capture downstream. All scripts are show in what follows. I'd appr