Embed Size (px)
Citation preview
SIEMENS
Business Intelligence (BI)
In-House Training Document
Trainer:
Muhammad Ali Mohsin
Senior Consultant – SEM/BI
Complied By:
Muhammad Faisal
Consultant BI/FICO
The purpose of the BI Training Document is documented all the level of information
related to BI during training sessions discussed. The training was held at Siemens
Learning Centre dated from November 2, 2009 to November 6, 2009.
Agenda
The following were the main agenda of the training:
• BI Architecture – Platform
• Extraction, Transformation and Loading (ETL) – Modeling
• Reports – Analyzer and Query Designer
• Dashboard – Web Application Designer
Overview
The SAP Business Intelligence (BI) allows us to analyze data from operative SAP
applications as well as all other business applications (legacy) and external data sources
such as databases, online services and the Internet.
The SAP BI Warehouse enables Online Analytical Processing (OLAP) to format the
information of large amounts of operative and historical data. OLAP technology enables
multi-dimensional analyses according to various business perspectives.
SAP BI is pre-configured with Business Content, ensures we can look at information
within the entire enterprise. Business Content contains pre-configured objects such as
InfoCubes, queries, key figures, Characteristics and other objects.
With the Business Explorer, the SAP Business Information Warehouse provides flexible
reporting and analysis tools for analyses and decision-making support in our enterprise.
These tools include query, reporting and OLAP functions. As an employee with access
authorization, we can evaluate past or current data on various levels of detail and from
different perspectives not only on the Web but also in MS Excel.
SAP BI Architecture
DWH Architecture
Comparison: OLTP Systems and OLAP Systems
We can see that there are fundamentally different demands on an OLTP system compared
with a Data Warehouse/ BI (OLAP) system. It is therefore most advantageous to
technically separate all aggregated reporting-related demands made on the Data
Warehouse from the OLTP system.
DEFINITIONS
InfoObject
Business evaluation objects are known in BW as InfoObjects. They are divide into
characteristics (for example, customers), key figures (for example, revenue), units (for
example, currency, amount unit), time characteristics (for example, fiscal year) and
technical characteristics (for example, request number).
There are two types of info objects:
• Characteristics (descriptive information e.g., Customer, Material, Sales Organization)
• Key Figures (quantitative information, e.g., amount, count, quantity).
InfoObject Catalogs:
The warehouse has many objects in it. In order to find these objects easily, we organize
them into different types of folders. InfoObject catalogs are just one of the types of
available folders in the warehouse.
InfoCube
An object that can function as both a data target and an InfoProvider. From a reporting
point of view, an InfoCube describes a self-contained dataset, for example, of a business-
orientated area. This dataset can be evaluated in a BEx query.
An InfoCube is constructed according to the so-called star schema.
A large fact table in the middle surrounded by several dimension tables.
It consists of a fact table that contains the key figures (233 key figures) [e.g. revenue,
sales quantity, etc] and sixteen (16) dimension tables that contain the characteristics
(every DIM table 248 characteristics [e.g. company code, division, etc].
InfoCubes are filled with data using the transformations from one or more Datasources.
InfoCube can be:
1. Standard InfoCube (Standard InfoCubes are technically for read accesses)
2. Real-time InfoCube (Real-time InfoCubes are technically for read and write
accesses)
Structure of InfoCube :
An InfoCube consist of the following structure:
• 1 fact table
• n dimension tables
• n surrogate ID (SID) tables
• n text tables
• n master data tables
Fact table : Contains the key figures, which are quantifiable values.
Dimension tables : Contain the characteristics that are used to analyze and report on the
key figures.
Sid tables : Specify tables in the SAP (BW) System that contains substitute ids. Sid
tables link the master and hierarchy tables outside the dimensions of a star schema.
Text tables : Contain descriptive text that might be time or language dependent.
Master tables : Contains attributes that are used for presenting and navigating reports in
SAP (BW) System. They can, however, be extended to include other data. Master tables
are also time-dependent and can be shared by multiple InfoCubes.
ODS / DSO
An ODS / DSO (Operational Data Store or Data Store Object) acts as a storage location
for consolidated and cleaned-up data (e.g., transaction data or master data) on the
document (atomic) level.
In addition pure “data warehouse theory definition” would be that data to ODS/DSO is
captured in “real time” or “near real time” mode and there is bigger portion of data
available as opposite to data warehouse’s cubes. ODS/DSO is combining key field (e.g.
business document or its item) with data field (e.g. business document status and other
properties) as a key figures. There is nothing multidimensional (no dimension neither fact
tables) with ODS/DSO as with cubes. Data in ODS/DSO is stored in transparent (flat)
database tables. ODS/DSO objects are reportable.
InfoSource
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:
• InfoSource for Transaction Data
• InfoSource for Master Data
DataSource
A DataSource is a set of fields that provide the data for a business unit for data transfer
into BI. From a technical viewpoint, the DataSource is a set of logically-related fields that
are provided to transfer data into BI in a flat structure (the extraction structure), or in
multiple flat structures (for hierarchies).
There are two types of DataSource:
1. DataSource for transaction data
2. DataSource for master data
a. DataSource for attributes
b. DataSource for texts
c. DataSource for hierarchies
Generic DataSource
A Generic datasource is created when no standard business content datasource is
available that meets client’s reporting requirements. There are three main methods for
generic extraction, namely
Extraction from View
Extraction by Functional Module
Extraction from Query
[http://www.youtube.com/watch?v=E1CO9XBQHnQ]
[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0ef83cd-9d90-2c10-249f-
92909d6d2612&overridelayout=true]
InfoSet [http://www.youtube.com/watch?v=wUTBjmgpZbI]
An InfoSet builds up a data join of basic InfoProviders. The valid combination of records
from the basic InfoProviders is determined by the join condition of the InfoSet.
An InfoSet describes data sources that are usually defined as joins for ODS objects or
InfoObjects (characteristics with master data). A time-dependent join or temporal join is
a join that contains an InfoObject that is a time-dependent characteristic.
An InfoSet is a semantic layer over the data sources and is not itself a data target.
Steps – Extraction from View
• Go to SBIW transaction code in R/3-select Generic DataSource.
• Select maintain generic DataSources.
• A new screen will be opened giving a table related application component under in
the application. Select table/view push button.
• Give the table name.
• Save and generate the DataSource.
• Select the width fields are transferred to BW.
• Generate the DataSource.
• Select the generic delta button for loading the deltas.
Multi-provider
Multi-Provider is a special Info-Provider which combine data from several Info-Providers
for its own reporting, without actually holding any physical data itself (i.e. its data comes
exclusively from the Info-Providers on which it is based), then, it can only use an Info-
Provider that is ready and available for reporting, in which case, the Transactional ODS
object is not one of them. Therefore, to include a Transactional ODS object in a Multi-
Provider, we would have to first define an Info-set for the Transactional ODS object.
We can include Master data table in the Multi-provider but for that we should convert the
Info-Object as the data target then only it is possible.
Note: We go for Multi-provider when we want to do reporting on two or more data
targets.
A Multi-Provider can be made of various combinations of the following Info-Providers:
1. InfoCubes
2. ODS Objects (Standard only)
3. InfoObjects
4. InfoSets
Creation steps:
1. Go to the info area where we want the multi provider; right click and chose create
multi provider.
2. Chose a technical name and also choose the info providers that we make part of this
multi provider.
3. When we confirm our entries, we will get infocube maintenance screen; on the right
side, we will see the characteristics available in al the basic cubes that we choose in the
first step.
4. Select the chars that we wish to be in the multi-provider and similarly for time chars,
key figs, and nav. attributes (if any).
5. Choose to create dimension and we will get a system msg. whether to create from any
of the basic cubes.
6. Either selects to create our own dimension and insert all the chars in to the appropriate
dimensions.
7. Go back to chars tab and there will be tab for "identification" clicks that and here is
where we specify which are the chars forms each cube we want into the multi-provider.
And likewise for the key figure.
8. Activate the multi-provider.
If we have data in the basic cube, we can view the data in the multi-provider from
LISTCUBE transaction.
Sources of Data for BI
Heterogeneous data can be loaded alongside the original mySAP Business Suite
components:
• Flat files: A flat file in ASCII or Comma Separated Value (CSV) format can
automatically be read by the BI standard.
• Multidimensional sources from other Data Warehouses
• XML: XML data can also be processed in BI, in many cases going through SAP XI
for preprocessing
• Relational data in other database management systems
• SAP R/3 Source System
ETL – Flat File loading
These simple steps will lead to load data from flat file.
Uploading of master data
Log on to our SAP BI with Transaction code RSA1
1. Creation of Info Objects:
• In left panel select info object
• Create info area and give InfoArea name and its description
• Create info object catalog (characteristics & Key figures) by right clicking the
created info area
• Create new characteristics and key figures under respective catalogs according to
the requirement
• Create required info objects and Activate.
2. Creation of Data Source:
• In the left panel select data sources.
• Create application component.
• Right click application component and create datasource.
• Specify data source name, source system, and data type (master data attributes,
text, and hierarchies).
• In general tab gives short, medium, and long description.
• In extraction tab specify file path, header rows to be ignored, data format (csv)
and data separator (,).
• In proposal tab load example data and verify it.
• In field tab we can we can give the technical name of info objects in the template
and we not have to map during the transformation the server will automatically
map accordingly. If we are not mapping in this field tab we have to manually map
during the transformation in Info providers.
• Activate data source and read preview data under preview tab.
• Create info package by right clicking data source and in schedule tab click star to
load data to PSA.(make sure to close the flat file during loading).
3. Creation of data targets:
• In left panel select info provider
• Select created info area and right click to select Insert Characteristics as info
provider
• Select required info object
• Under that info object select attributes
• Right click on attributes and select create transformation.
• In source of transformation , select object type( data source) and specify its name
and source system Note: Source system will be a temporary folder or package into
which data is getting stored
• Activate created transformation
• Create Data transfer process (DTP) by right clicking the master data attributes
• In extraction tab specify extraction mode ( full)
• In update tab specify error handling ( request green)
• Activate DTP and in execute tab click execute button to load data in data targets.
4. Monitor
• Right Click data targets and select manage and in contents tab select contents to
view the loaded data. Alternatively monitor icon can be used.
Uploading of Transactional data
5. Creation of Info Objects
• In left panel select info object
• Create info area
• Create info object catalog ( characteristics & Key figures ) by right clicking the
created info area
• Create new characteristics and key figures under respective catalogs according to
the project requirement
• Create required info objects and Activate.
6. Creation of Data Source
• In the left panel select data sources
• Create application component
• Right click application component and create datasource
• Specify data source name, source system, and data type (Transaction data)
• In general tab gives short, medium, and long description.
• In extraction tab specify file path, header rows to be ignored, data format (csv)
and data separator(,)
• In proposal tab load example data and verify it.
• In field tab we can we can give the technical name of info objects in the template
and we not have to map during the transformation the server will automatically
map accordingly. If we are not mapping in this field tab we have to manually map
during the transformation in Info providers.
• Activate data source and read preview data under preview tab.
• Create info package by right clicking data source and in schedule tab click star to
load data to PSA.( make sure to close the flat file during loading )
7. Creation of data targets
• In left panel select info provider
• Select created info area and right click to create ODS (data store object) or Cube.
• Specify name for the ODS or cube and click create
• From the template window select the required characteristics and key figures and
drag and drop it into the DATA FIELD and KEY FIELDS
• Click Activate.
• Right click on ODS or Cube and select create transformation.
• In source of transformation, select object type (data source) and specify its name
and source system Note: Source system will be a temporary folder or package into
which data is getting stored
• Activate created transformation
• Create Data transfer process (DTP) by right clicking the master data attributes
• In extraction tab specify extraction mode (full)
• In update tab specify error handling (request green)
• Activate DTP and in execute tab click execute button to load data in data targets.
8. Monitor
• Right Click data targets and select manage and in contents tab select contents to
view the loaded data. There are two tables in ODS new table and active table to
load data from new table to active table we have to activate after selecting the
loaded data.
• Alternatively monitor icon can be used.
Create InfoArea
Give InfoArea name and its description
Create InfoObject Catalog
Create InfoObject Catalog ===> InfoObject type Char ===> Create and Activate
Create InfoObject Catalog ===> InfoObject type Key Figure ==========> Create and
Activate
Create infoObject
Create Char type InfoObject==>Activate
Create KeyFigure type InfoObject ==> Activate
Create logical System
Create Application Component
Create Data Source
Give File Path and CSV Format
Activate DataSource
Preview
Create InfoCube
Include InfoObjects and Activate
Create Transformation either Cube level or DataSource Level
Rules generated and Activate
Create DTP from DataSource ===> InfoCube
Create InfoPackage
Name/description of the info package & save
Select data selection, extraction and Data target which ever we want to perform and then
go to scheduler tab and start.
Go to info provider, select respective data transfer process and click execute in right hand
side of the window and enter.
Check Monitor
Data Flow
Tools used for reporting are:
• BEx Query Designer - for making the queries.
• BEx Analyzer - To run the reports in Excel and design the format.
• BEx Web Analyzer - To run the reports on web application.
BEx Query Designer
The Query Designer is divided into eleven sub areas:
1. Infoprovider
All available objects such as Structures, Key Figures, and Dimensions will be displayed
in a directory tree structure in the left screen area of the Query Designer.
2. Characteristic Restriction
Here we define the characteristic filter values which apply to the entire result set.
3. Default Values
In this pane we define the characteristic filter values which should be used for the initial
view of the result set. The user may choose to modify these filters in the result.
4. Properties
Here is where the settings relevant to the currently highlighted query object are displayed.
We can also make changes to the setting here. Often there will be multiple tabs used to
organize the settings in this pane.
5. Messages
This pane is where informational or error messages are displayed.
6. Free Characteristics
Put the characteristics which we want to offer to the user for navigation purposes in this
pane. These characteristics do not appear in the initial view of the query result set, the
user must use a navigation control in order to make use of them. We do not define the
filter values here.
7. Columns
Any objects that needed to be included in the columns of the query are defined in this
area.
8. Rows
Any objects that needed to be included in the rows of the query are defined in this area.
9. Preview
The Preview section allows us to preview the result of our query in the Query Designer.
10. Tasks
A list of suitable tasks relating to highlighted query object are displayed here, we can
click on any of the tasks in the list to go directly to the settings.
11. Where Used
This pane provides information relating to the use of the query object.
SAP Tutor Tutorials are attached.
• Bex Query Designer
• Analytical Engine - Exception & Aggregation
• Query Designer Toolbar
There are a total of 22 icons in the toolbar with each having a different function that can
be performed on a query.
New Query
With this function, we are able to define a new query.
Open Query
Choose this function if we want to open an existing query.
Save Query
Using this function, we can save our query.
Execute
Choose this function if we want to display our query results via the portal.
Check Query
This function will perform a validity check on our query and inform us of any errors.
Properties
Choose this function if we want to change the description of the query or define the
settings for the result position, display options, numeric display, zero display and key
date of the query.
Cut
We use this function to remove a query object ready for inserting into another section of
the query definition.
Copy
We use this function to identify a query object in preparation for an insert of the object
into another section of the query definition.
Insert
This function is used to insert either the copied or cut object in query definition. Be sure
to mark the place where we want the query object to insert.
InfoProvider
This function will open the InfoProvider pane.
Filter
This function will open the Filter pane.
Rows/Columns
This function will open the Rows/Columns pane.
Table View
We can create a query for tabular reporting (each query element in a separate column), as
well as for Online Analytical Processing (OLAP) reporting, by activating or deactivating
the Table View mode in the query definition when defining a query. This function is only
available for queries with one structure. We can only have queries with two structures in
the multi-dimensional display. They are not suitable for OLAP reporting.
Cells
This function is only available for queries with two structures. We can define formulas
and selection conditions for cells explicitly. In this way, we control the values of cells
that appear at the intersections of structural components. This function enables us to
access individual cells in queries or to assign special values to these.
Conditions
We use this function to define conditions for a query. For each characteristic, we can give
limit conditions to the key figure values in order to determine, for example, all sales
revenues above or below a specified threshold value. The chosen characteristics are
displayed in the query with restricted key figures.
Exceptions
We use this function to define exceptions for a query. Exceptions are deviations from
normal key figure values, as defined by us, and are highlighted in color in the query view.
Query Properties
Choose this function if we want to change the description of the query or define the
settings for the result position, display options, numeric display, zero display and key
date of the query.
Tasks
Using this function, we can display the actions which are valid for the query object we
have highlighted.
Messages
This function opens the messages pane. In the messages pane there is a list of the
outstanding messages relating to the status of the query. These messages may be
informational i.e. .Query is successfully saved. or warning i.e. .No filter specified. Use
the Check Query function to display a list of messages in the messages pane relating to
the correctness of the query.
Query Where-Used List
Using this function, we can find out in which objects (Workbooks, Web templates) the
query is used.
Technical Name
Using this function, we can show/hide the technical names of the query components.
BEx Analyzer
Procedural Steps are as follows:
1. Access transaction by:
Start => Programs => Business Explorer => Analyzer
2. Choose ‘Enable Macros’ and then The Microsoft Excel screen shown below will
appear:
3. Choose the Folder option on the Business Explore toolbar and choose the query
option as shown below:
4. Log On to the SAP BW Production system as shown below:
5. On the “SAP BEx Select query” screen, click on the ‘Roles’ button to display a list
of queries.
6. If required, click on the ‘Spanner’ button to display the Technical Names of the
queries.
7. Highlight the name of the query that we wish to run and then click on the ‘OK’
button
8. Depending upon the query that we are running, we may be asked to input some
selection parameters as shown below:
9. Enter the appropriate selection criteria (such as those shown below) and click on
the button.
10. The report should now run and show a screen similar to the one shown below:
BEx Toolbar Functions
Use
As we start the Business Explorer Analyzer, the toolbar appears in Microsoft Excel. It
allows us to access all the important functions for navigating and analyzing the query
data.
Features
Open
This symbol takes we to the BEx Open dialog. We can open the following object types:
• Workbooks
• Queries
• Saved query views
• Exceptions
Depending on the type of object that we have selected, the BEx Open dialog appears
differently with the specified functions.
Saving
With the Save function on the BEx toolbar we can:
• Save the workbook as a new workbook
• Save the workbook as an existing workbook
• Change the title of the workbook
• Save the query view as a jump target
• Save the query view globally
If we save the workbook, then the query is not detached. We can call the workbook at a
later date, create a connection to the Business Information Warehouse Server, and refresh
the queries contained in the workbook.
Refreshing Queries
Refreshing the query means to request the current valid data from the BW Server. The
query is automatically refreshed when we insert it into the workbook and when we
change the navigational status, that is, unless we have activated the function Therefore,
we only usually need the function Refresh Query in the following cases:
• To update the data after we have opened a workbook
• When we fill the query with new variable values
Back
Choose Back if we want to undo our last navigation step.
Changing Queries
We use the function Change Query View on the BEx toolbar if we:
• Want to change the arrangement of characteristics and key figures into rows,
columns and free characteristics for the query and carry out several navigation
steps one after the other (Change Query View ® Change query (Local View)
• Want to change the definition of the query (Change Query View ® Change Query
(Global Definition)).
• Change Variable Values
Goto
With this function we can:
• Display exceptions in the alert monitor, providing that some exceptions have been
found for this query.
• Jump to a saved query view
• Reach to jump targets using the Report/Report Interface
• Activate the function Repeat jump on double-click, to use double-click to jump to
a saved view of query data
OLAP Functions for Active Cells
If we choose OLAP functions for active cell, we call the OLAP functions in the Business
Explorer. They are available on the cells for the filter and results areas of a query. The
context menu we call, depends on whether we select a cell in the filter area of the query,
or a cell in the results area of the query. We can also jump to documents for single master
data and characteristic values or documents for the navigation status.
Formatting
Formatting for the query underlines the type of data contained in a cell, highlighting the
structure of the delivered results. Query formatting consists of:
• Fonts
• Templates
• Borders
• Alignment
• Defining symbols for:
• Expanding hierarchically
• Collapsing hierarchically
• Expanding in other dimensions
• Linking to documents
• Hierarchy indentation
• Narrow
• Normal
• Wide
• Very wide
We can change the format of the query to configure the display however we like.
Layout
Using the layout functions, we can change the appearance of the screen for the query in
the workbook. We use the layout functions to:
• Attach a diagram or a map
• Display text elements for the query
• Display exceptions or conditions
• Move the filter area or the results area
• Select queries in a worksheet
Tools
We use the functions under Tools to:
• Display the query in a default view in the Web browser
• Call up the Query Designer
• Insert, copy, remove queries
• Remove all queries, delete the results and detach queries from the workbook
• Activate SAP sheet protection
Settings
We use the functions under Settings to determine whether:
• Queries are refreshed automatically
• There is a connection to the BW server
• Information about the BW server is displayed
• A new workbook it is created from scratch, selected from a list or based on an
existing template
• OLAP functions are available using the right mouse button
• Server warnings are suppressed
• Log book entries are recorded
BEx Web Application Designer (WAD)
With the BEx Web Application Designer, any source of data can be used as a Data Provider to
web items. These sources include data from the SAP data warehouse, non-SAP data warehouses
and OLTP sources from all systems. Dashboards are the type reports by using WAD.
The Web Items workspace in the Web Application Designer groups web items into
‘Standard’, ‘Advanced’ and ‘Miscellaneous’. There is a ‘Data Provider’ group that allows
us to add a new Data Provider of either type ‘Filter’ or ‘Query View’.
The Properties workspace shows the properties of the web template or selected web item.
The properties, and thus the groups of properties available for selection depends entirely
on the web item or template selected.
Some of the typical property groups are:
Display – all properties affecting the rendering of the item such as width, height and
visibility.
Internal Display – all properties relating to item-specific rendering such as ‘alternate table
row style’ for the Analysis web item.
Behavior – item-specific actions.
Data Binding – item-specific assignment of a Data Provider or the specification of
characteristics for a filter pane.
Paging – scrolling properties of an Analysis web item, for example
Cell Content – document link icon behavior for an Analysis web item.
Chart Texts – titles, axis descriptions and legend texts for the Chart web item.
LO COCKPIT
Step-by-Step Maintenance of LO Cockpit
Call Transaction LBWE and navigate as per the below screenshot:
Click on the maintain Extract structure to maintain the fields
An information message will be displayed
In the above screenshot: Click on the Update Overview text to reach the following
screen. This will take us to SM13 for any relative table updates and Execute.
Now go back to previous screen and click on BW Maintenance Delta Queue
This will take us to RSA7 transaction to view the delta queues if any
Click back to go reach this pop-up
Click on Run and it will prompt for confirming the entries in the Extract structure. Assign
a request so that it generates extract structure successfully.
Now on the Main LBWE screen, we can see RED status before the datasource
Now click on the Datasource as below
Assign a Request to have the Datasource screen where properties related to fields can be
modified.
As we assign this and come back we will see a change in the status color as YELLOW.
Now go to the BW System and Replicate the related Datasource from the Exact Source
system.
Now go back to the R/3 System and Click on the ACTIVE parameter under the Job
Control, assign a request
Now we will see that the status color will turn as GREEN and then we can assign the
update mode as well.
Now in the BW system create transformations from the datasource to the Infoprovider.
Create an infopackage and DTP to load the data.
COPA EXTRACTION
[http://www.sap-img.com/business/copa-extraction-steps.htm]
LIS, COPA, and FI/SL are Customer Generated Generic Extractors, and LO is BW
Content Extractors.
LIS is a cross application component LIS of SAP R/3, which includes, Sales Information
System, Purchasing Information System, Inventory Controlling. Similarly COPA is used
for specific Application Component of SAP R/3.
COPA collects all the OLTP data for calculating contribution margins (sales, cost of
sales, overhead costs).
COPA extraction steps:
R/3 System 1. KEB0
2. Select Datasource 1_CO_PA_CCA
3. Select Field Name for Partitioning (Eg, Ccode)
4. Initialise
5. Select characteristics & Value Fields & Key Figures
6. Select Development Class/Local Object
7. Workbench Request
8. Edit your Data Source to Select/Hide Fields
9. Extract Checker at RSA3 & Extract
BW 1. Replicate Data Source
2. Assign Info Source
3. Transfer all Data Source elements to Info Source
4. Activate Info Source
5. Create Cube on Infoprovider (Copy str from Infosource)
6. Go to Dimensions and create dimensions, Define & Assign
7. Check & Activate
8. Create Update Rules
9. Insert/Modify KF and write routines (const, formula, abap)
10. Activate
11. Create InfoPackage for Initialization
12. Maintain Infopackage
13. Under Update Tab Select Initialize delta on Infopackage
14. Schedule/Monitor
15. Create Another InfoPackage for Delta
16. Check on DELTA Option
17. Ready for Delta Load
SAP BW Glossary
Aggregate
An aggregate is a subset of an InfoCube. The objective when using aggregates is to
reduce I/O volume. The BW OLAP processor selects an appropriate aggregate during a
query run or a navigation step. If no appropriate aggregate exists, the BW OLAP
processor retrieves data from the original InfoCube instead.
Aggregate rollup
Aggregate rollup is a procedure to update aggregates with new data loads.
Application component
Application components are used to organize InfoSources. They are similar to the
InfoAreas used with InfoCubes. The maximum number of characters allowed for the
technical name is 32.
Authorization
An authorization defines what a user can do, and to which SAP objects. For example, a
user with an authorization can display and execute, but not change, a query.
Authorizations are defined using authorization objects.
Authorization object
An authorization object is used to define user authorizations. It has fields with values to
specify authorized activities, such as display and execution, on authorized business
objects, such as queries. The maximum number of characters allowed for the technical
name is 10.
Authorization profile
An authorization profile is made up of multiple authorizations. The maximum number of
characters allowed for the technical name is 10.
Bitmap index
A bitmap index uses maps of bits to locate records in a table. Bitmap indices are very
effective for Boolean operations of the WHERE clause of a SELECT statement. When
the cardinality of a column is low, a bitmap index size will be small, thereby reducing I/O
volume.
Business Content
Business Content is a complete set of BW objects developed by SAP to support the
OLAP tasks. It contains roles, workbooks, queries, InfoCubes, key figures,
characteristics, update rules, InfoSources, and extractors for SAP R/3, and other mySAP
solutions.
BW
BW is a data warehousing solution from SAP.
BW Monitor
BW Monitor displays data loading status and provides assistance in troubleshooting if
errors occur.
BW Scheduler
BW Scheduler specifies when to load data. It is based on the same techniques used for
scheduling R/3 background jobs.
BW Statistics
BW Statistics is a tool for recording and reporting system activity and performance
information.
Change run
Change run is a procedure used to activate characteristic data changes.
Characteristic
Characteristics are descriptions of key figures, such as Customer ID, Material Number,
Sales Representative ID, Unit of Measure, and Transaction Date. The maximum number
of characters allowed for the technical name is 9.
Client
A client is a subset of data in an SAP system. Data shared by all clients is called client-
independent data, as compared with client-dependent data. When logging on to an SAP
system, a user must specify which client to use. Once in the system, the user has access to
both client-dependent data and client-independent data.
Communication structure
The communication structure is the structure underlying the InfoSource.
Compound attribute
A compound attribute differentiates a characteristic to make the characteristic uniquely
identifiable. For example, if the same characteristic data from different source systems
mean different things, then we can add the compound attribute 0SOURSYSTEM (source
system ID) to the characteristic; 0SOURSYSTEM is provided with the Business Content.
Data packet size
For the same amount of data, the data packet size determines how work processes will be
used in data loading. The smaller the data packet size, the more work processes needed.
Data Warehouse
Data Warehouse is a dedicated reporting and analysis environment based on the star
schema database design technique and requiring special attention to the data ETTL
process.
DataSource
A DataSource is not only a structure in which source system fields are logically grouped
together, but also an object that contains ETTL-related information. Four types of
DataSources exist:
DataSources for transaction data
DataSources for characteristic attributes
DataSources for characteristic texts
DataSources for characteristic hierarchies
If the source system is R/3, replicating DataSources from a source system will create
identical DataSource structures in the BW system. The maximum number of characters
allowed for a DataSource's technical name is 32.
Delta update
The Delta update option in the InfoPackage definition requests BW to load only the data
that have been accumulated since the last update. Before a delta update occurs, the delta
process must be initialized.
Development class
A development class is a group of objects that are logically related.
Display attribute
A display attribute provides supplemental information to a characteristic.
Drill-down
Drill-down is a user navigation step intended to get further detailed information.
ETTL
ETTL, one of the most challenging tasks in building a data warehouse, is the process of
extracting, transforming, transferring, and loading data correctly and quickly.
Free characteristic
A free characteristic is a characteristic in a query used for drill-downs. It is not displayed
in the initial result of a query run.
Full update
The Full update option in the InfoPackage definition requests BW to load all data that
meet the selection criteria specified via the Select data tab.
Generic data extraction
Generic data extraction is a function in Business Content that allows us to create
DataSources based on database views or InfoSet queries. InfoSet is similar to a view but
allows outer joins between tables.
Granularity
Granularity describes the level of detail in a data warehouse. It is determined by business
requirements and technology capabilities.
IDoc
IDoc (Intermediate Document) is used in SAP to transfer data between two systems. It is
a specific instance of a data structure called the IDoc Type, whose processing logic is
defined in the IDoc Interface.
Index
An index is a technique used to locate needed records in a database table quickly. BW
uses two types of indices: B-tree indices for regular database tables and bitmap indices
for fact tables and aggregate tables.
InfoArea
InfoAreas are used to organize InfoCubes and InfoObjects. Each InfoCube is assigned to
an InfoArea. Through an InfoObject Catalog, each InfoObject is assigned to an InfoArea
as well. The maximum number of characters allowed for the technical name is 30.
InfoCube
An InfoCube is a fact table and its associated dimension tables in the star schema. The
maximum number of characters allowed for the technical name is 30.
InfoCube compression
InfoCube compression is a procedure used to aggregate multiple data loads at the request
level.
InfoObject
In BW, key figures and characteristics are collectively called InfoObjects.
InfoObject Catalog
InfoObject Catalogs organize InfoObjects. Two types of InfoObject Catalogs exist: one
for characteristics, and one for key figures. The maximum number of characters allowed
for the technical name is 30.
InfoPackage
An InfoPackage specifies when and how to load data from a given source system. BW
generates a 30-digit code starting with ZPAK as an InfoPackage's technical name.
InfoSource
An InfoSource is a structure in which InfoObjects are logically grouped together.
InfoCubes and characteristics interact with InfoSources to get source system data. The
maximum number of characters allowed for the technical name is 32.
Key figure
Key figures are numeric values or quantities, such as Per Unit Sales Price, Quantity Sold,
and Sales Revenue. The maximum number of characters allowed for the technical name
is 9.
Line item dimension
A line item dimension in a fact table connects directly with the SID table of its sole
characteristic.
Logical system
A logical system is the name of a client in an SAP system.
Multi-cube
A multi-cube is a union of basic cubes. The multi-cube itself does not contain any data;
rather, data reside in the basic cubes. To a user, the multi-cube is similar to a basic cube.
When creating a query, the user can select characteristics and key figures from different
basic cubes.
Navigational attribute
A navigational attribute indicates a characteristic-to-characteristic relationship between
two characteristics. It provides supplemental information about a characteristic and
enables navigation from characteristic to characteristic during a query.
Number range
A number range is a range of numbers that resides in application server memory for
quick number assignments.
ODS
ODS is a BW architectural component located between PSA and InfoCubes that allows
BEx reporting. It is not based on the star schema and is used primarily for detail
reporting, rather than for dimensional analysis. ODS objects do not aggregate data as
InfoCubes do. Instead, data are loaded into an ODS object by inserting new records,
updating existing records, or deleting old records, as specified by the 0RECORDMODE
value.
Parallel query
A parallel query uses multiple database processes, when available, to execute a query.
Partition
A partition is a piece of physical storage for database tables and indices. If the needed
data reside in one or a few partitions, then only those partitions will be selected and
examined by a SQL statement, thereby significantly reducing I/O volume.
Profile Generator
Profile Generator is a tool used to create authorization profiles.
PSA
PSA is a data staging area in BW. It allows us to check data in an intermediate location,
before the data are sent to its destinations in BW.
Query
A BW query is a selection of characteristics and key figures for the analysis of the data in
an InfoCube. A query refers to only one InfoCube, and its result is presented in a BEx
Excel sheet. The maximum number of characters allowed for the technical name is 30.
Read mode
Read mode for a query determines the size and frequency of data retrievals from
database: all data at once, as needed per navigation step, or as needed per hierarchy node.
Reconstruct
Reconstruct is a procedure used to restore load requests from PSA.
Request
A request is a data load request from BW Scheduler. Each time that BW Scheduler loads
data into an InfoCube, a unique request ID is created in the data packet dimension table
of the InfoCube.
RFC
RFC (Remote Function Call) is a call to a function module in a system different from the
caller's—usually another SAP system on the local network.
Role
In Profile Generator, an authorization profile corresponds to a role. A user assigned to
that role also has the corresponding authorization profile. A user can be assigned to
multiple roles. The maximum number of characters allowed for the technical name is 30.
SID
SID (Surrogate-ID) translates a potentially long key for an InfoObject into a short four-
byte integer, which saves I/O and memory during OLAP.
Source system
A source system is a protocol that BW uses to find and extract data. When the source
system is a non-SAP system, such as a flat file or a third-party tool, the maximum
number of characters allowed for the technical name is 10. When the source system is an
SAP system, either R/3 or BW, the technical name matches the logical system name. The
maximum number of characters allowed for the technical name is 32.
Star schema
A star schema is a technique used in the data warehouse database design to help data
retrieval for online analytical processing.
Statistics
For a SQL statement, many execution plans are possible. The database optimizer
generates the most efficient execution plan based on either the heuristic ranking of
available execution plans or the cost calculation of available execution plans. Statistics is
the information that the cost-based optimizer uses to calculate the cost of available
execution plans and select the most appropriate one for execution. BW uses the cost-base
optimizer for Oracle databases.
System Administration Assistant
System Administration Assistant is a collection of tools used to monitor and analyze
general system operation conditions.
System landscape
The system landscape specifies the role of each system and the paths used in transporting
objects among the various systems.
Time-dependent entire hierarchy
A time-dependent entire hierarchy is a time-dependent hierarchy whose nodes and leaves
are not time-dependent.
Time-dependent hierarchy structure
A time-dependent hierarchy structure consists of nodes or leaves that are time-dependent,
but the hierarchy itself is not time-dependent.
Transfer rule
Transfer rules specify how DataSource fields are mapped to InfoSource InfoObjects.
Transfer structure
A transfer structure maps DataSource fields to InfoSource InfoObjects.
Update rule
An update rule specifies how data will be updated into their targets. The data target can
be an InfoCube or an ODS object. If the update rule is applied to data from an
InfoSource, the update rule's technical name will match the InfoSource's technical name.
If the update rule is applied to data from an ODS object, the update rule's technical name
will match the ODS object's technical name prefixed with number 8.
Variable
A variable is a query parameter. It gets its value from user input or takes a default value
set by the variable creator.
Workbook
A BW workbook is an Excel file with a BEx query result saved in BDS. BW assigns a
25-digit ID to each workbook. Users need merely name a workbook's title.
Some Important Transaction Codes for SAP BW :
1 RSA1 Administrator Work Bench
2 RSA11 Calling up AWB with the IC tree
3 RSA12 Calling up AWB with the IS tree
4 RSA13 Calling up AWB with the LG tree
5 RSA14 Calling up AWB with the IO tree
6 RSA15 Calling up AWB with the ODS tree
7 RSA2 OLTP Metadata Repository
8 RSA3 Extractor Checker
9 RSA5 Install Business Content
10 RSA6 Maintain DataSources
11 RSA7 BW Delta Queue Monitor
12 RSA8 DataSource Repository
13 RSA9 Transfer Application Components
14 RSD1 Characteristic maintenance
15 RSD2 Maintenance of key figures
16 RSD3 Maintenance of units
17 RSD4 Maintenance of time characteristics
18 RSBBS Maintain Query Jumps (RRI Interface)
19 RSDCUBE Start: InfoCube editing
20 RSDCUBED Start: InfoCube editing
21 RSDCUBEM Start: InfoCube editing
22 RSDDV Maintaining
23 RSDIOBC Start: InfoObject catalog editing
24 RSDIOBCD Start: InfoObject catalog editing
25 RSDIOBCM Start: InfoObject catalog editing
26 RSDL DB Connect - Test Program
27 RSDMD Master Data Maintenance w.Prev. Sel.
28 RSDMD_TEST Master Data Test
29 RSDMPRO Initial Screen: MultiProvider Proc.
30 RSDMPROD Initial Screen: MultiProvider Proc.
31 RSDMPROM Initial Screen: MultiProvider Proc.
32 RSDMWB Customer Behavior Modeling
33 RSDODS Initial Screen: ODS Object Processng
34 RSIMPCUR Load Exchange Rates from File
35 RSINPUT Manual Data Entry
36 RSIS1 Create InfoSource
37 RSIS2 Change InfoSource
38 RSIS3 Display InfoSource
39 RSISET Maintain InfoSets
40 RSKC Maintaining the Permittd Extra Chars
41 RSLGMP Maintain RSLOGSYSMAP
42 RSMO Data Load Monitor Start
43 RSMON BW Administrator Workbench
44 RSOR BW Metadata Repository
45 RSORBCT BI Business Content Transfer
46 RSORMDR BW Metadata Repository
47 RSPC Process Chain Maintenance
48 RSPC1 Process Chain Display
49 RSPCM Monitor daily process chains
50 RSRCACHE OLAP: Cache Monitor
51 RSRT Start of the report monitor
52 RSRT1 Start of the Report Monitor
53 RSRT2 Start of the Report Monitor
54 RSRTRACE Set trace configuration
55 RSRTRACETEST Trace tool configuration
56 RSRV Analysis and Repair of BW Objects
57 SE03 Transport Organizer Tools
58 SE06 Set Up Transport Organizer
59 SE07 CTS Status Display
60 SE09 Transport Organizer
61 SE10 Transport Organizer
62 SE11 ABAP Dictionary
63 SE18 Business Add-Ins: Definitions
64 RSDS Data Source Repository
65 SE19 Business Add-Ins: Implementations
66 SE19_OLD Business Add-Ins: Implementations
67 SE21 Package Builder
68 SE24 Class Builder
69 SE80 Object Navigator
70 RSCUSTA Maintain BW Settings
71 RSCUSTA2 ODS Settings
72 RSCUSTV*
73 RSSM Authorizations for Reporting
74 SM04 User List
75 SM12 Display and Delete Locks
76 SM21 Online System Log Analysis
77 SM37 Overview of job selection
78 SM50 Work Process Overview
79 SM51 List of SAP Systems
80 SM58 Asynchronous RFC Error Log
81 SM59 RFC Destinations (Display/Maintain)
82 LISTCUBE List viewer for InfoCubes
83 LISTSCHEMA Show InfoCube schema
84 WE02 Display IDoc
85 WE05 IDoc Lists
86 WE06 Active IDoc monitoring
87 WE07 IDoc statistics
88 WE08 Status File Interface
89 WE09 Search for IDoc in Database
90 WE10 Search for IDoc in Archive
91 WE11 Delete IDocs
92 WE12 Test Modified Inbound File
93 WE14 Test Outbound Processing
94 WE15 Test Outbound Processing from MC
95 WE16 Test Inbound File
96 WE17 Test Status File
97 WE18 Generate Status File
98 WE19 Test tool
99 WE20 Partner Profiles
100 WE21 Port definition
101 WE23 Verification of IDoc processing
102 DB02 Tables and Indexes Monitor
103 DB14 Display DBA Operation Logs
104 DB16 Display DB Check Results
105 DB20 Update DB Statistics
106 KEB2 DISPLAY DETAILED INFO ON CO-PA DATA SOURCE R3
107 RSD5 Edit InfoObjects
108 SM66 Global work process Monitor
109 SM12 Display and delete locks
110 OS06 Local Operating System Activity
111 RSKC Maintaining the Permittd Extra Chars
112 SMQ1 qRFC Monitor (Outbound Queue)
