BW Overview Final V1.1

AppLabs confidential and restricted circulation 2

What is SAP R/3 ?


Why SAP ?


Why SAP ?


SAP #1 in ERP MarketSAP #1 in ERP Market


Is SAP the best ?


What are the features of SAP System?

SAP has all the characteristics a good ERP system should have.

It does all that is expected of it and then more.


Features of SAP


Why SAP BW ?


Why SAP BW ?


BI – The Way !!


Solution !!


Stay Ahead with SAP !!


BW 3.5 was part of Netweaver 2004 and BI7.0 is part of Netweaver 2004s which isalso known as Netweaver 7.0. Along with the platform, change a host of new featuresand ramp ups in terms of product capability was brought in. It is not a differentproduct but more of a highly improved.

Introduction To BW3.5 and BI7.0

The SAP NetWeaver Application Server is the central foundation for the entire SAP software stack. It also provides a platform for other NetWeaver components (Portal, XI, and so on), as well as for ABAP and Java applications. The full J2EE standard is supported. The SAP NetWeaver Application Server is the further development of the SAP Web Application Server.


DataSource defines Transfer Structure.

InfoSource defines Communication Structure.

Transfer Rules imply between DataSource and InfoSource.If we write a Routine in Transfer Rules we call It as transfer routine.Transfer Rules are specific to data source.

Update Rules imply between InfoSource and Data target.If we write a routine in Update Rules we call it as update routine.Update Rules are specific to Data target.

Data Target can be either ODS/DSO or INFOCUBE.

Property of ODS/DSO is overwrite.

Property of INFOCUBE is Additive.

Terminology Of BW3.5


SAP BW3.5 Flow


InfoObjects

InfoObjectInfoObjects are the basic information providers of BW. They structure the information needed to create InfoCubes/ODS Objects.

Types Of InfoObjects

1.Key Figures : Data part of an InfoObject. They are quantifiable values. (Eg. Quantity Sold, Revenue)2.Characteristics : Objects that are used to calculate and present KeyFigures. (Eg. Sales Office, Customer)3.Time Characteristics : Characteristics that are assigned to the dimension of time. (Eg. Fiscal Year, Period)4.Technical Characteristics : Only of structural use within BW.

5.Units : Units for the Key Figures.


Characteristics and KeyFigures

Key figures are measurable objects like Sales Quantity


InfoProviderIt is an area on which we can do Reporting.

All DataTargets cannot be InfoProviders but Infoproviders can be DataTargets.

Example:1.InfoCube,ODS/DSO,MasterData objects,InfoSet,Multiprovider all are Infoproviders.

2.Infocube,ODS/DSO ,MasterData objects can be DataTargets.

InfoProvider


PSA


PSA

• PSA stands for persistent staging area.

• It act as a inbound storage location for the data which is coming from any database.

• The loaded data is saved and unchanged.

• It holds Master data as well as Transaction data.

Advantages:

Error handling is the advantage in this transfer method.


DataSource

DataSource Data that logically belongs together is stored in the SAP (R/3) Source System in the form of DataSources. A DataSource contains a number of fields in a flat structure used to transfer data into SAP(BW) System. A DataSource is an object that, at the request of SAP (BW) System, makes data available in one of its predetermined structures.

There are 2 Categories of DataSource Standard DataSource (Application DataSource) Non-Standard DataSource (Generic DataSource) DataSources for transaction data DataSources for master data DataSource for Attributes Contain attributes of master data characteristic. DataSource for Text Contain descriptive text. DataSource for Hierarchies If we want drill up and drill down approach we go for hierarchies.


InfoSource

InfoSource

Data that logically belongs together is stored in the SAP (BW) System in the form of InfoSources.

An InfoSource contains a number of InfoObjects which structure the information needed to create InfoCubes / ODS Objects in the SAP (BW) System.

An InfoSource is an object that, at the request of SAP (BW) System, makes data available to the InfoCubes / ODS Objects.

There are 2 Categories of InfoSource

1.InfoSource For Transaction Data2.InfoSource For Master Data


Transfer Rules

In the transfer rules maintenance, you determine whether the communication structure is filled with fixed values from the transfer structure fields, or using a local conversion routine


Update Rules

The update rules specify how the InfoObjects (Key Figures, Time Characteristics,Characteristics) are updated in the DataTargets from the Communication Structure of an InfoSource. You are therefore connecting an InfoSource with an InfoCube/ODS object.


Operational Data Store(ODS) Types Of ODS(BW3.5)

This is an area where we can consolidate the data which comes from different DataSources.Reports can be build on the ODS/DSO. Advantages: - Read the data at document level - Data granularity - Overwrite functionality

There are two types of ODS(Operational Data Store)1. Standard ODS2.Transactional ODS

ODS is not used for multi-dimensional analysis like Infocube. The data from ODS can be updated with delta update into an Infocube. The data in ODS is stored in a transparent table. There is no fact or dimensional table created for ODS.


ODS has 3 Tables


DataStore object types:Standard DataStore object

Data provided using a data transfer processSID values can be generatedData records with the same key are aggregated during activationData is available for reporting after activation

Write-optimized DataStore objectData provided using a data transfer processSID values cannot be generatedRecords with the same key are not aggregatedData is available for reporting immediately after it is loaded

DataStore object for direct updateData provided using APIsSIDs cannot be generatedRecords with the same key are not aggregated

DataStore Objects BI(7.0)


InfoCube and DataTarget

• Infocubes are data targets

• They are central objects of MDM in SAPBW

• Reports and analysis are based on info cubes

• Queries can be defined and executed on the InfoCubes

DataTarget (InfoCube) The central objects upon which reports and analyses in BW are based, are called InfoCubes. An InfoCube is a multidimensional data structure. An InfoCube is a set of relational tables that contains InfoObjects. An InfoCube consists of a Fact Table and a set of n Dimension Tables that define the axes of its multiple dimensions.


Types Of InfoCubes(BW3.5)

There are two types of cubes(SAP BW3.5)1.Physical Cubes – Physically Contains Data2.Virtual Cubes -- No physical Data

Physical cubes are again two types(SAP BW3.5)1.Basic Cube -- For the existing data 2.Transaction Cube -- For forecasting Eg:SAP BPS (Business planning and Simulation)

Virtual infocubes are again three types(SAP BW3.5)1.SAP remote cube -- for other modules like CRM etc 2.Non SAP remote cube -- for other databases 3.With services -- for a particular functional module


Infocube Types(BW3.5)


Types Of InfoCubes(BI7.0)

There are two types of cubes(SAP BI7.0)1.Physical Cubes – Physically Contains Data2.Virtual Cubes -- No Physical Data

Physical cubes are again two types(SAP BI7.0)1.Standard InfoCube -- For the existing data 2.RealTime InfoCube -- For forecasting Eg:SAP IP (Integrated Planning)

Virtual infocubes are again three types(SAP BI7.0)1.Based on Direct acess -- for other modules like CRM etc 2.Based on BAPI -- for other databases 3.Based on FunctionModule -- for a particular function module


InfoSet

An InfoSet giving data by a join condition from different Datatargets like

• ODS/DSO• MasterDataObjects• InfoCubes


MultiProviders

Using MultiProviders we can combine and access the data from differentDataTargets like• InfoCubes• ODS/DSO• Infoset• Master data objects


SAP BI7.0 Flow


Trasformations and Creation of Transformations

Transformations

1.Right Click on the target object and select the CreateTransformation option


Transformations Screen Flow

2. Create the relevant direct mappings by dragging and dropping the source field to their relevant targets

3. Now save the transformation rule group.


Routines In SAP BI7.0

Routines are used to define complex transformation rules. In most of the cases data won’t be coming directly in desired form before sending to the target. In some cases output needs to be derived on some incoming data. In such cases we need to go for writing of routines at the transformation level.

There are four types of Routines availableCharacteristic or Field RoutineStart RoutineEnd RoutineExpert Routine

The routine which we need to go for depends on when it needs to be executed. Suppose if some logic needs to be implemented before transformation then the start routine needs to be implemented.


Start Routine

Start Routine

Definition

The start routine is run at the start of the transformation. The start routine has a table in the format of the source structure as input and output parameters. It is used to perform preliminary calculations and store these in a global data structure or in a table. This structure or table can be accessed from other routines. You can modify or delete data in the source_package .


End Routine

End Routine

Definition

An end routine is a routine with a table in the target structure format as input and output parameters. You can use an end routine to postprocess data after transformation on a package-by-package basis. Data is stored in result_package.


Characteristic Routine and Expert Routine

Expert Routine

Definition

An Expert routine is a routine with contains both the source and target structure. we can use Expert routine if there are not sufficient functions to perform transformation.

Characteristic or Field Routine

Definition

It operates on a single record for a single characteristic or key figure. The value gets modified in the routine based on one or more source fields before it is transferred to the data target.


1.The Data Warehousing Workbench replaces the Administrator Workbench.2.The InfoPackage is only used for loading data into the PSA and the subsequent DataTargets are loaded by using Transformations and DTP(Data Transfer Process).3.BI7.0 supports real-time data acquisition.4.In Infosets now you can include Infocubes as well.5.The Remodeling and Repartitioning of an infocube helps us to add new keyfigures and characteristics and handles historical data.6.Search functionality has improved.7.The transformation replaces the transfer and update rules.8.New authorization objects have been added. S_RS_ADMWB , S_RS_DTP , S_RS_AUTH.9.Renamed Operational Data Store(ODS) as DataStoreObject(DSO).10.Inclusion of Write-optmized DataStore for faster loading process.Its like a staging Area in BI7.0 and can be used in post process of further Data Target.

Major Differences between SAP BW3.5 and SAP BI7.0


Extractor types


Standard Extractor

Field4Field5Filed6

Field1Field2Field3

Field7Field8Field9

Field1Field 4Field9

Table1 Table2 Table3


Types of Extractors


Standard Extraction

Standard Extraction


T-CODE: LBWE(LO Cockpit Maintenance)


T-CODE:RSA5(Installing Business Content Data Source)


LO COCKPIT Maintenance Screen


Generic Extraction

Generic Extraction


Generic Extractor types

When Business content does not provide a data source then we had given a task to generate our own data source


Generic Data Source Creation


Delta Types in Generic Extraction


Cross Application


Enhancements

Enhancements


Standard Extractors with enhancement technique

Field4Field5Filed6

Field1Field2Field3

Field7Field8Field9

Field1Field 4Field9

Table1 Table2 Table3

Field9

Enhancement Technique


Standard Extractors with enhancement technique

Field4Field5Filed6

Field 1

Field2Field3

Field1Field 2Field6

Table1 Table2

Enhancement technique


Standard Extractors with enhancement technique..


Open Hub Destination


Process Chain


Typical Data load Cycle


Introduction

Process chains are a robust graphical scheduling & monitoring tool to maintain automation, visualization & monitoring of tasks/processes. These chained processes are designed to carry specific tasks. Process chains are integrated into CCMS, which is in turn integrated into portal based BI administration cockpit.

What Process Chains does is simply automate complex tasks/process scheduling, visualization of these processes plus central controlling of these tasks (either in same or linked process chains). If a process chain isn’t available for a specific task, SAP provides customers with an easy way to create custom process types, wherein one can still run customer programs using Business Content “ABAP process types”.

A process chain consists of a start process, individual application processes and the so-called collection processes. The application processes are the actual processes. SAP BI supports process types like loadprocess and post processing processes, Data target administration processes and other processes


Process chain Flow


Usage of Process Chains

Process Chains are similar to flowcharts which are scheduled to be waited in background & triggered for a event (or for starting further other processes) by a process. Here we need to list all Info packages, DTPs that's necessary to load the data, which can be either a full load or delta load, following which these chainsare scheduled (Viz. hourly, daily, monthly, etc, depending on business requirement). So, before creating process chains, we need to keep the process flow perfect (i.e. the links between BI objects like Info package,DSO, Cubes etc) in the BID system.

This process chains can be used to automatically load attribute/hierarchy etc, wherein in procedure these are listed as application process


Process chains in SAP Business Intelligence

Previously in 3.x, we had used Event chains, automatisms and process chains for automating processes, which had a lesser flexibility. In SAP BI 7.0, the existing automation functionalities are backward compatible,but now automations are not longer used for transformations & data transfer processes in SAP BI 7.0 Processes chains are necessary to support those processes which are sometimes complex & parallelization plus where branching for status-dependency is necessary. We can divide a process chain into several subprocesses which enable us to administrate it better for sake of clarity & effective management.


Process Chain Views

In a process chain, within a particular time slot all the respective time dependencies are bundled together,and they offer central controlling & monitoring of all processes steps defined in them.Process chain maintenance can be reached via Data Warehousing Workbench or via the transaction code:RSPC, which offers different views on process chains. Planning View: Using click, drag and drop, the process chain is designed at this stage. All the existing process chains and definition of process chains can be overviewed here and here in theplanning view all the process chains are created & maintained. Checking View: The process chain is checked for errors. We can view this using the control Ctrl+F2 in RSPC, where the results from the testing (both syntactical and semantic) are defined in the plan view, so as and when some changes are made respective process chains are executed. Log View: The results of each run are monitored. In this log view, we have the details of the process chain selected on the plan view.


Process Chain View


Building A Process Chain


Performance Tuning


Performance Tuning – w.r.t Query

These are the techniques to improve query performance.


Performance Issues


1.Loading into InfoCube Allways delete Indexes and then load into InfoCube and then Create Indexes.2.By using PSA as Transfer Method Allways choose PSA and DataTarget parallel Update subsequent datatargets(in order to reduce burden on the server).3.Resource Utilization.4.Deploy Parallelism - InfoPackages of different data selectios to be scheduled in parallel.5.DataPacketSize - Standard DataPacketSize is 50000 in SAP BW3.5.6.Timing of the load.7.Eliminate unnecessary processes. a)Deleting indexes doesnt make sense if we load less number of records b)For millions of records to be loaded,if the reporting frequency is very Less then go with Multiprovider. c)Depending on Delta process of the DataSource.

Performance – w.r.t Loading


Reports


Business Explorer


BEx


BEx


BEx


Query

A query is a data evaluation based on the selection of characteristics and key figures


Types Of Variables

Definition:To parameterize the queries.To pass the values to query dynamically.

Types:1.Characteristic Variable2.Formula Variable3.Text Variable4.Hierarchy Variable5.Hierarchy Node Variable

Characteristic Variable:To restrict the characteristic values dynamically we create characteristic variable.

Formula Variable:To make conditions,exceptions,calculated key figures,new formula dynamic weCreate formula variable


Variables..

Text Variable:In order to make headings of the columns dynamic we create text variable.

Hierarchy Variable:In order to fix the hierarchies at run time we create hierarchy variables.

Hierarchy Node Variable:In order to restrict the query dynamically to a particular node level of an hierarchy we create hierarchy node variable.


WorkBook


QUESTIONS???

Questions


End of Overview....

End of Overview

Documents

BW Overview Final V1.1