1106163sapr BW A Stepbystep Guide With Cdrom Fu Biao PDF Download
1106163sapr BW A Stepbystep Guide With Cdrom Fu Biao PDF Download
download
https://ebookbell.com/product/sapr-bw-a-stepbystep-guide-with-
cdrom-fu-biao-22123264
https://ebookbell.com/product/sap-r-3-handbook-third-edition-3rd-
edition-jose-antonio-hernandez-2184246
https://ebookbell.com/product/sap-r3-for-everyone-stepbystep-
instructions-practical-advice-and-other-tips-and-tricks-for-working-
with-sap-6th-ed-mazzullo-22041676
https://ebookbell.com/product/the-sap-r-3-guide-to-edi-and-
interfaces-2nd-axel-angeli-2158844
Common Sap R3 Functions Manual 1st Edition William Lawlor Msc Auth
https://ebookbell.com/product/common-sap-r3-functions-manual-1st-
edition-william-lawlor-msc-auth-4238604
The Sap R3 Guide To Edi And Interfaces Cut Your Implementation Cost
With Idocs Ale And Rfc 2nd Edition Axel Angeli
https://ebookbell.com/product/the-sap-r3-guide-to-edi-and-interfaces-
cut-your-implementation-cost-with-idocs-ale-and-rfc-2nd-edition-axel-
angeli-4603170
https://ebookbell.com/product/testing-sap-r3-a-managers-stepbystep-
guide-jose-fajardo-975610
https://ebookbell.com/product/implementation-strategies-for-sap-r3-in-
a-multinational-organization-lessons-from-a-realworld-case-study-
illustrated-edition-chetan-s-sankar-982010
https://ebookbell.com/product/the-123s-of-abc-in-sap-using-sap-r-3-to-
support-activitybased-costing-1st-edition-dawn-j-sedgley-2136018
https://ebookbell.com/product/rightshore-successfully-sapr-projects-
offshore-1st-edition-frank-thun-auth-4107092
®
SAP BW
A Step-by-Step Guide
The authors and publisher have taken care in the preparation of this book, but make no expressed
or implied warranty of any kind and assume no responsibility for errors or omissions. No liability
is assumed for incidental or consequential damages in connection with or arising out of the use
of the information or programs contained herein.
The publisher offers discounts on this book when ordered in quantity for bulk purchases
and special sales. For more information, please contact:
U.S. Corporate and Government Sales
(800) 382-3419
[email protected]
For sales outside of the U.S., please contact:
International Sales
(317) 581-3793
[email protected]
HF5548.4.B875 F8 2002
650'.0285'5785—dc21
2002066530
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or
transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording, or
otherwise, without the prior consent of the publisher. Printed in the United States of America.
Published simultaneously in Canada.
For information on obtaining permission for use of material from this work, please submit a
written request to:
ISBN: 0-201-70366-1
Text printed on recycled paper
6 7 8 9 10—OPM—070605
Sixth printing, August 2005
To
Xiqiang and Huizhong, our parents
Anna, Biao’s daughter
George, Henry’s son
This page intentionally left blank
Contents
Preface xi
Acknowledgments xix
v
vi • CONTENTS
Index 447
This page intentionally left blank
Preface
Book Objective
This book is a how-to guide. It uses step-by-step procedures with captured
screen shots to illustrate SAP BW’s functionalities. Although the book focuses
on the core SAP BW technology, it also discusses other SAP technologies, such
as Basis, ABAP (Advanced Business Application Programming), and ALE (Appli-
cation Link Enabling) when necessary. It does not, however, discuss third-party
reporting tools and BAPI (Business Application Programming Interface).
Intended Audience
This book is written for BW implementation teams and other individuals who
need a product to understand the data warehousing concept.
Prerequisites
BW is built on the Basis 3-tier architecture and coded in the ABAP language.
ALE and BAPI are used to link BW with SAP systems (R/3 or BW) and non-
SAP systems.
This book, however, does not require readers have knowledge in these
areas. Instead, BW has made the development of a data warehouse so easy that
people with minimal experience in database design and computer program-
ming can use it.
Book Structure
This book is organized into two parts:
xi
xii • PREFACE
The appendices introduce ASAP (Accelerated SAP) for BW, one of the
derivatives of the ASAP implementation methodology developed by SAP, and
give an overview of the Basis 3-tier architecture.
Almost always, you can complete a task in many ways. In such cases, we
will select a strategy that shows better logical dependency.
Caution Due to the differences among BW releases and patches, the screens
in your system may appear somewhat different from the screens illustrated in
this book. BW is becoming more stable, so these differences should be small.
Transaction Codes
In SAP, transaction codes are the technical names of menu items or ABAP pro-
grams. Transactions can be used as shortcuts to screens we want to open. For
example, to start Administrator Workbench, we can either (1) double-click the
menu item Administrator Workbench or (2) type RSA1 in the transaction field
and then click . The transaction field appears in the
upper-left corner of a SAPGUI window.
To display transaction codes for all menu items, in Screen 2.1 select the
menu item Extras ➞ Setting, check the option Display technical names in the pop-
up window as shown in Screen 0.1, and then click to continue.
xiv • PREFACE
Copyright by SAP AG
SCREEN 0.1
Screen 0.2 shows the result. Here transaction codes are displayed at the leaf
level of the menu item tree structure. For example, the transaction codes RSA1,
RRC1, RRC2, RRC3, and RSKC correspond to the menu items Administrator
Workbench, Create, Change, Display, and Permitted Characters, respectively.
Copyright by SAP AG
SCREEN 0.2
To find the transaction code for a particular screen, select the menu item
System ➞ Status of the screen. The transaction code will be displayed in a field
called Transaction.
PREFACE • xv
Legends
BW implements good visual aesthetics. That is, different icons and their colors
represent different objects and their status.
If the legend icon is visible in a screen, clicking it enables us to see the
meaning of each icon in that screen. Table 0.1 provides some examples.
Icons are also used to represent command buttons in BW. Table 0.2 offers
some examples.
TABLE 0.2
FREQUENTLY Icon Command
USED Create
COMMAND
ICONS Save
Delete
Change
Display
Display—change switch
Detail
Check
Activate
Generate
Continue
Cancel
Execute
Refresh
Display table contents
Look up
Enter
Back to the previous screen
xvi • PREFACE
Terminology
BW objects and terms encountered in each chapter are summarized in the last
section of each chapter, not necessarily the first place we use these objects and
terms.
PREFACE • xvii
Copyright by SAP AG
SCREEN 0.3
Many individuals made this book possible, directly and indirectly. In particu-
lar, we want to thank:
Our first complete draft was completed one year ago. Then, when we were
about to send it out for the final review, our laptop was stolen in a hotel break-
fast area, together with the backup CD. Without a hard copy of the draft, we
decided to start all over again. Stacie sent us the original draft of several chap-
ters that she had, and Mary gave us time to recover the loss. Together, they
encouraged us to finish the book.
We learned a hard lesson.
• Our reviewers:
- Capers Jones of Software Productivity Research, Inc.
- Claire Radice of Getronics
- Dr. Guido Schroeder of SAP America
- José A. Hernández of realTech Spain
- Prof. Dr. Peter Cunningham of University of Port Elizabeth, South
Africa
- Dr. Peter C. Patton of Lawson Software
- Todd Levine of Supply Access, Inc.
- Vladimir Berelson of Cap Gemini Ernst & Young
- William S. Girling of Institute for Data Research
They corrected our errors, gave us advice, and proofread the drafts word
by word.
xix
xx • ACKNOWLEDGMENTS
Peer Gribbohm led me to the data warehousing and the SAP BW worlds.
Mike Eames and Shelley Rossell provided me with an SAP Basis and SAP BW
teaching position at PricewaterhouseCoopers (PwC) Global Training Center.
Robert Freeman spent several months with us proofreading and tuning the
book’s language.
Clients offered us project opportunities. Friends and colleagues made these
challenging opportunities a fun experience, and they were always there when
we needed help.
Besides sharing their knowledge with us, they taught us how to tackle tech-
nical problems effectively. These skills helped us enormously, in both our aca-
demic and professional endeavors, after we developed interest in information
technology.
Of course, we are responsible for any errors and omissions. And we will
be glad to hear from any reader who wishes to make constructive comments.
We can be reached at [email protected]
Part
Contents
I
CHAPTER 1 Business Scenario and SAP BW
CHAPTER 2 Creating an InfoCube
CHAPTER 3 Loading Data into the InfoCube
CHAPTER 4 Checking Data Quality
CHAPTER
CHAPTER
5
6
Creating Queries and Workbooks
Managing User Authorization
Guided Tours
1
This page intentionally left blank
Chapter
1
Business Scenario
and SAP BW
3
4 • PART I: GUIDED TOURS
SAP R/3 is an ERP (Enterprise Resources Planning) system that most large
companies in the world use to manage their business transactions. Before the
introduction of SAP BW in 1997, ETTL of SAP R/3 data into a data warehouse
seemed an unthinkable task. This macro-environment explained the urgency
with which SAP R/3 customers sought a data warehousing solution. The result
is SAP BW from SAP, the developer of SAP R/3.
In this chapter we will introduce the basic concept of data warehousing. We
will also discuss what SAP BW (Business Information Warehouse) is, explain
why we need it, examine its architecture, and define Business Content.
First, we use sales analysis as an example to introduce the basic concept of
data warehousing.
Suppose also that you have the data in Tables 1.1 through 1.3 available
about your firm’s materials, customers, and sales organization.
*Prior to January 1, 2000, the Denver office was in the Midwest region.
You also have three years of sales data, as shown in Table 1.4.
6 • PART I: GUIDED TOURS
The data in these tables represent a simplified business scenario. In the real
world, you might have years of data and millions of records.
To succeed in the face of fierce market competition, you need to have a
complete and up-to-date picture of your business and your business environ-
ment. The challenge lies in making the best use of data in decision support. In
decision support, you need to perform many kinds of analysis.
This type of online analytical processing (OLAP) consumes a lot of com-
puter resources because of the size of data. It cannot be carried out on an
online transaction processing (OLTP) system, such as a sales management
system. Instead, we need a dedicated system, which is the data warehouse.
CHAPTER 1: BUSINESS SCENARIO AND SAP BW • 7
FIGURE 1.1
STAR SCHEMA Customer ID
Customer Name Customer ID
Customer Address Sales Rep ID
Material Number
Sales Rep ID*
Per Unit Sales Price
Unit of Measure Sales Rep Name
Customer Dimension Sales Office*
Quantity Sold
Sales Revenue† Sales Region*
Transaction Date
Material Dimension
*Sales Region, Sales Office, and Sales Rep ID are in a hierarchy as shown in Table 1.3.
†Sales Revenue = Per Unit Sales Price ⫻ Quantity Sold.
8 • PART I: GUIDED TOURS
The following steps explain how a star schema works to calculate the total
quantity sold in the Midwest region:
1. From the sales rep dimension, select all sales rep IDs in the Midwest
region.
2. From the fact table, select and summarize all quantity sold by the sales
rep IDs of Step 1.
FIGURE 1.2
ETTL PROCESS Data Warehouse
Load
Transform
Transfer
Extract
Source System
CHAPTER 1: BUSINESS SCENARIO AND SAP BW • 9
name (such as AT&T). The original data might reside in different databases
using different data types, or in different file formats in different file systems.
Some are case sensitive; others may be case insensitive.
In data loading, we load data into the fact tables correctly and quickly. The
challenge at this step is to develop a robust error-handling procedure.
ETTL is a complex and time-consuming task. Any error can jeopardize data
quality, which directly affects business decision making. Because of this fact
and for other reasons, most data warehousing projects experience difficulties
finishing on time or on budget.
To get a feeling for the challenges involved in ETTL, let’s study SAP R/3 as
an example. SAP R/3 is a leading ERP (Enterprise Resources Planning) system.
According to SAP, the SAP R/3 developer, as of October 2000, some 30,000 SAP
R/3 systems were installed worldwide that had 10 million users. SAP R/3
includes several modules, such as SD (sales and distribution), MM (materials
management), PP (production planning), FI (financial accounting), and HR
(human resources). Basically, you can use SAP R/3 to run your entire business.
SAP R/3’s rich business functionality leads to a complex database design.
In fact, this system has approximately 10,000 database tables. In addition to the
complexity of the relations among these tables, the tables and their columns
sometimes don’t even have explicit English descriptions. For many years,
using the SAP R/3 data for business decision support had been a constant
problem.
Recognizing this problem, SAP decided to develop a data warehousing
solution to help its customers. The result is SAP Business Information Ware-
house, or BW. Since the announcement of its launch in June 1997, BW has
drawn intense interest. According to SAP, as of October 2000, more than 1000
SAP BW systems were installed worldwide.
In this book, we will demonstrate how SAP BW implements the star
schema and tackles the ETTL challenges.
1.3.1 BW Architecture
Figure 1.3 shows the BW architecture at the highest level. This architecture has
three layers:
FIGURE 1.3
Non-SAP OLAP Clients
BW
ARCHITECTURE
Business Explorer ODBO
Browser Analyzer
OLE DB for OLAP Provider
ALE/BAPI
Extractor Extractor
PSA (Persistent Staging Area) stores data in the original format while
being imported from the source system. PSA allows for quality check before
the data are loaded into their destinations, such as ODS Objects or InfoCubes.
ODS (Operational Data Store) Objects allow us to build a multilayer struc-
ture for operational data reporting. They are not based on the star schema and
are used primarily for detail reporting, rather than for dimensional analysis.
InfoCubes are the fact tables and their associated dimension tables in a star
schema.
Data Manager maintains data in ODS Objects and InfoCubes and tells the
OLAP Processor what data are available for reporting.
OLAP Processor is the analytical processing engine. It retrieves data from the
database, and it analyzes and presents those data according to users’ requests.
BDS (Business Document Services) stores documents. The documents can
appear in various formats, such as Microsoft Word, Excel, PowerPoint, PDF,
and HTML. BEx Analyzer saves query results, or MS Excel files, as workbooks
in the BDS.
User Roles are a concept used in SAP authorization management. BW
organizes BDS documents according to User Roles. Only users assigned to a
particular User Role can access the documents associated with that User Role.
Table 1.5 indicates where each of these components is discussed in this
book. As noted in the Preface, this book does not discuss third-party reporting
tools and BAPI.
TABLE 1.5
Components Chapters
CHAPTERS
DETAILING BW Business Explorer: Chapter 5, Creating Queries and Workbooks
COMPONENTS • Analyzer and Browser
Non-SAP OLAP Clients Not covered
ODBO
OLE DB for OLAP Provider
Extractor: Chapter 3, Loading Data into the InfoCube, on how
• ALE to load data from flat files
Chapter 10, Business Content, on how to load data
from R/3 systems
Chapter 11, Generic R/3 Data Extraction
BAPI Not covered
Administrator Workbench The entire book, although not explicitly mentioned
BW Scheduler Chapter 3, Loading Data into the InfoCube, on BW
Scheduler
BW Monitor Chapter 4, Checking Data Quality, on BW Monitor
CHAPTER 1: BUSINESS SCENARIO AND SAP BW • 13
Components Chapters
Metadata Repository The entire book, although not explicitly mentioned
Metadata Manager
Staging Engine Chapter 3, Loading Data into the InfoCube
PSA
Chapter 4, Checking Data Quality
ODS Objects Chapter 9, Operational Data Store (ODS)
InfoCubes Chapter 2, Creating an InfoCube
Chapter 7, InfoCube Design
Chapter 8, Aggregates and Multi-Cubes
Data Manager Chapter 12, Data Maintenance
OLAP Processor Chapter 13, Performance Tuning
BDS Chapter 5, Creating Queries and Workbooks
User Roles Chapter 6, Managing User Authorization
Quotation Processing
• Quotation success rates per sales area
• Quotation tracking per sales area
• General quotation information per sales area
Order Processing
• Monthly incoming orders and revenue
• Sales values
• Billing documents
• Order, delivery, and sales quantities
• Fulfillment rates
• Credit memos
• Proportion of returns to incoming orders
• Returns per customer
• Quantity and values of returns
• Product analysis
• Product profitability analysis
14 • PART I: GUIDED TOURS
Delivery
• Delivery delays per sales area
• Average delivery processing times
1.3.3 BW in mySAP.com
BW is evolving rapidly. Knowing its future helps us plan BW projects and their
scopes. Here, we give a brief overview of BW’s position in mySAP.com.
mySAP.com is SAP’s e-business platform that aims to achieve the collabo-
ration among businesses using the Internet technology. It consists of three com-
ponents:
CHAPTER 1: BUSINESS SCENARIO AND SAP BW • 15
• mySAP Technology
• mySAP Services
• mySAP Hosted Solutions
FIGURE 1.4
MYSAP mySAP Technology
TECHNOLOGY
AND MYSAP
Portal Legacy, third-party, or external system
SOLUTIONS
Infrastructure
mySAP E-Procurement
mySAP CRM
mySAP SCM
mySAP PLM
mySAP R/3
Web
Application
Server
Exchange
Infrastructure
Source: Adapted from SAP white paper, “mySAP Technology for Open E-Business Integration—
Overview.”
16 • PART I: GUIDED TOURS
1.4 Summary
This chapter introduced the basic concept of data warehousing and discussed
what SAP BW is, why we need it, its architecture, and what Business Content
is. Later chapters will discuss these subjects in more details.
Key Terms
Term Description
Data warehouse A data warehouse is a dedicated reporting and analysis
environment based on the star schema database design
technique that requires paying special attention to the data
ETTL process.
Star schema A star schema is a technique used in the data warehouse
database design that aims to help data retrieval for online
analytical processing.
ETTL ETTL represents one of the most challenging tasks in building
a data warehouse. It involves the process of extracting, trans-
forming, transferring, and loading data correctly and quickly.
BW BW is a data warehousing solution from SAP.
Next . . .
We will create an InfoCube that implements the Figure 1.1 star schema.
Chapter
2
Creating an
InfoCube
Work Instructions
Step 1 After logging on to the BW system, run transaction RSA1, or double-
click Administrator Workbench.
Copyright by SAP AG
SCREEN 2.1
CHAPTER 2: CREATING AN INFOCUBE • 19
Step 2 In the new window, click Data targets under Modelling in the left
panel. In the right panel, right-click InfoObjects and select Create
InfoArea. . . .
Copyright by SAP AG
SCREEN 2.2
Note: In BW, InfoCubes and ODS Objects are collectively called data targets.
Step 3 Enter a name and a description for the InfoArea, and then click to
continue.
Copyright by SAP AG
SCREEN 2.3
20 • PART I: GUIDED TOURS
Result
The InfoArea has been created as shown in Screen 2.4.
Work Instructions
Step 1 Click InfoObjects under Modelling in the left panel. In the right panel,
right-click InfoArea – demo, and select Create InfoObject catalog. . . .
Copyright by SAP AG
SCREEN 2.4
CHAPTER 2: CREATING AN INFOCUBE • 21
Copyright by SAP AG
SCREEN 2.5
Copyright by SAP AG
SCREEN 2.6
22 • PART I: GUIDED TOURS
Result
Click to return to the previous screen. The newly created InfoObject Cata-
log will be displayed, as shown in Screen 2.8.
Copyright by SAP AG
SCREEN 2.7
CHAPTER 2: CREATING AN INFOCUBE • 23
Work Instructions
Step 1 Right-click InfoObject Catalog – demo: characteristics, and then select
Create InfoObject. . . .
Copyright by SAP AG
SCREEN 2.8
Copyright by SAP AG
SCREEN 2.9
24 • PART I: GUIDED TOURS
Copyright by SAP AG
SCREEN 2.10
Copyright by SAP AG
SCREEN 2.11
CHAPTER 2: CREATING AN INFOCUBE • 25
Copyright by SAP AG
SCREEN 2.12
Copyright by SAP AG
SCREEN 2.14
CHAPTER 2: CREATING AN INFOCUBE • 27
Copyright by SAP AG
SCREEN 2.15
Result
You have now created the characteristic IO_MAT and its attribute IO_
MATNM. A status message All InfoObject(s) activated will appear at the bottom
of Screen 2.14.
Copyright by SAP AG
SCREEN 2.16
INADEQUATE PREPAREDNESS
The more apparent the Entente's "policy of encirclement" and attack
became, the more the means of protecting our welfare should have
been strengthened for defensive reasons. This idea of natural and
justified self-protection, by means of defensive measures against a
possible hostile attack was carried out in a wretchedly inadequate
manner.
Germany's desire for peace, in fact, was unable to develop this
protection by land and sea in a manner compatible with her financial
and national strength and with the risk which our welfare was bound
to run in case of a war. Therefore, we are now suffering not from the
consequences of the tendency toward aggression falsely imputed to
us, but actually from the consequences of a well-nigh incredible love
of peace and of blind confidence.
The entirely different political principles of the Entente have already
been described by me, also our continuous efforts to get upon
friendly terms with the individual Entente nations.
I do not wish to ignore completely the less important work done by
Germany, also included within the framework of politics on a large
scale, which was always inspired by the same purpose: to effect
compromise of existing points of conflict. The Kiel regatta brought us
guests from all the leading nations. We sought compromise with the
same zeal on the neutral territory of sport as in the domain of
science by means of exchange professors, and foreign officers were
most willingly allowed to inspect our army system. This latter might
be adjudged a mistake, now that we can look back, but, in any
event, all these points are certain proofs of our honest desire to live
at peace with all.
Moreover, Germany did not take advantage of a single one of the
opportunities that arose for waging war with a sure prospect of
success.
I have already pointed out the benevolent neutrality of Germany
toward Russia at the time of the Russo-Japanese War.
At the time when England was deeply involved in the Boer War we
might have fought against England or against France, which, at that
time, would have been obliged to forego help from England. But we
did not do so. Also, while the Russo-Japanese War was in progress,
we might have fought not only against Russia, but also against
France. But we did not do so.
In addition to the Morocco crisis already touched upon, in connection
with which we set aside the idea of going to war, we also gave
evidence of our desire for peace by overcoming the Bosnian crisis by
diplomatic means.
When one considers these plainly visible political events as a whole
and adduces the declarations of Entente statesmen such as
Poincaré, Clemenceau, Isvolsky, Tardieu, and others, one is bound to
ask one's self, in amazement, how a peace treaty, founded upon
Germany's guilt in having brought on the World War, could have
been drafted and put through. This miscarriage of justice will not
stand before the bar of world history.
ebookbell.com