Creating an alias table

Hi all. I have a situation where I need to create an alias copy of a table and then pull information from both the original and the alian (the database creators built the table to hold different description, amount, and date info in the same fields when triggered by another field. Lovely)
Can I do this in Crystal?

I believe you can just add the same table twice to your report, and specify how they should be joined.  I believe Crystal will put a "2" (or some such) at the end of the second table's name for reference purposes in the report.
Or, do what I usually do, and base your report off of an SQL command, something like this (MS SQL):
select orig.order_no, ref.order_no
from orders orig, orders ref
where orig.ref_order_no = ref.order_no
I rarely use tables directly, as reports tend to run faster when based on an SQL command that just returns the required data (as opposed to whole copies of perhaps several very large tables), so I could be wrong on the first suggestion...
HTH,
Carl

Similar Messages

  • 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

  • Re:Alias Table

    Hi I am new to obiee, I have a doubt regarding alias tables in obiee..
    I had a fact and dimension(Party), I created three alias tables for party and joines
    Fact.Primary Borrowerid=Party.partyid
    Fact.SecondaryBorrowerid=party.partyid
    Fact.Primary officer id=party.partyid in the physical layer
    so when it comes to BMM Layer do i need to make one party table and drag the two alias (party tables) into the party table or else is there any other procedure?

    If you need any Party attributes interms something like
    Primary Borrower
    Secondary Borrower
    Primary officer
    then you need to have logical table for each.
    If helps mark

  • Alias table - join problem

    Hi,
    I am having time Dim for that I have created two alias tables DIM_TIME (STA) and DIM_TIME (STD).
    Both were joined with STA_ID and STD_ID of DIM_Product.
    When I am trying to fetch Dim_Time Time_Id with STA_ID from Dim_Product instead of selecting from DIM_TIME (STA) it's selecting from
    DIM_TIME (STD).
    Please see the executed query.
    select distinct T7901.TIME_ID as c1,
    T6838.STA_ID as c2
    from
    DIM_TIME T7901 /* DIM_TIME (STD) */ ,
    DIM_PRODUCT T6838
    where ( T6838.STD_ID = T7901.TIME_ID )
    order by c1, c2
    How to get the desired result?
    Thanks,
    Vino

    Hi,
    Thanks for the reply,
    In BMM I used the Alias tables as LTS for DIM_Time. And Join DIM_Time with DIM_Product.
    So it was not able to do the join.
    Currently I have created separate DIM for the aliases in BMM layer and joined it with DIM_Product, now the joins are
    working fine.
    Thanks,
    Vino

  • 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

  • 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

  • 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 create an alias to a subtype?

    Hi,
    How can I create an alias to a subtype?
    I.e. How can I asscciate a name with a subtype?
    Associate DOM_ADDRES with the type CHAR(50) or
    associate DOM_TELNO with the type NUMBER(10,0)
    so I can use it in the creation of a table like
    CREATE TABLE T1 (id INTEGER, addr DOM_ADDRES , tel DOM_TELNO);
    I tried CREATE DOMAIN statement -> Not working, statement not
    exists.
    I tried SUBTYPE lll IS CHAR(3) but it only works in PL/SQL
    programming, I can't create tables with that.
    Is it possible? Am I doing something wrong?
    I think subtyping and aliasing is very useful for readability and
    reuse.
    I don't want to use CREATE TYPE AS OBJECT, I do not need objects
    in my DB.
    I am using Oracle 8.1.7 for Linux.
    TIA,
    Jose P.

    In my .profile this works: alias f="/Applications/Firefox.app/Contents/MacOS/firefox -P doug"
    for starting under my profile. Make sure you run source ~/.profile if you add an alias to .profile
    Starting default FFox profile is /Applications/Firefox.app/Contents/MacOS/firefox -P swxazqvy.default
    And for Desktop icon to start whichever profile, open Script Editor and paste with proper changes(and save as an app(maybe to Desktop again?) :
    do shell script "/Applications/Firefox.app/Contents/MacOS/firefox -P doug"
    And you can make an executable with icon in a bash script with above and chmod u+x it and save to Desktop too.
    Message was edited by: doug pennington

  • 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.

  • Oracle 11 RPD: Create 2 Logical Tables Based on 1 Physical Table

    Hello,
    I have a date dimension table in the physical layer. From that I need to create 2 date dimension tables in the BMM layer. One is for order date and the other is for shipped date. There is a ship_date_key and an order_date_key in my fact table that I'm trying to use as my foreign key.  Seems I can create a joined ship date logical table or a joined order date logical table but not both.
    Very new to OBI Admin tool.  Any help would be greatly appreciated.

    If you create only one alias from Date dimension in Physical Layer then you can get only one data either Ship Date or Order date details.
    The data from Date dimension gets retrieved on the basis of the Join i.e on which key it was joined to the Fact.
    To solve the above ambiguity you should create two separate alias tables in physical layer, hence you will have two logical tables in BMM Layer
    Create Dim_Ship_Date and Dim_Order_Date from Date dimension.
    And now, you can join the fact with these two aliases on different keys. This practice is usually followed.
    If found useful mark the answer
    Srikanth

  • 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

  • Question on Alias Table

    Hi,
    I have three tables, Employer, Employee and Address. I created an Alias for Address table because the same table will be used in the same query for both Employer and Employee Addresses.
    Employer is joined to Address on AddressId, Employee is joined to AddressAlias on AddressId and Employer and Employee are joined together on EmployerID.
    When I query Employer.Name,Address.Address,Employee.Name,AddressAlias.Address, BI considers AddressAlias as the Address Table (which it should), but does not select the Employee address nor does it do the second outer join. Therefore, I get the same address in both columns, which is wrong.
    here's the query BI server issues:
    select distinct D1.c1 as c1,
    D1.c2 as c2,
    D1.c3 as c3,
    D1.c3 as c4
    from
    (select distinct T30717.EMPLOYER_NAME as c1,
    concat(concat(T31027.FIRST_NAME, ' '), T31027.LAST_NAME) as c2,
    T44205.ADDRESS_1 as c3
    from employer T30717, EMPLOYEE T31027, ADDRESS T44205
    where ( T30717.ADDRESS_ID = T44205.ADDRESS_ID (+) and T30717.EMPLOYER_ID = T31027.EMPLOYER_ID (+) ) and ( T30717.EMPLOYER_ID = 7585 and T31027.EMPLOYER_ID = 7585 )
    ) D1
    order by c1, c2, c3
    Can anyone help.
    Thanks
    rkingmdu

    You didn't describe your BMM logical model. I'm sure you got the LTS wrong.
    It's impossible to answer correctly without knowing:
    a) complex joins
    b) your logical tables and LTS
    I think you need to have 2 LTS with 2 mappings (1st being Employer.Name,Address.Address, EmployeeName and 2nd Employer.Name, Employee.Name, Address.Address)
    Order is important.
    This isn't a specific answer - rather a try to help you to get LTS configured correctly.

  • 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...

  • 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

Maybe you are looking for