Beruflich Dokumente
Kultur Dokumente
SAP BW
Student Guide
Page 1 of 197
SAP BW
Table of contents
Page 2 of 197
SAP BW
Page 3 of 197
SAP BW
The main differences between an OLTP and an OLAP system are as follows –
Page 4 of 197
SAP BW
Page 5 of 197
SAP BW
A fact is measure that answers the questions like “how much?” and “how
many?” The fact data (values for the facts) are stored in a highly normalized
fact table. A dimension is a textual description of the dimensions/features
of the business. The dimension answers the questions “Who? What? When?”
For example, the dimensions of a product may include product name, brand
name, size, and packaging type. The values of the dimension attributes are
stored in various demoralized dimension tables.
As shown in figure 1.1, a fact table appears in the middle of the graphic,
along with several surrounding dimension tables. The central fact table is
usually very large, measured in gigabytes. It is the table from which we
retrieve the statistical data. The size of the dimension tables amounts to
only 1 to 5 percent of the size of the fact table. Foreign keys tie the fact
table to the dimension tables.
Page 6 of 197
SAP BW
With the Business Explorer (BEx), SAP BW gives a flexible reporting and
analysis tool to support strategic analyses and decision-making processes
within an organization. These tools include querying, reporting and OLAP
functions.
Page 7 of 197
SAP BW
1.4.1.4. Databases
SAP BW allows data to be loaded from external relational database systems.
A DataSource is generated based on the external table structure, enabling
table content to be loaded quickly and consistently into SAP BW.
DB Connect is a way, which allows relational databases to be accessed
directly. Here, SAP DB MultiConnect is used to create a connection to the
database management system (DBMS) in the external database. By
importing metadata and original data, the necessary structures can be
generated in SAP BW and the data can be loaded into the SAP BW system.
Page 8 of 197
SAP BW
them using a monitor tool. However, before the data is in a suitable form to
be stored, it must be prepared by the Extraction, Transformation and Load
(ETL) process.
You can use these tools to carry out both Microsoft Excel and Web-based
analyses across several dimensions (such as time, place, product, and so on)
simultaneously.
Page 9 of 197
SAP BW
The main distinction between a classic start schema and SAP BW star
schema is that in the SAP BW star schema the dimension tables do not
contain master data information. This master data information is stored in
separate tables, called master data tables. We can think of the SAP BW star
schema as two self-contained areas:
• InfoCube
• Master Data Tables/Surrogate ID (SID-) Tables
1.5.1. InfoCube
InfoCubes are the central objects of the multi-dimensional model in SAP
BW. Reports and analyses are based on these. From a reporting perspective,
an InfoCube describes a self-contained data set within a business area, for
which you can define queries.
An InfoCube (BasisCube) consists of a number of relational tables- a central
fact table surrounded by several dimension tables- combined on a multi-
dimensional basis.
Note: There are various types of InfoCube in BW, which will be discussed
later. Till then an InfoCube will always refer to a BasisCube. The BasisCube
is the InfoCube relevant for modeling, since only physical objects (objects
that contain data) are considered in the modeling within the SAP BW- data
model.
In the SAP BW- star schema, the facts in the fact table are referred to as
key figures and the dimension attributes as characteristics. The dimension
tables are linked relationally with the central fact table by way of foreign
or primary key relationships. In contrast to the classic star schema, the
characteristic values are not stored in the dimension tables. A numerical SID
key is generated for each characteristic. This foreign key replaces the
Page 10 of 197
SAP BW
Each dimension table has a generated numerical 'primary key', called the
dimension key. In the graphic above, this dimension key is denoted with
the prefix DIM_ID_. Here, 'DIM_ID_MATERIAL' is the dimension key for the
material dimension table.
As in the classic star schema, the primary key of the fact table is made up
of dimension keys ('DIM_ID_DATENPAKET', 'DIM_ID_ZEIT', 'DIM_ID_EINHEIT',
'DIM_ID_KUNDE', 'DIM_ID_MATERIAL').
Page 11 of 197
SAP BW
The excavation of master data from the dimension tables using SID
technology allows you to use the same master data with different
InfoCubes. In other words, the master data is InfoCube-independent, and
can be used by several InfoCubes at the same time.
Page 12 of 197
SAP BW
Page 13 of 197
SAP BW
excavation of master data from the dimension tables using the SID
technique, the following modeling possibilities exist:
• Historizing dimensions
• Multi-lingual capability
• Cross-InfoCube use of master data ("shared dimensions")
• The query performance is improved here, as aggregated key
figures can be stored in their own fact tables.
Page 14 of 197
SAP BW
1.6.1. Modeling
The Modeling function area is used to create and maintain (meta) objects
relevant to the data staging process in SAP BW. These objects are displayed
in a tree structure, in which the objects are ordered according to
hierarchical criteria. You can use a context menu (using the Right mouse
click) to access the relevant maintenance dialogs for each object in the
object tree. You can also carry out additional functions. To access the
Modeling function area, choose transaction RSA1.
1.6.2. Administration
In the Modeling and Administration functional areas is used to display the
navigational area and, if applicable, the corresponding object tree in the
left hand area of the screen when applications are called. This means that
you can use the tree to start new application you are in.
Page 15 of 197
SAP BW
quality assurance into the productive system, for example). To access the
Transport Connection function area, in the AWB navigation window, choose
Transport Connection.
1.6.4. Documents
The Documents function area enables you to insert, search in, and create
links for one or more documents in various formats, versions and languages
for SAP BW objects. To access the Documents function area, in the AWB
navigation window, choose Documents.
1.6.5. BI Content
BI Content provides pre-configured information models based on metadata.
It provides users in an enterprise with a selection of information they can
use to fulfill their tasks. To access the BI Content function area, choose the
transaction RSORBCT.
1.6.6. Translation
In the Translation function area, you can translate short and long texts
belonging to SAP BW- objects. To access the Translation function area, in
the AWB navigation window, choose Translation.
Page 16 of 197
SAP BW
Note:
• There can be up to 248 characteristics per dimension table
Page 17 of 197
SAP BW
Key Figures – A key figure is a data element from a fact table and usually
represents numeric data that can be measured, such as revenues and gross
profit. The key figure InfoObjects provide the values to be evaluated. E.g.
Quantity sold (0QUANTITY), Amount (0AMOUNT), Headcount etc. In other
words, they represent the facts in the conventional data warehouse.
Units - The Unit InfoObjects enable key figure values to be associated with
their corresponding units in evaluation. E.g. Currency unit (0CURRENCY) can
be associated with the key figure Amount (0AMOUNT) and value unit (0UNIT)
with Quantity (0QUANTITY).
Page 18 of 197
SAP BW
In SAP BW, all dependent objects need to be activated before they can be
used, including InfoObjects, InfoCubes, transfer rules, communication
structures, and so forth. Additionally, custom InfoObjects can be created
(e.g., to define a custom data file).
You can use these tab pages to define characteristic InfoObjects and change
their settings. A precise knowledge of the business significance of these
characteristics is required before you can define them in a meaningful way.
General
Page 19 of 197
SAP BW
Page 20 of 197
SAP BW
SAP Business Explorer also allows displaying the data on maps (World map,
Continent maps etc.). Some third party vendors like ESRI, provide special
type of files called as Shape files that serve as a basis for displaying BW
data on maps. The related settings can be done using the BEx tab.
Master data/texts
On this tab page, you determine whether or not the characteristic can have
attributes or texts. If the characteristic is to have its own texts, you need
to make at least one text selection (short, medium-length, long text- 20,
40, 60 characters). The attributes are assigned to the characteristic on the
Attributes tab page.
Page 21 of 197
SAP BW
Attributes
Attributes are themselves InfoObjects (characteristics/key figures) that are
used to describe characteristics in greater detail. For example, the
characteristic Customer Number can be described in more detail with other
InfoObjects like Customer Type and Customer Class, Address etc. If the
With master data indicator was set on the Master data/texts tab page you
are able to specify attributes and properties for these attributes together
with the characteristic on the Attributes tab page.
Page 22 of 197
SAP BW
A characteristic that is used as a navigation attribute can also have its own
navigation attributes. These are called transitive attributes (navigation
attributes with two levels). You can activate these as well, thus making
them available for reporting.
Page 23 of 197
SAP BW
Note:
• If a characteristic InfoObjects is defined as Attribute Only, you can
only use this characteristic InfoObjects as a display attribute for another
characteristic.
• The extensive use of navigation attributes leads to a large
number of tables and joins, which can reduce performance.
(External) Hierarchy
Hierarchies are used in analysis to describe alternative views of the data. A
hierarchy comprises of multiple nodes and leaves. The nodes stand in a
parent-child relationship and the hierarchy leaves are represented by the
characteristic values. On the Hierarchy tab page, you determine whether or
not the characteristic can have hierarchies, and if so, what properties these
hierarchies are allowed to have. If the ‘With hierarchies’ indicator is set,
hierarchies can be created for this characteristic within SAP BW (choose
transaction RSH1). Alternatively, they can be loaded from SAP R/3 or flat
files.
Remarks:
Changes for hierarchies are available only after the “data change aggregate
update” program has been run. This is true even if there are no aggregates
associated with the hierarchies.
When using hierarchies you should filter out the ‘Not assigned’ node in the
hierarchy. Often the user does not notice that all nodes are included in the
Page 24 of 197
SAP BW
output (even the ones that are not needed or blank), but it slows down the
query result because a lot of useless data is being selected.
A Version-Dependant Hierarchy
Hierarchies for a characteristic can be maintained in different versions.
These versions can then be compared with one another in a query. E.g. As
shown in the Table 2.1, District 2 is placed under North region in the
planned version but is under South region in the actual version.
Page 25 of 197
SAP BW
Hierarchy Hierarchy
01.01.2000 – 31.12.2005 01.01.2006 – 31.12.2009
Region NORTH Region NORTH
District 1 District 1
District 2 District 3
District 3
Page 26 of 197
SAP BW
Hierarchy Intervals
It is possible to position characteristic values in the form of intervals under
a hierarchy node. Instead of positioning each cost element value for
material costs under the material costs node individually in a cost element
hierarchy, you can specify the cost element values as a cost element
between 100 and 1000. You can also create intervals for characteristic
values, for which no master data exists. As a result, you can save yourself
the need to extend the hierarchy every time for new master data.
Note:
• You cannot create hierarchies for characteristics that are
referenced to other characteristics (Reference characteristic).
• A characteristic can have more than one hierarchy.
• If a characteristic is to have hierarchies; the maximum length
(of the characteristic value) with compounding is restricted to 32
instead of 60 characters.
• Hierarchies can have a maximum of 98 levels.
Compounding
In Compounding, a field or another object is attached to an InfoObject. A
compounding characteristic is when the object’s definition is incomplete
without the definition of another characteristic. In other words the meaning
of master data depends on the source of the data.
Page 27 of 197
SAP BW
Example:
Cost center 100 stands for sales and distribution in controlling area 1000,
and it also stands for sales in controlling area 2000. In this case, you would
define a "cost center" to "controlling area" characteristic compounding.
Page 28 of 197
SAP BW
2. Create/maintain an InfoArea
4. Choose Create InfoObject via the context menu for the InfoObject
Catalog.
Page 29 of 197
SAP BW
• General
• Business Explorer
• Master data/texts
• Hierarchy
• Attributes
• Compounding
Page 30 of 197
SAP BW
2.5.1. Type/Unit
On this tab page, you determine the key figure type (amount, quantity,
number etc.), the data type (currency field / floating point number,
quantity filed/ floating point number etc.) as well as the currency /
quantity unit.
Page 31 of 197
SAP BW
For the key figure types amount, quantity and number, you can choose
between the data types decimal number and floating-point number. For the
date and time key figure types, you can choose the decimal display if these
fields are to be included in the calculation. If you choose the amount or
quantity key figure type, you must assign a currency or quantity unit to this
key figure. For the key figure type amount, you can choose between a fixed
currency (EUR, for example) and a variable currency, (OCURRENCY) for
example.
For the key figure type quantity, you can choose between a fixed quantity
unit, KG for example, or a variable quantity unit, OUNIT for example.
2.5.2. Aggregation
Default BEx settings for aggregation of the key figure are done using this tab
page. This is required for the meaningful evaluation of the key figure. The
aggregation behavior determines whether or not, and in which way, the key
figure values can be summarized using the different characteristics/their
values within the evaluation.
Page 32 of 197
SAP BW
2.5.3. Aggregation
In this field, you specify the function (SUM/MAX/MIN) which determines the
way in which the key figure is aggregated "by default" for the same key (--
>standard aggregation behavior).
Example:
The key figure number of employees is aggregated using the characteristic
cost center ( Standard aggregation behavior). In this case, you would set a
time characteristic as a reference characteristic with last value as the
exception aggregation.
Non-cumulative values (warehouse stock, for example) are key figures that
are only evaluated for selected time periods (markers).
The values for the remaining periods are calculated from the value in a
marker and the non-cumulative changes (in-/out- flow) that lie in between.
Page 33 of 197
SAP BW
Page 34 of 197
SAP BW
Enter the technical name (3-9 characters) and a long description for the
key figure (either a reference key figure or a template key figure) and
confirm your entry. (You need a reference characteristic for an
‘Elimination of Internal Business Volume’ in the query.)
2.6. InfoCubes
A cube is synonymous with a star schema, which means it consists of a fact
table and a surrounding group of dimension tables, all of which contain data
that logically belong together, and are linked relationally. Cubes are the
central objects, upon which reports and analyses are based in
multidimensional modeling. InfoCubes are the central objects of the multi-
dimensional model in SAP BW. Reports and analyses are based on these. An
InfoCube describes a self-enclosed data set for a business area from a
reporting perspective. Queries can be defined and/ or executed on the basis
of an InfoCube. InfoCubes contain the transaction data in multidimensional
format. In SAP BW a cube is called an InfoCube.
Page 35 of 197
SAP BW
Only BasisCubes physically contain data in the database. By doing so, they
are also data targets. In contrast, Virtual Cubes only represent logical
views of a dataset. There is no difference between these InfoCube types as
far as the reporting end user is concerned. Queries can be defined based on
all the above InfoCube types. InfoCubes are thus InfoProviders.
2.7. BasisCubes
As already mentioned, a BasisCube consists of a quantity of relational tables
arranged together in a star schema.
. Fact table
A BasisCube consists of one fact table, in which key figure values are
stored. A fact table can contain a maximum of 233 key figures.
Page 36 of 197
SAP BW
Fact
A fact is a measure that is normally (cumulative) and answers the question
“how much?” or “how many?” A fact is referred to as a key figure in the SAP
BW extended star schema. Revenues and expenses are examples of typical
facts. Examples of non-cumulative facts include closing stock price, daily
movements, or inventory levels.
Fact Table
Facts, of course, reside in a fact table. A fact table is the central table in a
star schema. It contains key figures and dimension IDs that point to the
dimension tables. In a star schema, typically
• The fact table is very large with small dimension tables.
• The fact table has a relatively small number of columns (key
figures) and a large number of rows (records) where
associated dimension tables tend to have a large number of
columns (attributes) and small number of rows.
Dimension
A dimension is a textual description of the dimensions/features of the
business. The dimension answers the questions “who? what? when?” For
example, the dimensions of a product may include product name, brand
name, size, and packaging type. Dimensions are stored in dimension tables.
The term dimension refers to dimension tables, and characteristics will be
used as the content of dimension tables.
Page 37 of 197
SAP BW
to access the Unit dimension table during queries, which may cause
degradation in system performance. Therefore, for query
performance, key figure InfoObjects of type Number or Integer
should be used whenever possible (unless you really plan to do
currency/unit conversions in the queries).
Page 38 of 197
SAP BW
Dimensions
A dimension in SAP BW is nothing but a grouping of logically related
characteristics under a single umbrella term. A maximum of 248
characteristics can be combined within a dimension.
Remote Cube
A Remote Cube is also called a Virtual Cube. It is an InfoCube whose
transaction data are not managed in SAP BW but in a remote system.
Page 39 of 197
SAP BW
• SAP Remote Cubes. The SAP Remote Cube is a Remote Cube that
allows the definition of queries with direct access to transaction data
in other SAP systems.
Page 40 of 197
SAP BW
Or:
You can insert InfoObjects without selecting a template in the left half of
the screen. This is useful if you know exactly which InfoObjects you want to
include in the InfoCube. Choose Insert InfoObjects in the context menu for
the folders for dimensions or key figures. In the dialog box that appears,
you can enter and transfer up to ten InfoObjects directly, or you can select
them using input help. You can use Drag&Drop to reassign them.
Note: You can mark a dimension as a line item dimension. In addition, you
can also set the Card. Height indicator to indicate high cardinality. This is
used if the dimension has at least 10-20% the size of the fat table in terms
Page 41 of 197
SAP BW
The number of partitions depends upon the span of time for which the
data is stored in the InfoCube and the actual volume of data. E.g. As
shown in the Figure 2.17, out of total 62 partitions, 60 partitions
correspond to months ranging from January’2001 to December’2005.
One partition is for the transaction data before January’2001 and one is
for the data after December’2005.
Note: Except for the text table, hierarchy table and E tables, you can view
the various tables generated using the transaction LISTSCHEMA.
Page 42 of 197
SAP BW
Page 43 of 197
SAP BW
The graphic shows the structure of the text table, for characteristic
COSTC##: in this example. Since the indicators for short text, medium-
length text, time and language-dependence were set on the Master
data/texts tab page, these fields are included in the structure of the text
table.
Legend:
"Compounded" characteristic
{...}
/BIC/<...> Newly-created characteristic
LANGU Language key
DATETO Date valid to
DATEFROM Date valid from
TXTSH Short description (20 characters)
TXTMD Medium-Iength description (40 characters)
TXTLG Long text description (60 characters)
Page 44 of 197
SAP BW
Page 45 of 197
SAP BW
OBJVERS has two statuses: A = Active (the data can be used for reports) and
M = modified/revised.
CHANGED also has two statuses: I = Entry marked for insertion and D = Entry
marked for deletion.
Page 46 of 197
SAP BW
Example:
Page 47 of 197
SAP BW
2.9.4. Hierarchies
The hierarchy table (H table) is used to store the hierarchical relationships
between characteristic values, when external hierarchies are used for the
characteristic. Only one H table is ever generated even if a characteristic
contains several hierarchies. In other words, the H table contains all
hierarchies.
Page 48 of 197
SAP BW
Page 49 of 197
SAP BW
Legend:
HIEID - Internal hierarchy ID (unique ID)
NODEID -Internal ID number of a hierarchy node
IOBJNM - InfoObject
NODENAME - Name of the hierarchy node
TLEVEL - Level of a hierarchy node
LINK - Link indicator for a hierarchy node
PARENTID - Parent ID for a hierarchy node
CHILDID - Child ID of a hierarchy node
NEXTID - Next ID of a hierarchy node
INTERVL - Indicator: Node is interval
In this graphic, you can see the content of the H table after a hierarchy was
loaded into SAP BW for characteristic 0COUNTRY, or after a hierarchy was
created and activated (simplified display) in SAP BW. Setting the indicator
in the INTERVL field permits intervals in this hierarchy, which means these
are modeled in the J table. The second row of the example hierarchy is
looked at more closely to help you better understand the structure of the
table. You can see from the NODEID field that this is the second node of this
hierarchy. The PARENTID field shows that the superordinate node has
NODEID 1. In this example, the superordinate node is the root node. The
CHILDID field denotes the subordinate node and the NEXTID denotes the
adjacent (next) node. In this example, the subordinate node is Austria and
the adjacent node is the USA
Page 50 of 197
SAP BW
2.9.6. S Table
The S table is generated when a characteristic is activated. With one
exception: When a characteristic is defined exclusively as an attribute. In
other words, this characteristic can only be defined as the attribute of a
master data-carrying characteristic in a different scenario. The graphic
shows the structure of an S table. The key of this table is the characteristic
for which the artificial key was generated. If the characteristic is
compounded, the key is also made up of the compounded characteristic.
The SID keys are automatically generated by the system when master data
is uploaded.
The following graphic illustrates the relationship between the S tables and
the tables belonging to the master data-carrying characteristic COSTC##.
The diagram has been simplified to make it easier to understand.
Page 51 of 197
SAP BW
Page 52 of 197
SAP BW
Page 53 of 197
SAP BW
Inclusion Table
In theory, this table contains the same information as the H table, meaning
that it displays the relationships between nodes/nodes and nodes/leaves.
Here, the leaves (characteristic values) are assigned positive SID values and
the nodes are assigned negative SID values (K table). The following graphic
shows the I table for a characteristic with a time-independent hierarchy.
Page 54 of 197
SAP BW
Legend:
SID - SID of node within the hierarchy
OSID - SID of node, original value
LINKNO - Link number
SVER - Version in key of inclusion table
PRED - Master data ID (predecessor)
SUCC - Master data ID (successor)
LISTNO - Sequence of inclusion relationships
FACTOR - Factor with which the inclusion relationship enters the nodes
NTYPEID - Internal ID for the node type
In this graphic, you can see example K and I tables after a hierarchy was
loaded into SAP BW for characteristic OCOUNTRY, or after a hierarchy was
created and activated (simplified display) in SAP BW.
Page 55 of 197
SAP BW
InfoCube Tables
This section looks at the structure of the dimension tables and the F- and E
tables.
Dimension Tables
When defining an InfoCube, characteristic InfoObjects are selected to be
components of this InfoCube. They are then assigned to your user-defined
dimensions. After the InfoCube is activated, the dimension tables are
generated.
Legend:
[…] Technical name of InfoCubes
# Numeration of the dimensions automatically allocated by the system.
The DIM numbers contain the following elements: P, T, V, 1, 2... 9, A, B, C,
D.
P Data package
T Time
U Unit
Page 56 of 197
SAP BW
A 10
B 11
C 12
D 13
The structure of the fact tables in the SAP BW star schema is the same as
that in the Basis star schema. The keys of the dimension tables (DIM IDs) are
the foreign keys of the fact table. Each row of the fact table is uniquely
identified by a combination of DIMID values.
The F table is optimized for data loading, since the data is always
automatically partitioned using the package dimension. As a result, you are
able to administer each individual data request separately. The E table is
optimized for data requests, since the DMID of the package dimension is set
to zero, thus reducing the key combination. Data records having the same
key values are compressed. The figure 50 shows the relationship between
fact tables and dimension tables.
Page 57 of 197
SAP BW
Transaction LISTSCHEMA shows you tables for the structure of the InfoCube.
In addition, you can also display the attribute tables for the characteristics
involved in the InfoCube. Hierarchy tables, text tables and the E table are
not shown.
Page 58 of 197
SAP BW
3.1.1. Definition
Page 59 of 197
SAP BW
The figure 1.1 illustrates an example of a data update from the DataSource
to an InfoProvider. The data can be updated from an InfoProvider to
another InfoProvider using a data transfer process. The data transfer
process can also be used to control data distribution from a BI system into
any target outside of the BI system. For this purpose, a data transfer
process with an open hub destination is used as the target. The following
are the ways of data transfer:
• The InfoPackage controls the transfer of data from the source to the
entry layer of BI.
• The data transfer process controls the distribution of data within BI.
• By using Infospoke BI can be used as the source system, whereby he
data can be loaded from BI to any other destination.
Page 60 of 197
SAP BW
Within SAP Netweaver 2004s infopackages can only load data from source
system to PSA without any semantic transformation. What can be done here
is a technical transformation (e.g. conversion exit to transform data from
external format to internal format). Transformations can be defined
between a source and a target for data transformation or conversion. DTP is
responsible for data loading from one persistent layer to the other. Every
path from persistent source to target is a DTP. This means that besides
InfoSource any other objects like InfoProviders, DataSources, DSO can be
the source or target for the DTP. Consider the following example:
• Infopackages only can load data from Source System to PSA without
any semantic transformation
• PSA will physically store the data
• Data can be loaded from PSA to DSO via DTP
• All the infopackages and DTPs should be included in process chain for
automations.
Page 61 of 197
SAP BW
Page 62 of 197
SAP BW
Page 63 of 197
SAP BW
Page 64 of 197
SAP BW
In update tab we can decide the type of error handling. There are 3 types:
• ‘No Update, No Reporting’ – Once errors occur, the whole data
package is terminated. The request is not released for reporting
• ‘Valid Records Update, No Reporting (Request Red)’ – Valid records
are only updated but data is available for reporting only after
manual processing of the request
• ‘Valid Records Update, Reporting Possible (Request Green)’ – Valid
records are updated and also available for reporting
Page 65 of 197
SAP BW
• Within the execute tab we can see all the process steps during the
data loading
• Process step filters out records with the same key
• It means if error handling is switched on and there are infoobjects
which have the update mode ‘overwrite’ in the transformation, new
records with the same key at the incorrect records will be filtered
out during data loading
Page 66 of 197
SAP BW
Page 67 of 197
SAP BW
Page 68 of 197
SAP BW
• Key of the error stack can be defined in the Semantic Groups option
• Maximum 16 key fields are possible
• It defines which data should be detained from the update after the
erroneous data record (for DSO)
• By default the key is same as complete target key (key of DSO)
Page 69 of 197
SAP BW
The Order Number field is the key for the error stack. During the
transformation, data record 02 of request 109882 is marked as containing
errors. In addition to the erroneous data record, all subsequent data records
for the request that contain the same key are written to the error stack. In
this example, this is data record 03. This ensures that when error records
are updated with the error DTP, the records are serialized correctly and
newer data is not inadvertently overwritten by older data.
During the transformation, the data records for request 109882 are
aggregated to one data record. If, for example, there is no SID for the
Page 70 of 197
SAP BW
The Order Number field is the key for the error stack. During the
transformation, data record 02 of request 109882 is marked as containing
errors. In addition to the erroneous data record, all subsequent data
records, including the following request that have the same key are written
to the error stack. In this example, data record 01 for request 109883 is
written to the error stack in addition to data record 02 for request 109882.
Page 71 of 197
SAP BW
The Order Number field is the key for the error stack. During the
transformation, data record 01 of request 109883 is identified as
containing errors. It is written to the error stack. Any data records from the
previous request that have the same key were updated successfully to the
target.
Page 72 of 197
SAP BW
• In the temporary data storage we can see all records – correct and
incorrect. Incorrect records are marked with a special symbol.
• In the error stack we can see only incorrect records. Here we can
correct these records manually.
Page 73 of 197
SAP BW
Page 74 of 197
SAP BW
Page 75 of 197
SAP BW
Page 76 of 197
SAP BW
5) Once Error DTP gets created, we can check the status of Standard DTP
which is changed from create to display, and can also check the Error DTP
under the Object for which we created the standard DTP.
Page 77 of 197
SAP BW
6) Error DTP
Page 78 of 197
SAP BW
8) In the Error DTP process monitor it’s showing 3 records that we corrected
in Error Stack in earlier steps.
9) We can also check the status of Standard DTP, it’s also Green now
(without errors).
Page 79 of 197
SAP BW
10) We can also check the records updated status of Standard and Error DTP
in the manage tab of data target.
The graphic displays the initial screen for InfoCube Management, including
the tab pages mentioned above.
3.8.2. Contents
This tab page lists all characteristics involved in the BasicCube for the
associated dimensions. Via InfoCube Content, you can display the key figure
Page 80 of 197
SAP BW
values for the BasicCube, as well as the characteristics, SIDs for the
characteristics and key figures of the Cube via a view. Fact Table can be
used to display a list of all dimension keys and key figures for the individual
transaction data records (the fact table content).
Via Selection, you can use a pre-selection to delete the data records
matching these selection criteria from the BasicCube. If you select the cost
center having cost center number T900000004250, all data records with this
value are deleted from the BasicCube.
Choose Contents tab, then click InfoCube content button, the following
screen is displayed
Page 81 of 197
SAP BW
• Choose Do not use any conversion to display the data in the database
formats
• Choose Use mat. Aggregates to display the data from an aggregate
instead of the fact table if an appropriate aggregate exists
• Choose Use DB aggregation to allow aggregation on the fields that
are not the selection condition
• Choose Output number of hits to add a new column in the display to
show how many records in the fact table are used to produce each
display row
• Choose Display modified structures to display the M version master
data. You use this option to check how the result would look in BEx
should the characteristic data be activated
Page 82 of 197
SAP BW
In this pop-up window, we can specify the data to be deleted and how to
delete them by clicking Delete selection button.
3.8.3. Performance
This tab page allows you to influence load and query performance using the
Delete Indexes, Repair Indexes and Create Index (Batch) functions.
Page 83 of 197
SAP BW
Note that the status light should always be green. If no index/statistics data
exist, the status lights will be red.
Depending on the size of the InfoCube, it may take some time for the
status light to turn green/red
To improve data loading performance, it is recommended that you
delete the indexes, load the data, and the recreate the indexes. To
automate this job, click Create Index button
Page 84 of 197
SAP BW
Check all the options and click Execute Changes button. Pl note that the
next time when you load data into this InfoCube, you will receive a
message, just click Yes button
Indexes are use to locate needed records in a database table quickly. SAP-
BW uses two types of indexes B-tree for database tables and bitmap indexes
for fact tables and aggregate tables. 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. The cost based optimizer uses statistics to calculate the cost of
available execution plans and select the most appropriate one for
execution.
3.8.4. Requests
All requests (data requests) that were loaded into the BasicCube are
displayed on this tab page. In BW, each data load from BW Scheduler is
considered as a request and is assigned a unique request number consisting
of 30 characters and is stored as an integer value called a request id, in the
data packet dimension of the InfoCube.
You can also delete request where required. The system displays whether
requests have been scheduled for aggregation or already aggregated. You
can also see whether requests have been compressed or have been
scheduled for deletion.
Page 85 of 197
SAP BW
You can enter an update period in the Request Display row to restrict the
number of displayed requests.
On the Request tab page, you can see the status (red, yellow, green) of
previous data load processes. The following table shows the values of the
request ID status:
Page 86 of 197
SAP BW
Each request has its own unique number (request ID). You can see this in
the following graphic. By using a request ID (a unique key generated by the
system) to indicate each request, the system can maintain a chronological
update history. It allows the system administrator to identify specific
upload sequences that had errors.
During extraction, the data requested in each request is taken from the
source system and packed in packages within the request, before being
loaded into SAP BW.
When executing a query, data packages with the status "red" or "yellow"
cannot be taken into consideration. Data packages having status "green"
that are loaded at a later time are also not used in the query here. If this
were not the case, the consistency of data within the query could not be
guaranteed.
To delete a request from the InfoCube, click Delete button. If the request
has been rolled up into an aggregate or compressed, then you cannot delete
it. If it has been rolled up, then the aggregate must be deactivated first. If
it has been compressed, then all data in the fact table must be deleted
first.
BW provides a useful function that allows us to check whether one data load
request overlaps with another. For that select request 31501 and then click
Page 87 of 197
SAP BW
A new session window opens and displays the request’s 30 character request
number
Page 88 of 197
SAP BW
3.8.5. Rollup
If activated and filled aggregates exist for the BasicCube and you then load
new requests into the BasicCube, you need to roll these up into the
aggregates as well.
3.8.6. Compress/Collapse
As mentioned above, each data load process is uniquely identified within a
BasicCube using a request ID, which is included in the package dimension.
This allows you to look at individual requests in detail. Using request Ids can
have the effect that a data record with the same content (where all
characters are the same except for the request ID) appears more than once
in the fact table. The result is an unnecessary increase in the data volume.
The greater data volume reduces performance in Reporting, since every
time a query is executed; the system accesses data via the request ID. This
is because data records are only aggregated within a request. To save
storage, space and improve read performance, you can compress a
BasicCube, whereby the request ID is set to null. Data records with the
Page 89 of 197
SAP BW
same dimension key are aggregated. During compression, data records are
written to the BasicCube E table and the compressed requests are removed
from the F table. Newly requested requests are written again to the F table
and can then be compressed if required (see graphic).
Page 90 of 197
SAP BW
For instance, we want to compress request 31839, enter 31839 into the
Request ID and then click . BW will compress 31839and
request below 31839. However, to delete records whose key figures are all
0, select the With Zero Elimination.
On order to delete a compressed request, we must either delete all off the
E Fact table data or use the Request reverse posting (Read everything in
manually) function in the Monitor-Administrator Workbench.
Page 91 of 197
SAP BW
3.8.8. Reconstruct
You can use this function to reconstruct requests that were already rolled
up into a BasicCube and that have since been deleted (update requests into
the BasicCube).
This function can only be used when the data is held in the PSA.
By accessing the Contents tab page in BasicCube management, you are able
to extract BasicCube data into an external file, or a new or existing DB
table. This is useful in situations where some of the collected data is to be
used in other analysis tools (for example, a different planning tool than SAP
Page 92 of 197
SAP BW
The system transfers the data after you confirm your entries. By default,
the data is returned as a display list.
BW Monitor enables us to trouble shoot during the load process. Simply put,
you may use BW Monitor to display the status of data loads and find out
when, where, and how errors (if any) occurred.
Page 93 of 197
SAP BW
• We see the status of all data load (successful and failed). Double
click on the last failed load operation to get the details.
Page 94 of 197
SAP BW
• Under the Details tab page, we can see how the data flowed and
where the errors have occurred.
Page 95 of 197
SAP BW
To review the status of other data loads, we can click New Selection (F5)
button .
Page 96 of 197
SAP BW
Page 97 of 197
SAP BW
1. Context Menu:
Direct Access to display data
Additional Functions
Page 98 of 197
SAP BW
Page 99 of 197
SAP BW
5) Structure (Tables):
Structure of the Standard Data Store Object is similar to that of the
standard ODS in BW3.5
Contains -
1. Activation Queue
2. Active Data
3. Change Log
Activation Queue:
1. Definition:
2. The uniqueness of the data can be switched off with a check box
Definition:
- This indicator is only relevant for write-optimized Data Store
Objects. The technical key for these objects in the active table
always consists of the fields Request ID, Data Package and Data
Record. The infoobjects that appear in the maintenance dialog in the
folder Key Fields from the semantic key of the Data Store Object.
- If this indicator is set, a unique index with the technical name “KEY”
is generated for the infoobjects in the semantic key.
- If this indicator is not set, the active table of the Data Store Object
could contain several records with the same key.
1. Definition:
2. The Data Store Object for direct update is perfect for using it for
external data.
There is an API available with various function modules:
- BAPI BAPI_ODSO_READ _DATA_UC
- RSDRI_ODSO_INSERT
- RSDRI_ODSO_INSERT_RFC
- RSDRI_ODSO_MODIFY
- RSDRI_ODSO_MODIFY_RFC
- RSDRI_ODSO_UPDATE
- RSDRI_ODSO_UPDATE_RFC
- RSDRI_ODSO_DELETE_RFC
4.3.1. Overview
There is new monitor concept installed for the Data Store Object
administration:
Load monitor like 3.X Monitor
Logs for DSO- request processing
a) Load Monitor:
Header View: Displays all relevant objects which do depend to the transfer
process.
Details View: Displays all the relevant steps with timestamp of the transfer
process.
Parameters Required:
Request ID
Name of the Data Store Object
1. SID Generation:
1. Partitioning/Clustering
3. Indexing:
5 MultiProviders
Sometimes, there are complex reporting demands for which you need to
combine data from several InfoCubes. These complex requests are carried
out using a MultiProvider. MultiProviders enable us to combine any
InfoProviders you choose in order to build a new semantic layer for
reporting, with having to change the data store.
MultiCube only exists as long as a logical definition. The data is still stored
in the InfoProviders on which they are based.
In a MultiProvider, each characteristic of the MultiProvider must match
precisely one characteristic or navigation attribute in each InfoProvider
involved.
Sales Process
• ONUM : Order Number (C)
• CUS : Customer (C)
• PROD : Product (C)
• OQTY : Order Quantity (K)
• OPRI : Order Price (K)
• DQTY : Delivered Quantity (K)
• DPRI : Delivery Price (K)
• BQTY : Billing Quantity (K)
• BPRI : Billing Price (K)
•OOAT : Order Date (C) •DDAT : Delivery Date (C) •BDAT : Billing Date (C)
•SALP : Sales Person (C) •DELP : Delivery Person (C) •BILP : Billing Person (C)
•OQTY : Order Quantity (K) •DQTY : Delivered Quantity (K) •BQTY : Billing Quantity (K)
•OPRI : Order Price (K) •DPRI : Delivery Price (K) •DPRI : Delivery Price (K)
MultiProvider Queries
MultiCube
Sales Process
Info Cube
Delivery
It is both desirable and sufficient for you to select from precisely one
InfoProvider involved in cases where a key figure, for example 0SALES
(sales) is stored redundantly in several InfoProviders (in other words,
entirely contained in all value combinations of the characteristics). If this is
not the case, the value appearing more than once in the MultiProvider
would be incorrectly added. However, if 0SALES is saved, say, as an actual
value in one InfoProvider and as a plan value in another, you must select
from several InfoProviders. This avoids overlaps in the data records (where
the revenue from several InfoProviders is distributed in disjointed form).
1. In the context menu for your InfoArea, right Click and choose Create
MultiProvider…
In the subsequent window, you can select the objects involved in the MultiProvider
viz., InfoCubes/ODS Objects…tab page and the click
6 Aggregates
Most end users need to access only a subset of information. In that case, we
would create a new InfoCube, which contains only that information you are
seeking. This new InfoCube is actually a subset of the original InfoCube.
Because the new InfoCube is smaller, this requires disk I/O volume during
execution will be smaller too, and thus see an improved query performance.
SAP implements this idea in BW and calls the new InfoCube an aggregate.
An InfoCube can have multiple aggregates, and the aggregates are
transparent to users. It means that we create queries on InfoCubes, not on
aggregates. For a query run or a navigation step, the BW OLAP processor is
responsible for selecting an appropriate aggregate. If no appropriate
aggregate exists, the BW OLAP processor will retrieve data from the original
InfoCube.
Too many aggregates may not be feasible because the rollup process takes
time and in spite of the query performance getting improved the ETL
process would take more time.
Country: *
Customer: Empty
Country Sales
Germany 45
USA 30
India 80
Country: Empty
Customer: *
Customer Sales
Siemens 75
ABB 50
P&G 10
Colgate 20
Country: F, India
Customer: *
Country: H, Level 2
Customer: Empty
Country Sales
America 30
Europe 45
Asia 80
• Switch off the aggregate -The aggregate is still filled with data, but is
not used by the OLAP processor.
• Deactivate the aggregate -The aggregate data is deleted. However, the
aggregate definition remains.
• Delete the aggregate - The aggregate data and definition are deleted.
In the above figure, the first request with number 41239 was not rolled up
into the aggregate and is also Request is available for reporting is also not
clicked, hence is not available for reporting. In the RSDDAGGRDIR table, a
read pointer is set to request 40424 in the RNSID_TO field. This read pointer
refers to the OLAP processor, which request is available for reporting during
the query execution.
After the roll-up of request 41239, you see that the reporting request is
available, and the read pointer in the RSDDAGGRDIR table is set to request
41239.
can be executed across all the requests. Data records with the same
characteristic value are aggregated. If a request has to be deleted after the
compression then all aggregates have to be deactivated first. This can take
a long time. If you compress the aggregates first when the InfoCube is also
compressed, then it is possible to delete a rolled-up but not yet compressed
request without taking up a great amount of time.
Read pointers are used to keep aggregate data and cube data in sync.
• Improved performance
• Identification of separate loads of data in the InfoCube and
aggregates
• The RNSID is useful when it is necessary to remove or reload specific
batches of data to/from the InfoCube and aggregates.
• Each data upload has a Request Set ID in the aggregates and the
InfoCube. The RNSID column is hidden in the fact table.
During the realignment run you are only able to report on the old non-
cumulative from attributes/hierarchies. Active versions of the changes
are available when the change run has finished. This also applies to
reporting using InfoCubes that are not affected by the realignment run,
but do use the modified hierarchies and attributes.
You can check which objects are affected by the realignment run by
using the monitor function for the realignment run. This shows you
which characteristics and hierarchies are activated, and which
aggregates and BasicCubes are affected. If the realignment run is active,
then you can see whether the changes are already active for each
aggregate.
To change material HIBE to PAI and Short description to MONEY and then
save the changes. Go to SE16 and type /BIC/PMATERIALC-the name of the
database table. The following screen is displayed.
For material 59, you see that the A in the OBJVERS column indicates that
the corresponding entry is active, and the M indicates that the
corresponding entry is modified and to be activated. The D in the CHANGED
column indicates that the corresponding entry is to be deleted, and the I
indicates that the corresponding entry is new one.
Steps to follow:
Select Apply Hierarchy/Attribute Change… on the tools menu (either from
InfoObjects or InfoProvider tree.
You cannot delete master data if they are used by other BW objects. The
SID table /BIC/SMATERIALC contents are shown in the next screen. The X in
column DATAFL indicates that an InfoCube uses the corresponding entry,
and the X in column INCFL indicates that a hierarchy uses the entry.
7 Admin Cockpit
Your organization works productively with BW. You want to get an overview
of how the system is used, the volume of data and the resources consumed.
You also need constant updates on how the system response time changes
over time.
8 Process Chains
8.1.1. Definition
A process chain is a sequence of processes that wait in the background for
an event. Some of these processes trigger a separate event that can start
other processes in turn.
8.1.2. Uses
In an operating BW system there are a multitude of processes in addition to
the loading process that occur regularly.
Process chains help us to
• Collectors are used to manage multiple processes that feed into the
same subsequent process. The collectors available for BW are:
AND: All of the processes that are direct predecessors must send
an event in order for subsequent processes to be executed.
OR: At least one predecessor process must send an event. The
first predecessor process that sends an event triggers the
subsequent process.
EXOR: Exclusive OR is similar to regular OR, but there is only
ONE execution of the successor processes, even if several
predecessor processes raise an event.
• Collector processes allow the designer of a process chain to trigger a
subsequent process based on whether certain conditions are met by
multiple predecessor processes.
In this chapter we will discuss how to load the appropriate R/3 data into the
new material characteristic ZMATERIAL. Its master data will be extracted
from MARA.
To create a view for the master data, run the transaction SE11, enter a
name for the object, select the views option in the Dictionary objects
block, and then click .
The view consists of one table MARA. Enter this name in Table/Join
Conditions tab page and in view fields, enter all the fields of table 8.1.
To link the text with the master data, the field MATNR of the table MARA
must be equal to the field MATNR of the table MAKT.
Run transaction SBIW and click Maintain Generic DataSource, or you may
run transaction RSO2.
You enter a name ZMARA_ATTR as the name of the DataSource and then
click . The next screen is displayed. Enter all the details in this
screen.
Now you need to create a characteristic ZMARA. Table 9.3 shows the
attributes of the characteristic ZMARA.
Note that the replication of DataSources from the source system SEND001
has already determined the client from which to extract.
To load the Master data and text follow the same steps discussed in the
earlier chapter. However, you need to assign DataSource(s) ZMARA_ATTR
for characteristic ZMARA and for texts choose ZMARA_TEXT.
10 Logistics Cockpit
10.1. What is Logistic Cockpit (LC)?
Fig.1: SBIW
With the LC, several data structures are delivered and, for each level of
detail, there exists an extract structure as well as a datasource (that
already represents a BW extract view).
When you create and save a sales order (as other transactional tasks),
the document is processed in the memory and then stored into
application (and database) tables. In LC extraction technique (see Fig.2)
we have at our disposal different LIS communications structures (like the
MCVBAK, MCVAP, MCVEP and so on for sales orders) that we can decide
to use for our reporting purposes when the application is running and
during memory processing.
In the maintenance screen (see Fig.4), on the left side, you see what has
already been selected in the standard extract structure and on the right
side, you see all the available fields of the communication structures
where you can select fields from for the update.
It’s enough to highlight the row and click on the left-arrow: (every)
selected field is included automatically in a generated append structure
for the corresponding include structure of the extract structure When
you successfully complete this step, the traffic light icon turns red. This
indicates that you changed the structure.
At this point, you have to generate the datasource (see Fig.6): here you
can (among the other things) choose fields that can be selected .For
various reasons, it is not possible to offer all the fields contained in the
LIS communication structure for selection in the extract structure; these
fields are hidden It is also possible that a key figure is inverted (refer to
OSS Note 382779 ‘Cancellation field in the datasource maintenance’ for
details).
Once you activate the update, data is written to the extract structure
and the traffic light then turns green. Our enhancement process is
completed and now you can schedule (if required by your delta method)
the delta job control process. I.e. select the job control process given
below and schedule the job providing the start date and print parameters
at the required frequency (see Fig.6)
Finally, the right choice will be the result of all these considerations; by
doing so, the information structures in BW will be current and overall
performance will be improved.
One the job gets scheduled the records get pulled into the delta queue
(RSA7) in the OLTP system. This will be the source for delta requests
emerging from the corresponding BW system.
about variant values via email or SMS (through background processing in the
Reporting Agent), or to instantly detect such objects in an alert monitor.
You can analyze data in the following areas in the SAP BW BEx:
. BEx Analyzer (Microsoft Excel based)
. In BE Web Applications
Both are seamlessly integrated. In other words, you can display queries
from the BEx Analyzer in a standard view in the Web browser with a single
click. The opposite is also possible, that is, you can export a Web
application into Microsoft Excel 2000.
You can use the BEx Web Application Designer, the desktop application for
creating Web applications, to generate HTML pages that contain SAP BW
specific content such as various tables, charts or maps. You can have the
Web applications as URLs and access them from the Internet, Intranet, or
mobile devices. You can also save Web applications as iViews and integrate
them into an Enterprise Portal.
An assistant, the Web application wizard, has been integrated into the Web
Application Designer to support you when creating Web applications. It uses
an automatic step-by-step procedure and a simplified design process.
Personal digital assistant (PDA) with Windows CE 3.0 and Pocket Internet
Explorer
WAP-enabled mobile telephone
Quit and Use Query: With this function, you leave the Query Designer
and use the query you have defined.
Exit Query: Choose Exit Query if you want to leave the Query Designer.
Your entries are not saved.
Display Query on the Web: Using this function, you can display the query
in a default view on the Web, once you have saved your query definition.
New Query: Choose this function if you want to create a query. The BEx
Open dialog box appears and you can select the InfoProvider here that
contains the data that you want to evaluate in the query.
Open Query: This function takes you directly to the BEx Open dialog box.
The, you can choose from queries in your History, Favorites, Roles, or from
the InfoAreas.
Save Query: You use this function to save a modified query under its
current name. If the query does not yet have a technical name, the system
automatically offers the function Save Query As....
Save Query As...: You use this function to save a query under a new
technical name. You can save the query in your favorites or in a role.
Delete Query: You use this function to delete the query. You can only
delete the query if it is not being used in workbooks, Web templates,
Crystal Reports, or reporting agent settings.
Note: Exceptions are deviations from normal key figure values, as defined
by you, and are highlighted in color in the query view. Using the small arrow
next to the exceptions symbol, you can change or create exceptions. For
more information, see the Exceptions and Conditions unit.
Note: For each characteristic, you 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. Using the small arrow next to the
conditions symbol, you can change or create conditions.
Define Cells: This function is only available for queries with two
structures. You can define formulas and selection conditions for cells
explicitly. In this way, you control the values of cells that appear at the
intersections of structural components. This function enables you to access
individual cells in queries or to assign special values to these.
Check Query: Using this function, you can check a new or saved query
for errors before you save it.
Query Where-Used List: Using this function, you can find out in which
objects (workbooks, Web templates, Crystal Reports, or reporting agent
settings) the query is used.
Display <-> Change: Using this function, you can switch between the
display and change modes.
Change Query (Global Definition): You choose this function if you are in
the Local Query Definition and want to switch to the Global Definition.
Table Display: You can create a query for tabular reporting, as well as
for Online Analytical Processing (OLAP) reporting, by activating or
deactivating the Table Display mode in the query definition when defining a
query. This function is only available for queries with one structure. You
can only have queries with two structures in the multi-dimensional display.
They are not suitable for OLAP reporting.
Technical Name: Using this function, you can show/hide the technical
names of the query components.
Context Menu: This function enables you to display the current context
menu without using the right mouse button (for example, for use with a
touch screen).
Help: This function takes you to the SAP BW online documentation. The
BEx Query Designer section is displayed automatically there in the BEx
documentation.
Using the small arrow next to the help symbol, under the About... entry,
you can see the version of the Query Designer, with the support package
number and the revision.
Once you have selected the InfoProvider, the Query Designer is displayed as
shown in the following graphic.
2. Columns
You define the columns of your report in this area.
3. Rows
You define the rows of your report in this area.
4. Free Characteristics
You transfer those characteristics into the free characteristics areas that
are not displayed in the first instance when you execute the query in the
BEx Analyzer or one the Web. You can then integrate these characteristics
through navigation steps. You can also use free characteristics for selecting
filter values in the report.
5. Filter
The characteristics displayed in the filter appear neither in the drilldown
nor as free characteristics in the query analysis. These characteristics are
only used as global filters on the cube data.
Use Drag & Drop or Choose CTRL C + CTRL V to transfer the characteristics,
key figures, and structures of the InfoProvider into the Filter, Rows,
Columns, or Free Characteristics areas of the Query Designer.
The following graphic shows the Query Designer with a query definition.
Once you have defined a query, choose Save Query or Save Query As... . If
you have not yet saved the query, you have to enter a query description and
a unique technical name. You can also choose where you want to save the
query (in your roles, favorites). You can use Save Query As... to save
existing queries under a different name.
Once you have saved the query, you have the following options:
• You can execute the query in the BEx Analyzer and include it in a
workbook. To do this, choose Quit and Use Query.
• You can display the query on the Web in a default view. To do this,
choose Display Query on the Web.
• You can use the query in the Web Application Designer as a data
provider for Web items.
11.3.BEx Analyzer
Once you choose Quit and Use Query from the Query Designer, a report is
displayed in Microsoft Excel sheet. The report contains the query
description, a filter area and the result area. The filter area contains the
characteristics and free characteristics chosen in the query definition.
IF you do not want to display the values for a characteristic choose Remove
Drilldown from context menu for that characteristic in the filter area.
If you have called the Query Designer, in the SAP BEx Query: Choose Query,
select a query.
You have two options for changing the query definition from a report in the
Analyzer:
• Choose Change Query (Global Definition) : By doing this, you can change
the query definition.
• Choose Change Query (Local View): Changes made to the query here
correspond to navigation in the report and are not saved in the query
definition.
• Query Technical Name: Technical name that you entered when you
saved the query.
• Key Date: Contains the date for which the time-dependent master data
is selected. You create a key date either in the query definition (query
properties) or provide the value using a variable (for more information,
see the Query Properties unit). If no key date has been defined, the
system date is taken as the key date.
• Changed At: Date and time at which the query definition was last
changed.
• Status of Data: Time at which the data from the last request was posted
to the InfoProvider. This can be evaluated for reporting.
• Current User: User who currently has the query open or who has inserted
it into a workbook.
• Last Refreshed: Data and time at which the query data was last
refreshed. This is the time at which you displayed the text elements (the
system has to refresh the query in order to display the text elements).
• Variables, Filter Values, Conditions, Exceptions: Depending on the
current query definition, additional text elements (variables, filter
values, conditions, and exceptions) may also be displayed.
reverse the +/- signs. The reverse +/- signs is only a display function. It
has no influence on calculation in formulas.
• Calculations: You can use this function to recalculate result rows and
individual values that are displayed in the version according to particular
criteria. E. g. You want to calculate the result on the basis of the
average of all displayed sales volumes instead of on the basis of total
sales volume.
• Currency Translation: In the Query Designer you can set a currency
conversion key and a target currency in the properties dialog box for a
structure part.
• Display As: This is where you determine the form in which the
characteristic values are displayed, as long as they were created in the
InfoObject maintenance for the characteristic:
No Display
Key and Name
Name and Key
Name
Key
Long or Medium Name
Display of Results
• Suppress Results Rows: You can structure the appearance of your report
by using this function to determine whether the results rows are
displayed Always, Never or With Only One Value.
• Normalized to: You can use this function to normalize key figure values
to a specific characteristic. When values are normalized, the key figures
are displayed as a percentage in relation to the chosen result. You can
select the Query Result, Overall Result and Result (interim result) as the
reference value. The characteristic is normalized only if it is in the
drilldown.
• Sorting: You can make settings for sorting within the characteristic. You
can use the following:
The characteristic itself, sorted by key or name,
All attributes of the characteristic sorted by Key or Name
The sort sequence is either Ascending or Descending. You cannot use
the attribute that you have selected for sorting in the display.
11.3.7.1. Attributes
Characteristics can be described in more detail through attributes. For
example, you can assign the attribute Telephone Number to the
characteristic Sold-to Party to display the telephone number of the sold-to
party.
You assign attributes to characteristics in the InfoCube maintenance. You
can maintain them as purely Display Attributes or as Navigation Attributes.
You can use Navigation Attributes for defining queries in reporting in the
same way as characteristics. They are displayed in the dimension of the
characteristic to which they belong.
The following figure shows the definition of a restricted key figure, which
will give the Sales amount only for year 2002.
The following is a snapshot of a report, which uses the restricted key figure
defined above to compare overall sales with the sales made in year 2002.
The following snapshot of a report shows the use of the calculated key
figure defined above.
11.6.Variables
For flexible reporting we often need variables. Variables are query
parameters that you define in the Query Designer and that are filled with
values only when you execute the query or Web application.
Variable Types
There are different variable types, depending on the object (for example,
characteristic, formula) for which the variable is defined as a placeholder.
When using the Between operator, you can restrict both limits using single
value variables or choose a single value variable for one of the interval
limits and transfer a fixed value for the other interval limit on the Fixed
Values tab page.
When using the operators Greater than or equal to, Less than or equal to,
Greater than, or Less than, from the list of available variables in the left
window, highlight a variable and move this using Drag & Drop or the arrow
button into the right Selection window.
You enter a default value when you create the variable. This default value
is then displayed for input-enabled variables in the input field of the
variable screen. For fields that are not input-enabled, the default value is
used as the variable value.
. Replacement Path
The processing type Replacement Path enables you to specify the value that
automatically replaces the variable when the query or Web application is
executed.
. Authorization
The Authorization processing type enables you to fill the variables
automatically with the values frothed authorization of a user. If you choose
the Authorization processing type when you create a variable, the variable
is filled automatically with the values in the user’s authorization.
When the user opens a query, the data selection is automatically carried
out according to his or her authorizations.
. Customer exit
If necessary, you have the option of using a customer exit to set up a
processing type for variables that is tailored specifically to your needs. The
Customer Exit processing type for variables enables you to determine values
for variables by means of a function module exit. The function module used
is EXIT_SAPLRRS0_001.
. SAP Exit
The SAP exit processing type is contained in variables that are delivered
with SAP BW Business Content. Overview of Variable Types and Processing
Types
Introduction
The first dialog step in the variable wizard explains that instead of defining
fixed values for your query, you can define variables as placeholders that
are then filled with values at runtime. If you do not want to display this
step in the future, put a check in the Do not display this step in future box.
General Information
The type of variable is shown in the second dialog step. You determine the
variable type by calling up the variable wizard in a specific context.
Context-Sensitive Entries
The following appear differently, according to context:
Details
Default Values
Replacement Path
Characteristic
Currencies and Units
Details
A dialog step in the variable wizard in which all types of variables appear
except for variables with the replacement path processing type.
The variable wizard automatically offers you only those options that are
possible and useful.
3. Under Ready for input you can determine whether the variable is input-
enabled when the query or Web application is executed. If the ready-for-
input option is active (= default setting), the variables screen is offered
when you execute the query or Web application. You can then enter the
required values, confirm the default values, or change the default values.
4. The option Can be changed in query navigation enables you not only to
select from values that you entered in the variables screen after you have
executed the query, but also use other values as dynamo ic filters in the
query.
Default Values
When you define a variable, you enter one or more default values. These
then appear in the variables screen when you execute the query or Web
application.
Replacement Path
A dialog step of the variable wizard that appears for characteristic value
variables, formula variables, and text variables with the replacement path
processing type.
There are different options for the replacement path, according to the type
of variable used:
. Text variables and formula variables with the Replacement Path
processing type are replaced by the corresponding characteristic value.
The value for a formula variable has to be a number. The value for a text
variable has to be a text.
1. Under Replace Variable With, you have the following options:
Key
External Characteristic Value of the Key
Name (Text)
Attribute Value
Hierarchy Attribute
2. Using the setting With Interval Take, you determine whether the From-
Value, the To-Value, or the Difference is used as the value when the value
to be replaced is an interval.
3. The setting Offset Start and Offset Length enables you to determine the
start and the length of the text output.
4. The Evaluate as Boolean function (value 0 or 1)
This function is only available for formula variables. If you select this
setting, the formula variable is not replaced by a value (for example, key
value), but rather it specifies that a value exists.
2. Enter a name and a description for the variable and choose the
Replacement Path processing type.
3. You reach the Replacement Path dialog step. Enter the name of the
query (for example, Top 5 Products)
4. You reach the Save Variable dialog step.
5. You can now insert the variable into the query (Sales Volume – Calendar
Year/Month) to determine how the sales volume of the 5 products with the
highest sales volumes has developed on a month-by-month basis.
Note: Each time that the query Sales Volume – Calendar Year/Month is
executed, the pre-query (Top 5 Products) is executed beforehand. This can
lead to long runtimes. If you do not absolutely need to execute a pre-query
(for example, you do not have to calculate the top 5 products every time
since these change only monthly), we recommend that you use a variable
that represents a precalculated value set.
Characteristic
A dialog step of the variable wizard that appears for text and formula
variables with the Replacement Path processing type.
In text and formula variables with the Replacement Path processing type,
the characteristic reference is not clear in the system. Therefore, select
the characteristic to which the variable refers.
The individual fields of the dialog box reflect the dialog steps in the
variable wizard and show the current settings of the variable. The dialog
box is context sensitive, which means that only the fields and options that
are relevant for the variable are displayed, depending on the type of
variable and the processing type. If you would rather make your changes
using a step-by-step processes with explanatory text, you can go to the
variable wizard.
11.7.Content Variables
Business Content variables are delivered for all types of variables. You have
to activate the variables delivered before you can use them. Variables that
are delivered with Business Content from SAP BW often have the SAP exit
processing type. This enables you to create complex queries quickly and
easily.
In the Metadata Repository, you find the variables that were created for the
InfoObjects used. You also find information about whether the variable in
question is actively available in the system.
11.8.Exceptions
The readability of a report improves if the threshold values are shown with
different colors. This is done using Exceptions on a query level.
11.9.Creating Exceptions
You create an exception in the Query Designer using the symbol Exception
New Exception.
In the dialog box that appears, you can specify a meaningful Description and
set the exception to Active. The exception is applied as soon as you execute
the query. If you do not set the active flag, you can activate the exception
in the report itself. In the BEx Analyzer, from the BW toolbar Layout Display
Exceptions you also have the option of adding an additional line between
the filter and results areas for each exception and activating or deactivating
the exception from there. There is an item for Web applications that you
can integrate into your template for the same purpose. You can use
exceptions to evaluate one or all key figures in your query definition. If you
want to use exceptions selectively on specific key figures in your query
definition, you have to define an exception for each key figure accordingly.
Hint: You can proceed as follows to make entering large values with many
zeros easier:
An apostrophe after the value means multiply by a thousand, two mean
multiply by a million and three mean multiply by a billion (for example: 1.=
1,000, 1,5..= 1,500,000).
You can include all values or specific intervals (for example, only those
falling below the threshold value in the red area) in the threshold value
catalog. You can enter fixed point or floating-point numbers for the values
you are defining.
With key figures that exceed the threshold value and are on the border
between two intervals, the worst alert level is always shown (for example,
interval 0 to 1000 alert level 9 and 1000 5000 alert level 8, the sales volume
key figure is 1000 - alert level 9 is used as the basis for identification
Cell Restrictions
On the Cell Restrictions tag page, you can specify whether a restriction with
regard to the use of the exception applies Only to the Totals (default
setting) or to All values (therefore not a restriction).
You can choose New to define an operator for each characteristic in the
query definition, and a value for each operator. You also choose Transfer
here to add your restrictions to the list.
Note that you have to list all characteristics that you defined in the Cell
Restrictions in the drilldown of the report, since the exception takes effect
only then. If there is a characteristic in the drilldown that is not recorded in
the cell restrictions, the effect that the exception has depends on whether
you selected Totals Only or All on the Cell Restrictions tab page. If you
selected All, it does not matter where you integrate the characteristic in
the drilldown, the exception is applied accordingly. However, if you
selected Totals Only you have to place this characteristic at the end of the
drilldown, otherwise the exception does not take effect.
The following snapshot of a report shows the cells in different colors as per
the exception.
You can change exceptions in the Query Designer using the symbol
Exception Change Exception. Use the cursor to highlight the exception that
you want to delete and choose Delete to confirm. Hint: If you execute your
report on the Web, you can create, change, activate and deactivate
exceptions using the List of Exceptions Web item. You can delete an
exception using the context menu only if you created the exception in the
Web application itself.
You can define several exceptions in a query for different value assignment
areas or for different versions. If the threshold value areas overlap when
you activate several exceptions, the worst (highest) alert level counts.
11.10. Conditions
Sometimes it is desired to flexibly restrict a report so that only the most
important information is displayed. This should enable a more efficient
analysis of data when large amounts of data are analyzed. This is achieved
using conditions.
By defining you have the option of analyzing the query results in more
detail. You can analyze combinations of characteristics using ranked lists,
thereby displaying your ten best customers by sales revenue, for example.
By defining value limits you can display all key figure values above or below
a certain value. The data is restricted accordingly in the results area of the
query, so that you only see the area that interests you. You can define
multiple conditions for a query, and then activate or deactivate them in the
report itself to create different views of the data.
You can set conditions for all characteristics, single characteristics and
characteristic combinations in the report drilldown, that is, in the results
area in the BEx Analyzer or in the table item.
11.10.2. Features
In the area Display all values for which at least one of the following
conditions applies, you choose New to select a Key Figure for which a
condition is to be used. In the second field, you can see the operators for
specifying value definitions. You choose Transfer to add your entries to the
list of conditions and choose New to define more conditions. You save your
conditions by choosing OK and you can then display your report in the BEx
Analyzer or in the browser.
A condition row consists of a key figure, an operator, and a value for the
operator. In query definitions that contain two structures, there is an
additional field for defining a structural component.
You can use the following operators for threshold value conditions::
• Equal to - Example: Invoiced quantity equals 1000
• Not equal to - Example: Line item not equal to 5
• Less than - Example: Sales revenue less than 100,000 EUR
• Greater than - Example: Incoming orders greater than 1,000,000 EUR
• Less than or equal to - Example: Sales revenue less than or equal to
100,000 EUR
In the variable definition, select Variable Entry. You are then given the
option of choosing an existing variable from the dropdown box, changing
the variable or creating a New Variable.
You can use the following operators for ranked list functions:
. Top N - Example: Display the sales revenue of the top 5 customers
. Bottom N - Example: Display the bottom3 (lowest) incoming orders
. Top % - Example: Restriction to 20%of the best revenue, in order
. Bottom % - Example: List of 15%of the customers with the lowest sales
revenue, in order
. Top Sum - Example: You get a list of the products with the highest sales
revenues where the total sales revenue makes up 20,000 EUR. All sales
revenues are sorted in descending order and then the sum is calculated
until the threshold value of 20,000 EUR is exceeded. All products, including
the product that takes the sales volume over the 20,000 EUR mark, are
listed.
. Bottom Sum - Example: As with Top Sum but here, a ranked list is sorted
in ascending order of products with the weakest sales revenue until a sum
greater than or equal to 20,000 EUR is reached. All products, including the
product that takes the sum over the 20,000 EUR mark are also listed here.
The following figure shows a report where only Top 2 Customers according
to Sales are displayed.
11.10.3. Calculate
Result As to display the Summation. If you are using the browser, you can
call the context menu and then choose Properties Local Properties
Calculate Result As Summation.
You can also delete conditions from the Selection dialog box by highlighting
the relevant conditions and choosing Delete to remove it from the list.
If you execute your report on the Web, you can create, change, activate
and deactivate conditions using the List of Conditions Web item. You can
delete a condition using the context menu only if you created the condition
in the Web application itself.
12.1.Introduction
The BEx Web Application Designer is a desktop application for creating Web
applications with BI-specific content. Using the BEx Web Application
Designer, you can create an HTML page containing BI-specific content such
as various tables, charts, or maps. This HTML page (Web application) forms
the basis of Web applications with complex interaction, as well as Web
cockpits and iViews. The command wizard and pattern wizard are integral
parts of the Web Application Designer. Using the command wizard, you can
easily generate commands from the Web Design API and include them in
your Web template. Using the pattern wizard, you can configure BI patterns
to a certain extent and tailor them to meet your needs.
12.2.Features
The initial view of the BEx Web Application Designer has four different
screen areas in addition to the menu and toolbars as depicted in the figure
below
You can adjust the appearance of the Web Application Designer to meet
your requirements. The object on which you are working, namely the Web
template, is handled differently from the tools and help windows with
which you are working.
● You can show and hide the individual screen areas and toolbars using
the View menu option.
● You can reposition the three toolbars and the Web Items and
Properties windows as required. Depending on where you position the
object, it is either anchored or appears freely as a toolbox.
● Since the Web Application Designer is a Multiple Document Interface
Application (MDI Application), you can open and manage different
windows with Web templates simultaneously. You can use the Window
menu option to arrange the windows differently: cascading
(overlapping), vertical, or horizontal.
The Web Items screen area is divided into the following sections:
• The selection groups for Web items (master Web items) are located in
the upper area, divided into various categories:
Standard: The following Web items are part of the Standard grouping:
• Analysis
• Chart
• Report
• Navigation area
• Filter area
• Button group
• Dropdown box
• Radio button groups
• Checkbox group
• List box
• Hierarchical filter selection
Extended: The following Web items are part of the Advanced grouping:
• Web Template
• Container Layout
• Container
• Tab Pages
• Group
• Single Document
• Document List
• Map
• System Messages
• Information Field
• Input Field
Miscellaneous: The following Web items are part of the Miscellaneous grouping:
• Data Provider – Information
• Text
• Link
• List of Exceptions
• List of Conditions
• Menu Bar
• Properties Pane
• Ticker
• Context Menu
• Script
Structure
In the upper section of the Web Template screen area, there are three tab
pages you can use to change the view of the Web template – in the same
way that you do in an HTML editor.
In the lower section of the layout view, you can create data providers.
When you double-click New Data Provider, the dialog for creating data
providers opens.
You can also create data providers in the Web Items screen area.
• XHTML tab page
The XHTML view displays the XHTML that corresponds to the layout view.
Each element of the XHTML syntax has a different color.
• Overview tab page
On the Overview tab page, all Web items, data providers, and commands
used in Web templates are listed. By selecting or deselecting
checkboxes, you specify which of these objects is listed. The objects are
listed vertically in the Web Item Name column. In the horizontal
alignment of the table, any data providers and reusable Web items
associated with the object listed are displayed. Using Sort Order, you
can specify how the used objects are to be listed:
o Grouped
If you choose this sort order, the objects used are listed by
type: data providers, Web items and commands.
o Web Template
If you choose this sort order, the sequence of the objects used
in the Web template are displayed as a flat structure.
o Web Template (Hierarchical)
If you choose this sort order, the sequence of the objects used
in the Web template are displayed as a hierarchical structure.
You see a hierarchical structure if you nest Web items in the
Web template (for example, when you use the Container Web
item).
You can change the parameters of the associated objects using the context
menu for each Web item, Web template, and data provider listed
• In the dropdown box in the header of the screen area you see the
selection for which you want to define properties – for a Web template or
for specific Web items. Depending on your choice in the dropdown box, you
can then make various settings for Web templates or Web items.
• Once you have selected a Web template from the dropdown box, you can set the
parameters for the Web template on the Web Template Parameter tab page.
• Once you have chosen a Web item from the dropdown box, you can make the
following settings:
• Tab page: General
Here you can use the Create New symbol next to the dropdown
box to create a data provider and assign it to the Web item. See
Web Template Parameters.
• Tab Page: Web Item Parameter
Here you can set the parameter for the selected Web item.
• In the lower area of the Web Item Parameter tab page or the Web
Template Parameter Web page, context sensitive help is available.
The Errors and Warnings screen area is used to display errors and warnings
that are found when a Web template is being verified.
Integration
The errors and warnings that are displayed in this screen area refer to the
following possible checks of the Web template.
• Verify
This check is performed automatically and by default every two
seconds. Within the verification, the internal structure of the Web
template is checked. You can change the refresh time for the
verification in the menu bar under Tools → Settings.
• Verification on the server
With this verification, which you trigger manually, additional
conditions for creating a correct Web template are checked on the
server side. Here for example, the system verifies whether a query
that is being used as a data provider exists. To trigger the
verification, on the menu bar for the Web Application Designer,
choose Web Template → Verify on Server
• Correct and format
During this verification, which you can trigger manually, the internal
structure of the HTML is checked. You can only trigger this
verification when you are in the XHTML view. From the Web
Application Designer menu bar, choose Edit → Correct and Format.
• Under Data Provider, you can create data providers of type Filter or
of type Query View. Drag the required data provider type into your
Web template using Drag&Drop. The dialog for creating data
providers opens.
• Underneath the selection for Web items and data provider
maintenance, you see the help area, which provides explanations for
the Web items and the data providers. To display the texts for the
After selecting Create a new web application , you will get a new screen
wherein you can add web items from the left of your screen to create a web
application. Let us create a simple web application having A table a Chart
and a Navigation Block.You can drag and drop these elements from under
the Standard Web Items pane into the WAD layout.
Select on Create a new data provider and the following window will pop-up
Browse for a query you have created . We have selected a query created on
one of the BW Statistics Cube here YTBD_STATS_QUERY. And select ok.
Select the table in your right hand pane and check the properties tab in
your left pane.. Assign the Info provider DP1 to the table. Repeat the same
process for the chart and the Navigation block.
Save the Web template and run this web template in the browser.