Star Schema For OSA

I want to know where i can get the example of star schema of OSA ... Please Help me

Your' s suggestion utterly anticipated ..

Similar Messages

Star schema for a uploaded data sheet

Hi All gurus,
I am new to this tech . I have a requirement like this , I have to prepare the star schema for this data sheet as below .
REPORT_DATE     PREPARED_BY     Units On-time     Units Late     Non-Critical On-time     Non-Critical Lates      Non-Critical DK On-time     Non-Critical DK Lates
2011 -01     Team1     1
2011-02     Team1
2011-03     Team1
2011 -01     Team2
2011-02     Team2                         7     1
2011-03     Team2                              4 5
2011 -01     Team3
2011-02     Team3
2011-03     Team3     1                         3
(Take blank fields as zeros)
Note : There are 3 report date types 2011-01,02,03 and three teams team 1,2,3 as text data and all others columns contain number data .
I am given Time as dimensional table containing the Report Date and Whole sheet as Data table . So how to define the relationship for this in Physical and BMM ?
I am thinking to make Time as Dimensional Table and the whole table(as Data) as a fact table in the Physical layer . And then in the BMM , I want to carve out a Logical Dimension called Group from the Data Physical Table and then make Group and Time as dimensional Table and Data as Fact table .
Is this approach is correct ? please suggest me and if have any better Idea ,then please note down what are the tables to be taken as Dimension and Fact table in both physical and BMM . Your help willl be appreciated ,so thanks in advance . You can also advice for any change in no of Physical tables in the Physical schema design ..

Your' s suggestion utterly anticipated ..

Administrator desing star schema for "time series analysis"

Hi all,
I need to develop a set of dashboard with reports display a set of customers properties at
the last etl period (this month) and, for these customers, show their properties in the "past"
(this month - "n").
I've a fact table with cust_id and the classic dimension cust, period, product and so on...
My question is find a technique to desing the model in order to do these analysis or
use oracle administrator function to retrieve the photo of my customers in the past.
Here a specific user request:
Find all customer revenue that this month have status = 1
and, only for these customer having status != 1, show the revenue "in the past".
Any suggestion?
Ugo
Edited by: user8021820 on 13-apr-2011 1.43
Edited by: user8021820 on 13-apr-2011 1.44

http://gerardnico.com/wiki/dat/obiee/function_time

Design Fixed Assets Star Schema from OLTP DB

Hi,
Scope : Design Fixed Assets logical Star Schema for Demonstrate with OLTP tables
Our platform is Oracle 10g Forms and Reports deployed on Oracle 10g App Server._ At the moment we don’t have data warehouse constructed. We are pumping OLTP Data into Staging DB thru jobs and then by using materialized views getting the data in DWH DB which is in progress.
OBIEE 10g installed and working fine for testing.
We are planning to implement OBIEE for Reporting. As a starting point I would like to design Fixed Assets star schema to demonstrate FA reports in OBIEE from OLTP Tables.
FA- OLTP Tables:_
AC_UNIT_MASTR           – Business Units
AC_ACNT_MASTR           - Nominal Codes
AC_COST_CENTR_MASTR      - Departments
AC_MANTN_ASTS           - Assets transaction table
AC_AST_BAL_DETLS           – Period wise Asset summary
AC_AST_BAL_DETLS_V      - View
To achieve this
1).Import tables in physical layer and set physical joins
2).identify and create dimensions and set complex joins and then move to presentation layer.
Please suggest best approach to design Repository
Thanks
Regards,
Kulkarni
Edited by: hai_shailesh on Jan 25, 2012 11:36 PM
Edited by: hai_shailesh on Jan 25, 2012 11:38 PM
Edited by: hai_shailesh on Jan 25, 2012 11:39 PM

Hi Saichand,
Thanks for the response.
Already i referred that doc and completed practically. now i have to work on Finance data . as a starting point working with Fixed Assets module. already i designed centralised fact with dimensions as below
in physical&BMM layer defined relationship as below()
AC_UNIT_MASTR_D                  --> AC_AST_BAL_DETLS_F
AC_ACNT_YEAR_MASTR_D        --> AC_AST_BAL_DETLS_F
AC_ACNT_PERD_MASTR_D        --> AC_AST_BAL_DETLS_F
AC_COST_CENTR_MASTR_D      --> AC_AST_BAL_DETLS_F
AC_AST_GRP_MASTR_D            --> AC_AST_BAL_DETLS_F
AC_AST_SUBGRP_MASTR_D      --> AC_AST_BAL_DETLS_F
and
AC_ACNT_YEAR_MASTR_D        --> AC_ACNT_PERD_MASTR_D
When iam trying to create a dimension for Periods(AC_ACNT_PERD_MASTR) , Periods dimesnion created with two tables
AC_ACNT_YEAR_MASTR_D,AC_ACNT_PERD_MASTR_D
Please advice..
Regards,
Kulkarni

Star Schema and MV's

Hi Guys,
I have designed a Star schema for one of my datamart and my client is after me suggesting that over that I should create a MV to provide a consolidated view. I am trying to convience my client not to do so with the points as below:
1.     As we have created a Star Schema in the database we should take advantages of the same and should avoid creating another layer of reporting which in future will increase the complexity of the queries while expanding the functionality of the mart.
2.     We have to create a complete refresh MV and during refresh data will not be available for reporting to users and the duration will increase over the period of time once the data increases
3.     As MV are a table on a disk using a MV in this case will consume the tablespace which will increase over the period of time.
Please can you experts suggest of any more points or additions. We are using SAP BO as a reporting tool in our organization wherein a Universe can be created easily for reporting.
Cheers,
Shaz

I have designed a Star schema for one of my datamart and my client is after me suggesting that over that I should create a MV to provide a consolidated view. I am trying to convience my client not to do so with the points as below:You are convincing them to NOT do one of the the things materialized views were originally introduced to provide?
I'm purposely going all the way back to 8i documentation here to emphasize the point.
http://docs.oracle.com/cd/A87860_01/doc/server.817/a76994/qr.htm#35520
" Overview of Query RewriteOne of the major benefits of creating and maintaining materialized views is the ability to take advantage of query rewrite, which transforms a SQL statement expressed in terms of tables or views into a statement accessing one or more materialized views that are defined on the detail tables. The transformation is transparent to the end user or application, requiring no intervention and no reference to the materialized view in the SQL statement. Because query rewrite is transparent, materialized views can be added or dropped just like indexes without invalidating the SQL in the application code. "
>
The theory behind query rewrite is this: have them build their queries based on your star schema (or you a build a traditional view that does that), then build a materialized view that mirrors the query/view. If the materialized view is refreshing or not up-to-date, their queries will run (more slowly) against the star schema. If it is up-to-date it will be used instead, providing faster results.
But before you go to that trouble: they are asking for a consolidated view (presumably something easier to query - common in data warehousing). You can create a view to provide this. If that view is not fast enough for their performance requirements, materialize it. Yes, the materialized view uses space, but that space is the price you pay for meeting the performance requirement.

Star schema or Snowflake schema

Hi Gurus,
I have following dimensions and fact table. let me know can I go ahead with star schema and snowflake schema while building the cube.
1. Country's table
2. workgroup table --> each country have N number of work groups
3. user table---> each workgroup have N number of users.
4. time table.
5. fact table.

This is a similar thread that discusses on the design approach of star vs normalized tables
https://social.technet.microsoft.com/Forums/sqlserver/en-US/7bf4ca30-a1bc-415d-97e6-ce0ac3137b53/normalized-3nf-vs-denormalizedstar-schema-data-warehouse-?forum=sqldatawarehousing
In my experience majority of cases I've some across is also star schema for data marts where tables will be more denormalized rather than applying priciples of normalization. And I believe so far as its through SSAS cubes that you exposes the OLAP model
it would be much easier to implement relationships using a denormalised approach.
What you may do is to have a normalised datawarehouse if you want and then built the datamarts over it using denormalised tables (star schema) for the cube.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Star Schemas with designer 6.0

How can I easily create star schemas for a Datawarehouse in Designer6? Where can I still find documentation for such release?
Mauro

Mauro,
You should be able to create start schemas - search in the online help for all references to data warehousing
and star schemas. There should be a few topics.
Regards,
Dominic
Designer Product Management
Oracle Corp

What is star schema - pls explain with example

Hai.
what is star schema - pls explain with example
thanks in advance
Giri

Hi Giri,
SAP's BIW employs extended star schama
The extended star schema consists of a fact table (in two parts, E and F - f is the inbound table, E long-term storage). Dimension tables are connected to the fact tables via the DIMID(dimension id) which is a generated value and is stored in both dimension and fact tables. In addition, the dimension tables are connected to tables which hold master data values (or bind the dimension table to tables that hold the values), such as S tables, P, Q, X, Y. These dimension tables hold SIDs, again generated keys which relate values in the dimension table (the DIMIDs) with master data values. Thus, at the time of the query, join operations ensure that the master data values can be merged with the key figure values stored in the fact tables.
Truthfully, one does not need to understand this schema extensively in order to model in BI in SAP NetWeaver. It helps to understand master data, navigational attributes, etc. Otherwise, simply model the key figures in the fact table and the characteristics into dimensions and you're good - the application generates the star schema for you - you don't have to specify it.
See the transaction "LISTSCHEMA" which will show you the relationship between the F fact table and the other tables of the cube's star schema.
Also follow the link for more info:
http://help.sap.com/saphelp_nw04/helpdata/en/4c/89dc37c7f2d67ae10000009b38f889/content.htm
Thanks for any points you assign.
Regards

Error in database parameter for star schema table in RSRV

Hi Experts,
In RSRV, I executed the following checks in my cube and it is showing me the following error:-
1) Check database parameter for star schema table for InfoCube ZMM_MVAL
564971 units missing from fact table /BIC/FZMM_MVAL; see details
Message no. RSRV134
Diagnosis
In the fact table /BIC/FZMM_MVAL records have been found that contain values other than zero for key figures that have units, but that have no value for the unit of the key figure. Since the value of the unit has to correspond to the value of the key figure, this inidicates an error when the data was loaded. The values of the units have not been loaded into BW correctly. Choose Details to display the incorrect records.
2) Consistency of time dimension of InfoCube ZMM_MVAL
/BIC/FZMM_MVAL PARTITIONED 1878 ( 30 - 50 )
Please advise me on this.
Thanks in Advance.
Aparna

As mentioned in the log, check the Unit KFs in your cube and make sure that unit is populated for all such values.
e.g. if Qty is 5 KG, then unit KF will have 5 and unit info object should have KF.
Regards,
Gaurav

Multiple star or snow flake schema for universe

Hi,
I would like to know following things
1. Can we use more than one star or snow flake schema for an universe? and how to do this?
2. Using multiple shemas for one universe is it good practice or not?
Regards,
Manjunath

Manjunath,
This is exactly where BusinessObjects excels.
When dealing with multiple fact tables, you use contexts.
Contexts are very simple to understand and you must take your time to do so if you are going to successfully develop universes based on more than one fact table. No matter what universe you build, the rule for contexts is always the same; there are no different circumstances based on, say, industry.
Each context starts with a base table, typically a fact table, where all its joins are at the many end of the relationship. The joins are then followed out through the joined tables up other joins where they in turn are at the many end, as in a snowflake schema.
For example, consider the very basic schema below:
D1 -< D2 -< F1 >- D3 -< F2 >- D4
There are two tables that only have many joins attached to them - F1 and F2.
Starting with F1, I can move to D2. I can also move from there to D1. In the other direction, I can move from F1 to D3. However, I cannot move from D3 to F2 because the join cardinalities are in the wrong direction. So, I've found all the joins that belong in the first context. They are D1-D2, D2-F1 and F1-D3. By the same process, I will get to the second context containing joins D3-F2 and F2-D4.
It doesn't work well with many-to-many joins, but you really shouldn't be facing these in a well-designed multi-star.
As for one-to-one joins, set the cardinality as one-to-many in the direction that you know the relationship should be in for the ownership to work out correctly..
The process that I've described above is essentially how the Detect Contexts algorithm works.
The only remaining thing for you to read up on is the SQL parameters but essentially you need ot be able to select multiple contexts and generate multiple sql statements for each context. Otherwise, what's the point in defining them?!!
Hope that clears it up for you.
Regards,
Mark

Extended Analytics for star schema creation from HFM application

Hi,
I'm trying to create star schema via extended analytics from HFM application but facing below error
3/21/2013 12:30:07 PM : Status : Extracting Metadata
Schema did not previously exist.
Metadata update has failed. : (-2147217900) (One or more errors occurred during processing of command.)
Processing status change: (-2147217900)
Data processing failed. : (-2147217900) (One or more errors occurred during processing of command.)
3/21/2013 12:30:10 PM : Status : Processing completed with errors
Extended Analytics export completed with errors for Application GCS using Label GCS CON.
What could be the possible reason for it?
Also can someone please provide any suitable references or links to learn this EA for star schema creation.
Thanks,
Ravi Agrawal

The error you pasted here is incomplete. Look in the system messages and you will find more complete information that will lead you to the error's cause. Very often this is an error in the database, though sometimes it is caused by a metadata member with an invalid character. To determine whether it is data or metadata that causes the error, you could generate a schema with metadata only and see if the error appears.
-- Chris

Using two facts of two different star schemas and conformed dimensions

Hi,
I've been working as developer and database designer for years and I'm new to Business Objects. Some people says you can not use two facts of two different star schemas in the same query because of conformed dimensions and loop problems in BO.
For example I have a CUSTOMER_SALE_fACT table containing customer_id and date_id as FK, and some other business metrics about sales. And there is another fact table CUSTOMER_CAMPAIGN_FACT which also contains customer_id and date_id as FK, and some other business metrics about customer campaigns. SO I have two stars like below:
DIM_TIME -- SALE_FACT -- DIM_CUSTOMER
DIM_TIME -- CAMPAIGN_FACT -- DIM_CUSTOMER
Business metrics are loaded into fact tables and facts can be used together along conformed dimensions . This is one of the fundamentals of the dimensional modeling. Is it really impossible to use SALE_FACT and CAMPAIGN_FACT together? If the answer is No, what is the solution?
Saying "you cannot do that because of loops" is very interesting.
Thank you..

When you join two facts together with a common dimension you have created what is called a "chasm trap" which leads to invalid results because of the way SQL is processed. The query rows are first retrieved and then aggregated. Since sales fact and campaign fact have no direct relationship, the rows coming from either side can end up as a product join.
Suppose a customer has 3 sales fact rows and 2 campaign fact rows. The result set will have six rows before any aggregation is performed. That would mean that sales measures are doubled and campaign measures are tripled.
You can report on them together, using multiple SQL passes, but you can't query them together. Does that distinction make sense?

Injecting data into a star schema from a flat staging table

I'm trying to work out a best approach for getting data from a very flat staging table and then loading it into a star schema - I take a row from a table with for example 50 different attributes about a person and then load these into a host of different tables, including linking tables.
One of the attibutes in the staging table will be an instruction to either insert the person and their new data, or update a person and some component of their data or maybe even to terminate a persons records.
I plan to use PL/SQL but I'm not sure on the best approach.
The staging table data will be loaded every 10 minutes and will contain about 300 updates.
I'm not sure if I should just select the staging records into a cursor then insert into the various tables?
Has anyone got any working examples based on a similar experience?
I can provide a working example if required.

The database has some elements that make SQL a tad harder to use?
For example:
CREATE TABLE staging
(person_id NUMBER(10) NOT NULL ,
title VARCHAR2(15) NULL ,
initials VARCHAR2(5) NULL ,
forename VARCHAR2(30) NULL ,
middle_name VARCHAR2(30) NULL ,
surname VARCHAR2(50) NULL,
dial_number VARCHAR2(30) NULL,
Is_Contactable CHAR(1) NULL);
INSERT INTO staging
(person_id, title, initials, forename, middle_name, surname, dial_number)
VALUES ('12345', 'Mr', 'NULL', 'Joe', NULL, 'Bloggs', '0117512345','Y')
CREATE TABLE person
(person_id NUMBER(10) NOT NULL ,
title VARCHAR2(15) NULL ,
initials VARCHAR2(5) NULL ,
forename VARCHAR2(30) NULL ,
middle_name VARCHAR2(30) NULL ,
surname VARCHAR2(50) NULL);
CREATE UNIQUE INDEX XPKPerson ON Person
(Person_ID ASC);
ALTER TABLE Person
ADD CONSTRAINT XPKPerson PRIMARY KEY (Person_ID);
CREATE TABLE person_comm
(person_id NUMBER(10) NOT NULL ,
comm_type_id NUMBER(10) NOT NULL ,
comm_id NUMBER(10) NOT NULL );
CREATE UNIQUE INDEX XPKPerson_Comm ON Person_Comm
(Person_ID ASC,Comm_Type_ID ASC,Comm_ID ASC);
ALTER TABLE Person_Comm
ADD CONSTRAINT XPKPerson_Comm PRIMARY KEY (Person_ID,Comm_Type_ID,Comm_ID);
CREATE TABLE person_comm_preference
(person_id NUMBER(10) NOT NULL ,
comm_type_id NUMBER(10) NOT NULL
Is_Contactable CHAR(1) NULL);
CREATE UNIQUE INDEX XPKPerson_Comm_Preference ON Person_Comm_Preference
(Person_ID ASC,Comm_Type_ID ASC);
ALTER TABLE Person_Comm_Preference
ADD CONSTRAINT XPKPerson_Comm_Preference PRIMARY KEY (Person_ID,Comm_Type_ID);
CREATE TABLE comm_type
comm_type_id NUMBER(10) NOT NULL ,
NAME VARCHAR2(25) NULL ,
description VARCHAR2(100) NULL ,
comm_table_name VARCHAR2(50) NULL);
CREATE UNIQUE INDEX XPKComm_Type ON Comm_Type
(Comm_Type_ID ASC);
ALTER TABLE Comm_Type
ADD CONSTRAINT XPKComm_Type PRIMARY KEY (Comm_Type_ID);
insert into comm_type (comm_type_id, NAME, description, comm_table_name) values ('23456','HOME PHONE','Home Phone Number','PHONE');
CREATE TABLE phone
(phone_id NUMBER(10) NOT NULL ,
dial_number VARCHAR2(30) NULL);
Take the record from Staging then update:
'person'
'Person_Comm_Preference' Based on a comm_type of 'HOME_PHONE'
'person_comm' Derived from 'Person' and 'Person_Comm_Preference'
Then update 'Phone' with the number based on a link derived from 'Phone' which is made up of Person_Comm Primary_Key where 'Comm_ID' (part of that composite key)
relates to the Phone table Primary_Key which is Phone_ID.
Does you head hurt as much as mine?

Star schema in OBIEE 11G

Hi Experts,
Please tell me the places in OBIEE 11G where i can design the start schema.is it only in Physical Layer or In BBM too?
Thanks-Bhaskar

Final point, for performance reasons you should also try to model data into star schema in the physical layer.
If the data is modelled as a true star then there are database features which optimise query performance. These features are set by a DBA when the Warehouse is configured (e.g. enable_star_transformations). The results with this parameter on/off can be staggering (query time reduced from minutes to seconds), showing the power of star schema.
When snowflakes occur, these performance features will not work as designed, and performance will be degraded. There are certain criteria that have to be met by the data e.g. bitmap indices on all of the foreign key columns in the fact.
Please mark if helpful / correct,
Andy
www.project.eu.com

Resolving loops in a star schema with 5 fact tables and 6 dimension tables

Hello
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

Hi Patil,
It is not clear what exactly is the problem. As a starting point you could set the context up so that it only covers the joins from fact to dimension.
Fact A, joins Dim 1, Dim 2, Dim 3, and Dim 4
Fact B, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 5
Fact C, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 6
Fact D, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 7
Fact E, joins Dim 1, Dim 2, Dim 4 and Dim 6
If each of these are contexts are done and just cover the joins from fact to dim then you should be not get loops.
If you could lay out your joins like above then it may be possible to specify the contexts/aliases that should work.
Regards
Alan

Star Schema For OSA

Similar Messages

Maybe you are looking for