Evolution of SAP BW

Evolution of SAP Business Information Warehouse

A Quick Look at SAP R/3 Architecture and Technologies
Founded in 1972 in Mannheim, Germany, as Systemanalyse und
Programmen-twicklung to produce and market standard software for
integrated business solutions, today that company is known as SAP
(Systems, Applications and Products in Data Processing),
headquartered in Walldorf, Germany. SAP built packaged
applications for mainframe computers, called SAP R/2. As the
client/server technologies emerged in the early 1980s, SAP launched
a major initiative to engineer powerful three-tiered integrated
business applications under one framework. The SAP R/3 product is
the outcome of that initiative.
Note Often, people ask what R/2 and R/3 mean. The letter R stands
for real-time, and 2 and 3 represent two-tiered and three-tiered
architectures, respectively. SAP R/2 is for mainframes only, whereas
SAP R/3 is three-tiered implementation using client/server
technology for a wide range of platforms-hardware and software.
When implementing a Web front-end to an SAP R/3 implementation,
the three-tiered architecture becomes multi-tiered depending on how
the Web
server is configured against the database server or how the Web
server Itself distributes the
transaction and presentation logic.
Evolution of sapbw
 All SAP R/3 business applications use an active dictionary to store all business rules defined to run
business. These business and workflow rules keep information flowing among application modules in a
controlled and secured fashion. The "ABAP Workbench" is used to develop business programs using the
Advanced Business Application Programming (ABAP) language. The Basis technology is responsible for
managing R/3 infrastructure such as software installation, operations, and administration.
 SAP R/3's multi-tiered architecture enables its customers to deploy R/3 with or without an application
server. Common three-tiered architecture consists of the following three layers:
 • Data Management
• Application Logic
• Presentation
 The Data Management layer manages data storage, the Application layer performs business logic, and
the Presentation layer presents information to the end user.
 Most often, the Data Management and Application Logic layers are implemented on one machine,
whereas workstations are used for presentation functions. This two-tiered application model is suited best
for small business applications where transaction volumes are low and business logic is simple.
 When the number of users or the volume of transactions increases, separate the application logic from
database management functions by configuring one or more application servers against a database
server. This three-tiered application model for SAP R/3 keeps operations functioning without performance
degradation. Often, additional application servers are configured to process batch jobs or other long and
intense resource-consuming tasks. This separation of the application server enables system operations
staff to fine-tune individual application servers suited for specific data processing tasks.
BI OVERVIEW
 Computer: Computer is an electronic device, which
takes input, processed it and gives the accurate
result as output.
 Hardware: which we can see and touch. Software:
it is a set of programs Applications are of 2 types.
 OLTP (Online Transaction Processing)
 OLAP (Online Analytical Processing)
 There are some differences are there between
OLTP and OLAP.
OLTP OLAP

 1)Two dimensional model1) Multi

dimensional model2)Day-to-Day
Transactions2) Historical data tractions
also3)Application oriented3) Subject
oriented4)Users -> Thousands4) Users - >
Hundreds5)DB size -> 100MB – 1GB5) DB
size -> 100GB-1TB6)Redundancy6) No
Redundancy7)No security7) Security8)Not
Integrated8) Integrated.
Netweavers:
 Netweavers: It provides open integrity for SAP and
Non SAP. Integration is of some types
 People integration
 Information integration -> BI, MDM, KM.
 Process integration -> XI
 Platform integration
 Collaboration integration -> EP
 The architecture of Netweavier is ESA. Netweaviers
also a set of capabilities to provide
information/integration.
Layout/steps in SAP BW (DW):
 DB => for designing we can use 2 –
dimensional model. Data can be stored
permanently in database.
 Table contains rows and columns.
 Each column is a field in OLTP.
 Every table must have a Primary key.
 All non-key columns describe key columns
called Attributes.
ER MODEL
 ER-Model (Entity Relationship model):
 Multiple tables’ likes with a primary and
foreign key relationships these are called as
ER Model. In a table one field is Primary key
if we use the same field in other table then it
act as a foreign key in that table. If two or
more columns of a table together acts as
Composite primary key.

 In figure (1) and (2), CID is common. Here in figure (2) it acts as foreign
key.
DB DESIGN
 Designing DB:
 Two ways of designing a DB.
 Objected Oriented
 Normalization
 Object Oriented:
 Requirements (i.e. Defining system)
 Identifying the Objects (i.e. Objects) Ex:
Customer, Material, Product etc
 Entity diagram is as follows
 Attributes or Properties are nothing but properties of a table.
 Front-end people use methods or functions only.

Normalization:
 Converts demoralized tables into normalized tables.
 Normalization is nothing but dividing the table into small tables and combine them with
the help of primary and foreign key relationship.
 Demoralization contains all table data into one table.
 Reduces redundancy of data.
 Reduce complexity
 Saves memory.
 DB concepts in OLTP:
 MDM (Multi Dimensional Model) is used for designing. There are 4 types:
 Star Schema (traditional schema)
 Extended Star Schema (BW schema)
 Snow Flake scheme
 Hybrid schema
Star Schema (traditional schema):
 Characters indicate on what base you are trying to
analyses.
 Key-figures indicate what you are trying to
analyses.
 Master data is qualifying transaction data. Master
data is of 3 types.
 Attributes
 Hierarchy
 Text
 Master data is also called as Dimensional table.
 Star schema is completely demoralized form.
 Limitations:
 Since master data is with in the fact cube so it is not
reusable component.
 Limited analysis because the maximum number of
master data tables is 16.
 Performance is low because the execution of
alphanumeric data is slower than numeric data.
 If we want to extract the data from the table for
 example
Extended star schema:
 Extended star schema is nothing but
combination of both star schema and SID
(sorigated id). Changes from star schema to
extended star schema are as follows.
 Cube is called as infocube.
 All master data tables are placed out side the
cube so they are reusable components.
 Here master data tables and Dimensional
tables are different.
 When we are loading the data into master data table then SID table is
generated. Fact table contains Dimensional ids and key figures.
 Maximum of 1 fact table per infocube.
 Any table contains maximum of 255 fields.
 Maximum of 16 Dimensional tables that an infocube contains. 1 –unit, 1
–time, 1- packet, 13 – Dim id
 Minimum of 4 Dimensional tables that an infocube contains. 1 –unit, 1 –
time, 1- packet, 1 – Dim id.
 Maximum of 248 char per Dimensional table contains
 Maximum of 233 key figures per infocube.
 Limitations:
 Limiting the no. Of joins in reporting.
 Limiting no. Of fields in Dimensional table.

 Inorder to enter into the BW Select BW 3.OB Æ LOGON
User -- SAPUSER, Password -- INDIA then press enter
 This is the first screen. Give RSA1 in the command field and then press enter to login BW.
 This is the first screen for BW. It mainly contains 8
tabs.
 Modeling
 Monitoring
 Reporting Agent
 Transport Connection
 Documentation
 Business Content
 Translation
 Metadata Repository
 1. Modeling:
 It mainly Contains Creating infoarea, infoobjects,
infocube, infosource, infopackage, ODS,
Multiprovider, datasource etc.
 Loading of all objects
 A field in OLTP is called as infoobject in BW system.
 In loading E - Extraction
 T - Transferring L - Loading
 (This ETL Processing, before it is called as ETTL –
Extraction, Transferring, Transporting and Loading.
But now this ETL Processing is called as DTP –
Data Transferring Process).
 2. Monitoring:
 To see weather the load is failed or not.
 3. Reporting Agent:
 It is a tool with which we can schedule and
execute reporting functions in the
background.

 4. Transport Connection:
 By using Transport connection we can move
the objects from Development to Quality and
then to Production.
 5. Documentation:
 It enables you to insert, search and create links for one or more documentations
in various formats, versions and languages for SAP BW Objects.
 6. Business Content:
 It contains all the objects are delivered by SAPBW. It provides pre-Configured
information models based on metadata. It is a predefined analytical application
model i.e. part of SAP BW
 software. Versions
 Until unless you activate the object, we can’t use the object. N – NEW
 M – Modified
 A – Activate
 D – Delivered.
 Installing the business content means that the object converted from delivered
version to active version and start using them. We can’t modify the business
content objects directly. For that first copy that object and modify it.
 7. Translation:
 Converting from one language to another language.
 There are 64 languages in SAP.
 If you are translating them, only description will be
changed not technical name.
 8. Meta data Reporting:
 Data about data is called as Meta date.
 Meta data management maintains it. It is purely in
HTML format.
 THANK YOU