List of Figures

Team-Fly

---

Chapter 1: Constructing a Data Warehouse

Figure 1-1: Independent and Dependent Data Marts.

Figure 1-2: The Architectural Layers of a Data Warehouse.

Figure 1-3: The Technical Aspects of a Data Warehouse.

Figure 1-4: Data Warehouse Performance Characteristics.

Figure 1-5: Evolution of ERP Applications and Data Warehousing.

Chapter 2: Evolution of SAP Business Information Warehouse

Figure 2-1: SAP R/3 Business Applications.

Figure 2-2: SAP R/3 Deployment Architecture.

Figure 2-3: SAP R/3 Reporting Environment.

Figure 2-4: SAP Business Framework Architecture.

Figure 2-5: R/3 Database-Centric Reporting Environment.

Figure 2-6: SAP ALE-Centric R/3 Reporting Environment.

Figure 2-7: Functionality Comparison of R/3 Data Warehouse Models.

Figure 2-8: Architecture of Business Information Warehouse.

Figure 2-9: Business Content in SAP BW 1.2B and BW 2.0A

Figure 2-10: SAP BW Staging Process in SAP BW 1.2B and SAP BW 2.0A.

Figure 2-11: Business Explorer Browser and Analyzer.

Figure 2-12: Business Explorer Analyzer.

Figure 2-13: A Typical Star-Schema Model for Multidimensional Data Analysis.

Figure 2-14: Star-Schema Model in SAP BW 1.2B.

Figure 2-15: Data Flow Within SAP BW 1.2B.

Figure 2-16: SAP BW Business Explorer Browser with Sample Reports.

Figure 2-17: SAP BW Business Explorer Browser-Starting Data Analysis Tasks.

Figure 2-18: SAP BW 1.2B Business Explorer Analyzer.

Figure 2-19: SAP BW 1.2B Business Explorer Analyzer Drill-Down by Product Hierarchy.

Chapter 3: Comparing SAP BW with Data Warehouse Solutions Provided by Other Vendors

Figure 3-1: SAP BW and Third-Party Vendors' Data Warehouse Products.

Chapter 4: Getting Started with SAP BW

Figure 4-1: The SAP BW Logon Icon.

Figure 4-2: The SAP BW Logon Server Selection Screen.

Figure 4-3: SAP BW Client Session Starts.

Figure 4-4: SAP BW Session Startup Screen.

Figure 4-5: SAP BW User Logon Information Screen.

Figure 4-6: SAP BW Main Screen for SAP BW 1.2B (SAPGUI 4.5A Frontend) and SAP BW 2.0A (SAPGUI 4.6A Frontend).

Figure 4-7: Exiting From SAP BW.

Figure 4-8: SAP BW Session Log Off Confirmation Dialog Box.

Figure 4-9: SAP BW Logon Paths in SAP BW 1.2B and SAP BW 2.0.

Figure 4-10: The Business Explorer Browser.

Figure 4-11: The SAP Business Warehouse Logo Window.

Figure 4-12: The SAP BW Server Selection Window.

Figure 4-13: The SAP BW Logon User Information Window.

Figure 4-14: SAP Business Warehouse Copyright Window for SAP BW 1.2B.

Figure 4-15: The SAP BW Browser is a Corporate Information Repository that Contains Information Objects Such as Reports, Analytical Applications, or Web Sites.

Figure 4-16: Simple Sales by Employee Data Analysis Report via BEX Analyzer.

Figure 4-17: The SAP Business Explorer Analyzer.

Figure 4-18: SAP BEX Analyzer Microsoft Excel Add-In.

Figure 4-19: Starting Connection to SAP BW From the SAP BEX Analyzer.

Figure 4-20: SAP BEX Information Catalog to List the Defined Query in SAP BW 1.2B.

Chapter 5: Planning for SAP BW Implementation

Figure 5-1: ASAP Methodology Road Map for Business Information Warehouse.

Figure 5-2: ASAP Methodology Templates and Accelerators for Business Information Warehouse.

Figure 5-3: Reporting and Data Analysis Categories and Boundaries of an SAP BW Project.

Figure 5-4: SAP BW Project Team Members.

Chapter 6: Setting Up SAP BW

Figure 6-1: SAP BW Installation Steps-Backend and Frontend. The Shaded Area Represents the SAP BW Specific Component Installation.

Figure 6-2: SAP BW System Landscape-Path to Production.

Figure 6-3: SAP BW Frontend Installation on the Administrator Workstation.

Figure 6-4: Installing SAP BW Components for End Users and Developers.

Figure 6-5: Launching the SAP Business Explorer Analyzer.

Figure 6-6: SAP BW Explorer.

Figure 6-7: SAP BW Installation Checkup.

Figure 6-8: Defining the SAP BW Active Client.

Figure 6-9: Copying the 000 Client to the SAP BW Active Client.

Figure 6-10: Basic SAP BW Setting. The Left Shows the Setting Menu for SAP BW 1.2B, and the Right Shows the Same Setting Menu in SAP BW 2.0A.

Figure 6-11: Customizing SAP BW Operational Parameters.

Figure 6-12: SAP BW Customizing Implementation Guide.

Figure 6-13: SAP BW Instance and Applications Specific Customization and Configuration Parameter Settings.

Figure 6-14: SAP BW Customization and Configuration Global Parameter Settings.

Figure 6-15: Setting Global Data Administration Parameters.

Figure 6-16: Modifying the SAP BW Operation Configuration Table RSADMIN.

Figure 6-17: Defining RFC Destination for Remote Data Source SAP R/3 Instance.

Figure 6-18: Testing RFC Destination for a Remote SAP R/3 Data Source.

Figure 6-19: SAP BW Operations on Microsoft Windows NT 4.0. On the Left is the Service Manager to Start and Stop the SAP BW 1.2B Instance. On the Right is the Service Manager Integration with Microsoft Management Console to Manage SAP BW 2.0 Services and Associated Processes.

Chapter 7: SAP BW-The Administrator Workbench

Figure 7-1: SAP BW Main Menu. The Menu on the Left is for SAP BW1.2B, and the Menu on the Right is for SAP BW 2.0A.

Figure 7-2: SAP BW 1.2B Administrator Workbench.

Figure 7-3: SAP BW Administrator Workbench (Transaction RSA1). The Top Section Shows the SAP BW 1.2 Administrator Workbench with Tabstrips to Manage Object Types. The Bottom Shows the SAP BW 2.0A Administrator Workbench. The Only Major Difference is that in BW 2.0A, You Select the Object Type From a Drop-Down Menu.

Figure 7-4: SAP BW Administrator Workbench-Changing the Startup View.

Figure 7-5: SAP BW Administrator Workbench-Selecting Display Options.

Figure 7-6: SAP BW Administrator Workbench-Operations and Development Environment and its Relationship with the SAP BW 1.2B Staging Process.

Figure 7-7: Classes of Data Sources for SAP BW.

Figure 7-8: Creating a Source System in SAP BW. The Source System is the Logical Name Assigned for a Remote Connection.

Figure 7-9: Defining an RFC Definition in SAP BW for SAP R/3 as a Data Source.

Figure 7-10: RFC Destination Connection Verification.

Figure 7-11: Source Systems Tree in the Administrator Workbench to Show Data Sources Connected to SAP BW.

Figure 7-12: Maintaining Data Sources in SAP BW, Such as Updating InfoSource Metadata from Source R/3 to SAP BW or Enhancing SAP-Provided Data Extractors.

Figure 7-13: Managing InfoObjects in the Administrator Workbench.

Figure 7-14: Maintaining InfoObjects in SAP BW 1.2B.

Figure 7-15: Characteristics in SAP BW 1.2B.

Figure 7-16: Maintaining Individual InfoObjects in SAP BW 1.2B.

Figure 7-17: Assigning Master Data and Text Elements to an InfoObject.

Figure 7-18: Maintaining an InfoObject and Assigning Hierarchies.

Figure 7-19: Assigning Attributes to an InfoObject.

Figure 7-20: Navigational Attributes of an InfoObject.

Figure 7-21: Building Compounding Functionality for an InfoObject.

Figure 7-22: Defining Basic Data Types for a Key Figure.

Figure 7-23: Defining an Aggregation Scheme for a Key Figure.

Figure 7-24: Definition of Calendar Year (0CALYEAR) Time Characteristics.

Figure 7-25: Definition of Unit of Measure, 0BASE-UOM InfoObject.

Figure 7-26: Managing InfoObjects in SAP BW 1.2B.

Figure 7-27: Creating an InfoArea, Demo Info Area, to Group Analytical Applications for Product Demonstration.

Figure 7-28: Creating a New InfoObject Catalog.

Figure 7-29: Defining Characteristics for an InfoObject Catalog.

Figure 7-30: Editing an InfoObject Catalog for Characteristics.

Figure 7-31: Editing an InfoObject Catalog for Key Figures.

Figure 7-32: Viewing InfoObject Details of an InfoObject Catalog.

Figure 7-33: Importing InfoSource Metadata in SAP BW From an SAP R/3 Data Source.

Figure 7-34: Creating New Application Components to Set up an InfoSource.

Figure 7-35: Sales and Distribution InfoArea and Associated InfoCubes.

Figure 7-36: SAP's Customer InfoCube Data Model.

Figure 7-37: Definition of SAP's Customer InfoCube Data Model.

Figure 7-38: Defining Dimensions for an InfoCube and Assigning Characteristics to the Dimensions.

Figure 7-39: Graphical View of Dimension Assignments for an InfoCube.

Figure 7-40: Viewing InfoCube Content.

Chapter 8: SAP BW-Loading Business Content

Figure 8-1: Information Flow between SAP BW and its Data Sources.

Figure 8-2: Verification of an SAP BW Add-On in an SAP R/3 OLTP Instance.

Figure 8-3: SAP BW 1.2B Metadata Management in SAP R/3 OLTP Instance. Tables that Manage SAP BW Specific Metadata.

Figure 8-4: Metadata Tables in SAP BW 1.2B.

Figure 8-5: Loading InfoSources Metadata From an SAP R/3 Data Source.

Figure 8-6: Importing Exchange Rates From an SAP R/3 OLTP Instance.

Figure 8-7: Importing Global Settings From SAP R/3.

Figure 8-8: Activating Business Content in SAP BW 1.2B.

Figure 8-9: Activating an InfoCube in SAP BW.

Figure 8-10: Transferring InfoCube Definition From SAP BW Business Content to Local Implementation.

Figure 8-11: Maintaining an InfoCube Schema in SAP BW.

Figure 8-12: Maintaining InfoCube Update Rules.

Figure 8-13: Visual View of the InfoCube Model for the Customer InfoCube in SAP BW.

Figure 8-14: Loading Queries From Business Content for Customer InfoCubes.

Figure 8-15: Activating SAP Delivered Channels.

Figure 8-16: Adding Channels in the InfoCatalog.

Figure 8-17: Assigning Users to Channels.

Figure 8-18: Activating the SAP Demo Cube.

Chapter 9: Preparing R/3 Data Sources for SAP BW Initial Data Loads

Figure 9-1: SAP R/3 OLTP Verification of the Workflow Runtime Environment for SAP BW.

Figure 9-2: A Typical Order Processing Transaction Data Flow in SAP R/3 and Associated Data Sets for InfoCubes in SAP BW 1.2B.

Figure 9-3: Statistical Update to Prepare Initial Data Loads and Process of Incremental Data Capture in SAP R/3 for SAP BW.

Figure 9-4: Identifying Permitted Characters in SAP BW Beyond Standard Text and Numeric Characters in SAP BW 1.2B. A Similar Method Exists in SAP BW 2.0A.

Figure 9-5: Setting Statistical Update for SAP BW LIS Structures in SAP R/3 OLTP Data Source.

Figure 9-6: Data Load Paths in SAP BW 1.2B.

Figure 9-7: Data Load Paths in SAP BW 2.0A. The Early Customer Release is SAP BW2.0B, But it May Change.

Figure 9-8: Editing Transfer Rules for an InfoSource to Define InfoSource Data Transfer Method.

Figure 9-9: Creating an InfoPackage to Load Data in SAP BW 1.2B.

Figure 9-10: InfoPackage Scheduling for SAP R/3 Transactional InfoSources Based on SAP BW Version 1.2B.

Figure 9-11: InfoPackage Scheduling for SAP R/3 Transactional InfoSources Based on SAP BW Version 2.0A.

Figure 9-12: InfoPackage Scheduling Options for Flat File InfoSources.

Figure 9-13: InfoPackage Scheduling for Third-Party Data Loading Tools that Use SAP BW Staging BAPIs.

Figure 9-14: Defining Data Load Flow in SAP BW When the Data Transfer Method is ALE IDOC.

Figure 9-15: Defining Data Load Flow in SAP BW When the Data Transfer Method is tRFC with ODS. In SAP BW Version 2.0A, ODS Means PSA.

Figure 9-16: Loading a Large Amount of Data in SAP BW by Splitting One Huge Task into Multiple Data Load Sessions. Each Session is Limited to a Given Range of Material Values.

Figure 9-17: Loading Incremental Changes in SAP BW.

Figure 9-18: SAP BW Data Load Monitoring Environment in SAP BW 2.0A.

Figure 9-19: Data Load Job Statistics Summary. The Lights (Green, Red, and Yellow) Show the Current State of Individual Jobs.

Figure 9-20: Monitor Assistant (Renamed Wizard in BW 2.0) Displays the State of Individual Data Load Tasks.

Figure 9-21: Data Load Detailed Analysis to Identify and Resolve Update Problems.

Chapter 10: Loading Data via Flat Files

Figure 10-1: Defining a Flat File Data Source.

Figure 10-2: Creating a Source System for Flat File Data Sources.

Figure 10-3: Defining InfoSource Type for Flat File Data Sources.

Figure 10-4: Assigning a Flat File Source System to a Master Data InfoSource.

Figure 10-5: Attributes Definitions for Master Data.

Figure 10-6: Texts Definitions for Master Data.

Figure 10-7: Hierarchies Definitions for Master Data.

Figure 10-8: Metadata Definition for Transaction Data Flat Files.

Figure 10-9: Scheduling an InfoPackage to Load Data in SAP BW.

Figure 10-10: Scheduling Data Load in SAP BW.

Figure 10-11: Loading Hierarchy Data in SAP BW

Figure 10-12: Loading Transaction Data via Flat Files.

Figure 10-13: Selecting InfoCubes to Load Data into From External Data Flat Files.

Chapter 11: Analyzing SAP BW Data

Figure 11-1: SAP BW Business Explorer Browser and Analyzer Architecture in BW 1.2B and BW 2.0A.

Figure 11-2: SAP BW Business Explorer (BEX) Analyzer Add-In and BEX Analyzer Menu Bars for BW 1.2B and BW 2.0B.

Figure 11-3: InfoCube Model to Demonstrate BEX Analyzer for Reporting and Analysis.

Figure 11-4: Defining a New Query in the BEX Analyzer.

Figure 11-5: Selecting Data Elements of a BEX Query.

Figure 11-6: The Default Query Results Based on the Global Query Setting. You Can Change the Look and Feel of the Query by Changing its Properties.

Figure 11-7: Selecting Characteristic Display Options.

Figure 11-8: Creating Charts and Graphs in the BEX Query.

Figure 11-9: Selecting Chart Display Options.

Figure 11-10: Creating Restricted Key Figures in the BEX Analyzer Query.

Figure 11-11: Using Restricted Key Figures in the BEX Analyzer Query.

Figure 11-12: Displaying Current and Past Year Revenues by using Restricted Key Figures.

Figure 11-13: SAP BEX Analyzer Query Navigation and Result Areas.

Figure 11-14: Drill-Down Methods to Navigate Data in SAP BW BEX Analyzer.

Figure 11-15: Swapping Dimensions. Revenues are Broken Down by Material and Customer on the Left and Revenue by Customer and Material on the Right.

Figure 11-16: The BEX Analyzer Default Displays Data with Repeated Characteristic Values. Setting the Query Property to Suppress Repeated Values Makes the Same Data Display Much Clearer and the Data More Presentable.

Figure 11-17: Displaying Subtotal Values Against a Given Characteristic During Drill-Down Navigation.

Figure 11-18: Defining Variable ZCUSTMR in SAP BW using Transaction RSZV that Will be Used to Dynamically Set Values for a Customer to Select.

Figure 11-19: Customizing the BEX Analyzer Query to Select Customer Data Based on User Input using a Variable. At the Query Runtime, the User is Prompted for Variable Value. This Variable Value is Used to Select Data at the Database Level.

Figure 11-20: Setting up the Query Global Properties for Time-Dependent (Slowly Changing Dimensions) Data Objects.

Figure 11-21: Enterprise InfoCatalog. A Collection of Enterprise-Wide Reports and Other Information Objects. Use Simple Drag-And-Drop Techniques to Move Objects.

Figure 11-22: Channel InfoCatalog. Common Repository of Channels. Here You Create New Channels and Manage and Assign Reporting Objects to the Channels. Note that You Assign Only Reports or Other Information Objects to a Specific Channel and Not to an End User.

Figure 11-23: User Channel Assignment. All Users in SAP BW are Listed Alphabetically on the Left. All Defined Channels are Listed on the Right. Select a User, and Drag and Drop it in a Channel to Make an Assignment.

Figure 11-24: Assigning Reports to Individual Favorites. The InfoCatalog Administrator Can Manage an Individual's Entries in His or Her Favorite Folders. You Can Organize Entries Simply by Dragging Them From One Folder and Dropping Them into Another Folder.

Figure 11-25: The BEX Browser Lists Only Assigned Channels to User BWADMIN. These Assignments were Made in the InfoCatalog as Shown in Figure 11-24.

Figure 11-26: Viewing Query Properties From the BEX Browser.

Figure 11-27: Including Non-SAP BW Information Objects in the BEX Browser.

Chapter 12: SAP BW-Defining Custom InfoCubes

Figure 12-1: Enterprise Data Warehouse Modeling.

Figure 12-2: Multidimensional Data Model in SAP BW. The Star Schema Representation for the Sales and Distribution Demo InfoCube in SAP BW 2.0A.

Figure 12-3: Factless Fact Table. It Contains No Measures.

Figure 12-4: Extended Star Schema for SAP BW 1.2B InfoCubes.

Figure 12-5: Defining a New InfoCube in SAP BW. The Top Shows the InfoCube Types Available in SAP BW 1.2B, the Middle in BW 2.0A, and the Bottom in BW 2.0B. Note that in SAP W 2.0B, There is No InfoCube Tree. In SAP BW 2.0B, You Will Find a Data Targets Tree, InfoAreas, and Either InfoCube or the ODS Object. SAP BW 2.0B is Discussed in Chapter 17; this is Here for Information Only.

Figure 12-6: Assigning Characteristics, Dimensions, and Attributes for a New InfoCube using SAP BW 2.0A.

Figure 12-7: Creating Dimensions and Assigning Attributes to Them.

Figure 12-8: Defining Update Rules for an InfoCube in SAP BW 2.0A. This Version Supports a Concept of a Startup Routine that was Not Available in SAP BW 1.2B.

Figure 12-9: Update Rules Details for Key Figures in an InfoCube. The Top Section Defines How Key Figures are Saved in an InfoCube, the Middle Section Describes Mapping of a Key Figure Value before it is Stored, and the Bottom are the Units for Reference for the Key Figure.

Figure 12-10: Defining Update Rules for Characteristics. Five Methods are Available to Map Characteristics and Assign Values: Direct InfoSource, Constant Value, From Master Data, Through an ABAP Routine, or Initial Value.

Figure 12-11: Accessing Error Logs and Generated InfoCube Update ABAP Code.

Figure 12-12: Selecting InfoCubes or MultiCube InfoCubes in SAP BW 2.0A.

Figure 12-13: MultiCube InfoCube Saved and Activated. Looks and Behaves Exactly Like a Typical InfoCube.

Chapter 13: Enhancing Business Content and Developing Data Extractors

Figure 13-1: Creating a Project for Enhancements in SAP BW using Transaction CMOD.

Figure 13-2: Enhancing Data Extractors in SAP R/3.

Figure 13-3: Activating and Adjusting the Database after Appending a Structure Definition.

Figure 13-4: Adding Custom ABAP Code to Fill New Data Elements in the InfoStructure using EXIT_SAPLRSAP_001.

Figure 13-5: Updating Metadata for Enhanced InfoObjects From SAP R/3 OLTP in SAP BW. It is Suggested that You Enhance Business Content on the OLTP Side, and then Pull Metadata in SAP BW.

Chapter 14: Integrating Third-Party ETL Products with SAP BW

Figure 14-1: SAP BW Data Loading and Data Access Interfaces.

Figure 14-2: SAP BW Metadata Management Process using Staging BAPIs.

Figure 14-3: SAP BW Data Loading Process using Staging BAPIs.

Figure 14-4: Components of PowerCenter Integration Server for SAP BW.

Figure 14-5: Defining Informatica PowerCenter as Data Source Provider in SAP BW.

Figure 14-6: Creating the Source System in SAP BW.

Figure 14-7: Establishing the RFC Definition for the PowerCenter Environment for SAP BW.

Figure 14-8: Testing the Connection between SAP BW and the PowerCenter Integration Server for SAP BW. Connection Time is in Milliseconds.

Figure 14-9: Importing InfoSource Metadata From SAP BW into a PowerCenter Repository as the Target Data Source.

Figure 14-10: Defining Source to Target Data Mapping and Transformations in PowerCenter.

Figure 14-11: PowerCenter Server Manager, Used to Define Sessions and to Monitor and Control Jobs.

Figure 14-12: Starting the PowerCenter Integration Server for BW.

Figure 14-13: Scheduling Data Import Jobs From SAP BW.

Chapter 15: Integrating Third-Party Data Access Products with SAP BW

Figure 15-1: The ODBO Architecture and its Implementation in SAP BW.

Figure 15-2: A Multidimensional Statement Syntax, Actual Query, and Results.

Figure 15-3: SAP BW Objects versus ODBO Schema Objects.

Figure 15-4: Enabling a BEX Analyzer Query to be Visible to the ODBO Consumer.

Figure 15-5: Installing ODBO Components at the Client Workstation.

Figure 15-6: Components of Arcplan inSight Version 2.3.5 to Design Pure Web-Centric Applications against SAP BW.

Figure 15-7: Building an Application using inSight 2.3.5; Defining a New Connection to the SAP BW Data Source.

Figure 15-8: Building a Sales Analysis Analytical Application in inSight.

Figure 15-9: Building an inSight Analytical Application; Defining Data Dependency Relationships among Selected Data Objects.

Figure 15-10: Launching the inSight Application over the Web by using ActiveX Control. You Don't Need an inSight Client, SAP Software, or Microsoft Office on the Client Workstation to Run this Application.

Figure 15-11: SAP BW ODBO BAPIs.

Chapter 16: Managing SAP BW-Performance and Sizing Tuning

Figure 16-1: Data Warehouse Performance Characteristics.

Figure 16-2: Setting up Data Load Performance Parameters in SAP BW 1.2B and SAP BW 2.0A.

Figure 16-3: Changing Buffering of the Number Range Objects.

Figure 16-4: A Data Warehouse Data Volume Growth Pattern.

Figure 16-5: Defining Aggregates against the Customer InfoCube.

Figure 16-6: Defining Aggregates for an InfoCube in SAP BW 1.2B. Initially, When an Aggregate is Created, the Entries in the Calls and Last Displayed Columns are Not Filled in. as Users Use Queries against the InfoCube, SAP BW Automatically Fills Information About Each Aggregate on How Often and When an Aggregate was Used. Never-Used Aggregates Should be Deleted.

Figure 16-7: Defining Aggregates Selection Criteria in SAP BW 1.2B. Here You Select the Characteristics You Want to Include in the Aggregate. This Shows the Characteristics Selected for Aggregate MAX 1 for Customer InfoCube (0SD_C01).

Figure 16-8: Defining Aggregates in SAP BW 2.0. In this Scenario, the Aggregate is Defined for a Specific Product, BIGSCREENTV, because End Users Want to do Extensive Sales Analysis for Large-Screen TVs.

Figure 16-9: Aggregate Usage Statistics.

Figure 16-10: Setting Global Query Read Mode for an InfoCube. Changing Read Mode for an InfoCube Does Not Change Read Mode for all Existing Queries against the InfoCube. This Mode is Applied to Only New Queries.

Figure 16-11: Changing Read Mode for an Existing Query using Transaction RSRT. Note that this Transaction Can be Used to Debug the Query.

Figure 16-12: SAP BW Benchmark Environment.

Chapter 17: The Operational Data Store in SAP BW 2.0

Figure 17-1: SAP BW 2.0 ODS Architecture Compared to its Earlier Version, BW 1.2B.

Figure 17-2: Defining ODS Tables in SAP BW 2.0A. Remember that this Screen Design May Change in SAP BW 2.0B.

Figure 17-3: SAP BEX Analyzer Query Against ODS and Results.

Figure 17-4: Comparing Query Response Time to Access Data From SAP BW ODS.

Figure 17-5: Defining Jump-Target" Scheme to Jump From an InfoCube to an ODS Query or in Reverse.

Figure 17-6: The Administrator Workbench in SAP BW 2.0A and SAP BW 2.0B. The InfoCube Tree Hierarchy No Longer Exists in SAP BW 2.0B. Instead, Both InfoCubes and ODS Objects are Listed Under the Data Targets Tree.

Figure 17-7: Defining New DDS Objects in SAP BW 2.0B. Note that the ODS Design Layout is Very Different From in SAP BW 2.0A, as Shown in Figure 17-2.

Figure 17-8: Getting Detailed Information on ODS Objects in SAP BW 2.0B.

Figure 17-9: Managing Data in ODS Objects.

Appendix A: Data Warehouse Industry References and SAP BW Training

Figure A-1: SAP BW Training Sessions Listed at the SAP Web Site.

Figure A-2: ODBO-Certified Products to Access Data in SAP BW as Listed on the SAP Web Site.

Figure A-3: Staging BAPl-Certified Products to Load Data in SAP BW as Listed on the SAP Web Site.

Appendix B: SAP BW and SAP R/3 Transactions, Tables, and Code Examples

Figure B-1: SAP BW Model for the IC_CUBE02 InfoCube as Described in Chapter 12.

Appendix D: Key Enhancements in SAP BW 2.0

Figure D-1: InfoCube Schemas in SAP BW 1.2B, on the Top, and BW 2.0A, on the Bottom. Notice How the New Star Schema Accounts for Several New SID Tables, Where Each Dimension Characteristic Has Time-Dependent Master Data.

Figure D-2: Administrator Workbench in SAP BW 1.2B. The InfoCubes Tabstrip Lists all Available InfoCubes in a Tree Format Under the InfoCubes Tree Node.

Figure D-3: Administrator Workbench in SAP BW 2.0A and SAP BW 2.0B.

Figure D-4: The BDS Document Management Environment. Assigning a Document to Key Figure ZAMOUNT.

Figure D-5: SAP BW Web Data Access Architecture using SAP Internet Transaction Server (ITS) and an Internet Server.

Figure D-6: SAP BW 2.0 Web-Reporting Architecture and Five-Step Web Reports Publishing Process.

Figure D-7: The SAP BW BEX Query to Publish on the Web.

Figure D-8: Publishing a Query View. The a Step is to Save the Basic Query in SAP BW. The B Step is to Save the View Query as Default View for Publishing over the Web. Here, Sales Revenues (Amount) are Shown by Product (Material). Step C is to Format the Layout of the Result Set using SAP BW Web Publisher.

Figure D-9: The SAP BW Web Publisher Defines SAP BW Web Report Elements Associated with the Query View. The HTML Wizard is Used to Determine How Items are Displayed in the Reports and Associated Navigation Schemes. You Can Have Several Query Views in One HTML Page. After Finalizing the HTML Template, Click Check in to Save the HTML Template in the SAP BW Server (BDS). To Review the Web Report, Click the HTML Browser.

Figure D-10: Viewing an SAP BW Analytical Application over the Web. Note How the Original SAP BEX Query, Shown in Figure D-7, Has been Transformed to Dynamically Perform Data Navigation over the Web.

---

Team-Fly