BW200 Business Information Warehouse - Overview BW200. Release 20B

Transcription

1 BW200 Business Information Warehouse - Overview BW200 Release 20B

2 BW200 Business Information Warehouse - Overview Copyright SAP Business Information Warehouse (BW 2.0B/2.1C) Course Prerequisites Target Group Course Overview Course Goals Course Objectives Course Content Course Overview Diagram Main Business Scenario BW Overview BW - Overview: Unit Objectives Course Overview: BW - Overview BW - Overview: Business Scenario Information-Orientated Management SAP OLTP Reporting Toolbox OLTP versus OLAP SAP Business Information Warehouse mysap Business Applications BW and the Business Framework BW Strategy: An End-To-End Solution Architecture of the Business Information Warehouse Details of the BW Architecture Business Information Warehouse: An Open System Business Content Development The Advantages of Business Content mysap.com Workplace Starting Workbooks Starting Web Reports BW - Overview: Unit Summary Business Explorer Business Explorer: Unit Objectives Course Overview: Business Explorer Business Explorer: Business Scenario Business Explorer Components From InfoCube to Workbook BEx Browser: Overview Executing Queries in the BEx Analyzer Managing Queries in the BEx Browser Creating a Query Choosing Characteristics and Key Figures Changing a Query Schema: Exception Reporting BEx Map Drill-Through MultiCube Query Web Reporting: Characteristics Business Explorer: Unit Summary

3 Business Explorer - Exercises Business Explorer - Solutions Data Warehousing Data Warehousing: Unit Objectives Course Overview: Data Warehousing Data Warehousing: Business Scenario OLTP Structure SAP BW Data Model Example: Sales Star Schema SAP BW: Extended Star Schema Specific Characteristics of the BW Star Schema Extended BW Star Schema: Details Master Data and InfoCubes (1/2) Master Data and InfoCubes (2/2) MDM/Star Schema and BW Granularity of Data From Data Model to Database InfoCube InfoCube: Example InfoCube: Multi-Dimensional Analysis InfoCube: Characteristics and Key Figures Data Warehousing: Unit Summary Administrator Workbench Administrator Workbench: Unit Objectives Course Overview: Administrator Workbench Administrator Workbench: Business Scenario Administrator Workbench Source Systems InfoObjects in BW Scenario for a New InfoObject DataSources and InfoSources Transfer Rules and Update Rules Staging Engine Extraction from Several Sources Methods of Extraction Scheduler Monitor Additional Administrator Workbench Functions Administrator Workbench: Unit Summary Administrator Workbench - Exercises Administrator Workbench - Solutions Defining the User Environment Defining the User Environment: Unit Objectives Course Overview: Defining the User Environment Defining the User Environment: Business Scenario Different Types of Data Warehouse User Business Factors Examples of Supported Roles SAP's Role Concept: Example

4 Role Activities SAP's Role Concept: Overview Defining the User Environment: Unit Summary Conclusion Conclusion: Course Objectives Recommended Follow-up Activities Recommended Follow-up Courses (1) Recommended Follow-up Courses (2)

5 BW200 Business Information Warehouse - Overview Business Information Warehouse - Overview SAP AG 2001 SAP BW System Release 2.0B May 2001 Material number

6 Copyright Copyright 2001 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. All rights reserved. SAP AG 2001 Trademarks: Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, OS/2, DB2/6000, Parallel Sysplex, MVS/ESA, RS/6000, AIX, S/390, AS/400, OS/390, and OS/400 are registered trademarks of IBM Corporation. ORACLE is a registered trademark of ORACLE Corporation. INFORMIX -OnLine for SAP and INFORMIX Dynamic Server TM are registered trademarks of Informix Software Incorporated. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mysap.com Logo and mysap.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

7 SAP Business Information Warehouse (BW 2.0B/2.1C) Level 1 Level 3 BW200 1 day Business Information Warehouse (BW) - Overview BW210 5 Tage days Business Information Warehouse (BW) - - Warehouse Warehouse Management BW205 3 Tage days Business Information Warehouse (BW) (BW) - - Reporting Reporting BW207 2 Tage days Business Information Warehouse (BW) (BW) - - Reporting Management BW209 2 Tage days Business Information Warehouse (BW) (BW) - - Web Web Reporting Reporting Delta D20BW 3 Tage days Business Information Warehouse (BW) (BW) - - Delta Release zu Release BW220 3 Tage days Business Information Warehouse (BW) (BW) - - Extraction Extraktionsmechanismen Mechanisms in SAP im R/3SAP R/3 SAP AG 2001

8 Course Prerequisites It is recommended that participants in this course have: Basic knowledge of the SAP R/3 environment Basic knowledge of data warehousing concepts SAP AG 2001

9 Target Group Participants: Project managers and project team members responsible for implementing BW IT employees responsible for managing BW BW power users Duration: 1 Day SAP AG 2001 Notes to the user: These training materials are not teach-yourself programs. They compliment the course instructor's explanations. There is space under the slides for you to make your own notes.

10 Course Overview Contents: Course Goals Course Objectives Course Content Course Overview Diagram Main Business Scenario SAP AG 2001 (C) SAP AG BW

11 Course Goals This course provides you with an overview of the functions and technology in the SAP Business Information Warehouse (BW) basic knowledge of how BW works SAP AG 2001 (C) SAP AG BW

12 Course Objectives At the conclusion of this course, you will be able to: Use the key terminology in BW Name the main components of BW Define and execute a query Explain the SAP Data Warehousing strategy and the BW data structure Explain how data is transferred from a source system into BW Explain the most important functions of the Administrator Workbench SAP AG 2001 (C) SAP AG BW

13 Course Content Preface Unit 1 Course Overview Unit 5 Administrator Unit 2 BW - Overview Workbench Unit 3 Unit 4 Business Explorer Data Warehousing Unit 6 Unit 7 Definition of the User Environment Summary SAP AG 2001 (C) SAP AG BW

14 Course Overview Diagram Data Warehousing Business Explorer Admin. Workbench BW Overview Summary Definition of the User Environment SAP AG 2001 (C) SAP AG BW

15 Main Business Scenario Your company has already implemented SAP R/3. You use the reporting tools in the R/3 system for reporting and accessing information. There are also non-sap systems in your company. The reporting tools you use at the moment provide you with application-specific and system-specific information. You need a tool that enables you to report on data from all the available source systems throughout the company. SAP AG 2001 (C) SAP AG BW

16 BW Overview Contents Overview of the BW structure Overview of the SAP Data Warehousing Strategy Business Content Integration with mysap Workplace SAP AG 2001 (C) SAP AG BW

17 BW - Overview: Unit Objectives At the conclusion of this unit, you will be able to use the information-processing terms that are used in OLTP and BW systems name the key BW components explain how BW fits into the SAP Business Framework outline the data warehousing strategy at SAP explain what Business Content is, and give examples describe how BW is integrated with mysap Workplace SAP AG 2001 (C) SAP AG BW

18 Course Overview: BW - Overview Data Warehousing Business Explorer Admin. Workbench BW Overview Summary Definition of the User Environment SAP AG 2001 (C) SAP AG BW

19 BW - Overview: Business Scenario Your company is considering implementing BW to meet its demand for company-wide, cross-system reporting. You need a general overview of BW to help you decide whether BW fulfills your company's requirements. SAP AG 2001 (C) SAP AG BW

20 Information-Orientated Management How do we get from here to here? Data Information Knowledge Results Realizing business value from transaction data SAP AG 2001 Reporting systems of all kinds are common in today s enterprise environment. Many of these systems, however, are unable to provide the kind of information that you need to help you make complex decisions. Data warehouses, such as the SAP Business Information Warehouse (BW), provide the kind of decision-support system that is needed in today s business environment. (C) SAP AG BW

21 SAP OLTP Reporting Toolbox EIS Report Portfolio Information Systems Profitability Analysis Report Tree Special Ledger SAP Tools ABC Report Painter/Writer Key Fig. Key Fig. 1 Key Fig Charact. Key 1, Descr. 1 xxx xx Key 2, Descr. 2 Key n, Descr. n Others Sum xxx xx xxx xx xxx xx SAP Query X X ABAP Business APIs Tables, Fields Import/ Export RFC Openness SQL, ODBC Word, Excel... insight for SAP EIS SAP AG 2001 SAP has provided solutions for reporting and analysis for a long time. Up until now, these solutions focused on the needs of operational reporting. The requirements of strategic reporting were not fully met. The SAP Business Information Warehouse provides a complete solution for all types of reporting and decision-support. (C) SAP AG BW

22 OLTP versus OLAP Characteristics OLTP OLAP Primary Operation Level of Analysis Amount of Data per Transaction Type of Data Relevance of Data Data Updates Database Concept Number of Transactions/Users Time Frame Database Data Number of Tables per Transaction Type of Processing Update Low Very small Detailed Current Often Complex Many Point in time Normalized Several Well-defined Analyze High Very large Summary Current and historical Less frequent, only new data Simple Few Time period Denormalized Few Ad hoc SAP AG 2001 OLTP (Online Transaction Processing) refers to the type of data processing typically done in an R/3 system. The reporting requirements in this type of system vary greatly from those in an OLAP (Online Analytical Processing) environment. BW is an OLAP (Online Analytical Processing) system, providing users with data in a form that makes reporting possible across different systems and different applications. (C) SAP AG BW

23 SAP Business Information Warehouse Data Warehouse system with optimized structures for reporting and analysis OLAP engine and tools Integrated Metadata Repository Data extraction and data staging in OLTP Preconfigured support for data sources from R/3 systems BAPIs for data sources from non-sap systems Automated Data Warehouse Management Administrator Workbench for controlling and managing SAP AG 2001 Against this background, SAP decided to develop its own data warehouse solution, an independent business component combining all the different reporting tasks, with a separate server, and its own database and SAP system. This solution is the SAP Business Information Warehouse. All of the requirements and objectives mentioned so far have been met in the conception and architecture of the SAP Business Information Warehouse. A decisive advantage of the SAP Business Information Warehouse is the fact that all of SAP's business know-how, gathered from over 25 years of software development in the commercial sector, has been applied in developing the Metadata Repository in the Business Information Warehouse. SAP R/3 systems can be configured as OLTP systems and supply the SAP Business Information Warehouse with the entire SAP Business Content. We are going to look at this particular aspect in greater detail later on in this course. (C) SAP AG BW

24 mysap Business Applications SAP Customer Relationship Management Initiative SAP Sales SAP Marketing Mobile Sales SAP Service R/3 Knowledge Mobile Service Warehouse Business-to-Business SAP SAP SAP Strategic Procurement To Business Business Strategic Enterprise Info Business Warehouse Management Management Initiative SAP Supply Chain Enterprise Management Information Management WarehouseSAP Logistics SAP Business SAP Logistics Execution Intelligence Initiative Knowledge Advanced Execution System System Management Management Planner& Optimizer Advanced Cockpit Corporate Planner & Optimizer Finance Management SAP AG 2001 The SAP Business Information Warehouse has a central position among the mysap solutions. Typical characteristics of the individual solutions are separate development, implementation, and maintenance of the components, and independent release cycles in the different areas. BAPI and ALE technology takes care of communication between these various systems. The advantages of this architecture include quicker implementation, flexibility, openness, and extendability. (C) SAP AG BW

25 BW and the Business Framework Non-SAP System Business Explorer - separate shipment - separate release cycle - separate maintenance - available as from R/3 3.1I Business Information Warehouse Server Preconfigured with SAP businessprocess know-how Data Sources SAP CRM SAP APO SAP SCM SAP SEM... R/3 R/2 External Sources SAP AG 2001 The SAP Business Framework Architecture has been developed to meet the demands made of a modern data warehouse solution. It is under this motto that SAP has recently transformed its R/3 System into a family of software components. Considerations such as how to implement new functions more quickly, flexibility, openness, enhanceability, and so on, form the basis of this strategy. Tried and tested ALE and BAPI technology in the SAP system provides the technical background for the componentization of business standard-software. SAP uses Application Link Enabling (ALE) and SAP Business Workflow to guarantee the integration of the whole system. This enables business processes to function across different components. (C) SAP AG BW

26 BW Strategy: An End-To-End Solution Common Metadata Enterprise-Wide Information Distribution Information Presentation Information Analysis Data Modeling Extraction, Transformation, and Loading Report Repository Role-Based Web Access Authorization MS Office Integration End-User and Analysis Tools Workbooks OLAP Dynamic Hierarchies Currency Conversion Aggregates External Hierarchies Realignment Time-Dependency Extraction from Various Source Systems Full-Updates and Deltas Automation & Monitoring Available 24 x 7 SAP AG 2001 BW is a complete data warehouse solution, from the extraction of data from various source systems, to providing a set of tools for analyzing and displaying the data. (C) SAP AG BW

27 Architecture of the Business Information Warehouse Business Explorer Web Reporting Third-Party Tools Client BAPI Administrator Workbench Metadata Repository OLAP Processor Staging Engine BAPI InfoCubes ODS PSA Business Information Warehouse Server Data Sources SAP AG 2001 BW has a multi-level architecture to provide the maximum degree of flexibility. BW can extract and use data provided by a variety of sources. These include R/3 and R/2 systems, non-sap systems, flat files, commercial data providers, and even other BW systems. The BW server provides all the tools necessary to model, extract, transform, aggregate, store, and access data. Since the description of the data, regardless of its source, is contained in a common Metadata Repository, data from a variety of sources can be combined to give you enhanced data analysis options. BW users can access data through the SAP Business Explorer, a standard Web Browser, or third-party display tools, which have been certified for use with a common BAPI interface. (C) SAP AG BW

28 Details of the BW Architecture Web Browser SAP Internet Transaction Server Administrator Workbench Manage Schedule Monitor Web Design Tool BDS Business Document Service Publish Views Save HTML Templates Metadata Repository BW WEBService Business Explorer Browser Metadata Manager BEx Analyzer (using MS Excel) OLAP Processor Data Manager Staging Engine BAPI Business Explorer Non-SAP OLAP Client ODBO BW Server InfoCubes Operational Data Store Non-SAP Production Data Extractor Non-SAP OLTP Applications Production Data Extractor OLTP Reporting R/3 OLTP Applications SAP AG 2001 This graphic gives a more detailed view of the BW architecture. For R/3 source systems, SAP provides a range of extractors that make it easier to use data from R/3. For non-sap systems, customers can either develop their own extractor programs, or use one of the certified third-party tools available. Sources of data can be legacy systems, R/3 systems, R/2 systems, flat files, 3rd party systems, or other BW systems. On the BW server, data is stored in one or more InfoCubes. In addition, the operational data store, or ODS, can be used to store the transaction-level data. The Business Explorer consists of two tools; the Business Explorer Analyzer that is used to create and execute queries, and the Business Explorer Browser that is used to display existing reports. Third-party presentation tools can also be used. Queries can also be accessed using a Web browser. (C) SAP AG BW

29 Business Information Warehouse: An Open System Data Extraction & Transformation Informatica, ETI, ETI, TSI, TSI, Informix, Systemfabrik, Information Builders, Acta Technology, Hummingbird, WRQ, Ascential Software, SeeBeyond Frontend Business Objects, Arcplan, Cognos, Seagate Software, BRIO, Comshare, Viador, MIS MIS Technologies, IntelliCube, PointOut, Ton Beller Data Providers AC AC Nielsen Dun & Bradstreet Other projectspecific providers SAP AG 2001 BW has an open architecture that allows you to use tools from other providers for extracting data and reporting. These 3rd-party tools are certified by SAP. Data from providers such as Dun & Bradstreet or A.C. Nielsen can be used in BW. (C) SAP AG BW

30 Business Content Development Business Content Roles Workbooks Queries InfoCubes Extractors, InfoSources Forecast: Analytical Applications Cross-component applications for analyzing and influencing processes in all systems that deliver data InfoObjects ca CRM Analysis SCM Analysis. 800 Enterprise Analysis and many more... SAP AG 2001 Business Content contains numerous objects that simplify the implementation of BW and accelerate the construction of an effective reporting system. These objects are grouped together to enable you to use them effectively: For all areas of your company and for many industry sectors, there are roles that provide users with the relevant reports and applications that they need to perform their tasks. In the future, cross-component applications called Analytical Applications will be available to provide direct access to all the information related to a process. They allow you not only to analyze these process, but also trigger actions and reactions in the systems that deliver data. Areas particularly suitable for the implementation of Analytical Applications are, for example, Supply Chain Management (for example, supplier and catalog analysis, manufacturing analysis), Customer Relationship Management (for example, e-business analysis, market exploration) or analyses within the company, such as performance analysis, payment analysis, or human capital analysis. (C) SAP AG BW

31 The Advantages of Business Content Faster and Lower-Cost Implementations Low Cost of Ownership Consistent Definitions and Data System-Openness Flexibility SAP AG 2001 Business Content enables customers to implement BW more quickly and more costeffectively. Business Content provides you with a data model that helps you implement your BW, and also benefit from other customers' experience. (C) SAP AG BW

32 mysap.com Workplace Web Browser Access Single Signon Workplace Industry-Specific Cock- Role-Based pits Personalized Drag & Relate Open Internet Standards R/2 3rd Party FI CFM Legacy System Non-SAP 3.1H R/3 4.6 LO HR KM APO B2B mysap Applications CRM BW SEM Marketplace Partner Enterprise Boundary within outside Other Internet Services SAP mysap Internet Services SAP AG 2001 When a user logs on to mysap.com Workplace, he or she has access to a variety of applications, including R/3 systems, legacy systems, and mysap.com components, such as BW, all of which are related to his or her role in the company. Users also have access to various Internet services. (C) SAP AG BW

33 Starting Workbooks Excel Add-In Functions Available Start Excel SAP AG 2001 A user accesses workbooks from his or her workplace (reports are assigned to a role). Simply clicking on the workbook launches Excel. All the standard query-navigation functions are available. (C) SAP AG BW

34 Starting Web Reports BW Web Report Start Report SAP AG 2001 Web reports can be executed directly from the launch pad by integrating the URL for the report directly into the user s role. An unlimited number of Web reports can be added to the user s role. The URL for a Web report can also be included in a role as a MiniApp, or defined as an item in an Internet page. Current data is selected by the OLAP processor upon execution. A user's authorizations are checked at this point. You are able to navigate in the Web report if the type of Web report you have selected includes a navigation toolbar or drilldown table items. (C) SAP AG BW

35 BW - Overview: Unit Summary You are now able to: Use the information processing terms that are used in OLTP and BW systems Name the key BW components Explain how BW fits into the SAP Business Framework Outline the Data Warehousing Strategy at SAP Explain what Business Content is, and give examples Describe how BW is integrated with mysap Workplace SAP AG 2001 (C) SAP AG BW

36 Business Explorer Contents: BEx Browser BEx Analyzer SAP AG 2001 (C) SAP AG BW

37 Business Explorer: Unit Objectives At the conclusion of this unit, you will be able to List the key functions of the BEx Browser List the key functions of the BEx Analyzer Explain the link between BW and Microsoft Excel Define and execute a query in the BEx Analyzer Execute and manage queries using the BEx Browser SAP AG 2001 (C) SAP AG BW

38 Course Overview: Business Explorer Data Warehousing Business Explorer Admin. Workbench BW Overview Conclusion Definition of the User Environment SAP AG 2001 (C) SAP AG BW

39 Business Explorer: Business Scenario You require detailed information about the functions of the BEx Analyzer, in order to check whether it meets your company's reporting needs. You want to familiarize yourself with the functions of the BEx Browser, which the BW user is to use to execute and manage their reports. SAP AG 2001 (C) SAP AG BW

40 Business Explorer Components Business Explorer Query Definition Analyzer Browser MS Excel OLAP InfoCatalog Processor InfoCube Database Business Information Warehouse Server SAP AG 2001 The Business Explorer helps to analyze the data in the SAP Business Information Warehouse. In the Business Explorer Analyzer, you define queries that are based on a selection of InfoObjects or pre-defined query templates for an InfoCube. By navigating through queries, you generate various view of the data which enable you to analyze and present the InfoCube data. You save the queries in workbooks and can manage them in your favorites. The Business Explorer Browser allows you to manage and execute workbooks that are in your favorites folder, or that belong to one of the roles that you are assigned to. (C) SAP AG BW

41 FI A R Tra nsa c tio n da t a Key figur es Dim ensions Accumulated balance Total credi t postings Total debit posti ngs Sales volume in period Customer Sector Cust omer number Country Company c ode Cur rency type Tim e Unit SAP Business Explorer Customer num ber Company c ode Customer num ber Becker AG A.S.S Gesam tergebnis 4.000,75 Filter Fr e ie Mer k m a le Zeilen C o u n tr y Com pany c ode DE Debit... IDES AG Customers Customers Columns Structure Kumuli.... IDE S AG Accumulate d bala nce Kumuliert , ,25 From InfoCube to Workbook Business Explorer Query Definition... Analyzer presents and manipulates... View OLAP Processor determines... Application Server Query Definition Database Server InfoCube Data SAP AG 2001 You analyze the database in the Business Information Warehouse, by defining queries for InfoCubes. If you imagine the InfoCube as a multi-dimensional cube, when you select characteristics and key figures in a query, a smaller cube is cut out of the larger InfoCube. The multi-dimensional structure of the query data enables you to generate various views of the data in an InfoCube. The OLAP processor creates the queries from the InfoCube data and provides methods for navigation within this data. The Business Explorer requests the data that you want for the query and presents the current view of the saved data. Only data which is actually required is transferred. If you want a new data view in the Business Explorer, the OLAP processor calls up the data from the InfoCube while you are navigating through the data. (C) SAP AG BW

42 BEx Browser: Overview The Business Explorer Browser allows access to all document types in the Business Information Warehouse that are assigned to the user's role or that are stored in the favorites. You can: Select and open documents that are assigned to you. Store and manage new documents in the BEx Browser. SAP AG 2001 Use the BEx Browser to access all types of documents that have been assigned to you in the role maintenance, or that you saved in your favorites. The administration of the document types displayed in the BEx Browser is based on the role maintenance (activity group maintenance) in the SAP Easy Access Menu. This is where you create new roles, assign them users, and maintain authorizations. You can select and organize documents in the BEx Browser. You can also create folders and specify how you want them presented on the screen regarding their position and any graphics used. You can maintain your favorites and add new folders and objects. Alternatively, you can maintain your favorites in the SAP Easy Access Menu in BW. The objects are displayed in a tree. (C) SAP AG BW

43 Executing Queries in the BEx Analyzer SAP BEx: Open 1 2 workbooks Queries Queries Description Profit Center Accounting Project System Quality Management Travel Management Purchasing Profitability Analysis Sales and Distribution OK Cancel New Change 4 Exceptions Sales and Distribution Customers Deliveries Description Find 3 Technical name SAP AG 2001 You can find the query definition you selected under Query in the BEx Analyzer, assigned to the corresponding InfoArea and InfoCube. A search function helps you to find the query quickly. You can either enter the description or the technical name of the query. When you find the query, select it with the mouse and confirm with OK. If the InfoCube contains data, the query result is shown on an Excel worksheet. (C) SAP AG BW

44 Managing Queries in the BEx Browser Create a folder in the BEx Browser B3T, SCHMITTA 1 2 SAP BEx Analyzer Save Execute a query in the BEx Analyzer, and save it in the folder you created SAP AG Start the query from the BEx Browser by clicking with the mouse If you want to save the query in a new favorites folder, proceed as follows: Open the 'Favorites' folder in the tree structure of the BEx Browser. Place the cursor on the right side of the screen and create a new folder (right mouse-click - New -> Folder. Give it an appropriate name and specify how you want it presented by choosing Select Color and Symbol. Open the BEx Analyzer and execute the selected query. Save the workbook by choosing Save -> Save as new workbook. Enter a name for the query and select the folder you created in your favorites. Confirm with OK. When you call the BEx Browser you see the name of the query in your new folder, as long as your favorites are open. Double-click on the name to start the query. (C) SAP AG BW

45 Creating a Query SAP BEx: Open Queries 1 Workbooks Description Production Planning and Control Product Cost Controlling Profit Center Accounting OK Cancel 2 Queries Quality Management Quality Cockpit Travel Management Sales and Distribution New Change 3 Exceptions Sales and Distribution: Overview Customers Description Find Technical Name Technical Name SAP AG 2001 Procedure for creating a new query: Choose the New icon in the toolbar. Choose the pushbutton Queries. Choose pushbutton New. This brings you to the selection screen containing all of the InfoCubes for which you can define a new query. Select the InfoCube on whose data you want the query to be based, by selecting it with the mouse. You can see the technical name of the InfoCube by choosing Technical Name (wrench icon). To create the query, choose New. (C) SAP AG BW

46 Choosing Characteristics and Key Figures Save Query New Query SAP DemoCube Sales Filter Execute Query Key Figures Accumulated Balance Total Credit Postings Total Debit Postings Sales Volume in Period Dimensions Customer Industry Customer Number Country Company Code Currency Type Time Unit Free Characteristics Rows Debit... Columns Structure Accumul. Bal. Accumul. Customers Customers SAP AG 2001 The objects available for the InfoCube you have selected are shown as a tree structure in the left-hand part of the query definition screen. These objects include the key figures and characteristics of the dimensions. The right-hand part contains empty directories for filter selections, rows, columns, and the free characteristics of the query. The bottom right-hand part of the screen shows a preview of the query result area. This area is empty at first. By clicking the plus or minus symbol for the directories, you can expand or compress the directory structure. By expanding the key figure node in the InfoCube tree, for example, you can display a list of all the key figures for the InfoCube. You can drag the characteristics and key figures for the InfoCube into the directories for the query definition (filter, rows, columns, free characteristics). When you have finished defining your query, choose Save Query. Choose Enter (checkmark icon) to start working with the query. (C) SAP AG BW

47 Changing a Query Change Query (local view) Change Query (local view) Filter Free Characteristics Columns 1 Rows Debit... Customers Customers Structure Accumulated Balance Accumul. SAP BEx Analyzer Customer Number Customer Number Change query (global definition) Accumulated Balance Becker Inc. 1, Hitech Inc. 2, A.S.S 3, Total 6, Change Query (global definition) SAP DemoCube Sales Key Figures Accumulated Balance Total Credit Postings Total Debit Postings Sales Volume in Period Dimensions Customer Industry Customer Number Country Company Code Currency Type Time Unit Filter Free Characteristics Rows Debit... Columns Customers Customers Structure 2 Accumulated Balance Accumul. SAP AG 2001 Choose Change Query to modify the query. There are two options for changing the query: Choose the mode Change Query (local view) to easily move or restrict the objects that are already in the query definition. The worksheet is refreshed each time you execute the query, but the changes are not saved in the query definition. Choose Change Query (global definition) to return to the definition screen, where you can use the same functions you could use when you first defined the query. Before executing the changed query, save the changes in the query definition. This applies the changes to the original query definition. There are two ways of saving the changed query: You can save the changed query under its previous name. To do this, choose Save Query in the toolbar. You can save the changed query under a new name. To do this, choose Save Query as... in the toolbar. Enter a new technical name and a new description. You can change this description at any time. (C) SAP AG BW

48 Schema: Exception Reporting BEx Analyzer Different Views Exception Definition Alert Monitor on the Web Query Definition Alert Monitor Frontend Reporting Agent Report Agent Settings SAP Office Mail (or ) SAP AG 2001 Batch Printing BW Server There are three types of exception reporting: The evaluation of exceptions online when you execute a query. The evaluation of exceptions in the background. And the Alert Monitor (notifies you that exceptions have occurred). (C) SAP AG BW

49 BEx Map Visualization... subsidiaries, plants, warehouses, stores Geographical Aggregation... by region, country, state, county, city, store Geographical Analysis... interrelating customers with stores... demographics: for example, real vs. potential customers SAP AG 2001 SAP has developed a geographical information system for BW: the BEx Map. With it, you can display query data on a designated map. BEx Map is fully integrated in the BEx Analyzer; the user can call up BEx Map for every query that contains geo-relevant characteristics. BW customers receive maps, on which they can display query results immediately after completing a few simple maintenance activities. (C) SAP AG BW

50 Drill-Through Drill-Through Options: From the result of a BEx query to the result of a query about Business Explorer an InfoCube ODBO an ODS object Metadata Repository OLAP Processor InfoCubes an InfoSet or BW Server ODS a transaction in the source system R/3 Operative Data SAP AG 2001 Using the report/report interface you can jump from one BEx query to another query or transaction, to gain additional information for your query result. The contents of the query result cells, from which you start navigating, function as a filter. You have the following drill-through options: From a BEx query to a BEx query using an InfoCube From a BEx query to a BEx query using an ODS object From a BEx query to an InfoSet query From a BEx query to a transaction in a source system (C) SAP AG BW

51 MultiCube Query MultiCube Plan data by product group Sales by product SAP AG 2001 A MultiCube is a virtual InfoCube that contains no data itself, but that accesses data from other InfoCubes that are specified when the MultiCube is created. You can put different InfoCubes together in one MultiCube, as long as they have at least one common key field. You can use the same reporting functions for the MultiCube as for a Basis InfoCube. (C) SAP AG BW

52 Web Reporting: Characteristics Publishing Workbooks on the Web Predefined navigation using buttons or drop-down menus Various display options: For example, diagrams, tables, tachometers Free arrangement of display objects Thin Client - Low Administration Expense Pure HTML solution Suitable for any Web browser User-Friendly Designed for users of reports Seamless Integration of the Web Publishing Environment with the BEx Analyzer Using the SAP Internet Transaction Server (scalability, security, integration...) SAP AG 2001 As we have already seen, it is possible to execute queries on the Web. You can call up the queries with any browser you want to use. (C) SAP AG BW

53 Business Explorer: Unit Summary You are now able to: List the key functions of the BEx Browser List the key functions of the BEx Analyzer Explain the link between BW and Microsoft Excel Define and execute a query in the BEx Analyzer Execute and manage queries using the BEx Browser SAP AG 2001 (C) SAP AG BW

54 Business Explorer - Exercises Unit: Business Explorer Topic: Creating and Executing Queries At the conclusion of this exercise, you will be able to: Create queries in the BEx Analyzer Manage queries in the BEx Browser and start them from there. Your organization s personnel department needs queries that deliver personnel administration information. Create these queries in the BEx Analyzer and store them in your Favorites folder in the BEx Browser, so that you can start them from there. 1-1 Create a query using the cube Headcount and Personnel Action (0PA_C01), which gives you information on the number of male and female employees in the personnel department Create the query in the BEx Analyzer, save it under the technical name BW200_GR##_Q1 and the description GR## Personnel Admin. Q1. Execute the query Save the query in the BEx Browser Favorites folder. 1-2 Create a second query using the same InfoCube. This query has to provide information on the age of employees in the personnel department Create the query in the BEx Analyzer, save it under the technical name BW200_GR##_Q2 and the description GR## Personnel Admin. Q2. Execute the query Check the query result in the workbook. You now want to display only the employees of the personnel department in Philadelphia Save this query view in the BEx Browser Favorites folder. 1-3 Open the BEx Browser and execute the query you created - GR## Personnel Admin. Q2 - from the Favorites folder. What do you notice? (C) SAP AG BW

55 Business Explorer - Solutions Unit: Business Explorer Topic: Creating and Executing Queries At the conclusion of this exercise, you will be able to: Create queries in the BEx Analyzer Manage queries in the BEx Browser and start them from there. 1-1 Create a query using the cube Headcount and Personnel Actions (0PA_C01), which gives you information on the number of male and female employees in the personnel department Create the query in the BEx Analyzer, save it under the technical name BW200_GR##_Q1 and the description GR## Personnel Admin. (## is your group number). Execute the query. Open the BEx Analyzer. You may need to log on again. Open Queries New Human Resources Personnel Management Personnel Administration Headcount and Personnel Actions (0PCA_C01) OK Key Figure Number of Employees Drag and drop into columns Characteristic Personnel Area (from the Personnel Area dimension) and Gender (from the Personal Data dimension) Drag and drop into the rows. Save Technical Name BW200_GR##Q1 ; description: GR## Personnel Admin. Q1 Choose OK Execute Save the query in the BEx Browser Favorites folder. After you have executed the query, choose Save as new workbook Select the Favorites folder Description: GR## Personnel Admin. Q1. Choose OK 1-2 Create a second query using the same InfoCube. This query has to provide information on the age of employees in the personnel department Create the query in the BEx Analyzer, save it under the technical name BW200_GR##_Q2 and the description GR## Personnel Admin. Execute the query. Open the BEx Analyzer. Open Queries New Human Resources Personnel Management Personnel Administration Headcount and Personnel Actions (0PCA_C01) OK (C) SAP AG BW

56 Key Figure Age (years) Drag and drop into columns Characteristic Personnel Area (from the Personnel Area dimension) and Employees (from the Employees dimension) Drag and drop into the rows. Save Technical Name BW200_GR##Q2 ; description: GR## Personneladmin. Q2. Choose OK Execute Check the query result in the workbook. You now want to display only the employees of the personnel department in Philadelphia. Right mouse-click on the characteristic Personnel area in the filter cells area Select filter value Select fixed value Philadelphia and, using the arrow key, or with drag and drop, drag the value into the Selection field OK Save this query view in the BEx Browser Favorites folder. After you have executed the query, choose Save as new workbook Select the Favorites folder Description: GR## Personnel Admin. Q2 Choose OK 1-3 Open the BEx Browser and execute the query you created - GR## Personneladmin. 2 - from the Favorites folder. What do you notice? SAP Business Explorer SAP Business Explorer Browser (Log In)Open Favorites folder Start the report by double clicking on the query name. The query result is restricted to employees from Philadelphia, since it is saved in this form in the favorites. (C) SAP AG BW

57 Data Warehousing Contents: Data Warehousing Concept Star Schema InfoCube Components SAP AG 2001 (C) SAP AG BW

58 Data Warehousing: Unit Objectives At the conclusion of this unit, you will be able to: List the main differences between the structure of data in an R/3 system and in a BW Explain what a star schema is Evaluate the effect the InfoCube concept has on data granularity Name and give a definition of the InfoCube components SAP AG 2001 (C) SAP AG BW

59 Course Overview: Data Warehousing Data Warehousing Business Explorer Admin. Workbench BW Overview Conclusion Definition of the User Environment SAP AG 2001 (C) SAP AG BW

60 Data Warehousing: Business Scenario You need a comprehensive overview of the data model that is used in BW You want to know how this data model is converted into InfoCubes, so that you are in a position to assess the InfoCube concept itself SAP AG 2001 (C) SAP AG BW

61 OLTP Structure Inquiry Customer Master Sales Doc. Header Credit Check Delivery Header Transport Request Invoice Accounting Document Cost Center Quotation Sales Doc. Line Delivery Item Invoice Item A/t Sub Ledger General Ledger Sales document item Storage Locations Warehouse Management Special Ledger ATP Material Master Data Goods Movement A/t Sub Ledger Human Resource Management Payroll Stock Bills of Material Production Order Requirement Goods Movement SAP AG 2001 Purchase Order Delivery master Incoming Invoices Impact on Information Analysis? Many tables Complex relationships Each application different Detailed transaction data In transaction processing, we are constantly filling specialized tables that are optimized for displaying the thousands of different steps of our business processes. For example, sales and distribution document items flow in from sales documents and quotation documents. These become delivery header data, which then becomes invoice header data and is sent on as accounts receivable information. The tables in the Business Information Warehouse are different in that they do not process transactions. Instead, all information for a specific business process in BW is gathered together and analyzed. (C) SAP AG BW

62 SAP BW Data Model One business process is modeled at a time An extended star schema is the best method of storing data for reporting processes Characteristics are grouped into interconnected branches called dimensions. Key figures make up the facts. This structure is identical for all application areas. Dimension 2 Dimension 1 Dimension 3 Dimension n Facts Dimension 4 SAP AG 2001 Data that has been loaded into BW from various source systems, is stored in BW in the form of star schemas. This type of table assignment is ideal for reporting purposes. The dimensions answer question such as "Who?" "What?" and "When?" The facts provide answers to questions such as; how much money, how many people, how much did we pay? (C) SAP AG BW

63 Example: Sales Who did we sell to? What did we sell? Who sold it? Who were our competitors? When did we sell? Customer Dimension Product Dimension Quantities Revenue Costs Taxes Sales Dimension Time Dimension Competition Dimension SAP AG 2001 The graphic shows a star schema for the area Sales. The data in the star schema provides you with answers to a variety of questions about a process. (C) SAP AG BW

64 Star Schema The combination of fact tables and dimension tables is called a star schema Customer Dimension C Cust. No. Region West... P C T Quantity Revenue Discount Sales Overhead $ $ $ $ $ $... Fact Table P Product No. Product Group Screens... Product Dimension Z Period Fiscal Year Time Dimension SAP AG 2001 InfoCubes produce a multi-dimensional data model on the database server of the Business Information Warehouse. This allows the facts to be grouped in separate fact tables, and the dimensions to be grouped in separate dimension tables. Both types of table are interconnected. Individual dimension values can be subdivided further into master data tables. In this way, master data tables, text tables, hierarchy data tables, and dimension tables, are grouped in a star-like formation around one central fact table. This structure is called an extended star schema. In an analysis, the data from the smaller tables at the edge of the star schema, is collected together first, before the corresponding data in the fact table is accessed using the keys. Structuring information in a data warehouse according to this star schema guarantees the efficiency of the reporting process, and provides a flexible solution that can be easily adjusted to changing business requirements. When you create an InfoCube, you choose the key figures and characteristics that you are going to require in your analysis. You have to group your characteristics together in a time dimension, a unit dimension, and a number of other dimension categories. On the basis of your entries, the system generates a star schema on the database automatically. (C) SAP AG BW

65 SAP BW: Extended Star Schema Master Text Master Text Master Text SID Table Hierarchies SID Table Hierarchies Master Text SID Table Hierarchies SID Table Hierarchies Master SID Table Text Hierarchies Dimension Table Dimension Table FACT Dimension Table SID Table Master Hierarchies Text SID Table Hierarchies Dimension Table Dimension Table Master Text SID Table Master Hierarchies Text SID Table Hierarchies SID Table Hierarchies SID Table Master Hierarchies Text Master Text Master Text SAP AG 2001 The BW extended star schema differs from the classic star schema. The BW star schema is divided into a solution-dependent part (fact tables and dimension tables = InfoCube) and a solution-independent part (master data tables, text tables, and hierarchy tables) that is also used by other InfoCubes. (C) SAP AG BW

66 Specific Characteristics of the BW Star Schema There are no restrictions on where the characteristics appear in the dimension tables Every combination of characteristics is possible in a dimension table, regardless of the relationship between the nodes This is why there are no predefined paths of analysis (drilldown) with the exception of those for external hierarchies The location of characteristics in BW is determined by: Analysis requirements Space restrictions Performance SAP AG 2001 When designing the dimensions of an InfoCube, you must put a lot of thought into which characteristics you are going to use, and how you are going to arrange them in the dimension table. This is an important part of the data modeling process, since the choices you make here have a significant impact on the size, performance, and usability of the InfoCube data. (C) SAP AG BW

67 Extended BW Star Schema: Details SID Table Hierarchies Master Data Attributes Text Separate maintenance for: Loading master data Loading text data Loading hierarchy data SAP AG 2001 The attribute tables, hierarchy tables, and text tables are not included in the InfoCube. This means that this data is maintained separately, and can be used across different InfoCubes. (C) SAP AG BW

68 Master Data and InfoCubes (1/2) Customer Dimension Sold to: Customer number Ship to: Customer No. Customer name Customer category Customer sub-category Division Industry Revenue class Transportation zone Currency VAT No. Legal status Regional market Cust. stats. group IncoTerms Billing schedule Price group Delivering plant ABC classification Account assignment group Address State Country Region Customer Dimension Sold to: Customer number Ship to: Customer No. Cust. stats. group IncoTerms Billing schedule Price group Delivering plant ABC classification Account assignment group Sold To Customer Attributes Sold to: Customer number Customer name Cust. Category Cust. Subcategory Division Industry Revenue Class Transportation zone Currency VAT # Legal Status Regional market Address State Country Region SAP AG 2001 Attributes are fields that describe an InfoObject. These attributes are used to display additional information within a workbook to make the results more meaningful. You are not able to navigate with this attribute. An attribute-type master data table can be used by any InfoCube that accesses this InfoObject. (C) SAP AG BW

69 Master Data and InfoCubes (2/2) Sales hierarchy Zone 1 Zone 2 Zone 3 District 1 District 2 District 3 District 4 District 5 Customer Master Data Attributes Cust.No. Name Location Industry Key Customer Dimension Territory 1 Territory 2 Territory 3 Territory 4 C Cust. No. Territory Chain Office Head Office Territory 5 Territory 6 Territory 7 Territory 8 Territory 9 Sales Hierarchy Sales InfoCube Fact Table C P T Quantity Sold Revenue Discnt Sales Overhead Stock Value Product Dimension P Product No. Product Group Brand Category Time Dimension T Period Fiscal Year SAP AG 2001 Product Master Data: Text Product No. Language Product Description This graphic shows a simplified example of how data from various tables and keys is combined. (C) SAP AG BW

70 MDM/Star Schema and BW MDM / Star Schema Fact Fact Table BW Star Schema Key Figure Fact Table (Dimension)attribute Characteristic / Navigation attribute / Reporting attribute / (External) hierarchy Dimension(table) Dimension table / Attribute table / Master data table / Text table / Hierarchy table / (SID table) SAP AG 2001 Common data warehouse terminology corresponds, for the most part, with BW terminology. In some cases, BW uses special terminology to describe various objects and processes. (C) SAP AG BW

71 Granularity of Data Data granularity is details from the database, and refers to the characteristics that describe our key figures The most detailed level of data By in the sense of according to - for example, sales by customer, or by material Determines how far you are able to drilldown on the data Example: Time granularity (day or month) A customer buys the same product two to three times a month With a time granularity of day: Two or three entries in the fact table With a time granularity of month: One data record in the fact table, but less information (since the number of orders for each day of the week is lost) SAP AG 2001 Granularity is a term used to describe the level of detail. If data has a high level of granularity, it means that the data is highly detailed and there are many characteristics describing the key figures. The level of granularity by customer, for example, is less detailed than by customer, by material. The level of granularity that a set of data has determines how far you are able to drill-down on the data. Granularity also affects the size of the database. Data that is stored by customer, by month is much more summarized than by customer, by day, by document, by document line item. A year s volume of data for the first case would therefore be much smaller than for the second. (C) SAP AG BW

72 From Data Model to Database Product Dimension Customer Dimension Sales Dimension Time- Dimension Quantities Revenue Costs Taxes Competition Dimension Product Dimension Customer Dimension Time Star Schema (Logical) InfoCube (Physical) SAP AG 2001 You use the term star schema, when you are talking about table structures conceptually, or from the perspective of data modeling. We talk about InfoCubes when we are referring to the actual set of tables where data is stored. In BW InfoCubes are used to create queries. (C) SAP AG BW

73 InfoCube Central data store for reports and evaluations Contains two types of data Key Figures Characteristics One fact table and 16 dimension tables Three dimensions are predefined by SAP Time Unit InfoPackage SAP AG 2001 The fact table and the relevant dimension tables of an InfoCube are connected with one another by the dimension keys. A dimension key is provided by the system, one per characteristic combination in a dimension table. When you execute a query, the OLAP processor checks in the dimension tables of the InfoCube that you want to evaluate, to see if they contain the characteristic combinations required by the selection. The dimension keys determined in this way, lead you to the information you need in the fact table. (C) SAP AG BW

74 InfoCube: Example Region North South East Customer Group Dept. Stores Wholesalers Retailers Glassware Ceramics Plastic Pottery Copper Pewter Division SAP AG 2001 This slide shows an InfoCube with three dimensions for analyzing the data stored in the fact table. This is the InfoCube used in the following slides as an example of how a query is created. (C) SAP AG BW

75 InfoCube: Multi-Dimensional Analysis Query Cache Characteristics: InfoCube Region North South East Customer Group Dept. Stores Wholesalers Glassware Ceramics Retailers Plastic Division Product Group Customer Group Division Zone Company Code Region Time Period Profit Center Business Area 1 Analysis of the Division Ceramics 2 Analysis of the DivisionPlastic 3 Analysis of the Division Plastic and the Region South Region North South East Ceramics Plastic Division Customer Group Dept. Stores Wholesalers Retailers Region North South East Glassware Glassware Ceramics Plastic Division Customer Group Dept. Stores Wholesalers Retailers Region North South East Glassware Ceramics Plastic Division Customer Group Dept. Stores Wholesalers Retailers SAP AG 2001 From the characteristics available in the dimensions of the InfoCube, you choose the characteristics that you want to use in your query. For these characteristics, a subset of data, called the Query Cache, is selected by the OLAP Processor and stored in the memory. This improves the query performance. From the data in the Query Cache, even more detailed views of the data can be generated. Filter values are used in the query to generate these more detailed views. This enables you to analyze specific divisions or regions. (C) SAP AG BW

76 InfoCube: Characteristics and Key Figures Region Customer Group RT-0001 Sales Hours Worked North Plastic Retailers Character -istics Key Figures Division One key figiure is stored for every unique combination of characteristic values Number of dimensions: Degree of granularity and level of summarization for the key figures SAP AG 2001 Once the values for each of your chosen characteristics have been retrieved, the corresponding rows of data in the fact table are located and displayed. (C) SAP AG BW

77 Data Warehousing: Unit Summary You are now able to: List the main differences between the structure of data in an R/3 system and in a BW Explain what a star schema is Evaluate the effect the InfoCube concept has on data granularity Name and give a definition of the InfoCube components SAP AG 2001 (C) SAP AG BW

78 Administrator Workbench Contents: Maintaining the BW system landscape Metadata management for InfoObjects and master data tables Transferring data Scheduler Monitor SAP AG 2001 (C) SAP AG BW

79 Administrator Workbench: Unit Objectives At the conclusion of this unit, you will be able to: Give examples of data sources, and explain how ALE connects source systems to BW Explain what metadata is, and how it is maintained Give a definition of an InfoObject Give a definition of an InfoSource Describe the process of transferring data from a source system into a BW Describe the Scheduler functions Explain the job of the Monitor SAP AG 2001 (C) SAP AG BW

80 Course Overview: Administrator Workbench Data Warehousing Business Explorer Administrator Workbench BW Overview Defining the User Environment Conclusion SAP AG 2001 (C) SAP AG BW

81 Administrator Workbench: Business Scenario You require information on the functions of the Administrator Workbench, the tool responsible for data modeling in BW, connecting source systems to BW, and loading data into BW. SAP AG 2001 (C) SAP AG BW

82 Administrator Workbench Central area for managing and controlling what happens in BW Scheduling data transfers Loading data BW set-up Maintenance Management Admin. Workbench Monitoring data transfers Monitoring update processes SAP AG 2001 The Administrator Workbench is the tool for maintaining, controlling, and monitoring the Business Information Warehouse. The jobs assigned to the Administrator Workbench include: Creating and customizing/maintaining all the components of the Business Information Warehouse Scheduling data transfers from various data sources Loading data Monitoring data transfers and data updates Business Content, delivered by SAP, reduces the work involved in configuring your BW system. The Administrator Workbench activates the SAP Business Content. (C) SAP AG BW

83 Source Systems A source system is a system that delivers data for extraction into the Business Information Warehouse Types of source system: SAP R/3 systems and mysap components External source systems (non-sap systems, flat files, data providers) SAP R/2 systems and SAP R/3 systems up to Release 3.1I are treated as external systems Data is extracted from the source system, and converted by InfoSources SAP AG 2001 All systems that provide the SAP Business Information Warehouse with data are referred to as source systems. An interface with the BW system must be maintained for each source system. SAP R/3 source systems (from Release 3.1I), mysap components ALE (Application Link Enabling) and/or trfc (Transactional Remote Function Call) External systems, SAP R/2 and SAP R/3 Releases earlier than 3.1I BAPI (Business Application Programming Interface) The data extraction process: Data from SAP R/3 (from Release 3.1I) and from mysap components, is extracted using the extractors delivered with Business Content, and loaded into BW. Data from SAP R/2 and R/3 (earlier than Release 3.1I) and data from non-sap source systems, is extracted using third-party tools. Data from flat files is loaded into BW using a file interface. (C) SAP AG BW

84 InfoObjects in BW InfoObject is a general term for a business object The definition includes technical information and business logic An InfoObject consists of: Technical definitions (for example, length, format, check routines, and so on) Master data / attributes Texts Hierarchies Compound information SAP AG 2001 InfoObject is the generic term for all business objects, such as customer, product, region, sales, head count and so on. As part of the BW Metadata Repository, InfoObjects include a technical definition as well as business logic. InfoObjects are used across the whole BW system (an InfoSource is a collection of InfoObjects). InfoObjects are either key figures or characteristics. Special characteristics are time and unit. The InfoObject definition includes: General information (data dictionary, Business Explorer, management, transfer routines) Master data/attributes Hierarchies Texts Compound information SAP InfoObjects start with the 0. Customer-defined InfoObjects start with a letter from A to Z. (C) SAP AG BW

85 Scenario for a New InfoObject Business Information Warehouse Cost Center Information CST Number: 13 characters Cost Center Information CST Number: 10 characters SAP R/3 OLTP (FI, CO, MM and so on) Overhead Cost Controlling Cost Center Information CST Number: 13 characters Non-SAP Systems Overhead Cost Controlling SAP AG 2001 In the scenario above, data from overhead cost controlling is loaded from two separate sources into a single InfoCube. The cost centers in the R/3 system are ten characters long, while the cost centers in the non- SAP source system have thirteen characters. The different ways the cost centers are displayed in the two source systems have to be homogenized, before you are able to report on all the cost centers in your company. In this case, the cost centers with ten characters that have come from the R/3 system have to be lengthened by three characters. To do this, you have to create a Cost Center InfoObject. (C) SAP AG BW

86 DataSources and InfoSources BW Server InfoSource InfoCubes Update Rules Communication Structure Master Data Transfer Rules Transfer Rules Transfer Structure Transfer Structure (Replicated) Transfer Structure Extraction Source Structure DataSource Flat File Source System OLTP System SAP AG 2001 Data extraction takes place in two components: the DataSource and the InfoSource. DataSources include extraction source structures and transfer structures. Data is staged in the extraction source structure and the transfer structure, and transferred into the BW system by ALE or trfc. An InfoSource is a set of information that logically belongs together. InfoSources manage transaction data and master data (attributes, texts, and hierarchies). InfoSources describe all the information that is available for a business transaction or a type of business transaction (for example, cost center accounting). Transfer structures support the transfer of data in a DataSource between a source system and the SAP BW system to which the source system is connected. The transfer structure transports the DataSource data from a source system to a SAP BW system. Transfer rules pass the data on to the InfoSource. The communication structure is independent of the source system and is generated from the InfoSource. It is filled from the transfer structure, according to the transfer rules. The communication structure contains all the fields in an InfoSource. This method of extracting and transferring cleansed data in the communication structure is called data staging. Every InfoCube has update rules that determine how data from the communication structure is stored in the InfoCube. (C) SAP AG BW

87 Transfer Rules and Update Rules Transfer Rules Provide the logical link between DataSources and InfoSources Allow you to assign fields to InfoObjects and use constants or ABAP routines Are available for transaction data, attributes, texts, and hierarchies Update Rules Provide the logical link between InfoSources and InfoCubes Allow you to assign InfoObjects to InfoObjects and use constants or ABAP routines SAP AG 2001 Transfer rules connect a DataSource to an InfoSource. The logic behind the assignment of DataSource-type data elements to InfoObjects in the InfoSource is contained in the transfer rules. Update rules determine in what form the data from the communication structure is updated in the InfoCube. Data can be manipulated by either set of rules. If you want to have a consistent definition of data for all InfoCubes, the best way of converting the data into a consistent format is by using the transfer rules. Update rules can be used for InfoCube-specific data conversions. (C) SAP AG BW

88 Staging Engine Data staging methods for: Metadata Master data (attributes, texts, and hierarchies) Transaction data Logical selection for delta updates and refresh Homogenization of various source systems for: Various R/3 releases and mysap components R/2 External data Flat files SAP AG 2001 Different types of data are collected from the different types of data source: Metadata Master data Transaction data To keep the data in BW consistent, specific methods within the data staging process are required for each data type and each data source. Metadata Metadata is data about data. It is information that characterizes the data in the data warehouse environment. Master data (SAP interpretation) Master data is data that remains unchanged over a long period of time. It contains information that is always needed in the same way. In BW, master data is assigned to the characteristics, and can be attributes, texts, or hierarchies. Transaction data Transaction data is created within an operational environment and updated frequently. (C) SAP AG BW

89 Extraction from Several Sources Update Rules InfoCube InfoSource Update Rules InfoCube Update Rules InfoSource Business Information Warehouse Server Transfer Rules Transfer Rules Data Extract Sales Europe Non-SAP Extraction Tool Data Extract Sales America Market Info. ASCII Data Source Systems R/3 Source System Non-SAP Source System Data Providers File Interface SAP AG 2001 Virtually any source of data can be extracted for use in the Business Information Warehouse. (C) SAP AG BW

90 ALE Inbound Methods of Extraction Source System BW IDOC 1,000 Bytes Transfer Structure IDOC IDOC Transfer Structure 1 Info Source 2 optional ODS PSA Transfer Structure Transfer Structure 1 Info Source Fields 1,900 Bytes Selection of an extraction method in the transfer structure One PSA for each Transfer Structure PSA 1 2 Transfer Rules Update Rules SAP AG 2001 There are two ways of extracting data: You can use IDocs to load the data into a data target (InfoCube) directly. If you choose this method, all of the data is transferred by way of the IDocs. Alternatively, you can load the data into the PSA. With this method, Info-IDocs are sent at the start and end of the extraction process, but the data itself is not sent by IDocs. (C) SAP AG BW

91 Scheduler InfoPackage Parameterized extraction job with: InfoSource Source System Selection criteria including variables User-friendly Consistency thanks to synchronized extraction One-off or repeated extraction jobs InfoPackage groups R/3 job scheduling Event-controlled or time-controlled SAP AG 2001 Data requests to the source system are managed by the Scheduler. The requests are formulated per InfoSource and source system, and differentiate between master and transaction data. There can be different extraction requests with different selection criteria for an InfoSource in one source system. These are known as InfoPackages. A variety of selection criteria can be used to restrict the data that is requested. R/3 job planning distributes InfoPackages or groups of InfoPackages into background processes. This means that you can completely automate the data transfer process, and decide for yourself when and how often to extract data. For example, you might want to use your own factory calendar to schedule data extraction on public holidays, and so on. The transaction concept in the Business Information Warehouse includes the retrieval of data from the OLTP, and the successful update of the data in the corresponding InfoCubes. Using the monitoring function in the Administrator Workbench, you monitor the data transfer and the processing of the data that has arrived in BW. You can generate lists per user, per source system, per day, and so on, that contain information on the status of the InfoPackage processing. (C) SAP AG BW

92 Monitor SAP AG 2001 An overview of the data extraction requests is displayed in the Monitor in a tree structure. In this tree structure, you can display details of the various requests, for example, the current status of a particular request. Any errors that have occurred during the extraction process are logged in the Monitor to help you locate and remove their cause. The Monitor Assistant analyzes the requests, and suggests any corrections that you might need to make. The Monitor Assistant can be run in the background, and notify specified recipients of problems. A series of different IDocs are required to handle the data transfer. These IDocs make communication and data transfer possible across the system boundaries. Information IDocs and data IDocs are different. You tell them apart by their status. (C) SAP AG BW

93 Additional Administrator Workbench Functions Activating BW statistics Maintaining aggregates Activating SAP DemoCubes Maintaining master data Maintaining hierarchies Managing InfoCubes Checking indexes, deleting or reconstructing Reconstructing InfoCubes Compressing InfoCubes Analyzing InfoCube status SAP AG 2001 The Administrator Workbench has many additional functions, some of which are listed above. BW Statistics activates an InfoCube, delivered by SAP, containing information on many aspects of system performance. This information is very useful in showing you how the BW system is being used, and if there are any areas that could be improved. One way to improve query performance in BW is to use aggregates. Aggregates are summarized versions of InfoCubes, and are useful in queries involving non-summarized characteristics. SAP DemoCubes provide demonstration scenarios that have been modeled according to the requirements of different types of company. They contain data from delivered flat files. When you activate a SAP DemoCube, all the required objects are created automatically, and you are able to see the underlying structure in the Administrator Workbench. Once the flat file data has been loaded, analyses can be displayed immediately. You use the tools in the Administrator Workbench to maintain the contents of the InfoCube. When you click with the right mouse-button on an InfoCube, and select Manage InfoCube Contents, you can choose from a selection of analyses that help improve the performance of the InfoCube. (C) SAP AG BW

94 Administrator Workbench: Unit Summary You are now able to: Give examples of data sources, and explain how ALE connects an R/3 system to a BW Explain what metadata is, and how it is maintained Give a definition of an InfoObject Give a definition of an InfoSource Describe the process of transferring data from a source system into a BW Describe the Scheduler functions Explain the job of the Monitor SAP AG 2001 (C) SAP AG BW

95 Administrator Workbench - Exercises Unit: Administrator Workbench Topic: InfoCube Analysis At the conclusion of this exercise, you will be able to: Use the Administrator Workbench functions to analyze the construction and contents of an InfoCube. Your company has given you the task of creating queries from various InfoCubes, and making them available to other employees in the company. Before you can do this, you have to analyze the construction of the InfoCubes, and check the contents of the fact table. You use the Administrator Workbench functions to this. 1-1 Analyze the InfoCube Customer Cube (SDDEMO3). This InfoCube is stored in the data targets directory under the InfoArea Customer Training/BW Customer Training/BW200 Overview. Use the Change function to answer the following questions Which characteristics are there in the InfoCube? What are the dimensions of the InfoCube called? Which characteristics are there in the Sales Area dimension? How many key figures are there in the InfoCube? Find out about the data type and field length of the time characteristics Fiscal year/period (0FISCPER). 1-2 Use the Display Dataflow function to find out from which source system the InfoCube gets its data, and which InfoSource is used to stage the data. What is the technical name of the InfoSource? 1-3 Use the Manage function to find out more information on the InfoCube Use the Requests tabstrip to find out when the last request was loaded successfully into the InfoCube Choose the Contents tabstrip. Check the contents of the fact table. (C) SAP AG BW

96 Administrator Workbench - Solutions Unit: Administrator Workbench Topic: InfoCube Analysis At the conclusion of this exercise, you will be able to: Use the Administrator Workbench functions to analyze the construction and contents of an InfoCube. 1-1 Analyze the InfoCube Customer Cube 200 (SDDEMO3). This InfoCube is stored in the data targets directory under the InfoArea BW Customer Training/BW200. Use the Change function to answer the following questions. Right mouse-click Change Which characteristics are there in the InfoCube? Characteristics tabstrip Characteristics: Distribution channel (0DISTR_CHAN), Division (0DIVISION), Material number (0MATERIAL), Sales organization (0SALESORG), Sold-to party (0SOLD_TO), Version (0VERSION), Value type for reporting (0VTYPE) What are the dimensions of the InfoCube called? Tabstrip Characteristics Dimensions button Define tabstrip Dimensions: Customer, Material, Sales Area, Version, Value Type Which characteristics are there in the Sales Area dimension? Assign tabstrip Characteristics in the dimension Sales Area : Distribution Channel, Division, Sales Organization How many key figures are there in the InfoCube? Close the Defining Dimensions window. Key Figures tabstrip Number of key figures in the InfoCube: 9 (C) SAP AG BW

97 1-1-5 Find out about the data type and field length of the time characteristics Fiscal year/period (0FISCPER). Time Characteristics tabstrip Detail View option Time characteristic Fiscal year/period Data type NUMC, field length: Use the Display Dataflow function to find out from which source system the InfoCube gets its data, and which InfoSource is used to stage the data. What is the technical name of the InfoSource? Return to the data targets directory in the Administrator Workbench. Right mouse-click on the InfoCube Show dataflow Name of the source system: ID3 Client 800 Icon Technical Name On/Off Name of the InfoSource: 2LIS_01_S001 Click on the Close button to close the window. 1-3 Use the Manage function to find out more information on the InfoCube. Right mouse-click Manage Use the Requests tabstrip to find out when the last request was loaded successfully into the InfoCube. Requests tabstrip Look at the request at the top of the screen with the green traffic light in the tabstrip, and note the date Choose the Contents tabstrip. Check the contents of the fact table. Contents tabstrip Fact Table button Execute button. (C) SAP AG BW

98 Defining the User Environment Contents: Roles Authorizations SAP AG 2001 (C) SAP AG BW

99 Defining the User Environment: Unit Objectives At the conclusion of this unit, you will be able to Define the term Role Explain how roles and authorizations work together to give users access to the appropriate data SAP AG 2001 (C) SAP AG BW

100 Course Overview: Defining the User Environment Data Warehousing Business Explorer Admin. Workbench BW Overview Conclusion Defining the User Environment SAP AG 2001 (C) SAP AG BW

101 Defining the User Environment: Business Scenario In your company, most users need access to existing reports using predefined datasets Using the BW role concept, make sure that all users receive the reports and information that are relevant for them and, at the same time, ensure that they cannot see data or information, for which they have no authorization SAP AG 2001 (C) SAP AG BW

102 Different Types of Data Warehouse User Different demands of the individual user High One-time users 70% 10% 20% Query developers Experienced users Complete multidimensional analysis Reporting ability Low Static report Predefined collection of data Predefined navigational paths Self-explanatory navigation Low User's level of knowledge High SAP AG 2001 The information that is already entered has to be adapted to the user's requirements. The majority of users prefer to work with predefined reports that are easy to access. These users need to be able to call up key figure values simply and easily. However, some users require extensive evaluation options. For example, they may want to navigate between certain sections of a report. As well as needing complete access to predefined queries and data collections, only a few users need to be able to create new queries and data sets in order to solve specific problems. (C) SAP AG BW

103 Business Factors Use your information resources Give your colleagues the right information at the right time Avoid overwhelming them with too much information Manage complex data, take account of the changes, avoid fragments and inconsistencies SAP AG 2001 The employees in your company have different requirements when it comes to type and scope of information. Using information resources optimally is always of high concern within a company. If individual employees can get the right information at the right time, they can then use it take the appropriate action. With growing competitive pressure, a company's ability to react quickly is essential. In the face of this, companies often attempt to have as many information sources as possible. However, this can lead to an unwelcome flood of information. Inconsistent or complex sources of information make you lose time when searching for data, therefore making it more difficult for you to react quickly. (C) SAP AG BW

104 Examples of Supported Roles Financial Accounting Corporate Finance Controller Cash Management Accountant Staff Accountant Accounts Receivable Accountant Accounts Payable Accountant Senior Cost Manager Financial Accounting Supervisor Travel Manager Budget Analyst Procurement Purchasing Manager Strategic Purchaser Procurement Planner Supply Chain Manager MRP Controller MM Retail: Purchaser CP: Buyer Manager Benchmarking based on SCOR Inventory Controller Production Manager Production Planner Production Controller Plant Manager Supply Chain Planner Foreman MRP-Contr Quality Planner Quality Manager Production APO: Supply Chain Planner APO: Production Planner APO: Strategic logistics planner Automotive: Prod. supervisor Automotive: Production planner Process Production Planner Shift Manager REM Production Planner Production Supervisor Sales & Marketing Sales Manager Sales Representative Product Manager Customer Service Manager Field Sales Representative CP: Brand Manager CP: Sales Manager CP: Key Account Manager Oil & Gas: Director HR Management Personnel Recruiter Personnel Controller Payroll Specialist Employer s Payments Specialist Specialist Training and Development Specialist Compensation Mgmt Specialist Time Management Specialist Organization Mgmt Budget Supervisor Service Manager Regional Manager Investment Manager Asset Manager Banking: Financial Analyst Banking: Branch Manager Banking: Profit Center Manager Banking: Senior Manager SAP AG 2001 Maintenance Manager Technical Project Manager Oil & Gas: Plant Manager Transportation Controller Automotive: JIT- Controller Exchange Accountant Exchange Manager Media: VP of Circulation Media: VP of Advertising Banking: Product Manager Banking: Relationship Mgr. Legend Cross-industry roles Industry-specific roles This slide shows only a few of the many roles that are delivered with SAP BW Business Content. These roles group together all the information tools needed by employees in different areas, regardless of the application, in which the data was originally prepared. Once you have activated the roles, you can assign the corresponding users to them. The roles are ready to use immediately. (C) SAP AG BW

105 SAP's Role Concept: Example Regional Sales Manager 1 I want to increase the revenue in my region. Which of my customers make a negative contribution? In which areas can I expand my business activities? Why is my rate of return higher in this quarter than in the last quarter? Sales and Distribution Profitability Market share Delivery Personal Quality Market Potential Product costs Sales and service costs Customer satisfaction SAP AG 2001 Regional sales managers are responsible for planning, organizing and converting the sales strategy. They supervise the sales targets and profitability in the sales department and have an overview of the sales employees and distributors. As well as monitoring the sales activities in general, sales managers can also check cost center activities. Regional sales managers coordinate the budget and the forecast. They also report on the products and prices. Additionally, they follow the development of customer complaints. The Business Information Warehouse delivers information on the sales pipeline, the sales portfolio, and the budget, by requesting information on sales activities. (C) SAP AG BW

106 Role Activities Incoming Orders Order and Sales Values Activities of a role Sales Incoming Orders Customer: Incoming orders / Sales: Months, current year Order, delivery and sales values menu Workbooks 2 Deliveries Customer: Return quantities and values Credit Memo Returns per customer Customer: Deliveries per week Jobs Cost center Cost center: Plan/actual deviation Cost center: Plan/actual deviation, current/cumulative periods Cost center: Statistical key figures Plan/actual deviation SAP AG 2001 From the task of regional sales manager, we derive the activities that can be assigned to this role. The regional sales manager needs, for example, current figures on incoming orders and deliveries, in order to monitor sales activities. The Business Information Warehouse delivers this information in the form of workbooks, which contain different queries. Every role is assigned one or more of these workbooks, which retrieve the required information. Moreover, you can assign R/3 and BW system transactions, MiniApps, Internet and intranet links to a role. (C) SAP AG BW

107 SAP's Role Concept: Overview Different roles in a company. Assign 1 4 User Activities of a role menu Workbooks Jobs 2 3 Profile generator 5 User comparison SAP AG 2001 The development of the user role concept was based on the idea that employees within a company who have the same tasks may also use the same transactions, Internet links and reports. It makes sure that the individual users are able to see only what they need for the tasks they perform. A role describes the business tasks of its assigned users. If a user is assigned to a user role that is predefined by SAP, the menu designed for his or her task area automatically appears when they log on to the SAP system (for example, transactions, reports and/or Internet links) as well as the authorizations the user needs for his or her work. SAP distinguishes between single and composite roles. The single roles contain the authorizations that users need to access, for example, the transactions and reports in the user-specific menu. Composite roles consist of several single roles. They do not receive any authorization data themselves, but get the authorizations from the single roles assigned to them. Use composite roles if some of your co-workers need authorizations for several single roles. This means you can assign user groups to one of the SAP composite roles instead of entering the required single roles for each individual user. (C) SAP AG BW