Shared member dimension build

I am trying to create a load rule that creates a shared member at a different generation. I looked at the dbag and it mentioned using the Parent/Child method with "Do Not Share" unchecked. But during testing, it moves the member instead of creating a shared member. Am I leaving something out? thanks

You cannot move shared members with a load rule. It will always end up moving the original member. What we had to do was to load a file with DummyParent DummyChild to delete all the members in the dimension (remove unspecified checked), and then rebuild the dimension with a new file where the shared member appears under its new parent.BKhanna

Similar Messages

  • Dimension Build File - Member Property Codes

    I am building a Dimension Build File.
    What is the code to create a Shared Member?
    I know the following codes:
    Code
    N Never Share
    O Label Only
    S Stored
    V Dynamic Calc and Store
    X Dynamic Calc
    Or is there a different way to specify a member as a Shared Member in the dimension build file?
    Thanks,
    Dave

    There is no property for a shared member. If you are using a parent/child build method it will automatically load shared members unless you specify don't share. To do a load as a level or generation build, you have to have the file in a particular order and use the dimension build tab of field properties. There is a section in the admin guide that shows you how to do it.
    But for using level builds it would be something like
    Lev 0, Product Lev 1, product Lev 2, Product Lev 1, product
    100-20 100 Products Diet Colas
    Notice how the second lev1 defines the alternate rollup and it would cause a shared member to be created

  • How to use Dimension Build to change member property?

    Hello,
    I have researched online on how to do this and I think i have an understanding but I cannot get it to work. My dimension build rules file is of type Parent Child. The fields are Parent, Child, Alias. I am looking to add a Property field to change the consolidation property to - for one member. I have checked off all the options required and tried several different ways but always come with the following error on that line.
    \\Record #95 - Child Member - with no parent (3331)
    P&L - ACC OPERATING Operating Expenses -
    order is:
    Parent Child Alias Property
    What i want to do is assign the - subtraction for consolidation on the OPERATING member. Can this be done with the Parent Child type dimension build? Could this be achieved automatically in another way?
    Thanks
    Alex

    Hey guys, thanks for the tips. The source file is tab delimited. I made sure there was a tab between Operating Expenses and the - for subtractions.  The lines look like so.
    REV_PROJ PS100001 - ACC PS100001 - ACC_PS-M9 Revenue Settlement
    REV_PROJ SC100000 - ACC SC100000 - ACC_SCS Revenue Settlement
    P&L - ACC OPERATING Operating Expenses -
    OPERATING LABOR Labour
    LABOR PAYROLL Payroll related
    I know they don't show the tab but it's there. I have the field set to Property for Account_Desc (Dimension im updating in the outline) with a value of 0. I have also checked off "Delete when the field is empty" as to not change the consolidation on the other lines. i guess i need to figure out why it's treating the final "-" as a member and not as a part of the same line holding it's property. Is there a EOL delimiter i should be setting?
    thanks again

  • Dimension Build - Change Member Names

    Does anybody know if there is a way to revise outline member names through a load rule without affecting (losing) the data associated with those members? I have a .txt file with the current parent names, child names, aliases, properties, formulas, attributes and UDAs for the Products dimension. I would like to revise all of the level 0 member names without having to do so manually in the outline. Any help would be appreciated.

    You can do this a couple of different ways.You can go into the outline itself through app manager, and witht he FILE drop down, update the outline at that point using your load rule.You could also automate this function with an esscomand script preforming and incremental dimension build (INCBUILDDIM).Randy Rehmer, Cincinnati Bell

  • Duplicate member names allowed dimension build

    I have turned on allow duplicate members in a current ASO essbase cube to test how much rework this will require to allow duplicate aliases.  After I switched the property on, I was recieving errors when attempting to associate an attribute to a dimension through a dimension build rule.  I realized that I needed to use qualified member names in the load file.  Here is an example of the file in Parent  Child  AttributeValue format
    [Domestic-PD].[Test_Comm-PD]     [Test_Comm-PD].[0001-PD]      [Test_Attr-MD].[Test1-MD]
    So I want to associate the attribue Test1-MD to product 0001-PD below.
    Domestic-PD
         Test_Comm-PD
              0001-PD
    What ends up happening is something like this
    Domestic-PD
         Test_Comm-PD
              0001-PD( [Test_Attr-MD].[Test1-MD]
              [Test_Comm-PD].[0001-PD]
    It attaches the attribute to the correct product but then adds an additional member.  I don't want it to add the additional member.  Any idea on what is happening?
    Thanks for any help!

    It ended up working in a different format.  I changed the data file to like below.  I also started over, recopying the outline, turning duplicate members on, so it is possible that there was just something off with the outline earlier.
    Test_Comm-PD     0001-PD      [Test_Attr-MD].[Test1-MD]
    It probably will have issues if there is a duplicate member but luckily I only will have duplicate aliases.

  • Dimension build rule file (Sort member)

    I am loading sorted data for one of the dimension. But its is not coming in sorted fashion in outline. New member which i am adding is always coming in The end.Even though that member is in sorted format in the file.
    I am using generation method . I am putting member for only generation 2 and its alias.I tried using ascending option but it is giving me error
    Can any body help me with this

    As Glenn said, the build only builds new members. In order to have FULL control over the order of a resultant dimension's order, you need to blank out the dimension first and then build via the load rule. As Glenn mentioned, you can do "incremental dimension building". You can do this directly in EAS in an interactive manner by using outline/update outline in pull downs. Just do not save the outline until all your changes are done. You can also accomplish incremental builds via Esscmd or via MaxL, but I'll assume for right now you are still testing. The advantages of the incremental changes is that you can do a number of changes before Essbase commits to doing a restructure, which is time consuming, not to mention confusing if you are "deleting" (however temporary) the entire dimension's hierarchy.
    Regarding setting ascending order
    1) in the load rule's Dimension Build Settings prompt
    2) Select Dimension Build Settings tab
    3) highlight the dimension you are changing
    4) select Ascending for sort order
    This should work...I've never had it error out. However, I will say that it sorts the entire dimension...not just the siblings of a new member. Your upper level members will move as well. Because of this, the ascending sort in a load rule is undesirable. Give it a try. If you don't like the results, just don't save the outline.
    Kevin

  • Ignore dimension build error Incorrect Parent For Member (3307)

    Hello,
    Is it possible to ignore the following error:
    Incorrect Parent [XYZ] For Member ABC (3307)
    The error appears because the member is in outline already. Is there a way to ignore that error?
    Thanks in advance

    The reason for the error is  you have multiple rows in your dimension build file with conflicting information.   One row says to associate the member with parent A and another row says to associate it with Parent B.   TimG's suggestion to set them ember to allow moves would get rid of the error, but the member will be associated with the last row in your data.   If you do not allow moves (as it appears you have) there is no way to turn off the error. In your case it is what I call a soft error, you know about it, but don't want to do anything about it.   I would suggest you clean up your data so it does not cause this issue. It is troublesome to me when the incoming data has this type of inconsistency and the solution is to ignore it

  • How to determine if shared member is descendant

    I have an account dimension that has several different alternate hierarchies. All of the leaf level accounts are in the Base Accounts hierarchy; these leaf members are then shared in the other hierarchies.<BR><BR>What I would like to do is build a calculated measure that performs a particular formula if the current member is a descendant of a specific member, say X. I have tried to use IsAncestor and also the Count(Intersect(Descendants())) formula, but it apparently doesn't consider the shared members at the bottom as a descendant of X. I have also tried adding a UDA to the members in question and using the IsUDA function, but again, I can't use UDAs on the shared members.<BR><BR>Note this is an ASO cube being built in EIS.<BR><BR>Is there a way to determine whether a shared member is a descendant of a particular member in a hierarchy?<BR><BR>Thanks,<BR><BR>Matt

    In general, shared members need careful handling in MDX. A couple of mechanical observations and a question.<BR><BR>Yup, there's a paradox at hand. The query <BR><BR> SELECT<BR> Filter (<BR> Descendants ( [Diet] ),<BR> IsAncestor ( [Product].CurrentMember, [Diet] )<BR> ) on axis (0)<BR> FROM [Sample.Basic]<BR><BR>returns an empty set, while the following formula only returns 1 for those shared versions that are in fact under the share, so the [100-20] under [Colas] does not get a 1.<BR><BR> Count (<BR> Intersect (<BR> { [Accounts].CurrentMember },<BR> Descendants (<BR> [[[Account Parent 1]]],<BR> [Accounts].Levels(0)<BR> ),<BR> ALL<BR> )<BR> )<BR><BR>Somehow, IsAncestor() returns FALSE even for members obtained as descendants of the Ancestor, while intersecting that member with the set of Descendants returns identity. But it's a different member somehow, since <BR><BR> Intersect (<BR> { [Accounts].Levels(0) },<BR> Descendants (<BR> [[[Account Parent 1]]],<BR> [Accounts].Levels(0)<BR> ),<BR> ALL<BR> )<BR><BR>only returns 1 instance of each member, not 2. Intersect(x,y, ALL) should return duplicates found in x when they exist. It seems like you can use Count(Intersect(Descendants())) for all "shared" versions of the member, but not the first, "non-shared" use of the member. Meanwhile, it would be great to avoid the set construction/counting overhead.<BR><BR>OK, enough of mechanics. What I'd like to inquire about is what you're trying to do. Are you trying to factor out logic into the shared parents, and then combine it based on what set of ancestors a member has? That would be clever, but maybe there's another approach. If you are trying to have different formulas for different shares, keep in mind that since a shared member is a shared instance of a member, it should have the same formula to calculate itself regardless of the parent it is under (since it is under all parents equally and simultaneously. A little more insight into your goals could give us a path to a solution.

  • EIS 9.3.1 shared member error

    Installed EIS 9.3.1 using SQL 2005. Everythign works fine with the exception of one dimension. My Period dimension (months) has one part built with a SQL view, which is used in the drill through reports, and the rest, which is not drillable, is build directly in the Metaoutline.
    Any member shared within the "manually" built members give me the following error:
    A shared member (member name) must be at the leaf level and cannot appear before its primary member.
    Now for the funny part. This exact architecture and outline builds in EIS 7.1.6 with no errors.
    Oracle Support suggested that I use a sort order to insure that it is built in the correct order. I do this in all my views in SQL itself, but these are not in the SQL view.
    Any thoughts woudl be helpful.
    THANKS!!!!!!

    Hi,
    I experienced (& luckily got it resolved) this error earlier!
    From your query, I understand, you were ensuring sorting would be done based on your key/functional columns.
    However, what Oracle seems to be suggesting you is: "Use an additional *column* (say, Sort_Order) to let the sort order ensure that- Base member always comes before Shared member". You may control the Sort_Order column using something like CASE statements...
    Correct me if you intend to ask something else!
    Greetings,
    - Natesh

  • About Shared Member

    Hi,
    I am creating a text file to create dimension build using Parent-Child references. I am not sure how do i mention a shared member in the test file. IS there any symbol to represent a Shared member in the text file?
    Give me suggestions on this.
    Thanks,
    Nagesam M.

    Would I be correct in saying that if the member already exists in the outline - but your text file has it against a different parent then you can either create the shared member or MOVE the member in the outline. Again controlled by the dim build settings.

  • Shared Member: Global Property Change

    Hi,
    I am working in DRM( Web Version) 11.1.2.1. I have some issue with Shared Member Property change.
    Is there any way to restrict/change the Shared member Global property value without changing its base member value? Is there any system preference for this?
    If anybody know any other way to restrict it than please tell me, its urgent.
    Thanks in advance
    Rotesh Gupta

    I don't really understand your question, you are talking about BSO loading dimensions then extract then ASO, what actually is your question?
    If it is there a property for shared members then no there is not, here are the list of valid member property codes - http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/dotrules.html#dotrules_2
    If you want to understand how to build shared members then have a read of - http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/dotdimb.html#dotdimb1061244
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • "Shared Member" Property

    I was told today that when building dimensions for a BSO cube, is "Shared Member" is not a valid property to specify in an extract ? To the best of my recollection, "Shared Member" is not a valid property in an ASO cube.

    I don't really understand your question, you are talking about BSO loading dimensions then extract then ASO, what actually is your question?
    If it is there a property for shared members then no there is not, here are the list of valid member property codes - http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/dotrules.html#dotrules_2
    If you want to understand how to build shared members then have a read of - http://download.oracle.com/docs/cd/E17236_01/epm.1112/esb_dbag/dotdimb.html#dotdimb1061244
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • (ESSBASE) How to move shared member into hyerachy

    Hi, i've this question: How can I move a shared member into the Essbase Outline hyerarchy when I load metadata?
    I've tried using the "Allow Move" option into "Dimension Builiding" session of the rule, but the system gives me an error...

    I have a dimension called "clienti" structured in this way:
    Clienti
    - GER1
    -XXXXX 1
    -A
    -XXXXXX 2
    -GER2
    - YYYY1
    - YYYY2
    - A (shared)
    -GER3
    - ZZZZZ1
    - ZZZZZ2
    - A (shared)
    Now, using a rule that reads form SQL source, I wanto to transofrm my hyerarchy in this way (the member "A" changes his parent in all hyerarchies [Ger1, 2 and 3]):
    Clienti
    - GER1
    -XXXXX 1
    -XXXXXX 2
    -A
    -GER2
    - YYYY1
    - A (shared)
    - YYYY2
    -GER3
    - ZZZZZ1
    - A (shared)
    - ZZZZZ2
    The way I follow it's:
    1) load ONLY GER1 members filtering by SQL statement (Select * form "TABLE" where "FILED_NAME" ="GER1") with "ALLOW MOVE" option checked into rule properties -> IT'S OK, the member "A" changes its partent correctly
    2) load GER2 in the same way, but the system gives me this error: Dimension build failed. Error code[1060053]. Check the server log and the dimension duild log for more information. Unexpected essbase error1007083
    The log dont give me any info and the dimension build log is not created
    The same when I try to load GER3 and if I try to load ALL (Ger1 + 2 +3)
    My doubt is that is not possible to move shared members..
    Thaks!!

  • Duplicate members to be showed as shared member

    Hi all,
    working on ver11.1.1.3.X,i tried to build dimensions through rules file but some duplicate members are there in the .dim file. I have build the primary member hierarchy first and later tried to build the member hierarchy having duplicates,when i loaded the duplicate member hierarchy the members in primary member hierarchy were automatically deleted.
    I'm using Level reference for dimesion building. The duplicates in the second member hierarchy should be shown as shared members,
    can any one tell me how to make the duplicate members as shared with level reference?
    thanks in advance

    Hi gurus,
    I'm building two members of a dimension hierarchy through rule files, i have two .dim files in level reference format so i created two rule files.The problem is during defining the dimension build properties because some of the members in the second member hierarchy have to be defined as shared members.
    Let say i have a dim A and the members are B & C. I need to load B.dim,C.dim files by using level reference method through B1.rul,C1.rul files. C.dim has some  duplicate members of B.dim which are to be defined as shared members of C member.
    The duplicate members are at different levels(in B at Levl2 and in C at Levo- these Lev0 duplicate members have to be shared ).Please help me out in defining the dim build properties,
    thanks in advance
    Edited by: kailash on Jan 4, 2012 11:27 AM

  • Issue with User Variable Due Shared Member Security Access

       Hi All,
    One of my client is using User variable in data form to define POV.
    Now if user has access to 2 member in the Dimension, he should able to see 2 member when he try to assign the value to this "user variable"
    but he can see some of the parent member name ,this parent name has only one child which is a shared member of the 2 base member for which he has access.
    For Example:
    Entity Dimension:
    E1 (user has access)
    E2
    E3(user has access)
    E4
    Alt_Entity
    Alt_Entity1E1 (sharedmember)
    Alt_Entity2E2 (sharedmember)
    Alt_Entity3E3 (sharedmember)
    Alt_Entity4E4 (sharedmember)
    User is able to see below members, when he try to assign value
    E1 (user has access)
    E3(user has access)
    Alt_Entity1
    Alt_Entity3
    Now if I add another member under this parent, than user are unable to see this parent member.
    For Example:
    Entity Dimension:
    E1 (user has access)
    E2
    E3(user has access)
    E4
    Alt_Entity
    Alt_Entity1
    E1 (sharedmember)
    E2 (sharedmember)
    Alt_Entity2E2 (sharedmember)
    Alt_Entity3
    E3 (sharedmember)
    E2 (sharedmember)
    Alt_Entity4E4 (sharedmember)
    User is able to see below members, when he try to assign value
    E1 (user has access)
    E3(user has access)
    Any idea?

    Sorry, but actually its the parent that needs tagging with "Never Share", not the level 0 member, so Alt_Entity1 and Alt_Entity2 etc, see Essbase DBA guide
    understanding Implied
    Sharing
    The shared member property defines a shared data relationship explicitly. Some
    members are shared even if you do not explicitly set them as shared. These
    members are said to be implied shared members.
    If you do not want a member to be shared implicitly, mark the parent as Never Share so
    that the data is duplicated, and is not shared. See Understanding Shared Members for an
    explanation of how shared members work.
    So in the example above
    Entity Dimension:
    E1 (user has access)
    E2
    E3(user has access)
    E4
    Alt_Entity
    Alt_Entity1 - Set to "Never Share"E1 (sharedmember)
    Alt_Entity2E2 (sharedmember)
    Alt_Entity3 - Set to "Never Share"E3 (sharedmember)
    Alt_Entity4E4 (sharedmember
    Thanks
    Anthony

Maybe you are looking for

  • SQL Server 2005 SP2 Failed to install the update

    I just purchased a Dell PC and during the start up one of the updates that tried to install was SQL Server 2005. I tried turning off my Anti Virus program and the install failed again. Everything I've read about this problem is too technical for me.

  • System voice loading voices

    I have this strange problem on system preferences > dictation and speech The system voice fails to load up a voice  (just hangs) I have checked the location of voices in system>library>speech>voices .  The voices folder exists and has all the voices

  • Service outages and slow speeds

    Why have I been having  service outages and slow speeds for the last several weeks. I am in south central PA. (Somerset County) Why do I have to pay Verizon for service that I do not get?

  • Why am I seeing someone elses iTunes ID?

    I just got my new iPhone today. I wanted to load an app, my first one. When I tap 'Install" it comes up with a window asking me to enter a password. Already appearing in this wondow is an earthlink.net ID, but it's not mine. When I do enter in my iTu

  • Satellite A200-27Z - How to unblock KeNotify on Windows Vista?

    Hi everyone, Well, that subject pretty much says it all. I'm doing a cleanup - on my Satellite A200-27Z - and I my Windows Vista keeps blocking KeNotify.exe on startup. Answers on Google etc. are contradictory - "it's safe!" - "no, don't touch it!" -