Alias table

Hi All,
I have a situation where I have four tables having one to many database relationship.
There is no defined fact or dimension table.
X(1)-->A(N)
A(1)-->B(N)
B(1)-->C(N)
Can we create an alias for A and B to act as confirmed dimensions so we can pull all the
records from all the tables without any errors? I apologize for any confusion.
Thanks,
Virat

Hi,
No need for aliases, your describing one branch of a snowflake, simply flatten the snowflake (in your Physical model) to a star-schema in your BMM model (add the tables together in one or multiple Logical table sources).
Phy Layer :
X -> A -> B -> C
BMM Layer :
Logical Fact (X?) -> Logical Dim (A,B,C)
Regards
Alastair

Similar Messages

Alias Table in SQL

Hello ..
i want to join an alias Table in an SQL statment something like
Invoices_Table
-Inv_ID
-Amount
-Delevery_Country_id
-Bill_Country_id
Country_Table
-Country_id
-Country_name
I want to join Country_ID once for deleivery Country and then for Bill_Country. Which are not necessarly the same ..
How can i express it in SQL ..?
Thanx

Try
API> CREATE TABLE Invoices_Table
2 (Inv_ID VARCHAR2(100),
3 Amount VARCHAR2(100),
4 Delevery_Country_id VARCHAR2(100),
5 Bill_Country_id VARCHAR2(100));
Tabla creada.
Transcurrido: 00:00:00.34
API>
API> CREATE TABLE Country_Table(
2 Country_id VARCHAR2(100),
3 Country_name VARCHAR2(100));
Tabla creada.
Transcurrido: 00:00:00.04
API>
API> INSERT INTO Invoices_Table VALUES('A','A','1','2');
1 fila creada.
Transcurrido: 00:00:00.04
API> INSERT INTO Country_Table VALUES('1','Country1');
1 fila creada.
Transcurrido: 00:00:00.03
API> INSERT INTO Country_Table VALUES('2','Country2');
1 fila creada.
Transcurrido: 00:00:00.03
API> COMMIT;
Validación terminada.
Transcurrido: 00:00:00.03
API> SELECT I.Inv_ID,
2    C1.Country_name AS NAME1,
3    C2.Country_name AS NAME1
4 FROM Invoices_Table I, Country_Table C1, Country_Table C2
5 WHERE I.Delevery_Country_id = C1.Country_id (+)
6    AND I.Bill_Country_id = C2.Country_id (+);
INV_ID
NAME1
NAME1
A
Country1
Country2
Transcurrido: 00:00:00.07

How to use non-default Alias Table in Analyzer report

Hi,I defined many alias tables in Essbase. I would like to use a different alias table other than the "default" in Analyzer 6.5 report. In the on-line help, it said I can modify in "database connection properties" when first defining a new report to use a specific alias table. It tells me to do the following: Click the "New" toolbar button. Select a Display Type or Layout, and click OK. Right-click a database connection name in the "Select Database Connections" dialog box, and select Modify from the right-click menu.So I did this, but as I did the last-right click, there is no "Modify" option available. Only has "Add New..", "Database Connection Properties.." However, if I defined a new personal database connection using the login user, I can select to use other alias table. But this will go to personal database connection properties.Is it possible to specifically tell Analyzer to use other alias the global level in database connection? What I use to do is to have certain reports to use the default alias, and another to use another alias table. These reports should be able to share across all users.Sam

In deed it is fix in the GA.Another way to set the alias table is to do it in the Admin client. If you add a connexion to a user there is a new 6.5 button "set alias" that allow you to set the default alias table for this specific user. But, it does not exit on a user group level.

SAP Query Alias Table in Info-set not working

Hi Guys,
I'm having a bit of trouble with a query I'm writing in SQ01.
I am trying to create a standard margin report between two different costing variants that we use.
n order to do so I have had to employ the use of alias tables.
I have named the alias tables KEKO_2 and KEPH_2 accordingly and joined them in the info set with the same joins as the original tables (Left Outer to MARC on MATNR and WERKS)
However, when I have come to test the query in SQ01 I get a runtime error which states the following:
The following syntax error was found in the program
AQA0MASTER_DATA=STANDARDMARGIN :
"Field "KEPH_2-KST001" is unknown. It is neither in one of the specified
tables nor defined by a "DATA" statement . . . . . . . . . ."
But it is in a specified table! My alias table.
How can I make this query work?
Any help would be appreciated.
Thanks in advance.

Hi,
This is SAP business one reporting and printing forum. Please find correct forum and repost your question to get quick assistance.
Please close this thread by marking helpful answer.
Thanks & Regards,
Nagarajan

Changing the LTS mapping in BMM layer to new Physical Alias table

Experts
I need to change the source table mapping in my BMM layer to new physical tables aliases.
I have finished BMM layer design (column name changes, business friendly names etc.) before actually creating the alias tables in the Physical layer and I know I hv to run for hiding now. I expected changing the logical source mapping to the new aliases will work but it's not the case though it works partially. Since the Column names are changed in the bmm, I have to manually change the Expression, Physical Table in the LTS column mapping tab for each non-matching name logical columns.
Column mapping is intact where both the BMM columns and the new Physical alias names match.
eg: CALENDER_YEAR(BMM) ---> CALENDAR_YEAR(Physical alias) mapping is intact but
Week Day(BMM) ---> WEEK_DAY(Physical alias) need to be changed manually.
Any tips/suggestions will be appreciated.
Regards,
Tom

Hi Tom,
I too do not see any other options here other than manually modifying the individual logical columns. When there is a new logical column, we have to map it manually to the physical column explicitly because the Admin tool will not know which physical column to pick up.
Hope this helps.
Thank you,
Dhar

Alias table update errors

Hi,
I am trying to update an alias table using rules file. I am trying to update members of multiple dimensions in one single rules file. the column structure is as below:
(Dim1, Lev 0) (Alias) (Dim2, Lev 0) (Alias) (Dim3, Lev 0) (Alias)
But the above rules file is failing at column 3. It says "\\column 3 validation failure". Can you please help?
Thanks!

Hi,
Have you read this post? Alias Update
I know it was you that raised it but did it not answer the question?
LEVEL0,Dim1 ALIAS0,Dim1 LEVEL0,Dim2 ALIAS0,Dim2 LEVEL0,Dim3 ALIAS0,Dim3
should validate if each of the dimensions is set up as a level build type
You can quickly test it by creating a file with say the following.
dim1val,dim1alias,dim2val,dim2alias,dim3val,dim3alias
Create a new load rule.
Set it to dimension build.
Open the text file
Set the properties for each column as
LEVEL0,Dim1 ALIAS0,Dim1 LEVEL0,Dim2 ALIAS0,Dim2 LEVEL0,Dim3 ALIAS0,Dim3
set the dimension build properties for dim1,dim2,dim3 as level build type.
validate
Cheers
John
http://john-goodwin.blogspot.com/

How to copy a physical Alias table from one rpd to another

Hi
I am copy pasting the physical tables from one rpd to another. I first copied the physical table and then tried to copy the alias table i get the message ' Unknown Error' when i click ok it says
'Failed to copy from clip board"

Identify the "class=MyStyle" string in the MTML code, and use the Multi-File Find and Replace feature to step through each topic and change the specific instances to "class=MyOtherStyle." (I doubt that you'll want to "Replace All".)
Sorry, there's no silver bullet!
Good luck,
Leon

Resolve self-reference table by alias tables in detail

Hello Gurus,
can you tell me how to resolve self-reference table by alias tables in detail?
Many thanks.

Hello, for the following step 3, I don't understand, will you please give me some explanation for step 3?
Save your Staff universe, and test the results in Web Intelligence Rich Client as follows:
1. Run a query using Manager and Employee. Add a count on both columns.
2. Add a query with only the Manager object. Add a count. Is this the correct value?
3. Open your Staff universe in Universe Designer and edit the Manager object. To ensure
that the data is restricted to only manager data, use the Tables button. Select the
EMPLOYEE table, to force the object to use the join between the table and restrict the
data.
4. Test the result, creating a new query with only the Manager object. It returns the correct
number of managers.
5. Edit the query and add Employee. Run and display the count. There are 26 rows. Why?
The join restricts the data to look only for employees that have managers. However, there
is a manager that does not have a manager, and is now excluded.
6. Open your Staff universe in Universe Designer and add an outer join on the MANAGER
table side.
7. Save the changes and test the results in Web Intelligence Rich Client.

About alias tables

What is the use of alias table in physical layer what is the use of it
if i am not using alias tables so what is the impact???
i heard that alias table is use full for avoiding circular joins and self joins
can you make me little bit clear on it
Thanks
sreedhar

I dont know whether it will improve performance but aliases are basically used when you want to do self join .One good example is to calculate second maximum salary .In that case you will make aliases of one table twice.In obiee alaises are basically used when you want to join same table with same fact twice .For example one fact can join to time dimesnion twice with diffrent join condition .
In that case you need to create alias of original table .If you join the same table with fact twice then OBIEE will throw an error that circular joins are not allowed,This is an example of circular join.
Regards,
Sandeep

Multiple Alias tables in FR

I have a report where I am using MemberAlias in my title. I have 2 alias tables and want the report to work with the second Alias table. I have set the report in the grid with alias table2 in the properties.
Unfortunately MemberAlias keeps picking up Alias table 1. Any thoughts on where I set this correctly to take the correct alias table?
Thanks in advance

That's what I am doing (based on your syntax).
I am referring to the Grid1. But really its the POV that the memberalias is refering to. so Memberalias (Grid1, CostCenter) is what I have in my title - Where CostCenter is a POV for Grid1 . It just refers to the wrong alias table. It gives me alias table1 even though the grid1 is refering to alias table2

Refresh using alias table not returning expected results

I am getting some unexpected results in SmartView and can't figure out the cause. I have an Essbase cube that has two alias tables: the "default" and one that I call "Short Descr". I can consistently bring back data using "none" and "default", but not "Short Descr". When I use "Short Descr" data will come back for some of the members, but not for others.
Here is an example of a query using "none" as the alias table:
     Net Income
     RD10078
     Y-T-D(MAR)
PRJG939306      20,372.05
PRJLG921508      (26.42)
Project      (1,179,752.36)
If I change the alias table to "Short Descr", I get the following results:
     Net Income
     ITA (RD10078)
     Y-T-D(MAR)
PRJG939306 (PRJG939306)      20,372.05
PRJLG921508 (PRJLG921508)      (26.42)
Project      (1,179,752.36)
But then if I just clear the amounts, and do a refresh, I get the following:
     Net Income
     ITA (RD10078)
     Y-T-D(MAR)
PRJG939306 (PRJG939306)
PRJLG921508 (PRJLG921508)      (26.42)
Project      (1,179,752.36)
And if I pivot Net Income, I get a message that "Any comments/ functions/ formulas on the sheet will be lost.", and the PRJG939306 member is lost.
          ITA (RD10078)
          Y-T-D(MAR)
Net Income      PRJLG921508 (PRJLG921508)      (26.42)
Net Income      Project      (1,179,752.36)
I can't figure out why it would start treating it as a comment. It looks to be a valid member name and I don't see anything strange if I look at the member properties in EAS. And what I really don't understand is why it would bring back the member name (with alias) and a data value when I change the alias table from "none" to "Short Descr", but not bring back a value when I just clear the amounts and do a Refresh. And why is it only doing it for some of the members and not all of them?
What could cause this type of behavior?

lets see if I can say this clearly. Smartview will noit convert from one alias to another. Before switching alias tables, try changing back to no alias and do a retrieve, then switch to the new alias table and retrieve. I think the problem is Smartview is not interpeting what is on the one line so it leave it blank as an unknown member.

Duplicate table and Alias table in the physical layer

Hi,
I want a clear information regarding the duplicate tables in the physical layer of the rpd.
I mean what is the purpose of the duplicate tables in the physical layer.........
thanks,
chinna.

what do you mean by duplicate of physical table? is it Alias table?
if then,
-> aliases are created to break the circular joins (which are not supported by obiee)
-> and, as per apps standards no operation can be done on base tables which are imported directly to physical layer. Only aliases are joined and will be used in BMM layer
-> useful to re-use the table more than one time , best example: W_DAY_D in apps rpd
Edited by: Kishore Guggilla on Sep 23, 2010 10:41 PM

Alias Tables and Duplicate tables in Physical Layer

Hi all,
I have a small doubt in physical layer. We have two options when we right click table, 'Alias' and 'Duplicate'. To create another instance of a table, can we use any one of these. Does it make any difference
Thanks & Regards,
Jagi

Hi,
If u duplicate any table the join conditions will carry with respective tables , same name appending (TableName#1)
In case of alias u need to specify joins conditions explicitly
We can use same table with different constrains to the same table
Aliases used, if you need to replicate a physical table and not create multiple tables with the same data
If you delete any column in the Original table automatically deleted in alias
table and Its not reflected in Duplicate table.
Steps:
Right Click the original table. Choose New Object and choose Alias.
The mistake most people make is try to bring in the same table again and rename it or choose Duplicate by right clicking the original table.
Thanks,
Balaa...

Implicit fact and Alias table with

Hi Gurus,
May i know what is the use of alias table and implicit fact with some real time scenarios for better under standing.
Thanks,
Rafi

For alias tables, refer to the oracle's documentation here which is explained in great detail: ( http://docs.oracle.com/cd/E14571_01/bi.1111/e10540/physicallayer.htm )
For implicit fact refer to the oracle's documentation here: ( http://oracle-bi.siebelunleashed.com/articles/implicit-fact-column/ ) . To define in layman's terms, implicit fact is set on a subject area when you are reporting out of dimensions in the report without any fact columns and you want the fact table to be part of the report's query.

Have error when change alias table in Grid of Financial Reporting Studio

Hi all,
I process in my working Grid. It start with Alias: English. Now i want change alias from English to Default. But when i change alias, it has error.
Detail of error:
Runtime error '-2147467259 (80004005):
;nested exception is:
java.lang.NullPointerException
Please help me.
Thanks

Thanks for your help.
I have found it. One of four (POV, Pages, Column, Row) has no dimenson. So when i change the alias table, this error appear.

Confuse about Alias table

Hi,
In the samplesale RPD, I saw a lot of alias tables and I check the mapping in physical layer, there is no mapping between source table of alias table and F, just have mapping between alias table and F, so what I want to know is what's the purpose of this kind of table? why alias it, why not use source table?
Regards,
anne

Hi Anne,
There will not be any physical join between the source dim and its alias.If you double click on an alias table in physical layer, you can see the source table from which this alias is created.The main purpose of an alias table is to avoid circular join.
For Example: Assume you have a fact table with various date foreign keys like registration_date_fkey,resignation_date_fkey etc. In this case you ll have to join a date dimension's primary to these two foreign keys in the fact.You cannot use the same date dimension twice to achieve this, in this scenario create aliases for date dim ,name them as w_day_d_registration and w_day_d_resignation and join them to the respective foreign keys.
Rgds,
Dpka

Alias table

Similar Messages

Maybe you are looking for