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

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

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

From a reporting point of view. an InfoCube describes a self-contained dataset. of a business-orientated area. for example. Their data can be analyzed in a uniform way. This dataset can be evaluated in a BEx query. 6|P ag e . 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. However. in the BEx Query Designer. they are seen as uniform objects.SAP/BI Manual Use InfoProviders are different metaobjects in the data basis that can be seen within query definition as uniform data providers. 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.

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

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

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

In the simplest case. the system also displays the aggregation levels (symbol ) and the underlying InfoProviders in the 10 | P a g e . Use the Planning Modeler or the Planning Wizard for this. An aggregation level is set using a set of characteristics and key figures from the underlying InfoProvider. an aggregation level is located on a real-time enabled InfoCube. In other words. 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. In contrast to a union. Aggregation levels can also be created on MultiProviders. As a comparison: InfoSets are created using joins. joins form the intersection of the tables Aggregation Level Use Aggregation levels are used as InfoProviders for planning: with an aggregation level. Here. Integration You can create multiple aggregation levels for an InfoProvider. all values of these data sets are combined. These joins only combine values that appear in both tables. see Simple Aggregation Level. In the Modeling functional area of the Data Warehousing Workbench. The key figures included in the aggregation level are aggregated using the characteristics that are not included in the aggregation level. 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.SAP/BI Manual A union operation is used to combine the data from these objects into a MultiProvider.

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

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

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 Functions of the Datawarehousing Workbench ‡ Modeling ± ‡ Database objects and transformations are created Administration ± Load Scheduling.

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 .SAP/BI Manual 1. To enter the Technical Name & Description for the New Infocube 2.

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 .

Sign up to vote on this title
UsefulNot useful