BW305 BI Enterprise Reporting,

Query & Analysis (Part I) - V2006Q2

Table of Contents
Unit #1: Introduction to BI Enterprise Reporting....................................................2
Unit #2: Navigating in Reports......................................................................................2
Unit #3: First Steps in BEx Query Designer..............................................................3
Unit #4: Key Figures...........................................................................................................5
Unit #5: Characteristics..................................................................................................10
Unit #6: Variables..............................................................................................................13
Unit #7: Exceptions & Conditions...............................................................................16
Unit #8: BEx Analyzer......................................................................................................24
Unit #9: BEx Web Analyzer...........................................................................................27
Unit #10: Information Broadcasting..........................................................................29
Unit #11: Enterprise Portal Integration....................................................................34
Unit #12: Document Integration.................................................................................42
Unit #13: Report Report Interface.......................................................................47
Unit #14: Managing Query Objects............................................................................49
Unit #15: Business Content..........................................................................................51
Unit #16: Further SAP BI Reporting Tools................................................................53
Unit #17: Appendix..........................................................................................................53
Glossary................................................................................................................................59

Unit #1: Introduction to BI Enterprise Reporting

In the

Business Information management IT practice, there are three IT scenarios.

Enterprise Reporting, Query and Analysis
Business Planning and Analytical Services
Enterprise Data Warehousing

Each InfoCube has one fact table and a maximum of 16 dimension tables. Each fact table
can contain a maximum of 233 key figures. A dimension can contain up to 248 freely
available characteristics.
You can export a web report to a BEx Analyzer report.

Unit #2: Navigating in Reports

In Open Dialog, you get following options
1. To choose the system from which you want to retrieve the data
2. Data Provider Types
BEx Web Analyzer :
o BEx Query / Query View
o InfoProvider
BEx Analyzer :
o BEx Query / InfoProvider
BEx Analyzer provides 3 Button on default screen
1. Chart
2. Filter
3. Info
When you drag a particular characteristic over another characteristics heading then the
second characteristic get exchanged with first one. But when you drag it over the values
of second characteristic, then it gets added after second.
If you simply drag a characteristics value to navigation pane, it is use to filter the query.
Whereas to exclude it, simply drag that value out of analysis area.

Unit #3: First Steps in BEx Query Designer

You have various options for calling up the Query Designer:
From the BEx Analyzer
As a separate program using Start Programs Business Explorer Query
Designer
Using the Web Application Designer
From the BEx Report Designer
With Crystal Reports (Crystal Reports >=8.5 including CR add-ons for SAP)
Table View : You can create a query for tabular reporting, as well as for Online Analytical
Processing (OLAP) reporting, by activating or deactivating the Table View mode. 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.
(Check)
Characteristic Restrictions: Here you define the characteristic filter values which apply to
the entire result set and cannot be modified by the user in the result. These are often
regarded as global or static filters.
Default Values: In this pane you 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.
(whats difference?? Any char added in default value appears in free char &
vice-versa) The user cannot add additional filters to the default values i.e. the filters in
the query definition set out the maximum range of the result data a user can display, this
may produce more data than the user requires so the user simply navigates to a reduced
result set by modifying the filters in the report.
Default description and technical name are proposed, these are made up of REP_
followed by the date and time.
BI Query can be published on web via Netweaver portal or executed with BEx Analyzer. It
can be used in Workbook, in WAD or Report Designer as DataProvider, & in the tabular
display in Crystal Reports as a data source for formatted reports.
Query Properties :
1. General Tab
Key Date - The checkbox Use standard date is used to tell the query to use the
current date at query run-time.
2. Display Tab
Adjust Formatting after Refreshing The default action is that whenever a query is
refreshed the result cells will be formatted so that the meaning of the cells is
emphasized. To prevent this from happening (perhaps to improve query
performance or you want to use your own format templates) you need to make
sure this box is unchecked.
Document Links Here you choose the document class which you would like to
make available to the query, this means a user can display or maintain
documents for these checked classes.
3. Value Display Tab
Zero Value Display These settings help you choose a suitable method of
presenting zero values in the result.
4. Planning Tab
Startup View This setting determines whether the query is started in display or
change (planning) mode. Planning mode allows the results cells to be changed.
5. Extended Tab
Release for OLE DB for OLAP If you want to expose the data from this query to a
third-party BI tool then this check box must be marked so the Microsoft ODBO
interface is filled.

InfoProviders used for Queries are:

InfoCube, DSO, Characteristic InfoObjects with master data (in BI these are always as
InfoProviders), InfoSets, Virtual Providers, & Multi-providers
InfoObject & DSO in Query Designer
The system generates the key figure Number of Records (1ROWCOUNT) for characteristic
InfoProviders and for DataStore Objects and places them in the Key Figures folder.
In the Dimensions folder, you find two different dimensions for each object type. For
characteristic InfoProviders, the dimensions are Attributes and Key Part, in accordance
with the definition of the master data tables. For DataStore Objects, the dimensions are
Data Part and Key Part.
InfoSet in Query Designer
The system also automatically generates the key figure Number of Records
(1ROWCOUNT) for InfoSets. Two dimensions are provided for each InfoProvider in the
InfoSet: Attribute and Key Part. Therefore, for an InfoSet composed of an DataStore
Object connected to a characteristic, four dimensions display.

MultiProviders in the Query Designer

In the Key Figure folder of a MultiProvider, you can find the generated key figure Number
of Records (1ROWCOUNT), if one of the InfoProviders included already contains this key
figure, for example, in DataStore Objects. The Data Package dimension contains the
generated characteristic InfoProvider (0INFOPROV), which enables you to specify a
unique InfoProvider in the selection or the display to supply data for the query. The
values of this characteristic are formed from the (technical) names of the InfoProviders
involved.
What InfoProviders can contain generated characteristics or key figures?
A InfoCubes

 B Data Store Objects

C InfoProviders for Characteristic InfoObjects
D InfoSets
E MultiProviders
Answer: B, C, D, E
MultiProviders contain generated characteristics or key figures, if at least one
InfoProvider in it contains these.

Unit #4: Key Figures

Restricted KFs :
The key figure that is restricted by one or more characteristic selections can be a basic
key figure, a calculated key figure, or a key figure that is already restricted.
The restricted KFs can be defined at 2 levels
At InfoProvider Level : In Restricted KF option under KFs on left side in Query
Designer
At Query Level : as Selection in Structure in Query Designer
Value

Range Options
History
Favorites
Single Values You can also use the search features and also select the single
values from a hierarchy (there is also a search feature within the hierarchy). The
search option allows you to enter either the characteristic key (i.e. product
number) or characteristic text (i.e. Pump) or you can enter any of the attribute
values of the characteristic (i.e color, speed). You can mix up your choices but you
are limited to a maximum of three search criteria.
Value Range Additional Options includes Between, Greater than or equal to, Less
than or equal to, Greater than, Less than
Variables
If your selection criteria returns a large result set then you should maximize the selection
window so you can see more of the results before you need to scroll.

Additional function for restricted key figures when activated, navigation and filtering have
no effect on the restricted key figure. To activate, select Constant Selection from the
context menu of the restricting characteristic while editing the restricted key figure.
(Check)
Note that several lines are available for key figure names to control the column width in
the report.
Calculated KFs :
You can take basic key figures, restricted key figures or calculated key figures to define
new calculated key figures.
Functions available for calculations
Percentage Functions
o Percentage Variance (%) <Operand 1> % <Operand 2> gives the
percentage by which the <Operand 2> exceeds the <Operand 1>.
o Percentage Share (%A)
o Percentage Share of Result (%CT) %CT<Operand> specifies how high the
percentage share is in relation to the result. The result means the result of
aggregation at the next level (interim result). %CT Incoming Orders
specifies the share of incoming order values of each individual
characteristic value (for example of each customer) in relation to the
characteristic's result (for example, customer of a division).
o Percentage Share of Overall Result (%GT) %GT <Operand> specifies how
high the percentage share is in relation to the overall result. In the
calculation of the overall result, the dynamic filters (filters that were not
already defined in the Query Designer) are included.
o (%RT) same as %GT Except filters that were not already defined
in the Query are not considered??
Data Functions

Counts COUNT(<Expression>) delivers the value 1 if the expression

named in <Expression> is not equal to 0.
o NDIV0 (x) is equal to 0 with division by 0, otherwise x.
o Result SUMCT <Operand>
o Overall Result SUMGT <Operand>
o Report Result SUMRT <Operand>
Mathematical Functions
o Maximum
o Minimum
o Absolute Value
o Smallest integer value larger than operand
o Division (integers)
Boolean Operators
o is less than <
o is not equal to<>
o is greater than >
o is less than or equal to <=
o is equal to =
o is greater than or equal to >=
o logical NOT, AND, OR, and logical exclusive OR XOR
o

You can define calculated key figures at both the query level and the InfoProvider level. If
you are defining calculations in the columns as well as in the rows, a formula collision can
occur in the interfaces of the two formulas. You can therefore, define which of the
formulas is to be used.
You can even create a new restricted KF directly in the formula editor for calculated KF.
This feature is only relevant to query level calculations. Right click in the place where you
want the new restricted key figure to appear in the formula and use the New Selection
menu option. This will create a dummy
key figure in the correct place. Right click on the dummy key figure and use the menu
option Edit to define the key figure and filters. The new restricted key figure will appear in
the key figure structure
and therefore will be part of the result (as well as the new formula). If you don't want to
see the restricted key figure in your result simply use the hide feature under the
properties.
Remember that you do not have access to all operators as some operators only make
sense at the query level. (Check & which operators as example??)
Properties of KFs :
If Use Default Setting box is checked the setting from the InfoObject metadata will be
used.

Description The total length of all characters in all lines including the line break
character for KF description is limited to 60 characters. It is also possible to edit
the description 'in-line' using the standard Microsoft Windows feature. i.e. you can
change the description directly on the key figure by simply clicking once on the
key figure, the cursor becomes positioned at the start of the description ready for
you to start editing.
Technical Name This is optional. But when accessing external interfaces (such as
Crystal reports, in URLs, or through OLE DB for OLAP), the structure parts must
have a technical name so that it can be accessed without error.
Hide
Highlight The actual formatting is taken care of in the front end tool, and not
here.
Number of Decimal Places

Scaling Factor
Sign Change The reverse +/- signs is only a display function. It has no influence
on calculation in formulas.
Exception Aggregation Using the new functions of exception aggregation, you
can create calculated key figures using a formula that uses exception aggregation
itself (this is a nested exception aggregation). You can also use calculated key
figures created on cell level (using the cell editor) with the new functions of
exception aggregation. (??)

Local Calculations
o Calculate Result As Use the setting Total to ensure that the totals are
recalculated locally once a condition has been applied. Otherwise the
totals will not be the sum of the result rows displayed, the total will include
rows which have been excluded from the condition.
o Calculate Single Values As & Also Apply to Result
o Cumulative causes the results to calculate over a series of values.
o Normalization of Result - ??
o Calculation Direction allows you to choose whether the calculation is
performed in the rows or column, depending on your layout and the
calculation methods you have chosen, not setting this correctly may cause
unexpected results.
Currency Translation You can set a currency conversion key & a target currency.
You can also use a variable to allow the translation setting to be determined at
runtime. This can be carried out at two levels while loading the data & executing
the report.
Unit Conversion You can set a Unit of Measurement conversion key and a target
unit. You can also use a variable to allow the translation setting to be determined
at run time.
Constant Selection This determines that the KF result remains constant during
navigation, regardless of the filtering set by the user at runtime.
Formula Collision The Formula Collision function only displays in the Properties
dialog box if two structures are used in the query definition and both contain
formulas.

Change Data You can decide if the cells are input ready for this key figure so
users can enter values directly into the cells. This setting is used for planning
applications. Here you can also decide if the key figure can be changed by a
planning function (a background planning task which modifies or generates
planning data, such as copy data, revalue data). (Check)

Structures :
A query can have a maximum of two structures, there is no restriction as to where these
structures appear in the layout, i.e. you could put both structures in the columns. You can
create some very flexible layouts using two structures. You can mix structures and
characteristics in the rows or columns. You can define formulas in either structure. (Can
we have combination of chara & KFs in both structures??)
Structures can also be used in several queries for the same InfoProvider. In order for this
to be possible, you need to save them as reusable structures whereas Local structures
are only used in one query. To make a structure reusable, Choose Save as... from the
context menu (right mouse-click) and enter a technical name and a description after
defining the structure as usual. Changes made later to global structures affect all queries
in which they were used. If you only want to make local changes in a particular query,
you can choose Remove Reference in the context menu for the structure, and thereby,
change the reusable structure into a local structure. (does it create new local
structure?)
Cell Editor :
Cell editor allows direct definition of specific cells in a query. The Cell Editor also allows
you to mark a specific cell as a 'reference cell' so that it can be referenced in further
calculations. Cells are the intersection of two structures in a query definition therefore
the Cell Editor can only be used in query definitions where there are two structures.
(Even though both the structures are in columns or rows??) One structure will
hold only characteristics while the other structure holds only key figures. Cells can be
formulas, selections, references or auxiliary cells.
Following 4 functions are available for a cell
New Selection
New Formula
New Cell Reference
Additional Cells If you need additional cells for auxiliary selections or formulas
which are

not already included in the query structure, you get this option on cell adjacent to
Help Cell. (Check)

Unit #5: Characteristics

Properties of Characteristics
1. Description
2. Display As
a. No Display
b. Key & Name
c. Name & Key

10

3.
4.
5.

6.

d. Name
e. Key
f. Long or Medium Name
Text View Here you choose length of the text recquired
Sorting The characteristics itself or all the attributes of the characteristics can be
sorted by Key or Name. You cannot use the attribute that you have selected for
sorting in the display.
Result line
a. Always Display
b. Display with more than one single value The result will only display if
there is more than one single value.
c. Always Suppress
Display Hierarchy

You can show Display Attributes in a report in the drilldown. However, navigation steps
are not possible. (For example, you cannot choose values from a display attribute as a
filter.)
Navigation Attributes always display in the dimension of the characteristic to which they
belong. Time dependent Navigational attributes enable you to view current data with
characteristic values from the past or view past data with current characteristic values.
Very slight loss in query performance when compared to characteristics.
External hierarchies are saved in special master data tables. They behave like master
data and therefore, you can use and modify them in all InfoCubes.
Properties of Display Hierarchy
1. Sorting
2. Expand to Level
3. Position of Lower Level Nodes Choose whether the subordinate nodes are
positioned above or below a superior node.
4. Values of Posted Nodes Choose whether you want to Always Show or Hide the
values of posted nodes.
5. Nodes with Only One Lower-level Node Choose whether you want to Always
Show or Hide nodes with only one lower level node. (Check)
The uppermost node of a hierarchy is the root. There can be several roots. There is a
distinction between postable and non-postable nodes. The hierarchy level of a node
denotes the distance of the node from the root. Hierarchy leaves contain the
characteristic values for the basic characteristic. In contrast to postable nodes, a leaf
cannot have any subordinate nodes. Intervals contain a number of leaves that belong
together, described by their upper and lower limits. You can create them for a node that
has more than one leaf.
Hierarchy nodes appear twice in the hierarchy when nodes that have the same technical
key and that appear more than once are leaves (postable nodes without lower-level
nodes), and when they are not attached to the same super-ordinate node. You can then
either set the nodes as link nodes or make the hierarchy structure time-dependent
and specify that the time intervals of all duplicate nodes with the same technical key do
not overlap.
You use link nodes to include a sub-tree in a hierarchy more than once. However, the link
node is only a link to the original node that you cannot change independently. Link nodes
cannot have their own lower-level nodes. They take on the lower-level nodes of the
original node. These lower-level nodes do not display in the hierarchy maintenance. (For
Link Node??)
You can choose from text nodes, characteristic nodes of external characteristics, leaves
of the basic characteristic of the hierarchy, or intervals.

11

Postable nodes (characteristic nodes of the basic characteristic in the hierarchy,

intervals) are symbolized by the green InfoObject icon. Non-postable nodes (text nodes,
external characteristic nodes) are symbolized by the yellow InfoObject icon or by the file
folder icon.
You can arrange the nodes as you wish beneath one another as far as interval level. You
cannot attach any additional nodes under intervals. (??)
Setting in the Hierarchy Maintenance
1. Level Maintenance You can use Level Maintenance to determine names for the
different levels of a hierarchy. These names are then used in the context menu of
the query during navigation.
2. Hierarchy Attributes You can set the presentation parameters for the hierarchy
display in the query using Hierarchy Attributes.
a. Do Not Display Leaves for Inner Nodes in the Query An inner node that
has subordinate postable nodes (lower-level nodes). You can either create
a leaf for each inner node and insert it directly underneath the inner node,
or choose not to display the additional nodes.
b. Changeable Display for Leaves of Inner Nodes - You can determine whether
the user is able to change the display for the runtime of the query.
' ': The display cannot be changed in the query.
'X': The display can be changed in the query.
c. Suppress Unassigned Node Here you can specify whether to suppress the
node under which all postable characteristic values that do not appear in
the hierarchy display.
d. Root/Totals Item Appears You can determine whether the root and
therefore, the totals item display at the end or start of the query and
whether the leaves appear above or below.
e. Start Drilldown Level You can set the default level to which the hierarchy
is drilled down when you first call up the query.

Hierarchy Properties on InfoObject Level

1. Hierarchies Version Dependant Check this box if you want to maintain different
versions of the hierarchies. When you define each hierarchy you will need to
supply a version identifier. in a query you are able to choose hierarchies from the
available versions.

12

2. Hierarchies Not Time Dependant

3. Entire Hierarchy is Time Dependant When you develop a query which uses the
hierarchy you can also select the hierarchy valid for a specific date.
4. Time Dependant Hierarchy Structure Select this radio button if you want to be
able to define the individual nodes in relation to time intervals. When you develop
a query which uses the hierarchy you can also select the hierarchy nodes valid for
a specific date.
5. Use Time Dependant Temporal Join - If members appear in more than one node
over a time period (i.e. a person is reassigned to a new team) then a check in this
box will ensure you are able to report on these movements in the same result.
6. Interval Permitted In Hierarchy Sometimes is more efficient to use intervals to
specify the members of the hierarchy nodes. i.e. cost centers 1000 to 1999 = New
Hire Costs. Any new cost centers you later add within the range will automatically
be included in the hierarchy.
7. Reverse +/- Sign for the Node Check this box if it makes sense to present the
key figures with the sign reversed. This is purely a presentation feature and does
not alter the actual value of the key figure.

Unit #6: Variables

Variables act as placeholders for:
Characteristic values
o Selecting Single Value Variables

13

Selecting Single Value Variables as Variable Value Range Limits If you are
using variables when making interval selections, you can swap the limits
by highlighting the relevant variable in the right Selection window, and
choosing Swap Interval Limits from the context menu.
o Selecting Variables with Several Single Values or Value Ranges
Hierarchies / Hierarchy nodes There are two possible combinations of hierarchies
and nodes.
o Variable hierarchy node with a fixed hierarchy For example, a report
about any department (variable hierarchy node) for the hierarchy valid for
2002 (fixed hierarchy).
o Variable hierarchy node with a variable hierarchy For example, a report
about any department (variable hierarchy node) for the hierarchy valid for
the current calendar year (variable hierarchy).
Texts You can use text variables in query descriptions, calculated key figures,
and structural components.
Formula elements
Variables are reusable objects. It depends on the InfoObject for which they were created.
o

Variable Processing Types

User Entry/Default 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.
o Text variables and formula variables with the replacement path processing
type are replaced by the corresponding characteristic value.
o Characteristic value variables with the replacement path processing type
are replaced by a query result.
Authorization The Authorization processing type enables you to fill the variables
automatically with the values from the authorization of a user.
Customer Exit 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.

14

SAP Exit The SAP exit processing type is contained in variables that are
delivered with SAP BW Business Content.

Properties of Variable :
General Information Tab Name of the variable & the processing type like Manual
Input / Default Value, Replacement Path, Customer Exit & Authorization
Replacement Path Tab This is used for characteristics value variable, formula
variables, & text variables with replacement path processing types.
o For Text / Formula Variable
Under Replace Variable With, you have the following options: Key
(Internal Value), External Characteristic Value of the Key, Label
(Text), Attribute Value, Hierarchy Attribute
Using the setting Use Interval, you determine whether the FromValue, the To-Value, or the Difference is used as the value when the
value to be replaced is an interval.
The setting Offset Start and Offset Length enable you to determine
the start and the length of the text output. For example, if the only
the first 10 characters of the text are to be used, the Offset Start
value would be 0 and the Offset Length value would be 10.
The Evaluate as Boolean function (value 0 or 1). This function is
only available for formula variables.
The value of the variable is 0 if the value to be replaced is a
string with only blank characters or a zero.
The value of the variable is 1 if the value to be replaced is a
string with characters that are not blank or a number that is
not zero. (Check)
o Characteristics Value Variable
From the Replace Variable Value withdrop down list you must
choose Query (Top 5 Products). Each time that the query 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), SAP
recommends that you use a variable that represents a
precalculated value set, where the variable values are stored
persistently.
Details Tab It allows to enter setting for all types of variables except those with
Replacement path processing type.
o Variable Represents Select the display area that the variable is to
represent.
Single Value
Multiple Single Value You can use this setting with hierarchy
nodes, for example, to enable the user to enter several single
nodes.
Interval
Selection Option
Precalculated Value Set The variable represents a number of
values that are stored in a database table by the Reporting Agent.
o Under Variable is, specify whether the variable input is Optional,
Mandatory, or Mandatory, Initial Value not Allowed.
o Under Variable is Ready for input you can determine whether the variable
is input-enabled when the query or Web application is executed.
o 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 dynamic filters in the
query.

15

Copy personalization data from variable: You can personalize variable

values for input-enabled variables for each user. These personal values are
saved for each variable and each user.
Default Value Tab
Currencies & Unit Tab This can be used with Formula Variable. You can select
from following Dimensions.
o Amount
o Quantity
o Price (=currency/unit)
o Number (=default setting)
o Date
o

Business Content Variables These 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.

16

Unit #7: Exceptions & Conditions

Exceptions:
If you do not set the active flag for an exception, you can activate the exception
interactively in the Web Analyzer or BEx Analyzer.
If you want to assign your own alert level colors, in the BEx toolbar in the BEx Analyzer
choose Format Patterns. So that these changes are kept in the query, you have to save
them in a workbook. For Web applications, the formats are stored in the MIME Repository
under the stylesheet used for the web template, such as BWReports.css. You can modify
them there.
On General Tab,with key figures values on the border between two alert levels, the
highest alert level rank is used. E.g.
Alert Level 1 : Bad 3 : between 0 to 1000
Alert Level 2 : Critical 3 : between 1000 to 3000
KF Value 1000 will have Alert Level 1 : Bad 3.

On the Definition Tab, There is a setting for determining whether the exception is
evaluated before or after any local calculation within the query.

17

On the Display Tab, if you select the checkbox for Exception Affects Data Cells, then the
following choices can be made: (Check)

18

If the checkbox for Exception Affects Characteristic Cells is selected, then you can select
from the following options: (Check)

On Cell Restrictions Tab, you can specify whether the exception applies to both detail and
result (total) values or to only the result values. This setting is used for any characteristic

19

that is not used in the Define Cell Restrictions area in the lower part of the screen.
(Explore what happens for all combinations)

You have the following selection options for the operators: (Check)
Everything - The cell context is not restricted. The exception applies for every
drilldown state of the characteristic.
Totals Only - The exception affects only the aggregated values of the
characteristic.
Everything Except Totals - The exception affects all values except for the
aggregated values of the characteristic.
Fixed Value - The exception applies only to a specific characteristic value of the
characteristic, which you can determine in the search help in the Value field. You
can also use a characteristic value variable here.
Level - The exception applies only to specific hierarchy levels of the characteristic.
You have to use all characteristics that you specified in the Define Cell Restrictions area
in the drilldown of the report (when option is Exception Only Affects result & in
Define cell area characteristics has operator other than Totals Only) since only
then will the exception take effect. If there is a characteristic in the drilldown that is not
recorded in the Define Cell Restrictions area, & if you selected Exception Only Affects
Results, you have to place this characteristic at the end of the drilldown, otherwise the
exception does not take effect. If Exception Affects Everything is selected then it does not
matter.
Neither the status nor the definition of the exception can be changed permanently in
Web Analyzer.
In the exception wizard in BI7 (only with Web Analyzer??), you get two exception
types Status Exception (Normal Exception) & Trend Exception. i.e. a KF might be
considered an exception if the deviation of the key figure is greater than +5% over time.
The operators Top N, Bottom N, Top %, Bottom %, Top Sum and Bottom Sum are not
available in the Exception Wizard since the filtering of the data supplied to the query has
already been done. Those operators are only available when defining exceptions in the
Query Designer.

20

In Set Visualization option (available only in Web Analyzer??), depending on Status

Exception or Trend Exception, you have an option to render the exception as background
colour or as a symbol such as a traffic light (red, yellow or green) or an arrow showing the
direction of a trend (up, down or flat). Choices are available for symbols to show only the
symbol in place of the value or along with the value either before or after it.

Note the arrow pointing to right to indicate yellow.

21

In order for the exception to take effect, all characteristics with a value on this screen
other than Standard must be in the drilldown of the report. If there is a characteristic in
the report drilldown that has Standard as the assigned value on this screen, you have to
place this characteristic at the end
of the drilldown, otherwise the exception will not take effect. (Check contradictory
with Example below last para of Exceptions)
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.
On the Cell Restriction Tab, the option Exception Only Affects Results is chosen. In
Define Cell Restriction sold-to-party, material as Everything except Totals & Cal.
Year/month is specified as Totals Only. Now, if you remove Cal. Year/month from
drilldown, you don't see the key figure's single values for the characteristic Cal. year /
month any more, but it's results, so the exception still works and the coloring is still
there. But instead if you remove sold-to-party from drilldown, you can see that the key
figure values are no longer shaded by the exception. This is because you now see the
results of the characteristic Sold-to Party in the report, and the results of this
characteristic are
not affected by the exception since the cell restriction is Everything Except Totals.

Conditions:
Operators for Threshold Value Conditions
Equal to, Not Equal to, Less than, Greater than, Less than or equal to, Greater than or
equal to, Between, Not between
Operators for Ranked List Conditions
Top N, Bottom N, Top %, Bottom % (Lists 15% of Customers with the Lowest Sales
Revenue), Top Sum (It displays all products with descending Sales till the total Sales
reaches the threshold value in condition say 20,000), Bottom Sum (sorted ascending)
A mixed condition uses a combination of both threshold and ranking criteria, such as top
5 salespeople plus products selling greater than 1000 EUR. (How to define? What is
the effect of Two separate conditions or two separate condition parameters in
one condition?)

22

When you execute a report with an active condition, you always see the unconditional
query result in the Overall Result row (overall result without filter). If you want to see the
filtered (conditional) query result, then Calculate Result as Summation.
On the characteristic assignments tab you define how the condition will work in
conjunction with the characteristics in your query .
All characteristics in the drill-down independently - The condition is always valid
for all characteristic combinations.
Most detailed characteristic along the rows - The condition is valid only when all
characteristics in the query have been used in the drill down along the rows.
Most detailed characteristic along the columns - The condition is valid only when
all characteristics in the query have been used in the drill down along the
columns.
Individual Characteristic and Characteristic combinations - For this setting you
define precisely which characteristics must be in the drill down before the
condition is valid. Check the boxes to include them.

If you are using several conditions in one report, conflicts can arise that lead to automatic
deactivation. The following status descriptions appear in the display:
Variant
Reason: The condition relates to a characteristic or characteristic combination
that
is not included in the drilldown.
Not Used
Reason: The condition relates to a characteristic that is drilled down using an
active
display hierarchy. The condition relates to a characteristic that is included through
the activation of another condition, leading to a collision, and is therefore
deactivated (however, you can reactivate this condition and automatically
deactivate the last condition activated).
If you activate a condition for a combination of characteristics, the results row no longer
displays.

23

Unit #8: BEx Analyzer

Features
Analysis Toolbox used to work with query results in workbook
Design Toolbox used to design workbook
On the Open Dialogue Box for Workbook has 4 options (Find, Favourite, History & Roles)
whereas Open Dialogue Box for Query has 5 options InfoAreas is additional. The option
History displays the last 15 workbooks/queries you have worked with.
With Open Dialogue Box for Query, you can simply select InfoProvider & then use the
navigation options in the workbook to filter the data as required. (Check in sys) But this
would cause long run times as all data is extracted.
A workbook saved here could only be opened by the user who saved it there. This is
regarded as a personal set of workbooks. (Cannot open with find??)
The refresh icon appears slightly differently depending on whether the workbook is in
automatic refresh mode or manual refresh mode. To switch between the automatic
refresh and manual refresh modes simply press the refresh button in the analysis
toolbox. Manual refresh has advantage over automatic, when several filters are to be
added, in auto the workbook refreshes after each filter added whereas in manual refresh
can be performed manually after adding all filters.

Changing Variable Values

24

Variants - A variant is a collection of variable values which have been previously

saved so that they can easily be recalled.
Personalize Variables - Instead of being presented with a huge number of
irrelevant variable values, the user simply sees the values which they use
frequently. To save values to the personal list press the Personalize Variables
button, the values currently entered in the variables selection fields will be added
to the list for the user.
Start With These Values Next Time - If this box is checked then the next time the
workbook opens using the variables values in the dialog box.

Tools button on Analysis Toolbox provides access to a number of useful tools such as
1. Query Designer
2. Broadcaster (to send the workbook results to other users either immediately or at
predefined point of time.)
3. Planning Modeler (to design planning applications that are fully integrated with
the BEx environment.)
4. Report Designer
5. Web Analyzer

25

Global Settings
Display System Name in Local History - to identify the source of the report before
opening.
Log On with Attached GUI - If the user is already logged on to the SAP BI, this
setting means that the same user id will be used to launch the BEx Analyzer.
Launch Legacy Version from RRMX - You can choose to launch the older BW 3.x
version of the BEx Analyzer from RRMX by checking this box.
Launch Analyzer whenever Excel starts
There is an option to log on/off manually. when you are logged on the 'plug' icon appears
connected, when you are not logged on the 'plug' remains unconnected.
Workbook Settings
General Tab
a. Refresh Workbook on open
b. Process Variables on refresh
c. Allow Drag and Drop - If you want the prevent the users from using the
drag and drop features then check this box. Don't forget to uncheck the
Allow Navigation boxes in the design items such an analysis grid and
filters, otherwise navigation can still be carried out using the menu
options.
d. Protect Workbook If you want to protect your workbook from
unauthorized changes to the design aspects, it can be password protected
here. Whenever a design toolbox button is pressed the user will be
prompted for a password. Entering the correct password will put the
workbook into unprotected mode. It does not uncheck the Protect
Workbook box.

26

Unit #9: BEx Web Analyzer

Please note Report Designer is a part of BEx Web. The BEx Web Analyzer is integrated
into the SAP NetWeaver Portal.

27

The Web Analyzer is able to access data from both SAP BI InfoProviders and third party BI
sources.

Analyses run with the Web Analyzer can be broadcast or saved for future use. With the
new BEx Web Analyzer, users have two options for saving the results of their ad hoc
analyses. The first option is to save in either the BEx Portfolio or the Favorites portion of
the Knowledge Management area. With the second option, users can save their ad hoc
analysis result as a BEx Query View via the context menu. The BEx Query View contains
the navigation status of the analysis, but does not contain information about the layout
(e.g. chart layout). This is saved in the BI metadata repository. This procedure allows you
to use query views based on third-party BI data, as well as SAP NetWeaver BI data, as
data providers for BEx Web Applications or BEx Reports.
Users can easily switch between table view, graphic view, or a combination of both using
a dropdown box. The combination view is a new feature of the Web Analyzer.

28

The result of an ad hoc analysis containing exceptions created in this way can be saved
in a KM folder in the portal or broadcast to other parties. However, the exception created
with the exception wizard in the Web Analyzer does not become part of either the query
or query view definition. In order to make an exception a permanent part of the query or
query view definition, the exception must be defined using the Exception Editor in the
BEx Query Designer.
Printing & Broadcasting the analysis

Unit #10: Information Broadcasting

Broadcast data can come from any SAP BI data source, but also non-SAP data sources
can be used in a broadcast.

29

A role is delivered with NetWeaver BI which provides easy access to Broadcasts via the
Portal. Any portal user who is assigned to this role will be able to access their broadcasts
easily via the Portal.
Applications through which settings can be defined
1. Query Designer
2. BEx Analyzer
3. BEx Web Analyzer
4. Report Designer

30

5. Portal
Object
1.
2.
3.
4.
5.

types available for broadcasting

Query
Query View
Report
Workbook
Web Template

Distribution Types
1. Broadcast Email
2. Broadcast to the Portal
3. Broadcast to the Printer
4. Broadcast Email (Bursting) - The broadcaster retrieves the emails of the recipients
from the master data attributes of a reporting characteristic. ie. the email address
of the cost center manager could be an attribute of the characteristic 'Cost
Center'.
5. Broadcast According to Exceptions
6. Broadcast (Multi Channel) - Use this option when you need a combination of the
above methods.
7. Fill precalculation store (??)
8. Precalculate Value Set This option will allow you to schedule a collection of filter
values for a characteristic by running a control query. These collected filter values
can then be used by a subsequent query as input parameters, thus dramatically
improving online query performance. (Check Main Query is not scheduled?)
9. Fill OLAP cache - Use this type to setup a broadcast to warm up the OLAP cache so
that online query performance will improve. (??)
10. Fill MDX cache - Use this type to setup a broadcast to warm up the MDX cache so
that online query performance will improve when using reporting tools (possibly
3rd party) which use this extraction method. (??)
Options for Output Format are dependent on the selection you have made for Distribution
Type. E.g. for Broadcast Email, the options available are HTML (to send the report results
as a separate file), MHTML (Multipart HTML combines all the objects required for the
report together in one single file to embed the BEx report within the body of the email),
OnLine Links to Current Data, PDF (as an attachment).
Information Broadcasting Settings
1. Recipient Tab
There are 3 options to include receiver
1. One or more SAP users separated by semi-colons
2. User in Role i.e the SAP users associated with the role or roles selected
3. One or more E-Mail addresses separated by semi-colons
External E-mail addresses have to be maintained for users in SU01. For
background processing, the Authorization User setting can be used to assess
date format and OLAP authorizations, otherwise current user & its authorizations
apply. If the document is created in the foreground, the logon language is used
unless you specify differently. If background processing is used, the language in
the setting is used.

31

With User Specific option, user specific documents can be generated. i.e. The
system generates the document for each of the specified recipients with their
personal settings (date format, language) and data authorizations. Recipients that
are only specified with E-Mail addresses are excluded from this.
2. Text Tab
In the Subject, you can attach Text Variable. The subject text can be 50
characters long.
Importance of mail can be low, medium or high. Contents also can have Text
Variable. When sending online links, the system automatically adds a link to the
text of the e-mail if it is not part of the text via the variable PR_ONLINE_LINK.

3. General Pre-calculation Tab

The theme drop down allows you to choose a preferred 'look' for the report
results. If you check the box 'Only Upon Data Change' then the broadcast will only
be sent if the data has changed since the last broadcast sent with this setting. An
important prerequisite is that this broadcast setting has not been modified since
the first broadcast.

32

4. Filter Navigation Tab

For workbooks there is no filtering option. The only Output Format which
supports filtering is HTML and you must use the Zip option. Filtering a query
which has sales for six different Divisions for example, would result in six separate
files by Division within the zipped file. Any characteristics in the query but not in
the filter can be filtered on.
If Add Unfiltered View is selected, a view will be pre-calculated which does
contain the selected characteristic. (??)
For each characteristic combination that occurs in the control query, a filtered
document is calculated. You should evaluate the number of possible combination
the control query may generate as this could cause a very large number of views
to be created.

Scheduling
1. Immediately on execution with or without saving the settings
2. Execution with Data Change in the InfoProvider
3. Execution at Pre-Defined Time
4. Direct Scheduling in the Background Processing

33

Workbook Pre-calculations
Before you can broadcast workbook results you must first setup the workbook
precalculation service.
Install Microsoft .Net Framework (installed with SAP Frontend)
Install SAP GUI 6.40
Install SAP Netweaver BI Frontend 2004s (BI Add-On).
Install Microsoft Excel 2000 or higher
Several administrative activities are necessary in the BW system for pre-calculation and
distribution of workbooks.
Here are the main steps for setup:
1. Install the pre-calculation software that is part of BI Add On.
2. After Finishing the installation go to the Services Window of your operating system
3. Search for Service called SAP BW PRECALCULATION SERVICE 7.0. Double click on
the service
4. Enable Automatic as Startup type.
5. In the logon tab mark the checkbox 'Allow service to interact with desktop'.
6. Log on to the BW system from the pc where you created the settings above, and
enter transaction RSPRECADMIN in order to Create Precalculation Server.
7. Enter the technical name of the server (max. 10 characters) and a description.
The description is language dependent and appears in the BEx Broadcaster during
selection of a special precalculation server. The precalculation server, which from
a technical viewpoint is an RFC server, appears in the list.
8. Start the Windows service SAP BW Precalculation Service. The precalculation
server is ready and the status display of the precalculation server shows a green
light. You can now see the server in the broadcaster setting dialog for a workbook
precalculation distribution type.
There is a log available to do trouble shooting in SPRO. The path is SAP Reference IMG >
SAP NetWeaver > SAP Business Information Warehouse > Reporting-relevant Settings >
General Reporting Settings in Business Explorer > Administer Precalculation Server >
Select the Documentation for the Server Icon > Display the Front End Log.
A broadcast setting is created from a saved workbook (i.e. Not a temporary workbook)
from the Tools option in the menu bar.

34

If the workbook contains variables, you can enter the desired variant, the data of which is
used to precalculate the workbook, in the Variants field.
Highlighting Select Automatically, the system would use the first available pre-calculation
server from the pre-calculation servers set in Customizing. If the system should use a
special pre-calculation server, then highlight Special Server and specify it. If this special
server is not available, then the system terminates.

Unit #11: Enterprise Portal Integration

You can integrate business-relevant content from SAP Business Intelligence seamlessly
into a SAP Enterprise Portal. The SAP Enterprise Portal enables you to access applications
from other systems and sources, such as the Internet or Intranet. Using one entry point,
you can reach both structured and unstructured information.
SAP BI users see their SAP BI role in the SAP Enterprise portal with the same content. You
can also use the iView concept to integrate SAP BI applications and bring individual Web
applications from SAP BI as an iView into the SAP Enterprise Portal.
Portal Desktop
It refers to the entire portal screen, including content and layout.

35

The three main areas are

1. Header area It consists of
a. Masthead It contains branding elements, user identification, and the
appropriate (based on the portal configuration) function links from among
Help, Personalize, New Session, Log Off and Log On.
b. Tools A persistent area that provides ready access to such key
applications as real-time collaboration, or to a search component.
c. Top-Level Navigation Your entry point for navigating the content available
to your role on your portal.
2. Navigation panel You can reduce, enlarge, collapse, and expand the navigation
panel by clicking the appropriate arrow icons. It contains following Navigational
iViews
a. Detailed Navigation This contains links to all the content that is assigned
to you, displayed in tree format.
b. Dynamic Navigation This area contains iViews whose user interface
controls, such as drop-down lists and links, access databases and retrieve
data related to the content displayed in the content area.
c. Drag&Relate Targets This iView contains a list of links pointing to iViews
that have been configured with drag-on capability, according to user
permissions. When you drag data items from content iViews onto these
links, you receive related information.
It enables you to execute BI applications or other transactions with BI
contents across system boundaries by connecting data from one
application with data in another application.
If you are publishing iViews in the enterprise portal using the BEx Web
Application Designer or the BEx Query Designer, these iViews are Drag &
Relate target objects by default and can therefore be selected as targets in
other iViews.
You can use the Drag & Relate function with Drag & Relate-enabled
characteristics in tables and charts. In charts you are able to use Drag &
Relate from legends, as long as the legend only contains one
characteristic. (Why??)

36

Note that the Drag & Relate function does not replace the Report-Report
Interface(RRI) function. The two functions complement each other.
Possible Drag & Relate Scenarios
BEx Web application BEx Web application
BEx Web application R/3 transaction
R/3 transaction BEx Web application
BEx Web application External (for example, Web Site)
By default you are only able to use the Drag & Relate function for
InfoObjects with the BOR (Business Object Repository) object type
assigned, where the key is exactly the same. Not all characteristics of the
Business Content are assigned. Any correlation that you want to establish
between BI InfoObjects and R/3 objects Unifier has to be defined manually
with the so called Relationship Editor. If you do want to use InfoObjects
that are not listed for Drag&Relate scenarios, first check whether you are
able to build the scenarios using the report-report interface.
The following characteristics are Drag & Relate enabled:
Basic Characteristics
Description
0ABCPROCESS
Business process number
0APPLICANT
Applicant
0APPR_REQU
Appropriation request
0ASSET
Asset subnumber
0BPARTNER
Business partner
0COORDER
Order number
0COSTCENTER
Cost center
0CS_ORDER
Service order
0CUSTOMER
Customer number
0DOC_NUMBER
Sales document
0EMPLOYEE
Employee
0EQUIPMENT
Equipment number
0FUNCT_LOC
Functional location
0INSP_LOT
Inspection lot number
0MATERIAL
Material
0PLANT
Plant
0WORKCENTER
Work center/ resources
d. Related Links This iView contains a list of links whose target topics are
relevant to the iView or portal page with which you are currently working.
The links are predefined on the iView and the page levels (Portal Content
Studio It provides a central environment for developing & managing
different types of portal content such as iViews, pages, layouts, roles etc. ).
Clicking an object in the Related Links iView opens its content in a new
browser window that can be customized.
Portal Favorites iView This iView contains user-compiled links that provide
direct access to Knowledge Management (KM) elements, such as folders
and documents, and portal navigation objects such as pages, or iViews
that run as full-page applications.
1. Content area The integration of SAP BI and SAP EP is especially concentrated on
the content area. Area in which administrative tools, navigation results, and portal
pages with iView content are displayed.
a. Page Title Bar An iView below header area containing items related to the
currently displayed content page.
b. Portal Pages (Services) It consists of iViews and are integrated into Portal
via Portal roles.

37

c. iView SAP Enterprise Portal lets you retrieve data through the use of mini
programs called iViews (integrated views). iViews can access documents,
e-mail, Web sites, intranets, and data in enterprise applications.

Masthead
Top-level Navigation

Tools

Depending on the type of integration, you create various objects with various displays in
the portal. The display types are
1. BEx Web Application as iView Web-based BI application that is displayed as an
iView in the Enterprise Portal. BEx Web applications are BI Web templates
executed in the Web that are created using the BEx Web Application Designer.
2. BEx Web Application as a Document in Knowledge Management In a document
stored in a KM folder with historic data of a Web-based BI application.
3. BEx Web Application as Online Link in Knowledge Management Link to a Webbased BI application with current data in a KM folder. The display requires the
Repository-Manager for BI Metadata.
4. BI Workbook as iView MS Excel workbook with one or more embedded queries
that are displayed in a separate browser window as an iView in the Enterprise
Portal.
5. BI Workbook as a Document in Knowledge Management MS Excel workbook with
one or more embedded queries that is stored as a document with historic data in
a KM folder.
6. BI Query as iView Query that is displayed as a Web-based BI application in a
standard view (Standard Web Template for Ad-hoc Analysis) as an iView in the
Enterprise Portal. It is a special form of a BEx Web application.
7. BEx Query as Online Link in Knowledge Management A link to a query with
current data stored in a KM folder that is displayed with the Standard Web
Template for Ad-hoc Analysis. The display requires the Repository Manager for BI
Metadata.
8. BI Query as a Document in Knowledge Management A document with historic
data for a query stored in a KM folder that is displayed with the Standard Web
Template for Ad-hoc Analysis.

38

9. Individual BI Document as a Document in Knowledge Management as iView A

single document generated in SAP BI (such as documentation for metadata) that
is displayed as in iView in the Enterprise Portal. The document of the link can
either be available through the Repository Manager for BI Document and BI
Metadata in Knowledge Management or a precalculated BEx Web Application in
Knowledge Management.
10. Multiple BI Documents in Knowledge Management as iView Multiple documents
and/or links from a folder in Knowledge Management are displayed with a KM
Navigation iView. The documents and/or links in Knowledge Management can
come from SAP BI and other sources. The layout of a KM Navigation iView can be
adapted using layout sets.
11. Web-Interface as iView Web-capable planning application of BI BPS that is
displayed in the Enterprise Portal as an iView.
12. Components from SAP BI Different applications and tools from SAP BI, such as
the Administrator Workbench, the BEx Query Designer, the BEx Web Application
Designer or the BEx Analyzer.
To distribute or integrate content from SAP BI to the SAP Enterprise Portal you can use
the following tools:
1. BEx broadcasting wizard
2. BEx Broadcaster
3. BEx Web Application Designer
4. BEx Query Designer
5. Portal Content Studio Central environment for the creation & management of
the portal content in the Enterprise Portal. You can use it to edit iViews, Portal
Pages, layout of Portal Pages, Portal Roles, Worksets (Worksets let you bundle
iViews and pages in folder hierarchies, like for roles. Worksets represent generic,
re-usable structures. A workset may be used in any number of roles, and a role
may consist of a number of different worksets. You may not assign worksets to
users. A workset that is to be added to a portal therefore is always part of a role.)
6. KM Content Central environment for the creation & management of documents
& links in Knowledge Management.
7. SAP Role Upload Tool for uploading role definitions and the associated objects
from backend systems (for example a BI system) into the Enterprise Portal.

The tools are customized for various groups of users:

39

1. Information Consumer - Broadcasting Wizard

2. Knowledge Worker - BEx Broadcaster
3. Authors and analysts
a. BEx Query Designer Following options are available to publish a query.
i. Publish in Roles The system saves a link to the current query in
the selected role. This role can later be integrated into the SAP
Enterprise Portal with the function Role Upload.
ii. Publish to Portal

iii. BEx Broadcaster

b. BEx Web Application Designer Same options are available as above with
one additional option.
i. Publish in Role
ii. Publish to Portal Depending on view, the system generates either
iViews in the portal or links in Knowledge Management.
iii. BEx Broadcaster
iv. Copy URL into clipboard
c. BEx Report Designer (For formatted reports)
d. BEx Broadcaster (to generate pre-calculated documents & links to BEx Web
Applications or Queries in Knowledge Management)
4. Administrators Portal Content Studio - KM-Content, SAP Role Upload
The Portal Content Studio is a tool within the portal that enables manual inclusion of
content from SAP BI, i.e. generation of iViews with BI workbooks is not directly supported
from within the BEx Analyzer.
Portal Roles
The Portal Roles view displays the portal roles assigned to the user. This view combines
the storage of iViews in the Portal Content Directory (PCD is the central storage
mechanism of the portal. It stores data from portal content objects such as roles, pages,
system landscape, worksets and many more) and assignment of iViews to a portal role or
portal page. The iViews are always appended to the folders of the portal role or to the
portal page from below. You can also generate links in Knowledge Management in the
Portal Roles view.

40

The system shows all iViews with BEx Web applications from the BEx system that you
logged onto with the BEx Web Application Designer. The content of KM navigation iViews
that are included in the portal roles or portal pages is seamlessly integrated into the
hierarchy of the portal roles. The generated iView receives all the same properties
described under the Portal Content view.
If you select a folder below KM navigation iView, this folder becomes a folder in
Knowledge Management and the system generates a link in Knowledge Management.
Portal system administrators (users with the portal role super_admin_role) are able to see
the contents of the view Portal Roles in the portal under Content Administration Portal
Content. To see the contents of the individual portal roles you need to open the portal
roles for editing.
The main purpose of Role upload is you want to continue to use existing role definitions
for a BI system in the Enterprise Portal since the BI system is the leading system & You
want to use objects from a BI system as content objects to build your roles in Portal.
Initially, you upload all relevant roles and objects from the BI system into the Enterprise
Portal. In the future you want to create and maintain your content objects only in the
portal or you can upload new role created in backend system.
Before you can upload objects from SAP BI into SAP EP, you must carry out the following
steps:
1. Import the plug-in You have to import the SAP Basis Plug-In into every BI system
from which you want to do an upload.
2. Authorizations in the BI System You need the authorization S_RFC in the BI
system for the function group PWP2.
3. Configuring the system landscape in the portal You need to create a system in
the portal within the portal system landscape for every BI system from which you
upload objects.
The uploaded objects are converted into portal objects. You can use these objects in the
portal without making any technical adjustments. The objects from ABAP-based systems
do not need any post-processing in the portal. They are converted to portal objects when
they are uploaded.
Role upload includes following functions
1. Upload roles (single roles and composite roles), or Transactions from the SAP
backend system to the portal.
2. Upload the services and attributes contained in the roles. Uploaded services that
depend on the role are created in the PCD (Portal Content Directory).
3. Single roles are created as either portal roles or worksets with the corresponding
menu hierarchy in the PCD, the same as the attributes of the contained services
(such as transactions).
4. Composite roles are created as either portal roles or worksets with their
corresponding menu hierarchy in the PCD.
5. When objects are uploaded again, you can define whether or not existing objects
should be overwritten.
6. User assignments can also be uploaded to the portal.

41

To upload objects from ABAP-based systems you have to perform the following steps:
1. Choose System Administration Transport Role Upload.
2. Under SAP System select the system from which you want to perform the upload.
3. Select the Object Type you want to upload, for example: Roles & Transactions
4. Enter an ID to search the objects that should actually be uploaded.
5. Select either single objects and choose Add or select Add All for the upload.
6. In this way you can also include objects from different component systems in the
list for uploading, and upload them all together. You should make sure that the
upload packages are divided into clear and meaningful units. SAP therefore
recommends that you only upload objects from one system in a given package.
7. After upload, you should define settings for the upload. e.g. Upload User Mapping
(an uploaded role is automatically assigned to a portal user, a prerequisite for this
is that these users have a corresponding user in the ABAP-based system); Upload
included services (when roles are uploaded, the services included in the roles,
such as transactions, are also uploaded and created as separate objects in the
PCD); Overwrite existing content; Migrate First Folder Level as Entry Point, etc.
8. After defining setting, choose start upload. A new screen displays status of upload
process.
9. Once the upload is completed, you can see the log to check if the objects are
uploaded correctly.
Once the objects have been uploaded from the ABAP-based systems, they can be found
in the Portal Catalog in the relevant folders. In the Portal Catalog, choose Portal Content
Migrated Content SAPComponentSystems. You will find further sub-folders in this
folder. The objects uploaded from the backend systems are stored by the portal object
type to which they were converted and the logical system from which they were
uploaded.

42

Unit #12: Document Integration

43

Enterprise Knowledge Management provides central and role-based access to the

information in your company and creates a connection between structured business data
and unstructured documents.

In the new Document Browser and in the List of Documents web item, you can display
the columns Name, Content., Assignment (to the BI Data) and Author/Change Date. The
columns can be switched on and off online or in the configuration.
If configured, the user can edit the document directly in the Document Browser. The user
can also:
Upload new documents
Add Links to documents (only for documents in the CM Repository)
Add Comments about the documents
These comments are not embedded in the document but simply are references to the
document.

44

KM integration makes all of the KM services available for BI documents (e.g. text search,
text mining, subscription, rating, personal documents, discussions). These services allow
efficient collaboration in your corporate portal and allow individual users and teams to
communicate within their business processes and access shared data in virtual rooms.
You can integrate SAP NetWeaver applications
and third-party applications in rooms.
For each document shown in the Document Browser, you can configure the feedback
service to be available to the user.
For metadata, master data and transaction data, you can define and even link one or
more documents in various formats, versions and languages.
SAP distinguishes between logical documents, which are linked to BI objects using
attributes (e.g. object type and object name), and physical documents which belong to a
specific logical document as individual characteristic values (versions) and which present
meta-descriptions for individual files using their attributes (e.g. language and format).
You can store the individual files either on an SAP
database or on an external content server using an HTTP interface.
Document Classes
1. Metadata The documents for metadata can be defined for BW objects such as
InfoObject, InfoCube, InfoSet, ODS Object & Query.

The name has to be unique among all documents in a document class. The
description appears later as a hyperlink text in the access browser window.
Multipurpose Internet Mail Extensions: MIME is an enhancement of the original
Internet Email Protocol, which enables different types of data to be exchanged on
the Internet. It contains, among other things, audio, video, graphical, and
application programs as well as ASCII files (originally only ASCII files).

45

If you define several documents for a metadata object with the property Online
Documentation, only the last created document displays as an online link, all
previous documents display as link references. The Online Documentation
displays by default as F1 help for the object to which it is assigned.
The ways in which you can reach to the document definition
From Administrator Workbench Documents
For Queries, Query Designer View Documents
For InfoObjects, Administrator Workbench Modeling InfoObjects or
RSD1 Edit InfoObjects
2. Master Data You can define documents for single characteristic values for
master data.

46

Alternate way to reach the document definition is Administrator Workbench

Modeling InfoObjects Maintain master data Choose a characteristics value
& choose Goto Documents.

3. InfoProvider Data You can assign one or more documents to the transaction data
of an InfoProvider. You also have the option of assigning any number of
documents to a combination of characteristic values and key figures. The
documents are then displayed in the report in a context-sensitive fashion, which
means that access to the documents adjusts according to the navigational state
of the report.

47

In characteristic InfoObject maintenance on the General tab page, you determine

whether the characteristic is permitted as a document attribute.

Generally, you can use the context menu in the report and then Documents
Display Documents to reach the Document Browser window and create a new
document using New Comment (or Formatted text or Upload).

48

To link one document from any document class to another document, without actually
linking to this document physically, you have to save both documents in a format that
supports hyperlinks: such as HTML, Microsoft WORD or Microsoft EXCEL.
The context menu in the Report, Documents Comment or Documents Formatted text
to create a new document.
The Repository Framework includes repository managers for documents stored on BI and
in the Content Management (CM) repository on the portal. This allows the user access to
documents stored on either system.
The BI documents for Metadata, Master Data and InfoProvider Data can be integrated
into the portal-based KM in different ways:
With the Repository Manager for BI Documents. In this case the documents are
physically stored on the BI server in the SKWF framework.
With a migration of documents into a CM repository. In this case, the documents
are physically stored in the portal. This allows the documents for master data and
InfoProvider data to be assigned on the hierarchy node level as well (in addition to
the characteristic values).
With the Repository Manager for BI Metadata. In contrast to manually created
documentation for metadata, the HTML-based documentation for the BI metadata
will continue to be generated automatically from the metadata repository as
needed.
For the query, choose Properties Display Document Links and check all the boxes.

Unit #13: Report Report Interface

With a single click you can go to the desired jump target.
Source as Sender:
BEx Query
InfoCube (Settings will apply to all the queries on that InfoCube)
Target as the Receiver:
SAP BW (internal)
o BEx Queries
o Web Applications
o Crystal Reports
o URLs (Web Address)
External SAP Source System
o InfoSet Queries
o Transactions
o ABAP/4 Reports
Source System for Target:
Local
Source System
o One Source System
o All Source Systems Here specify the source system in which you first
want to choose the required report.
For the receiver report you can also assign another name.
If an InfoCube is filled from several InfoSources, you should specify which InfoSource the
data is to be extracted from when allocating the receiver report. Select the desired
InfoSource in the InfoSource column using the F4 help. (Check in system??)
If, during the load process (source system BI), fields are converted into this InfoSource,
then you must create a conversion routine for the read process in the InfoSource. (What

49

are conversion routines??) E.g. Within an RRI, if the InfoObject 0FISCPER (2002.003) is
handed over as parameter to the source system, then this must be divided again into two
individual fields (YEAR 2002 and PERIOD 003). The source system does not have a data
field with the compound information and could not otherwise interpret the parameters
transferred.
Sometimes it is desirable to maintain the field allocations individually for the parameter
transfer of the transmitter to the receiver. For this, there are two exits.
EXIT_SAPLRSBBS_001: Here the field allocation to the DataSource in the source
system can be adapted.
EXIT_SAPLRSBBS_002: This functional module is called before the jump in an ECC
source system. (For Details refer How To paper Drilldown to OLTP using
User Exit mapping)
Calling up specific reports takes a long time if selections are missing. In BI, you can
prevent a called report from starting when jumping if it does not fulfil certain conditions
that you specify as mandatory input. The conditions can be entered via parameters in
Field Assignments dialog box. The system proposes all other field assignments
generically.
Group Description
Type

Default Setting
Generic

Selection Type

Mandatory Entry

No (Empty Checkbox)

Alternative
V Variables
I InfoObject
3 Table Field
P URL Parameters
X Delete
P Parameter
E Individual Values
I Interval
S Selection Option
H Hierarchy nodes
Yes (Indicator Set)

In order to determine the necessary parameter on the Internet side, extensive HTML
knowledge is necessary. The Internet source code must be interpreted. So, for example,
the stock symbol of a customer can be passed to a receiver URL and the current share
quotation can be returned.

50

Unit #14: Managing Query Objects

Deleting Query Objects:
You can delete query in Query Designer or using the path Business Explorer Query
Delete Objects. In order to delete a query object, there must be at least one query,
structure, restricted key figure, or calculated key figure.
If dependent workbooks, Crystal Reports, and views still exist for the objects, the system
gives you the option of deleting the objects from the favorites and roles of all users.
Coping Queries between InfoProviders:
The target InfoProvider must contain all of the InfoObjects in the source InfoProvider.
While coping the queries, you can check the InfoCube Compatibility.
For re-usable sub-objects
Variables are InfoProvider-independent; no copies are created.
No copies are created of global structures, calculated key figures, or restricted key
figures on the InfoProvider level.
The copied queries and sub-objects have a modified technical name that is a
combination of the technical name of the original object and the added elements
_<number>.
Translating Query Objects:
In the Translation function area in the Data Warehousing Workbench, you can translate
short and long texts for BI objects, this includes query objects. Once a query is selected
for translation the worklist automatically includes the sub-objects for translation, for
example restricted key figures, variables. Also the worklist includes any connected
objects such as workbooks.
Performance aspects of Query Definition:
Dos & Donts
Overlapping filters
Too many drill-down characteristics in the initial view

51

Over-use of exclude function Consider using inclusions wherever possible even if

this means that the initial setup of the filters is more complex.
Design aggregates aligned to common filter requirements
Make use of pre-calculated web templates It is possible to schedule the
execution of the query at any desired time. The results are stored within a web
template which means that web users have instant access to ready-made reports.
However do bear in mind that the results are calculated at the time the query was
run and this may mean the data is not always up to date.
Make use of value sets Value sets are containers which hold the results for a
single characteristic which was generated from a scheduled query. For example
you can schedule a query to run each night to calculate the top ten customers by
profit. This list of customers can be stored persistently as a value set so that you
can use this list as a ready-made input for another query.
Switch BEx Analyzer workbook refresh mode to manual If your users want to
select a number of filter values at one time then switch the refresh mode to
manual so that the user can choose the filter values first without the automatic
refresh taking place. This means only one round trip to the InfoProvider is
necessary to process all filters selected.
Use query performance monitoring tools
Ensure the query read mode is set appropriately The query read mode allows
the query developer/administrator to determine the mode in which the OLAP
process operates with regard to extracting reporting data. E.g. you may set the
query to read all free characteristics or hierarchy node levels when the query first
runs. This will mean the initial refresh of the query may be slower but the
subsequent changes to the filters will be much quicker as all the data has already
been read in memory. If you are looking for the initial execution of the query to be
quick then consider setting the read mode so that the free characteristics are only
processed when they are required by the user.
Warm up query cache via broadcaster Whenever a query is refreshed the OLAP
processor checks to see if the required results have already been collected in the
query cache. It is also possible to schedule the filling of the query cache from the
broadcaster so that the cache is 'warmed up'. This has a significant impact on
query performance.
Implement BI Accelerator BI Accelerator (BIA) ensures that the queries run at the
fastest possible speed.

52

Unit #15: Business Content

The Information model in Business Content consists of Roles, Queries & Workbooks (BI
Reports & particular Views of them), underlying InfoProviders, InfoObjects
(Characteristics & KFs used in the report), URs & Extractors.
With Business Content, all the necessary objects can be activated at the same time.
Analytical Applications:
BI release delivers cross-component applications such as analytical applications in the
form of business packages. These business packages deliver targeted access to
information for a process. The areas for analytical applications include Sales Analysis,
Campaign Management, Market Exploration, Procurement Analysis, Production Analysis,
Inventory Analysis, Customer Credit Management, and Packages for E-Analytics. Each
business package consists of an overview page, the cockpit, and additional targetoriented user interfaces known as worksets.
SAP DemoContent:
You can also use SAP DemoContent with delivered examples. The data is stored as flat
files during installation on the BI server. This allows demo scenarios from the Purchasing,
Sales and Distribution, Financial Analysis, Profitability Analysis, Mobile Applications, AC
Nielsen, and SEM to be activated and displayed.
The corresponding roles are:
Demo role (SAP_BW_0D_SAPDEMO)
Demo ACNielsen US (SAP_BW_0D_ACNUS1)
Mobile Executive (SAP_BW_0D_MOBILE_EXECUTIVE)
In addition, the Demo Web Applications are delivered for the following roles:
Sales Cockpit (SAP_BW_SALES_COCKPIT)
Demo Role (SAP_BW_0D_SAPDEMO)
Metadata Repository:

53

It contains definitions of all active objects delivered in Business Content, as well as their
links to other objects. The information includes
Technical data - Technical name, object version, content release, and description
Graphical display - the data flow and star schema (the latter available only for
InfoCubes)
Additional objects - the required objects, objects to which data is forwarded, and
objects that supply data
In the Business Content Browser, when you choose to transfer the objects. The system
then gathers together all the objects related to the query. This takes place as a
background job.
Settings in Business Content
1. Grouping Here, you determined what is to be gathered.
a. Only Necessary Objects This is the minimal variant of Business Content
transfer.
b. In Data Flow Before
c. In Data Flow Afterwards
d. In Data Flow Before & Afterwards This is the maximal variant of Business
Content transfer.
2. Collection Mode
a. Collect Automatically
b. Start Manual Collection The objects to be activated are only collected if
you choose the Gather Dependent Objects function.
3. Type of Transfer
a. Simulate Installation The result of the activation is shown by a green or
red icon beneath the Simulation result header.
b. Install
c. Install in Background Selected objects are activated in Background as a
batch job.
d. Install & Transport Selected objects are activated & written to the
transport request.
4. Display
a. Hierarchy
b. List
5. Install Column indicates objects transferred for the first time or objects
redelivered by Business Content in more recent version
6. Match or Copy Column A checkbox is displayed if it is possible to compare SAP
delivery version with active version. This indicator is set by default, with this, your
version is matched to the new SAP delivery version and enhanced. If you remove
this indicator, the new SAP delivery version is copied in its entirety.

54

Unit #16: Further SAP BI Reporting Tools

BEx Analyzer
BEx Web Application Designer The template can be enhanced with native web
languages such as HTML and Java Script.
BEx Report Designer
NetWeaver Visual Composer It is part of SAP Analytics. BI can provide content to the
Visual Composer via the BI Integration Wizard. It helps in building a closed loop analytical
application which bring together all the key information required (from transactional and
analytical sources) in one place to support my decision making.

Unit #17: Appendix

BW 3.5 Query Designer There are various options for calling up the Query Designer:
From the BEx Analyzer open dialog box
As a separate program using Start Programs Business Explorer Query
Designer
Using the Web Application Designer (see the BEx Web Application Designer unit)
With Crystal Reports (Crystal Reports >=8.5 including CR add-ons for SAP)
It offers different choices depending on the type of object selected
Object Type
Dialog Box Available
Workbook
History, Favorites, Roles
Queries
History, Favorites, Roles, InfoAreas
Stored Query
History, Favorites, Roles, InfoAreas
Views
Exceptions
History, InfoAreas

55

A restriction on a free characteristic affects the entire query, even if the free
characteristic is not in the drilldown. Characteristics in the global filter are only used to
filter the data from the InfoProvider.
Text Elements in BEx Analyzer Report
Author
Last Changed By
InfoProvider
Query Technical Name
Key Date - Contains the date for which the time-dependent master data is
selected. You create a key date either in the query definition (in Query Properties)
or provide the value using a variable. If no key date has been defined, the system
date is taken as the key date.
Changed At
Status of Data For MultiProviders, the current InfoPackages are determined from
the individual BasicCubes and from there, the one with the oldest date is referred
to for the status of the data.
Current User
Last Refreshed - Data and time at which the query data was last refreshed.
Variables, Filter Values, Conditions, Exceptions
BI Migration Aspects
- Objects created with SAP NetWeaver 2004s BEx Tools can no longer be edited with
3.x BEx Tool, however they still appear in the Open Dialog of 3.x Tool.
- It is possible to work with 3.x BEx Tools in connection with the new SAP NetWeaver
2004s server.
- Conversion occurs when the previous objects are opened in the new tool. This
enables transition on an as-needed basis.
- Converted objects are stored as new objects. Old objects are never automatically
deleted.
- There is no new GUID or new objects in database tables.
- The system allows you to edit other BW 3.5 queries even though they have reusing elements of the query that has been edited with NetWeaver 2004s as long
as these do not use any new feature.
- The Query Views do not need to be migrated as they still run even after the query
has been changed with new BEx Query Designer. New BEx Analyzer cannot access
views created by BEx Web Analyzer, but the views created with the BEx Analyzer
are available within the new BEx Web Analyzer.
- Standard workbooks are automatically upgraded whereas custom workbooks need
tro be manually upgraded & also, after saving in the new tool, workbooks cannot
be used in 3.x BEx Analyzer & no longer appear in the Open dialog. Old
workbooks are not deleted after migration.
- GIS functionality & new functions such as Exceptions/Conditions are only available
via BEx Web (Web Application Designer) & are not available in new BEx Analyzer.
- With many new web items in the SAP NetWeaver 2004s BI WAD, some 3.x web
items are not included anymore. E.g. Role Menu Item is replaced by NetWeaver
Portal Functionality. Alert monitor is replaced by Universal Worklist.
- Migration of 3.x Web application is triggered when it is opened with SAP
NetWeaver 2004s BI WAD, but custom JavaScript has to be converted manually.
Migrated versions will not appear in old Open Dialog.
In order to use the new SAP NetWeaver 2004s BI BEx Suite, the usage type BI Java,
including the usage types Portal and AS Java, must be installed. The BEx Suite now can
access any data source including:
- SAP BI InfoProviders
- SAP and non-SAP OLTP sources
- Other data warehouse sources

56

IT & Business Users (High BI Skills) uses BEx design tools such as the BEx Query
Designer, BEx Report Designer and BEx Web Application Designer. Business users make
use of the BEx Web Analyzer and the BEx Analyzer. Information Consumers require
virtually no Business Intelligence skills to access needed information via web
applications, queries, reports and patterns. Usage types SAP BI and SAP BI Java are used
to form a persistence layer and a runtime layer to support these tools.
Within the NetWeaver AS ABAP stack, a persistence layer is formed supporting the
development and execution of web applications, queries, query views and InfoProviders.
Additionally, this persistence layer is necessary for the new BI Accelerator functionality
based on the TREx search engine.
Within the NetWeaver AS J2EE engine, a runtime layer is formed supporting the BEx
Broadcaster, BEx Web, Integrated Planning and Knowledge Management functions of SAP
NetWeaver 2004s BI. Here too is the new Adobe Document Service to support web-based
printing.
Following tools are replaced with SAP NetWeaver 2004s
BEx Browser & Download Scheduler BEx Broadcaster, Enterprise Portal & Knowledge
Management
BEx Reporting Agent BEx Broadcaster, Enterprise Portal & Alert Framework
BEx Ad-hoc Query Designer BEx Web Analyzer
The new runtime is based on the technology of the SAP NetWeaver Portal and the NW AS
J2EE engine and it does not support the Table Interface. The old 3.x runtime is still part of
SAP NetWeaver 2004s BI and can be operated in parallel to the new runtime.
In SAP NetWeaver 2004s, the BEx Broadcaster is shipped in both a 3.x version and in a
SAP NetWeaver 2004s version. The version is accessed depending from which application
version it is called. If you use the new SAP NetWeaver 2004s Broadcaster, you can build
settings on all queries in the system but you have to build them from scratch. You cannot
use already existing 3.x broadcasting settings for queries. You can build settings on all
web applications that were built or converted with the SAP NetWeaver 2004s WAD. You
cannot build settings on old web applications. BW 3.x broadcasting settings for
workbooks can be used as before. There are no changes.
In order to use Mobile Intelligence, customers need to use the 3.x Web Application
Designer as well as the old 3.x BEx runtime. The SAP NetWeaver 2004s runtime does not
support automatic device recognition.

57

Elimination of Internal Business Volumes

With this function you can eliminate the internal business volume by executing a BEx
query. Internal business volume is then no longer displayed in the report.

Eliminations are performed when both the object and partner object belong to the same
node of the hierarchy. Based on the profit center hierarchy, revenue must be eliminated
at the ProfitCtr
Hierarchy profit center node. Based on the region hierarchy, revenue must be
eliminated at the Europe node and the Country node.

58

You have an InfoProvider that contains two characteristic InfoObjects (sender and
receiver) that have the same master data.

To eliminate internal business volume in an InfoProvider, you also have to create a key
figure with a reference to another key figure InfoObject. You then include both of these
key figures in the InfoProvider.
In the InfoObject maintenance for reference KF, you then have an additional tab page,
Elimination.
Enter one or more characteristic pairs here regarding the key figure to be eliminated. The
characteristics of such a pair must have the same reference characteristic. You can also
enter the names of the navigation attributes here.
If several characteristic pairs are maintained, you still have to specify one of the
following, using the selection buttons:
- All characteristic pairs need to be eliminated (then the key figure value is only
eliminated if the elimination condition described above is fulfilled for all
characteristic pairs) => AND

59

Each individual characteristic pair needs to be eliminated (then the key figure
value is eliminated as soon as the elimination condition for a characteristic pair is
fulfilled) => OR

In this example, four eliminations are being performed:

- ICE_REV1 eliminates revenue between a profit center/partner profit center that
are assigned to the same node of the profit center hierarchy.
- ICE_REV2 eliminates revenue between a country/partner country that are
assigned to the same node of the country hierarchy.
- ICE_REV3 eliminates revenue between a profit center/partner profit center where
EITHER the profit centers are assigned to the same node of the profit center
hierarchy OR the countries are assigned to the same node of the country
hierarchy.
- ICE_REV4 eliminates revenue between a profit center/partner profit center where
BOTH the profit centers are assigned to the same node of the profit center
hierarchy AND the countries are assigned to the same node of the country
hierarchy.

The last step is to add the special key figure to the InfoCube. In this way, it is included in
the data model, but not in the database table.

60

The elimination is performed when the query is run with the special key figures. The
queries above illustrate:
- ICE_QUERY1: Rev Profit Ctr is eliminated at the first common node for profit
center PC0301 and partner profit center PC0102, which is the ProfitCtr Hierarchy
node.
- ICE_QUERY2: Rev Country is eliminated at the first common node for country UK
and partner country DE, which is the Europe node, and all higher level nodes
(Country).
- ICE_QUERY3: Rev PCtr OR Ctry is eliminated if EITHER the profit center or
country rule applies.
- ICE_QUERY4: Rev PCtr AND Ctry is eliminated if BOTH the profit center and
country rules apply.

61

Glossary
Crystal report - BI object type. A Crystal Report contains no current data.
MIME Repository - Central repository for MIME objects in an SAP system.
Personal Digital Assistant (PDA) - A hand-held device combining computing,
telephony, and networking functions. A personal digital assistant (PDA) with Open PS can
connect to the SAP system.
Wireless Application Protocol (WAP) - Transfer protocol optimized for the
compressed transfer of WML contents to the cellular phone network.

62