776 Sap BW Web Reporting User Guide

SAP BW
Web Reporting
Function Description
14. February 2001
Version 2.0B13
(Valid as of BW 2.0B Server Patch 13)
SAP AG assumes no responsibility for errors or omissions in these materials.

These materials are provided as is" without a warranty of any kind, either express or implied, including but
not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or
consequential damages that may result from the use of these materials.
SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other
items contained within these materials. SAP has no control over the information that you may
access through the use of hot links contained in these materials and does not endorse your use of
third party web pages nor provide any warranty whatsoever relating to third party web pages.
Contents:
1 Overview............................................................................................................................4
2 Glossary.............................................................................................................................5
3 Templates..........................................................................................................................7
3.1 Structure.................................................................................................................................................... 7
3.2 Object Tags................................................................................................................................................ 7

3.2.1 Structure of the Data Provider Object Tag.............................................................................................. 8
3.2.2 Structure of the Item Object Tag............................................................................................................. 8
3.3 Command URLs........................................................................................................................................ 9
3.4 Language-Dependent Texts...................................................................................................................... 9
4 Object Model...................................................................................................................10
4.1 Templates................................................................................................................................................. 10
4.1.1 Calling up Templates............................................................................................................................ 10
4.1.1.1 Standard Call-up................................................................................................................................ 10
4.1.1.2 Call up template with another data provider......................................................................................12
4.1.1.3 Using default template for a data provider......................................................................................... 12
4.1.2 Exchanging Templates.......................................................................................................................... 12
4.1.3 Change Icon List................................................................................................................................... 13
4.1.4 Release Page....................................................................................................................................... 13
4.1.5 Call up Variable Screen........................................................................................................................ 13
4.1.6 Exit Session.......................................................................................................................................... 13
4.1.7 Entering Variables................................................................................................................................. 14
4.1.7.1 Characteristic Value Variables:.......................................................................................................... 14
4.1.7.2 Hierarchy node variables:.................................................................................................................. 14
4.1.7.3 Hierarchies, formulas and text variables............................................................................................ 15
4.1.8 Change variable values........................................................................................................................ 15
4.2 Data Providers......................................................................................................................................... 15

4.2.1 Generic Attributes................................................................................................................................. 15
4.2.2 Commands........................................................................................................................................... 16
4.2.3 View...................................................................................................................................................... 16
4.2.3.1 Back, Forward, and Back to Start...................................................................................................... 17
4.2.3.2 Filter.................................................................................................................................................. 17
4.2.3.3 Remove Filter.................................................................................................................................... 18
4.2.3.4 Call up Input Help.............................................................................................................................. 19
4.2.3.5 Drilldown............................................................................................................................................ 19
4.2.3.6 Remove Drilldown............................................................................................................................. 20
14.02.2001 Seite2
4.2.3.7 Exchange Characteristics/Structures................................................................................................. 20

4.2.3.8 Switching Axes.................................................................................................................................. 20
4.2.3.9 Set Navigational Status..................................................................................................................... 21
4.2.3.10 Sort............................................................................................................................................ 21
4.2.3.11 Calculate Lists........................................................................................................................... 22
4.2.3.12 Operations in Display Hierarchies............................................................................................. 22
4.2.3.13 Set Exception Status................................................................................................................. 24
4.2.3.14 Set Condition Status.................................................................................................................. 24
4.2.4 Alert Monitor......................................................................................................................................... 25
4.3 Item........................................................................................................................................................... 25
4.3.1 Generic Attributes................................................................................................................................. 25
4.3.2 Items for Views..................................................................................................................................... 26
4.3.2.1 Table.................................................................................................................................................. 26
4.3.2.2 Navigation Block................................................................................................................................ 26
4.3.2.3 Filter.................................................................................................................................................. 27
4.3.2.4 Text Element...................................................................................................................................... 28
4.3.2.5 Chart.................................................................................................................................................. 29
4.3.2.6 Exception Block................................................................................................................................. 29
4.3.2.7 Condition Block.................................................................................................................................. 29
4.3.2.8. Selection List.................................................................................................................................... 29
4.3.2.9 Selection Button Group..................................................................................................................... 30
4.3.2.8 Label.................................................................................................................................................. 30
4.3.3 Item Alert Monitor................................................................................................................................. 31
5 Parameterizing Templates.............................................................................................33
6 Command Sequences....................................................................................................34
7 Forms...............................................................................................................................35
7.1.1 Parameterizing Templates.................................................................................................................... 35
Buttons and Forms in Templates................................................................................................................... 35
14.02.2001 Seite3
1 Overview
Business Information Warehouse Web Reporting enables you to access BW data using an Internet browser. In most
cases, an Internet browser is installed at the same time as the operating system. No additional software installation is
required. Demands on the Web browser are minimal, as the solution offered is based entirely on HTML.
This document is intended for Web designers who want to create complex applications (information cockpits, and so
on) on the basis of BW Web Reporting.
14.02.2001 Seite4
2 Glossary
Alert Monitor
The Alert Monitor presents the views that were retrieved with the help of the Reporting Agent in a background process
as a list or hierarchy, and supports jumps to these views.
BW URL
By using <SAP_BW_URL Attribute1=Value1' ...> in a template, you can create links that transfer
data providers or items from one state to another. For example, you can alter the size of a chart, or
set a filter value for a view. Possible attributes and their values will be explained later in this
document.
Data Provider
Object that serves as a data source. Data for an item, for example, is obtained from this object.
Item
Object set into an HTML page that gets data from a data provider. Examples are tables, navigation
blocks, charts, exception blocks, condition blocks, text elements, filter values and the Alert Monitor.
Item Table
Item that gets data from a view in order to create a table for an HTML page. In addition to the table,
navigation links are also incorporated.
Item Text Element

Item that presents the text elements of a view. Text elements include the general text elements,
variables and static filter values. These are the same text elements that already exist in the Business
Explorer Analyzer. It is also possible to select individual text elements.
Item Filter
Item that displays the view's filter values created by navigating. It is also possible to select
individual text elements.
Item Nav Block

Item that gets data from a view in order to create a generic navigation block for an HTML page. This
block contains buttons that take characteristics into the rows or columns, for example.
Item Chart
Item that gets data from a view in order to create a diagram for an HTML page. The attributes (chart
type,...) are specified in the Web Publisher.
Item Exception
Item that lists the available exceptions for a View with their status (active / not active). You can
change the status of the exceptions using buttons.
Item Condition
Item that lists the available conditions for a View with their status (active / not active). You can
change the status of the conditions using buttons.
14.02.2001 Seite5
Comment Tag
Up to and including 2.0A Patch 4, a comment tag was delivered by the Web Publisher as a bookmark
for an item with a view for use in a template. These comments looked like this: . An object tag has been used since 2.0A Patch 5 to enable
you to better edit the template and to make better use of enhancements.
Object Tag
With the help of the object tag, you create data providers and items in a template. The object tags are
replaced by the created items HTML when you create an HTML page.
Style Sheet
The Cascading Style Sheets (CSS) are an HTML enhancement. You can define formats in them.
Styles are used in HTML created by BW Web Reporting items. Example CSS files that customers can
change are included in the ITS scope of supply. Access a style sheet in the template if possible.
Template
The template specifies the structure of an HTML page for Web Reporting. Using the Web Publisher,
you can insert bookmarks for items, data providers and BW URLs in an HTML document. The HTML
document with BW-specific bookmarks is named in the following template and can be checked into
the Web Publisher. The page is then available for Web Reporting.
View
Synonym for a navigational state (view) stored in the BEx Browser.
Web Publisher
The Web Publisher is part of the Business Explorer Analyzer (BEx). You can store navigational
states as views. In turn, you can create items for these views.
14.02.2001 Seite6
3 Templates
A template specifies the structure of an HTML page for Web Reporting. Using the Web Publisher, you
can insert bookmarks for items (in the form of object tags), data providers (in the form of Object tags)
and BW URLs in an HTML document. The HTML document with BW-specific bookmarks is named in
the following template and can be checked into the Web Publisher. The page is then available for Web
Reporting. A template is identified by the WbID (workbook ID), the key for the workbook under which
the template is stored, and the PageID, the name of the template.
3.1 Structure
A template is a basic framework for an HTML page containing bookmarks for items and command URLs. Usually, data
providers are created first, followed by items and command URLs for an HTML page.
The following is an example of a simple template with a navigation block and a table:
<html>
<head>
<linkrel="stylesheet"href="/sap/its/mimes/webrfc/bw/SAPBEx.css">
<title>NewPage1</title>
</head>
<body>
<!Createthedataprovider>
<object>
<paramname='OWNER'value='SAP_BW'>
<paramname='CMD'value='SET_DATA_PROVIDER'>
<paramname='DATA_PROVIDER'value='View1'>
<paramname='VIEWID'value='Viewabc'>
DATA_PROVIDER:View1
</object>
<!Createandgetthenavigationalblock>
<objectWIDTH="350">
<paramname='CMD'value='GET_ITEM'>
<paramname='ITEM'value='NavBlock'>
<paramname='ITEMID'value='NavBlock'>
ITEM:NavBlock
</object>
<br>
<!Createandgetthetable>
<objectWIDTH="600">
<paramname='ITEM'value='Table'>
<paramname='ITEMID'value='Table'>
ITEM:Table
</object>
</body>
14.02.2001 Seite7
3.2 Object Tags

Using the object tag, you can create data providers and items in a template and provide them with parameters. The
parameters for items can override settings made in the Web Publisher (for example, width and height). Additionally, you
can send a generic command (filter, change attributes) or a command sequence (see Command Sequences section) to
the data provider at the start of the page. To do this, the parameters are added to the object tag (see examples).
An object tag starts with <object...> and ends with </object>. For identification purposes, SAP_BW object tags are
given the parameter Owner with the value SAP_BW. . Only objects of this type are transformed into templates.
All other objects are transferred unchanged into the HTML page.
Parameters can be set at the start of the object tag
<objectWIDTH='350'HEIGHT='234'owner='SAP_BW'...></object>
as well as within the object tag in the form of parameter tags.
<object>
<paramname='owner'value='SAP_BW'>
...
</object>
Object tags are displayed in many HTML editors as well as in non-HTML code mode. FrontPage offers the extra option
of changing the size and maintaining the object tag parameters. Object tags can usually be moved using drag and drop
(within a page).
3.2.1 Structure of the Data Provider Object Tag

The parameters required to create a data provider are provided by the Web Publisher. You can add further parameters,
for example, to set up input help or to send a command to the data provider before calling up the page.
The 'Cmd' parameter must be filled with 'SET_DATA_PROVIDER' to indicate that you are creating a data provider.
Examples:
Create view:
<object>
DATA_PROVIDER:View1
</object>
Create view with filter on country USA and style sheet for input help:
<object>
<paramname='FILTER_IOBJNM'value='0COUNTRY'>
<paramname='FILTER_VALUE'value='US'>
<paramname='STYLE_SHEET'value='/sap/its/mimes/webrfc/BWReport.css'>
DATA_PROVIDER:View1
</object>
3.2.2 Structure of the Item Object Tag

The parameters required to create an item are provided by the Web Publisher. You can add further parameters, for
example, to subsequently adjust the size or to set a title.
The parameter 'Cmd' must be filled with 'Get_Item' to indicate that you are creating an item
Examples:
Create item:
<object>
<paramname='ITEM'value='NavBlock'>
14.02.2001 Seite8
<paramname='ITEMID'value='NavBlock'>
ITEM:NavBlock
</object>
Create item with height 400 pixels, width 500 pixels and title Business Graphic:
<objectWIDTH='400'HEIGHT='500'>
<paramname='ITEM'value='Chart1'>
<paramname='ITEMID'value='PieChart'>
<paramname='GENERATE_CAPTION'value='X'>
<paramname='Caption'value='BusinessGrafik'>
ITEM:Chart1
</object>
3.3 Command URLs

In addition to object tags, you can also set command URLs in a template. They serve as bookmarks for URLs or to
mark the start of a URL. They have the following structure:
<SAP_BW_URLParameter1='Value1'Parameter2='Value2'...>
and create a URL in the HTML page similar to the URL shown below:
/scripts/wgate//?
_function=WEBQUERY&~SESSION=0000.003f.5f516493&pageno=1&request_No=8&Parameter1=
Value1&Parameter2=Value2&...
This URL requests a new page from the ITS. The parameters are processed here.
You can find examples of command URLs in the following section.
3.4 Language-Dependent Texts

The SAP_BW_TEXT tag is another BW tag. Using this tag you can install language-dependent texts in a Web site. To
do this, you create text elements for an ABAP report. These can then be translated.
You can access the texts as follows:
<SAP_BW_TEXT PROGRAM=MYREPORT KEY=001>
14.02.2001 Seite9
4 Object Model
a le rt_ m o n ito r
d a ta _ p ro v id e r v ie w
0 ..*
1
te m p la te 1 1
0 ..*
ite m _ ta b le
ite m _ n a v _ b lo c k
ite m ite m _ filte r
0 ..*
ite m _ te x t_ e le m e n ts
ite m _ e x c e p tio n
ite m _ c o n d itio n
ite m _ filte r_ d d o w n
ite m _ filte r _ r a d io
ite m _ la b e l
ite m _ c h a r
ite m _ m a p
ite m _ a le r t_ m o n ito r
The aim of Web Reporting is to create HTML pages that reproduce data from BW. The Web designer uses templates to
specify the data providers that will supply the data, the way in which (items) this data will be presented, and in which
additional operations are to be made available (BW URLs).
If a Web Reporting request is sent to the BW server, an object template is first created that decides the structure of the
requested HTML page. On the basis of this template, the following objects are created:
Data Provider
Item
4.1 Templates
The template specifies the structure of an HTML page for Web Reporting. Using the Web Publisher, you can insert
bookmarks for items, data providers and BW URLs in an HTML document. The HTML document with BW-specific
bookmarks is named in the following template and can be checked into the Web Publisher. The page is then available for
Web Reporting.
4.1.1 Calling up Templates

4.1.1.1 Standard Call-up
CMD LDOC
Parameter Description
WBID Excel workbook key under which the template is stored in
the BEx
The workbook must be stored in BW (favorites, activity groups
/ roles).
PAGEID Template name
Name under which the template is stored in the Web Publisher.
STATELESS (optional) Reduce the link to the server as soon as possible
14.02.2001 Seite10
'X' = Yes, ' ' = No For pages that are only used for display without further
navigation, it is better to set the attribute STATELESS. The
session on the application server according to the structure of
the page is reduced again. This saves on resources on the
application server. The GENERATE_LINKS attribute is
automatically set to ' ' when you create the page.
If this attribute is not specified, it is assumed that the page is
still needed for navigation.
STYLE_SHEET (optional) Path to a style sheet, which is used for the presentation of
the page. This overwrites any style sheet the template may
have assigned already.
TRACE (optional) Switch OLAP Trace on
'X' = switch on, ' ' = do not switch on With SAP, you usually need a trace to analyze problems. You
can switch it on with the help of note 112458 or by using the
TRACE parameter.
VARIABLE_SCREEN (optional) Display Variable Screen
'X' = Display variable screen, ' ' = do not If you call up a template containing views with variables ready
display, if possible for input, you can use this parameter to display the variable
screen. If you do not set this parameter, or set it to ' ', the
variable screen is suppressed if possible. In any case, you can
see whether required variables have not been filled, for
example.
MELT_VARIABLES (optional) Melt Variables

'X' = melt, ' ' = display every query separately If you call up a template containing several views with
variables ready for input, and you want to display the variable
screen, you can use this parameter to determine whether you
want the variables that are used in all views in the same context
(same InfoCube, same values), to be ready for input once only.
VARIABLES_CLEAR (optional) Reset Variables

'X' = Reset variables, ' ' = do not reset If you call up a template containing several views with
variables ready for input, you can specify this parameter to
clear what you entered for the variables by the view. The
variables take on the entries made in the variable definition.
SUPPRESS_WARNINGS (optional) Suppress Warnings

X = Do not display warnings, = Display You can suppress the warning display using this parameter.
warnings Termination messages are still displayed.
DATA_MODE (optional) Data mode

NEW = Use current data This parameter is optional. If it is not specified, requests
'STORED' = use precalculated data are always sent to the OLAP processor and current data
'HYBRID' = use precalculated data, if this is is read.
missing, request current data For the modes STORED and HYBRID you have to have
precalculated data using the Reporting Agent. You can find
further information in the documentation enhancement 2.0B
Exceptions, Conditions, Reporting Agent.
14.02.2001 Seite11
Examples:
Call up template without navigating:
http://your_its/scripts/wgate/WebRFC/!?
_function=WEBQUERY&CMD=LDOC&WBID=D9EW857MLP6EN0AEM9BZSQP3C&PAGEID=Template_Name&
STATELESS=X
Call up template with trace switched on
TRACE=X
Call up template with cleared variables and active variable screen.
_function=WEBQUERY&CMD=LDOC&WBID=D9EW857MLP6EN0AEM9BZSQP3C&PAGEID=Template_Name
&
VARIABLE_SCREEN=X&VARIABLES_CLEAR=X
4.1.1.2 Call up template with another data provider

This method replaces all data providers of the type view with the specified data providers. This makes it possible to
make a query or view available without making any further settings in the Web, and then use predefined templates for
the page layout.
As well as those used in the standard call-up, this method also has the following parameters:
Call-up for presenting a query:
INFOCUBE Technical name of the InfoCube
QUERY Technical name of the query
VARIANT (optional) Variant, if you need to enter a variable
Call-up for presenting a different view:
VIEWID Key for a view
A view gets its initial status from the specified ViewID. The
ViewID identifies a view within a workbook
DATA_PROVIDER_WBID Excel workbook key under which the data provider is
stored in the BEx
/ roles).
VARIANT (optional) Variant, if you need to enter a variable
Examples:
Displaying a query using a self-selected template:
infocube=myCube&query=myQuery
4.1.1.3 Using default template for a data provider

If you call the previous variant without specifying a WBID or a PAGEID, the default template is used. You can make
this setting in BW Customizing under Reporting-relevant Settings -> Web Reporting -> Determine default web page'.
If no setting is made here, a template created by SAP is used.
Example:
Query without making any settings on the Web:
_function=WEBQUERY&CMD=LDOC
&infocube=myCube&query=myQuery
14.02.2001 Seite12
4.1.2 Exchanging Templates

As well as being able to call one up, you can exchange a template. All items and data_providers of the start template are
retained. The items and data_providers that are in the new template and for which there is no object of the same name
are created again. The objects are identified by their logical name.
The basic difference in calling up the template is that already existing objects are transferred unchanged, meaning, for
example, the navigation status of a view is retained.
This function is designed specifically to switch between overview pages (often only with diagrams) to detail pages
(with tables and navigation blocks).
CMD CHANGE_TEMPLATE
WBID Excel workbook key under which the template is stored in
the BEx
/ roles).
PAGEID Template name
Examples:
<SAP_BW_URL CMD='CHANGE_TEMPLATE' WBID='D9EW857MLP6EN0AEM9BZSQP3C'
PAGEID='DETAILS'>
4.1.3 Change Icon List

This command makes it possible to use more icons than usual for specific Web pages, for example, for expanding and
collapsing hierarchies. A different list of icons is assigned to the template. This, however, does not affect the names of
the icons. In the new list, the icons must appear with their original name, but can be formulated differently.
CMD SET_URLS
ICON_PREFIX Relative path for a list of icons on the ITS
Example:
Displaying a template with icons from a different list:
This example uses a command sequence. See "Command Sequences" for more details.
&cmd_1=cmd%3DSET_URLS%26ICON_PREFIX%3DmyPath
4.1.4 Release Page

You can use this command to remove the current page with all its objects from the memory of the application server.
The page can no longer be addressed. You must create it anew with the command Call up template.
You can use other commands as follow-up commands to initialize other pages, for example.
CMD PAGE_FREE
Examples:
<SAP_BW_URL CMD='PAGE_FREE'>
4.1.5 Call up Variable Screen

This command allows you to call up the variable screen again for the current page. The variable screen then displays the
previous variable values to be changed.
New values can also be transferred as explained in the unit Entering Variables. Alongside the values that have already
been set, these new values serve as preassignments for the variable screen.
If you want the variable screen to appear when you call up the page, you must adjust the template (see section Call up
Template -> Default Call-up).
14.02.2001 Seite13
CMD PROCESS_VARIABLES
SUBCMD VARIABLE_SCREEN
Examples:
<SAP_BW_URL CMD='PROCESS_VARIABLES' SUBCMD='VARIABLE_SCREEN'>
4.1.6 Exit Session

You can use this command to close the active session on the application server.
CMD LOG_OFF
~command (optional) End Logon to ITS
'logoff' = log off from the ITS If this parameter is set, you need to log on again to the system
with your user and password if you want to use the system
again.
Example:
<SAP_BW_URL CMD='LOG_OFF' ~command='logoff'>
4.1.7 Entering Variables

Query variables play a central role in BW. They can be used to filter the entire query of only parts of the query by
values, before the data is read for the first time. There are variables with automatic replacement, replacement from
authorizations, or variables that are ready for input.
You can process these variables in a dark color (without variable screen), or in a light color (with variable screen). In
both cases you should enter parameters for the variables. All types of variables ready for input are supported here.
Contrary to filtering, you must specify the external value of the variables. This means, for example, that the data is
copied over as it was entered.
You can also fill variables by parameterizing the URL. The values of the variables are separated from one another by
different indexes.
In the following, '_I' indicates the index in the parameter.
4.1.7.1 Characteristic Value Variables:
Parameter variables are filled as follows:
VAR_NAME_I Technical name of the variable
VAR_VALUE_EXT_I Characteristic value in external display
Key of the characteristic value as it is displayed externally.
Interval variables are filled as follows:
VAR_VALUE_LOW_EXT_I From-characteristic value in external display
VAR_VALUE_HIGH_EXT_I To-characteristic value in external display
Selection option variables are filled as follows:
VAR_OPERATOR_I Operator
EQ' = single value, 'BT' = interval, 'LT' = less than, 'LE' less
equal, 'GT' = greater than, 'GE' = greater equal
VAR_VALUE_LOW_EXT_I From-characteristic value in external display
VAR_VALUE_HIGH_EXT_I To-characteristic value in external display
Only specify this value with VAR_OPERATOR='BT'.
VAR_SIGN_I Effect of the row
'I' found values add,
'E' found values remove.
4.1.7.2 Hierarchy node variables:
14.02.2001 Seite14
VAR_VALUE_EXT_I Node key in external display
Name of the node characteristic
VAR_NODE_IOBJNM_I Name of the node characteristic
For characteristic nodes, you must enter the characteristic
name, like you do for text nodes (0HIER_NODE).
4.1.7.3 Hierarchies, formulas and text variables
VAR_VALUE_EXT_I Hierarchy name, formula value, text
Examples:
Filling parameter variables:
http://yourITS/&pageid=yourTemplate&var_name_1=myParameterVariable&var_value_ext_1=4711
Filling parameter variable (4711) and selection option variable (1, 7 to 12):
http://yourITS/
&pageid=yourTemplate&var_name_1=myParameterVariable&var_value_ext_1=4711&var_name_2=mySelOptVa
r&var_operator_2=EQ&var_sign_2=I&var_value_low_ext_2=1&var_name_3=mySelOptVar&var_operator_3=
BT&var_sign_3=I&var_value_low_ext_3=7&var_value_high_ext_3=12
Hierarchy node variable (DE, 0HIER_NODE):

http://yourITS/
&pageid=yourTemplate&var_name_1=myHryNodeVariable&var_value_ext_1=DE&var_node_iobjnm_1=0HIER
_NODE
4.1.8 Change variable values

You can use this command to change variable values for the active page.
Variable values are enterd as explained in the unit Entering Variables. Variables that are not specified keep their
previous value.
CMD PROCESS_VARIABLES
SUBCMD VAR_SUBMIT
Examples:
<SAP_BW_URL CMD='PROCESS_VARIABLES' SUBCMD='VAR_SUBMIT'
VAR_NAME_1=myParameterVariable VAR_VALUE_EXT_1=4711>
4.2 Data Providers

Data providers are objects that deliver data. You can change the status of the data provider by navigating through the
data or by setting parameters for the call. A data provider can supply any number of items with data.
4.2.1 Generic Attributes

Generic attributes are attributes that are valid for every data provider. These attributes are required right from the point
of creating the data provider
Attribute Description
DATA_PROVIDER ( or name ) Logical name of the data provider
You cannot change this attribute with a This name is used to couple items with this data provider and
command URL. to send commands to the data provider. The name must be
unique within the template.
WBID ( or DATA_PROVIDER_WBID ) Excel workbook key under which the data provider is
14.02.2001 Seite15
(optional) stored in the BEx

You cannot change this attribute with a The workbook must be stored in BW (favorites, activity groups
command URL. / roles).
If this parameter is not specified, the template WBID is used
instead.
4.2.2 Commands
You can use commands like filter with data providers. These commands usually have to be supplied with parameters.
Some commands allow you to enter a list of parameter values. The parameter name is given an index _1, _2, ... .
This is shown in the following by Parametername_n.
For every command at least one example is specified, relating in particular to the syntax, as described in the section
Command URLs.
All commands have the following parameters in common:
CMD Command name
Most commands are triggered using this parameter. In addition
to this kind of command there are also generic commands
whose parameters can be added to other commands. Generic
commands are always applied after the named commands.
DATA_PROVIDER Data provider name
DATA_PROVIDER_N A command can be applied to several data providers. In
addition to explicit information from a data provider, you can
also specify a list of data providers or restrict the quantity using
wildcards (multi='X'). The command is then applied to all these
data providers as long as they allow this operation.
You must specify the data provider(s).
MULTI Use DATA_PROVIDER as template
Optional If MULTI is set to 'X', then the command is applied to all the
'X' = Yes, ' ' = No data providers that contain the template. * corresponds, for
example, to all data providers.
Examples:
Apply command to 'DP 1':
<SAP_BW_URL DATA_PROVIDER='DP 1' CMD='' ...>
Apply command to 'DP 1' and 'DP 2':

<SAP_BW_URL DATA_PROVIDER_1='DP 1' DATA_PROVIDER_1='DP 2' CMD='...''
Apply command to all data providers containing 'USA' in the name:

<SAP_BW_URL DATA_PROVIDER='*USA*' MULTI='X' CMD='...' ...>
4.2.3 View
You can store different views of a BW query. When you call a template, a view (not a database view) with the saved
navigational state is created on the server.
Views have the following attributes:
ViewID Key for a view
You cannot change this attribute with a A view gets its initial status from the specified ViewID. The
command URL. ViewID identifies a view within a workbook. By entering the
WbID you can use views from various workbooks in a
template.
WBID ( or DATA_PROVIDER_WBID ) Excel workbook key under which the data provider is
(optional) stored in the BEx
You cannot change this attribute with a The workbook must be stored in BW (favorites, activity groups
command URL. / roles).
14.02.2001 Seite16

instead.
VARIANT (optional) Name of variant for variable assignment
You cannot change this attribute with a When you save a view, the current variable values are also
command URL. saved. You can override these values by entering a variant
(optional). You can create variants from the variable screen.
STYLE_SHEET (optional) Path to style sheet to be used for displaying input help.
If you do not make an entry here, the template style sheet is
used by default.
HOME_FRAME (optional) Mainframe name
If you are using HTML frame technology to display data, and
want to display Input Help in a different frame to that of the
template, then for the view, you have to fill the attribute
HOME_FRAME with the frame name of the frame in which
the template is displayed. You also have to specify the attribute
TARGET_HELP_FRAME for the item navigation block.
BLOCK_SIZE Number of rows in a block
This parameter defines the amount of rows displayed before an
index for navigating to other blocks is begun. If the value is
0, the table is displayed in its entirety without taking the
number of rows into account.
The following commands can be applied for a view.

4.2.3.1 Back, Forward, and Back to Start
You can undo the last action in a view. Likewise, if you have undone one or more actions, you can redo them. Unlike
the way you use the "Back" and "Forward" functions in the Web browser, these commands only apply to the specified
data provider, and not to the entire page.
CMD Description
BACK Undoes the last action performed in this view.
RESET Jumps back to the navigational status that you saw when you
called up the page.
FORWARD Performs an undone action again.
Examples:
You want to undo the last action in view 1:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='BACK'>
You want to reset all views to how they were when you called up the page:
<SAP_BW_URLDATA_PROVIDER='*USA*'MULTI='X'CMD='...'
4.2.3.2 Filter
You can set filter values for characteristics and structures for a view. You can also set several filters for the same
characteristic / structure or even for different characteristics / structures within a command call. 'Filter' is a generic
command and does not require any entry for the 'CMD' parameter.
The filter parameters can be added to every other command!
Filtering is carried out at the end of an operation.
FILTER_IOBJNM Name of characteristic / structure according to which you
FILTER_IOBJNM_N (optional) want to filter
Specify the technical name of the characteristic (for example,
0COUNTRY) / structure (25 place character string) here.
FILTER_COLLAPS (optional) Remove filter characteristics from drilldown
Take the characteristics that are specified under
FILTER_IOBJNM according to the axis filter. If the parameter
'X' = Yes, ' ' = No is not specified, the value X = yes is used.
VAR_SIGN_N (optional) Effect of the row
'I' found values add,
14.02.2001 Seite17
'E' found values remove.

If the parameter is not specified, the default is 'I'.
If the entry for FILTER_IOBJNM_N is missing from an index n, the value FILTER_IOBJNM is used if available.
The following additional parameters are specified for the single value filters,:
FILTER_VALUE Filter value
FILTER_VALUE_N Value by which you want to set the filter. If you choose the
FILTER_VALUE_EXT variant with the ending EXT, you must specify the complete
FILTER_VALUE_EXT_N compounded value externally, for example, 24.12.2000. If the
ending EXT is not used, you must specify the complete
compounded value internally, for example, 20001224 for
24.12.2000.
FILTER_VALUE_TYPE (optional) Type of value, specified under FILTER_VALUE
FILTER_VALUE_TYPE_N (optional) 'VALUE' : Key of a characteristic value.
'VARIABLE_EXIT' : Name of an exit variable. This resets the
filter with the values of the variable exit. Parameter, interval,
and selection option variables are supported for customer and
SAP exit variables and for the default values of variables.
OPERATOR (optional) Operator
OPERATOR_N (optional) 'EQ' = Single value, 'LT' = less than, 'LE' less equal, 'GT' =
greater than, 'GE' = greater than.
If you do not specify an operator, 'EQ' is used.
The following additional parameters are specified for filtering intervals:
FILTER_VALUE_LOW Filter value lower limit (not compounded)
FILTER_VALUE_LOW_N
FILTER_VALUE_LOW_EXT
FILTER_VALUE_LOW_EXT_N
FILTER_VALUE_HIGH Filter value upper limit (not compounded)

FILTER_VALUE_HIGH_N
FILTER_VALUE_HIGH_EXT
FILTER_VALUE_HIGH_EXT_N
The following additional parameters are given for filtering hierarchy nodes:
FILTER_VALUE Hierarchy node name
FILTER_VALUE_N
FILTER_NODE_IOBJNM_(optional) Name of the node characteristic

FILTER_NODE_IOBJNM_N (optional) Must be specified if you are filtering by node hierarchy node.
Examples:
Filter view 1 according to country Germany:
<SAP_BW_URLDATA_PROVIDER='View1'FILTER_IOBJNM='0COUNTRY'FILTER_VALUE='DE'>
Filter view 1 according to the first 3 months:
<SAP_BW_URLDATA_PROVIDER='View1'FILTER_IOBJNM='0CALMONTH'
FILTER_VALUE_LOW_EXT='1'FILTER_VALUE_HIGH_EXT='3'>
Filter all views according to cost and the countries Germany and USA:
<SAP_BW_URLDATA_PROVIDER='*'MULTI='X'
FILTER_IOBJNM_1='DRB9ZVVMBCHVX4F04Z1JGKYVC'
14.02.2001 Seite18
FILTER_VALUE_1='DTG057U7OQ8K2ALKCMR2AWM14'FILTER_IOBJNM_2='0COUNTRY'
FILTER_VALUE_2='DE'FILTER_IOBJNM_3='0COUNTRY'FILTER_VALUE_3='US'>
Filter all views according to the current month:
<SAP_BW_URLDATA_PROVIDER='*'MULTI='X'FILTER_IOBJNM='0CALMONTH'
FILTER_VALUE='0CMONTH'FILTER_VALUE_TYPE='VARIABLE_EXIT'>
4.2.3.3 Remove Filter

By calling this command, you can remove the filter for one or more views relating to a characteristic or a structure.
CMD Remove_Filter
IOBJNM Name of characteristic / structure
IOBJNM_N Enter here the technical name of the characteristic (for
example, 0COUNTRY) / structure (25-place character string)
whose filter you want to remove. You can also specify a list of
characteristics/structures.
ALL Remove all filters
'X' = Yes, ' ' = No As an alternative to listing characteristics and structures, you
can also remove all the filters.
Examples:
Remove filter from country for view 1:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Remove_Filter'IOBJNM='0COUNTRY'>
Remove filter from country for all views and filter according to calendar year 2000:
<SAP_BW_URLDATA_PROVIDER='*'MULTI='X'CMD='Remove_Filter'IOBJNM='0COUNTRY'
FILTER_IOBJNM='0CALYEAR'FILTER_VALUE='2000'>
Remove all filters from all views and filter according to the calendar year 2000:
<SAP_BW_URLDATA_PROVIDER='*'MULTI='X'CMD='Remove_Filter'ALL='X'
4.2.3.4 Call up Input Help

When you call up this command, you can get to Input Help for a characteristic or a structure of a view.
CMD Process_help_window
HELP_SERVICE DP_VIEW_FILTER
Enter here the technical name of the characteristic (for
for which you want to call up Input Help.
BOOKED_VALUES Use booked values as Input Help
If you do not specify this parameter, or if it is set to 'X', the
Input Help shows only values that are also booked in the
InfoCube within the current valid filter conditions. Under
certain circumstances, this can take a long time. If the
parameter is set to ' ', all the values of the dimension table are
displayed. This may be quicker, but it means that those values
that do not meet the current filter conditions in the InfoCube
are also shown. And they give the result "No relevant data
found" when you filter.
4.2.3.5 Drilldown
By calling this command, you can change the position of a characteristic or a structure for one or more views.
CMD Expand
14.02.2001 Seite19

you want to include in the drilldown.
AXIS (optional) Axis to which you want to move the characteristic /
'X' = Columns structure
'Y' = Rows The characteristic / structure is moved to the axis behind the
' ' = Free characteristic (=remove drilldown) other characteristics / structures if you do not specify
PARENT_IOBJNM. If you do not specify the 'axis' parameter,
then the value 'Y' is taken for characteristics and 'X' for
structures.
PARENT_IOBJNM (optional) Name of a characteristic / structure on the axis
You can move a characteristic / structure behind another on an
axis if you enter this parameter.
Examples:
Drilldown view 1 according to country:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Expand'IOBJNM='0COUNTRY'>
Drilldown view 1 according to country and filter according to calendar year 2000:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Expand'IOBJNM='0COUNTRY'
Move periods 1, 2 and 3 (2000) from view 1 to the columns:

<SAP_BW_URLDATA_PROVIDER='View1'CMD='Expand'IOBJNM='0FISCPER'AXIS='X'
FILTER_IOBJNM='0FISCPER'FILTER_VALUE_1='2000001'FILTER_VALUE_2='2000002'
FILTER_VALUE_3='2000003'>
4.2.3.6 Remove Drilldown

By calling this command you can remove a characteristic or a structure from the drilldown for one or more views. This
command corresponds to the drilldown command if the parameter AXIS=' ' is set.
CMD Collaps
that you want to remove from the drilldown.
Examples:
Remove drilldown according to country from view 1:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Collaps'IOBJNM='0COUNTRY'>
4.2.3.7 Exchange Characteristics/Structures

By calling this command you can replace a characteristic or a structure with another characteristic or structure for one
or more views.
CMD Exchange
IOBJNM_1 Name of characteristic / structure 1
Enter here the technical name of the 1st characteristic (for
example, 0COUNTRY) / 1st structure (25-place character
string).
IOBJNM_2 Name of characteristic / structure 2
Enter here the technical name of the 2nd characteristic (for
example, 0COUNTRY) / 2nd structure (25-place character
string).
Examples:
Replace drilldown according to country with drilldown according to calendar year in view 1:
14.02.2001 Seite20
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Exchange'IOBJNM_1='0COUNTRY'
IOBJNM_2='0CALYEAR'>
or:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Exchange'IOBJNM_1='0CALYEAR'
IOBJNM_2='0COUNTRY'>
4.2.3.8 Switching Axes

You can use this command to swap the roles of the axes (list is copied). All chars and structures are taken from the rows
and put in reverse in the columns.
CMD Switch_Axis
Example:
Swap axes for view 1:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='SWITCH_AXIS'>
4.2.3.9 Set Navigational Status

When you call up this command, you can rearrange characteristics and structures on the axis.
CMD SET_NAV_STATE
ALL Arrange all characteristics and structures again
'X' = Yes, ' ' = No If this attribute is set to 'X', all characteristics and structures are
first taken from the axis and then arranged again according to
the other parameters. If you do not set the parameter, or it is set
to , the characteristics in the list are arranged by the axes
parameter.

IOBJNM_N Enter the technical name of the characteristic (for example,
0COUNTRY) or the structure (25-characters), how you want it
to appear on the axis.
AXIS Axis to which you want to move the characteristic /
AXIS_N structure
'X' = Columns The characteristic/structure is dragged to the axis. Its position
'Y' = Rows on the axis is determined by the parameter position.
' ' = Free characteristics
POSITION Position on an axis
POSITION_N The characteristic/structure is placed on the axis in the position
you specify here. If you do not specify a position, or if it is set
to 0, the characteristic/structure is placed at the end of the
drilldown sequence
Example:
Shift the key figure structure to the rows, and put calendar year and plan/actual structure in the columns:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='SET_NAV_STATE'ALL='X'
IOBJNM_1='DTG057U7OQ8K2ALKCMR2AWM14'AXIS_1='Y'IOBJNM_2='0CALYEAR'
POSITION_2='1'AXIS_2='X'IOBJNM_3='EFG057U7OQ8K2JKKCMR2AWM67'POSITION_3='2'
AXIS_3='X'>
Make sure that all the views have cost centers in their drilldown, and not materials:
<SAP_BW_URLDATA_PROVIDER='*'MULTI='X'CMD='SET_NAV_STATE'
IOBJNM_1='0COSTCENTER'AXIS_1='Y'IOBJNM_2='0MATERIAL'AXIS_2=''>
4.2.3.10 Sort
Use this command to sort according to the parameters of the characteristics, or by value.
CMD Sort
14.02.2001 Seite21
Sort_Type Type of sorting

'K' = key, 'T' = text, 'H' = hierarchy, 'S' = Characteristics can be sorted according to key, name, hierarchy
selection, 'V' = value (if there is an active display hierarchy) or by selection (if there
is a restriction to several single values or dynamically in the
query definition). You can also sort by value.
Sort_Direction Required sort direction
'A' = ascending, 'D' = descending The sort direction for Sort_Type=H is always 'A'.
IOBJNM Characteristic to be sorted
Only for sorting characteristics. This parameter is left out when sorting by value.
Structure_Member_1 Structure part of 1st structure
Only for sorting by value. If you sort by value, you must specify the exact value cell. You
must also specify the structure parts (25 characters) for all
structures that appear (maximum 2).
Structure_Member_2 Structure part of 2nd structure
Only for sorting by value. If you have defined 2 structures in the query, you must also
specify the structure part of the 2nd structure.
Examples:
Sort customers ascending, according to text in view 1:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='SORT'IOBJNM='0CUSTOMER'SORT_TYPE='T'
SORT_DIRECTION='A'>
Ascending list by "actual" "sales":
<SAP_BW_URLDATA_PROVIDER='View1'CMD='SORT'SORT_TYPE='V'SORT_DIRECTION='D'
STRUCTURE_MEMBER_1='DTG057U7OQ8K2ALKCMR2AWM14'
STRUCTURE_MEMBER_2='EFG057U7OQ8K2JKKCMR2AWM67'>
4.2.3.11 Calculate Lists

You can use this command to change the settings for list calculation for a value cell.
CMD SET_LIST_CALCULATION
Structure_Member_1 Structure part of 1st structure
You must determine the value cell precisely for list calculation.
You must also specify the structure parts (25 characters) for all
structures that appear (maximum 2).
Structure_Member_2 Structure part of 2nd structure
If you have defined 2 structures in the query, you must also
specify the structure part of the 2nd structure.
APPLY_TO_RESULTS (optional) Also apply calculation settings to result cells.
'X' = Yes, ' ' = No
CUMULATION (optional) Accumulated output
'X' = Yes, ' ' = No
VALUE_CALCULATION (optional) Calculations
'X' = Columns = No list calculation
'Y' = Rows R = Standardization of query result
G = Standardization of overall result
C = Standardization of result
S = Ranking list
O = Ranking list (olympic)
RESULT_CALCULATION (optional) Result cell calculations
00 = No list calculation
'01' = Summation
'02' = Maximum
'03' = Minimum
04 = Including all values
05 = Including all values <> 0
06 = Average of all values
07 = Average of all values <> 0
08 = Standard deviation
09 = Variant
10 = Suppress result
14.02.2001 Seite22
11 = First value
12 = Last value
Examples:
Display maximum plan turnover:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='SET_LIST_CALCULATION'
STRUCTURE_MEMBER_1='DTG057U7OQ8K2ALKCMR2AWM14'
STRUCTURE_MEMBER_2='EFG057U7OQ8K2JKKCMR2AWM67'VALUE_CALCULATION='02'>
4.2.3.12 Operations in Display Hierarchies

You have the option of 4 operations for display hierarchies:
With the command SET_HIERARCHY_STATE, you can activate or deactivate a display hierarchy that was assigned to
a characteristic (in the query definition or in the view, for example).
CMD Set_Hierarchy_State
IOBJNM Characteristic name
Characteristic that already has a display hierarchy assigned to
it.
ACTIVE (Option 1) Required status of the display hierarchy
'X' = activate, ' ' = deactivate
TOGGLE_STATE (Option 2) Switch the status of the hierarchy
'X' = switch over, ' ' = do not change If this attribute is set to 'X', the display hierarchy is activated if
it was not before and vice versa.
Example:
Activate hierarchies for the characteristic cost center for view 1:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Set_Hierarchy_State'
IOBJNM='0COSTCENTER'ACTIVE='X'>
With the command SET_HIERARCHY, you assign a display hierarchy to a characteristic.
CMD Set_Hierarchy
The characteristic to which you want to assign a display
hierarchy.
HIERARCHY_NAME Technical name of the hierarchy
HIERARCHY_VERSION Version of the hierarchy
If the required hierarchy has a version, you must specify the
version, otherwise, this parameter can be left out.
HIERARCHY_DATE Key date of the hierarchy
For time-dependent hierarchies, you can enter a key date here.
You must use the format, yearmonthday (for example,
20002412). If this parameter is not used, the system takes the
key date of the query.
ACTIVE Required status of the display hierarchy
Example:
Assign 'MyHierarchy' to the characteristic cost center for view 1:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Set_Hierarchy'IOBJNM='0COSTCENTER'
Hierarchie_Name='MyHierarchy'ACTIVE='X'>
With the command Drill_To_Level, you can drilldown on a display hierarchy, to the predefined hierarchy level.
CMD Drill_To_Level
Parameter Beschreibung
The characteristic that has an active display hierarchy assigned
to it.
14.02.2001 Seite23
LEVEL Level of the hierarchy

Level to which you want to drilldown on the hierarchy. Level 1
is the level of the root.
If a hierarchy node is filtered at the same time, you must make
sure that the level is higher than the filtered node.
Example:
Drilldown to level 3 on the hierarchy of the characteristic cost center for view 1:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Drill_To_Level'Iobjnm='0COSTCENTER'
Level='3'>
You can use the command Set_Drill_State to expand or collapse a node in a display hierarchy. When you do this, make
sure that the node is visible in the list in the current navigational view. The command is designed to influence the
expand level of the hierarchy when you call up a Web report, when you activate a hierarchy, or when you specify and
activate a hierarchy To carry out both functions at the same time, you need a command sequence.
CMD Set_Drill_State
The characteristic that has an active display hierarchy assigned
to it.
NODE_NAME Node name
Technical name of the node (internal display).
NODE_IOBJNM Name of the node characteristic
DRILL_STATE Required drill state
'E' = expanded, 'C' = collapsed
Examples:
Determine the hierarchy for the characteristic cost center for the view 1 and expand the node
"myNode","0HIER_NODE" at the same time:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Set_Hierarchy'IOBJNM='0COSTCENTER'
Hierarchie_Name='MyHierarchy'ACTIVE='X'
CMD_1='CMD=set_Drill_State&Data_Provider=View1&iobjnm=0COSTCENTER&Node_name=myNo
de&Node_iobjnm=0HIER_NODE&Drill_State=E'>
Determine the hierarchy for the characteristic cost center for the view 1 and expand the node
"myNode","0HIER_NODE" at the same time:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Drill_To_Level'Level='3'
CMD_1='CMD=set_Drill_State&Data_Provider=View1&iobjnm=0COSTCENTER&Node_name=myNo
de&Node_iobjnm=0HIER_NODE&Drill_State=E'>
4.2.3.13 Set Exception Status

By calling this command you can change the status for a view exception.
CMD Set_Exception_State
EXCEPTION_ID Technical name of the exception
Enter the technical name of the exception here (25-place
character string).
ACTIVE (Option 1) Required status of the exception
TOGGLE_STATE (Option 2) Switch the exception status
'X' = switch over, ' ' = do not change If this attribute is set to 'X', then the exception will be activated
if it was not previously active, and deactivated if it was
previously active.
Examples:
Set the exception Problems in Sales from view 1 to active:
14.02.2001 Seite24
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Set_Exception_State'
EXCEPTION_ID='DTG057U7OQ8K2ALKCMR2AWM14'ACTIVE='X'>
Switch exception Problems in Sales from view 1:

<SAP_BW_URLDATA_PROVIDER='View1'CMD='Set_Exception_State'
EXCEPTION_ID='DTG057U7OQ8K2ALKCMR2AWM14'TOGGLE_STATE='X'>
4.2.3.14 Set Condition Status

By calling this command you can change the status for a view condition.
CMD Set_Condition_State
CONDITION_ID Technical name of the condition
Enter the technical name of the condition here (25-place
character string).
ACTIVE (Option 1) Required status of the condition
TOGGLE_STATE (Option 2) Switch the status of the condition
'X' = switch over, ' ' = do not change If this attribute is set to 'X', the condition is activated if it was
not active previously, and vice versa.
Examples:
Set condition Top 10 Customers from view 1 to active:
<SAP_BW_URLDATA_PROVIDER='View1'CMD='Set_Condition_State'
EXCEPTION_ID='DTG057U7OQ8K2ALKCMR2AWM14'ACTIVE='X'>
Switch exception Top 10 Customers from view 1:

<SAP_BW_URLDATA_PROVIDER='View1'CMD='Set_Condition_State'
CONDITION_ID='DTG057U7OQ8K2ALKCMR2AWM14'TOGGLE_STATE='X'>
4.2.4 Alert Monitor

The Alert Monitor displays the results of the Reporting Agent background processing. The Exception Reporting results
are made available via the Alert Monitor.
Since the Alert Monitor only has one data source, you not need to create it as a separate data provider. The Item Alert
Monitor automatically creates its own suitable data provider and automatically passes on the filter operations to the
data provider.
Therefore, you do not have to manually create a data provider for the Alert Monitor.
See Item Alert Monitor for further information.
4.3 Item
Items are objects that obtain data from data providers and make it available in a particular way as HTML. Items have
attributes, for example, header, width and height, create navigation links and so on. You can subsequently change these
by setting parameters or calling commands. If you change the data, the navigational state or the attributes, the HTML is
recreated for the item. An item always has to be assigned to a data provider.
4.3.1 Generic Attributes

Generic attributes are attributes that are valid for all items.
ITEM ( or NAME ) Logical name for the item
You cannot change this attribute with a In addition to the ITEMID given when you create the item in
command URL. the Web Publisher, you also have to use a logical name if you
want to use the item for Web Reporting (pre-assigned with the
ITEMID). This makes it possible to use the same item more
than once in a template. If you send commands to this item,
always specify the name of the item as item parameter.
ITEMID Item key
14.02.2001 Seite25
You cannot change this attribute with a An item is created for a template on the basis of an item setting
command URL. made in the Web Publisher. The ViewID identifies an item
within a workbook By entering the WbID, you can use items
from various workbooks in a template.
WBID ( or ITEM_WBID ) (optional) Key for the Excel workbook under which the item is stored
You cannot change this attribute with a in the Web Publisher
command URL. The workbook must be stored in BW (favorites, activity groups
/ roles).
instead.
DATA_PROVIDER Logical name of the data provider for the item
Every item must be assigned to (exactly) one data source. From
this data source the item gets the data and Metadata it needs to
create output and commands
HIDDEN Hide item
'X' = Yes, ' ' = No If HIDDEN=X, then the item is not displayed, nor is the title
with the open/close symbol.
CLOSED Close item
'X' = Yes, ' ' = No In addition to the attribute HIDDEN, you can also close/open
items. If an item is closed, you can only see its title (if
available) and the open/close symbol.
GENERATE_CAPTION Display item header
'X' = Yes, ' ' = No Style SAPBEXTableCaption is used for the header.
CAPTION Header
If you do not specify a header, a suitable default value is used
instead (if Generate_Caption is equal to 'X').
GENERATE_LINKS Create filter and navigation URLs
'X' = Yes, ' ' = No If you do not want the user to be able to navigate or to see a
printable version, then set this attribute to ' ' = No
WIDTH Item width
Entry in pixels The specified width is used for graphics. The width for tables is
generated in the table tag (HTML) for the table. In the latter
case, the Web browser tries to retain the width. If the width is
set too narrow, the Web browser automatically increases the
width.
HEIGHT Item height
Entry in pixels Exactly this height is used for graphics. This attribute has no
function with HTML tables.
4.3.2 Items for Views

4.3.2.1 Table
The item table displays the values for a view in the form of a table. The same list geometry is supported as that which is
available in BEx. You can display characteristics and structures in rows or in columns.
As well as the generic attributes, the table has the following additional attributes:
ALT_STYLES Alternate row format (zebra list)
'X' = Yes, ' ' = No The 'SAPBEXstdData' format and the 'SAPBEXstdDataOdd'
format are used alternately for the rows to display numeric
values (no sum cells). You can adjust them in the CSS file
assigned to the template.
BLOCK_SIZE Number of rows per block
This parameter defines the amount of rows displayed before an
index for navigating to other blocks is begun. If the value is
0, the table is displayed in its entirety without taking the
number of rows into account.
14.02.2001 Seite26
4.3.2.2 Navigation Block

The item navigation block displays the navigational state for a view in the form of a table. All the characteristics and
structures for a view are listed in the table and their filter values are also displayed. You also have the option of
changing the navigational state. You can add or remove characteristics and structures from an axis (rows or columns).
You can filter according to single values or remove filters completely.
As well as the generic attributes, the navigational block has the following additional attributes:
TARGET_HELP_FRAME Frame in which Input Help is displayed
(optional) If you use HTML frame technology, then you have the option
of displaying Input Help in a different frame to the data. If you
have not maintained the parameter, then Input Help is output in
the same window as the data.
This parameter is not offered in the Web Publisher, and can
only be used for setting parameters in the template.
FILTER_VALUE_LENGTH Number of characters after which a filter value is indicated
(default value : 80) with :
If the value is set to 0, the filter value is displayed in its
complete form.
HORIZONTAL_ALIGNMENT Horizontal display of the navigation block
'X' = Yes, ' ' = No As well arranging the characteristics one below the other, you
can also display them side by side. In many cases, this makes
better use of the interface and commands a stronger visual link
between table and navigation block.
HORIZONTAL_NUMBER Maximum number of characteristics that can be placed side
by side
You can only use this specification when
HORIZONTAL_ALIGNMENT = X.
If the navigation block contains more than the given number of
characteristics, it is automatically displayed with several rows.
The number of characteristic per row is increased according to
the equal distribution of rows and the required number.
ITEM_NAV_BLOCK_IOBJNM_N (optional) Listing the entries in the navigation block
By listing the characteristic and structure names, you can see
which entries appear in the navigation block and in which
order.
If you do not specify a parameter here, all characteristics and
structures are displayed.
BOOKED_VALUES Use booked values as Input Help
If you do not specify this parameter, or if it is set to 'X', the
Input Help shows only values that are also booked in the
InfoCube within the current valid filter conditions. Under
certain circumstances, this can take a long time. If the
parameter is set to ' ', all the values of the dimension table are
displayed. This may be quicker, but it means that those values
that do not meet the current filter conditions in the InfoCube
are also shown. And they give the result "No relevant data
found" when you filter.
4.3.2.3 Filter
The Item filter displays the filter values created by navigation for a view.
As well as the generic attributes, the filter has the following additional attributes:
ONLY_VALUES Display values only
'X' = Yes, ' ' = No The filter values are separated with a semicolon, without
description or formatting.
FILTER_VALUE_LENGTH Number of characters after which a filter value is indicated
(default value : 0) with :
14.02.2001 Seite27
If the value is set to 0, the filter value is displayed in its

complete form.
FILTER_NODE_IOBJNM_N (optional) Listing characteristic and structures
By listing the characteristic and structure names, you can see
which entries appear in the filter and in which order. Only those
entries are displayed that have a filter value, the other entries
are ignored.
(optional) Filter value display
PRESENTATION_N (optional) The filter value is displayed according to the setting. If you do
KEY not specify a display for an index, the display of Index 0 (no
TEXT index) is used.
'KEY_TEXT' If you do not use this parameter, the display used is that valid
'TEXT_KEY' for the characteristic.
With the combination of ONLY_VALUES=X and ITEM_FILTER_IOBJNM=MyInfoObject, you can address a specific
filter value in the template. You can also use this in titles, for example.
Examples:
Display the filter values for the characteristic calendar year, without formatting:
<object>
<paramname='ITEM'value='Filter'>
<paramname='ITEMID'value='Filter'>
<paramname='ONLY_VALUES'value='X'>
<paramname='ITEM_FILTER_IOBJNM'value='0CALYEAR'>
ITEM:Filter
</object>
Entry field for filtering by calendar year the dynamic filter preset (only applies for single value filters):
<form action="<SAP_BW_URL DATA_PROVIDER='View 1' FILTER_IOBJNM='0CALYEAR'>" method="post">
Calendar year: <input name="FILTER_VALUE_EXT" size=4 maxlength=4 value="
<object>
<paramname='ITEM'value='Filter'>
<paramname='ITEMID'value='Filter'>
<paramname='ONLY_VALUES'value='X'>
<paramname='ITEM_FILTER_IOBJNM'value='0CALYEAR'>
<paramname='PRESENTATION'value='KEY'>
ITEM:Filter
</object>">
<input type=submit value="Submit">
<input type=reset value="Reset">
</form>
4.3.2.4 Text Element

The item text element presents the text elements for a view. You can address the same text elements that appear in the
Business Explorer Analyzer.
As well as the generic attributes, the text elements have the following additional attributes:
ONLY_VALUES Display values only
'X' = Yes, ' ' = No The text element values are separated with a semicolon,
without description or formatting.
SHOW_COMMON_ELEMENTS Display general text elements (validity of data, InfoCube,
14.02.2001 Seite28
'X' = Yes, ' ' = No current users)

SHOW_VARIABLES Display variable values
'X' = Yes, ' ' = No
SHOW_FILTERS Display filter values that were defined in the filter area of
'X' = Yes, ' ' = No the query definition
ELEMENT_NAME_N Listing text elements
By listing text elements in combination with their type
ELEMENT_TYPE_N, you can determine which entries appear
as text elements and in which order.
With general text elements, the name corresponds to one of the
values below; with variables, it corresponds to the variable
name and with filters it corresponds to the characteristic name.
ELEMENT_TYPE_N Listing types of text elements
COMMON = general text element See ELEMENT_NAME_N
FILTER = static filter value
VARIABLE = variable value
The combination of ONLY_VALUES=X, ELEMENT_TYPE =COMMON and ELEMENT_NAME=REPTXTLG, you
can address a specific text element in the template, for example, query name. You can also use this in titles, for
example.
General text elements:
REPTNAME Technical name of the query
REPTXTLG Description of the query
INFOCUBE = InfoCube
SRDATE Key date of the query
ROLLUPTIME validity of the data (date and time
AUTHOR Author of the query
MODTIME = Last changed on (date and time)
MODUSER = Last changed by
SYUSER = Current user
SYUZEIT = Last refresh (date and time)
4.3.2.5 Chart
The item table displays the values for a view in the form of a graphic.
As well as the generic attributes, the chart has the following additional attributes:
SWITCHMATRIX Inverting data
'X' = Yes, ' ' = No Depending on the list geometry of the view, it is useful to swap
the row roles and the columns in the diagram. By setting this
attribute, you can swap the roles without affecting the
navigational state of the view itself.
SUPPRESS_OPENHIERARCHIENODES Hide open hierarchy node
'X' = Yes, ' ' = No If the hierarchy display is switched on, you can remove the
expanded node from the graphic. This ensures that the total of
all the displayed values is the overall total.
4.3.2.6 Exception Block

The item exception block displays the exception status of a view in the form of a table. All the exceptions are listed in
the table along with their status (active / not active). You also have the option of switching the exception status.
This item only has the generic attributes.
4.3.2.7 Condition Block
The item condition block displays the condition status for a view in the form of a table. All the conditions are listed that
can be applied in the current navigational state of the view. For every condition the status is displayed extra (active, not
used, not active). You also have the option of switching the condition status
4.3.2.8. Selection List
14.02.2001 Seite29
The item selection list puts characteristic values in the Web report for filtering in a selection list. If a value is selected,
the view is filtered according to this value. If a filter value has been selected for the characteristic in the selection list in
another way, the current filter value is put into the selection list.
The item selection list has the following attributes in addition to the generic attributes:
IOBJNM Name of characteristic / structure according to which you
want to filter
SHOW_LABEL BW Use description as heading
'X' = Yes, ' ' = No
If this attribute is activated, the characteristic descrption is used
as the heading of the selection list.
MAXVALUES (optional) Maximum number of values in selection list
Contains the maximum number of values that should be
displayed in the selection list.
If this attribute has the value 0, all values are displayed in the
selection list.
ONLY_VALUES (optional) Only create selection list
'X' = Yes, ' ' = No
If this attribute is activated, only the HTML formular
element is created for the value list. The form that
contains the selection list must in this case be created by
hand.
This attribute is designed for structuring forms which
contain more than one selection list.
(optional) Index in filter command
Must have a unique value for all selection lists and
selection button groups within the form tag.
You only need to use this attribute if the attribute
ONLY_VALUES is activated.
4.3.2.9 Selection Button Group

The item selection button group puts characteristic values for filtering in a group of selection buttons. If a value is
selected, the view is filtered according to this value. If a filter value is selected for the charcteristic of the selection
button group in another way, the current filter value is marked as selected.
The item selection button group has the following attributes in addition to the generic attributes:
IOBJNM Name of characteristic / structure according to which you
want to filter
SHOW_LABEL BW Use description as heading
'X' = Yes, ' ' = No
If this attribute is activated, the characteristic description is
used as the heading of the selection list.
MAXVALUES (optional) Maximum number of values in selection list
Contains the maximum number of values that should be
displayed in the selection list.
If this attribute has the value 0, all values are displayed in the
selection list.
ONLY_VALUES (optional) Only create selection button group
'X' = Yes, ' ' = No
If this attribute is activated, only the HTML formular
element is created for the selection button group. The
form that contains the selection button group must in this
14.02.2001 Seite30
case be created by hand.

This attribute is designed for structuring forms which
contain more than one selection button group.
(optional) Index in filter command
Must have a unique value for all selection lists and
selection button groups within the form tag.
You only need to use this attribute if the attribute
ONLY_VALUES is activated.
HORIZONTAL_ALIGNMENT Entries on top of each other
'X' = Yes, ' ' = No If this attribute is activated, the various characteristic values are
displayed vertically. If this attribute is deactivated, the various
characteristic values are displayed horizontally.
HORIZONTAL_NUMBER Number of entries next to / on top of each other
Contains the number of entries that may be displayed, vertically
or horizontally as defined by the setting of the attribute
HORIZONTAL ALIGNMENT. You can specify the required
number of entries by double-clicking on the attribute or via
Change Attribute.
4.3.2.8 Label
The item label allows you to display descriptions of parts of characteristics, attributes or structres, and to place a link
from the context menu of the characteristic.
This item can be used with the items selection list and selection button group to make a comfortable Cockpit.
The item label has the following attributes in addition to the generic attributes:
ATTRINM Attribute name
Technical name of the attribute whose heading should be
displayed as a label.
STRUCTURE_MEMBER Structure part
Structure part whose text or context menu is displayed.
CONTEXT_MENU Context menu
'X' = Yes, ' ' = No If you activate this attribute, a link is created in the description
of the characteristic to the context menu of the characteristic.
ONLY_VALUES Unformatted display
'X' = Yes, ' ' = No Display description without formatting.
4.3.3 Item Alert Monitor

The Alert Monitor presents the views, which were retrieved with the help of the Reporting Agent in a background
process, as a list or hierarchy and supports jumps to these views. Furthermore, it is possible to set filters.
FILTER_RED Only display rows with at least one red / yellow / green
FILTER_YELLOW light.
FILTER_GREEN For example, if you choose only FILTER_RED=X and
'X' = Yes, ' ' = No FILTER_YELLOW=X, you do not see any rows that are green.
FILTER_INFOAREA Filter according to entries that are below a certain InfoArea
If the attribute is empy, no filter is used.
FILTER_INFOCUBE Filter according to entries that are below a certain
InfoCube
FILTER_QUERY Filter according to entries that are below a certain query
14.02.2001 Seite31
HIERARCHY Hierarchical display

'X' = Yes, ' ' = No The hierarchical display copies the InfoArea, InfoCube and
query to build a hierarchy that you see when you open a query
for example. Alternatively, you can choose a flat list. This
displays only the navigation statuses, without the InfoArea,
InfoCube and queries. This display variant is especially suited
to a small amount of entries.
DISPLAY_MAX_LEVEL Only display the highest level
'X' = Yes, ' ' = No Instead of displaying the red, yellow and green lights with their
frequency per navigation status, you can also only display the
light with the highest alert level. This makes the display more
compact.
BLOCK_SIZE Number of rows before turning the page
(default value : 10 Since the Alert Monitor potentially has a large number of
entries, you can specify a maximum number of entries to be
displayed. This can be used for layout especially. If more rows
exist, an index is added to go to a different page.
If the value is set to 0, all entries are displayed.
JUMP_WBID (optional) Excel workbook key under which the template is stored in
the BEx
You need this attribute if you want to display the detail view of
a navigation status from the Alert Monitor in a different
template as the default template The alternative template is
characterized by JUMP_WBID and JUMP_PAGEID.
JUMP_WBID : The workbook must be stored in BW
(favorites, activity groups / roles).
JUMP_PAGEID (optional) Name of the template (see JUMP_WBID)
TARGET_FRAME (optional) Name of the frame for the detail view

If this is not specified, the detail view is displayed in the same
window if you are using pure HTML . With Java Script
switched on, a separate window is opened.
14.02.2001 Seite32
5 Parameterizing Templates
The URL for calling a template is generated by the Web Publisher. You can make a copy and use it again and again.
A typical URL looks like this:
The first part of the URL, (http://your_its/scripts/wgate/WebRFC/!?_function=WEBQUERY) calls
the WebRFC Service for BW Web Reporting from the ITS. The template is called next. This takes place using the
'LDOC' command with the parameters 'WBID ' and 'PAGEID '.
The command LDOC requests a new HTML page and creates it according to the template.
By inserting other parameters, you can parameterize the template. These parameters are passed on to all data providers
and items. By parameterizing the URL you can therefore filter all views according to a particular country or cost center,
for example.
Examples:
Filter all views according to Germany:
FILTER_IOBJNM=0COUNTRY&FILTER_VALUE=DE
Filter all views according to Germany, 2000:

FILTER_IOBJNM_1=0COUNTRY&FILTER_VALUE_1=DE&FILTER_IOBJNM_2=0CALYEAR&FILTER_VALUE
_2=2000
Display all items with title:

GENERATE_CAPTION=X
14.02.2001 Seite33
6 Command Sequences
There are many factors involved in the need to change several objects in various ways under one command. Until now it
was not possible to filter a data_provider according to the fiscal year 1999 and another data_provider according to 2000
under one request (command).
Command sequences make it possible to add other commands to a command. Only after all commands have been
executed is the data requested from the OLAP processor and the HTML page sent back to the Web browser.
The sequence commands are added to commands as parameter CMD_N. Please note that the characters '=' and '&' must
be replaced in the sequence demand by their Hex display:
=' is replaced by '%3D' and '&' becomes '%26'.
Every sequence command can be up to 250 characters long. If there are other characters, they are omitted.
If the command sequence is too large to fit in a URL then you can add the attribute NO_OUTPUT' to a command. As a
result, the command is executed and a blank page is sent back. No data is read at this point. This is useful if you want to
go to a main frame from a control frame, for example. With JavaScript you can lead a sequence of individual commands
in the main frame and only leave out the NO_OUTPUT' attribute when you get to the last command.
Examples:
Start page and filter DP1 according to DE and DP2 according to US:
CMD_1=DATA_PROVIDER%3DDP1%26FILTER_IOBJNM%3D0COUNTRY%26FILTER_VALUE
%3DDE&CMD_2=DATA_PROVIDER%3DDP2%26FILTER_IOBJNM%3D0COUNTRY%26FILTER_VALUE%3DUS
Command URL to filter DP1 according to calendar year 2000, change title of graphic GRAPHIC to '2000' and change
the title of table TABLE to Details 2000'.
<SAP_BW_URL DATA_PROVIDER='DP1' FILTER_IOBJNM='0CALYEAR' FILTER_VALUE='2000'
CMD_1='ITEM=GRAPHIC&CAPTION=2000' CMD_2='ITEM=TABLE&CAPTION=Details2000'>
14.02.2001 Seite34
7 Forms
With HTML forms you can integrate entry fields into an HTML page easily. It is possible to use this HTML technology
in BW Web Reporting.
7.1.1 Parameterizing Templates

You can set parameters for calling Web Reporting pages that meet end user requirements by implementing forms. To do
this, create an HTML document with a form from which the actual URL for Web Reporting is called with set
parameters.
Example:
After calling the subsequent HTML document, the user is presented with a form in which s/he can select a calendar year
and a country from the dropdown boxes. By executing the submit command, a Web Reporting page is displayed with
view filters already set.
<html>
<body>
<table>
<formmethod="POST"action="http://your_its/scripts/wgate/WebRFC/!?
_function=WEBQUERY&CMD=LDOC&WBID=D9EW857MLP6EN0AEM9BZSQP3C&PAGEID=Template_Name&FILTER_IO
BJNM_1=0CALYEAR&FILTER_IOBJNM_2=0COUNTRY">
<tr>
<td>Kalenderjahr</td>
<td><selectsize="1"name="FILTER_VALUE_1">
<optionvalue="1997">1997</option>
</select></td>
</tr>
<tr>
<td>Land</td>
<td><selectname="FILTER_VALUE_2">
<optionvalue="BR">Brazil</option>
<optionvalue="DE">Germany</option>
<optionvalue="FR">France</option>
<optionvalue="GB">GreatBritain</option>
<optionvalue="JP">Japan</option>
<optionvalue="RU">Russia</option>
<optionvalue="ES">Spain</option>
<optionvalue="US">USA</option>
</select></td>
</tr>
</table>
<inputtype="submit"value="Submit"name="Submit">
</form>
</body>
</html>
Buttons and Forms in Templates

You can integrate commands into a template by using anchors (<a href= ... ></a>) and HTML forms. These
commands can affect one or several items or data providers.
You can use the bookmarks described under Command URLs in the place where you would usually see URLs in
HTML appear. They are replaced automatically during processing so that only valid URLs appear in the created HTML
page.
Examples:
14.02.2001 Seite35
Drilldown view 1 according to country and filter according to calendar year 2000:
<ahref="<SAP_BW_URLDATA_PROVIDER='View1'CMD='Expand'IOBJNM='0COUNTRY'
FILTER_IOBJNM='0CALYEAR'FILTER_VALUE='2000'>">Jahr2000+AufrinachLand</a>
Forms where a user can select a calendar year and a country from dropdown boxes:
<formmethod="POST"action="<SAP_BW_URLDATA_PROVIDER='*'MULTI='X'
FILTER_IOBJNM_1='0CALYEAR'FILTER_IOBJNM_2='0COUNTRY'>">
<table>
<tr>
<td>Kalenderjahr</td>
<td><selectsize="1"name="FILTER_VALUE_1">
</select></td>
</tr>
<tr>
<td>Land</td>
<td><selectname="FILTER_VALUE_2">
<optionvalue="BR">Brazil</option>
<optionvalue="DE">Germany</option>
<optionvalue="FR">France</option>
<optionvalue="GB">GreatBritain</option>
<optionvalue="JP">Japan</option>
<optionvalue="RU">Russia</option>
<optionvalue="ES">Spain</option>
<optionvalue="US">USA</option>
</select></td>
</tr>
<table>
<inputtype="submit"value="Submit"name="Submit">
</form>
Buttons that filter view 1 according to calendar year:
<formmethod="POST"action="<SAP_BW_URLDATA_PROVIDER='View1'
FILTER_IOBJNM='0CALYEAR'>">
<inputtype="submit"value="1998"name="FILTER_VALUE">
</form>
14.02.2001 Seite36

776 Sap BW Web Reporting User Guide

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

776 Sap BW Web Reporting User Guide

Загружено:

Авторское право:

Доступные форматы

SAP BW

14. February 2001

(Valid as of BW 2.0B Server Patch 13)

SAP AG assumes no responsibility for errors or omissions in these materials.

3.2 Object Tags................................................................................................................................................ 7

3.3 Command URLs........................................................................................................................................ 9

3.4 Language-Dependent Texts...................................................................................................................... 9

4.2 Data Providers......................................................................................................................................... 15

4.2.3.7 Exchange Characteristics/Structures................................................................................................. 20

Item Text Element

Item Nav Block

3.2 Object Tags

3.2.1 Structure of the Data Provider Object Tag

3.2.2 Structure of the Item Object Tag

3.3 Command URLs

3.4 Language-Dependent Texts

4.1.1 Calling up Templates

STATELESS (optional) Reduce the link to the server as soon as possible

MELT_VARIABLES (optional) Melt Variables

VARIABLES_CLEAR (optional) Reset Variables

SUPPRESS_WARNINGS (optional) Suppress Warnings

DATA_MODE (optional) Data mode

4.1.1.2 Call up template with another data provider

VARIANT (optional) Variant, if you need to enter a variable

Call-up for presenting a different view:

4.1.1.3 Using default template for a data provider

4.1.2 Exchanging Templates

4.1.3 Change Icon List

4.1.4 Release Page

4.1.5 Call up Variable Screen

4.1.6 Exit Session

4.1.7 Entering Variables

4.1.7.2 Hierarchy node variables:

4.1.7.3 Hierarchies, formulas and text variables

Hierarchy node variable (DE, 0HIER_NODE):

4.1.8 Change variable values

4.2 Data Providers

4.2.1 Generic Attributes

(optional) stored in the BEx

Apply command to 'DP 1' and 'DP 2':

Apply command to all data providers containing 'USA' in the name:

If this parameter is not specified, the template WBID is used

The following commands can be applied for a view.

'E' found values remove.

The following additional parameters are specified for filtering intervals:

FILTER_VALUE_HIGH Filter value upper limit (not compounded)

FILTER_NODE_IOBJNM_(optional) Name of the node characteristic

4.2.3.3 Remove Filter

4.2.3.4 Call up Input Help

IOBJNM Name of characteristic / structure

Move periods 1, 2 and 3 (2000) from view 1 to the columns:

4.2.3.6 Remove Drilldown

4.2.3.7 Exchange Characteristics/Structures

4.2.3.8 Switching Axes

4.2.3.9 Set Navigational Status

IOBJNM Name of characteristic / structure

Sort_Type Type of sorting

4.2.3.11 Calculate Lists

4.2.3.12 Operations in Display Hierarchies

With the command SET_HIERARCHY, you assign a display hierarchy to a characteristic.

LEVEL Level of the hierarchy

4.2.3.13 Set Exception Status

Switch exception Problems in Sales from view 1: