bw doubt

[Former Member]

Hello Experts,

I am familiar with ODS structure concept. But not as clear for cubes. How is key concept applied to cubes.

I know fact table has dimension ids. But can I say also that each characteristic is a key to fact table?

Hope you could help clarify a little.

Thanks,

Shankell

[former_member181964]

Hi,

Infocube is having Fact table and sourrounded by Dimension tables.

The relation between Fact table, DImension table and SID table is.....

Customer Price Qty.

Eg: C100 100 2

Assume that you want to store above data in Infocube.

First you need to load Master data of Customer,then you need to load Transactional data.

Whenever you load master data at that time SID's will be genarated in SID table, in SID table it store like

SID_100 C100

Whenever you load Transactionla data at that time Dimensional Id's will be genarated like...DIM_100.

So in Dimenstion table the data is like

DIM_100 SID_100

So dimensional table will store DIM Id and SID.

Fact table will store Dimensional Id and Key figure like..

DIM_100 100 2

So like this there is a Primary forgin key relation.At the time of reporting it use the referance and dispy the

customer information.

Thanks

Reddy

[Former Member]

Shankell,

Dimids form the key in the infocube fact table.

An InfoCube fact table only contains key figures, in contrast to an ODS object, whose data part can also contain characteristics. The characteristics of an InfoCube are stored in its dimensions.

The dimensions and the fact table are linked to one another via abstract identification numbers (dimension IDs), which are in the key part of the particular database table. As a result, the key figures of the InfoCube relate to the characteristics of the dimension.

-Doodle

[Former Member]

Hello

Infocube (Multi Dimensional Modelling):-

(Extended STAR Schema or BW STAR Schema)

Technical Name : 3 to 9 Characters

No of Dimensions : 3 SAP Delivered + 13 User Defined = 16

Minimum no of DIM : 3 SAP Delivered + 1 User Defined = 4

For storing Transactional Data.

Has 2 Fact Tables (E & F), normally we use F fact table; after compression it reaches the E fact table.

F Fact table contains Keys for DIM table & Facts ( Key Figures)

For every Characteristics in the Dim Table it creates a SID table which links to the Master Data Tables(Texts, Attributes & Hierarchies)

Here in the Fact table DIM ID s are maintained

in the Dim table DIM IDs & SID s are maintained

in the SID table SID & CH-IO s (EMPNO) are maintained

So master data is maintained seperately, not in the Dim tables like STAR Schema. The extended part is the SID tables and the Master Data tables), thats y it is termed as Extended star schema.

Finally the Master Data tables are Attributes, Texts and Hierarchies.

Attributes like EMPNAME, EMPDESIG etc...

Texts olangu, 0txtsh,....

Hierarchies.....

Hope this will give some idea....

Best Regards....

Sankar Kumar

91 98403 47141

[Former Member]

Hi,

The Infocube (fact table ) contains kFig's and Dim id's and dims id's contains dim id's and sid's .. sid's exist betw the master data tables and dim tables...

so the char of cube stored in the corresponding dim's..

The grouping of classification groups (characteristics) whose content is logically connected, under a single generic term. If the dimension contains a characteristic whose value already uniquely determines the values of all other characteristics from a business-orientated viewpoint, then the dimension is named after this characteristic.

The customer dimension could, for example, be made up of the customer number, the customer group and the levels of the customer hierarchy.

The sales dimension could contain the characteristics ‘sales person’, ‘sales group’ and ‘sales office’.

The time dimension could be given using the characteristics ‘day’ (in the form YYYYMMDD), ‘week’ (in the form YYYY.WW), ‘month’ (in the form YYYY.MM), ‘year’ (in the form YYYY) and ‘period’ (in the form YYYY.PPP).

When defining an InfoCube, characteristics for dimensions are grouped together to enable them to be stored in a star schema table (dimension table). The aforementioned business-orientated grouping can be the basis for this. With the aid of a simple foreign key dependency, dimensions are linked to one of the key fields of the fact table.

Also refer to Star Schema.

Structure

From a technical viewpoint several characteristic values are mapped to an abstract dimension key (DIM ID), to which the values in the fact table refer. The characteristics chosen for an InfoCube are divided up among InfoCube-specific dimensions when creating the InfoCube.

Also refer to the following for specific cases arising when defining dimensions:

-Shreya