Essbase cube level order

Hi All,
I am using Essbase XMLA interface .
As levels are ordered from lowest to highest starting from the root level. Essbase orders them in the reverse direction—level 0 is the leaf level, and level 1 is the parent of the leaf level.
Is there any way to get the level in normal order - level o parent and level 1 as child ?

Incidentally we had been trying to use Essbase studio as an option.But there are 2 oints that we are trying to investigate.
1) Can we bypass deployment of data and metadata everytime through Essbase studio after the initial outline is delpoyed? In the system architecture the relational tables are populated using ODI. We would like to load the data and metadata through ODI into the cube. Eeven then can we implement drill thru bypassing deployment through Essbase Studio?
2) If Essbase studio is imperative for drill through then what are the batch automation options for deployment through Essbase studio? Ideally the option should be after the relational tables are populated through ODI then the Essbase deployment should be invoked and batch script should load the data and metadata through Essbase Studio.
Please advise.
Thanks,
Anirban

Similar Messages

Sort in date order from Essbase cube source

Hi everyone,
I have an Essbase cube which I'm displaying the data from in OBIEE. Within the cube one of the dimensions is a date ( set as a time dimension ).
It has several generations:
Gen2 - Year, 2010
Gen3 - Year/Quarter, 2010/Q1
Gen4 - Year/Month, 2010/01
Gen5 - Day/Month/Year, 26/01/2010
If I produce a report filtered on the Year, say 2009, and display the full date, it puts all twelve 1st's of the month first, then the 2nds, and so on. I can resolve this by putting the Year/Month field into the report and sort on that, then the full date, but I really only want the date in chronological order.
Can anyone advise on the best way to achieve this?
Thanks to all in advance.
Bagpuss
Edited by: Bagpuss1969 on Jan 26, 2010 12:46 PM
Generation 5 is DD/MM/YYYY

And this is one of the reasons why OBIEE/Essbase integration is still #1 on the [Dont Try This At Home Kids|http://majendi.blogspot.com/2009/06/dont-try-this-at-home-kids.html] list.
One of the most basic facts about the current integration - which is often disregarded - is that dimension levels and hence their contained members come across as pure VARCHARs. Sort order-wise this gives you a standard alpha-numeric sort order by default.
However there's a workaround which we discussed just last week: Oracle BI import Essbase cube (problem on the months)
Essbase defines the sort order. Otherwise it's alpha-numeric.
C.

Reporting Essbase cubes from Answers

I followed the documentation available in support site to configure Essbase cubes in RPD in a Solaris environment. I got the Essbase client installed, added required variables (HYPERION_HOME, ESSBASEPATH, ARBORPATH) and cahnged LD_LIBRARY_PATH variable in OracleBI\setup\user.sh file. I started the BI Services in 64-bit mode successfully.
I am getting the below error while running an Answers query.
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. Essbase Error: Network error [146]: Unable to connect to [HostName:pot#]. The client timed out waiting to connect to Essbase Agent using TCP/IP. Check your network connections. Also make sure that server and port values are correct (HY000)
SQL Issued: SELECT ALL_LOCATIONS."Gen2,ALL_LOCATIONS" saw_0, ALL_FORECAST_MONTH."Gen3,ALL_FORECAST_MONTH" saw_1, ALL_PRODUCTS."Gen2,ALL_PRODUCTS" saw_2, "FCST".FORECASTED_COST saw_3, "FCST".FORECASTED_PRICE saw_4, "FCST".FORECASTED_QTY saw_5, "FCST".FORECAST_AMOUNT saw_6 FROM "FCST_CUBE" ORDER BY saw_0, saw_1, saw_2
I am able to telnet the HostName on the port# from BI server. I am not sure what I am missing. Can someone please help?
Regards,
Changa

Tony,
thanks for your reply...
I thought about that as well but the 14 cubes (countries) are allowed to add level 0 members so in the mapping table i need to point to the correct Essbase cube as well..
I wasn't able to find any script that is triggered while updating the mapping (by clicking browse for target value)..
So adjusting the connect does solve my problem partially since there's some kind of cache that i need to refresh..
Do you know if this is possible?
Otherwise i have to go for the multiple adapter solution.
Kind regards,

Enabling drill through from Essbase cube to drill through report

The requirement is that I keep summary level information in the Essbase cube and detailed granular information (order level) in a relational table.I would like to enable drill through between the cube and the report.
Please advise what would be the best approach considering the current system architecture that is outlined below.( Hyperion suite 11.1.2.1).
Would also like to know drill thru vs hybrid analysis options.
1) ASO/BSO cube is populated through Oracle Data Integrator
2) The relational transactional table is also poulated through ODI.
3) The cube would hold summary level info while thr drill through report should provide the order level details in the same context as chosen in the cube.
Would appreciate guidance on the best way forward.
Thanks & Regards,
Anirban

Incidentally we had been trying to use Essbase studio as an option.But there are 2 oints that we are trying to investigate.
1) Can we bypass deployment of data and metadata everytime through Essbase studio after the initial outline is delpoyed? In the system architecture the relational tables are populated using ODI. We would like to load the data and metadata through ODI into the cube. Eeven then can we implement drill thru bypassing deployment through Essbase Studio?
2) If Essbase studio is imperative for drill through then what are the batch automation options for deployment through Essbase studio? Ideally the option should be after the relational tables are populated through ODI then the Essbase deployment should be invoked and batch script should load the data and metadata through Essbase Studio.
Please advise.
Thanks,
Anirban

E-mail Alerts from Essbase Cubes

Hi,
I have Essbase 7.1.3 windows server and We do lots of Cube processing through Batch Files.
I would like to have an option to send email alerts to the business users once we are done with the processing.
Say for example , I have a Deposits Essbase cube and once i am done with the calculation and Enable connects to the users i would like to send a mail notification " The Deposit Cube now available....."
Essbase have some thing called " Triggers..." But i am not sure how far will it help me.
Looking forward for your inputs.
Thnx,
MS

Okay, yes, I still use esscmd, so this example is for an esscmd script (some day I will convert them, I promise...).
The shell (batch) script that I use calls esscmd to do the job, and then scans the script (using the for command) for tokens. These tokens determine who gets an email depending on the outcome of the script. By encoding the messaging into the script, I can control the business logic at an appropriate level. The TITLE token is also used during the notification, but I left the logic out that builds the SUBJECT variable (for brevity)...
:TITLE Load Budget data to Daily Trends
:Job Notifications:
:ONERR [email protected]
:ONERR [email protected]
:ONSUCCESS [email protected]
:ONSUCCESS [email protected]
:ONSUCCESS [email protected]
:ONSUCCESS [email protected]
LOGIN "LocalHost" "<superuser>" "<superpassword>";
... etc.Here is the relevant part of the shell job that scans for tokens (the RESULT environment variable is set to either "ERR" or "SUCCESS" based on the output, with other variables set as needed):
TYPE %SCRFILE% | FIND ":ON%RESULT%" >Notify.tmp
FOR /f "tokens=2" %%a in (Notify.tmp) DO SendEmail -f %FROM% -t %%a -u "%SUBJECT%" -m "%MESSAGE%" -s %RELAY% -a %ATTACH%
ERASE /Q Notify.tmp

Essbase Studio: Failed to deploy Essbase cube

Hi
I have started working with Essbase studio sometime back and I am able to deploy BSO cube with success using the TBCSample Database which comes along with Essbase. Now I wanted to deploy ASO cube, as no sample database is available I thought to create one, I extracted ASOSamp using ODI to CSV files. Then I bulk inserted the csv extracts into MSSQL 2003 server which created 11 tables (Age, Geography, IncomeLevel, Measures, PaymentType, Product, Stores, Time TransactionType, Year). The above mentioned table does not have any keys(Primary, Foreign) as it is an Essbase export.
I then successful created ASO Cube Schema using the newly created sample database in MSSQL, validated cube schema without any errors.
Essbase Property Setting:
Measures Hierarchy is tagged as Dynamic Compression at dimension level
Time, Product and Year Hierarchy is tagged as Multiple Hierarchies Enabled, Year does not have multiple hierarchies but it has formulas for Variance and Variance % member. Is there a way to tag Year as Dynamic hierarchy?
But when I try to deploy the cube to Essbase I receive following errors:
Failed to deploy Essbase cube
Caused By: Cannot end incremental build. Essbase Error(1060053): Outline has errors
\\Record #1 - Member name (Time) already used
+ S Time + S
\\Record #6 - Member name (1st Half) already used
MTD + S 1st Half + S
\\Record #7 - Member name (2nd Half) already used
MTD + S 2nd Half + S
\\Record #21 - Member name (Qtr1) already used
Qtr1 + S Feb + S
\\Record #22 - Member name (Qtr1) already used
Qtr1 + S Jan + S
\\Record #23 - Member name (Qtr1) already used
Qtr1 + S Mar + S
\\Record #24 - Member name (Qtr2) already used
Qtr2 + S Apr + S
\\Record #25 - Member name (Qtr2) already used
Qtr2 + S Jun + S
\\Record #26 - Member name (Qtr2) already used
Qtr2 + S May + S
\\Record #27 - Member name (Qtr3) already used
Qtr3 + S Aug + S
\\Record #28 - Member name (Qtr3) already used
Qtr3 + S Jul + S
\\Record #29 - Member name (Qtr3) already used
Qtr3 + S Sep + S
\\Record #30 - Member name (Qtr4) already used
Qtr4 + S Dec + S
\\Record #31 - Member name (Qtr4) already used
Qtr4 + S Nov + S
\\Record #32 - Member name (Qtr4) already used
Qtr4 + S Oct + S
\\Record #33 - Member name (Time) already used
Time + S MTD + S
\\Record #34 - Member name (Time) already used
Time ~ S QTD ~ S
\\Record #35 - Member name (Time) already used
Time ~ S YTD ~ S
\\Record #9 - Error adding Attribute to member QTD(Jan) (3320)
\\Record #9 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD + S QTD(Jan) + S [Jan]
\\Record #10 - Error adding Attribute to member QTD(Apr) (3320)
\\Record #10 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Apr) ~ S [Apr]
\\Record #11 - Error adding Attribute to member QTD(Aug) (3320)
\\Record #11 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Aug) ~ S [Jul]+[Aug]
\\Record #12 - Error adding Attribute to member QTD(Dec) (3320)
\\Record #12 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Dec) ~ S [Oct]+[Nov]+[Dec]
\\Record #13 - Error adding Attribute to member QTD(Feb) (3320)
\\Record #13 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Feb) ~ S [Jan]+[Feb]
\\Record #14 - Error adding Attribute to member QTD(Jul) (3320)
\\Record #14 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Jul) ~ S [Jul]
\\Record #15 - Error adding Attribute to member QTD(Jun) (3320)
\\Record #15 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Jun) ~ S [Apr]+[May]+[Jun]
\\Record #16 - Error adding Attribute to member QTD(Mar) (3320)
\\Record #16 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Mar) ~ S [Jan]+[Feb]+[Mar]
\\Record #17 - Error adding Attribute to member QTD(May) (3320)
\\Record #17 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(May) ~ S [Apr]+[May]
\\Record #18 - Error adding Attribute to member QTD(Nov) (3320)
\\Record #18 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Nov) ~ S [Oct]+[Nov]
\\Record #19 - Error adding Attribute to member QTD(Oct) (3320)
\\Record #19 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Oct) ~ S [Oct]
\\Record #20 - Error adding Attribute to member QTD(Sep) (3320)
\\Record #20 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
QTD ~ S QTD(Sep) ~ S [Jul]+[Aug]+[Sep]
\\Record #36 - Error adding Attribute to member YTD(Jan) (3320)
\\Record #36 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD + S YTD(Jan) + S [Jan]
\\Record #37 - Error adding Attribute to member YTD(Apr) (3320)
\\Record #37 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Apr) ~ S [Qtr1]+[Apr]
\\Record #38 - Error adding Attribute to member YTD(Aug) (3320)
\\Record #38 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Aug) ~ S [1st Half]+[Jul]+[Aug]
\\Record #39 - Error adding Attribute to member YTD(Dec) (3320)
\\Record #39 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Dec) ~ S [1st Half]+[Qtr3]+[Qtr4]
\\Record #40 - Error adding Attribute to member YTD(Feb) (3320)
\\Record #40 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Feb) ~ S [Jan]+[Feb]
\\Record #41 - Error adding Attribute to member YTD(Jul) (3320)
\\Record #41 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Jul) ~ S [1st Half]+[Jul]
\\Record #42 - Error adding Attribute to member YTD(Jun) (3320)
\\Record #42 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Jun) ~ S [1st Half]
\\Record #43 - Error adding Attribute to member YTD(Mar) (3320)
\\Record #43 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Mar) ~ S [Qtr1]
\\Record #44 - Error adding Attribute to member YTD(May) (3320)
\\Record #44 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(May) ~ S [Qtr1]+[Apr]+[May]
\\Record #45 - Error adding Attribute to member YTD(Nov) (3320)
\\Record #45 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Nov) ~ S [1st Half]+[Qtr3]+[Oct]+[Nov]
\\Record #46 - Error adding Attribute to member YTD(Oct) (3320)
\\Record #46 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Oct) ~ S [1st Half]+[Qtr3]+[Oct]
\\Record #47 - Error adding Attribute to member YTD(Sep) (3320)
\\Record #47 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
YTD ~ S YTD(Sep) ~ S [1st Half]+[Qtr3]
\\Record #2 - Incorrect Dimension [Year] For Member [ParentName] (3308)
ParentName Consolidation DataStorage MemberName Consolidation DataStorage Formula
\\Record #1 - Member name (Promotions) already used
S Promotions S
\\Record #2 - Incorrect Dimension [Promotions] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #3 - Member name (Promotions) already used
Promotions S Coupon S
\\Record #4 - Member name (Promotions) already used
Promotions S Newspaper Ad S
\\Record #5 - Member name (Promotions) already used
Promotions S No Promotion S
\\Record #6 - Member name (Promotions) already used
Promotions S Temporary Price Reduction S
\\Record #7 - Member name (Promotions) already used
Promotions S Year End Sale S
\\Record #2 - Incorrect Dimension [Payment Type] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #2 - Incorrect Dimension [Transation Type] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #22 - Member name (Home Entertainment) already used
Home Entertainment + S Home Audio/Video + S
\\Record #23 - Member name (Home Entertainment) already used
Home Entertainment + S Televisions + S
\\Record #24 - Member name (Other) already used
Other + S Computers and Peripherals + S
\\Record #25 - Incorrect Dimension [Product] For Member [ParentName] (3308)
ParentName Consolidation DataStorage MemberName Consolidation DataStorage
\\Record #26 - Member name (Personal Electronics) already used
Personal Electronics + S Digital Cameras/Camcorders + S
\\Record #27 - Member name (Personal Electronics) already used
Personal Electronics + S Handhelds/PDAs + S
\\Record #28 - Member name (Personal Electronics) already used
Personal Electronics + S Portable Audio + S
\\Record #31 - Member name (All Merchandise) already used
Products + S All Merchandise + S
\\Record #32 - Member name (High End Merchandise) already used
Products ~ S High End Merchandise ~ S
\\Record #33 - Member name (Systems) already used
Systems + S Desktops + S
\\Record #34 - Member name (Systems) already used
Systems + S Notebooks + S
\\Record #18 - Error adding Attribute to member Digital Recorders (3320)
Home Audio/Video + S Digital Recorders + S
\\Record #36 - Error adding Attribute to member Flat Panel (3320)
Televisions + S Flat Panel + S
\\Record #37 - Error adding Attribute to member HDTV (3320)
Televisions + S HDTV + S
\\Record #8 - Incorrect Dimension [Income Level] For Member [ParentName] (3308)
ParentName DataStorage MemberName DataStorage
\\Record #1 - Member name (Geography) already used
S Geography S
\\Record #2 - Error adding member 27425 (3317)
\\Record #2 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
A M F GREENSBORO - NC S 27425 S 336
\\Record #3 - Error adding member 36310 (3317)
\\Record #3 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABBEVILLE - AL S 36310 S 334
\\Record #4 - Error adding member 29620 (3317)
\\Record #4 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABBEVILLE - SC S 29620 S 864
\\Record #5 - Error adding member 67510 (3317)
\\Record #5 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABBYVILLE - KS S 67510 S 316
\\Record #6 - Error adding member 58001 (3317)
\\Record #6 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERCROMBIE - ND S 58001 S 701
\\Record #7 - Error adding member 42201 (3317)
\\Record #7 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - KY S 42201 S 502
\\Record #8 - Error adding member 21001 (3317)
\\Record #8 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - MD S 21001 S 410
\\Record #9 - Error adding member 39730 (3317)
\\Record #9 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - MS S 39730 S 601
\\Record #10 - Error adding member 28315 (3317)
\\Record #10 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERDEEN - NC S 28315 S 910
\\Record #11 - Error adding member 79311 (3317)
\\Record #11 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABERNATHY - TX S 79311 S 806
\\Record #12 - Error adding member 79601 (3317)
\\Record #12 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABILENE - TX S 79601 S 915
\\Record #13 - Error adding member 79608 (3317)
\\Record #13 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
ABILENE - TX S 79608 S 915
\\Record #14 - Error adding member 79698 (3317)
\\Record #14 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
Are these errors due to data source, if yes what could be possible work around?
Is there any problem with Essbase properties which I have set if so then when I validate cube schema why I dn't get any errors?
Please help me, I am stuck here not able to deploy ASO Cube.
Thanks in advance

Hii
I have the same problem , you have.
did you manage to solve it ??
Thanks in advance

Combining relation facts with dimensions from an Essbase cube

Hi!
I am having trouble combining relational measures (from EBS) with dimensions from an Essbase cube. The dimensions that we want to use for reporting (drilling etc) are in an Essbase cube and the facts are in EBS.
I have managed to import both the EBS tables and the cube into OBIEE (11.1.15) and I have created a business model on the cube. For the cube I converted the accounts dimension to a value based dimension, other than that it was basically just drag and drop.
In this business model I created a new logical table with an LTS consisting of three tables from the relational database.
The relational data has an account key that conforms to the member key of the accounts dimension in the Essbase cube. So in the accounts dimension (in the BMM layer) I mapped the relational column to correct column (that is already mapped to the cube) - this column now has two sources; the relational table and the cube. This account key is also available in the LTS of my fact table.
The content levels for the LTS in the fact table have all been set to detail level for the accounts dimension.
So far I am able to report on the data from the fact table (only relational data) and I can combine this report with account key from the account dimension (because this column is mapped to the relational source as well as the cube). But if expand the report with a column (from the accounts dimension) that is mapped only to the cube (the alias column that contains the description of the accounts key), I get an error (NQSError 14025 - see below).
Seeing as how I have modeled that the facts are connected to the dimension through the common accounts key, I cannot understand why OBIEE doesn't seem to understand which other columns - from the same dimension - to fetch.
If this had been in a relational database I could have done this very easily with SQL; something along the lines of select * from relational_fact, dim_accounts where relational_fact.account_key=dim_accounts.account_key.
Error message:
[nQSError: 14025] No fact table exists at the requested level of detail
Edit:
Regards
Mogens
Edited by: user13050224 on Jun 19, 2012 6:40 AM

Avneet gave you the beginnings of one way, but left out that a couple of things. First, you would want to do the export of level zero only. Second, the export needs to be in column format and third, you need to make sure the load rule you use is set to be additive otherwise the last row will overwrite the previouse values.
A couple of other wats I can think of doing this
Create a replicated partition that maps the 3 non used dimensiosn to null (Pick the member at the top of the dimension in your mapping area)
Create a report script to extract the data putting the three dimensions in the page so they don't show up.
Use the custom defined function jexport in a calc script to get what you want

Update member count error for essbase cube

Whenever i import a cube from essabse into obiee. i get the following error when i click on "update member count" on any member in the Physical layer of the obiee administration.
this problem comes even if i import a different cube, meaning this is not due to essbase error.
[NQODBC][SQL_STATE:HY0000][nQSError: 10058] A general error has occurred.
[nQSError:43093] An error occured while processing the EXECUTE PHYSICAL statement.
Essbase Error: Unknown Member Measures.xxxyyyxxxCount used in query
kindly help!!

i am using version 11.1.1.3
i have created an holap cube in Essbase integration services. i have created olap model using rdbms source in the EIS. however i am unable to access the rdbms level(hybrid analysis enabled) data of the essbase cube in obiee.

Multiple source columns from Oracle DB to Hyperion Essbase cube

Hi Experts ,
We have a Source as oracle table to the target Hyperion Essbase Cube(Planning) 11.1.2 using ODI 11g.
Right now my issue is We need to map multiple columns from Oracle DB to One Dimension in Essbase (Planning).
For example -> * In Oracle table i have columns as Name,Volume,unit and item *
In Essbase the dimension called "*CatDefinition has lower level members as Name,Volume,unit and item * "
Now using ODI ,* I want to map the oracle table columns(Multiple) to the dimension(Catdefinition) ? * Please suggest me with idea to achieve multiple column mapping to the single dimension in Essbase .
Thanks in Advance !
Keny Alex

Do you even need FDM? You could build a load rule in Essbase directly. If you need to map, then you would register the Essbase target adapter.

Integrating Essbase cubes with Oracle Tables in BI Server

I'm trying to link together data from an aggregated Essbase Cube with some static table data from our oracle system. Both the essbase and oracle data exist correctly in their own right in the physical, business and presentation levels. Aggragted data is client sales, static data is client details
Within the OBIEE Administration tool I've tried to drag the physical oracle table for clients onto the clients essbase section in the business area, and it seems to work OK, until you try and report on them together and I get the following error:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 42043] An external aggregate is found in an outer query block. (HY000)
Can anyone advise on what I'm doing wrong?
Thanks

Thanks Christian I found some very useful articles (one or two by you) - I'll have to look harder on the net before posting.
One thing I found out, with respect to vertical federation, that others may benefit from, is that I fuond it much easier to start from the most detailed level and then attach the less detailed source rather start with the less detailed and add the additional on.

Exporting set of measures with aliases into essbase cube

We were wandering if there is an easy way to import bunch of measures with aliases into Essbase cube rather then entering them one by one?
thank you

Simplest way, would be to create a spreadsheet with the Measures and alias listed in column format.
You can organize them in Generation, Level or Parent-Child format.
Create a dimension load rule that maps the columns to properties in Essbase.
When you want to modify the Measures dimension layout, change the spreadsheet and rerun the load rule.
Brian Chow

Dynamically connect to multiple Essbase cubes from 1 adapter

Hi Guys,
i have 14 Essbase cubes (containing the same dimensions).
What i like to accomplish is that based on the selected location in the POV an essbase cube is selected..
I've updated the connect action with:
If RES.pstrLoc = "SampleGreece" Then
                    objHW.Connection.PstrDatabase = "TstGRE"
               ElseIf RES.pstrLoc = "SampleSpain" Then
                    objHW.Connection.PstrDatabase = "TstSPA"
               Else
                    objHW.Connection.PstrDatabase = API.DataWindow.DBTools.fGlobalOptionGet(API.IntBlockMgr.IntegrationMgr.PstrSysKey & "DBName").Value
               End If
And this works fine for the first location..
However, when i change the pov to another location the 'browse for target value' still points to the first one. After re-logon it works fine for the new location.
It looks like its stored in some kind of cache memory so i'm looking for a method to clear this cache or to reconnect while changing the POV.
It's FDM and Essbase 11.1.1.3
Thanks in advance,
Marc

Tony,
thanks for your reply...
I thought about that as well but the 14 cubes (countries) are allowed to add level 0 members so in the mapping table i need to point to the correct Essbase cube as well..
I wasn't able to find any script that is triggered while updating the mapping (by clicking browse for target value)..
So adjusting the connect does solve my problem partially since there's some kind of cache that i need to refresh..
Do you know if this is possible?
Otherwise i have to go for the multiple adapter solution.
Kind regards,

Essbase cube optimization

Hi All,
I know a lot has been discussed on optimizing Essbase cubes and others but need to get some more guidance on the same.
Scenario:
Essbase app 11.1.2.2 with 2 dense and 6 sparse as below:
Account ~500 stored (dense)
Period ~13 stored (dense)
Fin Element ~2000 stored (sparse)
Entity ~10000 stored (sparse)
Prod ~10000 stored (sparse)
* Year, Version and Scenario are non-aggregating dimensions
Stats: Block size ~50kb and lev0 size ~400MB
The issue is that there are few monthly end calc scripts that takes more than ~3-4hrs /script to execute on the cube.
I had done the following things so far:
1- Provide custom hour glass outline: Period-Accounts-Fin Element- Prod - Entity - Yr - Version -Scenario
2- Changed few member properties
3- Optimized script
However the run time for the scripts is equal to what was earlier.
A quick question:
If I make dimension 'Fin element' as dense, block size is ~80MB. I guess 100KB is max recommended, but need to confirm on this.
Kindly guide ahead as in what else should I try ahead and do..
Regards..

Hi
This is all a little subjective....but....
Are your upper level members of dense dims dynamic or are you having to run any CALC DIM commands against them within the lengthy BR's? If you are then these will probably be responsible for a fair chunk of the time - could always pull these out and run separately to see exactly how much time they take.
JB

EAL replicated Essbase cube empty

Hi,
I am trying to build a replicated Essbase cube using EAL from HFM, all 11.1.2.2. The EAL bridge shows green across the board, so all good. When I build a transparent cube, I can see the data in Essbase, nio problems. Now I am trying to build a replicated cube, using the same region and Essbase grid definition as for the transparent. The outline gets built fine, and when I go to retrieve, it does the retrieve, shows the status bar, and eventually comes back with Successful.
However when I look at the replicated cube there is no data in it, no blocks were created, nothing. When I look in the EAL log, there are no errors, the last entry refers to Extract Region with a list of the dimensions, nothing more. I tried using both Embedded and a specific APS URL in the Essbase cube link in EAL. Like I said the transparent cube is fine, so I believe the region and grid definitions are valid, so I cannot understand why the data is not in the replicated cube.
Anyone has experienced anything similar and might have some hints?

Could the level 0 data have been zeroed out, and no agg run to propagate the zeros (or #Missing) to upper levels?
Did you at one time have some data in the database, then lock n send to overwrite?
If you had performed a database reset, that would leave no page file. If you simply overwrote data, then you could have some fragmentation (when data is overwritten, the data is written to a new space in the page file with the index pointing to new data. This leaves the prior data behind with no index pointer to it, but it's still in the page file.)
Was the export file of all data, or level zero data?
If it was level 0 export, perform an export all (3mb is not that much) to verify if there is any data. If not, I'd chalk it up to fragmentation.
Robert

Show key content of essbase cube in BIEE

After importing Essbase cube into BI admin tool, I can query its content in BI Answer.
But when I display the dimensional content(says, Gen5,Loc1), it displays Alias content rather than the key content. What should I do in BI admin tool to show the key content? or are any settings required in Essbase?

That's expected behaviour. As soon as there's an Alias, it gets used. Otherwise, it defaults back to the acutal member name.
Yes, you can change this, but only for the lowest level of the hierarchy. We discussed this already some times togehter with the alternatives.
Here's the official modelling guide BTW: http://www.oracle.com/technology/products/bi/pdf/obiee-essbase-modeling-guide.pdf --> 7.3 on page 19.

Essbase cube level order

Similar Messages

Maybe you are looking for