BW 名词解释

来源：好走旅游网

BW GLOSSARY

Last Changed:

Administrator Workbench

Tool for controlling, monitoring and maintaining all those processes involved in data procurement and processing within the Business Information Warehouse.

after-import method

Method that is used in connection with the transport of an object into a different system. The after import method is called in the target system after the object has been imported. The after import method is object specific and, therefore, you have to rewrite it for every object type.

You might typically use the after import method to activate the imported object, in order to integrate it in a new context in the target system.

aggregate

An aggregate stores the dataset of an InfoCube redundantly in a summarized form. In this instance, summarization means condensing the original fact table of an InfoCube for an aggregate table. This table no longer contains certain characteristics of the InfoCube that has been summarized using attributes, or characteristic values, or a hierarchy level.

The summarization enables you to access the data of an InfoCube quickly when reporting. Therefore, aggregates are tools for enhancing performance.

Aggregates are created from logical data packages (requests). You can distinguish between the processes of filling and rolling up here:

• The first time that data is loaded in an active aggregate is described as filling. After filling, the aggregate is used in reporting.

• Rolling up is understood as loading data packages from the fact table of an InfoCube in all of the aggregates for this InfoCube.

aggregation level

Selection of characteristics and navigation attributes of an InfoCube, from which aggregates are constructed.

You have the following aggregation options:

• All characteristic values (“*”): Data is grouped by all values of the characteristic or the navigation attribute.

• Hierarchy level (“H”): Data is grouped by hierarchy level nodes.

• Fixed value (“F”): Data is filtered according to a single value.

alert monitor

Monitoring tool used for displaying exceptions, whose upper or lower threshold value has been exceeded. The exceptions concerned are found in background processing using the reporting agent and are displayed in the alert monitor as a follow-up action. Exceptions are displayed not only in the BEx Analyzer, but also in the reporting agent scheduler of the Administrator Workbench. Moreover, exceptions can also be displayed as an alert monitor in a Web application.

Meaning of the alert monitor in the BEx Web Application:

Web item that displays the query views, which were found in background processing using the reporting agent, as a list or hierarchy in a Web application. You can jump between query views and see conspicuous key figure values that deviate from the defined threshold values at a glance. You can also set filters.

and-process

Combined process of the process chain maintenance.

When you use an and-process in the process chain maintenance, the application process is started only when all events in the previous process, on which this process is waiting, have been triggered.

application process

A process that is automated in the process chain maintenance. For example, data loading process or attribute change run.

attribute

InfoObjects that are assigned or subordinated to a logical characteristic and which cannot be selected in the query.

Example: To a given cost center, you could assign the attribute:

• \"Cost center manager\" (the attribute here is a characteristic), or

• \"Size of cost center in square meters\" (the attribute here is a key figure)

axis data set

Combination of different values on an axis.

Data sets for elements (members) of an axis dimension are used when defining MDX queries.

BasicCube

Data container, on which reports and analyses are based. A BasicCube contains two types of data: key figures and characteristics. A BasicCube is a collection of related tables that are put together according to the star schema. The star schema is a large

fact table in the center with several surrounding dimension tables. The fact table is there to store all the key figures with the minimum of detail, whereas the dimension table stores the characteristics that are needed for reporting on and evaluating these key figures.

Dimension tables are considered independently of each other. Only the fact table links the dimension tables to the key figures. All data is consequently stored multi-dimensionally in the BasicCubes.

BEx Map

The Business Explorer’s geographical information system (GIS). The BEx Map allows you to display data with a geographical connection (characteristics such as customer, sales region, and country) together with key figures relevant for business management on a map. You can then use this map to evaluate the data.

BEx Mobile Intelligence

Use of Web applications for mobile devices that have an online connection to a BW system. Synonyms: Business Explorer Mobile Intelligence, Mobile Intelligence

BEx Query Designer

Tool for defining queries that are based on a selection of characteristics and key figures (InfoObjects) or on reusable InfoProvider structures. In the BEx Query Designer, you can parameterize queries by defining variables for characteristic

values, hierarchies, hierarchy nodes, texts or formulas. You can specify the selection of InfoObjects more precisely by:

• Restricting characteristics and key figures by characteristic values, characteristic value intervals and hierarchy nodes

• Defining calculated and restricted key figures for reuse

• Defining structures for reuse

• Defining exceptions

• Defining conditions

• Defining exception cells

You can use all queries that you define in the BEx Query Designer for OLAP reporting, and for flat reporting.

BEx Web Application

Web-based application of Business Explorer for data analysis, reporting, and analytical applications on the Web. You can format and display your data differently in the BEx Web Application Designer with a series of Web items (for example, tables, filters, charts, maps, and documents). In this way you can individually set Web applications like BI Cockpits and access them by using the intranet or by using an

enterprise portal.

BEx Web Application Designer

Desktop application for creating Websites with BW contents. With the BEx Web Application Designer you can create an HTML page that contains BW-specific contents, such as different tables, charts, or maps. This HTML page serves as the basis for Web applications with complex interactions like BI Cockpits. You can save the Web applications as a URL and access them by using the intranet or by using mobile terminals. Additionally, you can save the Web applications as an iView and integrate them into an enterprise portal.

Synonyms: Business Explorer Web Application Designer, Web Application Designer

BEx Web Application Wizard

Assistant that supports the creation of Websites with BW-specific contents. This enables a simplified design process by means of an automatic step-by-step sequence. The Web Application Wizard is integrated in the Web Application Designer.

Synonyms: Business Explorer Web Application Wizard, Web Application Wizard

Business Explorer

Abbreviation: BEx

The analytical and reporting tool in the Business Information Warehouse. The Business Explorer (BEx) covers the following areas:

• Query design and application design: BEx Query Designer and BEx Application Designer

• Analysis and reporting: BEx Analyzer, BEx Web Applications, and Mobile Intelligence

• Formatted reporting: Crystal Reports Integration

• Organization: BEx Browser

Business Explorer Analyzer

Abbreviation: BEx Analyzer

Analytical and reporting tool in the Business Explorer that is embedded in Microsoft Excel. In the Business Explorer Analyzer, you can analyze selected InfoProvider data by navigation to queries created in the BEx Query Designer and can create different query views for the data.

Business Explorer Browser

Abbreviation: BEx Browser

Tool for organizing and managing workbooks and documents. Using the Business Explorer Browser (BEx Browser), you can access all documents in the Business Information Warehouse that are assigned to your role and that you have stored in you favorites. You can work with the following document types in the Business Explorer Browser:

• BW workbooks

• Documents that are stored in the Business Document Service (BDS)

• Links (references to the file system, short cuts)

• Links to Internet pages (URLs)

• SAP transaction calls

• Web applications and Web templates

• Crystal Reports

business intelligence cockpit

abbreviation: BI cockpit

synonyms: Web cockpit, information cockpit

Web-based \"control panel\" with Business Intelligence contents. Just like a cockpit in an aeroplane, it gives the management of a company an overview of all the relevant business data.

You use the Business Explorer Web Application Designer to generate individual BI cockpits that display data in tables, charts, or on maps. The alert monitor that is integrated into the BI cockpit tells you immediately if any critical data falls outside of the specified range of acceptable values. You also have the option of adding additional information to the business data in the form of documents, graphics, or hyperlinks.

BI cockpits have the following functions:

• You can collect data from different data sources and display it in various ways (as a table, a chart, and so on)

• You can use structured (BI contents) and unstructured (documents, and so on) information to enhance each other

• Personalized initial screen: Parameters are filled with user-specific values (for example, values regarding cost center, region and so on) automatically

• Role-specific variants: Different BI cockpits for different roles

You can get a quick overview of business information in much the same way that you scan the front page of a newspaper. To access more detailed information you can use user-friendly navigation elements such as hyperlinks, dropdown boxes,

pushbuttons and so on. You can save BI cockpits as iViews. These are completely integrated into an Enterprise Portal.

characteristic

An evaluation group such as company code, product, customer group, fiscal year, period or region.

Characteristics provide classification possibilities for the dataset. The master data encompasses the permitted values of a characteristic, the so-called characteristic values. Characteristic values are discrete names.

Note: The characteristic region could, for example, have the values 'North', 'Central' and 'South'.

chart

Web item that retrieves data from a query view to create a diagram for a Web application. You can choose from a range of display options for the diagram. You can also navigate within interactive charts and analyze the data displayed.

classic InfoSet

Corresponds to the InfoSet, already familiar from R/3 Basis: An element of a SAP query. The InfoSet determines to which table, or which fields of the table, the query refers. InfoSets are mostly created using table joins or logical databases.

cleansing

Cleans data before update, checks data for feasibility before update and suppresses incorrect records.

collation process

Allows you to gather together several chains into a single chain in process chain maintenance screens. This means that you no longer have to schedule application processes individually.

The process chains maintenance screens contain the following collation processes:

• AND-process (last):

• The application process starts when all the events for the preceding processes have been triggered successfully.

• OR-process (each):

• The application process starts each time an event in a preceding process is triggered successfully.

• EXOR-process (first):

• The application process starts when the first event in one of the preceding

processes is triggered successfully.

communication structure

The communication structure is independent of the source system and has the structure of an InfoSource. It contains all the InfoObjects that belong to an InfoSource. All the data is updated into the InfoCube with this structure. The system always refers to the actively saved version of the communication structure.

Technically (i.e. with respect to length, type) the fields of the communication structure correspond to the InfoObjects of the Business Information Warehouse.

Common Warehouse Metamodel (Abbreviation: CWM)

The official definition from the OMG Web Site: The Common Warehouse Metamodel (CWM) is a specification that describes metadata interchange among data warehousing, business intelligence, knowledge management and portal technologies.

condenser

Program that compresses the contents of an InfoCube fact table.

control query

A help query that you execute before you execute the queries in the Web template, the result of which you use to parameterize the Web template.

Crystal Enterprise

Server component for scheduling, caching, and displaying reports on the Web. Content and user administration is carried out as part of the integration using the BW server.

Crystal Reports Designer

Design component for creating a Crystal Report that contains the report definition (layout).

Crystal Report

BW object type.

Report definition created using the Crystal Reports Designer and saved in BW. In a Crystal Report, several queries can be imbedded with several queries (similarly to an EXCEL workbook). A Crystal Report contains no current data.

A Crystal Report contains no current data.

data manager

Part of the OLAP processor that controls the data bank access that arises from the definition of a query.

Part of Warehouse Management that writes data into the data bank.

data mart interface

Enables the user to update data from one data target to another. Enables the user to update data within a BW system (Myself system) and also between several systems. If several BW systems are used, the system delivering the data is called the source BW and the system that is receiving data is called the target BW. The individual Business Information Warehouses in this type of setup are called data marts.

data provider

Object that delivers data for one or more Web items. A data provider has the same navigation status as a query at a particular point in time. The start view of a data provider corresponds to the query view. By navigating through the data or parameterizing the call, you change the status of the data provider.

data request

Denotes:

• The request that is sent to the source system by the scheduler, and also;

• The quantity of data and information that results in BW and in the source system through this request, and also;

• The loading procedure.

DataSource

Contains a number of fields that are provided in a flat structure, the extract structure, for data transfer to the Business Information Warehouse. Additionally, it describes the properties of the related extractor with regard to the data transfer to the Business Information Warehouse.

data target

Super-ordinate term for objects, into which data is loaded. InfoCubes, ODS objects, and InfoObjects (characteristics with attributes, texts or hierarchies) belong to these objects. Standard data targets, for which you cannot create or execute queries, and data targets, for which you can define queries, are different. The latter are also called InfoProviders. Data targets are the physical objects that are relevant for data modeling and for data loading.

data warehouse

A system that makes theme-oriented, integrated, stable, and time-related data available and supports making decisions on management levels. The function of a data warehouse is to pull together, clean up, consolidate, and provide consistently accessible data using analysis, reporting, and evaluation tools from various internal and external sources. The knowledge gained from this data forms the basis for guiding decision-making in an organization. A data warehouse is, therefore, a system that is primarily

used for supporting company control.

delta process

Extractor feature. Specifies how the data is to be transferred. As a DataSource attribute, it specifies how the DataSource data is to be forwarded to the data target. The user can determine, for example, with which data targets a DataSource is compatible, how the data is to be updated, and how serialization is to take place.

device recognition

Recognition by the server of mobile devices for device-specific adjustment for displaying Web applications. Using device recognition, the system decides whether a Web application or a mobile application (WAP or PDA application) is to be sent back to the client.

dimension

A grouping of those evaluation groups (characteristics) that belong together, as regards contents, in one generic term. With the definition of an InfoCube, characteristics are summarized into dimensions in order to store them in a table of the star schema (dimension table).

dropdown box

Web item that places characteristic values for filtering in a Web application in a

dropdown box.

elementary test

Part of a test that can not be split further into sub-tests. An elementary test checks related logical objects for consistency.

event

Signal to the background processing system that a certain status has been reached in the SAP system. The background processing system then starts all processes that were waiting for this event.

event collector

A number of events that have been successfully completed independently of each other, and to which the background processing is to respond.

The event collector corresponds to the and-process and the process chain maintenance. If an application process is scheduled using an event collector, it starts when all events for the preceding process are successfully triggered.

exor-process

Combined process in process chain maintenance.

When you use an exor-process in the process chain maintenance, the application process starts when the first event of the previous processes has been triggered successfully.

external system

System that stages data for the Business Information Warehouse and thus serves BW as a source system.

An external system can either be:

• an R/3 System with a release status before 3.0D, or

• a non-SAP system

Data and Metadata transfer from an external system to the Business Information Warehouse takes place using Staging BAPIs.

extraction structure

In the extraction structure, data of a DataSource is made available in the source system.

The extraction structure contains the number of fields that are offered by the extractor in the source system for the data loading process in BW.

extractor

Program used to fill the extract structure of a DataSource with data from datasets in the SAP source system.

fact table

The fact table is at the center of the star schema of an InfoCube. The data part contains all key figures (also called \"facts\") of the InfoCube and the key is formed by links to the entries of the dimensions of the InfoCube.

filter

Web item that displays those filter values for a query view in a Web application that you created when navigating. Also allows you to select single values.

flat reporting

Reporting based on one-dimensional tables, meaning the analysis is restricted to one dimension and its attributes. Unlike OLAP reporting, with flat reporting you can arrange the columns any way you like when you are designing a query in the tabular editor mode of the BEx query designer. For example, you can put a column for a characteristic between two columns for key figures. During the design of the query, you decide how you want the columns to be displayed. Once you have chosen a display type you are not able to change it. In flat reporting, the interactive options are restricted to filter, filter and drilldown according to, sort according to, and navigate on

hierarchies. Navigation functions that alter the geometry of the flat list, meaning that they change the number and order of the columns, for example, swapping or adding a drilldown, are available with OLAP reporting but not with flat reporting.

formatted reporting

Structure for reports that use master data, ODS objects, and multi-dimensional InfoProviders. Formatted reporting has all of the options for formatting reports (for example, font, font size, colors, graphics, and styles), and allows you to place report elements anywhere on the screen to the accuracy of one pixel (no grid positioning). The focus is on formula-based reports and the printing of reports.

There are no analytical functions: Interaction options are introduced at the time of designing the report.

generation template

Template, from which a program is generated.

A generation template is used when the desired program can not be generically written and must be suitably written for each special situation anew.

generic navigation block

Web item that retrieves data from a query view and displays it in the form of a table. All characteristics and structures of the query view are listed in the table and their

filter values are displayed. You can change the navigation status in the block by:

• Placing characteristics and structures in an axis (rows or columns) or removing them from an axis.

• Filtering by single values or removing filters.

hierarchy attribute

Attribute that describes the properties of an entire hierarchy (for example, level table type: specifies the form that a level table takes).

impact analysis

Group of methods that assess the effect of changes made to any dependent objects when an object is checked and activated.

The impact analysis ensures that the objects are consistent.

Examples:

• A navigation attribute is deleted from a characteristic. When the characteristic is activated, all the InfoCubes that use this characteristic are set to inactive. The InfoCubes have to be reactivated (without the navigation attribute) to make them consistent.

• In other cases, dependent objects are adjusted immediately if this is not possible

without manual changes.

InfoArea

Groups meta-objects together in the Business Information Warehouse:

Every data target is assigned to an InfoArea. The resulting hierarchy is then displayed in the Administrator Workbench. In addition to their property as a data target, InfoObjects can also be assigned to different InfoAreas using InfoObject catalogs.

InfoCube

The central objects, on which reports and analyses are based in BW, are known as InfoCubes.

An InfoCube describes a self-contained dataset (from the reporting view), for example, for a business-orientated area. This dataset can be evaluated with the BEx query. With an InfoCube, you might be dealing with:

• A BasicCube, that shows a quantity of relational tables in the star schema.

• A RemoteCube, whose transaction data is not managed in the Business Information Warehouse, or

• A MultiCube that presents a view on data from several BasicCubes or

RemoteCubes

Unlike the ODS object, the data fields of the BasicCube fact table cannot contain any character fields as key figures. Character fields are thus interpreted as keys.

InfoObject

Business reporting objects (customers, sales,...) are called InfoObjects in BW. They are categorized as characteristics, key figures, units, time characteristics and technical characteristics (for example, request number).

InfoPackage

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

InfoPackage group

Logically related InfoPackages are combined in an InfoPackage group.

InfoProvider

Super-ordinate term for objects, for which queries are created and executed in SAP BW. There are two types of InfoProvider; objects that contain physical data and objects that do not contain physical data. Data targets, such as InfoCubes, ODS objects, and InfoObjects (characteristics with attributes, texts or hierarchies) belong to the first type of InfoProvider, and InfoSets, RemoteCubes, SAP RemoteCubes, and MultiProviders belong to the second type. InfoProviders are the objects or views that are relevant for reporting.

InfoSet

Semantic layer using ODS objects and master data to create reports from these objects, in particular joins between these objects. In contrast to the classic InfoSet, this data view is BW-specific. InfoSets are created and changed in the InfoSet Builder. You can define reports based on InfoSets using the BEx Query Designer.

InfoSet Builder

Tool for creating and changing InfoSets using repository objects from BW (InfoObjects with master data and ODS objects).

InfoSet query (Abbreviation: ISQ)

Corresponds to the InfoSet query, already familiar from R/3 Basis (Business Content-SRV-QUE): Tool for creating lists. The data that is to be evaluated is compiled in InfoSets. The output medium for InfoSet queries is the SAP List Viewer.

InfoSource

An InfoSource describes the quantity of all available data for a business event, or type of business event (for example, Cost Center Accounting).

An InfoSource is a quantity of information that has been grouped together and can be said to belong together logically from a business point of view. InfoSources can contain either transaction data or master data (attributes, texts, and hierarchies). An InfoSource is always a quantity of InfoObjects that can be said to belong together logically. An InfoSource always refers to one scenario from an application (for example, Financial Accounting).

key figure

Values or quantities, such as sales revenue, fixed costs, sales quantity or number of employees.

In addition to the key figures saved on the database, you have the option of defining derived (calculated) key figures in the query definition in the Business Explorer. Such key figures are calculated using a formula from the key figures of the InfoCube.

Examples of derived key figures are \"sales revenue per employee\" (sales revenue divided by number of employees), or \"variance as a percentage\" or \"contribution margin\".

label

Web item with which you display characteristic, attribute and structure component descriptions and with which you can set a link to the context menu for the characteristic, attribute or structure component.

list of conditions

Web item that lists the available conditions and their status (active/not active/not applicable/not used) for a query view in a Web application.

list of exceptions

Web item that lists the available exceptions and their status (active/not active) for a query view in a Web application.

map

Web item that contains all the information necessary for displaying a geographical map in a Web report. The \"map\" Web item relates to the \"map layer\" Web items that are used. It has no direct connection to a data provider.

map layer

Web item that contains all the information about a particular layer of a map. You use this information to determine the various display formats (color shading, bar charts, and pie charts) and their settings for the map layer.

master data ID (SID)

Internal key of type INT4 that you use for master data for master data-bearing characteristics, especially for hierarchy nodes and for characteristic names. Master data IDs and characteristic values are stored in master data tables (SID tables). Information about time-independent or time-dependent master data, which is stored in a P table or a Q table, is saved again in an X or Y table, using SIDs instead of characteristic values.

master Web item

Template for a Web item. The master Web item determines the type of the Web item (for example, table, filter, chart, map, and so on) and includes default values for the attributes of each Web item. The various master Web items are available on the \"Standard\" tabstrip in the BEx Web Application Designer or in the BEx Web Application Wizard. You choose a master Web item from this list, assign a DataProvider to the Web item, and process the attributes to generate a Web item of your own. You add your Web item to your Web template or store it in the library so that it can be reused in the future. Web items that are stored in the library can become master Web items and be used as a template for additional Web items.

Example: You take the \"chart\" master Web item and create various master Web items for your library: Bar charts with either vertical or horizontal bars, pie charts, and so on.

master Web template

A Web template that is copied and used as a template for a new Web template.

MDX

Multidimensional Expressions

Query language for queries about data that is saved in multidimensional cubes.

metadata

Metadata is data about data. That is, metadata describes the origin, history and other aspects of data. Metadata enables you to use the information saved in the Business Information Warehouse effectively for reporting and analysis.

There are different classes of metadata:

• technical

• business

metadata repository

The metadata repository contains the different classes of metadata.

With this method of storing and presenting data, a consistent and homogeneous data model results across all source systems.

mobile application

Web application on a mobile device with an online connection to a BW system. Super-ordinate term of: PDA application, WAP application.

MOF

Meta-Object Facility

• One of the OMG-recognized (Object Management Group) standards which

• determines guidelines for the definition of metadata models provides

• programming tools for saving and accessing metadata in repositories.

The MOF standard is integrated in XMI.

You can find the specifications of MOF at www.omg.org.

• A metadata service which abides by the MOF specifications.

MOLAP (Multidimensional Online Analytical Processing)

Multidimensional data storage in special data structures that are based on arrays or cubes. MOLAP is used mostly in comparison with or as an alternative to ROLAP. Synonym: MOLAP store

MOLAP aggregate

Aggregate for a MOLAP cube. The aggregate is saved in a MOLAP store. Superordinate term: MOLAP

MOLAP cube

BasisCube with data that is saved in a MOLAP store.

monitor

The monitoring tool of the Administrator Workbench.

Using the monitor, you can oversee the data request and processing in the Administrator Workbench

MultiProvider

Special InfoProvider that collates data from several InfoProviders and makes it available for reporting. The MultiProvider itself does not contain any data; the data

comes from the InfoProviders on which it is based. You can assemble a MultiProvider from different combinations of InfoProviders.

InfoProviders and MultiProviders are objects or views that are relevant for reporting.

Myself system

System that is connected to itself via the data mart interface. This enables the user to update data from one data target into another data target.

navigation

Analysis of the InfoProvider data by displaying different views on the data of a query or a Web application. With the aid of the various navigational functions, such as:

• 'Fix as filter value'

• 'Insert drilldown according to'

you can generate different views of the data (navigational states), that are presented in the results area of the query or in a Web application. Changing views is considered to be navigation.

navigation attribute

Characteristic attributes can be changed into navigation attributes. You can then drilldown according to these navigation attributes in a query. Characteristic attributes can only be displayed.

node attribute

Attribute that every node in the hierarchy possesses (for example, the date fields DATETO and DATEFROM, if the hierarchy structure is time-dependent).

nodes

Nodes are the objects that build a hierarchy. A node can have children (sub-nodes). There are two different types of node:

• postable nodes

• unpostable nodes

object tag

Placeholders in a Web template that start with . You use object tags to generate data providers and Web items in a Web template.

ODS object

Object that stores consolidated and cleaned transaction data on a document level.

An ODS object describes a consolidated dataset from one or several InfoSources. This dataset can be evaluated using a BEx query. An ODS object contains a key (for example, document number, position) as well as data fields that, as key figures, can also contain character fields (for example, customer). You can update ODS object data into InfoCubes or other ODS objects in the same system or a different system using a delta update. In contrast to multi-dimensional data stores for InfoCubes, data in ODS objects is stored in transparent, flat database tables.

OLAP reporting

Reporting based on multidimensional data sources. OLAP reporting allows you to analyze several dimensions at the same time (for example, time place, product, and so on). The aim of OLAP reporting is to analyze key figures, such as an analysis of the sales figures for a certain product in a particular time period. The questions that you have about this product in this period are formulated in a query. The query includes the key figures and characteristics that contain the data that are necessary to analyze and answer your questions. The data is displayed in a table and is the starting point for a more detailed analysis to answer a number of different questions.

A range of interaction options, such as sorting, filtering, swapping characteristics, and recalculating values, allow you to navigate flexibly through the data during the runtime.

In the Business Information Warehouse you can analyze the data in the following areas of the Business Explorer:

• In the BEx Analyzer in the form of queries

• In the BEx Web Applications

Unlike in flat reporting, the number of columns in OLAP reporting is dynamic. The analysis of the data is the main focus. The layout, formatting, and printing of reports is secondary.

OLAP trace

Record of system activities in a log

or-process

Combined process in the process chain maintenance.

When you use an or-process in the process chain maintenance, the application process is started each time an event in one of the previous processes is triggered successfully.

PDA application

Web application on a PDA device with Pocket IE.

Persistent Staging Area

Transparent database table, in which request data is stored in the form of the transfer structure. A PSA is created per DataSource and source system. It represents an initial store in BW, in which the requested data is saved unchanged for the source system.

process

A process within or outside an SAP system with a defined start and end time.

process chain

Series of processes that are scheduled in the background waiting for an event. Some of these processes trigger an event that, in turn, can start other processes.

process instance

Instance of a process. This contains the most important information that the process or subsequent processes want to communicate. For example, with the loading process, the name of the request. The instance is determined by the process itself for the run time. The process log is stored under the process instance.

process type

Type of process, for example, loading process. The process type decides, amongst other things, which tasks the process has to perform and which properties it has in the maintenance.

process variant

Name of the process. A process can have different variants. For example, in the loading process, the name of the InfoPackage represents the process variants. The user defines a process variant for the scheduling time.

P table

Master data table for time-independent master data.

This table contains the following fields:

• The characteristic with the master data itself

• The characteristic compounded to this characteristic („super-ordinate characteristic“)

• All time-independent attributes

• CHANGED (D: Delete record, I: Insert record, Blank space: No changes; changes evaluated only after activation)

• OBJEVERS (A: Active version, M: Modified and therefore, not active version)

These fields form the key.

Q table

Master data table for time-dependent master data. The Q table has the same fields as the P table.

query

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 per InfoProvider.

You define a query in the BEx Query Designer by selecting InfoObjects or reusable structures of an InfoProvider and distributing them to filters, rows, columns, and free characteristics to create a view of the data (query view). You save the start view of the query (that was saved in the query designer) into your favorites or roles. You use this saved query view as a basis for analyzing data and reporting in the BEx Analyzer, BEx Web Application, BEx Mobile Intelligence, or in formatted reporting.

query view

Saved navigational status of a query.

radio button group

Web item that allows you to filter characteristic values using a group of radio buttons.

RemoteCube

A RemoteCube is an InfoCube whose transaction data is managed externally rather than in the Business Information Warehouse. Only the structure of the RemoteCube is defined in BW. Data for reporting is read from another system using a BAPI.

Reporting Agent

Tool for scheduling reporting functions in the background. The following functions are available:

• Evaluating exceptions

• Printing queries

• Precalculating Web templates

results area

In the Business Explorer Analyzer, every part of the worksheet is a results area in which the result of a query is displayed. The results area corresponds to the Web item table in Web applications.

reusable structure

Part of a query that is saved, so that it can be used again in an InfoCube.

Reusable structures enable you to use parts of a query definition again in other queries. These structures are freely definable reports consisting of combinations of characteristics and basic key figures (for example, calculated or restricted key figures from the InfoCube). A structure can be a plan/actual comparison or a contribution margin scheme, for example.

ROLAP (Relational Online Analytical Processing)

Store for multi-dimensional data in a relational database, that is, in tables that are organized in a star schema. Opposite: MOLAP

SAP exit

Processing type for variables that are delivered with SAP BW Business Content. Used for variables that are processed by automatic replacement using a predefined replacement path (SAP exit).

scheduler

With the aid of the scheduler, you determine which data (transaction data, master data, texts or hierarchies) is to be requested and updated from which InfoSource, DataSource and source system and at which point in time.

scheduling package

Logical collection of several reporting agent settings for background processing.

source Business Information Warehouse

Business Information Warehouse that you can use as a source system for other BW servers.

source system

System that makes the Business Information Warehouse available for data extraction.

staging

A process that prepares (stages) data in a data warehouse.

standard Web template

A Web template used to display a query in ad-hoc reporting on the Web. You can specify any Web template from the SAP Reference IMG as a standard Web template.

start process

Defines the start of a process chain.

surrogate index

Special BW index on the key fields of a fact table.

The surrogate index is created on a fact table and not on the primary index. In contrast to the primary index, the surrogate index has no UNIQUE restriction.