Do we use direct star schema concept anywhere in sap bw

i know about extended star schema,and where sap uses this concept.
my question is do we use normal star schema concept any where in sap bw, apart from extended star schema concept.
if yes specify the answer briefly .
thanks in advance
with regards
yash.b

Hi,
If I'm not mistaken an Analytic view in Hana is more like the normal star schema, it is definitely not extended and can be consumed by BW for OLAP processing.
Regards,
Michael Devine

Similar Messages

Master data sharing using ext. star schema

Hi,
I have undetrstood the concept of extended star schema.
I understand,
One of the advantages of extended star schema is, that the master data can be shared, meaning, since the master data is stored separately, other star schema's can also share this master data provided it is of the same relevance( with same infoobjects used in this star schema).
Confirm if my understanding is right and if right,
Any idea or suggestion how to demonstrate this ?
Points will be given for good answers.
thanks.
bwlearner

Hey,
If u could map this with programming.
MASTER DATA Tables are like GLOBAL declaration and InfoCubes (Fact Tables) are like LOCAL declaration. Any number of IncoCubes can access one particular Master Data Table.
Assume Sales data coming from 5 regions. Here 0CUSTOMER & its attributes will update the same Master Data Table. The data fields will be stored in the Infocube. So all the 5 InfoCubes access the same Master Data tables using the Dimension & SID tables.
Clear ?
Best Regards....
Sankar Kumar
+91 98403 47141

Show Star Schema of Cube in SAP BW

Hello experts,
is ist possible in SAP BW to show the star schema of a Cube?
Thanx
Axel

Hi ,
Goto RSA1 -> in the left side you will find tabs like Modeling, Monitor etc, the last tab is meta data repository -> click it -> right side it will display the screen -> here select info cube it displays active cubes in your system find your info cube here under graphical display you will get 3 options select display as star schema.

Understanding Star Schema Operations

Hi All,
I worked on Oracle Answers and have knowledge on Data Warehousing concepts. I have enough oracle documentation on OLAP, OBIEE, Data Warehousing.
But i 'm not able to understand the star schema concepts in and out. I'm lost on all documents, where i'm getting the simple answer on the following topics:
1. Is it necessary to create dimensions using CREATE DIMENTION or it can be a simple relational table structure with CREATE TABLE statement?
2. What will be the steps to create a very basic/simple star schema using DML statements not using any tool?
3. Where I can get very basic level step by step tutorial to create a very simple star schema by sql -> loading test data by sql commands -> then what queries we can use to get BI reports or using OBIEE to create a simple rpd.
Please give me some idea on this as I have to create a small OBIEE repository where i have to do create the warehouse and ETL process, everything.
Pls advise.
Thanks in Advance.
Sudipta

No my question was on creating the star schema. If i have to create a very simple star schema then can I create the star schema with the following relational tables?
create table dim_products (
product_id number primary key,
product_name varchar2(32),
brand varchar2(32),
category_name varchar(32),
sub_category_name varchar2(32)
create table dim_time (
time_id number primary key,
selling_date date,
selling_day number(2),
selling_month varchar2(12),
selling_Quarter varchar2(6),
year number(4)
create table dim_region (
region_id number primary key,
store_name varchar2(32),
city_name varchar2(32),
state_name varchar2(32),
country_name varchar2(32),
region_name varchar2(32)
create table fact_sales (
sale_id number primary key,
region_id number ,
time_id number ,
product_id number ,
unit_sold number,
constraint fact_sales1 foreign key (region_id) references dim_region (region_id),
constraint fact_sales2 foreign key (time_id) references dim_time (time_id),
constraint fact_sales3 foreign key (product_id) references dim_products (product_id)
Or I have to create the DIMENSIONS explicitly, in order to building the hierarchy levels?
Regards
Sudipta

Star Schema and EUL

1. It's a prerequisite to use a star schema to build a EUL or I can/ must used a Relational Schema?
2. The OLAP Option of Discoverer Plus work with an EUL or with a star schema
3. Which components requiere the OLAP option that don't require the Relational Option (i.e. AW) ?
4 I can generate a star schema as: a) a simple relational model where the FK key is a common domain for the fact and dimension table (i.e. Dept. Number) and having a table for each dimension (I don't speaking about time dimensions, but fields like barnch, dept., etc,). b) a star schema where the dimensions are grouped in tables depending on its significance (i.e. Producto, Channels, Time, etc). In this case I'll use a auto-generated sequential number as key for each table record, wich is referenced in the fact table. The question is, which is, in general, the best strategy 1.a ot 1.b. It depends of the size of the database?
5. There is two bussines areas wich need the same information, but one of them, will used always a summarized version whit 60000 records (the other one will process more than 1000000 each time). No doubts in using two distincts set of tables to generate two distincts EULs or Star Schemas, in order to gain in performance?

This is a more suitable question for the Business Intelligence (EBS).
In the mean time, you may want to check the BI OBE: http://www.oracle.com/technology/obe/obe_bi/bi.html , as well as http://www.oracle.com/technology/products/bi/index.html, http://www.oracle.com/technology/documentation/bi_doc.html
~ Madrid.

Unable to run a star schema in HFM. Error message below.

We are currently unable to run an existing star schema in our HFM 9.3.3 application. This has never caused an issue in the past and is causing a disruption in our montly close process.
Any assitance would be greatly appreciated!
I've attempted to delete the Star Schema but still receive same error message.
Error message below:
Thank you,
Brian Riedel
==================================================================================================================
8/1/2012 1:34:24 PM : Status : Extracting Metadata
Metadata update has failed. : (-2147220903) (Attention: One or more processes are currently using the Star Schema specified by the DSN and Prefix. You must wait until all other processing is completed before attempting to create the specified Star Schema.)
Processing status change: (-2147220903)
Data processing failed. : (-2147220903) (Attention: One or more processes are currently using the Star Schema specified by the DSN and Prefix. You must wait until all other processing is completed before attempting to create the specified Star Schema.)
8/1/2012 1:34:24 PM : Status : Processing completed with errors
Extended Analytics export completed with errors for Application BSCPROD using Label PL. Error code is:

The message means another process has a lock on the EA tables, so you have to wait until that processis complete before proceeding. This could happen if you are trying to execute more than 1 concurrent EA exports.
--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?

Error with creating star schema using HsvStarSchemaACM

Hi,
I am trying to create a star schema using the API HsvStarSchemaACM. But when calling the create function of API, i get the below exception. Exception from HRESULT: 0x80040251 (A general error occurred while trying to obtain a database Reader/Writer lock). Is this something to do with the parameters passed and its connections(connection works fine and createstarschema is running thru workspace).
Any solutions to this is more welcome.
Thanks,
Logu

Can you provide details on HsvStarSchemaACM API? How is it related to ODI?

Wat is the use of sid in extended star schema rather than linking masterdat

hi bw gurus,
wat is the use of sid in extended star schema rather than linking masterdata with dimention tables?
thanx in advace,
i will assign points,
srinivas

hi,
the sid are used instead of the data in order to avoid the redunduncy of data.
and reduce the datastorage size.
the data will be present in the sid table and the data is linked used the corerponding sid in the dimension.
regards

Star Schema Using OWB 10g

Hello,
I would like to know whether is it possible to build a star schema using Oracle OWB 10g?
If so how could I do build one? Any help is highly appreciable.
Regards

Hi ,
You can use Oracle SQL Developer Data Modeler .
SQL Developer Data Modeler provides a full spectrum of data and database modeling tools and utilities, including modeling for Entity Relationship Diagrams (ERD), Relational (database design), Data Type and Multi-dimensional modeling, full forward and reverse engineering and DDL code generation. The Data Modeler imports from and exports to a variety of sources and targets, provides a variety of formatting options and validates the models through a predefined set of design rules.
Oracle SQL Developer Data Modeler can connect to any supported Oracle Database and is platform independent
http://www.oracle.com/technology/products/database/datamodeler/index.html
Thanks,
Sutirtha

How to join 2 star schemas using a Dimensional table( like Bridge Table)

How to join 2 star schemas using a Dimensional table( like Bridge Table) in OBIEE?

Complex joins and Content levels is all you need, have you tried the forum search?

Why is EA Star Schema used ?

Hello,
I have a simple question on why the Star Schema is used ? Getting an answer from Wiki is not what I wanted , some response from the Gurus would be great to hear. Every time when there is a Metadata Update in HFM during Monthly Change and Maintenance a New Star Schema should be created and only then I run the Dimension Update Job in Essbase, what is the real reason for that. If you say that it Updates the New Dimension changes in HFM to Essbase , then for that we already have an EAL taking care of Updating the Essbase Metadata in Tandem with HFM.
Any comments.
Thanks !!

I was on a Extended Analytics project in 2008. There was no EAL. EA was it.
Regards,
Cameron Lackpour
P.S. Thankfully, I can't remember the functionality other than it was like being cooked, slowly, over a roaring fire.
Edited by: CL on Jan 9, 2013 3:42 PM

Question on BW Star Schema

Hello all
Please help me understand the DIM/SID table concept.
I was going through the BW star schema and I was curious to know the importance of Dimension table. What is wrong with putting the SID ID directly in Fact table instead of relating it through the DIM table?
Please post a link to documentation on SAP Star Schema, if you have.
This is how I understood
Fact Table:
DIM_CUST     | QUANTITY
001          | 50
002          | 100
001          | 60
Dimension Table:
DIM_CUST     | SID_CUST
001          | 011
002          | 022
003          | 033
SID Table:
SID_CUST     | CUST_ID
011          | 123ABC
022          | 767TYT
033          | 989UHY
- In Fact table we identify unique transaction by combination of Cust ID and Date/time
- We can have the same Cust ID appearing multiple times in Fact table for different transactions
- DIM and SID table have 1:1 relation
- In SID table, SID ID has 1:1 relation with a customer ID
If they are all right, I still want to know why can't we have SID ID appear directly in Fact table?
Please explain.
Thanks
-Sudhakar
Message was edited by: Sudhakar Upadhyaya
Message was edited by: Sudhakar Upadhyaya

About you last question:
"Can anyone give me a scenario where we use multiple characteristic in the same domension?"
The first consideration about the number of characteristic involved is the most evident, but consider even the problem related with the number of key fields of a DB Table (no more than 16).
Speaking about a scenario: let's say you have to report on Division, Sales Org, Sales Off, and Sales Pers: putting all this char in a "line item" dimension makes sense only in order to elimiate the corresponding Dimesion Table, but are you sure that the query will be faster that putting all of the in the same Dimension? And what about the comprehension of the underlying schema? Think about a complex one, with 50 or more Chars ...
By the way the easier way to solve such a doubts is to read something about MultiDimensional Data Modeling: there's a wide litterature about this topic that can't be summarized in few rows without omitting important notes
If you don't want to start with "heavy" books search in http://service.sap.com/bw for a doc about Multidimensional Data Modeling (see under InfoIndex / DataModeling / BW ASAP for 2.0B Phase 2: Multi Dimensional Data modeling (doc)) that's an old doc (before 2k), but a very good starting point, that will answer to you questons about SidID and DimID.
Hope it helps
GFV

Why do we need SSIS and star schema of Data Warehouse?

If SSAS in MOLAP mode stores data, what is the application of SSIS and why do we need a Data Warehouse and the ETL process of SSIS?
I have a SQL Server OLTP database. I am using SSIS to transfer my SQL Server data from OLTP database to a Data Warehouse database that contains fact and dimension tables.
After that I want to create cubes using SSAS form Data Warehouse data.
I know that MOLAP stores data. Do I need any Data warehouse with Fact and Dimension tables?
Is not it better to avoid creating Data warehouse and create cubes directly from OLTP database?

Another thing to note is data stored in transactional system may not always be in end user consumable format for ex. we may use bit fields/flags to represent some details in OLTP as storage required ius minimum but presenting them as is would not make any
sense to user as they would not know what each bit value represents. In such cases we apply some transformations and convert data into useful information for users to understand. This is also in the warehouse so that information in warehouse can directly be
used for reporting. Also in many cases the report will merge data from multiple source systems so merging it on the fly in report would be tedious and would have hit on report server. In comparison bringing them onto common layer (warehouse) and prebuilding
aggregates would be benefitial for the report performance.
I think (not sure) we join tables in SSAS queries and calculate aggregations in it.
I think SSAS stores these values and joined tables and we do not need to evaluates those values again and this behavior is like a Data Warehouse.
Is not it?
So if I do not need historical data, Can I avoid creating Data Warehouse?
On the backend SSAS uses queries only to extract the data
B/w I was not explaining on SSAS. I was explaining on what happens inside datawarehouse which is a relational database by itself. SSAS is used to built cube (OLAP structures) on top of datawarehouse. star schema is easier for defining relationships
and buidling aggregations inside SSAS as its simple and requires minimal lookups to be performed. Also data would be held at lowest granularity level which can easily be aggregated to required levels inside OLAP cubes. Cube processing is very resource
intensive and using OLTP system would really have a huge impact on processing performance as its nnot denormalized and also doing tranformation etc on the fly adds up to complexity. Precreating a layer (data warehouse) having data in required format would
make cube processing easier and simpler as it has to just cross join tables and aggregate data based on relationships defined and level needed inside the cube.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Star schema without a fact table?

Hi,
I'm preparing my warehouse for using with Discoverer and my question is about the star schema.
- Is a star schema directly associated with data warehouse?
- Can I talk about a star schema if a) I do not have a fact table (no summarized values) and b) if I do not have a dimension of time?
The problem is, I'm thinking of usine Discoverer but should I use it if it's not connected to a data warehouse?
As I told, I'd like to modelized my data "like" a star schema but my "center table" will contain only the foreign key of my dimensions; no time dimensions, no aggregate data in the center table (fact table).
Is there another word for the model I'd like to do?
Thank in advance.

Hi,
Is a star schema directly associated with data warehouse?Not really, a star schema is just one where there is one large fact table joined to many smaller dimension tables using key fields. You usually see this in data warehouses.
Can I talk about a star schema if a) I do not have a fact table (no summarized values) and b) if I do not have a dimension of time?A star schema must have a fact table but it doesn't need contain summarised values or a time dimension.
You can use Discoverer with any Oracle database, it doesn't have to be a data warehouse.
Rod West

Do we use direct star schema concept anywhere in sap bw

Similar Messages

Maybe you are looking for