Multiple Essbase-derived measure dimensions in OBI EE

Hi guys,
I have a requirement here which basically requires the usage of measures coming from two different measure dimensions of Essbase (Account and Scenario) next to each other in reports.
I set both to dim type "measure dimension" and made sure the respective measures exist as physical cube columns. Then I tried two alternatives:
1.) One logical fact table - result spool:
-------------------- Logical Request (before navigation):
RqList distinct
Actual:{DAggr(Account.Actual by { } )} as c1 GB,
Actual LY:{DAggr(Account.Actual LY by { } )} as c2 GB,
Target:{DAggr(Account.Target by { } )} as c3 GB,
Vs Actual LY:{DAggr(Account.Vs Actual LY by { } )} as c4 GB,
Vs Actual LY %:{DAggr(Account.Vs Actual LY % by { } )} as c5 GB,
Ops:{DAggr(Account.Ops by { } )} as c6 GB,
Sales_In:{DAggr(Account.Sales_In by { } )} as c7 GB
+++Administrator:2a0000:2a000a:----2008/11/10 14:29:55
-------------------- Execution plan:
RqList <<60982>> {for database 0:0,0} distinct
D1.c1 as c1 {for database 0:0,0},
D1.c2 as c2 {for database 0:0,0},
D1.c3 as c3 {for database 0:0,0},
D1.c4 as c4 {for database 0:0,0},
D1.c5 as c5 {for database 0:0,0},
D1.c6 as c6 {for database 0:0,0},
D1.c7 as c7 {for database 0:0,0}
Child Nodes (RqJoinSpec): <<61009>> {for database 0:0,0}
RqList <<60949>> {for database 3023:179879:Full cube,34}
AggrExternal(INSIT.Actual) as c1 GB {for database 3023:179879,34},
AggrExternal(INSIT.Actual LY) as c2 GB {for database 3023:179879,34},
AggrExternal(INSIT.Target) as c3 GB {for database 3023:179879,34},
AggrExternal(INSIT.Vs Actual LY) as c4 GB {for database 3023:179879,34},
AggrExternal(INSIT.Vs Actual LY %) as c5 GB {for database 3023:179879,34},
AggrExternal(INSIT.Ops) as c6 GB {for database 3023:179879,34},
AggrExternal(INSIT.Sales_In) as c7 GB {for database 3023:179879,34}
Child Nodes (RqJoinSpec): <<60952>> {for database 3023:179879:Full cube,34}
INSIT T179892
) as D1
+++Administrator:2a0000:2a000a:----2008/11/10 14:29:55
-------------------- Sending query to database named Full cube (id: <<60949>>):
select
{ {Scenario}.{Actual},
{Scenario}.{Actual LY},
{Scenario}.{Target},
{Scenario}.{Vs Actual LY},
{Scenario}.{Vs Actual LY %},
{Scenario}.{Ops},
{Scenario}.{30001}
} on columns
from {INSIT_C.INSIT}
2.) Two logical fact tables - result spool:
+++Administrator:2a0000:2a0007:----2008/11/10 14:49:23
-------------------- Logical Request (before navigation):
RqList distinct
Account.Sales as c1 GB,
Account.Backlog as c2 GB,
Account.Sales_In as c3 GB,
Scenario.Act vs Bud % as c4 GB,
Scenario.Act vs Budget as c5 GB
OrderBy: c1 asc, c2 asc, c3 asc, c4 asc, c5 asc
+++Administrator:2a0000:2a0007:----2008/11/10 14:49:23
-------------------- Query Status: Query Failed: {nQSError: 15018} Incorrectly defined logical table source (for fact table Account) does not contain mapping for {Scenario.Act vs Bud %, Scenario.Act vs Budget}.
+++Administrator:2a0000:2a0009:----2008/11/10 14:49:28
-------------------- Logical Request (before navigation):
RqList distinct
Account.Sales as c1 GB,
Account.Backlog as c2 GB,
Account.Sales_In as c3 GB
OrderBy: c1 asc, c2 asc, c3 asc
+++Administrator:2a0000:2a0009:----2008/11/10 14:49:28
-------------------- Execution plan:
RqList <<37039>> {for database 0:0,0} distinct
D1.c3 as c1 GB {for database 0:0,0},
D1.c2 as c2 GB {for database 0:0,0},
D1.c1 as c3 GB {for database 0:0,0}
Child Nodes (RqJoinSpec): <<37047>> {for database 0:0,0}
RqList <<37051>> {for database 3023:179879:Full cube,34}
INSIT.Sales_In as c1 GB {for database 3023:179879,34},
INSIT.Backlog as c2 GB {for database 3023:179879,34},
INSIT.Sales as c3 GB {for database 3023:179879,34}
Child Nodes (RqJoinSpec): <<37059>> {for database 3023:179879:Full cube,34}
INSIT T179892
) as D1
OrderBy: c1 asc, c2 asc, c3 asc {for database 0:0,0}
+++Administrator:2a0000:2a0009:----2008/11/10 14:49:29
-------------------- Sending query to database named Full cube (id: <<37051>>):
select
{ {Scenario}.{Sales}{Scenario}.{Backlog}{Scenario}.{30001}
} on columns
from {INSIT_C.INSIT}
+++Administrator:2a0000:2a0009:----2008/11/10 14:49:29
-------------------- Query Status: Query Failed: Essbase Error: Unknown Member Scenario.Sales used in query
So basically neither of the two options work at all. Most of the time he just assumes that all that measures are coming from the last hierarchy I defined as a measure dimension...hence the unknown member error.
Likewise with the two logical tables, he screws the query up completely and doens't even manage to resolve the column mappung against the logocal tables.
Has anyone ever tried to mix measure dimensions retrieved from Essbase? Using OBI EE it's very tricky to define the acutal measure containing data points in Essbase.
Cheers,
C.
Edited by: Christian Berg on Nov 10, 2008 2:58 PM
Edited by: Christian Berg on Nov 10, 2008 3:00 PM
Sorry for the reformatting...the forum doesn't like the square brackets in the BI server logs...

Solved. Takes some nibbling around in Answers, but doable with unioning and pivot tables.
Cheers,
C.

Similar Messages

Essbase's attribute dimensions in OBI 10.3.4.1

Hello everybody:
As far as I know, it is possible to use Essbase attribute dimensions in OBI 10.3.4.1. But, in your opinion, is there any problem when integrating them or they work in OBI as standard dimensions?. Have somebody had any issue with this integration?
Thank you in advance
Regards,
Javier

Hello:
I have read this article before writing this post. But it refers to Essbase 9.3.1 (I refer to 11.1.1.3) and OBI 10.1.3.3.2 (I refer to 10.3.4.1). One of the goals of my questions is knowing if something has changed since that article was written, because it implies some manual changes in the rpd.
Thank you
Regards
Javier
Edited by: Javi M on 28-feb-2011 4:51

Count distinct derived measure on SCD type 2 dimension

Hi,
I have 2 dimension tables with SCD type 2 and one fact table :
DIM1 :
DIM1_SURR_KEY
DIM1_NAT_KEY
DIM1_PROPERTY1
DIM1_PROPERTY2
EFFECTIVE_DATE
EXPIRATION_DATE
DIM2 :
DIM2_SURR_KEY
DIM2_NAT_KEY
DIM2_PROPERTY1
DIM2_PROPERTY2
EFFECTIVE_DATE
EXPIRATION_DATE
FACT :
DIM1_SURR_KEY
DIM2_SURR_KEY
MEA1
MEA2
Dimension and fact tables are joined with : DIM1_SURR_KEY and DIM2_SURR_KEY.
In my business layer fact table, I would like to define this derived measure : count distinct of DIM1_NAT_KEY.
I tried to add new source for the fact table. I also tried an alias of DIM1 in physical layer.
Nothing works as I want : In Answers, if I select the fact and the count distinct, it works. Even if I select property of DIM1. But if I select property of DIM2, my count distinct return 0 (in SQL sent to Oracle DB, the formula is replaced with NULL).
Is it possible (and how) to count the number of Nat_Key with a derived measure defined in business layer ?
If not, I’ll define materialized view on fact table with natural key and dimension ID.
My first goal is to avoid end user to redefine derived column in Answers for each reports.
Thanks for your help

Hi,
my advise is to map the DIM1_NAT_KEY iside the Fact Table of the Business Model, so you have a new Logical Table Source inside the Logical Fact Table that maps the DIM1_NAT_KEY as a measure. Define the Level for this Logical Table Source and set the COUNT DISTINC aggregation. In this way OBIEE knows that that measure is inside a fact an it treat like that.
I hope it helps.
Regards,
Gianluca

Multiple source tables for Measures dimension.

Hi,
We have two different SQL source tables for the Measure dimension in our project. Both the tables have the same structure but the Measures they contain are different. Based on certain condition Essbase will have to pick up Measures from one of the two tables. So basically the source table changes based on the condition. Is it possible to design rule files to achieve this? Please help me with this.
Thanks,
Krishna

as I am sure many will say essbase and load rules are not really an ETL tools.^^^ :)
Glenn is going to counter with a "I know how to do this in three steps using create column as text, join, and a oft-overlooked but awesome command that everyone but Tom Tortolani (I think I have the spelling on that right -- he was the Arbor employee that wrote Load Rules) forgot.
I 100% agree with John -- why not do it in SQL?
Regards,
Cameron Lackpour
Edited by: CL on Jan 23, 2013 6:33 AM
Misspelt Tom's name

Rolling up multiple leaves on a dimension into a single measure

I'm sure this is a common problem but I cannot find any talk of it with my Google searching.
The problem I am having is when I need to a get a single measure, using an 'Average' aggregate, for multiple leaves in a dimension.
For example, say I have a geography dimension and I need a single score for the three countries GB, HK and US combined, I might do this (though it won't be good enough):
select avg(s.score) as score
from my_cube_view s
where s.geography in ('GB','HK','US')
It's not good enough because the avg() needs weighting, GB, HK and US not containing an equal number of facts each (their individual scores will already be averaged by the cube).
Is there a way for the cube to do this calculation for me? Or should I, when wanting to rollup scores this way, revert to manually averaging up the fact scores?
Hope that makes sense,
Dominic
Edited by: Dominic Watson on Sep 8, 2011 5:02 AM

You should be able to generate weighted averages. Check the Aggregation Operators section of the OLAP User's Guide to see the different hierarchical aggregation options for averages.

'Essbase Error: Repeated dimension [Accounts] in MDX query'

Dear Essbase Gurus,
I have an error in a query passed to my Essbase cube from an OBI front end, but the errors states quite clearly that it is an essbase error:
'Essbase Error: Repeated dimension Accounts in MDX query'
This is the query it generated:
With
set Accounts3 as 'Accounts.Generations(3).members'
set Attribute Calculations2 as '[Attribute Calculations].Generations(2).members'
set Events5 as 'Events.Generations(5).members'
set Month3 as 'Month.Generations(3).members'
set Scenario2 as 'Scenario.Generations(2).members'
set Year2 as 'Year.Generations(2).members'
set Axis1Set as 'crossjoin ({Accounts3},crossjoin ({Attribute Calculations2},crossjoin ({Events5},crossjoin ({Month3},crossjoin ({Scenario2},{Year2})))))'
select
{Measures.Total e-revenue} on columns,
NON EMPTY {Axis1Set} properties ANCESTOR_NAMES, GEN_NUMBER on rows
from Richmond.RichPOC
As an Essbase newbie I'm unfamiliar with mdx and have no idea what this means, any help would be appreciated.
Thanks
Ed
Edited by: Ed Higgins, AltiusConsulting.com on Oct 15, 2008 9:26 AM

Hi garycris,
Thanks for taking a look, I fear you may have hit the nail on the head, as I mention we are reporting on this using OBIEE, so we have imported the cube (BSO) into our OBI repository, OBI flattens the cube to make it look like a star schema it doesn't recognise the Accounts dimension correctly so we have to set it to be of type 'Other' after we have imported it, otherwise none of the figures in the Accounts dimension are actually reported (you can see the members but when included in a query no data is returned).
Another issue we found was that OBIEE appeared to substitute the name 'Measures' for Accounts when building the query, so we made 'Measures' the default alias for the Accounts dimension, to add to the issue I probably should have mentioned that the aggregation rule in OBIEE for this fact column has been set to SUM rather than External_Agg, but Oracle support have previously indicated that this is OK to do. The issue originally arose because we wanted to extend on of our dimensions with additional attributes stored in a SQL database table.
Sorry it is all a bit messy, the whole OBI with Essbase as a source is still relatively new, and it looks like there may be a few things for the mighty O to iron out, I posted this in here because the OBIEE forum has no posts with similar issues, so thanks for your help so far and anything else you can add.
Ed

The "Measures" dimension contains more than one hierarchy... Collation issue

It appears that an Excel query pased through to SSAS has a "measures" with lowercase "m" when analysis services expects an uppercase "M" so it should look like "Measures". Is there a fix in excel to allow
the correct passing of "Measures" member name to the cube?
BTW, I have NO Calculations in the cube.
In excel 2013 when I pivot with a pivot table connected to a case sensitive collation (non default config)
cube and perform a filter by "Keep only Selected Items" I get the error "The 'Measures' dimension contains more than one hierarchy, therefore the hierarchy must be explicity specified".
When I revert back to server wide setting to case insensitive, and I preform the exact same pivoting function it works without error. The problem appears to be that excel does not understand the server collation setting.
When I run SQL Server Profilier I narrowed down the MDX statement run in Excel that gives me an error to this:
with
member measures.__XlItemPath as
Generate(
Ascendants([Employee].[Location Code].currentmember),
[Employee].[Location Code].currentmember.unique_name,
"|__XLPATHSEP__|"
member measures.__XlSiblingCount as
Generate(
Ascendants([Employee].[Location Code].currentmember),
AddCalculatedMembers([Employee].[Location Code].currentmember.siblings).count,
"|__XLPATHSEP__|"
member measures.__XlChildCount as
AddCalculatedMembers([Employee].[Location Code].currentmember.children).count
select { measures.__XlItemPath, measures.__XlSiblingCount, measures.__XlChildCount } on columns,
[Employee].[Location Code].&[01W]
dimension properties MEMBER_TYPE
on rows
from [Metrics]
cell properties value
Playing around with the query I discovered that if I capitalize the first letter of the "with measures" member, the statement works.
with
member Measures.__XlItemPath as
Generate(
Ascendants([Employee].[Location Code].currentmember),
[Employee].[Location Code].currentmember.unique_name,
"|__XLPATHSEP__|"
member Measures.__XlSiblingCount as
Generate(
Ascendants([Employee].[Location Code].currentmember),
AddCalculatedMembers([Employee].[Location Code].currentmember.siblings).count,
"|__XLPATHSEP__|"
member Measures.__XlChildCount as
AddCalculatedMembers([Employee].[Location Code].currentmember.children).count
select { measures.__XlItemPath, measures.__XlSiblingCount, measures.__XlChildCount } on columns,
[Employee].[Location Code].&[01W]
dimension properties MEMBER_TYPE
on rows
from [Metrics]
cell properties value
Also, I realise that I could change the collation on just the cube itself to case insenstive to get this to work, but I really don't want to do an impact analysis of running a mixed collation environment.
So, my question is: Is there an excel fix that will allow me to run a case sensitve cube and allow me to click on filter and filter by "keep only selected items" or "Hide selected Items"? All other filtering works, it's only those two
filtering options error for me.
Here are the versions I'm working with:
Excel 2013 (15.0.4535.1507) MSO(15.0.4551.1007) 32-bit Part of Microsoft Office Professional Plus 2013
Microsoft Analysis Server Enterprise 2012 11.0.3000.0
Any help would be appreciated. Thank you in advance!

Hi, i assume this logic is for Dimension formula?
If you have multiple hierarchy like ParentH1 and ParentH2 you should use FormulaH1 and FormulaH2 and not FORMULA column.
in FORMULAH1
[Account.H1].[Account_A] / [Account.H1].[Account_B]

Use of Essbase types measures in Planning v.11.1.2.2.

Hi. Can I use Essbase date type measures in Planning 11.1.2.2? I want to store contract start and contract end dates, possibly in a Measures dimension separate from the Accounts dimension.
Thanks in advance,.

Typed measures are not yet supported.
Cheers
John
http://john-goodwin.blogspot.com/

Essbase Date Measures in OBIEE

Dose Essbase Date Measures supported by OBIEE. Can we have a Essbase Date Measures display as a DATE in OBIEE?
Thanks

Hi Nilaksha,
I thought you might say that, I think this is because Essbase doesn't use data types as such, all data is stored as a value and characteristics of that data or how it is treated are more like meta data. This certainly rings true for the time dimensions I have seen. I think your best bet is to look at how you can format the numbers in the columns to make them appear in the format you require.
Regards
Ed

Essbase Date Measures as DATE in OBIEE

Hi,
We have created an ASO Cube in Essbase 11.1.1 with a Date Measure member call "Maturity Date" in Measure dimension (Tagged as Accounts).
Once we create the Physical layer Administrator tool on OBIEE this member refers as a double data type. And also when we create a criteria on Answers and displays the result it is shown as a number.
But on excel (with essbase add-on) data shows as a date. (Ex: 2009-09-20)
Can anyone tell what has to be changed to display a Date Measures as Date type on OBIEE or suggest another alternate.
Thanks!
Nilaksha.

Hi Nilaksha,
I thought you might say that, I think this is because Essbase doesn't use data types as such, all data is stored as a value and characteristics of that data or how it is treated are more like meta data. This certainly rings true for the time dimensions I have seen. I think your best bet is to look at how you can format the numbers in the columns to make them appear in the format you require.
Regards
Ed

Essbase Studio :: Measure Hierarchy :: "accounts not from fact"

Hello,
I am trying to build a Measure dimension in Essbase Studio not from fact table, but from parent-child metamodel table.
[http://docs.oracle.com/cd/E17236_01/epm.1112/est_user/frameset.htm?ch10s03s02s05.html]
Here I've read that I should add loose measure creating cube schema to Measures/Measure Hierarchy field.
What loose measure? I added column from fact table. In Essbase metamodel it created Measure dimension with that one member.
Is it even possible to create measure dimension not from fact table?
Thanx in advance,
L00ka
Edited by: 990463 on Feb 26, 2013 7:40 AM

The approach to take is to create a hierarchy from your measures table, then use the data column from your fact table to populate the measures box in the schema. When building the Essbase model, select the accounts dimension manually.
Oracle recommend that you build the measures dimension directly from your fact table, the above approach deems it a loose measure, that is it isn't based off the fact table.
Steve

Convert measure dimension to flat measure option not found

Hi All,
I am integrating Essbasse with BI. In the physical layer, I tried to convert measure dimension to flat measures. But when I right clicked my Essbase cube I am unable to find the
convert measure dimension to flat measures option . My BI machine version is 11.1.1.6 .Kindly guide me to overcome this issue.
Thanks and Regards
Sai

Sai, you first have to make sure that the properties of ONE of your dimensions is set to be a measures dimension. Then this option will show up upon right clicking.

Display aggregate total for multiple members of a dimension.

When multiple members of a dimension are selected in a row or column in Financial Reporting tool, it tends to display the result in multiple rows or columns. Is it possible to display the aggregate value of all the members and not display the individual details. I have tried the Auto Calculation which shows the "Total" but also shows the Individual members that were selected in multiple rows or columns. Any suggestions would be great.
Ajay.

Brian, I will post all my future questions in the Reporting Forum as you suggested. Coming back to my question, I do not want to display all the Individual members that I had selected in the report. I only need the aggregate value (Custom Totals) of all the Dimension members together.
eg: If I choose the following account members in one row (Salaries, Bonus, Advertising), I do not want to display the individual line items for the three members, I only need one row called "Expenses" that has the aggregate value for the three members. Essbase by default (even if I don't select "place selections in separate columns" ) will put the members in separate rows or columns.
Thanks.

How to Watermark multiple images with different dimensions in Photoshop ?

Is there any way that I can place a watermark on the right bottom of multiple images, no matter what dimension the images are? I have tried using Photoshop Scripts > image processor, but it works only for images of same dimension. I want to put watermark on multiple images of different dimensions. This is the output i got.
For the first image the watermark got placed correctly, but for the second image watermark got distracted. As you can clearly see the dimensions are different. Please suggest me some solution.

Open an image to watermark. We must have this open before we start recording an action or else it will keep opening this image and watermarking it over and over again.
In Photoshop go to Windows >> Actions
At the bottom of the Actions Palette you will see a little folder icon, click on it and create a new folder to hold you action in.
Once you have a folder to hold your action we need to hit the Create New Action button (next to the new folder Icon we just used.)
Give our new action a name and set a function key (if required.)
If the record button is not already depressed which it should be by default, hit it now to start recording our action. (located near the folder icon again but this time to the left)
Now that our action is recording go to File >> Place
When the dialog box comes up navigate to your previously created watermark file.
Hit the Place button
Position the watermark as you would normally have it (default is dead center) and hit enter.
Go to File >> Save as,navigate to where you want your watermarked images to finish up and hit save. DO NOT CHANGE THE FILE NAME if you do when you play the batch it will name all the files it saves the same over-writing each other.
Close the image we just watermarked.
when a save dialog comes up do not save the image.
On the Actions Palette hit stop recording.
Our Action is now recorded.
To process an entire folder of images we go to File >> Automate >> Batch
Select the folder in which your images are currently
Select the folder you wish to save the watermarked copies too.
Hit OK
Photoshop is now watermarking all the Images in the selected folder for you.

Need Multiple Units of Measure for a given material due to multiple vendors

Hello,
We have a requirement where we must have multiple units of measue (each, box, case, pallet) for a given material.
Background:
We have multiple vendors for one SAP material number. We need to store 4 levels of units of measure for each vendor+material combination.
Unit of Meaure levels
1. Each
2. Innerpack (ex: 12 each = 1 innerpack)
3. Box (ex: 36 eaches = 1 box)
4. Pallet (ex: 100 eaches = 1 pallet)
Standard SAP allows in MM01 additional data --> Units of Measure only 1 Ea, Box, Plt, etc.
Our requirement is to allow multiple Units of Measure due to multiple vendors providing the same material.
So, our unique combination is by a Material+Vendor.
We are considering adding the vendor name and vendor number to the material master --> additional data --> Units of Measure tab.
Does this seem like a good solution? What impacts do you foresee with approach?
Any alternatve solutions?
We thought we could enhance the purchasing info records to allow multiple units of measure too but then we need to also add many fields to hold the weight, lenght, height, width, volume, country of origin, etc.
Please recommend a best practice or solution to handle this requirement.
Thanks in advance!!!

Hi,
Maintain the alternative units in Material Master in Additional Data -> Units of Measure section with proper conversion factors.
Create individual info-records i.e. per mtl-vendor combination & in the info-record maintain the order unit, along with other details as required.
Now when you create a PO, the details will be read from the info-record. To test the same, create them in your sandbox & see if it meets your requirement.
Hope the above clarifies your query.
Regards,
Vivek

Multiple Essbase-derived measure dimensions in OBI EE

Similar Messages

Maybe you are looking for