How I may help
LinkedIn Profile Email me!
Call me using Skype client on your machine

Reload this page SAP Business Intelligence

Here is a condensed but yet detailed analysis of SAP Business Intelligence.

RSS 2.0 XML feed on SAP valid:
SAP Solution Applications, Modules, Exams
SAP Certification Exams and Training
SAP Installation
SAP R/3 Configuration
SAP Netweaver Architecture Internals
SAP R/3 Tablespaces
SAP Solution Manager
SAP R/3 User and Server Administration
SAP R/3 Monitoring and Performance Tuning
SAP GUI Emulation for Load Testing
SAP R/3 ABAP Programming
SAP Portal
SAP Business Intelligence

 

Site Map List all pages on this site 
About this site About this site 
Go to first topic Go to Bottom of this page


* SAP's Glossary,
* help.sap.com
* SAP Developer Network
* SAP Professional Journal
* SAP Insider

SAP Courses:
BW001_62 SAP NetWeaver Business Intellig E-Learning
BW310
BW360

Set screen Product Version History

    SAP BW 2.0B/2.1C used ITS server for web reporting.
    SAP BW 3.0B & 3.1 used WAS 6.20
    SAP BW 3.5 integrated with IGS 6.40

 

Go to Top of this page.
Next topic this page

Set screen Technical Summary

    The SAP NetWeaver BI (Business Intelligence) Suite operates in 3 layers to provides flexible reporting and analysis tools for strategic analysis.

    1. Reporting Layer
    2. Data Warehousing Layer
    3. ETL (Extract Transfer Load) Layer

    Business Explorer (BEx) suite,

    BEx Query Designer.

    Queries created within the BEx Query Designer can be used by two technologies:

    • On MS Excel Add-in (desktop client software)
    • On the web

    Excel-based BEx Analyzer uses many more round-trips and transferred data to the server than web frontend.


Go to Top of this page.
Next topic this page

Set screen Installation


Go to Top of this page.
Next topic this page

Set screen BI Services

    Services:

    • ACL Service
    • Lock Service
    • Transport Service
    • Object Cache Service
    • Messaging Service


Go to Top of this page.
Next topic this page

Set screen Data Objects

    InfoProviders are objects or views relevant to reporting, which queries in SAP BW can be created or executed.
    There are two types of InfoProviders:

    1. objects that contain physical data, called data targets:
      • InfoCubes — self-contained datasets for a business-oriented area, with a set of relational tables created with a star schema. Such datasets can be evaluated using BEx query.
      • DSO/ODS (DataStore Object/Operational Data Store) objects which store master data and flow data in flat structures containing key fields and data fields referenced by index tables to primary objects. DataStore objects relevancy indicators are the basis for selecting data in the Source Data Layer. Such objects are used in the Tool BI part of Bank Analyzer.
      • InfoObjects (characteristics with attributes, texts, or hierarchies).
    2. objects that display no physical data storage:
      • ISets (InfoSets) a SAP Query element which determine the tables (or fields within a table) to which a query can refer. InfoSets are usually based on table joins (logical databases).
      • RemoteCubes ,
      • SAP RemoteCubes , and
      • MP (MultiProviders) provide views which combine data from all types of InfoProviders (collated using a union operation). MultiProviders are used for logical partitioning. Global queries on independent basis InfoProviders with cumulative key figures are by default parallel and united at a defined synchronization point. However, global queries though a MultiProvider can be manually switched to serial processing (using transaction RSRT, per SAPnote 449477).
      • VP (VirtualProviders) provide a path for read-only direct access to data stored in the BI system or in other SAP systems or non-SAP systems.

    Each InfoProvider is assigned to an IA (InfoArea) for grouping meta-objects in the BI system, as displayed in the Data Warehousing Workbench. In addition to their properties as an InfoProviders, InfoObjects can also be assigned to different InfoAreas.

    Star Schema: a large fact table in the center, with several dimension tables surrounding it.)

    An extended star schema includes Navigational attributes. These require additional table joins at runtime (versus dimension characteristics which do not).
    Aggregates with navigational attributes require change runs to be scheduled every time this master data is loaded.

    AG (Aggregate) store the dataset of an InfoCube redundantly and persistently in a summarized form in the database. When building an aggregate from the characteristics and navigation attributes of an InfoCube, you can group the data according to different aggregation levels. Remaining characteristics that are not used in the aggregate are summarized. New data is loaded into an aggregate using logical data packages (requests). You differentiate between filling and rolling up with regard to loading data. Aggregates enable you to access InfoCube data quickly for reporting. Thus, aggregates help to improve performance.

    ISP (InfoSpoke) object for the export of data within the open hub service. Defined in the InfoSpoke are the following:

    • from which open hub data source the data is extracted,
    • in which extraction mode the data is delivered, and
    • into which open hub destination the data is delivered.

    An IP (InfoPackage) describes which data in a DataSource should be requested from a source system. The data can be precisely selected using selection parameters. An InfoPackage can request the following types of data: Transaction data, Attributes for master data, Hierarchies for master data, Master data texts.

    APD - Analysis Process Designer is a tool used to model an analysis process. It provides a graphical interface to model analysis processes. An analysis process is built using nodes and data flow arrows. The nodes stand for data sources, transformations and data targets. The dataflow arrows model the sequence in which the data is read and transformed.

    A PC (Process Chain)is a sequence of processes that are scheduled in the background to wait for a particular event. Some of these processes trigger an additional event, which in turn can start other processes.


Go to Top of this page.
Next topic this page

Set screen Tablespaces

    Default tablespaces for BW 3.x is reduced from previous versions.
    PSAPSID,
    PSAPSIDUSR,
    PSAPSID620,
    PSAPTEMP
    SYSTEM.

    For performance reasons, temporary objects SAP BW uses for query processing and other processes are defined outside the ABAP data dictionary.

    Because of typically large tables residing within BW tablespaces, separating fact and dimension tables of InfoCubes, aggregates, ODS Object tables and PSA tables to their own tablespaces improves performance and administration of grouped objects (e.g. archiving, backup of a tablespace).


Go to Top of this page.
Next topic this page

Set screen Visual Composer

    Each report is a collection of characteristics and key figures (InfoObjects) for the analysis of the data of an InfoProvider.


Go to Top of this page.
Next topic this page

Set screen Queries

    Saved query view are used as the basis for data analysis and reporting in the BEx Analyzer, in BEx Web applications, in BEx Mobile Intelligence, or in formatted reporting.

    A query always refers exactly to one InfoProvider, whereas many queries can be defined for a InfoProvider.

    Query variables serve as place-holders for characteristic values, hierarchies, hierarchy nodes, texts, and formula elements.


Go to Top of this page.
Next topic this page

Set screen BEx Query Analyzer

    SAP BI users use BEx Analyzer as an analytical, reporting, and design tool embedded in Microsoft Excel to access InfoProvider data, Queries, Query Views, and workbooks easily, and to analyze the data by navigating interactively. They can configure global settings and specific settings for workbooks, create new workbooks, and trigger workbook distribution. To define new query definitions, they can also launch the BEx Query Designer.


Go to Top of this page.
Next topic this page

Set screen BEx Query Designer

    The Query Designer designs queries by dragging InfoObjects (reusable objects) and dropping into a query design consisting of filters, rows, columns, and free characteristics.


Go to Top of this page.
Next topic this page

Set screen xApp Analytics

    Broadcaster and BEX Web Charts use IGS (Internet Graphics Server) 6.40, which stores data in XML (earlier versions store chart settings in binary format).

 




Go to Top of this page.
Next topic this page

Set screen Publishing BI Info to NW Portal


Go to Top of this page.
Next topic this page

Set screen Web Business Planning

    The Overview of these functions:
    Planning Modeler
    Planning Wizard
    BEx Web Analyzer


Go to Top of this page.
Next topic this page

Set screen Web Business Explorer

    The Overview of these functions:
    My Portfolio
    BEx Portfolio
    BEx Web Analyzer
    BEx Broadcaster
    Universal Worklist
    Collaborative


Go to Top of this page.
Next topic this page

Set screen Consuming External Web Services


Go to Top of this page.
Next topic this page

Set screen Report Layouts in Excel and Web


Go to Top of this page.


Go to Top of this page.
Next topic this page

Set screen ETL Layer

    A TR (Transformation) occurs when data is loaded from one BI object to another BI object. A transformation converts the records in a data package from the format of the source structure into the format of the target structure. A transformation consists of at least one transformation rule.

    RT (Rule/Routine) such as Start/End/Expert/Update/Transfer are where particular data object transformations are handled. It can be direct mapping from input to output, formula (FOX), ABAP routine, etc. Transfer and update rules can be debugged using transaction RSMO (Upload Monitor).

    Each DTP (Data Transfer Process) takes care of data ‘Distribution’ within SAP BI (from PSA or InfoProviders to InfoProviders).

    The DS (DataSource) to a BIW is populated by an EX (Extractor) reading datasets in the SAP source system.

    A DataSource describes the properties of the related extractor with regard to the data transfer to the Business Information Warehouse.

    The DataSource contains a number of fields that are provided in a flat structure (the extraction structure) for data transfer to the Business Information Warehouse.

    The Extractor (Function Module, report, table view, BAPI, user exit) is a program used to fill the extraction structure of a DataSource with data.

 
Go to Top of this page.
Next topic this page

Portions ©Copyright 1996-2010 Wilson Mar. All rights reserved. | Privacy Policy | | HTMLHELP | CSS | Cynthia 508 |

Related Topics:
another page on this site LoadRunner 
another page on this site SNMP 
another page on this site Rational Robot 
another page on this site Free Training! 
another page on this site Tech Support 


How I may help

Send a message with your email client program


Your rating of this page:
Low High




Your first name:

Your family name:

Your location (city, country):

Your Email address: 



  Top of Page Go to top of page

Thank you!