Strategies, Techniques,

and Best Practices to

Upgrade, Copy, and
Migrate SAP BW Systems
Ron Silberstein
SAP
What We’ll Cover …
SAP Business Information Warehouse
(BW) upgrade

SAP BW Unicode migration

SAP BW system copy

Wrap-up
What We’ll Cover …
SAP BW upgrade

SAP BW Unicode migration

SAP BW system copy

Wrap-up
Overview
SAP BW upgrade
Enterprise Data Warehousing and SAP BI

Foundations and requirements

Upgrade and the system landscape
Alpha conversion
Prepare and upgrade
Overview
SAP BW upgrade
Enterprise Data Warehousing and SAP BI

Foundations and requirements

Upgrade and the system landscape
Alpha conversion
Prepare and upgrade
 SAP BI Overview – Release Upgrade Strategy

Information on SAP BI release strategy:

End of Regular
Delivery Maintenance
SAP BW 2.0B (GA)

SAP BW 2.1C (GA)

SAP BW 3.0B (GA)

SAP BW 3.1 (SAP BI 3.3) (GA/UrS)

SAP NetWeaver ’04

SAP BW 3.5 (UrS)

time
Aug Dec Jun Nov Mar Dec Dec Mar
2000 2000 2002 2002 2004 2005 2006 2013
© SAP AG 2005, 6
 Upgrading to SAP BI 3.5 – Upgrade Paths

Upgrade from supported releases SAP BW 2.x, SAP BW 3.x, SAP BI

3.1 Content, and BI Content Add-on 3.2 and 3.3 available
Direct Release Upgrade possibilities…

Full Release Add-On Delta

Upgrade upgrade
Components:

Components: BI_Cont 352

BI Content 3.3 SAP_BW 350

BI Content 3.2 BI_Cont 351
BW 3.1 Content
SAP BW 3.0B SAP_BW 350
SAP BW 2.1C
SAP BW 2.0B

Content release Content releases underlying technical release

© SAP AG 2005, 7
 Upgrading to SAP BI 3.5 – Basis/Web AS Viewpoint

Upgrade of underlying Basis/Web Application Server (AS) release

to Web AS 6.40
Direct upgrade possible from Basis 4.6x
Important reminder:
SAP BW’s Web AS is not a separate instance, installation, or optional!!

Full Release Upgrade

(SAP BW and Web AS) Add-On Delta Components:
upgrade
BI_Cont 352

Components: SAP_BW 350

Web AS 6.40
BI_Cont 351
BI Content 3.3
BI Content 3.2 SAP_BW 350
BW 3.1 Content
BW 3.0B Web AS 6.40
BW 2.1C
BW 2.0B
Web AS 6.20
Basis 4.6D
Basis 4.6C

© SAP AG 2005, 8
 Upgrading to SAP BW 3.5 – Upgrade Paths

The upgrade to SAP BW 3.5 is a full technical upgrade

The SAP BW system, SAP BI Content add-on*, and

underlying Web AS system is upgraded

Customer experiences with upgrades indicate that SAP BW 3.5

upgrade runtime results are very similar to the runtimes for
prior SAP BW 3.x upgrade runtimes:

Upgrade runtimes

From To From To
SAP BW 3.x -> 3.5.x = SAP BW 3.0B -> 3.1
SAP BW 2.x -> 3.5.x = SAP BW 2.x -> 3.1

Minimum downtime 1~2 hours [downtime-minimized strategy]

Upgrade runtime determined by CPU and I/O speed (not size)

* If already installed (SAP BW 3.1 or greater)

© SAP AG 2005, 9
 SAP BW 3.5 Upgrade Requirements –
SAP BW System Requirements

SAP BW System requirements for upgrade:

SAP BW System 2.0B 2.1C 3.0B 3.1/3.2/3.3
Basis Kernel version Latest version Latest version Latest version Latest version
4.6D^ 4.6D^ 6.20 (173+) 6.20(173+)
SAP_BW Support SP 8 or greater SP 1 or greater SP 16 or SP 9 or greater
Package greater
SAP_BASIS Support Latest Latest Latest (32 or >) Latest (32 or >)
Package (23 or >) (12 or >)
SAP_ABA Support Latest Latest Latest (32 or >) Latest (32 or >)
Package (23 or >) (12 or >)
PI_BASIS 2003_1_620 N/A N/A SP 4 OR > SP 4 OR >
SPAM/Saint Patch lvl SAPKD0040/32 SAPK0050/33 SAPKD62015 SAPKD62015
(4.6C) (4.6D) (6.20) (6.20)
EPx.0/WP plug-in* Version 6.00 Version 6.00 Version 6.00 Version 6.00

Executable versions (min): • PREPARE now checks the versions of executables

tp OS/390: 320.56.57
All other tps: 320.56.56 ^ See SAP Note 318846 for Kernel (upgrade) installation info
R3trans: 09.07.2002 * See SAP Note 655941 for Plug-in upgrade info

Source: SAP note 658992 • Note: All recommended OS patches/patchsets should be

© SAP AG 2005, 10 applied. See specific OS/DB SAP notes for details.
 SAP BW 3.5 Upgrade Requirements – Plug-in (PI)
Requirements

Source system Plug-ins/Service APIs (SAP SMP alias R3 Plug-In)

PI-2004.1, PI-2003.1, or PI 2002.1 is required for SAP BW 3.5
PI-2004.1 is required for new BI 3.5.2 content and BI 3.5.3 extractors
Latest PI patch level is recommended
PI-2003.1 is in mainstream maintenance until Jun 2005

Key tip: Source system plug-in can be the longest timeline in an upgrade project
Plan accordingly!
Plug-In/ Release SP level 3.1I/SP 4.0B/SP 4.5B/SP 4.6B/SP 4.6C/SP 4.7/SP

PI 2004.1 SP/HR SP 38 SP 19 SP 3 SP 1 SP 0
(SP lvls to be confirmed B2/C9 PI_Basis
Check SAP notes) 2004_1_620
PI 2003.1 SP/HR SP 38 SP 16 SP 3 SP 1 SP 0
B0/B4

SAP notes of interest:

704564 (R/3 plug-in: PI 2003.1 installation/delta upgrade) for details on
actions upgrading your plug-in version
704566 (Add-On Support Packages and CRTs for PI 2004.1)
614603 (Skipping releases during R/3 upgrade (jump upgrade))
701179 (Composite SAP BW-BCT note: PI 2004.1 Upgrade)
© SAP AG 2005, 11
Overview
SAP BW upgrade
Enterprise Data Warehousing and SAP BI

Foundations and requirements

Upgrade and the system landscape
Alpha conversion
Prepare and upgrade
 Upgrade Prep: SAP BW 3.x Landscape and the Web
ITS

SAP BW 2.0
• Mainly used for Web-enabling
existing SAP applications
• Dynpro-based
Web
• SAP BW used ITS only as a
Server. ITS
gateway (WEBRFC)
• ITS Flow Logic was only used
in special cases

HTTP
WEB SAP BW 3.0 with mySAP Web AS
Browser mySAP Web AS
• Enhanced scalability,
technology
performance, and robustness
• Generation of charts and maps
on Internet Graphic Server (IGS)
• Support of background
processing
IGS • Generation of mobile reporting
types in SAP BW server
• Easy administration

© SAP AG 2005, 13
 IGS Installation and Requirements

If you are upgrading from BW 2.x, you must install

the Internet Graphics Service (IGS) before the Web
template conversion

The IGS is used in SAP BW to create graphics

(charts and maps)

You can find more information on configuring

IGS on the Server component CD and in the IMG
(transaction SPRO)
Communication between SAP BW and IGS is via RFC

All MIMEs and customer-owned CSS stored on the

ITS should be transferred to the MIMEs Repository

For IGS known bugs and solutions, see

OSS Note 459674

© SAP AG 2005, 14
 The IGS Landscape for SAP BW

HTTP
BW 3.x
Internet
Web AS

RFC/HTTP
RFC
HTML +Java

Chart-
Engine

IGS GIS
Engine

EP 5.0
SAP Dialog-Protocol and Automation-
Calls
HTTP Protocol, for HTML, JavaScript, Java
Applets, etc.
External system

The user never calls IGS directly; graphics generation is server : server
© SAP AG 2005, 15
 IGS Installation and Upgrade:
Distributed Architecture – Standalone

disp disp disp

disp disp disp

ICM

ICM

ICM
WP
WP

WP

WP
WP

WP

WP
WP

WP
SAP BW System RFC Dest

System boundaries* RFC HTTP

Network RFC HTTP
Listener Listener
Listener Listener
Communication component
Data conversion (syntax)
MUX
Data interpreter (semantics) MUX
Multiplexer
Component Multiplexer
Workload-balancing check

PW PW PW
PW PW PW
Portwatcher Portwatcher Portwatcher
Portwatcher Portwatcher Portwatcher

SAP BW SAP BW
SAP BW SAP
ChartBW Interpreter
Interpreter Zip Interpreter
Chart Interpreter Chart
Interpreter for GIS Zip Interpreter
Chart Interpreter Interpreter for GIS
Chart Chart
Chart Chart Geocoder Zipper
Control Control Geocoder Zipper
Control Control

© SAP AG 2005, 16
 IGS Installation and Upgrade: Distributed Architecture
– Application Server Installation
System boundaries*
Network
MS
MS Note: On different
Communication component CI
Data conversion (syntax) application
Data interpreter (semantics) servers!
Component
Workload-balancing check

disp disp
disp disp
ICM

ICM
WP
WP

WP

WP
WP

WP
RFC Dest RFC Dest

RFC HTTP RFC HTTP

RFC HTTP RFC HTTP
Listener Listener Listener Listener
Listener Listener Listener Listener

MUX MUX
MUX MUX
Multiplexer Multiplexer
Multiplexer Multiplexer

PW PW PW PW PW PW
PW PW PW PW PW PW
Portwatcher Portwatcher Portwatcher Portwatcher Portwatcher Portwatcher
Portwatcher Portwatcher Portwatcher Portwatcher Portwatcher Portwatcher

SAP BW SAP BW Interpreter SAP BW SAP BW Interpreter

SAP BW SAP
ChartBW Interpreter Zip Interpreter SAP BW SAP
ChartBW Interpreter Zip Interpreter
Chart Interpreter Chart for GIS
Interpreter Zip Interpreter Chart Interpreter Chart for GIS
Interpreter Zip Interpreter
Chart Interpreter Interpreter for GIS Chart Interpreter Interpreter for GIS
Chart Chart Chart Chart
Chart Chart Geocoder Zipper Chart Chart Geocoder Zipper
Control Control Geocoder Zipper Control Control Geocoder Zipper
Control Control Control Control
© SAP AG 2005, 17
 SAP BW 3.5 Upgrade Requirements – IGS Chart
Migration
Converting chart settings (BLOB to XML)
The conversion of chart settings is mandatory when you used charts in SAP BW Web
applications and you upgrade to SAP BW 3.5 see Upgrade Guide
All SAP BW 3.5 customers upgrading from SAP BW 3.x should execute this
conversion directly after the upgrade
Conversion requires a Windows-based IGS 6.40

All chart settings of your systems are converted:

Chart settings of chart items that are stored
in a library for reuse purposes
Local chart settings of SAP BW Web applications
Chart settings that are saved as bookmarks

Web Object conversion (upgrade SAP BW 2.x SAP BW 3.5)

If your source release is SAP BW 2.x, you must have completed the conversion of the
Web objects successfully see Upgrade Guide
The conversion of the chart settings is based on the prior successful conversion of the
Web Objects
If you start the conversion of the chart settings although the Web objects conversion did
not succeed, you can no longer repeat the Web Objects conversion. Then, you must
correct all open problems manually!
© SAP AG 2005, 18
Overview
SAP BW upgrade
Enterprise Data Warehousing and SAP BI

Foundations and requirements

Upgrade and the system landscape
Alpha conversion
Prepare and upgrade
 Upgrade Preparation and Prerequisites: Alpha
Conversion
After the check has executed, the user must decide whether to:
Remove the conversion exit
Convert the characteristic

Note: These decisions should be made with your SAP BW Administrators!

All characteristics found are listed in three groups
Characteristics with collisions in the SID table
Marked in red
Neither “remove” nor “convert” is suggested – the user must decide which
Characteristics with inconsistent values in the SID table
Marked in yellow
Remove exit is suggested if current content version is without exit
Otherwise, conversion is suggested
Other characteristics used in ODS Objects
Marked in green
Conversion is suggested

Compounded characteristics must be converted in one step

Note: The system lock remains active during the maintenance

© SAP AG 2005, 20
 Upgrade Preparation and Prerequisites: Alpha
Conversion (cont.)

Alpha conversion (OSS note 447341) – Only required for 2.x upgrades:
What is the Alpha conversion?
Only data that contains only digits is stored on the database with leading zeros
111 0000000111
11 1 11 1
Internal format
11A1 11A1
0001110 0000001110

Data can be converted to external format (display and data selection)

0000000111 111
external format
11A1 11A1

The data extraction and loading must be consistent; previously, a warning

was given only if transfer rules in SAP BW and R/3 extraction were different
(some content InfoObjects were initially delivered incorrectly)
Trans. Structure Char 4 Comm. Structure Char 6
0 0 0 1 0 0 0 1 Values are not
found when
0 1 0 1 entered on Dynpro

© SAP AG 2005, 21
 Upgrade Preparation and Prerequisites: Alpha
Conversion (cont.)

The Alpha converter:

(Trx: RSMDCNVEXIT)

Conversion status

Check job
status

Start the check job

Conversion decisions

Conversion job
status

Start the
conversion job

© SAP AG 2005, 22
Overview
SAP BW upgrade
Enterprise Data Warehousing and SAP BI

Foundations and Requirements

Upgrade and the system landscape
Alpha conversion
Prepare and upgrade
 PREPARE Upgrade Process

Features:
May run any time before the upgrade
Only minor influence on production operation Initialization
Check system prerequisites
Run PREPARE early to determine necessary actions

Configure the upgrade Extension

Specify support packages
Supply add-on upgrade CDs
Integration
Specify languages

Check system status

Open repair requests CHECK modules
Incomplete imports
Update tasks
SAP BW-specific checks ...

© SAP AG 2005, 24
 System Switch Upgrade Strategy

Overview of the Process: Shadow act

ivation
4.6x*
SPDD
4.6x* 6.40

SAP BW
DATA 4.6x* 6.40
SAP BW
Shado DATA 4.6x* 6.40
w ins
tallati
on Import

* Example:
DA TA
conv XPRA SAP BW
2.x -> 3.5 upgrade (4.6x) ersio DATA 6.40
n Phase
3.x -> 3.5 would use 6.20
© SAP AG 2005, 25
 System Switch Upgrade Strategy (cont.)

SAP BW 3.x upgrades (based on 6.40 upgrade technology)

Benefits:
Almost constant downtime even with packages

Modification adjustments during uptime

Destination release features in Basis database objects
Data dictionary and SPDD (at fixed support package level 0)
Patches of central Basis dictionary objects
Ability to distribute upgrade processing to different servers

Costs:
f on
Increased overall runtime
o f
Start-to-finish time is increased
Increased system resources
Shadow instance requires additional CPU and memory

© SAP AG 2005, 26
 Downtime Minimized – An SAP BW Perspective

The system switch and upgrade strategies provide options for the
continued productive use of SAP BW
Productive use:
From an SAP BW perspective, this refers to the ability to execute
queries against the SAP BW system
If “Downtime minimized” is selected, users can expect approximately
2-4 hours of upgrade-processing-related downtime for executions
of queries

Other SAP BW operations:

Note: Operations such as Data loading, Data and SAP BW object
administration, and SAP BW query element building should cease
at the start of R3up
These SAP BW operations create objects in the Data Dictionary
and Database
Plan accordingly to cease admin operations!
No automated SAP BW lock process
System objects like DDIC will be locked automatically

© SAP AG 2005, 27
 System Switch Upgrade: Timing Diagram

Production Downtime
resource-minimized
(on target release)
Shadow Instance

Import of Control Data

in Copy Tables
Production Downtime

Substitution Set
Support Pack‘s

Modification
Adjustment
downtime-minimized

Distribution
Add-Ons

Activation
Import of

ICNV
Inst. Upgrade
Uptime

Backup
Backup

New
PREPARE Upgrade Downtime-Minimized
Downtime-Minimized Rel.
Downtime

Backup
Imp.
Backup

Resource-Minimized Post
Upgrade
Stop of
Productive use
© SAP AG 2005, 28 (Strategy dep.)
The Upgrade Itself: Best Practices and Tips

Some R3up phases do not have individual logs € use

CONNECT.LOG

SAP BW upgrades generally should be done using database

archiving turned off
Database will not log upgrade activities
Much easier to manage

Do not “ignore” any phase unless directed by SAP BW development

Do not “jump” phases

Tip: Start R3up at end of the day; continue next morning

With luck, the upgrade will be far along the next morning ☺
Upgrade guide will help you determine which phases require user input.
6.40 PREPARE eliminates most of the user input for R3up.

© SAP AG 2005, 29
 Key Upgrade Resources: Service Marketplace
Alias “BW”

http://service.sap.com/BW > InfoIndex > U > Upgrade / Go-Live

© SAP AG 2005, 30
What We’ll Cover…
SAP BW upgrade

SAP BW Unicode migration

SAP BW system copy

Wrap-up
Overview
SAP BW Unicode migration
Enterprise Data Warehousing and SAP BI

Unicode concepts
SAP BW and Unicode
SAP BW Unicode migration
Overview
SAP BW Unicode migration
Enterprise Data Warehousing and SAP BI

Unicode concepts
SAP BW and Unicode
SAP BW Unicode migration
 Unicode Essentials

What is Unicode?
Character encoding schema for (nearly) all characters used
worldwide – includes nearly 100,000 distinct language characters!

Each character has a unique number (“Unicode code point”)

Notation U+nnnn (where nnnn are hexadecimal digits)
See http://www.unicode.org for complete code charts

© SAP AG 2005, 34
 ISO-639 Languages Supported by Unicode

Kuanyama
Kazakh
Manx Greenlandic Marathi
Dzongkha Hausa Khmer Malay Pali
Greek Hebrew Kannada Maltese Polish
Bihari Telugu
English Hindi Korean Burmese Pushto
Bislama Tajik
Esperanto Hiri Motu Kashmiri Nauru Portuguese
Bengali Thai Uzbek
Afar Spanish Croatian Kurdish Norwegian Bokmål Quechua
Tibetan Tigrinya Vietnamese
Abkhazia Estonian Hungarian Komi Ndebele Raeto-Romance
Breton Turkmen Volapük
Avestan Basque Armenian Cornish Nepali Rundi
Bosnian Tagalog Wolof
Afrikaans Persian Herero Kirghiz Ndonga Romanian
Catalan Tswana Xhosa
Amharic Finnish Interlingua Latin Dutch Russian
Chechen Tonga Yiddish
Arabic Fijian Indonesian Letzeburgesch Norweg. Nynorsk Kinyarwanda
Chamorro Turkish Yoruba
Assamese Faroese Interlingue Lingala Norwegian Sanskrit
Corsican Tsonga Reserved- cust.
Aymara French Inupiak Lao Ndebele Sardinian
Czech Tatar Zhuang
Azerbaijani Frisian Icelandic Lithuanian Navajo Sindhi
Church Slavic Irish Twi Chinese trad.
Bashkir Italian Latvian Nyanja Northern Sami
Chuvash Tahitian Chinese
Belarusia Gaelic Inuktitut Malagasy Occitan Sango
Welsh Uighur Zulu
Bulgarian Gallegan Japanese Marshallese Oromo Serbo-Croatian
Danish Ukrainian
Guarani Javanese Maori Oriya Sinhalese
German Urdu
Gujarati Georgian Macedonian Ossetian Slovak
Kikuyu Malayalam Panjabi
Mongolian
Moldavian

© SAP AG 2005, 35
 SAP Languages and Code Pages: Pre-Unicode

Choose one ellipsis:

Chinese Chinese
Hebrew (Trad.) • All languages
(Simp.) Korean within this ellipsis
can be combined
Greek within one (non-
Unicode) R/3
System
Japanese
Example:
Russian English With ISO-8859-2,
Ukrainian you can use all the
following languages:
Thai • Croatian
Danish
• Czech
Dutch German Croatian
Finnish Czech • Hungarian
French, Italian Hungarian • Polish
Norwegian Polish • Romanian
Portuguese Romanian • Slovak
Spanish Slovak • Slovenian
Swedish Slovenian
• German
Turkish
• English
© SAP AG 2005, 36
Overview
SAP BW Unicode migration
Enterprise Data Warehousing and SAP BI

Unicode concepts
SAP BW and Unicode
SAP BW Unicode migration
 SAP BW 3.5 – Languages/Unicode

The following languages are delivered with SAP BW 3.5

Bulgarian Chinese Chinese trad. Croatian Czech

Danish Dutch English Finnish French
German Greek Hebrew Hungarian Italian
Japanese Korean Norwegian Polish Portuguese
Romanian Russian Slovakian Slovenian Spanish
Swedish Turkish
As with all other SAP NetWeaver ’04 components,
SAP BW 3.5 supports Unicode
For SAP BW, Unicode is optional
Customers can continue using non-Unicode SAP BW or choose
to migrate to Unicode
Even though Web AS 6.40 J2EE requires Unicode, it is possible to continue
using non-Unicode SAP BW
SAP BW supports extraction from Unicode, non-Unicode, and MDMP
source systems

© SAP AG 2005, 38
 Unicode-Compliant SAP BW

Unicode compliance means:

SAP BW can interpret and display Unicode characters
User interface will be shown in local language
Business data can use all languages in parallel

SAP BW can extract data from Source Systems with specific code
pages (non-Unicode or Unicode)

SAP BW can extract data from SAP Source System running mixed
code pages (MDMP)

Interfaces to third-party systems support correct code page

conversion

© SAP AG 2005, 39
 Unicode Release Planning

Which versions of SAP BW are released for Unicode and

when are they available?

SAP BW Unicode releases

SAP BW 3.5 as part of SAP NetWeaver ’04 and all subsequent releases
[SAP BW 3.1 Content has been piloted, but it is not shipped anymore]

Availability dates
Unicode has been generally available with SAP BW 3.5 (NetWeaver ’04)
since Sept 1st 2004

Unicode Conversion: Only available for SAP BW 3.5

(new SAP BW migration tool delivered)

© SAP AG 2005, 40
 SAP BW Unicode Installation and Conversion
How can I make my SAP BW Unicode-compliant?
Delivery
You can choose between non-Unicode and Unicode installation
Note: Unicode installation requires more hardware resources
(depending on database platform)

Installation modes
New installation
Conversion of an existing SAP BW
Before the conversion, upgrade your SAP BW to SAP BW 3.5
R3LOAD converts an existing SAP BW 3.5 automatically by exporting the
database, realigning the database, and importing the database again
Note that the Unicode Conversion is a pilot project as part of an SAP BW
System Copy (see OSS Note 543715)
Customer-developed programs (variable exits, virtual characteristics/key
figures, transformation rules, table interface, etc.) must be in line with the
Unicode rules
The duration of a conversion depends on the size of the existing database

© SAP AG 2005, 41
 Resource Requirements for Unicode-Compliant SAP BW
Additional resource requirements after a Unicode conversion:
Text fields are usually longer in a Unicode environment than in a non-Unicode
environment. Enhanced functionality requires additional resources, which strongly
depend on the given customer scenario. In the following, we give a rough estimation
of what a Unicode conversion could mean for the resources.

CPU
We expect additional SAP BW requirements of roughly 30% more CPU power –
similar to the SAP R/3 requirements

Main Memory
We expect additional SAP BW requirements of roughly 50% more memory – similar
to the SAP R/3 requirements

Disk Storage
Disk Storage depends strongly on the underlying DBMS and the given data
model/volume. For a significant share of InfoCube data (only numeric keys!), there
might not be a significant increase of the database size
For SAP R/3 on ORACLE, tests have resulted in roughly 35% additional disk space
For SAP BW, we expect – depending on the scenario – less additional disk space
Note that after a conversion, the disk size may even decrease because of
database reorganization
© SAP AG 2005, 42
Overview
SAP BW Unicode migration
Enterprise Data Warehousing and SAP BI

Unicode concepts
SAP BW and Unicode
SAP BW Unicode migration
 The Unicode Conversion Project: Overview

Preparation

Conversion

Post -Conversion
Post-Conversion

Set up the Unicode To be done during Up and Running

upgrade project system downtime
Verification of
Export/import process Data Consistency
Perform list of tasks to entire database contents
prepare system for Integration Testing
migration Use of SAP BW focused on
migration tool language handling

© SAP AG 2005, 44
 Conversion Preparation: Transaction SPUMG

Pre-Conversion
Unicode Conversion
Post-Conversion
Set up the
Conversion
Project

Check Unicode system is

Prerequisites up and running

Plan database SUMG Verification of

downtime during
conversion SAPInst Data Consistency

Integration
Enable Customer SPUMG (R3load) Testing focused
Developments Post-Conversion on
language
Repairs handling
Conversion Database
in Unicode
Preparation Export,
system
in Conversion
non-Unicode & Import
system

© SAP AG 2005, 45
 Database Export, Conversion, and Import

Pre-Conversion
Unicode Conversion
Post-Conversion
Set up the
Conversion
Project

Check Unicode system is

Prerequisites up and running

Plan database SUMG Verification of

downtime during
conversion SAPInst Data Consistency

Integration
Enable Customer SPUMG (R3load) Testing focused
Developments Post-Conversion on
language
Repairs handling
Conversion Database
in Unicode
Preparation Export,
system
in Conversion,
non-Unicode and Import
system

© SAP AG 2005, 46
 Database Export, Conversion, and Import: Basis

The basis for a standard Unicode conversion is a System Migration:

Guide: Homogeneous and Heterogeneous System Copy

OSS Note 516246: “Hom. and Het. System Copy for SAP

Systems Based on Web AS 6.20

Preparation tasks
Export the database with SAPinst
Install database on target system
Import the database dump with SAPinst
Post-processing tasks

Also the standard R/3 platform and database-dependent installation guide have to be
used, which can be found in:

Standard Installation Guide Directory: SAPNet Installation Guide Directory

© SAP AG 2005, 47
 Database Export, Conversion, and Import: Tools

The system setup tool SAPInst is used for the entire system
copy — internally SAPInst uses the program R3load

R3load performs the database export with conversion to Unicode

using control table and System Vocabulary, writes an R3load
Repair Log in case code page information is not available, and
performs the database import

Special SAP BW tools are included in the import procedure to

deal with SAP BW objects, which are non-standard from other
SAP basis objects (e.g., partitioned tables)

As a system copy to Unicode, database conversion and system

shutdown/Unicode system start will be completely automated

© SAP AG 2005, 48
 R3Load – Export

SAPInst is used as “Frontend tool”

Logs are written to the SAPInst directory
Export Files are written to the Export directory

Conversion (non-UC UTF-16) during Export:

Non-UC R3Load R3load.exe -datacodepage 4103 –e ....
Example: “für“ (0x66 FC 72 0x0066 00FC 0072)

SAP System Export DIR:

SAPAPPL0.001 Database-independent format
non-Unicode
SAPAPPL1.001 (big or little endian,
... depending on platform)
.
.
Multiple processes
possible
Default: One process (STR file) per data class
(see SE11 Technical Settings)
Space needed on Export directory:
Advanced Export options: 50 largest tables get ~10-25% of database size
own process each

© SAP AG 2005, 49
 R3Load – Import

SAPInst is used as “frontend tool”

Non-UC database can be deleted or UC database can be installed on
different server
Import procedure nearly same as new installation
Special SAP BW objects procedures included
UC R3Load
R3load.exe -i ....

Export DIR:
SAPAPPL0.001
SAPAPPL1.001 SAP
... System
. Unicode
.

Multiple processes
possible.
Number of processes
same as during export
(default)

© SAP AG 2005, 50
 Unicode System: Transaction SUMG

Pre-Conversion
Unicode Conversion
Post-Conversion
Set up the
Conversion
Project

Check Unicode system is

Prerequisites up and running

Plan database SUMG Verification of

downtime during
conversion SAPInst Data Consistency

Integration
Enable Customer
Developments
SPUMG (R3load) Post- Testing focused
on
Conversion language
handling
Repairs in
Conversion Database
Unicode
Preparation Export,
in Conversion system
non-Unicode & Import
system

© SAP AG 2005, 51
 Runtimes

How long does it take to convert a database?

Time required to convert the database will depend on:

Database size

Number and speed of CPUs available

Distribution of sizes of the tables

© SAP AG 2005, 52
 Runtimes – Customer Experiences

Customer example – Export

Database: Oracle
Operating system: Unix
CPU frequency: 731 MHz
System: MDMP (Latin 1/Latin 2)
System vocabulary: 701,433 entries

Average speed for exporting 880 GB: 3.36 GB/hour/CPU

Total size of the export dump files: 194 GB

© SAP AG 2005, 53
 Runtimes – Customer Experiences (cont.)

Customer example – Import

Database: Oracle
Operating System: Unix
CPU Frequency: 1150 MHz
System: Unicode

Average speed for importing 880 GB: 14.4 GB/hour/CPU

Average speed for importing 194 GB dump size: 3.17 GB/hour/CPU

© SAP AG 2005, 54
 DB Growth – Customer Experience

Customer experience – R/3 Enterprise

Unicode conversion includes a database reorganization

Database growth is often compensated in UTF-8 case by
database shrinking due to reorganization

Size before Size after Database Unicode

Conv.in GB Conv.in GB Growth in % Encoding
306 271 -11,4% CESU-8
530 461 -13,0% CESU-8
112 93 -17,0% CESU-8
880 674 -23,4% CESU-8
460 650 +41,3% UTF-16
22 36 +63,6% UTF-16

© SAP AG 2005, 55
What We’ll Cover…
SAP BW upgrade

SAP BW Unicode migration

SAP BW system copy

Wrap-up
Overview
SAP BW system copy
Enterprise Data Warehousing and SAP BI

System landscape configuration

System copy:
SAP BW and Source System together
System copy: SAP BW refresh w/o Source System
System copy: Source System refresh w/o SAP BW
Overview
SAP BW system copy
Enterprise Data Warehousing and SAP BI

System landscape configuration

System copy:
SAP BW and Source System together
System copy: SAP BW refresh w/o Source System
System copy: Source System refresh w/o SAP BW
 A Few Words about SAP BW System “Refreshes”

There are essentially four types of SAP BW system refreshes with

differing implications:
1. System copy of both the SAP BW and Source Systems in parallel
2. System refresh of both the SAP BW and Source Systems in parallel
3. System refresh of SAP BW system without copying Source Systems in parallel
4. System refresh of Source Systems without copying the SAP BW system
in parallel

There are many reasons why system copies are performed. It is usually
a last-resort technology-based solution to resolve a business/organizational
issue – obviously some issues are more justified than others! ☺
Data alignment issues:
One system does not have sufficient data to perform its function, so a data refresh is
required. Example: refresh of an R/3 QAS system from the R/3 Production system
Data Dictionary and Development alignment issues:
Developments are not synchronized in the system landscape, or inadequate change
management and controls are in place
Creation of a Sandboxing or Production support system
It should be noted that as Data Warehouses and OLTP systems grow,
the resource impact of system refreshes also grows

© SAP AG 2005, 59
 Key Technologies Relevant to SAP BW System
Configurations
Logical system names:
Every client in an SAP System can be assigned a logical system name for
identification purposes in ALE scenarios
SAP BW requires that clients and clients in Source Systems be identified by a
logical system name
Each client within a single SAP System must be assigned a unique logical system
name
Each Source System client connected to a single SAP BW system must have a
unique logical system name
A Source System client cannot have the same logical system name as an SAP BW
client

Client 000 Client 200 Client 000 Client 200

LogSys: BWCL000 LogSys: R3CLT200 LogSys: BWCL100 LogSys: R3CL200
R/3 system
R/3 system
Client 100 Client 100
LogSys: BWCL100 LogSys: BWCL100
Client 200
Client 200
LogSys: R3CL200
LogSys: R3CL200

Client 300 Client 100

LogSys: R3CL300 LogSys: BWCL100
SAP BW system R/3 system SAP BW system R/3 system
© SAP AG 2005, 60
 Key Technologies Relevant to SAP BW System
Configurations (cont.)
SAP BW system landscape:
The SAP-recommended system landscape* consists of an SAP BW
development (DEV), consolidation (QAS), and production (PRD) system
For each SAP BW system type (DEV, QAS, PRD), there should be an
equivalent SAP Source System of the same type

DEV QAS PRD

CRM
Transports Transports
CRD CRQ CRP
ALE/RFC ALE/RFC ALE/RFC

BW
Transports Transports
BWD BWQ BWP
ALE/RFC ALE/RFC ALE/RFC

R/3 Transports Transports

R3D R3Q R3P

* Note: The same principle applies to any SAP Source System (SAP APO, mySAP CRM, SAP BW, etc.)
© SAP AG 2005, 61
 Key Technologies Relevant to SAP BW System
Configurations (cont.)
Logical System Name (LSN) strategy:
A logical system naming strategy is extremely important as it additionally has
impacts on the system copies and the work to complete this
Logical system renaming of OLTP system data can be very time consuming
There are two main options available for naming and assigning logical system
names:
1. Using non-unique logical system names across systems in the same landscape, and
unique logical system names within each system type (DEV, QAS, PRD)
DEV QAS PRD
Logical System: Logical System: Logical System:
BWCL100 BWCL100 BWCL100

SAP BW
Transports Transports
BWD BWQ BWP

ALE/RFC ALE/RFC ALE/RFC

R/3 Transports Transports

Example:
SAP BW client and R3D R3Q R3P
one R/3 client as
a Source System Logical System: Logical System: Logical System:
R3CL200 R3CL200 R3CL200
© SAP AG 2005, 62
 Key Technologies Relevant to SAP BW System
Configurations (cont.)
Option 1 is recommended by SAP Development as it simplifies the system copy process
Consult SAP note 184447 for more information
Note: There are restrictions with such an approach, particularly in complex ALE
scenarios and system connections that span system types

2. Using unique logical system names across systems in the same landscape, and unique
logical system names within each system type (DEV, QAS, PRD)

DEV QAS PRD

Logical System: Logical System: Logical System:
BWDCL100 BWQCL100 BWPCL100

SAP BW
Transports Transports
BWD BWQ BWP

ALE/RFC ALE/RFC ALE/RFC

R/3 Transports Transports

Example: R3Q R3P

R3D
SAP BW client
and one R/3 client as Logical System: Logical System: Logical System:
a Source System R3DCL200 R3QCL200 R3PCL200

© SAP AG 2005, 63
 Key Technologies Relevant to SAP BW System
Configurations (cont.)

Implications of each Logical system naming option:

Option 1 Option 2

Logical system names unique across each system type

Logical system names unique across system landscape

Logical system renaming not required after system copy

Support complex ALE scenarios

(e.g., DEV BWD connecting to both DEV R3D and QAS R3Q)
Support for connections between SAP BW system in a system
landscape (e.g., QAS BWQ connecting to both PRD BWP)
Supports Centralized functions/systems connection
(e.g., Central User Admin [CUA], Workplace, Solution Mgr, etc.)

Support connections to centralized Enterprise Portal System

Compatible with Transport system

Logical System Naming strategy can be changed at a later time

(conversion effort can be significant!)

© SAP AG 2005, 64
 Key Technologies Relevant to SAP BW System
Configurations (cont.)

Relationships between SAP BW Objects in SAP BW and

Source Systems
Critical relationships exist between objects in each of your SAP-based
Source Systems and your SAP BW system
It is important that you analyze the system copy choices and the
impact of your decision on the preservation of your object
relationships
Failure to consider this could lead
to object and data inconsistencies,
and in the worst cases, incompatible
data load scenarios
Additionally, the Data consistency
between SAP BW and your Source
Systems should be considered.
Will old data be compatible with new?
DataSources, Transfer structures,
Extraction enhancement, Delta
extraction status, Data compatibility
should all be considered

© SAP AG 2005, 65
Overview
SAP BW system copy
Enterprise Data Warehousing and SAP BI

System landscape configuration

System copy:
SAP BW and Source System together
System copy: SAP BW refresh w/o Source System
System copy: Source System refresh w/o SAP BW
 System Copy of Both the SAP BW and Source Systems

Scenario: A system copy of the SAP BW and Source Systems (in parallel) is a
simple process of creating new systems from a copy of existing systems
Examples of such uses: creation of a test upgrade landscape or production firefighting systems

Depending on your choice of LSN strategy, there are two options available:
1) Using non-unique LSNs across systems in the same landscape (see diagram below):
1. On BWT, change the Source System RFC Destination host names to the new host for R3T
2. On BWT, check the RFC destination host name for the BWT Source System (blank)
3. On R3T, change the Source System RFC Destination host names to the new host for BWT

DEV QAS PRD TST

Logical System: Logical System: Logical System: Logical System:
BWCL100 BWCL100 BWCL100 BWCL100

SAP BW
Transports Transports Copy
Example: BWD BWQ BWP BWT
Create an upgrade ALE/RFC ALE/RFC ALE/RFC ALE/RFC
Testing system
Transports Transports Copy
R/3
R3D R3Q R3P R3T
Logical System: Logical System: Logical System: Logical System:
R3CL200 R3CL200 R3CL200 R3CL200
© SAP AG 2005, 67
 System Copy of Both the SAP BW and Source Systems
(cont.)
2) Using unique LSNs across systems in the same landscape (see diagram below):
1. On BWT, execute two logical system renaming processes (transaction BDLS)
1. Execute BDLS to convert SAP BW client LSN from BWPCL100 to BWTCL100
2. Execute BDLS to convert R/3 Source System LSN from F3PCL200 to R3TCL200
2. On BWT, create two new RFC destinations for the R3T Source System copy entries
1. Copy existing entries R3PCL200 and R3PCL200_dialog, creating new RFC
destinations R3TCL200 and R3TCL200_dialog
2. Delete the old RFC destinations R3PCL200 and R3PCL200_dialog
3. On BWT, create a new RFC destination for the BWT Source System
1. Copy existing entry BWPCL100, creating new RFC destination BWTCL100
2. Delete the old RFC destination BWPCL100

DEV QAS PRD TST

Logical System: Logical System: Logical System: Logical System:
BWDCL100 BWQCL100 BWPCL100 BWTCL100

SAP BW
Transports Transports Copy
Example: BWQ BWP BWT
BWD
Create an upgrade ALE/RFC ALE/RFC ALE/RFC ALE/RFC
Testing system
Transports Transports Copy
R/3
R3D R3Q R3P R3T

Logical System: Logical System: Logical System: Logical System:

R3DCL200 R3QCL200 R3PCL200 R3TCL200
© SAP AG 2005, 68
System Copy of Both the SAP BW and Source Systems
(cont.)
4. On R3T, execute two logical system renaming processes
(transaction BDLS)*
1. Execute BDLS to convert R/3 client LSN from R3PCL200 to R3TCL200
2. Execute BDLS to convert SAP BW target client LSN from BWPCL100 to
BWTCL100
5. On R3T, create a new RFC destination for the BWT SAP BW system
Copy existing entry BWPCL100, creating new RFC destination BWTCL100
Delete the old RFC destination BWPCL100
6. Restart SAP BW data loads

* Warning:
Converting the logical system for an R/3 system can be very time consuming.
The runtime is dependent on whether ALE has been enabled on your R/3
system for certain documents.
If so, a large number of documents (sales orders, etc.) may be tagged with the
logical system name for ALE purposes. These would have to be converted.
It is suggested that you analyze your R/3 system before executing this
conversion (BDLS has a test function, but runtimes can be just as long as the
conversion itself)
Note: Connecting SAP BW to your R/3 system does not enable this ALE
functionality!

© SAP AG 2005, 69
System Copy of Both the SAP BW and Source Systems
(cont.)

Scenario: A System refresh of both the SAP BW and Source Systems in

parallel is the simplest choice for system refresh…
…yet it is sometimes the hardest to accomplish due to coordination reasons!

The SAP BW steps to perform after this refresh are the same as previously
outlined in the system copy procedure
Optional: You can add steps to save SAP BW Objects from the old SAP BW
System and Source systems
DEV QAS Copy PRD
Logical System: Logical System: Logical System:
BWCL100 BWCL100 BWCL100

SAP BW
Transports Transports
BWD BWQ BWP
ALE/RFC ALE/RFC ALE/RFC

Transports Transports
R/3
R3D R3Q R3P

Logical System: Logical System: Logical System:

R3CL200 R3CL200 R3CL200
Copy

© SAP AG 2005, 70
System Copy of Both the SAP BW and Source Systems
(cont.)

Pros:
Minimal steps to perform refresh and reconnect systems
Data is aligned between SAP BW and the Source systems after the refresh
Delta extractors status is maintained
Consistency between SAP BW Objects across interconnected systems
is maintained
System connection configuration is already defined and in place
Valid for both Logical system name strategies
No need to consider individual data target synchronization when fed from
multiple Source Systems

Cons:
Coordination of timing for the system refresh
All work in QAS systems must be completed
and imported into PRD or reapplied after refresh

© SAP AG 2005, 71
Overview
SAP BW system copy
Enterprise Data Warehousing and SAP BI

System landscape configuration

System copy:
SAP BW and Source System together
System copy: SAP BW refresh w/o Source System
System copy: Source System refresh w/o SAP BW
 SAP BW System Refresh Without Source Systems

Scenario: The SAP BW system is refreshed without refreshing the Source System in
parallel. The following implications should be understood:
SAP BW Objects (in SAP BW and Source System) need to be re-synchronized
All data will be out of synchronization between SAP BW and Source Systems
Master, transactional, and global settings data re-synchronization is required.
This effort can be considerable.
SAP BW is essentially an “island” until data is re-synchronized
SAP BW systems with multiple Source Systems may want to consider using the InfoObject
0LOGSYS in data models as it provides an easier mechanism for selecting data during Data
synchronization
DEV QAS Copy PRD
Logical System: Logical System: Logical System:
BWDCL100 BWQCL100 BWPCL100

BW
Transports Transports
BWD BWQ BWP

ALE/RFC ALE/RFC ALE/RFC

R/3 Transports Transports

Example:
SAP BW client and one R3D R3Q R3P
R/3 client as a Source
System Unique LSNs Logical System: Logical System: Logical System:
R3DCL200 R3QCL200 R3PCL200
© SAP AG 2005, 73
 SAP BW System Refresh Without Source Systems
(cont.)
Steps to connect your SAP BW and Source System after the refresh
Also see SAP note 184754 for more detailed information
We are using the example on the previous slide
Note: It is assumed that Source System-dependent SAP BW Objects have
been saved

1. Prior to the refresh, in the SAP BW System to be refreshed, delete

the R/3 Source Systems
Note: In our example, this would occur in BWQ before the refresh from BWP
2. Perform the system refresh. If logical system name is to be changed,
execute a logical system renaming process (transaction BDLS)
3. In the newly refreshed SAP BW system, create a new RFC destination for
the BWQ Source System and delete the old BWP RFC destination
4. In the newly refreshed SAP BW system, delete the original Source System
connection. (connection to R3PCL200 in our example)
1. Warning: Ensure that the RFC Destination is not functioning (dummy)!
2. In the Admin Workbench, delete the R/3 Source System (R3PCL200). This may
take some time as all the transfer rules and PSA tables are deleted

© SAP AG 2005, 74
SAP BW System Refresh Without Source Systems
(cont.)

5. On the Source System (R3QCL200), delete the DataSource and

connection information of the old SAP BW system that was overwritten
6. In the newly refreshed SAP BW system, create a new Source System
connection (for R3QCL200 in our example)
1. The DataSources should now replicate. This can take some time
7. Optional: In the newly refreshed SAP BW system, recreate the Source-
System-dependent SAP BW objects using the “Save for System copy”
Transport. This saves you considerable manual work
1. In the Transport Connection, select the “Conv. of log. Sys name” button
2. Create a mapping for the SAP BW system to itself (Mapping of BWQCL100
to BWQCL100)
3. Import the “Save for System copy” transport into the SAP BW system
8. Global Settings, Master and Transaction Data can now be re-
synchronized
1. Global Settings can be completely replaced using the “Rebuild tables
option” but consideration should be made for other Source Systems
2. Transaction and Master data should be deleted before re-synchronization

© SAP AG 2005, 75
Overview
SAP BW system copy
Enterprise Data Warehousing and SAP BI

System landscape configuration

System copy:
SAP BW and Source System together
System copy: SAP BW refresh w/o Source System
System copy: Source System refresh w/o SAP BW
 Source Systems Refresh Without SAP BW System
Scenario: The Source system is refreshed without refreshing the connected
SAP BW system in parallel
The following implications should be understood:
SAP BW Objects (in SAP BW and Source system) need to be re-synchronized
All Data will be out of sync between SAP BW and Source Systems
Master, Transactional, and Global settings Data re-synchronization is required.
This effort can be considerable.
SAP BW is essentially an “island” containing old data until data is re-synchronized
For SAP BW systems using multiple Source Systems consider using the InfoObject
0LOGSYS in data models, as it provides an easier mechanism for selecting data
during Data synchronization
DEV QAS PRD
Logical System: Logical System: Logical System:
BWDCL100 BWQCL100 BWPCL100

SAP BW
Transports Transports
BWD BWQ BWP

ALE/RFC ALE/RFC ALE/RFC

R/3 Transports Transports

Example:
R3D R3Q R3P
SAP BW client and one
R/3 client as a Source Logical System: Logical System: Logical System:
System Unique LSNs R3DCL200 R3QCL200 R3PCL200
Copy
© SAP AG 2005, 77
Source Systems Refresh Without SAP BW System
(cont.)

Steps to connect your SAP BW and Source System after the refresh
Also see SAP note 184322 for more detailed information
We are using the example diagrammed on the previous slide
Note: It is assumed that Source-System-dependent SAP BW Objects have
been saved

1. Perform the normal technical system refresh procedures

2. In the newly refreshed Source System, delete the original Source
System connection (The connection to R3PCL200 in our example)
1. Disable the RFC Connection for BWPCL100
This disables the interface from the Source System to SAP BW, and
ensures we do not connect to the production SAP BW system
2. Delete the DataSource and connection information for the old SAP BW
system that was overwritten
3. If logical system name is to be changed, execute a logical system renaming
process (transaction BDLS)
4. Execute BDLS to convert R/3 client LSN from R3PCL200 to R3QCL200

© SAP AG 2005, 78
Source Systems Refresh Without SAP BW System
(cont.)

3. In the newly refreshed R/3 Source System, re-import the DataSources

saved from R3Q prior to the refresh
Hint: This saves you considerable manual work
4. In the SAP BW system, restore the Source System connection to the
new Source System (R3QCL200 in our example)
1. Restore the connection: BWQ already has information about a connection
to R3QCL200 – we will use this information to rebuild it!
2. When using the Restore function, choose the “Replicate Metadata” option:
This will re-establish the Source System connection, replicate your
DataSources, and activate them.
5. Global Settings, Master and Transaction Data can now be
re-synchronized
1. Global Settings can be completely replaced using the “Rebuild tables
option,” but consideration should be made for other Source Systems
2. Transaction and Master data should be deleted before re-synchronization

© SAP AG 2005, 79
What We’ll Cover…
SAP BW upgrade

SAP BW Unicode migration

SAP BW system copy

Wrap-up
7 Key Points to Take Home

1. SAP BW upgrade projects require significant planning and preparation.

The preparation steps are often more time consuming than the actual
upgrade runtime itself
2. Unicode is a global effort towards handling all characters in the world’s
major and minor languages in systems
3. Converting an SAP BW system to Unicode requires significant effort, as
an SAP BW system migration is part of the process
4. An SAP BW Unicode system migration is similar to a heterogeneous
DB/OS migration, which is a pilot project for SAP BW systems
5. SAP BW system copies require system landscape planning, and the
logical system naming convention has a big impact
6. Carefully plan any system copy activities, as object dependencies with
Source System objects must be considered
7. System “refreshes” can be avoided through good change management
techniques, avoiding disruption to the landscape

© SAP AG 2005, 81
 Further Information on the SAP Service Marketplace

SAP BW SAP R/3 Enterprise

http://service.sap.com/bw http://service.sap.com/enterprise
SAP NetWeaver New Release Strategy
http://service.sap.com/NetWeaver http://service.sap.com/releasestrategy
Unicode Release Notes
http://service.sap.com/globalization http://service.sap.com/releasenotes
Upgrade Information Center SAP Plug-In
http://service.sap.com/upgrade http://service.sap.com/R3-Plug-In

SAP SDN Safeguarding

http://sdn.sap.com http://service.sap.com/safeguarding

Maintenance Strategy Safeguarding Upgrade

http://service.sap.com/maintenancestrategy http://service.sap.com/safeguardingupgr
ade
Services from SAP Support and SAP Consulting

© SAP AG 2005, 82
 For More Information: Access the SAP Developer Network
– www.sdn.sap.com
The central hub for the SAP technology
community
Everyone can connect, contribute, and
collaborate – consultants, administrators and
developers
Focus around SAP NetWeaver and SAP xApps

High quality of technical resources

Articles, how-to guides, weblogs,
collaborative areas, discussion forums,
downloads, toolkits, and code-samples

A collaboration platform, not a

one-way street
SAP experts from customers, partners
and SAP

SDN is powered by SAP NetWeaver™

Built on the SAP Enterprise Portal
Featuring collaboration capabilities of SAP
Knowledge Management
© SAP AG 2005, 83
Questions?

© SAP AG 2005, 84
 Feedback

Please complete your session evaluation

and drop it in the box on your way out.

[email protected]

© SAP AG 2005, 85
 Copyright 2005 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.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C 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.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may
vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of
these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of
hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web
pages

© SAP AG 2005, 86