SAP BW






Overview of SAP History and BW/BI Evolution
In a SAP life we are full time user/developer of SAP and we have spent lot of time in understanding the components and features of SAP but in this competitive environment I don't know how many people tried to know about the history of SAP. This blog is to help those who are interested to know the history but caught with hectic schedule where they don't find time for their analysis. Here I have compiled several points as easy reckoner to know the history.SAP Enterprise Resource Planning is a product of SAP AG, which is a German based company headquartered at Walldorf. The primary objective is to develop standard application software for real-time business processing
In 1972, the SAP was founded by five former IBM employees.Dietmar Hopp,
 Hans-Werner Hector,
 Hasso Plattner,
Klaus E. Tschira,
Claus Wellenreuther
The SAP is an acronym of German language description, Systemanalyse und Programmentwicklung which means System Analysis and Program Development. After some time the acronym was changed as Systeme, Anwendungen und Produkte in der Datenverarbeitung which means Systems, Applications and Products in Data Processing.
In 1973, the first product SAP R/1 solution based on Mainframe was launched. In 1979, SAP launched SAP R/2 as a result of intensive examination of SAP's IBM database and dialog control system.In 1992, SAP followed the trend from mainframe (R/2) computing to client-server architectures (R/3). The development of SAP's internet strategy with mySAP.com redesigned the concept of business processes.
Note: 'R' stands for real-time data processing.
SAP BW/BI history:
In 1997, the first version of SAP product for reporting, analysis and data warehousing was launched and the product was termed as "Business Warehouse Information System".
Evolution of SAP BW/BI:
Name Version Release 
BIW 1.2A Oct-1998 
BIW 1.2B Sep-1999 
BIW 2.0A Feb-2000 
BIW 2.0B Jun-2000 
BIW 2.1C Nov-2000 
Name Change, BIW to BW 
BW 3.0A Oct-2001 
BW 3.0B May-2002 
BW 3.1 Nov-2002 
BW 3.1C Apr-2004 
BW 3.3 Apr-2004 
BW 3.5 Apr-2004 
Name Change, BW to BI 
BI 7 July-2005 
BIW => Business Warehouse Information System.
BW => Business Warehouse
BI => Business Intelligence.
We everyone is sticked to the incremental change of version change with enhanced features so always the name change is confusing for us.
Even several SAP BW consultant posted question to know the difference between SAP BW and SAP BI. There is no definite definition for the name change it's just like a normal version change with some addition/modification.
Still the confusion remains how to name the current product, the below SAP blog content helps in certain extent for the clarification.
In 2008, SAP used the term "Business Intelligence" to refer
Ø  SAP BusinessObjects BI solutions and also
Ø  SAP NetWeaver BI.
In order to remove confusion, the term Business Intelligence is now associated only with the solutions from the SAP BusinessObjects portfolio.
So SAP NetWeaver Business Intelligence (BI) is no longer used and instead we refer by,
Ø  SAP NetWeaver Business Warehouse (BW) ,
Ø  SAP Business Explorer (SAP BEx) and
Ø   SAP NetWeaver BW Accelerator (BWA)  




BW Glossary ,Definitions and Acronymns

A

Aggregate

An aggregate is a subset of an InfoCube. The objective when using aggregates is to reduce I/O volume.The BW OLAP processor selects an appropriate aggregate during a query run or a navigation step. If no appropriate aggregate exists, the BW OLAP processor retrieves data from the original InfoCube instead.
For examples, assume you may have 10 dimensions and each one have 10 value, that means you may have up to 10^10 possible records. If high level manager often access the report focus revenue in 2008 by customer, that's mean only 2 dimension are involved. You can do aggregate and it may only contain 2 dimensions with 100 records. It reduce the I/O and improve the performance.

Aggregate rollup

Aggregate rollup is a procedure to update aggregates with new data loads. Reference Aggregate

Application component

Application components are used to organize InfoSources. They are similar to the InfoAreas used with InfoCubes. The maximum number of characters allowed for the technical name is 32.

Authorization

An authorization defines what a user can do, and to which SAP objects. For example, a user with an authorization can display and execute, but not change, a query. Authorizations are defined using authorization objects.

Authorization object

An authorization object is used to define user authorizations. It has fields with values to specify authorized activities, such as display and execution, on authorized business objects, such as queries. The maximum number of characters allowed for the technical name is 10.

Authorization profile

An authorization profile is made up of multiple authorizations. The maximum number of characters allowed for the technical name is 10.

B

BEx

Short for Business Explorer. It includes following tools to present the reports to end user: Analyzer  / Web Application Designer / Report Designer / Web Analyzer.

Bitmap index

A bitmap index uses maps of bits to locate records in a table. Bitmap indices are very effective for Boolean operations of the WHERE clause of a SELECT statement. When the cardinality of a column is low, a bitmap index size will be small, thereby reducing I/O volume.
Another possible choice in BW on this topic is B-tree index.

Business Content

Business Content is a complete set of BW objects developed by SAP to support the OLAP tasks. It contains roles, workbooks, queries, InfoCubes, key figures, characteristics, update rules, InfoSources, and extractors for SAP R/3, and other mySAP solutions.
You can simply use business content directly, or take it as template for your project to speed up implementations.

BW

Business Warehouse (BW) is a Data Warehousing solution from SAP.
When we talking about BW, it often talking about BW3.5. The latest version is SAP Business Intelligence 7.0.

BW Monitor

BW Monitor displays data loading status and provides assistance in troubleshooting if errors occur. T-code: RSMO

BW Scheduler

BW Scheduler specifies when to load data. It is based on the same techniques used for scheduling R/3 background jobs.

BW Statistics

BW Statistics is a tool for recording and reporting system activity and performance information.
BWA / BIA
BW/BI Accelarator is a tool that improves the performance of BW 7.x queries on InfoCubes. It enables quick access to any data with a low amount of administrative effort and is especially useful for sophisticated scenarios with unpredictable query types, high data volume and high frequency of queries

C

Cache / OLAP Cache

A technology to improve the performance. Cache buffers query result data, in order to provider them for further accesses.  

Cache Mode

Determines whether and in what way the  query result and navigational states are to be saved in the OLAP  Cache.

Change run

Change run is a procedure used to activate characteristic data changes.

Characteristic

Characteristics are descriptions of fields, such as Customer ID, Material Number, Sales Representative ID, Unit of Measure, and Transaction Date. The maximum number of characters allowed for the technical name is 9.

Client

A client is a subset of data in an SAP system. Data shared by all clients is called client-independent data, as compared with client-dependent data. When logging on to an SAP system, a user must specify which client to use. Once in the system, the user has access to both client-dependent data and client-independent data.

Communication structure

The communication structure is the structure underlying the InfoSource.

Compound attribute

A compound attribute differentiates a characteristic to make the characteristic uniquely identifiable. For example, if the same characteristic data from different source systems mean different things, then we can add the compound attribute 0SOURSYSTEM (source system ID) to the characteristic; 0SOURSYSTEM is provided with the Business Content.

Compress

Compressing will bringing data from different requests together into one single request (request ID 0) in Infocube.
When you load data into Infocube, they are group with Requests ID. You can easily manage the data with Request ID. But the request ID have disadvantages cause the same data record (with same characteristics but different request ID) to appear more than once in the fact table. It waste the table space and affects query performance.
You can eliminate these disadvantages by compressing data and bringing data from different requests together into one single request (request ID 0).
Technically, Compress will move the data in F table to E table and aggregate the records with same char. automatically.
It is widly used when you are sure that the data in InfoCube is correct and you won't need Request ID in the future. And be careful if you defined your own delta mechanism.

D

Data packet size

For the same amount of data, the data packet size determines how work processes will be used in data loading. The smaller the data packet size, the more work processes needed.You can set it in SPRO

Data Mining

Data mining is the process of extracting hidden patterns from data. It is one of the function provided by SAP BI.
Take the most famous story "beer and diapers" as example. Wall-Mart noticed that men often bought beer at the same time they bought diapers. They mined its receipts and proved the observations. So they put diapers next to the beer coolers, and sales skyrocketed. The story is a myth, but it shows how data mining seeks to understand the relationship between different actions.

Data Warehouse

Data Warehouse is a dedicated reporting and analysis environment based on the star schema (Extended) database design technique and requiring special attention to the data ETTL process.
DataMart
The distribution of contents of ODS or InfoCube into other BW data targets on the same or on other BW systems

DataSource

A DataSource is not only a structure in which source system fields are logically grouped together, but also an object that contains ETTL-related information. Four types of DataSources exist:
  • DataSources for transaction data
  • DataSources for characteristic attributes
  • DataSources for characteristic texts
  • DataSources for characteristic hierarchies
If the source system is R/3, replicating DataSources from a source system will create identical DataSource structures in the BW system. The maximum number of characters allowed for a DataSource's technical name is 32.

BW SD MM FI DATASOURCES

MM 
Data Sources Tables
Purchasing
2LIS_02_SCL EKKO, EKBE, T001, T001W, EKET, EKPA.
2LIS_02_HDR EKKO, EKBE, T001, EKPA.
2LIS_02_ITM EKKO, EKBE, T001, T001W, EKPO, TMCLVBW, T027C, ESSR, T147K, T147
2LIS_02_SCN EKET, EKES, EKPO.
2LIS_02_CGR EKBE, EKES, EKPO.
2LIS_02_SGR EKET, EKBE, KKPO

Inventory
2LIS_03_BX stock tables, MCHA, MARA, T001, T001W, CALCULATED FROM MBEW, EBEW, QBEW.
2LIS_03_BF MSEG, MBEW, MKPF.
2LIS_03_UM BKPF, MBEW, QBEW, EBEW, BSEG.
MM   
Purchasing   Datasources
ODS  
 0PUR_O01  2LIS_02_ITM, 2LIS_02_SGR, 2LIS_02_CGR, 2LIS_02_SCN.
 0PUR_O02  2LIS_02_HDR, 0PUR_O01
 0PUR_DS03  2LIS_02_SCL and 2LIS_02_SGR.
CUBE  
 0PUR_C10  2LIS_02_SCL and 2LIS_02_SGR.
 0PUR_C07  
 0PUR_C08  
 0PUR_C09  0PUR_O02, 80PUR_O01, 2LIS_02_HDR
 0SRV_C01  2LIS_02_S174
 0PUR_C04  2LIS_02_S011, 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR
 0PUR_C01  2LIS_02_S012, 2LIS_02_ITM, 2LIS_02_SCL
 0PUR_C02  2LIS_02_S013
 0PUR_C05  0MM_PUR_VE_01
 0PUR_C06  0MM_PUR_VE_02
 0PUR_C03  2LIS_02_S015
Inventory Management  
CUBE  
 0IC_C03  2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM
 0IC_C02  2LIS_03_S195, 2LIS_03_S197
 0IC_C01  2LIS_03_S196, 2LIS_03_S198
SD 
 Data sources Tables
 2LIS_11_VAKON VBUK, VBUP, VBAK, VBAP, VBKD, KOMV, T001.
 2LIS_11_VAHDR VBAK, VBUK, T001
 2LIS_11_VAITM VBAP, VBUP, VBAK, VBKD, VBAJP, T001, VBUK, PRPS.
 2LIS_11_VASCL VBAP, VBUP, VBAK, VBEP, VBKD, T001, PRPS
 2LIS_11_VASTH VBUK
 2LIS_11_VASTI VBUP, VBUK
 2LIS_11_V_ITM VBAP, VBAK, VBKD, VBUP, T001, PRPS, VBUK.
 2LIS_11_V_SCL VBUP, VBEP, VBKD, VBAP, VBAK, T001, PRPS.
 2LIS_11_V_SSL VBAP, VBEP, LIPS, WVBEP, VBUP
 2LIS_13_VDKON VBUK, VBRP, KOMV, T001, VBRK.
FI 
 DATASOURCES Tables
Cost Center Accounting 
 0CO_OM_CCA_1 COSP, COSS
 0CO_OM_CCA_2 COSP, COSS
 0CO_OM_CCA_3 COSL, COKL.
 0CO_OM_CCA_4 COSR
 0CO_OM_CCA_5 COSB
 0CO_OM_CCA_6 COOMCO
 0CO_OM_CCA_7 BPJA, BPPE.
 0CO_OM_CCA_8 COST, TKA07,COOMCO, CSLA, COST, COKL.
 0CO_OM_CCA_9 COVP (COEP& COBK), COSP, COST, COEJ, COEP, T001.
 0CO_OM_CCA_10 COOI, COSP_VTYPE.
Product Cost Controlling 
 0CO_PC_PCP_01 KEKO, TCKH3, TCKH8.
 0CO_PC_PCP_02 KEKO, TCKH3.
 0CO_PC_PCP_03 CKIS, T001K, TKA02, KEKO, MARA, MBEW.
 0CO_PC_PCP_04 CKIS, T001K, TKA02, KEKO, MBEW, MARA
 0CO_PC_01 AUFK, AFPO, COSS, COSP, COSB, COSL, COKEY, TKA09, TKV09
 0CO_PC_02 AUFK, AFPO, COSS, COSP, COSB, COSL, COKEY, TKA09, TKV09


DB Connect

A BW function that offers flexible options for extracting data directly into the BW from tables and views in database management systems that are connected to the BW in addition to the default connection. You can use tables and views from the database management systems that are supported by SAP to transfer data. DataSources are used to make data known to the BW, where it is then processed in the same way as data from all other sources.

Delta Caching

Additional requests will be read from the InfoCube's (F) fact table. These additional requests will be updated into the OLAP Cache. In this way, when they are changes to the data basis, the complete data for the query no longer has to be read from the database again.  

Delta update

The Delta update option in the InfoPackage definition requests BW to load only the data that have been accumulated since the last update. Before a delta update occurs, the delta process must be initialized.

Development class

A development class is a group of objects that are logically related.
Dimension table
Part of the Star Schema structure for InfoCubes. Dim tables contain pointers to the Fact tables & to the Master Data (SID tables).

Display attribute

A display attribute provides supplemental information to a characteristic. Reference Navigation attribute

Drill-down

Drill-down is a user navigation step intended to get further detailed information. For example, you can drill-down to detail report through free characteristic

DSO

Short for Data Store Object. Reference ODS in BW3.5
A DataStore object serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level. This data can be evaluated using a BEx query.
A DataStore object contains key fields (such as document number, document item) and data fields that, in addition to key figures, can also contain character fields (such as order status, customer). The data from a DataStore object can be updated with a delta update into InfoCubes (standard) and/or other DataStore objects or master data tables (attributes or texts) in the same system or across different systems.
There are 3 kinds of DSO: Standard DataStore Object / Write-Optimized DataStore Objects / DataStore Objects for Direct Update. Check the definition and example at:http://help.sap.com/saphelp_nw2004s/helpdata/en/f9/45503c242b4a67e10000000a114084/frameset.htm
DTP
The Data Transfer Process (DTP) transfers data from source objects to target objects in BI 7.x. You can also use the data transfer process to access InfoProvider data directly. Prerequisite: a transformation to define the data flow between the source and target object.

E 

EDW

The Enterprise Data Warehouse, a comprehensive / harmonized data warehouse solution, is design to avoid isolated applications. Reference BW330.

ETTL

ETTL, one of the most challenging tasks in building a data warehouse, is the process of extracting, transforming, transferring, and loading data correctly and quickly. Also known as ETL.
Extraction Structure
The data structure used by the extraction program to extract data. Its fields are mapped to the fields of the SAP Source System DataSource.

F

Fact tables

The Fact table is the central table of the InfoCube. Here key figures & pointers to the dimension tables are stored. There are two fact tables: the F-fact table and the E-fact table. If you upload data into an InfoCube, it is always written into the F-fact table. If you compress the data, the data is shifted from the F-fact table to the E-fact table. The F-fact tables for aggregates are always empty, since aggregates are compressed automatically. After a changerun, the F-fact table can have entries as well as when you use the functionality 'do not compress requests' for Aggregates.
E-fact table is optimized for Reading => good for Queries. F-fact table is optimized for Writing => good for Loads

Free characteristic

A free characteristic is a characteristic in a query used for drill-downs. It is not displayed in the initial result of a query run.

Full update

The Full update option in the InfoPackage definition requests BW to load all data that meet the selection criteria specified via the Select data tab. Reference Delta update
Filter
Filter is used to restrict data to a certain business sector, product group, or time period. And these can be saved and reused in the in othercontexts. Here the data is filtered and showed in the intial result of the query. 

G

Generic data extraction

Generic data extraction is a function in Business Content that allows us to create DataSources based on database views or InfoSet queries. InfoSet is similar to a view but allows outer joins between tables.

Granularity

Granularity describes the level of detail in a data warehouse. It is determined by business requirements and technology capabilities. For high level reports, manager tend to high aggregated report such as by month or by BU. But operational reports always require more detail information such as by day or by product spec. 

H

High Cardinality

means that this dimension contains a high number of attributes. This information is used to execute physical optimizations, depending on the database platform. For example, different index types from those in a standard case are used. Generally, a dimension has a high cardinality if the number of dimension entries is 20% (or more) of the number of fact table entries.

I

IDoc

IDoc (Intermediate Document) is used in SAP to transfer data between two systems. It is a specific instance of a data structure called the IDoc Type, whose processing logic is defined in the IDoc Interface. See: IDOC Basics

Index

An index is a technique used to locate needed records in a database table quickly. BW uses two types of indices: B-tree indices for regular database tables and bitmap indices for fact tables and aggregate tables.

InfoArea

InfoAreas are used to organize InfoCubes and InfoObjects. Each InfoCube is assigned to an InfoArea. Through an InfoObject Catalog, each InfoObject is assigned to an InfoArea as well. The maximum number of characters allowed for the technical name is 30.

InfoCube

An InfoCube is a fact table and its associated dimension tables in the star schema. The maximum number of characters allowed for the technical name is 30.

InfoCube compression

InfoCube compression is a procedure used to aggregate multiple data loads at the request level.

InfoObject

In BW, key figures and characteristics are collectively called InfoObjects. See: https://wiki.sdn.sap.com/wiki/display/BI/Characterstic+and+Key+FiguresCharacteristic and key figures

InfoObject Catalog

InfoObject Catalogs organize InfoObjects. Two types of InfoObject Catalogs exist: one for characteristics, and one for key figures. The maximum number of characters allowed for the technical name is 30.

InfoPackage

An InfoPackage specifies when and how to load data from a given source system. BW generates a 30-digit code starting with ZPAK as an InfoPackage's technical name.

InfoSource

An InfoSource is a structure in which InfoObjects are logically grouped together. InfoCubes and characteristics interact with InfoSources to get source system data. The maximum number of characters allowed for the technical name is 32. In BW 3.5 it is a MUST and in BI 7.0 it is optional.

Information Lifecycle Mangement

Generally, the data was generated in OLTP system such as R/3. In BW, Information Lifecycle Management includes data target management and data archiving.
Reference ADK and archiving for more information. And online help: http://help.sap.com/saphelp_nw2004s/helpdata/en/d0/84e5414f070640e10000000a1550b0/frameset.htm

K

Key figure

Key figures are numeric values or quantities, such as Per Unit Sales Price, Quantity Sold, and Sales Revenue. The maximum number of characters allowed for the technical name is 9. Reference Characteristic.

L

Line item dimension

A line item dimension in a fact table connects directly with the SID table of its sole characteristic.
When you creating a InfoCube, you have chance to use this feature on define dimension. It is only possible if exactly one characteristic in a dimension. It help to improve the performance because we do not need to join SID table when accessing the master data.

Logical system

A logical system is the name of a client in an SAP system.

M

Metadata Repository  

Metadata repository contains information about the metadata objects of SAP NetWeaver Business Intelligence, important object properties and their relationships with other objects. Metadata contains data about data.

Multi-cube

A multi-cube is a union of basic cubes. The multi-cube itself does not contain any data; rather, data reside in the basic cubes. To a user, the multi-cube is similar to a basic cube. When creating a query, the user can select characteristics and key figures from different basic cubes.

N

Navigational attribute

A navigational attribute indicates a characteristic-to-characteristic relationship between two characteristics. It provides supplemental information about a characteristic and enables navigation from characteristic to characteristic during a query.
The naming convention for a navigational attribute is: InfoObject_Attribute, such as 0customer_0country

Number range

A number range is a range of numbers that resides in application server memory for quick number assignments.

O

ODS

ODS is a BW architectural component located between PSA and InfoCubes that allows BEx reporting. It is not based on the star schema and is used primarily for detail reporting, rather than for dimensional analysis. ODS objects do not aggregate data as InfoCubes do. Instead, data are loaded into an ODS object by inserting new records, updating existing records, or deleting old records, as specified by the 0RECORDMODE value.
Reference DSO.

Open Hub Service

The open hub service enables you to distribute data from an SAP BW system into external data marts, analytical applications, and other applications.

OLTP / OLAP

Short for Online Transaction Processing / Online Analytical Processing.
OLTP system are Transacton-Orientated, which means it is generally used to support the daily operation. For example, SAP R/3, ERP / PDM / MES ...
OLAP is generally used to analysis data. For examples, SAP BW, DDS - Decision Support System, EIS - Executive information systems.

P

Parallel query

A parallel query uses multiple database processes, when available, to execute a query.

Partition

A partition is a piece of physical storage for database tables and indices. If the needed data reside in one or a few partitions, then only those partitions will be selected and examined by a SQL statement, thereby significantly reducing I/O volume. It can be done in Cube or DB level.
The benefit of using partition is mainly focus on:
  • Well balanced partition / fragments
  • Improve read performance
  • Fast of delete partition by "Drop" instead of "Delete from where"
Fact table can be partitioned over a time characteristic either 0CALMONTH or 0FISCPER(Fiscal year/period). Repartition is possible in SAP BI 7.0. Seehttps://wiki.sdn.sap.com/wiki/x/N4C4AQRepartitioning

Partitioning Type

For MultiProvider queries, Partitioning Type provides options for handling the data that is returned by the individual InfoProviders from the MultiProvider separately and saving it in the cache separately.
  • No Partitioning: All results of the InfoProviders are summarized as one result and cached.
  • Partitioning in Groups: Infocubes in one group, and other infoproviders are saved together in groups according to their properties.
  • Partitioning in Groups: Basis Cubes Separate: similar as above. individual Infocubes are saved separately.
  • Each InfoProvider Separate: All InfoProviders are saved separately.

Process Chain

A process chain is a sequence of processes that are scheduled to wait in the background for an event. You can include process chains in other process chains to manage a group of them, known as meta chains.
It is design at the implementation phase and one of the most important jobs in support and maintenance phase.
More information please reference: http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm

Profile Generator

Profile Generator is a tool used to create authorization profiles.

PSA

The Persistent Staging Area (PSA) is a data staging area in BW. It allows us to check data in an intermediate location, before the data are sent to its destinations in BW.

Q

Query

A BW query is a selection of characteristics and key figures for the analysis of the data in an InfoCube. A query refers to only one InfoCube, and its result is presented in a BEx Excel sheet. The maximum number of characters allowed for the technical name is 30.

R

Read mode

Read mode determines how often the OLAP processor reads data from the database during navigation.
  • Read all data
  • Read during navigation
  • Read during navigation & expanding hierarchy 

Reconstruct

Reconstruct is a procedure used to restore load requests from PSA.

Request

A request is a data load request from BW Scheduler. Each time that BW Scheduler loads data into an InfoCube, a unique request ID is created in the data packet dimension table of the InfoCube.

RFC

RFC (Remote Function Call) is a call to a function module in a system different from the caller's usually another SAP system on the local network.

Role

In Profile Generator, an authorization profile corresponds to a role. A user assigned to that role also has the corresponding authorization profile. A user can be assigned to multiple roles. The maximum number of characters allowed for the technical name is 30.
Reclustering
It allows you to change the clustering of Infocubes and Data store objects that already contain data.

S

SID

SID (Surrogate-ID) translates a potentially long key for an InfoObject into a short four-byte integer, which saves I/O and memory during OLAP.

Source system

A source system is a protocol that BW uses to find and extract data. When the source system is a non-SAP system, such as a flat file or a third-party tool, the maximum number of characters allowed for the technical name is 10. When the source system is an SAP system, either R/3 or BW, the technical name matches the logical system name. The maximum number of characters allowed for the technical name is 32.

Step-By-Step BW Connectivity

Abstract: Describes all the activities that need to be carried out in order to connect the BW System to other source system.
1. Update client objects
T-code: SCC4 Display View "Clients": Overview
Task: Choose the client, update Std Currency / Client Role info. 
2. Define the logical system
T-code: SPRO
Task:  Define the logical system 
3. Assign logical system to client
T-code: SCC4   
4. Create BW System as an own logical system
T-code: RSA1
Task: Activating Metadata 
5. Create user
T-code: SU01 
Task: Address: Last Name / Function
Logon data: Password / User Type, System
Profiles: SAP_ALL / SAP_NEW / S_BI-WHM_RFC 
6. Assign User
 T-code: RSA1
Task: Setting -> Global Setting
Create Source System / R/3 Client User Pwd  
And reference this wiki for more information: https://wiki.sdn.sap.com/wiki/display/BI/BW+Connectivity
Configurations in the SAP Source System to connect to a BI system in order to transfer data:http://help.sap.com/saphelp_nw70/helpdata/EN/27/8d8342a7d30d53e10000000a155106/frameset.htm
Configurations in BI each SAP source system you want to connect to the BI system in order to transfer data:http://help.sap.com/saphelp_nw70/helpdata/EN/5a/d98342fa4b5551e10000000a1550b0/frameset.htm


Star schema

A star schema is a technique used in the data warehouse database design to help data retrieval for online analytical processing.
SAP BW use extended star schema with following advantage compare to classical star schema: 
  • Use of generated key (short number) for faster access
  • External hierarchy
  • Multi-language support
  • Master data are separated. It is common to all cubes
  • Support slowly changing dimensions
  • Aggregates in its own tables for faster access

Statistics

For a SQL statement, many execution plans are possible. The database optimizer generates the most efficient execution plan based on either the heuristic ranking of available execution plans or the cost calculation of available execution plans. Statistics is the information that the cost-based optimizer uses to calculate the cost of available execution plans and select the most appropriate one for execution. BW uses the cost-base optimizer for Oracle databases.

System Administration Assistant

System Administration Assistant is a collection of tools used to monitor and analyze general system operation conditions.

System landscape

The system landscape specifies the role of each system and the paths used in transporting objects among the various systems.

T

Time-dependent entire hierarchy

A time-dependent entire hierarchy is a time-dependent hierarchy whose nodes and leaves are not time-dependent.
For example, you have two hierarchy which presents organization of company in 2007 and 2008.

Time-dependent hierarchy structure

A time-dependent hierarchy structure consists of nodes or leaves that are time-dependent, but the hierarchy itself is not time-dependent.
For example, you have one hierarchy but one of his node was changed from 2007 and 2008. HR may belong to administration division before 2007 and belong to supporting division after 2008.

Transfer rule

Transfer rules specify how DataSource fields are mapped to InfoSource InfoObjects.
In BI 7.0, transfer rule and update rule are replaced by transformation.

Transfer structure

A transfer structure maps DataSource fields to InfoSource InfoObjects.
Transformations (TRF)
TRFs connect source objects (DataSources, DSOs, InfoCubes, InfoSets) to Data Targets (InfoProviders) of a data-staging process. They replace combination of transfer rules & update rules. The TRF process allows you to consolidate, cleanse & integrate data. You must use DTP to load data to InfoProvider.

U V W X Y Z

Update rule

An update rule specifies how data will be updated into their targets. The data target can be an InfoCube or an ODS object. If the update rule is applied to data from an InfoSource, the update rule's technical name will match the InfoSource's technical name. If the update rule is applied to data from an ODS object, the update rule's technical name will match the ODS object's technical name prefixed with number 8.
In BI 7.0, transfer rule and update rule are replaced by transformation. But we still have chance to use it in BI 7.0

Variable

A variable is a query parameter. It gets its value from user input or takes a default value set by the variable creator.
Variables act as placeholders for:
  • Characteristic values
  • Hierarchies
  • Hierarchy nodes
  • Texts
  • Formula elements

Virtual InfoProvider

A Virtual Provider is a type of InfoCube where the data is not managed in BI. Only the structure of the VirtualProvider is defined in BI, the data is read for reporting using an interface with another system.

Workbook

A BW workbook is an Excel file with a BEx query result saved in BDS. BW assigns a 25-digit ID to each workbook. Users need merely name a workbook's title.

BW Transport:

Useful links
Documents
Transport Source System -> source system not transportable, create in target system
Transport Datasource
Cannot collect transfer rules -> Source system assignment
Source system not exist -> Source system mapping
Transport application component hierarchy
R3TR DSAA APCO
How to create Package/Development Class
Object is locked by request
Transport sequence
Transport Infopackage
Transport Process Chain
What's the difference Transport and BEx Transport
Is it possible to transport between different BW version ?
Note 1015518 - Different objects (original, target) cannot be transported
Using XML import/export ?
Transport in different geography ?
Other resources
http://www.bwexpertonline.com/archive/Volume_01_(2003)/Issue_02_(February)/V1I2A5.cfm?session=












Five Ways to Enhance BI Functionality Using ABAP-- Part I--Data Extraction



This part I will explain the first point: Data Extraction.
For data extraction, there are three aspects that we can do the enhancement.
1. Creating generic DataSources using function modules for data extraction.
   When should we use the generic data extraction tools to create a DataSource?
  • Business Content does not include a DataSource for your application.
  • You want to implement a delta method on your generic DataSource that cannot be implemented by using the generic delta functionality(timestamp,date...)
  • The application does not allow you to create additional application-specific generic extractors(CO-PA,FI-SL,LIS)
  • You use your own programs in the SAP system to populate your own tables
  • You have to extract data from several DB tables when: Using a view is not possible because of insufficient JOIN; Only some fields are relevant to these tables; Data has to be enriched with information not available in the BW system.
    Tools for Generic Data Extraction: TCODE---RS02.
  


     
    For funtion module here I used SAP Standard: RSAX_BIW_GET_DATA_SIMPLE, you can see the detail through TCODE:SE37. OR you can write your own function module as well.
2. Enhancing DataSources for transaction data, master data attributes, and texts.
   Reasons:
  • You want to add extra attributes to the characteristics(master data) shipped with the system
  • You want to populate additional fields that you appended to the extract structure with data at the time of extraction
  • You want to change/enhance texts or hierachies.
   TCODE: SBIW---> Postprocessing of DataSources
     ----> Edit DataSources and Application Component Hierarchy 


click the red mark button: 'Enhance Extraction Structure'.



fill in the name and then you can append the fields in this structure.
3. Using the Service API function enhancement to enrich data.
   TCODE: SBIW---> Postprocessing of DataSources
     ----> Edit DataSources and Application Component Hierarchy 
click the red mark button: 'Function Enhancement'. 
create the project and assign the Enhancement 'RSAP0001' (this is the only enhancement for service API). 
See there are four user-exits for different use.
EXIT_SAPLRSAP_001: use for transaction data
EXIT_SAPLRSAP_002: use for master data
EXIT_SAPLRSAP_003: use for text
EXIT_SAPLRSAP_004: use for hierarchy
You can write the code in each of these function modules according to your requirements.
This part I will explain the second point: Data Staging.
For BI 7.0, in data staging, there are many aspects that we can write abap code to deal with data.
1. InfoPackages


The routine here is to create dynamic file name, click the red mark button and create name and write the related code. The following is for your reference. 
2. Start Routines
    Start routines are processed:
   ---After the data in written into the PSA
   ---Before the transformance is processed
  Actually, we write ABAP code here is for data cleansing or data consolidation. 
 3. Transfer Rules
     It is processed in the transformance and actually this routine is written for some particular fields.
     In the transformance, select the particular field and right click the rule detail, in the rule type, choose 'Routine'. 
4. End Routine
     End Routine is processed after transformance, actually for data cleansing. 
5.Expert Routine
This type of routine is only intended for use in special cases. You can use the expert routine if there are not sufficient functions to perform a transformation. The expert routine should be used as an interim solution until the necessary functions are available in the standard routine









This part I will explain the third point: BEx Variables.
We can use ABAP coding to fill a variable value.
Here we should use the standard SAP Enhancement 'RSR00001'.
  • Through TCODE: SMOD, fill in the enhancement, you can see the details.
       
  • In the function module of this enhancement, you will find include ZXRSRU01 where you implement your program code.
  • The exit is called four times, called '"steps" (I_STEP)
   Step 1(I_STEP = 1): is called before the processing of the variable pop-up and gets called for every variable of the processing type,"customer exit." You can use this step to fill your varibale with a default or proposal value.
   Step 2(I_STEP = 2): is called after porcessing of the variable pop-up. This step is called only for those variables that are not marked as "ready for input" and are set to "mandatory variable entry"
   Step 3(I_STEP = 3): is called after all variable processing and gets called only once and not per variable. Here you can validata the user entries.
   Step 0(I_STEP = 0): is called for variables that are used in authorizations objects.
This part I will explain the last point: ABAP in Process Chain.
Use the ABAP Program process type if you want to use a simple, independent program in a chain or if you want to use a program scheduled by a user or another program in the background. This allows you to schedule a program of your choice (ABAP report) in the process chain management, with or without program variants.
Actually using ABAP Program in Process Chain is to record error messages or trigger a event to start another process chain. 
Drop and Drag the process type 'ABAP Program' , then create a name for it. 


Put the program name which you create for recording the message or raise an event.
The following code is for your reference, I used it to raise an event. 
Comment: EVENTID is created through tcode: sm62.








  Note: You can nto overwrite the user input values into a variaable with this customer exit. You can only derive values for other variables or validate the user entries.
Code in ZXRSRU01 is for your reference:


Comment: TIM_VAR is the variable that is created in BEx Query Designer and its type is customer exit so that it can be called through the function module.
In this demo, I put the I_STEP = 1,  that means before the variable pop-up, I give the value 'current date' for this variable.

Useful ABAP Programs & Function Modules in SAP BI



Listed below are some of the frequently used ABAP Programs in SAP BI (NW 2004).
Program name
RSCDS_NULLELIMDelete fact table rows where all Key Figure values are zero. See Note 619826.
RSDG_CUBE_ACTIVATEActivation of InfoCubes
RSDG_CUBE_COPYMake InfoCube Copies
RSDG_CUBE_DELETEDelete InfoCubes
RSDG_DODS_REPAIRActivation of all ODS Objects with Navigation Attributes
RSDG_ODSO_ACTIVATEActivation of all ODS Objects
RSDG_IOBJ_ACTIVATEActivation of all InfoObjects
RSDG_IOBJ_DELETEDeletion of InfoObjects
RSDG_IOBJ_REORGRepair InfoObjects
RSDG_IOBJ_REORG_TEXTSReorganization of Texts for InfoObjects
RSDG_MPRO_ACTIVATEActivating Multiproviders
RSDG_MPRO_COPYMake Multiprovider Copies
RSDG_MPRO_DELETEDeleting Multiproviders
RS_COMSTRU_ACTIVATE_ALLActivate all inactive Communication Structures
RS_TRANSTRU_ACTIVATE_ALLActivate Transfer Structure
RSAU_UPDR_REACTIVATE_ALLActivate Update Rules
RRHI_HIERARCHY_ACTIVATEActivate Hierarchies
SAP_AGGREGATES_ACTIVATE_FILLActivating and Filling the Aggregates of an InfoCube
SAP_AGGREGATES_DEACTIVATEDeactivating the Aggregates of an InfoCube
RS_PERS_ACTIVATEActivating Personalization in Bex(Inactive are highlighted)
RSSM_SET_REPAIR_FULL_FLAGConvert Full Requests to Repair Full Requests
SAP_INFOCUBE_DESIGNSPrint a List of Cubes in The System and Their Layouts
SAP_ANALYZE_ALL_INFOCUBESCreate DB Statstics for all InfoCubes
SAP_CREATE_E_FACTTABLESCreate Missing E-Fact Tables for InfoCubes and Aggregates
SAP_DROP_EMPTY_FPARTITIONSLocate/Remove Unused or Empty partitions of F-Fact Table
SAP_DROP_TMPTABLESRemove Temperory Database Objects
SAP_RSADMIN_MAINTAINAdd, change, delete RSADMIN table entries
CUBE_SAMPLE_CREATEA fast way to put some "sample" records in a InfoCube. No need to use Flatfiles,
just enter the value in a ALV-Grid or let fill the Cube with random value.
SAP_CONVERT_NORMAL_TRANSConvert BasisCube to Transactional Cube and the opposite way around.
Listed below are some of the frequently used Function Modules within BW.
Function ModuleDescription (Function Group RRMX)
RRMX_WORKBOOK_DELETEDelete BW Workbooks permanently from Roles & Favourites
RRMX_WORKBOOK_LIST_GETGet list of all Workbooks
RRMX_WORKBOOK_QUERIES_GETGet list of queries in a workbook
RRMX_QUERY_WHERE_USED_GETLists where a query has been used 
RRMX_JUMP_TARGET_GETGet list of all Jump Targets
RRMX_JUMP_TARGET_DELETEDelete Jump Targets
Function ModuleDescription
MONI_TIME_CONVERTUsed for Time Conversions.
CONVERT_TO_LOCAL_CURRENCYConvert Foreign Currency to Local Currecny.
CONVERT_TO_FOREIGN_CURRENCYConvert Local Currency to Foreign Currency.
TERM_TRANSLATE_TO_UPPER_CASEUsed to convert all texts to UPPERCASE
UNIT_CONVERSION_SIMPLEUsed to convert any unit to another unit. (Ref. table : T006)
TZ_GLOBAL_TO_LOCALUsed to convert timestamp to local time
FISCPER_FROM_CALMONTH_CALCConvert 0CALMONTH or 0CALDAY to Financial Year or Period
RSAX_BIW_GET_DATA_SIMPLEGeneric Extraction via Function Module
RSAU_READ_MASTER_DATAUsed in Data Transformations to read master data InfoObjects
RSDRI_INFOPROV_READ
RSDRI_INFOPROV_READ_DEMO
RSDRI_INFOPROV_READ_RFC		Used to read Infocube or ODS data through RFC
DATE_COMPUTE_DAY
DATE_TO_DAY		Returns a number what day of the week the date falls on.
DATE_GET_WEEKWill return a week that the day is in.
RP_CALC_DATE_IN_INTERVALAdd/Subtract Years/Months/Days from a Date.
RP_LAST_DAY_OF_THE_MONTHS
SLS_MISC_GET_LAST_DAY_OF_MONTH		Determine Last Day of the Month.
RSARCH_DATE_CONVERTUsed for Date Converstions. We can use in Info Package routines.
RSPC_PROCESS_FINISH    To trigger an event in process chain
 DATE_CONVERT_TO_FACTORYDATEReturns factory calendar date for a date
 CONVERSION_EXIT_PDATE_OUTPUTConversion Exit for Domain GBDAT: YYYYMMDD  -> DD/MM/YYYY
 CONVERSION_EXIT_ALPHA_INPUTConversion exit ALPHA, external->internal
CONVERSION_EXIT_ALPHA_OUTPUTConversion exit ALPHA, internal->external
 RSPC_PROCESS_FINISHFinish a process (of a process chain)
RSAOS_METADATA_UPLOADUpload of meta data from R/3
RSDMD_DEL_MASTER_DATADeletion of master data
RSPC_CHAIN_ACTIVATE_REMOTETo activate a process chain after transport
                         
USEFUL ABAP-CLASS in NW 7 - BI to fix problems with Transformation
Class CL_RSTRAN_STATDescription
DELETE_VERSION_FROM_DB (Static Method)


BI Certification Info links

Links and information about the certifications offered by SAP in the BI Space. Common questions regarding BI certification are addressed and relevant links provided.
 There are lots of question floating arounds related to BI certification. This Wiki is for those who has already thought of taking the exam. If you are still
SAP provides three levels of Certification in BI.
1. 
C_TBW45_04S
 Certification Syllabus SAP Consultant Certification Solution Consultant SAP NetWeaver 2004s - Business Intelligence
 2 . C_TBW45_70:- SAP Certified Application Associate- Business Intelligence with SAP NetWeaver 7.0
 3. P_BIE_70 - SAP Certified Application Professional - BI Enterprise DataWarehousing with SAP Net Weaver 7.0
These certification exams vary in their level of difficulties and different pattern. For example:C_TBW45_04S will have 80 questions to be answerd in 3 hours whereas C_TBW45_70 will have 90question in 3 hours. Also, 
you will get partial credit in the former but no such privilegesin later exam
.There are no better study materials than TBWs. Which all TBWs to be read, check the syallabus here:http://www.sap.com/services/education/certification/certificationtest.epx?context=%5b%5bC_TBW45_04S%5d%5d%7c
These can be downloaded from Internet. Besides these TBWs, there are some important links - which is listed below:
Simulation Test:
Some Important Documents on SDN:
Threads Related to Certification:
Miscellaneous Links:

For deleting a transformations rule version from database, helpful if the transformation metadata are corrupted.



Subscribe to: Posts (Atom)