Duplicating Physical Tables vs Aliasing Physical Tables

Hi All,
what is the significance of alising a physical table over duplicating the physical table. In which senarios we use those strategies?
Thanks and Regards,
Sreekanth.

hi,
alias is different to duplicate. if duplicate a table it contians all the joins with another table and duplicate is mainly used for reference where as alias is used when we have 2 joins for same fact.
thanks and regards
Ranganathan T.A.

Similar Messages

Dimension on Aliased Physical Table

Hi,
Simplified example of my problem.
I have two tables; -
journals
balances
Both of these are the fact tables connected various dimension tables.
One of these is code combinations, which has cost centres, expense types etc. This is used by both fact folders, by means of aliasing the physical table to pull it into the latterly created of the two business areas for balances.
This works fine, until I try to create a dimension against the code combination folder.
Then I get -
ERRORS:
BUSINESS MODEL Balances:
[nQSError: 15001] Could not load navigation space for subject area Balances.
[nQSError: 15019] Table Code Combinations is functionally dependent upon level Cost Centre, but a more detailed child level has associated columns from that same table or a more detailed table.
n.b. I do not want to run reports against multiple FACTS but as soon as I create a dimension on the aliased physical table the dimension points at the original physical table as its source - which I cannot change - and not its aliased version which is my desired action.
Anyone tell me where I am going wrong please??? (the dimension is large, I do not want to have to create multiple copies of the data in the underlying data warehouse)
thanks,
Robert.

Hi angel,
If i got your question right,
> I create a dimension on the aliased physical table the dimension points at the original physical table as its source ,and not its aliased version which is my desired action.
Definately it would point to the original table when you refer it as its source is that.
An idea can you partition the code combination table into 2 that is cost centres as one single table and expense type as 1 single table .So that way u can create dimension on the one desired.
Cheers,
KK

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

Physical query not accessing Fact Table/Column

Hi,
I'm facing a weired issue. I have a report with 32 columns. 22 columns are from 8 dimensions and 10 columns from 3 Facts.
But while observing the Physical query. Its not touching 1 particular Column coming from 1 Fact Table.
So, in the query only 2 Fact columns are there and in the report its always Null value.
When I'm adding a filter on that Fact Column to force Analytics to go and join with that Fact Table, Its not including that Fact Table/Column and producing a very funny query like the following:
SELECT
COLUMNS....
FROM
TABLES (8 DIMENSION AND 2 FACTS)
GROUP BY COLUMNS....
HAVING cast(NULL as DOUBLE PRECISION )>1234
================================
"cast(NULL as DOUBLE PRECISION )>1234" - this is the filter, I have added on that Fact Column.
Note- It may be because of RPD configurations/joins. But the system (Siebel Analytics 7.8) is in production for 2 years and 500 users using it and nobody reported any issue like this before.
Can anyone please give me some helpful hint, idea, what is happening?
Thanks in Advance
Regards
Sudipta

Hi Kishore,
Thanks for your reply.
However, I did the analysis and found following, please let me know if your perspective is falling in the same line or not.
Scenario:
Suppose all the columns i'm trying to fetch, are coming from 5 dimensions [d1,d2,d3,d4,d5] (some of them are aliased table) and 3 fact tables [f1,f2,f3]
Now, the report is not fetching data for c1 column which is coming from f3 fact table. Even f3 table is not included in the physical query.
Now what i found that, there is a dimension suppose d3 which is not having any direct join with f3, but other facts like f1,f2 have joins with d3 table.
If i remove the columns coming from d3 dimension from report, then f3 fact columns are getting populated in report.
Problem:
I need to provide a single physical query for that report, while those report columns are defined by the business.
Questions:
1. So is it really possible to create a query for that kind of report without changing the RPD design?
2. If no, then is the only solution to split that report (i'm thinking) into 2-3 sub reports?
Thanks all of you for replying and providing your thoughts.
Regards
Sudipta

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

Unable to include a table in a Physical Model Diagram via the RON

Hi,
In Designer 10g I am unable to include a table in a Physical Model Diagram (Edit > Include) if I open the diagram via the RON, but it works if the diagram is opened via the Design Editor.
I found Doc ID268944.999 on Metalink which seems to detail the same problem, but no solution. So does this only work via the Design Editor now?
Thanks,
Antony

I tried to find the item on Metalink but could not find it.
I have never tried to move tables in the RON to an SMD.
Of course I do not know why you would want to do that. The DE does it so nicly.
What error message are you getting?
Tell me exactly what your doing and I will try it here.

Dimension table and fact table exists data physically

Hi experts,
can anyone plz tell me weather dimension table and fact table exists data physically or not/

Hi..Sudheer
SAPu2019s BW is based on "Enhanced Star schema" or "Info Cubes" database design.This database design has a central database table, known as u2018Fact Tableu2019 which is surrounded by associated dimension tables.
Fact table is surrounded by dimensional tables. Fact table is usually very large, that means it contains
millions to billions of records.
These dimension tables doesn't contain data it contain references to the pointer tables that point to the master data tables which in turn contain Master data objects such as customer, material and destination country stored in BW as Info objects. An InfoObjects can contain single field definitions such as transaction data or complex Customer Master Data that hold attributes, hierarchy and customer texts that are stored in their own tables.
SID is surrogate ID generated by the system. The SID tables are created when we create a master data IO. In SAP BW star schema, the distinction is made between two self contained areas: Infocube & master data tables/SID tables.
The master data doesn't reside in the satr schema but resides in separate tables which are shared across all the star schemas in SAP BW. A numer ID is generated which connects the dimension tables of the infocube to that of the master data tables.
The dimension tables contain the dim ID and SID of a particular IO. Using this SID the attributes and texts of an master data Io is accessed.
The SID table is connected to the associated master data tables via teh char key.
Fact table(Transaction data,DIM ID)<>Dimention Table(SID and Dim ID)<->Masterdata table(SID,IO)
Thanks,
Abha

Where are tablespace, table structure, package physically stored?

Running Oracle 11g on Linux.
My disk settings are:
/dev/sda1 (boot)
/dev/sda2 (/)
/dev/sda3 (/u01) for Oracle software. Base: /u01/app/oracle
/dev/sda4 (swap)
/dev/sdb1 ASM disk for DATA
/dev/sdc1 ASM disk for DATA
/dev/sdd1 ASM disk for FRA
1. Where are the tablespace, table structure (such as table name, column name, column type, primarykey key, and index), package, procedure, trigger, and function PHYSICALLY stored? I want to know the common directory path and disk location?
2. When the Fast Recovery Area (FRA) does the backup job, will the tablespace, table structure (column, type, key, index), package, procedure, trigger, and function also be backed up to the Fast Recovery Area (FRA), in addition to the data files, control files, redo logs and archived logs?
Thanks

You need understand the difference and concept about Physical Storage Structures and Logical Storage Structures.
http://docs.oracle.com/cd/E11882_01/server.112/e16508/physical.htm
http://docs.oracle.com/cd/E11882_01/server.112/e16508/logical.htm
/dev/sdb1 ASM disk for DATA
/dev/sdc1 ASM disk for DATA
/dev/sdd1 ASM disk for FRA
1. Where are the tablespace, table structure (such as table name, column name, column type, primarykey key, and index), package, procedure, trigger, and function PHYSICALLY stored? I want to know the common directory path and disk location?Probably your database is stored on ASM Filesystem, wich are using the /dev/sdb1 and /dev/sdc1. So if your database files is on ASM "DATA" diskgroup then all objects is there.
Query V$DATAFILE, V$CONTROLFILE, V$LOGFILE, V$TEMPFILE
2. When the Fast Recovery Area (FRA) does the backup job, will the tablespace, table structure (column, type, key, index), package, procedure, trigger, and function also be backed up to the Fast Recovery Area (FRA), in addition to the data files, control files, redo logs and archived logs?FRA is used to hold backups of database then your objects are backed up there too.
Use RMAN to check it:
LIST BACKUP;
LIST ARCHIVELOG ALL;
Edited by: Levi Pereira on Oct 8, 2012 12:05 PM
Edited by: Levi Pereira on Oct 8, 2012 12:09 PM

Lgical table from two physical table

Hi,
I am trying to design a logical fact table from two physical table. One table has transaction data and another has accounting data. The requirement is, I need to merge the rows between these two tables, where were it matches. If the keys are not matching between these two table then also I need to bring those rows from both tables as separate rows. How can i do this? Also can i have a logical table as source for my fact table.

You'll need outer joins in your physical layer and you can drag the columns from both physical tables to a single logical table and you will see in the BMM layer it will create the two logical table sources.

Physical table list against Cluster Table CDPOS and PCDPOS

Hello experts,
For function customized requirement, we need to know the physical table
list against Cluster Table CDPOS and PCDPOS and EDID4, just like
Cluster Table BSEG contain with six physical tables
BSAD/BSID/BSAS/BSIS/BSAK/BSIK. Also we want to know if there is any
general way to find out the physical table list for any cluster table.
My question is:
1. How can I find all the transparent table for Cluster Table CDPOS?
just like Cluster Table BSEG has transparent tables of
BSAD/BSID/BSAS/BSIS/BSAK/BSIK.
2. How can I find all the transparent table for Cluster Table PCDPOS?
3. How can I find all the transparent table for Cluster Table EDID4?
4. Additionally,I want to know if there is any
general way to find out all the transparent tables for an specific
cluster table.
Many thanks.

Hello,
simply look in transaction SE11.
Example:
1. SE11 -> Table CDPOS - Display. On Tab 'Delivery and Maintenance' you'll find Pool/Cluster 'CDCLS'.
2. SE11 -> Table CDCLS -> Display. On next screen position on CDCLS-> Where-used-list -> Tables -> you'll find tables CDPOS and PCDPOS.
Same thing with EDID4 -> EDI40 ...
Regards Wolfgang

Records are getting duplicated on presing enter key in table control

Hi All,
I am using table control in module pool program. The issue is records are getting duplicated on press of enter key.
I cannot use sy-ucomm enter and do some validation thing in my code. As the record should get update in int_tab(internal table). Otherwise ZSTR_TAB(table control)will be blank after pressing enter key.
I have gone through all the previous threads on this. Have implemented sol provided in one of threads. Now records are not getting duplicated but the next line is getting disabled. The code to avoid duplication is :
MODULE read_table_control INPUT.
data tc-lines type i.
DESCRIBE TABLE int_tab LINES tc-lines.
IF tc-lines GE control-current_line.
    MODIFY int_tab FROM zstr_tab INDEX control-current_line.
ELSE.
    IF gcreate_code = 'CREATE'.
      zstr_tab-zemp_num = gemp_num.
      INSERT zstr_tab INTO int_tab INDEX control-current_line.
    ENDIF.
    IF gchange_code = 'CHANGE'.
      MODIFY int_tab FROM zstr_tab INDEX control-current_line.
    ENDIF.
ENDIF.
ENDMODULE.
This module is in PAI. Now how to make the lines in control input enabled??
Any other sol for avoiding duplicate records on pressing enter key?
Thanks,
Seema

Hi,
Have you written any code in when Others of case...Endcase ?
If Yes then checkout if there is anything wrong over there, debug and check.
If not then write delete adgecent duplicates from Int_tab comparing key fields.
Also check in PBO, if you have written any query that selects data from particular table and appending the internal table irrespective of entry is already exist. So you should write select query in the if...Endif block as below,
If int_tab[] is not initial.
select * from ZSTR_TAB
into table int_tab
where .........
endif.
If above is not the case then debug and check where exactly entries are getting duplicated so that I can have idea what exactly is happening.
Regards,
Umang Mehta

Multiple 'logical joins' between a fact table and one dimension table

It appears that one cannot create multiple ‘logical joins’ between a fact table and one dimension table in OBIEE using the Oracle BI Administration Tool. For example, considering a Business Model with a dimension table TIMES and a fact table FACT containing START_TIME and END_TIME, we would like to create separate logical joins from FACT to TIMES for the START_TIMEs and END_TIMEs? Obviously, the underlying foreign keys can be created, but as far as I can tell the Oracle BI Administration Tool doesn’t support this. The workaround would be to replicate the TIMES table, but that’s ugly.
I seek an alternative approach.

Try this. Create an two aliases for the TIMES dimension (Start & End) in the Physical Layer and then remove foreign key to the "Parent" Times dimension. Create the Foreign Key in the Physical Layer to the new aliases and then create the complex joins in the BMM Layer to the new aliases as well. This will allow you to present both dates within the same table in the Presentation Layer. Not the most elegant solution but it works.

Universe Design - Linking two columns in a table to a subordinate table

Post Author: bradwist
CA Forum: Semantic Layer and Data Connectivity
I hope this is the right forum to ask a question about Universe Design. If not, please redirect me. Thanks.
I have a question on a universe design that I am trying to implement. I'll try to simplify to what I really am focusing on here. I've got a table, PersonRelationship, that defines a relationship between two people (Person1, Person2). Both Person entities have a set of data that are contained in the PersonTable. I'm trying to set up a universe design that allows the PersonRelationship table to join to the Person table twice, for Person1 and Person2 (fields are Person1Id and Person2Id respectively).
(below is a poor attempt to draw the table relationships)
Person (table)          PersonRelationship (Table)                  OtherData (table)
PersonId (PK)          RelationshipId (PK)                             OtherDataId (PK)
               ^----
Person1Id (FK)
         ^----
Person2Id (FK)
                               OtherDataId (FK) -
^
I then would like to build a query in Web-I that allows me to query against certain parameters for both Person1 and Person2. For instance, I may want information that reflects when Person1 is male and Person2 is female.
Is there a way to establish this relationship within the universe without having to create two physical tables?
Thanks.

Post Author: bradwist
CA Forum: Semantic Layer and Data Connectivity
With further information, I believe the answer to this is Aliasing the table. But when I create and Alias of the person table, it doesn't show up in WebI. I only see the original. Not sure what the problem is.

How map to my particular table to the fact table in obiee 11g...

Hi friends,
I did this simple report in obiee 11g(i.e)
"NATIONALITY COUNT IN DEPARTMENT WISE"
For that i used the following tables:
per_all_assignments_f----->fact table
hr_all_organization_units----->dim table(containing departments)
per_all_people_f---------------->dim table(containing nationality)
I made all the mappings in the physical diagram, as also viewed my report in BI answers
It shows the following results like
NATIONALITY---------------------------------------------------------------------COUNT(NATIONALITY)
AUS------------------------------------------------------------------------------------------------24
AFR------------------------------------------------------------------------------------------------25
PHQ_VB-------------------------------------------------------------------------------------------40
SH_VT----------------------------------------------------------------------------------------------4
The problem is for me it is showing the above results, but the nationality column is of various codes of the country.
Since i doesnt want the code of the nationalitian to display in the results..i need the meaning of each and every nationality..
like,
AUS------------------------Australian
AFR-------------------------African
PHQ_VB----------------------Germanian(assigned)
Since i know that the meaning for the nationalitian is available in "FND_LOOKUP_VALUES"...okay..
I can import "FND_LOOKUP_VALUES" table to the physical layer...but how i can able to give the mapping to the fact table in my physical diagram...
In my report the fact table is "per_all_assignments_f"
As my fact table doesnt contains any matching column corresponding to the dimension table "FND_LOOKUP_VALUES".....
Then how i can give mappings to the fact column???? for viewing the full meaning of the nationalitian in my report.....Help me friends...
Regards,
Harry...

Hi bifact,
I followed the step that U asked me to go but im stuck with later.....
*) I saved the query that i executed in toad with the columns showing country codes and country meaning to the excel sheet...
This is the query that i executed in toad and copied data s in excel sheet..
select z.lookup_code, z.meaning
from per_all_people_f e, per_all_assignments_f f, hr_all_organization_units h, fnd_lookup_values z where
e.person_id = f.person_id and f.organization_id = h.organization_id and e.business_group_id = f.business_group_id
and f.business_group_id = h.business_group_id and f.location_id = h.location_id
AND z.lookup_type(+) = 'NATIONALITY'AND z.lookup_code(+) = e.nationality and sysdate between
e.effective_start_date and e.effective_end_date and e.nationality is not null
*) After that i created a system DSN for the excel drive..
*) After that when i tried to import metadata of the excel data that is saved, it showed me connection failed...
For importing this excel data
what connection details i need to give:--------------------
as well as user name and also password...
Soon after importing this excel you said that to give key connection only to fnd_lookup_tables(dim) and that excel data..
if so, again im not giving key connection to my fact table..
I think again the same error will occur that no logical mapping is not made to fact so again repository is inconsistent...
Hi bifact sorry to ask you, but can you see the steps that i followed is correct and after that wat more steps i need to proceed..Can you tell me in breif manner...Thanks for your help...
Regards,
Harry...

Reference a Derived table in another Derived Table

Is it possible to reference a derived table from another derived table? I am using Business Object XI 3.0.

This is not possible as the Designer wants physical tables...
What you could do is create the second derived table as follows:
SELECT     table1.col1,
     table1.col2,
     table2.col1,
     table2.col2
FROM     table1,
     (SELECT col1,
          col2
     FROM     atable) table2
Regards
Jacques

Duplicating Physical Tables vs Aliasing Physical Tables

Similar Messages

Maybe you are looking for