About Fact Tables and Image Tables

Not sure, if this is correct forum for Oracle BI 10.x EE, but still
I couldn't find another forum, quickly, hence posting here.
Pardon me.
Here is the main Q's
I need little help.
Our company is implementing Oracle BI 10.x. We don't have much experience in Siebel Analytics/OBI.
We have few fact tables e.g. W_XXXX_F, which we need/wish to extend. We are not sure about which methodology we should implement. When we talked with few SA experts they mentioned we need to extend based on ROW_WID. Well, this column doesn't exists anymore in many fact tables, so currently we are thinking of creating ROW_WID on this F table manually and then create WC_XXXX_FX and take these two tables in physical layer of RPD.
Additially, we need to create few Informatica mappings, again SA experts pointed out to use Image tables. Our data source is Oracle Applications, I don't have much idea about Image tables, but clearly there is not S_ETL_I_IMGAGe or so tables in Oracle Apps
Please guide us as how to proceed on these two issues.
Rajat

Similar Messages

What is FACT table and FLAT table?

Hello,
 Kindly tell me what is mean by FACT table and FLAT table and how it is use in the BI system ?also tell me can i see these table in the system ?if yes then please tell me the procedure to see the content of the FACT and FLAT table. And also tell me about the SID table and how to see it.

Cube consists of Fact tables and Dimension tables.
The structure of these tables are "Flat".
Cube consists of two factables... 'F' - Fact table and 'E' - Fact table.
The naming convention will be..
/BIC/F<..Cube name..> for F Fact table
/BIC/E<..Cube name..> for E Fact table
Eg: for cube "EMPLOYEE" the names are..
/BIC/FEMPLOYEE
/BIC/EEMPLOYEE
The dimention tables have naming convention..
/BIC/D....
You can check these tables in SE11 or you can use the transaction LISTSCHEMA and then provide the Cube name.
SID's tables are used to link the master data with the dimention tables.

Fact Table and Dimension Tables

Hi Experts, I'm creating custom InfoCubes for data coming from non-SAP source systems. I have two InfoCubes. Tha data is coming from like 10 tables. I have 10 DataSources created fo this and the data will be consolidated in Standard DSO before it will flow into 2 InfoCubes.
Now client wants to know before how much data will be there in InfoCubes in Fact table nad Dimension tables in both the InfoCubes. I have the total size of all the 10 tables from the sources given to me by the DBA. I wan not sure how I can convert that info for Fact table and Dimension table as I have not yet created these Infocubes.
Please help me with this on how I should address this.

hi,
The exact data will be hard to give however you can reach at a round figure in your case.
You are consolidating the data from the tables that means that there is relation between the tables. Arrive at a rough figure based on the relation and the activity you are performing while consolidating the data of the tables.
For example, let us say we want to combine data for sales order and deliveries in a DSO.
Let Sales order has 1000 records and Delivery has 2000 records. Both the tables have a common link (Sales Order).In DSO you are combining the data that means the data will be at the most granular level consist of Delivery data, so the maximum no of records which the consolidated DSO can have is 2000.
regards,
Arvind.

Reg: Fact table and Dimension table in Data Warehousing -

Hi Experts,
I'm not exactly getting the difference between the criteria which decide how to create a Fact table and Dimension table.
This link http://stackoverflow.com/questions/9362854/database-fact-table-and-dimension-table states :
Fact table contains data that can be aggregate.
Measures are aggregated data expressions (e. Sum of costs, Count of calls, ...)
Dimension contains data that is use to generate groups and filters.
This's fine but how does one decide which columns to consider for Fact table and which columns for Dimension table?
Any help is much appreciated.
Pardon me if this's not the correct place for this question. My first question in the new forum.
Thanks and Regards,
Ranit Biswas

ranitB wrote:
But my main doubt was - what is the criteria to differentiate between columns for Fact tables and Dimension tables? How can one decide upon the design?
Columns of a fact table will often be 'scalar' attributes of the 'fact' data item. A dimension table will often be 'compound' attributes of a 'fact'.
Consider employee information. The EMPLOYEE table can be a fact table. It might have scalar attribute columns such as: DATE_HIRED, STATUS, EMPLOYEE_ID, and so on.
Other related information that can't be specified as a single attribute value would often be stored in a 'dimension' table: ADDRESS, PHONE_NUMBER.
Each address requires several columns to define it: ADDRESS1, ADDRESS2, CITY, STATE, ZIP, COUNTRY. And an employee might have several addresses: WORK_ADDRESS, HOME_ADDRESS. That address info would be stored in a 'dimension' table and only the primary key value of the address record would be stored in the EMPLOYEE 'fact' table.
Same with PHONE_NUMBER. Several columns are required to define a phone number and each employee might have several of them. The dimension tables are used to help 'normalize' the data in the employee 'fact' table.
And that EMPLOYEE table might also be a DIMENSION table for other FACT tables. A DEVELOPER table might have an EMPLOYEE_ID column with a value that points to a 'dimension' row in the EMPLOYEE dimension table.

Fact table and dimension table

what is the difference b/w fact table and dimension table

A fact table contains numeric values and also contain composite key(i.e collection of foreign key) e.g.. sales and profit. Typically has two types of columns: those that contain facts and those that are foreign keys to dimension tables.
Dimension tables, also known as lookup or reference tables, contain the relatively static data in the warehouse. It contains character values E.g Customer_name,Customer_city.
Dimension tables store the information you normally use to contain queries. Dimension tables are usually textual and descriptive and you can use them as the row headers of the result set.
Rachna

To find the size of the fact table and dimension table

Hi experts,
Can anyone plz tell me if i want to find size of the fact table and size of the dimension table to find cardinality and line item do we first build statistics then find size by transaction DB02 or any other method we have?
Thanks in advance

Hi ,
Please go to Tcode DB02 >Space>Table and Indexes.Give your table name or pattern (like /BIC/F* for gettinf all the Fact tables)
.This will give you sizes of all the table.
Also if you want to get list like TOP 30 Fact tables and Dimension Table.Please use TCode ST14, this will give a desired output with all the required details.
-Vikram

Where can we see Fact Table And Dimension Table in DataWarehouse Workbench?

Hai Experts
where can we see Fact Table And Dimension Table in DataWarehouse Workbench?
Best Regards
nvnkmr12

Hi
Refer the link below and you will get a comprehensive explanation of how data is stored and modeled in BI. If explains fact table, dimension table, SID table, P and Q , X and Y tables.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
Cheers
Umesh

Ratio between Fact table and Dimention table for a Infocube

Hi All,
How can we reduce the Ratio between Fact table and Dimention table for a Infocube below 20%.??
please give suggestions

Hi
Reduce Ratio??
The Ratios are dependent on the Fact Table, and the Dimension table that is modeled for your Cube.
You cannot change ratio individually, but can set the Line Item Dimension , provided you have only one char object is taking much space and bulky with much percentage, based on your requirement. You can always use fine tuning objects.
Please be more specific while posting, to get right help from sdn.
Hope it helps

Backup and restore georaster table and rdt table by image id

Hellow everyone,
I want to backup my georaster table and rdt table by the Specified image id and also can use these georater rows to restore? How can I do? the geraster table structure is as follows:
image_table
id NUMBER,
filename VARCHAR2(255),
raster SDO_GEORASTER
Best Regards,
Lin

ylin wrote:
Hellow everyone,
I want to backup my georaster table and rdt table by the Specified image id and also can use these georater rows to restore? How can I do? the geraster table structure is as follows:
image_table
id NUMBER,
filename VARCHAR2(255),
raster SDO_GEORASTER
Best Regards,
LinIf I understand you correctly, There is no specific issue if you want to export table with spatial data - It is the same as with normal tables.

What is auxilary mappings in Informatica and IMAGE tables in DAC

Hi Guys,
Please let if you have any info regarding auxillary mappings and Image tables
Thanks and Regards,
sp

Auxillary mappings and Impae tables are both used in implementing Change Capture and primarily this concept is Used in Siebel.
For more information look at this link -
http://download.oracle.com/docs/cd/E12104_01/books/DAC/DACCommonTasks18.html
Cheers,
Sid

DATA BASE TABLE AND INTERNAL TABLE

Dear Friends,
please help me out in getting complete information about database table and internal table.
you can email me at < Removed by moderator - please maintain e-mail iDs in Business Card>
Message was edited by:
Arun Varadarajan

Hi Hazi,
DATABASE Tables :
This are the tables which are stored in the database (eg Oracle , informix , DB2 etc..) Physically. u can view it from T-codes SE11 or SE16. here in SE11 u can create ur own Transparent table.
for more information...
http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/dictionary_tutorial.html
Internal Tables.
While generating reports or other objects we are not modifying the database tables directly first we are selecting the data of the database table into the internal tables... so that we can reduce the database access time and network traffic .. which is highly needed in R/3 system..
internal tables are not exist phyiscally in the system. its like a array. the existance of the internal tables is upto the program execution in which u r declaring nd using it...
for more information..
http://www.sapbrainsonline.com/TUTORIALS/TECHNICAL/internaltables_tutorial.html
Hope it will solve ur problem..
Reward points if useful..
Thanks & Regards
ilesh 24x7

Inforation on Pool tables and cluster tables required.

I want to know about the pool tables and cluster tables like how to create them and how to look the tables associated with the given tables. Like for the table BSEG we have other tables linked BSID etc. I'm new to this concept please guide me.

Pooled Table:
A pooled table in R/3 has a many-to-one relationship with a table in the database (see Figures 3.1 and 3.2). For one table in the database, there are many tables in the R/3 Data Dictionary. The table in the database has a different name than the tables in the DDIC, it has a different number of fields, and the fields have different names as well. Pooled tables are an SAP proprietary construct.
When you look at a pooled table in R/3, you see a description of a table. However, in the database, it is stored along with other pooled tables in a single table called a table pool. A table pool is a database table with a special structure that enables the data of many R/3 tables to be stored within it. It can only hold pooled tables.
R/3 uses table pools to hold a large number (tens to thousands) of very small tables (about 10 to 100 rows each). Table pools reduce the amount of database resources needed when many small tables have to be open at the same time. SAP uses them for system data. You might create a table pool if you need to create hundreds of small tables that each hold only a few rows of data. To implement these small tables as pooled tables, you first create the definition of a table pool in R/3 to hold them all. When activated, an associated single table (the table pool) will be created in the database. You can then define pooled tables within R/3 and assign them all to your table pool.
Pooled tables are primarily used by SAP to hold customizing data.
Cluster Table:
A cluster table is similar to a pooled table. It has a many-to-one relationship with a table in the database. Many cluster tables are stored in a single table in the database called a table cluster.
A table cluster is similar to a table pool. It holds many tables within it. The tables it holds are all cluster tables.
Like pooled tables, cluster tables are another proprietary SAP construct. They are used to hold data from a few (approximately 2 to 10) very large tables. They would be used when these tables have a part of their primary keys in common, and if the data in these tables are all accessed simultaneously.
Table clusters contain fewer tables than table pools and, unlike table pools, the primary key of each table within the table cluster begins with the same field or fields. Rows from the cluster tables are combined into a single row in the table cluster. The rows are combined based on the part of the primary key they have in common. Thus, when a row is read from any one of the tables in the cluster, all related rows in all cluster tables are also retrieved, but only a single I/O is needed.
A cluster is advantageous in the case where data is accessed from multiple tables simultaneously and those tables have at least one of their primary key fields in common. Cluster tables reduce the number of database reads and thereby improve performance.
Restrictions on Pooled and Cluster Tables
1. Pooled and cluster tables are usually used only by SAP and not used by customers, probably because of the proprietary format of these tables within the database and because of technical restrictions placed upon their use within ABAP/4 programs. On a pooled or cluster table:
2. Secondary indexes cannot be created.
3. You cannot use the ABAP/4 constructs select distinct or group by.
4.You cannot use native SQL.
5.You cannot specify field names after the order by clause. order by primary key is the only permitted variation.
For creation of pooled /cluster table, have a look at below link.
http://help.sap.com/saphelp_erp2004/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
For creation of table pool /cluster, have a look at below link.
http://help.sap.com/saphelp_erp2004/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
Have a look at below link.
http://www.sap-img.com/abap/the-different-types-of-sap-tables.htm
Best Regards,
Vibha
*Please mark all the helpful answers

Reg value table and check table

Hi Friends,
I have defined a value table(ZVALTAB) for a domain and defined the relation ship between check table(ZCHKTAB) and dependent table(ZDEPTAB). Here value table and check table both are different. My problem is while I am entering the values into check table, it is not restricting the values to enter into check table even those values are not in value table. And while I am entering values into the dependent table through the menu option Utilities->Create entries then also foreign key is not working. But when I use the SM30 then the foreign key is working. So can any body explain me when this value table restrict the values and why the option Utilities->Create entries is not validating the foreign key relation ship.
Sathish Reddy

Hi,
Value Table will just provide you the possible set of values. It won't restrict u for the wrong entries. Moreover whenever u enter entries thru Create entries no user interface is available. The constraints whatever we give is not at all stored in the Data Dictionary. Only the user interface which takes care all about this. Hence it wont restrict you. For this u have to create table maintenance generator for your table. Then it will restrict the values against check table.
Both Value table and Check table will provide u possible set of values. But only the check table will restrict the values.
Hope this will help u.

REG:Internal table and Database table

Hi Xperts,
Can you tell me /give me a sample code so as to
Compare the data present in the database table and internal table.i.e
Wheher the data in the db table matches with the data in the internal table
Thanks.

Hello,
First make sure that data is there in the internal table
TABLES : Declare your table example MARA, VBAK etc
TYPES: BEGIN OF ITAB1,
Declare your fields here
example
v_mat(10) type c,
v_code(5) type I,
END OF ITAB1.
IF NOT ITAB[] is INITIAL.
LOOP AT
END IF.
To compare the data with DB tables, read the database table and copy into the internal table ITAB2
Then compare the ITAB and ITAB1
IF ITAB1[] = ITAB2[]
END IF
See these links for [Creating Internal Tables|http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3660358411d1829f0000e829fbfe/content.htm]
[Comparing Internal Tables|http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3841358411d1829f0000e829fbfe/content.htm]
See this for more about [Processing Internal Tables|http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb36ae358411d1829f0000e829fbfe/content.htm]
Declaring the internal table in ABAP objects
[Thanks|http://chandranonline.blogspot.com/]
[Chandran|http://chandranonline.blogspot.com/]

Oracle Data Compression on SID tables and Dimension Tables

Hello Community,
We have had great success with Oracle compression on ODS tables that are no longer loaded.
We'd now like to move on to other types of BW tables that are very large.
OSS Note 701235 provides answers to questions concerning the possible use of Oracle compression together with SAP BW.
But the Note does not give suggestions for (or against) Oracle compression on SID tables or Dimension tables.
I believe both table types would exhibit the same behaviour : mostly inserts of new SID IDs and new DIM IDs, but few updates to existing SID or Dimension records. If this is true, then both are good candidates for oracle compression.
Do you also agree that this is the typical behaviour for SID tables and dimension tables ? And that these types of tables are good candidates for Oracle compression in a large BW system ?
Thanks kindly!
Keith Helfrich

Hi all,
Although this is an old thread I stumbled on during my own investigations I can provide some answers to your questions.
Table candidates for compression are found by these criteria
 - Table size big enough?
 - Long lifetime of object planned ?
 - No or only rare structural changes for the table ?
 - u201EUpdateu201C rate low : is your data mostly kind of u201Cread onlyu201D ?
-- for the wideley used rolling window partition techniques of
 tables in BW this is not a problem: mostly INSERTu2019s in the
 current partition not affecting other partitions
BW tables that can benefit from compression (see SAP notes 105047,701235)
 - PSA tables with data that must be saved for a longer time
 - ODS change log (no Updates of old data, only Inserts of new data)
 - u201Ehistoricalu201C cubes wich get no changes in table structure anymore
Limitations
 - normal Insert or Update statements are stored ALWAYS in uncompressed
 format and must be compressed separately ( <= Oracle10g )
 - Slight CPU overhead of compression, butu2026
 -- CPU consumption is more than compensated by doing less I/O as
 for Bulk loads or parallel processing
 -- SAP BW transformations took a significant amount of CPU for
 overall load-time into cubes caused by the application server not
 the database
 - Table must have not more than 255 fields
 - Adding columns with an initial value or dropping columns require
 uncompression of the complete table (strongest limitation)
Consider all this above and you can decide that tables that going through UPDATE's are
not good candidates for compression or tables that can change it's structure (like
Fact- or DIM tables) .
Now, my questions to you:
Wich Oracle version do you use?
Wich tool do you use for Oracle compression?
BRspace (can you give an example ?)
ALTER ... MOVE COMPRESS
bye
yk

About Fact Tables and Image Tables

Similar Messages

Maybe you are looking for