Sorting by Member's Alias name during dimension build

I dynamically build/update an Employee dimension each month. I want to sort the members by their alias name, which in this case is the employee name. Has anyone done this before? The data file which I'm using to build the outline is already sort by employee name. The problem I have is each month when I do an update build, all the new members drop to the bottom. The option in the load rule definition to sort members is no good because that sorts the member by their ID and not by their Alias.Thanks for helping!!Peter

The best method is to clear all the members of the dimension and rebuild the entire dimension from scratch.This can be done manually through the Outline editor from the Essbase Applicaiton Manager or using an Incremental Build Dim from Esscmd or Maxl.Using Esscmd you it would be easiest to have a dummy build file with a single member and process that file first then process the real file. Use the remove unspecified option and set sorting to none. Regardless of method do NOT restructure the data between deleting all the old members and processing the updated file.If you restructure between these steps you will need to reload all data.Joseph HoganSenior Essbase Lead ConsultantHyperion Solutions203.703.3300 x6364

Similar Messages

Alias names for dimensions in BO 4.0 Explorer (Information Space)

Hello,
I have a requirement to add 15 dimensions and 2 measures in an information space. Each dimension has alias names. Example, buyer is a dimension which can be also be called purchasing group, Pgroup, Employee etc. I know it is possible to rename the dimensions. But is there any way to assign alias names to dimensions either in the universe or in information space? So when a user types Pgroup and hits the search button in explorer, he/she should find a match in the information space where buyer is a dimension.
Also, is there any limit in adding dimensions to an information space? Can I add upto 15 dimensions?
Appreciate your inputs.
Thanks,
Ann

Hi there
In the Universe, you can have objects with a different name that point to the same database table/field name. From your example below, you could have both the Purchasing Group and Employee dimension pointing to the same database table.field. You should be able to add 15 (and more) dimensions to your Information Workspace-- I haven't seen any documentation on the maximum number of dimensions out there.
Just keep in mind that as you add more dimensions/facets, users may get a scroll bar and will need to scroll across to see then.
Hope this helps!
D.

How to sort the members by alias names

I am trying to create dimension build rule whicl will sort the dimension members in an ascending order, but it has to be based on the alias name instead of the member name.
I have tried both Parent-CHild and Generation reference but it doesn't work.
For example
for the city members PSE ( alias name Purchase), and USALB ( alias Albany) needs to be sorted by alias names
the current order is
PSE(Purchase)
USALB(albany)
but the requirement is to be
USALB( Albany)
PSE(Purchase)

Even with presorting the input, you still have work to do. By default, Essbase will add new members to the bottom of the list of membrers, it does not insert them into an existing hierarchy in the right places. If your trying to update existing hierarchies and are going the SQL route, you will need two rules (or 1 rule and a flat file). You also need to specify remove unspecified as part of the dimension build process.
HAve a dummy input (either sql or file) that gets loaded the first time. IT will basically wipe out all the members of the dimension, then your second rule (or same rule calling your SQL) can reload the dimension sorted in alias order.
IT is important that these two rules be done together (either in MaxL using comasin a single statement) or in a BSO cube in the outline before the outline is saved. Otherwise you will have deleted any data that existed in the database. It would be impartant that your SQL also pulls all members (including any special members)
Edited by: GlennS_2 on Jan 6, 2010 9:48 AM
You say you are going to change the stored procedure. That is not necessary, you could put an order by clause in your sql extract statement

How to Import Member Aliases during Dimension build.

HI All ,
I have to build dimensions in Essbase using load rule files. I can create dimensions and its respected members.
But problem is that i also want to assign aliases with member names in Essbase hierarchy.
so How i can assign aliases (In source .csv file) also along with dimension members to update aliases in hierarchy of Essbase.
your suggestions are very precious for me .
Thank you.

Hi,
in the source file itself you can have a column for Alias names.
You can use any build type either genref or levref or parent-child.
the below DBAG link will guide you for adding alias names using Rules file.
http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm
- Krish

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.

Error during dimension building

Hi All,
Is there a way to move the members using alias names in outline using a load rule?
I have two dimesnion build process, one to create lev 0 members in a dimension and the other to move these members under proper rollups. The first dimension build process will build the members and it's aliases and in second dimemsion build source file, I have member aliases instead of orginal member names and when I am trying to do dimbuild (trying to move the members using alias names) I am getting error "Error moving member....".
Is there any way to move members in outline using alias names?
Any suggestions will be appreciated. I am using essbase version 7.1.5
Thanks
Maddy

How you are extracting both the dimension files.
if you are getting both from differant tables, you can genearte single file with all required fields by using alias name in the join criteria of the query.
Then you can build the entire dimension in one attempt.

Cube hang up is happening during Dimension Build process

We are using the Excel VBA tool for the Dimension build process.The tool will build the members in 3 applications(Atlaunch,ModeLife,Textcube).Most of the times cube hung up is happening at the Text cube. The dimension build process is described below
Dimension Build Process :-
The dimension build process is performed by the Calculation and Dimension Build Tool.
Before executing dimension build logging in to essbase server is required through the tool
Once logged in the particular region where dimension build is supposed to be carried out is selected from NML, NA, NE and NS.
Per region there are 3 applications namely <Region>LNCH, <Region>LIFE and <Region>TEXT and per application there is only 1 database namely AtLaunch, ModeLife and TextData respectively. The cube structure per region is given below:
NML Region:
NMLLNCH.AtLaunch
NMLLIFE.ModeLife
NMLTEXT.TextData
NA Region:
NALNCH.AtLaunch
NALIFE.ModeLife
NATEXT.TextData
NE Region:
NELNCH.AtLaunch
NELIFE.ModeLife
NETEXT.TextData
NS Region:
NSLNCH.AtLaunch
NSLIFE.ModeLife
NSTEXT.TextData
The Dimension Build Process is carried out in 2 steps:
1.     Project Master Code Build –
2.     Grades, Line Options, Project Description and Reference Currency Build –
Project Master Code Build:-
In the Project Master Code Build by the Calculation and Dimension Build Tool the following processes are involved
•     Some members are dynamically created in <Region>LNCH.AtLaunch, <Region>LIFE. ModeLife and <Region>TEXT. TextData cubes.
•     Some data is loaded in <Region>LNCH.AtLaunch Cube.
Grades, Line Option, Project Description and Reference Currency Build:-
Grades – Some members are dynamically created in <Region>LNCH.AtLaunch and <Region>LIFE. ModeLife cubes.
Line Options - Some members are dynamically created in <Region>LNCH.AtLaunch
Project Description - Some members are dynamically created in <Region>TEXT.TextData cube. After that some data is loaded in <Region>TEXT.TextData cube.
Reference Currency – UDA is updated in <Region>LNCH.AtLaunch, <Region>LIFE.ModeLife cube and UDA and Alias is updated in <Region>TEXT.TextData cube.
Note: Most of the times during Project Description Build we are experiencing cube hang up / no response for NMLTEXT.TextData, NATEXT.TextData, NETEXT.TextData and NSTEXT.TextData cubes.
Text cube dimension build process flow :-
1. Introduction
The Dimension Build process in CDB system is used for adding new project information in the cubes (AtLaunch, ModelLife and TextData). The text files which are needed for performing dimension build are generated from the child packages and stored in the local system of the user (<LocalDrive>:\GCEP4\Input\CDB_DimensionBuild). The Dimension Build process is carried out in 2 stages:
1.     Project Master Code Build
2.     Grades, Line Option, Project Description and Reference Currency Build
Project Master Code Build:-
In the Project Master Code Build by the Calculation and Dimension Build Tool the following processes are involved
•     MsPr_DIM rule is used for the text file F0P_<Project>-<Milestone>-<Version>.txt to build Project Master Code in AtLaunch, Model Life and Text Data Cubes.
•     MsPr_FLG rule is used to Load some data from the text file F0P_<Project>-<Milestone>-<Version>.txt in AtLaunch Cube.
Grades, Line Option, Project Description and Reference Currency Build:-
Dimension Build w.r.t. Grades and Line Options are carried out in AtLaunch and Model Life cubes which is not in scope of this document. Dimension Build w.r.t. Project Description and Reference Currency change are carried out in Text Data cube, so only those parts are discussed in this document.
2. Project Description Build (Detailed process flow)
The Project Description Build is carried out in the following steps:
•     First, any Lock on the particular PMV is checked. If not locked next operation is carried out.
•     Database availability is checked next (whether any other Dimension build is happening that time or not) and accordingly the availability flag is updated in TextData cube.
•     Next cache is set from high to low to carry out dimension build.
•     After cache setting, one rule file at a time is taken (as given in the cfgDL sheet) and dimension build is performed by using the Rule file and text file (created in local by input packages) on the intended cube.
•     For a particular Rule file “GCM_FDIM” which is used to build CCM information in TextData cube, the following steps are followed by the tool itself:
o     From the TextData cube all the child members under CCM member under Grades dimension are fetched by “GetMbrInfo” function (GetMbrInfo is used around 2000 to 3000 times).
o     The child members under CCM for that particular PMV combination are deleted (if previously build).
•     New child members under CCM are build based on the information provided in the text file F1G_<Project>-<Milestone>-<Version>.txt
•     Once CCM is build rest of the rule files are used to carry the dimension build operation.
•     The Dimension build process is carried out by building dimensions as well as updating some flags (loading data).
•     Reference Currency is updated (if required) at last.
Why this cube hang up is happening?
Thanks in advance

53 questions, all still open. Would you mind marking them as closed as without at least the "question is closed" tag, there's no way for future readers to know if your issues have been resolved or not. I know that I personally use this board for answers quite often and it really helps me when I see that a question has been adequately answered. Points assigned to those who helped you is a nice touch.
Now to your question: did you by any chance change from one Essbase server to another? You didn't state if this build issue happens all the time, or only if you do all three databases, or much of anything in your post as to the actual process of failure, so I'm kind of guessing wildly on this. If true, you might want to look at: http://timtows-hyperion-blog.blogspot.com/2007/12/essbase-api-error-fix-geeky.html
Regards,
Cameron Lackpour
P.S. MMIC, GlennS, and I were just discussing your kind of build-hierarchy-in-Excel approach last week and how infrequently it's seen nowadays. Not a criticism, I personally like these old-school approaches, probably because I've built one or two myself.

Properties not getting updated during dimension build

Hi-
I'm building an Account dimension. The build only updates the aggregation property and not the storage property. Any pointers at what can be the issue?
I've a rule file that is set to allow property changes.
thanks
PARENT0,Account     CHILD0,Account     ALIAS0,Account     PROPERTY0,Account     PROPERTY0,Account
AC_1     AC_2     Desc1     +     Dynamic Calc
AC_1     AC_3     Desc2     +     Store
AC_2     AC_2a     Desc3     +     Store

Check out the link here: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotrules.htm
Table 39. Member Property Codes shows the proper coding for properties. As far as I know, you need to use the codes instead of the store option names. S for store, X for dynamic calc, etc.
Cheers,
Mehmet

Sort by Alias name in Webform

Hi All,
Greetings!!!
I have defined employee dimension as row in Webform and display property as "Alias". Now the requirement is, I need to display the employees based on sort by their alias names.
Thank you so much for your kind help
Regards,
tvmk

I am sure others will also share their opinions, but I think this can be done thru updating your metadata upload process. Let say you get your Employee list from PeopleSoft and update your employee dimension by using one of the ETL tools (ODI, outline load utility, HAL, etc). I am not an ETL expert, but I have seen this before where the sorting would take place in the ETL process, so the members are loaded to your application in ascending order. Makes sense?

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

Not able to get the Alias Name(Member Description) in FR by using Planning

Hi All,
we are using the 11.1.2 version in my project. While i am developing the FR repots by using planning database i am not able to find the Member name in my report, but i am able to see the option. MemberName, Alias and Both. If i check the Alias or both its giving only member name only.
Any ides on this or any post are there prior this .
Thanks in Advance.
Rao

Rao,
Thanks for the info! It is strange that despite having alias name report is populating member name. It is not the first time strange things hapend with FR.
Can you please check if you are connecting to same data source where you see alias name? Can you pull alias name from SmartView?
Venu

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

Alias names for account dimension

Hi,
The alias names for account dimension is not getting pushed to EAS for all EPMA essbase applications(ASO and BSO). However i see them in the application and in the dimension library. I just see the alias for accounts dimension as account but not for any members.
The dimension has the alias associated with it. But for other dimensions i do see the alias names in EAS.
Hyperion EPMA - 11.1.2.0.00.938
Regards,
Ragav.
Edited by: ragavhere on Feb 5, 2013 3:16 PM

Thanks.
It was because of a patch that I had installed yesterday. I uninstalled the patch and then deployed the applications. The problem is resolved.
And we are upgrading to 11.1.2.2.
Regards,
Ragav.

How to extract member, default alias and custom alias into separate columns

Hi,
is there a way to get simultaneously member name, default alias name and custom alias name with Essbase 9x report scripts (Report Writer)?
I do know that using for example
<OUTALTSELECT "default or custom alias table"
<REPMBRALIAS "dimension"
I can get both the real member name and selected alias table, but the problem is that they're both returned to same column.
Using fix columns and order I can repeat member name into several columns if needed, but I would need to tell what to put for each column.
For example : { ORDER 0,0,0,1,2,3,4,5 FIXCOLUMNS 8 }
I would like to force the report script to put Member name into first column in row, default alias name of member into second column in row and custom alias name of member into third column in row, like :
MEMBERNAME DEFAULTALIASNAME CUSTOMALIASNAME
Any ideas how to handle this?
I can of course create several extracts containing one sort of info per list, but it would make life somewhat easier having all of these in same extract.
Thanks in advance!
Br,
MK

Hi,
well, that's pretty much what I want to achieve, to get all info of member within same row, but into separate columns.
The other option is to then produce 2 other extracts containing:
Extract 1:
MEMBERNAME DEFAULTALIASNAME
and
Extract 2:
MEMBERNAME CUSTOMALIASNAME
These values should be in separate columns?
I think I lost the track while playing around with report writer, does anyone have a ready made solution for this?
<REPMBRALIAS brings the needed info, but returns the values into same column.
Empty space delimiter could be handled with customalias table, but in this case default alias name may have long text with several empty spaces making it hard to sort in the other system side.
Any suggestions?
Thanks so far for your kind help.
Br,
MK

Members rejected during dimension load

Hi,
I am trying to deploy an application from Essbase studio. It loads few members and rejects few members. And it does not load any member to scenario and Version dimensions. I have the source in Parent, child relationship and the top most parent being #root for every dimension.
And when I preview the hierarchy, it shows in correct parent child relationship. But after the cube deploy, in the outline it is in random order. All parents are created under the dimension itself. And the error during cube deploy in Essbase studio is
Member load for dimension Account started at: Sep 30, 2013 12:34:15 AM PDT. Records processed: 2,424. Records rejected: 1,770.
Member load for dimension CostCenter started at: Sep 30, 2013 12:34:16 AM PDT. Records processed: 2,865. Records rejected: 1,271.
Member load for dimension Period started at: Sep 30, 2013 12:34:17 AM PDT. Records processed: 16. Records rejected: 12.
Member load for dimension Year started at: Sep 30, 2013 12:34:17 AM PDT. Records processed: 9.
Member load for dimension Product started at: Sep 30, 2013 12:34:17 AM PDT. Records processed: 254. Records rejected: 156.
Member load for dimension Project started at: Sep 30, 2013 12:34:18 AM PDT. Records processed: 1,503. Records rejected: 56.
Member load for dimension Scenario started at: Sep 30, 2013 12:34:18 AM PDT. Records processed: 9. Records rejected: 9.
Member load for dimension Version started at: Sep 30, 2013 12:34:18 AM PDT. Records processed: 15. Records rejected: 15.
Member load for dimension State started at: Sep 30, 2013 12:34:19 AM PDT. Records processed: 102. Records rejected: 85. Member load elapsed time: 5 Seconds.
Data load started at: Sep 30, 2013 12:34:21 AM PDT. Records processed: 50,854. Records rejected: 50,854. Data load elapsed time: 6 Seconds.
\\Record #17 - Member name (REAL ESTATE STATS) already used
REAL ESTATE STATS 31104
\\Record #18 - Member name (REAL ESTATE STATS) already used
REAL ESTATE STATS 31201
All data records are rejected as well.
Regards,
Ragav.

If you look at the Error record it says you have same member/alias twice, check the source and see if you have special characters?
Also check for duplicate members.
Regards
Celvin
http://www.orahyplabs.com

Sorting by Member's Alias name during dimension build

Similar Messages

Maybe you are looking for