Using Shared members

Hi,
I have Created shared member in Market dimention. the structure is like
Market(dimension)
ASP(parent)
India(child)
China(child)
Usa(parant)
Newyork(child)
xxx(chiild)
Misc(parant)
India (Shared member)(hild)
in Excel add-in I have taken all the markets including shared member (India).
but if enter the data at the base member the data is not saving to database. if i enter the data at shared member is saving to database and the shared member data is transfering to base member. why it is happening i am not understanding please give me suggesions.
actual theory is the data and properties of the base member should be shared to shared member but in my case shared member data is updating to base member. did i done any thing wrong please guide me.
Regards,
Suneel.
Edited by: 850159 on Apr 13, 2011 5:02 AM

If I understand your issue right,, you can not use base member and shared member in the same data form or
Excel-template. Try to save the value to base member by deleting the shared member selection, It should work.
Have an other template if you need to use shared member for data input.
--Ram                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

Similar Messages

  • UDAs re shared members and Intersect

    I'm INTERSECTing two sets:
    Leaf-level from [Entities].CurrentMember and
    UDA([Entities],"myuda" (also leaf-level)
    This intersection works appropriately on my primary stored hierarchy but not on any of my alternative hierarchies (also stored). It does work when I zoom to the leaf level in the alternate hierarchy but not any of the rollups.
    I had assumed the UDA on the shared member (in the alternate hierarchies) would acquire the UDA of its stored member. However, it doesn't appear to be working that way.
    Can anyone shed any light on this issue or suggest a different approach?
    Thanks,
    Barb

    We're using shared members in 11.1.1.2, in both dense and sparse dimensions. So, the good news is that it can be done. The bad news is that I'm not sure why you're experiencing this issue.
    Will you provide some additional details about the dimension where you're having this issue? Is it in a shared library, or a local library? Is there any chance that the prototype member (the original non-shared member) is set to "NeverShare"? Unfortunately, EPMA will allow users to select certain settings that cause problems downstream. (And sometimes it won't allow perfectly valid settings.)
    - Jake

  • Aliases on Shared Members not in Essbase

    <p>I used HAL to create alternate rollups using shared members inmy Accounts dimension and in a custom dimension (Customers). The aliases for the shared members appear in Planning, butafter refreshing Essbase, the aliases are not in Essbase; only themember names.  When I add a shared member manually inPlanning, the alias is populated in Essbase.  Does anyone havean idea of how to get the aliases in Essbase?</p>

    <p>I realize that the alias will display when reporting on it. The reason it came up is because you can't see the alias whenperforming a member selection.  It's an inconvenience, not ashow stopper.  I just thought it was strange that the aliaswould go into Essbase when the shared member was added manually,but not when added using HAL.  Seems like a bug to me.</p>

  • Delete shared members (lots of them)

    Hi!
    We have a account hierarchy with lots of members. At the end of the account dimension we have a lot of shared members, which are located as direct children of Account dimension. In Planning web we can delete those member by member, but it is a time consuming exercise.
    Is it possible (and safe) to delete those at this point unnecessary shared membes in Essbase admin console? We would then load a new P&L hierarchy (using shared members) into Planning using HAL (our version is 9.3.1. and we are using classic administration)
    Kind regards

    It is best to remove via HAL or some tool that allows communication with the SQL repository. Best to try to keep essbase and planning in sync........hope this helps.

  • How to build shared members using Rules file

    hi all,
    we have a source file like below,in that Bold members are shared member. we doknow how to modify the source file for building shared members using Rules file.
    Conf Total,~,Config A,*Lightbolt 365 A*
    Conf Total,~,Config A,*Lightbolt 540 A*
    Conf Total,~,Config A,*Lightbolt 730 A*
    Conf Total,~,Config A,*Thunderball 365 A*
    Conf Total,~,Config A,*Thunderball 270 A*
    Conf Total,~,Config A,*Roadranger 123 A*
    Can anyone give suggestion to resolve this issue.
    Thanks in Advance

    hi John,
    Here i'm building the dimension through generation build method.
    setting the properties as
    Field, Dimension, Field Type, Field Number
    Field1,Product,Generation,2
    Field2,Product,property,2
    Field3,Product,Generation,3
    Field4,Product,Generation,4
    After mapping it shows dimensions are correctly mapped.
    When i load the source file and the rule file, it shows error partially loaded data,.And it doesn't shows the shared member property. That is what asked How to modify the source file for building shared members using Rules file.
    Thanks,
    Edited by: user@99 on 25-May-2010 15:37

  • Building shared members using rules file

    How to build Shared members in the outline using load rule file.
    I tried but it is not working correctly.

    Hi,
    If you are loading the build file in parent child format...you don't need to mention the member as shared or stored.
    Essbase automatically makes the second one shared.
    If you are using generations or levels format to build the dimension then I suggest you to refer the docs to understand it clearly.
    http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/esb_dbag.pdf
    Thanks,
    Jeeth

  • How to load shared members into a duplicate outline using load rules

    Hello, I am trying to load an alternate hierarchy into the same dimension in an outline that accepts duplicate members using EAS load rules ... there is no property for shared members so i can't specify it in the load rule .. i tried using parent child and it is not working - no shared members are loaded in the alternate hierarchy .. any ideas? would another utility make it happen?
    thx

    You might find this useful: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm
    Especially the Building Shared Members by Using a Rules File section: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm#dotdimb1061244
    Cheers,
    Mehmet

  • How to see Shared Members in Smart View on Ad-hoc Analysis mode

    Hi All,
    We are using Hyperion Planning v 11.1.1.3.
    For the alternate hierarchy we have created shared members. But in Smart View we are unable to see Shared members hierarchy in Ad-hoc analysis mode.
    Is this limitation in Hyperion Planning?
    Or
    Is there any way to see shared members Hierarchy in Smart View in Ad-hoc analysis mode?
    It is urgent requirement Please let me know as early as possible
    Thanks in Advance!!!

    When you say open data form in Ad-hoc mode, can you do that? I think when you select Ad-hoc mode, you are basically connecting to Essbase and therefore need to manually select the members. (of course, I've got a 11.1.2 env right now so not too sure of 11.1.1.3)
    I'm able to just go to Member Selection and select whatever hierarchy i want, Shared or Stored, when I'm connected to Essbase. When connecting to Planning, I dont have any option of opening the form as Ad-hoc mode.
    Can you see the hierarchy if selecting the members using Essbase connection and not planning?
    Cheers,
    Abhishek

  • Level building/shared members

    Can you generate shared members when level building your dimensions?

    I'm afraid I have to disagree with the previous 2 posters. You can build shared members when you use a level build method. I do it all the time. Assume your level zero member is in a primary and secondary rollup and that there are 3 parents in the firs rollup and 2 in the second, the format of the load rule would be:
    Lev0,Lev1,Lev2,Lev3,lev1,Lev2

  • Building RULES file to load shared members in Aggregate storgage outline

    Hi there
    I posted this yesterday (sorry, somewhat different subject description). I am trying to create an alternate hierarchy containing shared members using a load rule and flat file in an Aggregate Storage outline. One response was to remove the "allow moves" option and use parent child build in the load rule. I tried that and it did not work. i was pointed to a section in the essbase guide (which is about as clear as mud), and still cannot get this to work. First of all - can you do this with an ASO outline? If so, how? I tried a simple 6 line flat file and recreated the load rule based on the above recommendations and it will not the shared members. Can someone out there help?
    thanks

    Here is an example in the simplest form.
    Create Aso db (duplicate members names not selected)
    Create Product dimension member, set to "Multiple Hieararchies Enabled", (though probably would work if dynamic)
    Create load rule, set as parent/child dimension build for product, make sure allow moves is not ticked.
    Data file
    Parent,Child
    100,100-20
    200,200-20
    Diet,100-20
    Assign field properties in rule for Parent.Child
    Load data, 100-20 will be created as shared.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • EPMA Shared Members not reflecting in Planning application post deployment

    Hi,
    I have added a member in 'Entity' dimnesion. The same member is also added in an alternate hiererchy as shared member (Using Insert member option in dimension library). When I refresh the application view, I do see both the original member and shared member in application vieiw. But post deployment, only the base member is reflected in planning application and not the shared member.
    I have redeployed the application multiple times now, but i am still not able to see the shared members reflected in Planning application.
    Kindly let me know if you have any idea on the same or faced a similar issue?
    Regards
    Meenal

    Hi,
    Have you patched up EPMA with patches from Metalink3
    9.3.1.1 Patch includes -
    6897835 SHARED MEMBERS IN ENTITY DIMENSION CAN NOT BE DEPLOYED TO ASO/BSO APPS
    It is advisable to keep a look out for patch fixes with EPMA
    Hope this helps
    John
    http://john-goodwin.blogspot.com/

  • Shared Members

    Is there any way in which you can use a filter to look at just Shared Members and not the original members?we have looked at this and believe that it is not possible on the basis that whenever you drill down in Excel, you can see the values for the shared members and the original members as well.It would be great to confirm that the above is True, or even better, provide a solution to the problem.

    When you drill down from a parent member, you should be viewing the child members and if that is shared memebers then that is what you will see.The data value of the shared member and the origianl member is always the same. The roll ups will have differnet values. So I am not sure what you mean when you say the shared value and the origianl value are visible. Please clarify.Thanks.

  • Shared Members in Load Rules

    Hello,I am trying to build a dimension build load rule.How do you create shared members within a dimension? Does it have to be through a parent-child load rule? What if you have a subset of a dimension, (eg duplicate hierarchy) with more then two levels, ie parent child? How do you create shared memebers then?Any help would be greatly appreciated.Thanks.

    I'm a newbie in dim build using load rule too. I'd a bunch of products that had to be in 2 roll-up structures, apparently as shared members in one of them. It took little effort to build the first roll-up using a generation build method. Just when I thought it was gonna be a slam dunk, I couldn't create the second roll-up. I kept trying different load options but it just wouldn't work. I noticed the "Do Not Share" check box was always disabled. So I clicked on the different build method buttons. I noticed that the box become enable when I selected the parent/child method. I tried and it turned out to work fine. So, for the little knowledge I have, it seems you must use the parent/child rule to create shared members.

  • Shared Members Alias

    Hello,
    I am facing problems while creating / removing aliases of shared members in Essbase outline.
    1) What is the best possible way to create aliases for shared members (already present in the outline not new ones) ?
    2) What is the best possible way to remove aliases for exisitng shared members in the outline ?
    Any leads greatly appreciated.
    Thanks,
    Neetesh

    Hi.
    The Easiest Way of Doing it is by Parent-Child References..
    COnstruct a Data File using Parent child Reference and then Add a Third Column in which you provide Alias name.
    In the Field Property of Third Column make is as Alias and tag it to proper dimension and in Dimension build Setting go to Dimension Build tab and check "Allow property changes".
    In case of Removing Alias just create Another Column in Rule File And Leave it Blank
    Then in its Field Propety Check "Delete When Field is Empty".

  • Shared Members on interface changes of Entity or account hierarchy

    Hello,
    Is there any scripted way to remove 'Shared Members' from the Account and Entity hierarchy, or if not, is there any means of finding them on mass, as we have set up a database interface to maintain account and entities, but the problem is after accounts or entity change parent they leave a 'Shared Member' on the original parent, which is not desired functionality as it throws totals out on forms / reports.
    thanks for your input, no blogs please as our security prohibits me seeing them.
    Robert.

    Thanks John, can I ask you a follow on also...
    If a member had never share as its property and you used the hierarchy interface to assign it to a new would would it; -
    a. Prevent update of its parent hierarchy via the interface
    b. Move it to whatever new parent you deemed and remove it from its original
    thanks for your input,
    Robert.

Maybe you are looking for