Info-Object
An InfoObject is a generic
term for characteristics and key figures in the Business Information Warehouse.
InfoObjects are used in data targets and in the three structures that are
relevant for data requests; extract, transfer, and communication structures.
Hierarchies
Hierarchies are tree-like
structure of characteristic values for a particular characteristic. Characteristic
hierarchies are stored in their own data tables. They act like master data and
can therefore be used in all InfoProviders.
Example: Hierarchy using
cost centres that are assembled in cost centre groups.
Infocube
InfoCubes are InfoProviders
but are not necessarily data targets (InfoCubes are also data targets only if
data is physically stored in them).
From a reporting point of
view, an InfoCube describes a self-contained dataset, for example, of a
business-orientated area. This dataset can be evaluated in a BEx query.
An InfoCube is a quantity
of relational tables arranged according to the star schema: A large fact table
in the middle surrounded by several dimension tables.
InfoCubes are made up of a
number of InfoObjects. All InfoObjects (characteristics and key figures) are
available InfoCube-independently. Characteristics relate to master data with
their attributes and text descriptions.
An InfoCube consists of
several InfoObjects and is structured according to the star schema. This means
there is a (large) fact table that contains the key figures for the InfoCube as
well as several (smaller) dimension tables which surround it. The
characteristics of the InfoCube are stored in these dimensions.
An InfoCube fact table only
contains key figures, in contrast to an ODS object, whose data part can also
contain characteristics. The characteristics of an InfoCube are stored in its
dimensions.
Data Store Objects (DSO)
A DSO object acts as a
storage location for consolidated and cleaned-up transaction data (transaction
data or master data, for example) on the document (atomic) level.
It describes a consolidated
dataset from one or more InfoSources. This dataset can be evaluated using a BEx
query.
Info-source
An InfoSource is a quantity
of information that logically belongs together, summarized into a single unit.
InfoSources contain either transaction data or master data (attributes texts
and hierarchies).
An InfoSource is always a
quantity of InfoObjects that logically belong together. The structure in which
these are stored is called a communication structure.
ABAP Routines
ABAP routines may be
created to manipulate & QA data for transformation and Update.
Info-packages
This describes which data
in a DataSource should be requested from a source system. The data can be
precisely selected using selection parameters (for example, only controlling
area 001 in period 10.1997).
An InfoPackage can request
the following types of data:
·
Transaction data
·
Attributes for master data
·
Hierarchies for master data
·
Master data texts
Info-package Group
In order to summarize data
requests which logically belong together from a business point of view, and to
therefore simplify the request, you can collect data requests (meaning the InfoPackages)
into an InfoPackage Group. You can schedule each of these groups in the
scheduler. With the data request the scheduler can access InfoPackage groups
directly and thereby request more than one InfoPackage at a time, corresponding
to the setting in the InfoPackage group. Thus, you can support InfoPackage
groups with the serialization of your data requests.
Collection of a selection
of characteristics and key figures (InfoObjects) for the analysis of the data of
an InfoProvider. A query always refers exactly to one InfoProvider, whereas you
can define as many queries as you like for each InfoProvider.
You define a query in the
Bex Query Designer, in which you select InfoObjects or reusable structures for
an InfoProvider and specify the view of the data (query view) by distributing
them to filters, rows, columns, and free characteristics. You used this saved
query view as a basis for data analysis and reporting in the Bex Analyzer, in
Bex Web applications, in Bex Mobile Intelligence, or in formatted reporting
Bex Query Variant
A query variant is a query
for which the variable values have already been selected. The variants may be
used for both opening the query in the online display and for background
processing.
Restricted Key Figures (InfoProvider Level)
A restricted key figure is a key figure that
is restricted to certain characteristic values. It is defined in the query and
limits the selected data to the values or range of values selected.
Calculated Key Figures (InfoProvider Level)
A calculated key figure is
a key figure that is calculated of one or more other key figures. Standard,
custom, restricted key figures and other calculated key figures can be used for
the calculation.
Variables are parameters of
a query that you defined in the Query Designer and that are filled with values
when you execute the query or Web application. They serve as a store for
characteristic values, hierarchies, hierarchy nodes, texts and formula
elements, and can be processed in different ways.
Currency Translation Types
contain a combination of different parameters that establish how the exchange
rate for the translation is executed. A translation type can be determined
independently from source and target currencies.
Authorization objects enable you to define
complex authorizations by grouping up to 10 authorization fields in an AND
relationship to check whether a user is allowed to perform a certain action. To
pass an authorization test for an object, the user must satisfy the
authorization check for each field in the object.
An authorization is the empowerment to carry
out a certain activity in the Business Information Warehouse. Each
authorization refers to an authorization object and defines one or more values
for each field that is contained in the authorization object. Individual
authorizations are summarized into authorization profiles by system
administration. You can copy the roles delivered by SAP and adjust them when
you want. The system administrator creates these authorizations and enters them
into individual users’ master records in the form of profiles.
There are two object classes in the Business
Information Warehouse:
·
Business Information Warehouse – Reporting
No authorization objects are delivered in
this object class. You create user authorization objects for reporting as and
when you require them.
·
Business Information Warehouse
Roles are collections of activities which
allow a user to use one or more business scenarios of an organization.
You can create workbook templates, into which
you can insert your queries. Workbook templates contain the following elements:
·
Preset positions for the different areas (title, filter cells, results
area, text element).
·
Format settings: You can change the background pattern, color scheme,
and so on.
·
Logo, Bitmaps.
·
VBA macros.
Workbooks
Queries are inserted into
workbooks so you can display them. When you insert a query, a link is made
between the cell areas of the worksheet and the data of the Info Provider upon
which the query is based. A link therefore exists between the Business Explorer
and the Business Information Warehouse Server (BW Server). This link stays in
place until you interrupt it.
When you open a query and
insert it into a workbook, the query is calculated and the view (initial view)
of the data established in the Query Designer is displayed.
A Web template determines
the structure of a Web application. You use the Web Application Designer to
insert placeholders into a HTML document for Web items (in the form of object
tags), data providers (in the form of object tags) and BW URLs. The HTML
document with the BW-specific placeholders is called a Web template. Web
templates are checked into the Web Application Designer. The HTML page that is
displayed in the Internet browser is called a Web application. Depending on
which Web items you have inserted into the Web template, a Web application
contains one or more tables, an alert monitor, charts, maps, and so on.
Web Reports
Web reporting enables the
publishing of queries defined in the Business Explorer Analyzer to the Intranet
or Internet. It is possible to insert and display queries in any HTML page.
Multiple queries may be embedded into one HTML page, and graphics used to
display the data (cockpit). Navigation functions are available to report on the
data contained in a Web query (drilldown, refresh, and so on).
Name for a particular type
of Info-Provider: An Info-Set describes data sources that are usually defined
as joins for OD objects or Info-Objects (characteristics with master data). A
time-dependent join or temporal join is a join that contains an Info-Object
that is a time-dependent characteristic.
An Info-Set is a semantic
layer over the data sources and is not itself a data target.
Unlike the classic
Info-Set, an InfoSet is a BW-specific view of data.
A Classic InfoSet gives you
a view of a dataset that you report on using the InfoSet Query. The Classic
InfoSet determines which tables or fields within a table an InfoSet Query
refers to.
Since Release 2.0B,
InfoSets have been used in the Business Information Warehouse for InfoObjects
(master data), ODS objects, and joins for these objects. These InfoSets are
Basis Objects, not BW Repository Objects. The InfoSet Query can be used to
carry out tabular (flat) Reporting on these InfoSets.
InfoSet User Groups
InfoSet User Groups are
used to control who may access InfoSet Queries. Users may not be allowed to
modify queries from other user groups, although they may, under certain
circumstances, copy and execute them (see Copying Queries).
Within a user group, it is
irrelevant who has defined a certain query, since anyone who belonging to that
group can execute it. However, only users with the appropriate authorization
can change queries or define new ones.
Each user can be assigned
to several user groups.
