Implementation and Upgrade Guide

Efficient

SAP NetWeavef BW

Implementation

and

_Upgrade

Guide

®

Galileo

Press

Acknowledgments

21

Introduction 23

&/ f¥ ^"ASIBttiBB^iXiS

1.1 SAP ECC vs.SAP NetWeaver BW

Implementations

28

1.2 Difference Between OLTP and OLAP

_Systems

28

1.3 SAP NetWeaver BW from A to Z 29

1.3.1 Extraction 30

1.3.2

_Staging

and

_Storage

31 1.3.3 Transformation and Harmonization 32

1.3.4 Presentation 34

1.4 External Data: What is the

_Big

Deal? 35 1.5 Build for the Present,

Keep

an

_Eye

onthe Future 36

1.6

_Dirty

Data 38

1.7 Can't SAP NetWeaver BW Just Clean the Data? 39

1.8

_{Understanding}

SAP NetWeaver BW 40

1.9 Reasonsfor

_implementing

SAP NetWeaver BW 40 1.9.1

_Analytical

_System

Accessfrom the Transactional

(SAP ECC)

System

41

1.9.2 Transitiontoa

Single

Version ofthe Truth 43

1.9.3

Consolidation, Harmonization,

and

Centralization of Information 45

1.9.4 Establishan EDW 47

1.9.5

_{Competitive Advantage}

49 1.9.6 Provide Flexible

_Analysis

ofInformation Assets 49

1.9.7 Business Information to More

_People

in the

Organization

49

1.9.8 The

_Report

is Notthe

_Only

_Output

of

SAP NetWeaverBW

_{Implementations}

51

1.10

_Why

Not Another DataWarehouse? 51

1.10.1 Data Extraction From ECC isMuch Easierwith

SAP NetWeaverBW 51

1.10.2 SAP NetWeaver BW Has

_{Pre-configured}

Business

1.10.3 SAP NetWeaver BW is

_Already

Part of the

_Landscape

53 1.10.4 SAP NetWeaver BWis the Foundation for Most

SAP NetWeaver Products 53 1.11 What SAP NetWeaver BW is Not

_Designed

to Do 54 1.11.1 SAP NetWeaver BW is NotaTransactional

_System

54

1.11.2 SAP NetWeaver BW is Not the

_Only

_{Reporting System}

... 56 1.11.3 SAP NetWeaver BW is Not

_Usuaily

_Updated

in

Real Time 56

1.11.4 BW is NotaSilverBullet 57

1.12 SAP

_{BusinessObjects Capabilities}

58

1.13

_Ingredients

foraSuccessful SAP NetWeaver BW

_Project

Manager

59

1.13.1 Cood Communication Skills 60

1.13.2

_Knowledge

ofSAP NetWeaver BW and Data

Warehousing

61

1.13.3

Knowfedge

ofBusiness Processes and

_Ana/ysfs

Goa/s 63

1.13.4 The Need for Political

_Savvy

64

1.13.5

_Highly

_Organized

and

_Quality

Minded 65 1.13.6

_Willing

and Ableto

_Develop

and Enforce Standards 65

1.13.7 Team

_Building

66

1.13.8

_{Budget Accountability}

67

1.13.9

_Willing

to

_Say

Both "Yes" and "No" 67

1.14 Conclusion 68

•

IlllöiJ

2.1

_Defining

an

Upgrade

_Strategy

71

2.2 SAP NetWeaver BW

_{Implementation}

_Approach

72

2.3 SAP NetWeaver BWHardware

_Sizing

73

2.4

_{Landscape Strategy}

74

2.4.1 Insiston aSand box

_System

75

2.4.2 Think About the

_Training

Environment 78 2.4.3

_Adding

a Production

Support System

80 2.4.4

_Keep

_Development,

QA, Production Environments

in

_Sync

81

2.4.5 Assess New Phases of

_Development

82

2.5

_{Upgrade Landscape}

86

2.6.1

Develop

and Communicate the

_Transport

Path 88 2.6.2

_{Implement Transport Approval}

Processfrom the

Beginning

90

2.6.3 Make SureEach

_Developer

Locks

_Objects

90

2.6.4

_Transport

Steward Process 91

2.6.5

_{Keep aThorough Log}

of

Transports

92 2.6.6

_Develop

a Processfor

Troubleshooting

Failed

Transports

92

2.6.7 Some

_Objects

will be

_Changeable

94

2.6.8

_Transport

_Organizer

Tool 96

2.7 New Release Rollout

_Strategy

_Challenges

97

2.7.1

_Timingof

SAP NetWeaver BWRollout 98

2.7.2 Rollout

_Scope

98

2.8

_Upgrade

Rollout

_Strategy

99

2.8.1

_Timing

99

2.8.2 Features and

Functionality

99

2.8.3

_Upgrade

_{Testing Strategy}

100

2.8.4

_Upgrade

_Change

_{Management Strategy}

100

2.9 Database

_Strategy

100

2.10 EDWand Global

_{Rollup Strategies}

101

2.11

_{Report Strategy}

104

2.11.1

_{Query Strategy}

104

2.11.2 Visual

_Composer

107

2.11.3 Web

_Template

Strategy

108

2.11.4 SAP

_{BusinessObjects Strategy}

109

2.12 Support

Package

Strategy

109

2.12.1 Recommendation 110

2.12.2 Front-End

_Support

_Packages

111

2.13 Authorization

_Strategy

112

2.13.1 SAP NetWeaver BW

_Security

112

2.13.2 Authorizations for

_Upgrade

to NW2004s 113

2.14 Conclusion 114

3.1 Unclear Definition of Goals and

_Scope

115 3.1.1

_Develop

Clear

_Project

_Scope

Documentation 115

3.1.3 Avoid

_{Scope Creep}

118 3.1.4 Establisha

Scope

Change

Control Process 119

3.1.5 Take

_Advantage

of

_{Existing Legacy Systems}

119

3.2 Over-Ambitious

_Scope

120

3.2.1 StartSmall 120

3.2.2 Be

_Wary

of

_Implementing

SAP NetWeaver BW at

the SameTime as SAP ECC orSAP R/3 121

3.3 UnrealisticTime Line 123

3.3.1 Don't

_Forget

the Time for Documentation and

_Training

... 124

3.4 Governance 126

3.5 Communication Issues 129

3.5.1 Insist on

_Weekly

Status

Reports

130

3.5.2

_Encourage

Informal Discussion 130

3.5.3 Locate

_Centrally

130

3.5.4 Centralize Issues Listand Use It 130

3.6

_Ownership

Issues 131

3.6.1 Insist on

_Signoff

of Documents 132

3.6.2 Have the Power Users

_Develop

the SAP NetWeaver

BW Queries 132

3.7 Data

Quality

Issues 133 3.7.1 Don't

_{Completely Rely}

onthe Source

_Systems

to

Ensure Data

_Quality

135

3.7.2 Establish Active Governanceof Data 136 3.7.3 Don't Keep Data Mismatch Issues

_Open

for

_Long

Time ... 136

3.7.4

_Leverage

the SAP

_{BusinessObjects}

Data Services Tool 137 3.7.5 Turn toa

Third-Party

to

Help

with Validation 138

3.8 Data

_Alignment

Issues 139

3.8.1 Master Data

_Alignment

139

3.8.2 Transactional Data

_Alignment

142

3.9 Data

_Realignment

143

3.9.1

_Realignment

Without Reload-Is It Possible? 144

3.9.2

_Remodeling

Toolbox 145

3.10 Performance Issues 147

3.10.1 Establish Clear Goals forPerformance 147

3.10.2 Measure

_Against

the Performance Goals viaStat/stics

InfoCubes 150

3.10.3 Establish a Performance Sub-Team 150

3.10.4

_{Keep Up-to-Date}

on

Support

Packages

151

3.10.5 DataModel for Performance 151

3.12 Resource Issues 155 3.12.1 Insist onthe Best, Not Just the Most Available 155

3.12.2 The

_{Consultant-Heavy}

_Project

156

3.12.3 Insiston

_Interviewing

All Candidates 157

3.12.4 Transition OutBad Consultants 157 3.12.5 AvoidConflict Between

_Consulting

Partners, SAP,

and Others 158

3.12.6 SAP R/3 or SAP ECC Basis

_Experience

isNot

SAP NetWeaver BW

_Experience

159

3.12.7

_Keep

the

_Project

Team

_Physically

_Together

159

3.13 Political Issues 160

3.14 Over-Customization 160

3.14.1 Determine Ifthe Customization Can Take Place

Outside of SAP NetWeaver BW 161

3.14.2

_Develop

a

"Why

not SAP?"

Approach

162

3.14.3 Know Where

_Many

SAP NetWeaver BW

_Projects

Use

_Third-Party

Tools 162

3.14.4 Validation Tools 166

3.15

_Meeting

and Decision

_Paralysis

167

3.15.1 Slow Decision

_Making

167

3.15.2 The

_Lonely

SAP NetWeaver BW Team 167 3.15.3 The

_Populär

SAP NetWeaver BW Team 168

3.15.4 What Can beDone? 168

3.16

_Change

Control and

_Change

_Management

169

3.16.1

_Change

Control 170

3.17

_{Analyze Organization}

User

_{Groups Using}

Different

_Reporting

Tools 173

3.18 Conclusion 174

4.1 The DataWarehouse

_Lifecycle

178

4.2 The

_{Upgrade Lifecycle}

180

4.2.1 What's New in NW 2004s SAP NetWeaver BW

System?

181

4.2.2

_Upgrading

onthe

Existing

SAP NetWeaver BW

Landscape

183

4.2.3 Dedicated

_{Upgrade Landscape}

184

4.2.5 Obsolete Queries 186

4.2.6

_Upgrade

Cutover 187

4.2.7 How

_Long

Will This Take? 188

4.2.8 When Should I

_Upgrade?

190

4.3

_Project

Charter 191

4.4 DetailScope Documentation 192

4.4.1 What Isa Stakeholder? 192

4.4.2 Stakeholder Document 193

4.4.3 Communication Plan Document 193

4.4.4

_{Integrated Project}

Plan 193

4.4.5

_Naming

StandardsDocument 194

4.4.6 SAP NetWeaver BW

_Development

Standards

Document 195

4.4.7 OtherDocuments 196

4.5

_Planning

for Information

_Lifecycle

_Management

196 4.6

_Typical

Roles Needed foran SAP NetWeaver BW

Project

197

4.6.1 SAP NetWeaver BW

_{Project Manager}

198 4.6.2 SAP NetWeaver BW Business

_Subject

Matter

_Expert

199 4.6.3 SAP NetWeaver BW DataArchitect 200 4.6.4 SAP NetWeaver BW

_{Applications Developer}

202 4.6.5 SAP NetWeaver BW Presentation

_Developer

203 4.6.6 SAP NetWeaver BW Basis

_Developer

204

4.6.7 ABAP

_Developer

205

4.6.8 SAP Portal Consultant 206

4.7

_Staffing

aSAP NetWeaver BW

Project

207

4.7.1 SmallSAP NetWeaver BW

_Project

208

4.7.2 Medium-Sized SAP NetWeaver BW

_Project

210

4.7.3

_Large

SAP NetWeaver BW

_Project

211 4.7.4

_Large

Global SAP NetWeaver BW

_Project

213 4.8

_Outsourcing

and SAP NetWeaver BW 215

4.8.1 When Does

_Outsourcing

Work? 217

4.9 SAP NetWeaver BW Interview Process 217

4.10

_{Training Requirements}

222

4.11 Conclusion 223

5.1

_Requirements

_Gathering

226

5.1.2 IsAll Data in SAP ECC or SAP R/3 or in

Multiple

Systems?

229

5.1.3 Is

_Intra-Day

orReal-Time

Reporting

Needed? 229

5.1.4 What Else Do You KnowAbout the

_Requirement?

230 5.2 Information

_Request

Form 232 5.3

_Gathering

a

Report Inventory

232

5.4 Functional Model Document 234

5.4.1 How

_Many

Functional Model Documents are Needed? ... 236

5.4.2 Sectionsof the Functional Model Document 237 5.5 SAP NetWeaver BW

_{Key Figure}

or KPI Matrix 243

5.6

_Steps

to Obtain SAP NetWeaver BW Star Schema Model

from the KPI Matrix 244

5.6.1

_Step

1: Determine Business

_Subjects

244 5.6.2

_Step

2:

_Assign

Business

_Subjects

to

_{Key Figure}

245 5.6.3

_Step

3: Determine

_Strang

Entities and

_Granularity

245 5.6.4

_Step

4 Join Similar

_{Key Figures}

245 5.7

_Budgeting

or

Estimating

SAP NetWeaver BW Time Lines 246

5.8 SAP NetWeaver BW

_Physical

Model 252

5.9 BusinessContent Evaluation 255

5.9.1

_{Key Figure (Top}

Down)

Approach

255

5.9.2 Data Source(Bottom

_{Up) Approach}

256 5.9.3 BusinessContentas a

LearningTool

256 5.9.4

_Evaluating

Business ContentforYour Needs 258 5.9.5

_Using

aSubset of the Business Content 261

5.10

_Design

Reviews 261

5.10.1 Functional Model Review 262 5.10.2

_Conceptual

and

_Physical

ModelReview 263

5.10.3 DataModel and

_System

Review 263

5.10.4 Final Check 263

5.11 Conclusion 264

6.1

_Extracting

and

_Loading

Datafrom SAP Source

_Systems

266

6.1.1 Service API DataSources 267

6.1.2 Generated DataSources 270

6.1.3 Generic DataSources 270 6.1.4 Custom AB AP DataSources 272

6.1.5

_Filling

In

_Missing

Data in Extractions 272 6.1.6

_Testingthe

DataSources 275 6.2

_Loading

Data from Non-SAP Source

Systems

276

6.2.1 Fiat File Interfaces 276

6.2.2 DBConnect 278

6.2.3 UDConnect 280

6.2.4 XML Interfaces 280

6.2.5 ETL Interfaces 281

6.3

_Extracting

Data From the SAP NetWeaver BW

_System

281 6.4

_Loading

and

_Transforming

Data into SAP NetWeaver BW 283

6.4.1 Transformationand

_Mapping

ofData in

SAP NetWeaver BW Version 3.x 284

6.4.2 Transformation and

_Mapping

of Data in NW 2004s 288

6.4.3 Start Routines 289

6.4.4 End Routines 290

6.4.5

_Expert

Routines 291

6.4.6

_{ImplementingTransformations}

291

6.4.7

_Auditing

Transformations for

_Efficiency

292 6.4.8

Converting

from Version 3.x to NW 2004s

Transformations 292

6.4.9 InfoSource 295

6.5

_Appending

or

Changing

Standard SAP NetWeaverBW

Objects

... 296

6.6

DataModeling

297

6.6.1

_Loading

intoan DSO or ODS 297

6.6.2 Create aConsolidation

Layer

for Data 298

6.6.3 ExtractOnce, Use

_Many

Times 299

6.6.4 Write

_Optimized

DSO 300 6.6.5 Use the

_{Right Object}

for the Job 301 6.7

_Designing

Process Chains 303

6.8 Issue Resolution and Issue

_Tracking

303

6.8.1

_Reporting

Issues via SAP's Service

_Marketplace

304

6.8.2

_Response

_Delays

304

6.9

_Query

Performance

_Analysis

in SAP NetWeaver BW 305

6.9.1 DataModel Does Not Fitthe DataVolume 305

6.9.2 Poor

_Query

Definition 306

6.9.3 Lack of

_Aggregates

307

6.9.4 OLAP Cache 309

6.9.5

_Partitioning

Not Set 313 6.9.6 DatabaseStatistics Not

_Up-to-Date

314

6.9.7 Virtual Characteristics and

_{Key Figures}

314

6.9.8

_{Time-Dependent}

Master Data 315

6.9.9

_Complex

Authorizations 317

6.9.10 NW 2004s Bl Accelerator 318

6.10 Conclusion 318

7.1 DataModeland

_System

Review 322 7.2

_Documenting

SAP NetWeaver BW

_{Configuration}

324 7.2.1 SAP NetWeaver BW Functional Model Document 324 7.2.2 DataStore

_{Object/Operational}

Data Store (DSO/ODS)

Technical

_Design

Document 324 7.2.3 InfoCube Technical

_Design

Document 325 7.2.4 Extraction,

Transformation,

and

_Loading

(ETL)

Technical

_Design

Document 325

7.2.5 The MetaData

_Repository

326

7.3 SAP NetWeaver BW Document

_Management

Tool 328

7.4 SAP Solution

_Manager

329

7.5

_{Transport Management}

in SAP NetWeaver BW 330 7.5.1 SAP NetWeaver BW

_Transport

_Management

System Tips

332

7.5.2 GeneralSAP NetWeaver BW

_{Transport Tips}

333 7.5.3

_Separate

SAP NetWeaver BW

_Transports

into

Logical

Groups

333

7.5.4

_Keep

Careful Watch of

_{Transports—Take}

Good Notes 335

7.5.5 Never Leave a

Transport

Behind 335

7.5.6 Final Cutover

_Recapture

of

_Transports

336

7.5.7 The MockCutover 337 7.6

_Testing

in SAP NetWeaver BW 337 7.6.1

_Develop

at SAP NetWeaver BW Test Plan 337 7.6.2

_Developing

Test

_Scripts

for SAP NetWeaver BW 338 7.6.3 Automated

_Testing

Tools 340

7.7

_{Organizational Change}

_Management

341

7.7.1

_Training

341

7.7.2 A

_{Separate Training System}

341

7.7.3 Do I

_Really

Need Hands-On

_Training?

342

7.8 Cutover

_Planning

343

7.9 Go-Live Checklist 345

7.10 Run Initial Loads in SAP NetWeaver BW 347 7.10.1 Create and Schedule Process Chains in

SAP NetWeaver BW 348

7.10.2 Schedule SAP ECCJobs 350

7.10.3 Portals and SAP NetWeaver BW 352

7.10.4

_Developing

a Portal

Strategy

353

7.11 SAP

_Safeguarding

Service for SAP NetWeaver BW Go-Live 356

7.12 Conclusion 356

8.1

_{Post-Implementation}

Review 357 8.2

_Building

aProduction

_Support

Center ofExcellence (COE) 358 8.3

_{Transitioning}

from SAP NetWeaver BW

_Development

to

Production-Support

COE 360

8.3.1 Transition the

_Knowledge

360

8.3.2 Determine MeasurementCriteria 361

8.4

_Ongoing

SAP NetWeaver BW Reconciliation and Validation 365 8.4.1

_Develop

a Reconciliation

Strategy

365

8.4.2

_Reconciling

the Datato SAP ECC orSAP R/3 367 8.4.3

_Reconciling

Data to External

_Systems

369 8.5 PeriodicJobs to Run inan SAP NetWeaver BW Environment 369

8.6

_Develop

an

Ongoing

SAP NetWeaver BW

Support Package

Strategy

372

8.6.1 Frontend

_Support

_Packages

374

8.6.2 Conducta Lessons-Learned Session 375

8.7

_Retaining

and

_AAotivating

Stafffor Future Rollouts 377

8.8

_Prepare

forFuture Rollouts 378

8.9 Conclusion 378

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^H

9.1 Introduction to Six

_Sigma

379

9.1.1

_History

379

9.1.2 Definition 379

9.1.4 Six

_Sigma

_{Terminologies}

380

9.1.5 Basic Statistics 383

9.2 Reasonsto

_Implement

Six

_Sigma

in anSAP NetWeaver

BW

_Project

386

9.2.1 Six

_Sigma

isa Pro-Active

_Approach

386

9.2.2

_Talking

in Customer's

_Language

386

9.2.3

_High

level ofCorrectness 386

9.2.4

_{Happy Strategie}

Users —A Foundation for New

Business

_{Opportunities}

386

9.3 Phase 1: Define 387

9.3.1 Voice ofCustomerand Voice of Business 387

9.3.2 Criticalto

_Quality

(CTQ)

387

9.3.3 CTQTree 388

9.3.4

_Project

Charter 388

9.4 Phase 2:Measure 390

9.4.1 SIPOC-

Supplier

Input

Process

Output

Customer 390

9.4.2

_Analyze

Process — Fishbone

Diagram

392

9.4.3 Cause and

_{Impact Analysis}

392

9.5 Phase 3:

_Analyze

393

9.5.1 Pie Chart 393

9.5.2 Bar Charts 393

9.5.3 ParetoChart 394

9.5.4

_Histogram

and Box Plots 395

9.5.5 Conclusion of

_Analyze

Phase 397

9.6 Phase 4:

_Improve

398

9.6.1

_BrainWriting

398

9.6.2 Brain

_Storming

398

9.6.3 Selectand

_Implement

Ideas 399

9.7 Conclusion 399

10.1 SAP +

_{BusinessObjects}

401

10.2 SAP NetWeaver BW Presentation

_Layer

402

10.2.1 SAP NetWeaver BW Standard BEx

_Reporting

403 10.2.2

_Reporting

with SAP

_{BusinessObjects}

403 10.3 SAP

_{BusinessObjects}

Installation Guides 405

10.3.1 SAP

_{BusinessObjects}

_Enterprise

Server Installation 406

10.3.2 SAP

_{BusinessObjects}

Client Installation 406 10.4 OLAP Universe

_Design

Based onSAP SAP NetWeaver BW 407

10.4.1

_Creating

OLAP Universe Based onSAP NetWeaver

BWQueries 408

10.4.2

_Setting

OLAP Universe Generation

_Options

411

10.4.3

_Customizing

OLAP Universe 413

10.4.4

_Leveraging

SAP NetWeaver BW

_Query

Variablesin

Universe 416

10.4.5 OLAP Universe: BestPractice and Guidelines 417 10.5 Web

_Intelligence

_{Report Design}

on Universe 418 10.5.1 In Which Scenario Can Web

_Intelligence

be Used? 418 10.5.2

_Creating

aWeb

Intelligence Report

418

10.5.3

_Exporting

Web

_Intelligence

_Report

in

_Enterprise

CMS .... 420

10.5.4 Define Alert inWeb

_Intelligence

_Report

420 10.5.5

_Accessing

Web

_Intelligence

_Reports

from JnfoView 421 10.5.6

_Opening

and

_Saving

Web

_{Intelligence Report}

in

Different Modes within InfoView 422 10.5.7

_Displaying

Track

_Changes

in Web

_{Intelligence Report}

423 10.6

_Query

asaWebService (QaaWS) 424

10.6.1

_Starting

QaaWS Tool 424

10.6.2

_Steps

for

_Creating

aNewQaaWS 425

10.6.3 Business Scenarios Where QaaWS is

_Required

426 10.6.4

_{Implementation}

Best Practicefor QaaWS 427

10.7 Xcelsius 427

10.7.1 Different

_Types

of Flavors to Suite Your Need 427

10.7.2

_Creating

a

Simple

Xcelsius

Application

Based on

QaaWS 428

10.7.3 Xcelsius Best Practices 431

10.8 Microsoft Office

_Integration

with Live Office 432 10.8.1 Live Office Ribbon within Microsoft Office

Applications

433

10.8.2

_Logging

in SAP

_{BusinessObjects}

_Enterprise

from

Live Office 434

10.8.3

_Inserting

_Crystal

_Reports

Content in Live Office

Document 434

10.8.4

_fnserting

Web

_Intelligence

Content in Live Office

Document 435

10.9

_Crystal

_Reports

4-37 10.9.1

_{Crystal Reports Connectivity Options}

with SAP 437 10.9.2 SAP Toolbar in

_Crystal

_Reports

438 10.9.3 General

_Steps

to Create A

_Simple

_Report

Based

on SAP NetWeaver BW

Query

438

10.9.4

_{Crystal Reports}

Best Practices 439 10.10_{Information Discovery}with Polestar 439

10.10.1 What isInformation

_Space?

440

10.10.2

_Accessing

Polestar 440

10.10.3

_Creating

_Space

440

10.10.4 Information Search Features in Polestar 442 10.10.5 Guidelines and Best Practicesfor Polestar 443 10.11 Pioneer: The Best ofthe Both Worlds 443 10.12 Other Tools Provided

_by

SAP

_{BusinessObjects}

445 10.12.1 SAP

_{BusinessObjects}

DataServices 445 10.12.2 SAP Business

_Objects

Bl

_Widget

445

10.12.3

_Voyager

446

10.12.4 SAP

_{BusinessObjects}

Data Federator 446 10.12.5 SAP

_{BusinessObjects LifeCycle}

_Manager

446

10.13

_Summary

447

Bffl^^w

mSI

11.1

_Usingthis

Book 449

11.2 CommonIssues and

_Challenges

450

11.3

_Important

_Things

to Remember 450 11.3.1 More

_Challenging

than an ECCor R/3

_Project

450

11.3.2

_Management

Commitment Needed from the

Beginning

451

11.3.3

_{Project Management: User-Focused,}

Not

_Technology

Focused 451

11.3.4 Clear

_Methodology

Needed to Determine

Requirements

451

11.3.5

_{Understanding}

Data LoadVolume and

_Granularity

451

11.3.6

_{Manage Expectations}

for BW 452

11.3.7 Fix Bad Dataat Its Source 452

11.3.9 When the BW

_System

IsLive, the Solution Isn't

Finished 452

11.4 Conclusion 452

A

_{Sample Project}

Plan 455

B

_Important

Checklists 473

C Document

_Templates

487

D Common Issues When

_Upgrading

from SAP NetWeaver BW

Version 3.xto NW2004s 505

E

_Sample

SAP NetWeaver BW

_Naming

Standards Document 511

F SAP NetWeaver BW

_Integration

Test

_Script

515

G

_Bibliography

519

H TheAuthors 521