Académique Documents
Professionnel Documents
Culture Documents
SAP software by default has two clients 000 (SAP client) and 066, and if we find
any other client like 100 it is a copy of 000 client and it becomes active client.
In SAP BW we can have only one active client at any given point of time.
In SAP R/3 we can have multiple active clients which are a copy of 000.
In SAP R/3 we have client dependent and independent tables where as in SAP BW we have
only client independent tables.
Types of Applications:
1. OLTP: On-Line Transaction Processing
a. It is used to record transactions.
b. OLTP record a transaction into data base or modify a transaction in data base
and on doing reporting they extract data from data base and display the report.
c. Master Data + Application is Transaction Data.
d. Ex: SAP r/3.
1
Master Data:
It is the detailed information of an entity which refers to the data that remains unchanged
over an extended period of time.
Transaction Data:
This is the data used to represent the transactions in business process. Transaction Data
are the business transactions taken from specific data that are assigned to certain master
data.
When two or more entities interact with each other they form a transaction.
Entity:
Entity is an object which can perform work by itself or which can be used to perform some
other work.
SAP Products:
ENTERPRISE PORTALS SAP CRM SD + BW
OLAP SYSTEM
SAP SEM
FICO + BW
SAP CRM: Consumer Relationship Management.
Holds detailed information about customers.
CRM server is called as CRMONLINE.
CRM is used for retaining customer.
1. Internet sales ecommerce.
2. Mobile sales
Service
3. Call center .
CRM + ABAP + ORACLE/DB2 + UNIX/WINDOWS + TO RETAIN EXISTING COLUMNS.
2
Enterprise Portal:
This is used this application to post data/reports. It works as a single sign on location to
access any of the data (reports) from any of the modules.
SAP Netweaver is not a single product but it is a suit of multiple products.
SAP NETWEAVER
PEOPLE INTEGRATION
MULTIPLE CHANNELS -
ENTERPRISE PORTAL
ACCESS PORTALS
INFORMATION -
INTEGRATION
1. BI.
2. KNOWLEDGE
BI
MANAGEMENT.
3. MASTER DATA
MANAGEMENT.
PROCESS INTEGRATION.
KNOWLEDGE MANAGEMENT
APPLICATION PLATFORM
LAYER.
J2EE, ABAP. OLTP SYSTEM
Web Reports:
These can be published on the web as well as enterprise portal.
BW Versions:
BW 2.0, 2.1c, 3.0, 3.1, 3.5, BI 7.0.
Business Intelligence (BI 7.0) is a part of netweaver.
Using MDM (Master Data Management) all the master data in one application will
be referred when ever required.
3
PRESENTATION LAYER + DATA BASE + OPERATING SYSTEM + CONCEPT
ABAP + DATA BASE + UNIX/WINDOWS +DATA WAREHOUSE
Business Intelligence:
This concept is given by a management consulting group Gartner Group.
The main concept of BI is to have all the historical data for taking the decision.
The father of Data Warehouse is William Henry Imman.
Historical Data BI
Decision DSS
making process
DW
Fact Based
System
Facts
4
Main concept of BI is to have all historical data for taking the decision or extracting data
from different heterogeneous source system to generate reports using
multidimensional methods which can be used for decision support system.
2. Integrated (I):
We should be able to integrate the data coming from any heterogeneous OLTP
system.
3. Non-Volatile(N):
Should be fast, not changeable and the date should be fixed.
Data Warehouse:
Cognos Only for reporting
Informatica ETL tool
BO reporting
Oracle & DW Staging
SAP BW Has got end to end data warehouse solutions like modeling,
extraction and reporting.
5
Modeling Concept
Database design in OLTP and OLAP:
In any database we store the data in the form of tables.
Tables:
A table is a collection of rows and columns. All the columns of the table define the logical
definition of an entity. Rows can also be called as a record. Each row or record defines a
physical existence of an entity.
Primary Key:
Every table must have a primary key. Primary key is a column with which we can
identify a record uniquely in the table.
2. Non Key column: Any key that is not a part of a primary key.
All our non key columns of the tables are attributes/properties of key column (primary key).
Primary key/Key column non key column & also attributes of key column
6
In every bill item no cannot be duplicated. In this table we don’t have a single column as a
primary key so here we have combination of columns.
Here BILL NO + ITEM NO are the Primary Key.
When multiple columns are acting as a primary key then that key is called Composite key.
Denormalized table
When all the information is stored in one table then that table is called Denormalized table.
The problem with this table is data redundancy (repetitive values), complexity will be increased
and wastage of storage space.
So in order to overcome we can serve the information in two different tables.
When primary key of one table takes part in another table then the key is called Foreign Key.
Normalized Table:
The table without redundant data is called Normalized Table.
To over come the problem with denormalized table we split the data in one table into different
small normalized multiple tables and connect them with primary key and foreign key.
7
Database design in OLTP system:
It is two dimensional (row-column).
This is implemented with the concept of ERM (Entity Relationship Management).
MATERIAL SALES
GROUP DEPARTMENT
CUSTOMER
SALES
TRANSACTION
Intersection Entity
When entities are trying to interact with each other (to perform a transaction)
we need to know the relationship between the entities.
8
Product Sales
9
2. i. Find out relationship between key column and non-key column.
CREGI CNO
Indicates that the customer region and customer no has one to many relationship
in between them.
Date redundancy is possible because of one to many relationship i.e. multiple data can be
stored in a column.
Since the CREGI has one to many relationship with CNO (i.e. in one region there can be ‘n’
number of customers), so the column CREGI data can be split into another table as below.
Here the data in column CREGI is stored in numeric because the processing speed of
numeric is faster than alphanumeric.
ii.
CADDR CNO
Customer address and customer number has one to many relationship like that of
customer region.
10
iii.
CNAME CNO
Each customer has a unique name with that of a customer number, so duplication of data
is not possible in it and thus there is no need to split the table.
If there is one to many relationship between key column and non key column we
should split into two tables and connect them with primary key and foreign key
relationship.
If there is one to one relationship between key column and non key column there
is no need to split into different tables.
If there is many to many relationship between key column and non key column
we should split into two tables and connect them with primary key and foreign
key relationship.
2. Stronger entity:
Any tables which are directly connected to intersection entity table with the help of
primary key and foreign key relationship.
11
2. External star schema or BW star schema.
3. Snow flake.
4. Hybrid.
Transaction table:
It stores all the transaction data.
Dimension tables:
The same master data tables are acting as a side of a cube these are called as
dimension tables.
Fact table:
Records in it are cannot be changed but we can add records.
In fact tables there are 2 types of columns exits:
1. Characteristics :
On what basis we are analyzing the key figures becomes characteristics.
Ex: Analyze the revenue based on customer here revenue is the key figure and
customer is the characteristics.
2. Key figures :
These are the quantitative measures, these are nothing but what we are going to
analyze.
Fact table:
C1 M1 S1 4 2 8
C2 M1 S1 6 4 24
C1 M1 S2 3 5 15
C2 M1 S2 6 4 24
Intersection entity
12
SID REVENUE
SID table:
Every master table will have its own SID table.
SID table is also outside the cube like master data table.
For every record in the master data table it generates an SID in the SID table
automatically.
SID-CID is always numeric. By implementing SID table we can improve the
performance.
Dimension table:
To increase the analysis, instead of SID tables dimension tables are placed in the
cube, which acts as a mediator between SID tables and Fact tables.
When loading transaction data into cube it generates Dimension ID (Data taken
from OLTP system).
Only one dimension ID is created for each entity from the master data table.
We can connect 248 master data tables to one dimension table.
Maximum number of columns in any table is 255.
Out of 255 columns 6 columns are used for internal purpose of the cube and
one column is left for dimension key and the remaining is 248 columns.
Therefore a fact table can have 16 dimension tables and each dimension
tables can have 248 SID tables.
Maximum number of master data tables we can have for a fact table is
16x248.
13
Primary Key Primary Key
1 C1 3 M1
2 records
2 C2 3 records 4 M2
5 M3
Customer SID Table
Material SID Table
9 1 11 3
2 records
10 2 3 records 12 4
13 5
Dimension Table
9 11 5 10 50
Total
9 12 6 10 60
5
10 11 7 7 49
records
FACT TABLE
INFOCUBE
Here all the data in fact table are in numeric, so this extended star schema has better
performance.
14
Here Customer master data table consists of 2 records as well as its SID because for
every record entered in master data table a SID is generated. Where as Material master data
table consists of 3 records as well as its SID.
Therefore the maximum number of records in each dimension table consists as many as
its respective master data records.
Here the fact table consists of 16 characteristics and each characteristic has a
dimensional table. Therefore there are 16 dimensional tables in an info-cube. Each
dimensional consists of SID table and those SID tables consists of master data tables.
We still have a limited analysis of 16 inorder to improve the analysis we can make one
dimension table for all SID tables as shown below:
C1 ABC HYD M1 A
2 records
3 records M2 B
C2 XYZ BAN
M3 C
Customer master data table Material master data table
1 C1 3 M1
2 records 4 M2
2 C2 3 records
5 M3
DI SID_CID SID_MID
Total 6 records
DIMENSION TABLE
DI P Q REVENUE
FACT TABLE
INFOCUBE
15
In order to design optimized info-cube we have to concentrate on reducing the
number of dimension tables in a cube and at the same time we should also reduce
the number of records in a dimension table.
If two master data tables have many to many relationships then it is preferred to
have two dimension tables in order to reduce the number of records.
If the two master data tables have one to many relationships then it is preferred to
have one dimensional table.
16