You are on page 1of 74

SAP/BI Manual


Document Covers: To enter into the Data Warehousing Workbench : Modeling


T-Code RSA1 Options: Document covers steps for entering into Data Warehousing Workbench : Modeling Please refer below instructions.

What is a Data Warehouse? ‡ ‡ ‡ ‡ A data warehouse is a copy of the transaction data specifically structured for querying and analysis.* Ralph Kimball A data warehouse can also include non-transaction data A data warehouse is separate from the transaction processing system(s) A data warehouse often focuses on a specific activity or entity

Purpose The Data Warehousing Workbench (DWB) is the central tool for performing tasks in the data warehousing process. It provides data modeling functions as well as functions for controlling, monitoring, and maintaining all the processes in SAP NetWeaver BI that are related to the procurement, retention, and processing of data.

1|P ag e

SAP/BI Manual

Structure of the Data Warehousing Workbench The following figure shows the structure of the Data Warehousing Workbench

Application Toolbar

Menu Bar

Views & Applications of single functional area

Navigation Window with functional areas

Status Bar

2|P ag e

SAP/BI Manual

Modeling Purpose The tool you use for modeling is the Data Warehousing Workbench. Depending on your analysis and reporting requirements, different BI objects are available to you for integrating, transforming, consolidating, cleaning up, and storing data. BI objects allow efficient extraction of data for analysis and interpretation purposes. Process Flow The following figure outlines how BI objects are integrated into the dataflow:

Data that logically belongs together is stored in the source system as DataSources. DataSources are used for extracting data from a source system and transferring it into the BI system. Definition: Data Source A DataSource is a set of fields that provide the data for a business unit for data transfer into BI. From a technical viewpoint, the DataSource is a set of logically-related fields that are provided to transfer data into BI in a flat structure (the extraction structure), or in multiple flat structures (for hierarchies). There are four types of DataSource: Ɣ DataSource for transaction data Ɣ DataSource for master data  DataSource for attributes  DataSource for texts  DataSource for hierarchies

3|P ag e

as is the case with InfoCubes.SAP/BI Manual The Persistent Staging Area (PSA) in the BI system is the inbound storage area for data from the source systems. time characteristics (for example. currency. period. characteristics are stored in dimensions. Use The transformation process allows you to consolidate. customers). InfoObjects with attributes or texts can themselves also be InfoProviders (if in a query). fiscal year. The transformation rules map the fields of the source to at least one InfoObject in the target. The characteristics determine the granularity (the degree of detail) at which the key figures are kept in the InfoCube. The requested data is saved. They are divide into characteristics (for example. Use InfoObjects are the smallest units of BI. product. request number). unchanged from the source system. The data format remains unchanged. Structure Characteristics are sorting keys. units (for example. A transformation converts the fields of the source into the format of the target. 4|P ag e . cleanse. You can semantically synchronize data from heterogeneous sources. key figures (for example. When you load data from one BI object into a further BI object. into an InfoProvider or InfoSource. for example. or region. fiscal year) and technical characteristics (for example. These dimensions are linked by dimension IDs to the key figures in the fact table. such as company code. The transformation specifies how the data (key figures. The requested data is saved. time characteristics. Request data is stored in the transfer structure format in transparent. characteristics) is updated and transformed from the source. revenue). unchanged from the source system. customer group. In the InfoCube. This is required for constructing InfoProviders. meaning that no summarization or transformations take place. the data is passed through a transformation. and integrate data. information is mapped in a structured form. relational database tables in BI. Using InfoObjects. InfoObject Definition Business evaluation objects are known in BI as InfoObjects. The information is mapped in structured form using the InfoObjects. Purpose The Persistent Staging Area (PSA) is the inbound storage area in BI for data from the source systems. They specify classification options for the dataset and are therefore reference objects for the key figures. amount unit).

Technical characteristics have only one organizational meaning within BI. which is obtained as ID when loading requests. Key figures of type amount are always assigned a currency key and key figures of type quantity also receive a unit of measurement. Units are also required so that the values for the key figures have meanings. or number of items. InfoProviders Definition Generic term for BI objects into which data is loaded or that display views of data.SAP/BI Manual In general. an InfoProvider contains only a sub-quantity of the characteristic values from the master data table. Time characteristics are characteristics such as date. You analyze this data in BEx queries. The key figures provide the values that are reported on in a query. An example of this is the request number in the InfoCube. These are known as the characteristic values. fiscal year. and so on. They form the data part of an InfoProvider. 5|P ag e . Key figures can be quantity. It helps you to find the request again. The master data includes the permitted values for a characteristic. amount.

of a business-orientated area. However. From a reporting point of view. 6|P ag e . This dataset can be evaluated in a BEx query. Their data can be analyzed in a uniform way. The term InfoProvider encompasses objects that physically contain data: InfoArea InfoCubes Definition An object that can function as both a data target and an InfoProvider. The type of data staging and the degree of detail or "proximity" to the source system in the data flow diagram differs from InfoProvider to InfoProvider. an InfoCube describes a self-contained dataset.SAP/BI Manual Use InfoProviders are different metaobjects in the data basis that can be seen within query definition as uniform data providers. they are seen as uniform objects. for example. in the BEx Query Designer.

A dialog box appears in which you can set indicators for individual navigation attributes.SAP/BI Manual An InfoCube is a quantity of relational tables arranged according to the star schema: A large fact table in the middle surrounded by several dimension tables. DataStore Object Definition A DataStore object serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level. In InfoObject maintenance. customer). 7|P ag e . InfoObjects as InfoProviders Definition You can flag an InfoObject of type characteristic as an InfoProvider if it has attributes. You can also define queries for the characteristic (more exactly: for the master data of the characteristic) and then report using the master data. A DataStore object contains key fields (such as document number. The system does not create fact tables or dimension tables. flat database tables. the data in DataStore objects is stored in transparent. can also contain character fields (such as order status. transactional InfoCube). SAP RemoteCube. virtual InfoCube with Services. These are then available like normal characteristics in the query definition. you can also select two-level navigation attributes (the navigation attributes for the navigation attributes of the characteristic) for this characteristic on the Attributes tab page. In the InfoObject maintenance on the Master Data/Texts tab page. 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. It is not yet possible to use transformation rules to load hierarchies. Unlike multidimensional data storage using InfoCubes. This data can be evaluated using a BEx query. Use You can define transformation rules for the characteristic and use them to load attributes and texts. you set the With Master Data indicator . in addition to key figures. Select Navigation Attribute InfoProvider. Use InfoCubes are supplied with data from one or more InfoSources or ODS objects (Basic InfoCube) or with data from a different system (RemoteCube. The data is then loaded into the master data tables using the transformation rules. document item) and data fields that.

such as: VirtualProviders InfoSet Definition Name for a particular type of InfoProvider: An InfoSet describes data sources that are usually defined as joins for ODS objects or InfoObjects (characteristics with master data). and can then use the master data for reporting. Use In the BEx Query Designer you compile reports (queries) about activated InfoSets. The information is collected from the tables of the relevant InfoProviders. When an InfoSet is made up of several characteristics. The individual objects can appear in a join any number of times. Structure Every ODS object and every InfoObject that is a characteristic with master data can be included in a join. A join can contain objects of the same object type. you have to assign an InfoArea to the characteristic. or objects of different object types. A time-dependent join or temporal join is a join that contains an InfoObject that is a timedependent characteristic.SAP/BI Manual Integration If you want to use a characteristic as an InfoProvider. Unlike the classic InfoSet. You create an InfoSet using the characteristics Business Partner (0BPARTNER) Ȃ Vendor (0VENDOR) Ȃ Business Name (0DBBUSNAME). InfoProviders can also be objects that do not physically store data but which display logical views of data. Staging is used to load data into these InfoProviders. you are able to map transitive attributes and report on this master data. Join conditions connect the objects in a join to one another (equal join-condition). InfoSets allow you to report on several InfoProviders by using combinations of master data-bearing characteristics and ODS objects. The characteristic is subsequently displayed in the InfoProvider tree in the Data Warehousing Workbench. A join condition determines the combination of records from the individual objects that are included in the resulting set. 8|P ag e . and InfoSet is a BW-specific view of data. An InfoSet is a semantic layer over the data sources and is not itself a data target.

Use the Table Display pushbutton to activate this function. For a detailed description of the procedure.0B/2. ODS object. and InfoSet. Use A MultiProvider allows you to run reports using several InfoProviders. See Creating InfoSets and Editing InfoSets. The MultiProvider does not itself contain any data. since products that do not result in sales are also displayed.1C. For every InfoProvider that is included in a join there are two dimensions (key and attribute) in the BEx Query Designer.SAP/BI Manual Integration InfoSet Maintenance in the Administrator Workbench You create and edit InfoSets in the InfoSet Builder. In BW releases 2. this combination of two InfoCubes is still called a MultiCube. These InfoProviders are connected to one another by a union operation. refer to the Slow Moving Items Scenario. Its data comes entirely from the InfoProviders on which it is based. InfoProviders and MultiProviders are the objects or views that are relevant for reporting. 9|P ag e . InfoCube and InfoObject: You have an InfoCube with your products and sales. InfoObject. These dimensions contain the fields and attributes for the selected InfoSet. You combine this InfoCube with the 0MATERIAL InfoObject. Structure A MultiProvider can consist of different combinations of the following InfoProviders: InfoCube. Reports using InfoSets The BEx Query Designer supports the tabular (flat) display of queries. You can combine the two InfoProviders into one MultiProvider so that you can compare the actual data with the planned data in a query. InfoCube and InfoCube: You have an InfoProvider with actual data for a logically closed business area and an equivalent InfoProvider with planned data. MultiProviders Definition A MultiProvider is a type of InfoProvider that combines data from a number of InfoProviders and makes it available for reporting purposes. This allows you to display any "slow-moving items".

These joins only combine values that appear in both tables. joins form the intersection of the tables Aggregation Level Use Aggregation levels are used as InfoProviders for planning: with an aggregation level. In contrast to a union. Use the Planning Modeler or the Planning Wizard for this. the system also displays the aggregation levels (symbol ) and the underlying InfoProviders in the 10 | P a g e . For more information on the functioning principle of aggregation and saving the changed data records for an aggregation level by means of a simple example. Integration You can create multiple aggregation levels for an InfoProvider. An aggregation level is set using a set of characteristics and key figures from the underlying InfoProvider. The key figures included in the aggregation level are aggregated using the characteristics that are not included in the aggregation level. an aggregation level is located on a real-time enabled InfoCube.SAP/BI Manual A union operation is used to combine the data from these objects into a MultiProvider. In the simplest case. all values of these data sets are combined. see Simple Aggregation Level. In the Modeling functional area of the Data Warehousing Workbench. Here. In other words. you model levels whose data can be changed manually using input-ready queries or automatically using planning functions. the system constructs the union set of the data sets involved. As a comparison: InfoSets are created using joins. Aggregation levels can also be created on MultiProviders.

The InfoObjects selection list allows you to display all 11 | P a g e . choose Create. Once it has been activated. To change an aggregation level.. This InfoProvider includes at least one real-time-enabled InfoCube. choose Save. Choose Transfer. 1. Features Simple Aggregation Level A real-time enabled InfoCube is the basis of a simple aggregation level.SAP/BI Manual InfoProvider overview. To save the definition of the aggregation level. 4. the system displays an overview of all InfoObjects of the InfoProvider. the system shows all the InfoProviders available in your system. Note the conditions listed above. If you do not enter a search term and choose Start. To check the definition of the aggregation level in view of consistency. In the lower screen area of the Planning Modeler. When you choose Check. choose Check. 2. Creating Aggregation Levels . is the basis of a complex aggregation level. such as superordinate characteristics from compounded characteristics. 8. 5. Prerequisites In the Planning Modeler or Planning Wizard you have selected (and if necessary edited) an InfoProvider to act as the basis of the aggregation level. If the definition is consistent. choose Activate. you can branch to the Planning Modeler and edit the selected aggregation level. the system displays an overview of all InfoObjects of the InfoProvider used in the aggregation level. choose Change.. When you double-click on the aggregation level. Changing Aggregation Levels . 6. The Create Aggregation Level dialog box appears. Enter a technical name and a description. the aggregation level is ready for use. For more information about the corresponding processing step. Choose the InfoObjects that are to be included in the aggregation level... Complex Aggregation Level A MultiProvider that includes at least one real-time enabled InfoCube. see InfoProvider. To create an aggregation level. 7. 1. You can find a simple example under Simple Aggregation Level. 3. In the lower screen area of the Planning Modeler. but no simple aggregation level. the system tries to complete necessary objects. Choose the appropriate InfoProvider.

Change the definition as required. or those not used in the aggregation level. Data Flow 12 | P a g e . In BEx. You need to use an InfoSource if you want to execute two transformations one after the other. the system accesses an InfoProvider. Subsequently. 2. check and activate the changed definition. the data can be updated to further InfoProviders. only those used in the aggregation level. The InfoProvider provides the data that is evaluated in queries. The following figure gives an overview of the BI objects that can be used in analysis and reporting. Save. 3. it is not important how the data is modeled. You can also distribute data to other systems using the open hub destination.SAP/BI Manual InfoObjects for the InfoProvider. They are divided into InfoProviders that contain data and InfoProviders that only display logical views and do not contain any data.

SAP/BI Manual Functions of the Datawarehousing Workbench ‡ Modeling ± ‡ Database objects and transformations are created Administration ± Load Scheduling. Monitoring and data administration ‡ Transport Connection ± Specialized BI Transport tool set ‡ Documents ± Central GUI for maintenance of documents ‡ BI Content ± Delivered content is activated for use 13 | P a g e .

SAP/BI Manual ‡ Translation ± BI Object description are translated for Multiple Language support ‡ Metadata Repository ± Power Users and Functional Experts can find details on delivered and custom content objects Transformation: BI 2004s 14 | P a g e .

SAP/BI Manual To enter into Data Warehousing Workbench : Modeling 15 | P a g e .

SAP/BI Manual Right Click on ͞Infoprovider͟ bar and choose option ͞Create Infoarea͟ InfoArea name / Object name must be alphanumeric 16 | P a g e .

SAP/BI Manual Type Infoarea ʹ Alphanumeric Space between two is not allowed to create Infoarea name (Technical Name) 17 | P a g e .

SAP/BI Manual New Infoarea Created 18 | P a g e .

SAP/BI Manual How to Create New Infocube? 1. Right Click on InfoArea (Test Project) & click on ͞Create Infocube͟ option 19 | P a g e .

The Technical Name Should be Alphanumeric 20 | P a g e . To enter the Technical Name & Description for the New Infocube 2.SAP/BI Manual 1.

SAP/BI Manual Add Key Figures & Dimentions 21 | P a g e .

SAP/BI Manual 22 | P a g e .

SAP/BI Manual 23 | P a g e .

SAP/BI Manual 24 | P a g e .

SAP/BI Manual 25 | P a g e .

SAP/BI Manual 26 | P a g e .

SAP/BI Manual 27 | P a g e .

SAP/BI Manual 28 | P a g e .

SAP/BI Manual 29 | P a g e .

SAP/BI Manual 30 | P a g e .

SAP/BI Manual 31 | P a g e .

SAP/BI Manual 32 | P a g e .

SAP/BI Manual 33 | P a g e .

SAP/BI Manual

34 | P a g e

SAP/BI Manual

35 | P a g e

SAP/BI Manual

36 | P a g e

SAP/BI Manual 37 | P a g e .

SAP/BI Manual 38 | P a g e .

SAP/BI Manual 39 | P a g e .

SAP/BI Manual 40 | P a g e .

SAP/BI Manual 41 | P a g e .

SAP/BI Manual 42 | P a g e .

SAP/BI Manual 43 | P a g e .

SAP/BI Manual 44 | P a g e .

SAP/BI Manual 45 | P a g e .

SAP/BI Manual 46 | P a g e .

SAP/BI Manual 47 | P a g e .

SAP/BI Manual 48 | P a g e .

SAP/BI Manual 49 | P a g e .

SAP/BI Manual 50 | P a g e .

SAP/BI Manual 51 | P a g e .

SAP/BI Manual 52 | P a g e .

SAP/BI Manual 53 | P a g e .

SAP/BI Manual 54 | P a g e .

SAP/BI Manual 55 | P a g e .

SAP/BI Manual 56 | P a g e .

SAP/BI Manual 57 | P a g e .

SAP/BI Manual 58 | P a g e .

SAP/BI Manual 59 | P a g e .

SAP/BI Manual 60 | P a g e .

SAP/BI Manual 61 | P a g e .

SAP/BI Manual 62 | P a g e .

SAP/BI Manual 63 | P a g e .

SAP/BI Manual 64 | P a g e .

SAP/BI Manual 65 | P a g e .

SAP/BI Manual 66 | P a g e .

SAP/BI Manual 67 | P a g e .

SAP/BI Manual 68 | P a g e .

SAP/BI Manual 69 | P a g e .

SAP/BI Manual 70 | P a g e .

SAP/BI Manual 71 | P a g e .

SAP/BI Manual 72 | P a g e .

SAP/BI Manual 73 | P a g e .

SAP/BI Manual 74 | P a g e .