Members in Essbase

How many maximum number of members can be in a dimension. We have a client who has 60,000 employees and they want to include into planning and budgeting process.

Hi,
To add Jake's points, I've had quite interesting experience with these type of dimensions. In one instance I've created an application where one of the dimensions had 60k+ members and another had around 8k. Because of a strange requirement, I had to place these 2 dimensions plus 2 more to the rows section of a web form. This was when we realized that there is a limitation with essbase 32 bit. You can't design web forms in which there is a member combination of more than 2^32 in the rows section. This is and mdx limitation in Essbase 32 bit.
I then split the form into pieces then things worked fine with the settings like suppress missing blocks, data etc.
You must however be extremely careful with these type of cubes as they are like time bombs which can easily explode after say a wrong calculation which creates unnecessary blocks.
Cheers,
Alp

Similar Messages

  • Maximum no of members in Essbase Dimension can support

    Dear All,
    I am using Essbase 11.1.2.2 (64-bit)
    Number of dimensions used in my BSO Essbase cube is 9 (4-dense and 5 sparse).
    I am having a Customer dimension (sparse) upto 7 levels.
    The number of members in customer dimension is 98000.
    After loading data in essbase BSO cube, while performing Ad hoc Analysis it throws the following error in Smartview,
    "Request timed out contact your administrator to increase netretrycount and netretryinterval"
    After making changes to below variables in registry and essbase.cfg files
    NETDELAY 500
    NETRETRYCOUNT 400
    Registry settings
    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]\
    ReceiveTimeout=480000
    KeepAliveTimeout=180000
    ServerInfoTimeout=180000
    and also with
    ReceiveTimeout=900000
    KeepAliveTimeout=300000
    ServerInfoTimeout=300000
    I am getting the following error
    "Concurrent requests on the same session are not allowed. Wait till the previous request completes processing"
    After i reduced the no of members considerably in Customer dimension, the issue got resolved.
    My question is "Do we have any limitations in maximum no of members in a single dimension"
    What is the maximum no of members a Essbase dimension can support ?
    Regards,
    Tharik

    To answer your specific question, the limits are listed here: http://docs.oracle.com/cd/E26232_01/doc.11122/esb_dbag/limits.html. According to that, BSO will handle 1,000,000 members.
    My question would be what exactly you are doing when the error occurs. Does it happen when you attempt a drill to level zero for example? Or as soon as you retrieve an ad hoc sheet?

  • How to load shared members in Essbase

    Can anyone tell me how to load Shared Members in Essbase using ODI
    -app

    Did you not already ask the question :- Essbase Error log issue for Shared Members
    You never answered my question to your original post.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Function to get all Level members in essbase

    Hi All,
    Could any one please tell me what is the function to get all Level Members in Essbase.

    Hi IMD,
    It sounds like you are looking for the @LEVMBRS function. It has two parameters, a dimension and the level number. You should also review the @RELATIVE function.
    For much more in-depth information review the Technical Reference and Database Admin Guides which are part of the 11.1 docs.
    Essbase 11.1 docs - http://download.oracle.com/docs/cd/E12825_01/nav/portal_3.htm
    Database Admin Guide - http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag.pdf
    Technical Reference - http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_techref/frameset.htm?launch.htm
    Chapter 22 in the Database Admin Guide covers use of Formuals
    See the Member Set Functions of the Tech Ref
    http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_techref/frameset.htm?func_memsettype.htm
    Regards,
    -John

  • DRM and Shared Members in Essbase & Planning

    Hi,
    Many years ago we implemented Razza and one of the difficulties we had was in handling shared members in Essbase and Planning applications. The workaround as I recall was to use a prefix in alternate hierarchies, and strip it out before exporting. But this did not allow for a single place to maintain a node. Is there a best practice for handling shared members in DRM?
    Thanks!

    DRM now supports shared members in the application. This application functionality used configurable suffixes. You can read about this in the DRM User Guide.
    This makes Essbase integration virtually seemless since Essbase will treat the first occurance of a member encountered during the dimension load process as the base member and any subsequent occurances of that member as shared members. Planning, however, requires shared members to be marked as such and thus depending on how the hierarchies are maintained in DRM and then exported, it is possible for the shared member to appear before the base member, which will cause Planning to raise an error. This can be accommodated with two pass loads and other techniques.
    Also note that this information could be dated as I haven't personally been on a project that fed hyperion Planning for a couple of years. Regards.

  • Rename multiple members in essbase

    Hi,
    Can anyone tell me how can we rename multiple members in essbase at a time and also the data should not be lost for the existing member combination.

    It depends on how many members you want to rename and if any of the names switch between members. If all of the new member names are not the same as an old member name and there are not too many of them, then you could just rename them in EAS and the data will follow.
    If some of the names are the same (for example, you want to reanme a -> B and C->A) then you have to do it in two steps rename A-B and save the changes then rename C->A and save the change.
    If you have a lot to do, then it becomes a bit harder as it is difficult to automate it. You can sometimes use new aliases to make the new names, then go back and rename the members to match the aliases.
    You can also use the API to do this. read something that has the onl and new names and do a rename function. This would take a little more work to incorporate. I think the code to get you started is still available from a presentation I gave a couple of years ago at the Kaleidoscope conference. Look on the ODTUG site (You have to be a member, but you can sign up for free)

  • Duplicate Members in Essbase

    I need to have duplicate members in one of my dimensions, without adding a qualifying prefix or sufix. For example, suppose my dimension is as follows:
    Country->State->City->Zip. I want to have duplicate member names at the City level, without having something like "MA_Springfield". I want the city name to just be "Springfield"
    So in order to accomplish this, I modify the key binding for City in Essbase Studio to the following:
    *"[" || connection : \'OBIEEDEV'::'ENTERPRISEBI.COUNTRYDIM.'Country' || "].[" || connection : \'OBIEEDEV'::'ENTERPRISEBI.COUNTRYDIM.'State' || "].[" || connection : \'OBIEEDEV'::'ENTERPRISEBI.COUNTRYDIM.'City' || "]"*
    I then enable duplicate members in Essbase properties and deploy the cube, but the Cities that are duplicates get dropped during the outline build.. The error messages say that *"duplicate members are not allowed at this generation level"*
    What am I doing wrong?
    Appreciate any advise.
    Fyi - I'm building an ASO cube in EPM 11.1.2 using Essbase Studio. Also, in my Essbase properties Outline Build, I'm choosing the Move duplicate members (and their descendants) setting
    Edited by: 806008 on Nov 11, 2010 11:19 AM
    Edited by: 806008 on Nov 11, 2010 11:22 AM

    Hello,
    Create a new member down the first one in your dimension. Put the value 'shared member' in DataStorage options.
    Regards

  • How to build the members in essbase based on levels using EAL

    Hi All,
    How to restrict the members to build the in essbase based on levels using EAL.
    I've requirement, in one dimension, needs to build the one level1 member as level0 in essbase.
    please let me know the procedure, if any one implemented or face similar.
    Thanks in advance,
    Kiran

    there's no such functionality in EAL to create Essbase outlines based on levels. the only workaround to this is to use Mapping tables:
    1- create the dimension in essbase with the desired HFM level 1 members as level 0.
    2- set this specific dimension to mapping in your design grid within your EAL Bridge
    3- create the SQL Mapping table and start mapping those members from HFM to Essbase.
    Tanios

  • FDM : How to map rejected members in Essbase

    Hi,
    I'm new to FDM, I have a simple mapping in FDM :
    Type of mapping : LIKE
    thirdparty_code in source file = I_thirdparty_code in essbase
    The problem is that there is new thirdparty every day and I cannot update essbase metadata every day so some members are rejected during the EXPORT step.
    Is there is way to automaticaly mapped rejected thirdparty to a generic member i_none using FDM ?
    Thanks

    There is no out-of-the-box functionality that will let you do this. It could be done via a customized set of scripts but this would require quite a bit of work and I'm not sure it's worth it for the benefit you'd get. What you probably need to do is look at your process around metadata maintenance and updating as metadata that is changing every day is always going to be very difficult to manage.

  • Loading members to Essbase using ODI

    Hi All,
    We are planning to use ODI to load members from Oracle database to Essbase using ODI. Should we convert all the dimension tables in Oracle database to Parent-Child relation and then load it or can we use the existing hierarchial structure in Oracle database.
    Thanks in Advance.
    Kannan.

    Hi,
    If you reverse engineer an essbase cube it creates columns :- ParentName, MemberName.
    When you load metadata into essbase using ODI it will need to be mapped against Parent and Member, to make it easier it would be useful if your source data is in parent/child format.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Add unidentified members to Essbase outline automatically on load

    We are using FDM to map and import data files to Essbase. Due to the number of members in each Essbase dimension, and since all of the source members are identical to the target members, most of the FDM mappings are taken care of by single "like" mapping for each dimension, in order to map the data file members straight to the Essbase members (map source member to target member):
    Rule Name: ALLACCOUNTS
    Rule Desc: All Accounts
    Rule Definition: *
    Target Accounts: #Script
    Script: Result=varValues(13)
    However, if the source system has had new members added but Essbase has not, the load will fail since Essbase cannot locate the new members.
    Is there a way to get Essbase to automatically create new members (under a designated parent in each dimension) if they are found to be present in the data file, but found missing in the Essbase outline? This may be a question specifically for the Essbase Forums, however since we are loading from FDM this must be a scenario experienced by others? If the above is not possible (I imagine this is quite likely) what would be the workaround?

    FDM is focussed on loading data not metadata. I wouldn't try to automate this, there should be a business process for this that uses a more appropriate toolset (EPMA, ODI etc) to do this i.e. have a seperate metadata update process based on the content of the source files that runs prior to any data load processes.

  • Enabling Duplicates / Disabling Shared Members in Essbase Studio

    I am building an ASO cube using Essbase Studio in EPM 11.1.2. I need to check the *"Ignore duplicate members, do not move*" option in the outline build properties for one of my dimensions. However, the check-box for this is greyed out for some reason. How do I activate this option? Also, is there any other way to disable shared-members? I want my dimension to contain duplicate members and not shared members. But the build rule is currently treating two members with the same name as shared members.

    We've figured out how it works. You should set minischema first for txt file.

  • Copying data between members in essbase

    Hi Team,
    I have essbase 11.1.2.2 and I have the below dimensions,
    1)accounts
    2)location
    3)Time
    4) ITEM
    Under ITEM dimension I have the below members. I need to copy data from India and America to India_history and America_history respectively.  Can you please help me how I can perform the below task. India_history and America_history and Country_history are the new members which I created for this task.
    ITEM
    |----|- Country
              |- India
              |- America
         |-Country_history
              |-India_history
              |- America_history

    Hi Tim,
    Thanks for your response. Yes, its a BSO cube.  I am new to calc script. Will the below script work? I am bit confused with the Fix command.
    FIX (@LEVMBRS("Time","Lev0,Time"));
    DATACOPY "India" to "India_history";
    DATACOPY "America" to "America_history";
    ENDFIX

  • Handling HFM Shared Members in Essbase Analytics Link (EAL)

    We have an entity dimension in HFM with Shared Members in an alternate hierarchy.  The shared members happen to be parents and when the metadata is synchronized in EAL, only the shared parent is brought into the alternate hierarchy in our EAL cube.  We'd like to find a way to bring all of the descendents of the shared parent into our cube but Essbase does not allow it.  Is there a way to prefix the shared members during synchronization so the EAL cube contains the same structure as HFM while accommodating the need for unique member names in Essbase?

    I've seen this kind of behaviour in EAL when using both 11.1.1.3 versions. Could you let me know what are your EPM and EAL versions?
    May be your EAL will require a patch.
    Cheers.

  • Members in Essbase outline but not Planning outline

    We currently use Planning v3.5 and Esssbase v6.5.5 We want to add a member only to Essbase. It would not exist in Planning. <BR> <BR>Here are the specifics: <BR>We have a 3 generation outline and want to insert a member between generation 2 & 3 only in Essbase. The result would be that Essbase would have a 4 generation outline and Planning would have a 3 generation outline. We've tested this and done a refresh with no problem. Do you know of any problems with this approach? Also, we plan on upgrading to version 4.x in the near future. Would this be a problem if we upgraded?<BR> <BR>Ex. <BR> <BR>Current Outline:<BR> <BR>CONS_GAAP<BR> 00004<BR> 00004DIST<BR> 00004TRANS<BR> <BR> <BR>Essbase outline after change:<BR> <BR>CONS_GAAP<BR> 00004<BR> 00004TOT - add this member only in Essbase<BR> 00004DIST<BR> 00004TRANS<BR> <BR> <BR>Planning outline after change: <BR> <BR>CONS_GAAP<BR> 00004<BR> 00004DIST<BR> 00004TRANS

    Okay two things if 00004TOT is going to be a parent to 00004DIST/TRANS in Essbase, then absolutely not.<BR><BR>If 00004TOT is going to be on the same level as 00004DIST/TRANS (in other words also a level 0 member) then in theory you could do it, but it would not be considered best practice or a supported solution. The problem is when you refresh planning you would run the risk of losing the member, having the database corupt, etc.. If this was somehting you really wanted to do, you would have to thinking it through and build a lot of preocedures around it, so that after every Planning refresh an Essbase dim build would kick in and add the memebr, then relaod your data, yada, yada, yada. You really don't want to go down this road. Either add the member in Planning or let the users do the math in Excel/Report writer.<BR><BR>Don't forget Planning does support alternate rollups with shared members. So you can create an alternate roll up with 00004DIST and 00004TRANS as shared members that roll up into 00004TOT. That would be the supported/best practice solution to your problem.<BR><BR>HTH

Maybe you are looking for