Querying within a dimension

Hi,
New to SSAS cube in general.
I've build a bunch of reports in Excel using cubevalue functions.
How do i query an attribute within a dimension.
Eg. My Period dimension has Year->Half Year->Quarter-> Month
I want to know how you query which half year a month belongs to.
In SQL you'd just query select halfYear from dimDate where month = '201410'.
How's this done in a cube via excel and SSRS ?

Hi,
If you have a user defined hierarchy created by using these attributes you can easily achieve this by using Ancestor member function. Take a look into the following MDX against Adventure Works.
WITH CALCULATED MEMBER [Measures].[Ancestor Quarter] AS ANCESTOR([Date].[Calendar].CURRENTMEMBER, [Date].[Calendar].[Calendar Quarter]).ITEM(0).MEMBER_NAME
CALCULATED MEMBER [Measures].[Ancestor Semester] AS ANCESTOR([Date].[Calendar].CURRENTMEMBER, [Date].[Calendar].[Calendar Semester]).ITEM(0).MEMBER_NAME
SELECT {[Measures].[Sales Amount], [Measures].[Ancestor Quarter], [Measures].[Ancestor Semester]} ON COLUMNS,
{DESCENDANTS([Date].[Calendar].[Calendar Year].&[2007],[Date].[Calendar].[Month]) } ON ROWS
FROM [Adventure Works]
This will query the months of year 2007 and at the same time it is returning to what Quarter and Semester each month belongs to. Here is the final result.
I hope this will give you an idea.
Best regards...
Chandima Lakmal Fonseka

Similar Messages

1:N relationships within a dimension

We are using OBIEE 10.1.3.3
I have a request from users where they want attributes within a dimension where those attributes have a 1:N relationship.
Example, Sales is dimensioned by Customer and Time.
The granularity of the Sales Fact is Day and Customer.
Now each customer can be know by different names and that attribute is known as Customer Synonym. There is a 1:N relationship between Customer and Customer Synonym. The users want to see both Customer and Customer Synonym and also query sales. When I add the Customer Synonym table within the same logical table source and run a query,the Sales numbers are doubled counted where there are more than one Synonyms. To avoid confusion we have trained users about this issue. However, I would like to figure out a better way to avoid the double counting. I cannot create a dimension out of Customer Synonym because the grain of the sales data is customer.
Is there a better design pattern within OBIEE to address this issue ?
Any suggestions would be appreciated.

Ya got your requirement,I got an idea or think its a suggestion lets give a try
If you know SQL coding and as you said they are alternative names,you can do 1 thing instead of displaying both names as different columns.You combine them in SQL it is concatenated like this
customer_name||' '||customer_synonym so result=AB Corporation Alpha Beta Corporation Barclay Corporation
so end result AB Corporation Alpha Beta Corporation Barclay Corporation 100
but this can be written in the query itself or may be as a condition you should give a try and play around.
Hope it helps you.
Cheers,
Kranthi

M:N relationships within a dimension: Standard process vs. BI Data model

Hi,
I just completed a review of the u201CMulti-Dimensional Modeling with BIu201D from this link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84 and I have a quick question here:
On page 36 of this link, the author noted that
u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
i.e. my understanding is that, based on Standard Process it is NOT possible to place two characteristics in M:N relationships in the SAME dimension but with BI Data Model, this, the author points out is possible
u201Cdue to the usage of surrogate keys (DIM-IDs) in the dimension tables allowing the same material several times in the dimension tableu201D i.e. although material is the unique key of the dimension.
1.
What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
2.
It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
3.
Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
u201CIf you can avoid compounding - do it!
Compound attributes always mean there is an overhead with respect to:
Reporting - you will always have to qualify the compound attributes within a query
Performance
Compounding always implies a heritage of source systems and just because it makes sense within the
source systems does not necessarily mean that it will also make sense in data warehousing.u201D
Thanks

Hi Amanda.......
In a dimension table, any number of semantically related dimension attributes are stored in a hierarchy (parent-child relationship as a 1:N relationship). If an M:N relationship exists between dimension attributes, they are normally stored in different dimension tables.
I checked the document.........
On page 36 of this link, the author noted that
u201CAccording to the standard process, color should be in the master data table for material, like material type. But this is not possible because the material is the unique key of the master data table. We cannot have one material with multiple colors in the master data table.u201D
1.
What is being referred here as u201CStandard Processu201D since document is on u201C u2026 modeling with BIu201D?
Here the first thing that I want to tell u is that............the diagram shown here is Classic Start Schema............since Extended Star Schema will never store Master data in Dimension tables.........it stores Masterdata in seperate Master data tables..........and nowadays..............Classic Star schema is obsolet.......Dimension table will only store Dimension id and SID......
Now the Standard process is that..........anything which is Describing a master data..........can be added as an Attribute of that master data.......
Suppose........Employee is the Masterdata.then Ph no can be one of the Attribute of this master data......
So this the Standard Process.........but this cannot be followed every time.........why........already explained.....
2.
It goes on to discuss u201CDesigning M:N relationships using a compound attributeu201C as a solution to the M:N relationship in a dimension.
What is the need to address this problem with compound attributes if characteristics in M:N relationships within a dimension, such as material and color, are not a problem in BI Data Model?
Bcoz ..........we use compounding Characteris tic to define the Master data uniquely.........and we load compounding Characteristic seoerately...which is independent of the Master data........ie......compounding Characteristic there is a seperate master data tables...........so ..........problem resolved......
3.
Can you help explain the underlined cautions of the following guidelines for compound attributes (with examples if possible please):
u201CIf you can avoid compounding - do it!
Compound attributes always mean there is an overhead with respect to:
Reporting - you will always have to qualify the compound attributes within a query
Performance
Compounding always implies a heritage of source systems and just because it makes sense within the
source systems does not necessarily mean that it will also make sense in data warehousing.u201D
For Compounding Characteristic............u hav to laod the Coumpoundede master data seperately..which is a overhead...........moreover while query execution......two tables will be accessd..which may result a performance issue.......Performance can be affected when compounded characteristics are used extensively, particularly when a large number of characteristics are included in a compounding. In most cases, the need to compound is discovered during data modeling.
Regards,
Debjani.........

Database connection(select ,insert query) within javascript function

Hi ,
How to write the database connection(insert,delete or select query) within javascript function.Is it possible.Anyone can you help me
than you

Hi ,
How to write the database connection(insert,delete
ete or select query) within javascript function.Is it
possible.No

Hierarchies within a Dimension

Hello,
The BW Multidimensial modeling states there are 3 types of Hierarchies that BW employs.
Can anyone shed light on what " Hierarchies within a Dimension" does?
Thanks in advance.

Hi
Any dimension's members may be organized based on parent-child relationships, typically where a parent member represents the consolidation of the members which are its children.
The result is a hierarchy, and the parent/child relationships are hierarchical relationships. For example, the Time dimension would contain the following hierarchy
Day Week Month Quarter Year.
Based on the business queries, such hierarchies would be formed in all dimensions.
Regards
Sai

Physical query generation: unneeded dimension tables get joined to the fact

Hi there!
The setup is the following:
There is a logical fact table which is joined to 7 logical dimensions, it has 4 table sources which correspond to different time dimension levels (all other dimensions are mapped to Detail level).
Time dimension logical table also has 4 different table sources (for days, months, quarters, and years).
The data source is an Oracle Database 11gR2.
The problem is:
No matter what the logical query is, in the physical query all 7 joins are performed, even if the resulting data is then simply discarded. This results in very bad query performance.
I feel that it is somehow related to the level-based fragmentation (since, for instance, inclusion of time dimension columns in SELECT list (not in WHERE) seems to affect physical queries), but lack sufficient knowledge to solve this problem or put up with it.
My questions are the following:
1) Have you ever encountered such a situation?
2) Can unneeded joins be eliminated?
2.1) If yes, how?
2.2) If not, then why are they needed?
Thanks in advance!

Physical level:
D01-D06 - ordinary physical tables.
D_DATES - all time levels from dates to years, D_MONTHS - time levels from months to years, also D_QUARTERS and D_YEARS.
F_DAILY - fact table joined to all of the D01-D06 and to D_DATES, F_MONTHLY - joined to D01-D06 and D_MONTHS, also F_QUARTERLY and F_YEARLY. All measure columns are the same.
Logical level:
D01-D06 correspond to ordinary logical tables with a single table source. Logical dimensions are created.
D_TIME is a logical time dimension with four levels (dates, months, quarters, and years) and four table sources ( D_DATES, D_MONTHS, D_QUARTERS, and D_YEARS ).
F is a fact table with four logical table sources ( F_DAILY, F_MONTHLY, F_QUARTERLY, and F_YEARLY ) with aggregation content levels set correspondingly.
OBIEE correctly picks physical table sources for different time levels, but generates extremely inefficient SQL (joining all dimension sources in a WITH-subquery, doing ROW_NUMBER over a result set, and then discarding half the columns, which were not needed to start with).

Help with doing SELECT sub query within the SET of an UPDATE statement

After doing some research, it appears as if it's possible to use a SELECT subquery in the SET of an UPDATE statement. i did find some examples and here is my code, however when I click the "check" button it's saying the field (my entire select subquery) is unknown and neither in one of the specified tables or defined by a "DATA". Do I have a syntax issue or is there another reason why it's not taking this as a valid statement? Thanks for the help!
LOOP AT IT_DATA
UPDATE /BIC/AZDP_O0140
   SET /BIC/ZCOUNTER = (SELECT COUNT( DISTINCT MATERIAL )
                        FROM /BIC/AZDP_O0140
                        WHERE MATERIAL EQ IT_DATA-MATERIAL
                        GROUP BY MATERIAL).
ENDLOOP.

my Update does indeed have a WHERE clause but because of the issue i'm having, all my criteria in my WHERE is black text in the ABAP editor. The editor doesn't even recognize the keywords "WHERE" or "EQ". Below is my entire statement which contains all WHERE criteria in both the Update and the Subquery, i've just removed it for testing to help simplify the query and eliminate as many other factors as posisble that may be causing problems:
LOOP AT IT_DATA.
   UPDATE /BIC/AZDP_O0140
   SET /BIC/ZCOUNTER = (SELECT COUNT( DISTINCT MATERIAL ) FROM /BIC/AZDP_O0140
   WHERE WHSE_NUM EQ IT_DATA-WAREHOUSE
    AND PLANT EQ IT_DATA-PLANT
    AND /BIC/ZTRAN_NO EQ IT_DATA-TRANS_NUM
    AND DELIV_NUMB EQ IT_DATA-DELIVERY
    AND MATERIAL EQ IT_DATA-MATERIAL
    GROUP BY MATERIAL)
   WHERE WHSE_NUM EQ IT_DATA-WAREHOUSE
    AND PLANT EQ IT_DATA-PLANT
    AND /BIC/ZTRAN_NO EQ IT_DATA-TRANS_NUM
    AND DELIV_NUMB EQ IT_DATA-DELIVERY
    AND MATERIAL EQ IT_DATA-MATERIAL.
ENDLOOP.
i should also mention the sources i found were not within the SAP Library but instead on other third-party ABAP websites. so because i was having issues i wanted to post here to see if anyone else has come up with a working solution. but if this cannot be done i can likely come up with a solution for my needs using multiple internal tables, this would just have been much easier since i can get a query like this to do what i want in SQL Server. Thought i could utilize this in ABAP as well.

Query within the Cursor loop is very slow

Hi ,
I have a stored procedure which has Select/Insert operation which is looped within the cursor. The Select uses variables from the cursor, and inserts the data into the table.
My problem is the peformance. The stored procedure executes in 2 mins if I hard code the where clause values in the Select. Instead if I use the variables obtained from the cursor, the query takes so long (more than 20 mins) to insert the same no of records into the table.
Below is the snippet of my code
create procedure sample is
declare
v_acct_month number(2);
v_sp_name varchar2(30);
cursor v_cur is Select distinct Acct_Month,salesperson_name from period;
begin
open v_cur;
loop
fetch v_cur into v_acct_month, v_sp_name;
exit when v_cur%notfound;
Insert into T1
Select * from T2,T3.. Where T2.month=v_acct_month,t3.sp_name=v_sp_name;
end loop;
End;
The query is not using the optimizer when the variables are used.The optimizer is used when I hard code the values in the select.
Please give me suggestions to make this query faster..
Thanks,
Arun
Edited by: [email protected] on Mar 28, 2009 10:18 AM

Hi,
Whenever you write code, format it to show the scope of BEGIN, LOOP, IF statements, and so on.
Type these 6 characters
{code}
(small letters only, inside curly brackets) before and after the formatted code, to preserve spacing on this site.
You've discovered why the tecnique you're using is called "slow-by-slow" processing.
You don't need a cursor. You may not even need PL/SQL.
Just write an INSERT statement that reference the table from the cursor and the tables from your current INSERT statement.
Here's one way:
INSERT
INTO     t1 (columns)
SELECT         columns
FROM     t2
,     t3
WHERE     ...
AND     (t2.month, t3.sp_name)     IN (
                          SELECT DISTINCT
                               acct_month
                       ,        salesperson_name
                       FROM        period
                       );Depending on the details of your case, there may be a better way, such as a 3-way join.

Querying Levels in Dimensions joined to the Facts

I created a location dimension using the standard levels, i.e., region > subregion > country > state > location_id. I then attached it to a sales fact that had the location_id as the key, but when I tried to query the cube by it's levels the only level I see is the location_id level which is at the state. None of the other levels appear or are queryable when I do something like:
SELECT * FROM vw_SALES_CUBE A, vw_LOCATION_DIM B
WHERE A.LOCATION_DIM = B.DIM_KEY
AND A.LEVEL = 'COUNTRY'
Only one level comes up although in the location_dim all the other levels exist the join does not carry them over. The data for the levels appears in the COUNTRY_LONG_DESCRIP column and not in the LEVEL column.
What am I doing wrong. Are there other objects I need to create like an MV.
jrod

I was thinking that is if I created a cube such as the one described in the thread and that I did a query along the LEVEL_NAME that the cube would fetch the data without the need for me to create say MV's aggregateing the data. For example,
/* The following is a basic query against a fact table */
SELECT T.CALENDAR_YEAR_DSC TIME, SUM(F.SALES) SALES
FROM TIME_DIM T, UNITS_FACT F
WHERE T.CALENDAR_YEAR_DSC IN ('2005', '2006')
AND T.MONTH_ID = F.MONTH_ID
GROUP BY T.CALENDAR_YEAR_DSC;
/* The next query fetches the exact same results from a cube using filters: */
SELECT T.LONG_DESCRIPTION TIME, F.SALES SALES
FROM TIME_CALENDAR_VIEW T,
PRODUCT_PRIMARY_VIEW P,
CUSTOMER_SHIPMENTS_VIEW CU,
CHANNEL_PRIMARY_VIEW CH,
UNITS_CUBE_VIEW F
/* Apply filters to every dimension */
WHERE T.LONG_DESCRIPTION IN ('2005', '2006')
AND P.LEVEL_NAME = 'TOTAL'
AND CU.LEVEL_NAME = 'TOTAL'
AND CH.LEVEL_NAME = 'TOTAL'
/* Join dimension views to cube view */
AND T.DIM_KEY = F.TIME
AND P.DIM_KEY = F.PRODUCT
AND CU.DIM_KEY = F.CUSTOMER
AND CH.DIM_KEY = F.CHANNEL
ORDER BY TIME;
In these two queries I fetch the same grain. So why is it that the cube has not precomputed these factors. What do I need to do this?

Alternative for result from other query and merge dimension option option

Hi Everyone ,
Am Developing one webi report over bex Query.
Actual scenario is output of one webi report should be the input of other webi report.
Eg:
Table 1
2010        Cus 1
2010        Cus 2
2011        Cus 3
table 2
cus1    m1   100
cus2    m2   200
Cus3    m1 400
Report 1 designing
First report created using table 1 and prompt for year
Report 2 designing
Second report created using table2 and prompt for customer
So when am Running first report it will ask for parameter year and if am selecting 2010 then the report will return C1 and C2
this out put should e the input for report 2.
So out put will be 100+200=300
NOTE:1. Result from other query is not working in webi filter pane since am building on olap universe.
           2. Merge Dimension performance is very slow .
Any Solution ?
Regards,
Kannan.B

Hi,
Thanks for ur reply
As you said , If am giving hyperlink to other report .
Eg: User selected Tamilnadu then report 1 opened then he has to click the some cell or hyperlink cell to view the actual report(2nd report).
Suppose user Clicked that hyperlink cell and 2nd report opened and he is viewing the data for Tamil nadu and he decided to see the report for
Andrapradesh so according to this logic he has to select first report and refresh the data for Andra and from there he has to come to 2nd report.
totally 4 screen will be opened for seeing the two states report.
So Some other alternative.......

[Excel Source].[Measure 1] where [Excel Source].[Dimension 1] in [SQL Query 1].[Dimension]?

Is this possible in WEBI XI ?
If not is there a way to get pass the issue?

Hi Anthony ,
This is doable .We may need to have 2 universes ,1 for Excel source and other for SQL server.
Then apply Dimension in SQL universe as a prompt .
Drag Dimension in Excel universe to Query filters pane .
From Type of filters drop down select "Result From another Query" . Select The Dimension object of SQL Universe.

Prevent Excel from recalculating when refreshing a query within a workbook

Hello,
I have a BEx workbook with 4 queries and a significant number of Excel formulas retrieving and rearranging query data.
**The issue**:
When Excel>Tool>Options>Calculation is set to "Automatic" (as it should be in normal situations), refreshing anyone query takes about 2 hours.
When Excel>Tool>Options>Calculation is set to "Manual", refreshing anyone query takes about 2 minutes.
Therefore I conclude that BEx does not prevent Excel from recalculating during a query refresh and this cause unacceptable delays.
**Question**
Is there any way to prevent to temporarily prevent Excel from recalculating during a query refresh ?
Thank you.
Louis

I have a star schema, ie 5 FACT tables and 7 dimension tables, All fact tables share the same dimension tables, some FACT tables share 3 dimesnsions, while other share 5 dimensions.
I did adopt the best practices, and as recommended in the book, I tried to resolve them using Context, as it is the recommended option to Alias in a star schema setting. The contexts are resolved, but I still have loops. I also cleared the Multiple SQL Statement for each context option, but no luck. I need to get this resoved ASAP,
I checked all the context and they look fine, however when I again go to detect context it asks me to add the context which is already present. It give me an option to overwrite? Besides, I also get some Alias options. However I was told and it was mentioned in the book that Alias is not a good option to resolve loops but context is when you have a STAR SCHEMA.
Please suggest idea.
AP

Representing a calculation schema within a dimension hierarchy

Hi,
I want to build a reporting hierarchy in SSAS to have it readily available for reporting.
The real hierarchy look like:
http://i59.tinypic.com/2irl0k1.png
However I want it to be like the following:
http://i57.tinypic.com/2v93rl2.png
I have tried to do this with the following statement in the cube design:
Scope([DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB1]);
This = [DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB1]
+ [DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[TURNOVER];
End Scope;
Scope([DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB2]);
This = [DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB2]
+ [DIM Contribution Margin].[Hierarchy].[CM1 KEY].&[DB1];
End Scope;
However, this has an effect on the other dimensions. When I now put just the products on one axis the result is messed up.
How can this be done?
Many thanks in adavance.
Calculated Member are not a solution, because to my knowledge they cannot be placed freely in the hierarchy.

Hi Felix,
It looks like the simple hierarchy you are querying should have been conceived as a ragged hierarchy instead. This is remarkable because the labels have also a financial nature.
Instead of struggling with scope statements, is it an option to build that hierachy like those find in a financial cube?:
http://martinmason.wordpress.com/2012/02/26/the-ssas-financial-cubepart-1ragged-hierarchies/
Philip,

Broadcast query within email

Hello,
Is it possible to broadcast query results "within" an email. Currently we are sending attachments but i would like to send the results within the body of the email. I've tested all the different settings but dont see what i am looking for. Broadcasting an online link does not fit our requirement, we are sending a snapshot in time not current data.
Regards,
TMS

Hi,
In BEx broadcaster create a setting that has:
Distribution Type: "Send as E-Mail"
Output Format: "Independent HTML File"
leave As Zip File unchecked.
For me, this sends the web template I choose in the body of the email.
Also, you may need to add the email address that you are sending the emails from as a trusted site in your email list. This may allow the email program (we use Outlook) to apply the CSS from the templates to the table in the email and it will look exactly like what you would see in your web portal.
Cheers,
Rusty

My first PL/SQL block not working with using Select query within begin

I am new to PL/SQL , just started with basics of BLOCKS .
I am having a query here in executing a block .
When i am doing a insert oprtation in Blocks Begin method everything is working fine , but when ever i tried to do select operation , some error is being thrown .
First of all This is my Table :
select from try :*
KEY      VALUE
Key     Value
Key1     Value1
Key2     Value2
Key3     Value3
======================
This is the code which is not working : Please see the code and tell me what is the problem .
DECLARE
v_KEY    VARCHAR2(20);
v_VALUE   VARCHAR2(20);
BEGIN
select key into v_KEY FROM try where v_value='Value' ;
dbms_output.put_line(v_KEY);
END;
When i run this code , it is saying Data Not Found on this line " select key into v_KEY FROM try where v_value='Value' ;"
wheer when i run tis individually it worked fine :
select KEY FROM try where VALUE='Value' ;"
please share your ideas .as why it isn't running ??
Edited by: user10503747 on Sep 20, 2010 3:16 AM

Hi,
user10503747 wrote:
I am new to PL/SQL , just started with basics of BLOCKS .
I am having a query here in executing a block .
When i am doing a insert oprtation in Blocks Begin method everything is working fine , but when ever i tried to do select operation , some error is being thrown .
First of all This is my Table :
select from try :*
KEY      VALUE
Key     Value
Key1     Value1
Key2     Value2
Key3     Value3
======================
This is the code which is not working : Please see the code and tell me what is the problem .
DECLARE
v_KEY    VARCHAR2(20);
v_VALUE   VARCHAR2(20);
BEGIN
select key into v_KEY FROM try where v_value='Value' ;
dbms_output.put_line(v_KEY);
END;
When i run this code , it is saying Data Not Found on this line " select key into v_KEY FROM try where v_value='Value' ;"
wheer when i run tis individually it worked fine :
select KEY FROM try where VALUE='Value' ;"
please share your ideas .as why it isn't running ??
Edited by: user10503747 on Sep 20, 2010 3:16 AMInstead of:
{code}
select key into v_KEY FROM try where v_value='Value' ;
{code}
perhaps you meant something like:
{code}
v_value := 'Value1';
select key into v_KEY FROM try where v_value=Value ; -- No quotes
{code}
Until you assign a vlue to a variable, like v_value, it is NULL, so your original statement was equivalent to
{code}
select KEY FROM try where NULL='Value' ;
{code}
In PL/SQL, a SELECT ... INTO statement must return exactly one row, or else you will get an error (either NO_DATA_FOUND or TOO_MANY_ROWS). This is different from SQL, where a query cn return any number of rows, including 0, without raising an error.

Querying within a dimension

Similar Messages

Maybe you are looking for