SAP BI Data Warehousing Workbench - Modeling

SAP/BI Manual

A Document Covers:

To enter into the Data Warehousing Workbench : Modeling

B T-Code

RSA1

C 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

PurposeThe 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 a g e

SAP/BI Manual

Structure of the Data Warehousing Workbench

The following figure shows the structure of the Data Warehousing Workbench

2 | P a g e

Navigation Window with functional areas

Status Bar

Views & Applications of single functional area

Menu BarApplication Toolbar

SAP/BI Manual

Modeling  

PurposeThe 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 FlowThe 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 SourceA 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 a g e

SAP/BI Manual

The Persistent Staging Area (PSA) in the BI system is the inbound storage area for data from the source systems. The requested data is saved, unchanged from the source system.

PurposeThe Persistent Staging Area (PSA) is the inbound storage area in BI for data from the source systems. The requested data is saved, unchanged from the source system.

Request data is stored in the transfer structure format in transparent, relational database tables in BI. The data format remains unchanged, meaning that no summarization or transformations take place, as is the case with InfoCubes.

The transformation specifies how the data (key figures, time characteristics, characteristics) is updated and transformed from the source, into an InfoProvider or InfoSource. The transformation rules map the fields of the source to at least one InfoObject in the target. The information is mapped in structured form using the InfoObjects.

UseThe transformation process allows you to consolidate, cleanse, and integrate data. You can semantically synchronize data from heterogeneous sources.When you load data from one BI object into a further BI object, the data is passed through a transformation. A transformation converts the fields of the source into the format of the target.

InfoObject  

DefinitionBusiness evaluation objects are known in BI as InfoObjects. They are divide into characteristics (for example, customers), key figures (for example, revenue), units (for example, currency, amount unit), time characteristics (for example, fiscal year) and technical characteristics (for example, request number).

UseInfoObjects are the smallest units of BI. Using InfoObjects, information is mapped in a structured form. This is required for constructing InfoProviders.

InfoObjects with attributes or texts can themselves also be InfoProviders (if in a query).

StructureCharacteristics are sorting keys, such as company code, product, customer group, fiscal year, period, or region. They specify classification options for the dataset and are therefore reference objects for the key figures.

In the InfoCube, for example, characteristics are stored in dimensions. These dimensions are linked by dimension IDs to the key figures in the fact table. The characteristics determine the granularity (the degree of detail) at which the key figures are kept in the InfoCube.

4 | P a g e

SAP/BI Manual

In general, an InfoProvider contains only a sub-quantity of the characteristic values from the master data table. The master data includes the permitted values for a characteristic. These are known as the characteristic values.

The key figures provide the values that are reported on in a query. Key figures can be quantity, amount, or number of items. They form the data part of an InfoProvider.

Units are also required so that the values for the key figures have meanings. Key figures of type amount are always assigned a currency key and key figures of type quantity also receive a unit of measurement.

Time characteristics are characteristics such as date, fiscal year, and so on.

Technical characteristics have only one organizational meaning within BI. An example of this is the request number in the InfoCube, which is obtained as ID when loading requests. It helps you to find the request again.

InfoProviders  

DefinitionGeneric term for BI objects into which data is loaded or that display views of data. You analyze this data in BEx queries.

5 | P a g e

SAP/BI Manual

UseInfoProviders are different metaobjects in the data basis that can be seen within query definition as uniform data providers. Their data can be analyzed in a uniform way. 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. However, in the BEx Query Designer, they are seen as uniform objects.

The term InfoProvider encompasses objects that physically contain data:

InfoArea

InfoCubes

DefinitionAn object that can function as both a data target and an InfoProvider.From a reporting point of view, an InfoCube describes a self-contained dataset, for example, of a business-orientated area. This dataset can be evaluated in a BEx query.

6 | P a g e

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.

UseInfoCubes are supplied with data from one or more InfoSources or ODS objects (Basic InfoCube) or with data from a different system (RemoteCube, SAP RemoteCube, virtual InfoCube with Services, transactional InfoCube).

DataStore Object  

DefinitionA 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.

Unlike multidimensional data storage using InfoCubes, the data in DataStore objects is stored in transparent, flat database tables. The system does not create fact tables or dimension tables.

InfoObjects as InfoProviders

DefinitionYou can flag an InfoObject of type characteristic as an InfoProvider if it has attributes. In the InfoObject maintenance on the Master Data/Texts tab page, you set the With Master Data indicator .

The data is then loaded into the master data tables using the transformation rules.

UseYou can define transformation rules for the characteristic and use them to load attributes and texts. It is not yet possible to use transformation rules to load hierarchies.

You can also define queries for the characteristic (more exactly: for the master data of the characteristic) and then report using the master data.

In InfoObject maintenance, 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. Select Navigation Attribute InfoProvider. A dialog box appears in which you can set indicators for individual navigation attributes. These are then available like normal characteristics in the query definition.

7 | P a g e

SAP/BI Manual

IntegrationIf you want to use a characteristic as an InfoProvider, you have to assign an InfoArea to the characteristic. The characteristic is subsequently displayed in the InfoProvider tree in the Data Warehousing Workbench.

 Staging is used to load data into these InfoProviders.

InfoProviders can also be objects that do not physically store data but which display logical views of data, 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). A time-dependent join or temporal join is a join that contains an InfoObject that is a time-dependent characteristic.

An InfoSet is a semantic layer over the data sources and is not itself a data target.

Unlike the classic InfoSet, and InfoSet is a BW-specific view of data.

Use

In the BEx Query Designer you compile reports (queries) about activated InfoSets.

InfoSets allow you to report on several InfoProviders by using combinations of master data-bearing characteristics and ODS objects. The information is collected from the tables of the relevant InfoProviders. When an InfoSet is made up of several characteristics, you are able to map transitive attributes and report on this master data.

You create an InfoSet using the characteristics Business Partner (0BPARTNER) – Vendor (0VENDOR) – Business Name (0DBBUSNAME), and can then use the master data for reporting.

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, or objects of different object types. The individual objects can appear in a join any number of times. Join conditions connect the objects in a join to one another (equal join-condition). A join condition determines the combination of records from the individual objects that are included in the resulting set.

8 | P a g e

SAP/BI Manual

Integration

InfoSet Maintenance in the Administrator Workbench

You create and edit InfoSets in the InfoSet Builder. See Creating InfoSets and Editing InfoSets.

Reports using InfoSets

The BEx Query Designer supports the tabular (flat) display of queries. Use the Table Display pushbutton to activate this function.

For every InfoProvider that is included in a join there are two dimensions (key and attribute) in the BEx Query Designer. These dimensions contain the fields and attributes for the selected InfoSet.

MultiProviders  

DefinitionA MultiProvider is a type of InfoProvider that combines data from a number of InfoProviders and makes it available for reporting purposes. The MultiProvider does not itself contain any data. Its data comes entirely from the InfoProviders on which it is based. These InfoProviders are connected to one another by a union operation.

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

UseA MultiProvider allows you to run reports using several InfoProviders.

InfoCube and InfoCube: You have an InfoProvider with actual data for a logically closed business area and an equivalent InfoProvider with planned data. You can combine the two InfoProviders into one MultiProvider so that you can compare the actual data with the planned data in a query. In BW releases 2.0B/2.1C, this combination of two InfoCubes is still called a MultiCube.InfoCube and InfoObject: You have an InfoCube with your products and sales. You combine this InfoCube with the 0MATERIAL InfoObject. This allows you to display any "slow-moving items", since products that do not result in sales are also displayed. For a detailed description of the procedure, refer to the Slow Moving Items Scenario.

StructureA MultiProvider can consist of different combinations of the following InfoProviders: InfoCube, ODS object, InfoObject, and InfoSet.

9 | P a g e

SAP/BI Manual

A union operation is used to combine the data from these objects into a MultiProvider. Here, the system constructs the union set of the data sets involved. In other words, all values of these data sets are combined. As a comparison: InfoSets are created using joins. These joins only combine values that appear in both tables. In contrast to a union, joins form the intersection of the tables

Aggregation Level  

UseAggregation levels are used as InfoProviders for planning: with an aggregation level, you model levels whose data can be changed manually using input-ready queries or automatically using planning functions.

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.

In the simplest case, an aggregation level is located on a real-time enabled InfoCube. 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, see Simple Aggregation Level.

Aggregation levels can also be created on MultiProviders.

IntegrationYou can create multiple aggregation levels for an InfoProvider. Use the Planning Modeler or the Planning Wizard for this.

In the Modeling functional area of the Data Warehousing Workbench, the system also displays the aggregation levels (symbol ) and the underlying InfoProviders in the

10 | P a g e

SAP/BI Manual

InfoProvider overview. When you double-click on the aggregation level, you can branch to the Planning Modeler and edit the selected aggregation level.

PrerequisitesIn the Planning Modeler or Planning Wizard you have selected (and if necessary edited) an InfoProvider to act as the basis of the aggregation level. This InfoProvider includes at least one real-time-enabled InfoCube. For more information about the corresponding processing step, see InfoProvider.

FeaturesSimple Aggregation Level

A real-time enabled InfoCube is the basis of a simple aggregation level. You can find a simple example under Simple Aggregation Level.

Complex Aggregation Level

A MultiProvider that includes at least one real-time enabled InfoCube, but no simple aggregation level, is the basis of a complex aggregation level.

Creating Aggregation Levels...       1.      To create an aggregation level, choose Create. The Create Aggregation Level dialog

box appears.        2.      Enter a technical name and a description.        3.      Choose the appropriate InfoProvider. If you do not enter a search term and choose

Start, the system shows all the InfoProviders available in your system.        4.      Choose Transfer. In the lower screen area of the Planning Modeler, the system

displays an overview of all InfoObjects of the InfoProvider.        5.      Choose the InfoObjects that are to be included in the aggregation level. Note the

conditions listed above.        6.      To save the definition of the aggregation level, choose Save.        7.      To check the definition of the aggregation level in view of consistency, choose

Check. When you choose Check, the system tries to complete necessary objects, such as superordinate characteristics from compounded characteristics.

       8.      If the definition is consistent, choose Activate. Once it has been activated, the aggregation level is ready for use.

Changing Aggregation Levels...       1.      To change an aggregation level, choose Change. In the lower screen area of the

Planning Modeler, the system displays an overview of all InfoObjects of the InfoProvider used in the aggregation level. The InfoObjects selection list allows you to display all

11 | P a g e

SAP/BI Manual

InfoObjects for the InfoProvider, only those used in the aggregation level, or those not used in the aggregation level.

       2.      Change the definition as required.        3.      Save, check and activate the changed definition.

The following figure gives an overview of the BI objects that can be used in analysis and reporting. They are divided into InfoProviders that contain data and InfoProviders that only display logical views and do not contain any data. In BEx, the system accesses an InfoProvider; it is not important how the data is modeled.

You need to use an InfoSource if you want to execute two transformations one after the other.

Subsequently, the data can be updated to further InfoProviders. The InfoProvider provides the data that is evaluated in queries. You can also distribute data to other systems using the open hub destination.

Data Flow

12 | P a g e

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

• Translation

13 | P a g e

SAP/BI Manual

– 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

15 | P a g e

To enter into Data Warehousing Workbench : Modeling

SAP/BI Manual

InfoArea name / Object name must be alphanumeric

16 | P a g e

Right Click on “Infoprovider” bar and choose option “Create Infoarea”

SAP/BI Manual

17 | P a g e

Type Infoarea – Alphanumeric

Space between two is not allowed to create Infoarea name (Technical Name)

SAP/BI Manual

18 | P a g e

New Infoarea Created

SAP/BI Manual

19 | P a g e

How to Create New Infocube?

1. Right Click on InfoArea (Test Project) & click on “Create Infocube” option

SAP/BI Manual

20 | P a g e

1. To enter the Technical Name & Description for the New Infocube

2. The Technical Name Should be Alphanumeric

SAP/BI Manual

21 | P a g e

Add Key Figures & Dimentions

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