Extended Star Schema

analytics ,Ph: 9676622111

SAP Business Objects BI 4.0 1

Contents

1. Data Warehouse ............................................................................................................................................................. 2

2. Star Schema .................................................................................................................................................................... 5

3. Extended Star Schema .................................................................................................................................................... 7

4. OLTP Vs OLAP : .............................................................................................................................................................. 8

5. Business Intelligence Tools: .......................................................................................................................................... 10

6. ETL Tools: ...................................................................................................................................................................... 11

7. Types of Joins in Business Objects Universe ................................................................................................................. 12

8. SAP BOBJ - Business Object XI Architecture .................................................................................................................. 17

Client tier ......................................................................................................................................................................... 19

Intelligence tier ................................................................................................................................................................ 20

Processing tier ................................................................................................................................................................. 20

Data tier ........................................................................................................................................................................... 20

Application tier ................................................................................................................................................................ 21

9. SAP Business Objects 4.0 Connectivity for SAP Landscape ........................................................................................... 22



1. Data Warehouse



2. Star Schema



3. Extended Star Schema

The BW extended star schema differs from the basic star schema, in case of extended star schema, we will have Fact table

connected to the Dimension table and the Dimension table is connected to the SID table and SID table is connected to the

master data tables.

Fact Table and Dimension table will be inside the cube.

SID table and Master data tables are outside the cube.

One Fact table can get connected to 16 Dimension tables, one Dimension table can be assigned with maximum of 248 SID

tables (248 characteristics).

When we load Transaction data into InfoCube, System generates DIM ID based on the SIDs and uses the Dim IDs in the Fact

Table.

Each Characteristic can have its own master data tables (ATTR, TEXT, HIER). Attribute Table is used to store all the attribute

data, Text table is used to store the description in multiple languages, Hier table is used to store the Parent-Child data.

Fact Table

Fact Table will have Dimension IDs and Key figures.

Maximum DIM IDs 16

Maximum KeyFigure 233

The Dimension IDs in the Fact Table is connected to the Dimension Table.

Fact Table must have at least one Dimension ID.

Dimension Table

Dimension Table contains Dimension ID and SID columns.

One column is used for Dimension ID.

We have maximum of 248 SID Columns.

We can assign maximum of 248 characteristics to one dimension.



4. OLTP Vs OLAP :

OLTP (On-line Transaction Processing) is characterized by a large number of short on-line transactions (INSERT, UPDATE, DELETE).

The main emphasis for OLTP systems is put on very fast query processing, maintaining data integrity in multi-access environments and an

effectiveness measured by number of transactions per second. In OLTP database there is detailed and current data, and schema used to

store transactional databases is the entity model (usually 3NF).

OLAP (On-line Analytical Processing) is characterized by relatively low volume of transactions. Queries are often very complex and

involve aggregations. For OLAP systems a response time is an effectiveness measure. OLAP applications are widely used by Data Mining

techniques. In OLAP database there is aggregated, historical data, stored in multi-dimensional schemas (usually star schema).



5. Business Intelligence Tools:



6. ETL Tools:



7. Types of Joins in Business Objects Universe

In Previous post we have covered cardinalities in BO universe. In this post we would be learning types of join in SAP Business Objects

Universe and how to set up joins.

Following join types are available in Business Objects Universe Designer which can be used to join two tables.

Equi-Join

Equi-join is join which uses = equal operator to join two tables. Generally equi join is used to join primary table using primary key with

foreign tale using foreign key

When two tables are used using equi-join it returns all those rows from selected table which matches the equality condition.

Outer Join

Outer join links two tables using a join operator. When tables are linked using outer joins the select query returns all the records which

matches the join condition and returns all the records from one table even though do not match the join condition.

There are two types of outer join

Left Outer join: This outer join returns all the records from left table even when they do match the join condition.

Right Outer join: This outer join returns all the records from right table even when they do match the join condition.



You should avoid using outer joins as it may cause query to run slower. Outer joins should be placed at the end of a join path otherwise it

maybe causes other queries to match a NULL equality condition which might give an error.

Theta Join

A theta join is a between-type join thats joins tables based on a relationship other than between two columns. It is generally used to

demonstrate ranges. A theta join can use any operator other than equality operator.

Lets see how to create a theta join



1. From Insert menu click on join to create a new join

2. Select the table1 which should be joined to another table using between operator.

3. Select the table2

4. Now select the two columns from table two which should represent the range.

5. Set the cardinality to N-1

6. Click Ok

This theta joins uses between operators to join two tables



Shortcut Join

A shortcut join is a join which provides shorter way to join two tables by avoiding intermediate tables between join paths of tables. It is very

helpful to improve the performance of a query as it reduces number of joins in a query.

Shortcut joins are also useful to solve loops in a Universe.

Lets take an example of Shortcut join.

Shop_facts, Article_lookup and product promotion facts are joined through Article id. Now if we want to see Duration and amount sold the

query will have un-necessary join of shop_fact and Article_lookup table as there is no join between shop_facts and product_promotion_fact.

However if we join shop_facts and product_promotion_fact, it will create a circular loop which might confuse universe to decide on which

join path to take. This can be avoided by using shortcut join instead of using normal join. Shortcut join is represented by dotted line in

designer.

Self Restricting Join

Self restricting join is not actually a join but a restriction on a table. Generally it is used to restrict the data returned by a table.

To create a self restricting join

1. Click on Insert menu and click on join to create new join

2. Select the table on which you want to create self restricting join.

3. Select the same table name from table 2 combo box also.

4. Select the column which should be used for self-restricting join.

5. Edit the expression and put the restriction condition

6. Click OK.



Cardinality of self restricting join should be set to 1:1 otherwise it gives error while detecting contexts.

Try to create each type of join in BO universe and practice it and test it using Query Panel.



8. SAP BOBJ - Business Object XI Architecture



Architecture overview / basics

BusinessObjects XI is a multitier, server-based product that comprises a number of logical servers. These servers run as Windows services, and they

can all be installed on one machine or distributed across multiple machines, each running multiple processors as your needs demand.

The BusinessObjects Enterprise technical architecture is composed of a set of tiers optimized for specific tasks and operations. The five tiers are:

1. Client tier: web browser and rich clients.

2. Intelligence tier: system server processes.

3. Processing tier: data analysis and report generation.

4. Data tier: source repositories.

5. Application tier: Java web application servers and tools.

Developers can access the platform using a set of web services and Java APIs to integrate BusinessObjects Enterprise into other enterprise systems,

and to share dynamically updated documents with users on separate networks.

End users can access, create, edit, and interact with reports using specialized tools and applications that include:

1. Crystal Reports.

2. SAP BO - Web Intelligence.

3. Desktop Intelligence.

4. Voyager.

5. Dashboard and Analytics.

6. Dashboard Builder.

IT departments can use data and system management tools that include:

1. SAP BOBJ - Central Management Console (CMC).

2. SAP BO - Central Configuration Manager (CCM).

3. Import Wizard.

4. SAP BOBJ - Publishing Wizard.

5. Business Object - Universe Designer.

6. Repository Diagnostic Tool (RDT).



Articles Related

1. SAP Business Object

Server

You can manage the various servers that comprise a BO XI installation by selecting the Servers option from the main menu of the CMC More ...

Client tier

Two application categories are available in the client tier:

operating system independent web applications that run in web browsers, like Internet Explorer, Firefox, or Safari. Examples of this type of

application include the :

SAP BO - InfoView,

SAP BO - Web Intelligence,

SAP BOBJ - Central Management Console (CMC) (CMC),

Report viewers,

Dashboard and Analytics,

Voyager,

Xcelsius,

BusinessObjects Mobile.

and rich desktop applications installed on a Microsoft Windows operating system. This approach allows you to offload BI processing from

BusinessObjects Enterprise onto individual client computers. Most desktop applications directly access your organization's data through

middleware drivers installed on the desktop, and communicate with your BusinessObjects Enterprise deployment through CORBA or

encrypted CORBA SSL. Examples of this type of application include :

Crystal Reports,

Desktop Intelligence,

Live Office

Business Views Manager

SAP BO - Central Configuration Manager (CCM) (CCM)

Data Source Migration Wizard

Repository Diagnostic Tool (RDT)

Import Wizard

SAP BOBJ - Publishing Wizard



SAP BO - Query as a Web Service

Report Conversion Tool

Translation Manager

Universe Builder

Business Object - Universe Designer

SAP BO - Web Intelligence rich client

Intelligence tier

The Intelligence tier manages the BusinessObjects Enterprise system. It maintains all of the security information, sends requests to the appropriate

servers, manages audit information, and stores report instances. This tier contains the following components:

Central Management Server (CMS) (CMS).

Event Server.

SAP BOBJ - File Repository Servers (FRS) (FRS).

SAP BOBJ - Cache servers instances.

Processing tier

The BusinessObjects Enterprise processing tier accesses the data tier and generates reports for clients. It is the only tier that directly interacts with the

reporting database.

The processing tier includes the following server types.

Job servers

Report and Processing servers

Crystal Reports page server

Multi-Dimensional Analysis Server (MDAS) (MDAS)

Dashboard and Analytics

Data tier

The Data tier is made up of the data sources that contain the information used in the reports and documents managed by your BusinessObjects

Enterprise XI system, which supports a wide range of corporate databases.



Semantic layers

The Business Objects semantic layer is a platform-unspecific layer of abstraction that lies between BusinessObjects Enterprise and the raw source

data contained with a reporting database.

SAP BOBJ - Universe

Business Views

Connection Server

The Connection Server provides database access to the raw source data.

Application tier

The application tier acts as the translation layer between :

the end user and

the processing tier.

A third-party BOBJ - Web application servers hosts Java SDK modules to process requests from the user tier, then communicates those requests to

the appropriate service in BusinessObjects Enterprise.

The web and application services tier communicate with the following BusinessObjects Enterprise :

The BusinessObjects Enterprise SAP BOBJ - Software development kit (SDK).

BusinessObjects Enterprise BusinessObjects Web Services.



9. SAP Business Objects 4.0 Connectivity for SAP Landscape

Documents

Extended Star Schema