rmc_1250813687

8/22/2019 rmc_1250813687

1/86

Ron SilbersteinSAP

Strategies, Techniques,and Best Practices toUpgrade, Copy, andMigrate SAP BW Systems

8/22/2019 rmc_1250813687

2/86

SAP BW system copy

SAP Business Information Warehouse

(BW) upgrade

SAP BW Unicode migration

Wrap-up

What Well Cover

8/22/2019 rmc_1250813687

3/86

SAP BW system copy

SAP BW upgrade


Wrap-up

What Well Cover

8/22/2019 rmc_1250813687

4/86

Overview

Enterprise Data Warehousing and SAP BI

Foundations and requirements

Upgrade and the system landscapeAlpha conversion

Prepare and upgrade

SAP BW upgrade

8/22/2019 rmc_1250813687

5/86

Overview




Prepare and upgrade

SAP BW upgrade

8/22/2019 rmc_1250813687

6/86

SAP AG 2005, 6

SAP BI Overview Release Upgrade Strategy

Information on SAP BI release strategy:

Aug

2000

Dec

2000

Jun

2002

End of Regular

MaintenanceDelivery

Nov

2002

Mar

2004 Mar2013Dec2005 Dec2006

time

SAP BW 2.0B (GA)

SAP BW 2.1C (GA)

SAP BW 3.0B (GA)

SAP NetWeaver 04SAP BW 3.5 (UrS)

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

8/22/2019 rmc_1250813687

7/86

SAP AG 2005, 7

Upgrading to SAP BI 3.5 Upgrade Paths

Upgrade from supported releases SAP BW 2.x, SAP BW 3.x, SAP BI3.1 Content, and BI Content Add-on 3.2 and 3.3 available

Direct Release Upgrade possibil ities

BI Content 3.3

BI Content 3.2

BW 3.1 ContentSAP BW 3.0B

SAP BW 2.1C

SAP BW 2.0B

BI_Cont 351

SAP_BW 350

Components:

Full Release

Upgrade

BI_Cont 352

SAP_BW 350

Components:

Add-On Delta

upgrade

Content release Content releases underlying technical release

8/22/2019 rmc_1250813687

8/86

SAP AG 2005, 8

Upgrading to SAP BI 3.5 Basis/Web AS Viewpoint

Upgrade of underlying Basis/Web Application Server (AS) releaseto Web AS 6.40

Direct upgrade possible from Basis 4.6x

BW 2.1C

BI_Cont 351

SAP_BW 350

Components:

Full Release Upgrade

(SAP BW and Web AS) Add-On Delta

upgradeBI_Cont 352

SAP_BW 350

Components:

Web AS 6.40

Web AS 6.40

BI Content 3.3

BI Content 3.2BW 3.1 Content

BW 3.0B

BW 2.0BWeb AS 6.20

Basis 4.6D

Basis 4.6C

Important reminder:

SAP BWs Web AS is not a separate instance, installation, or optional!!

8/22/2019 rmc_1250813687

9/86

SAP AG 2005, 9

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)

8/22/2019 rmc_1250813687

10/86

SAP AG 2005, 10

SAP BW 3.5 Upgrade Requirements SAP BW System Requirements

SAP BW System requirements for upgrade:

SP 4 OR >SP 4 OR >N/AN/API_BASIS 2003_1_620

Version 6.00

SAPKD62015

(6.20)

Latest (32 or >)

Latest (32 or >)

SP 16 orgreater

Latest version

6.20 (173+)

3.0B

SAPKD62015

(6.20)

SAPK0050/33

(4.6D)

SAPKD0040/32

(4.6C)

SPAM/Saint Patch lvl

Version 6.00Version 6.00Version 6.00EPx.0/WP plug-in*

SP 9 or greaterSP 1 or greaterSP 8 or greaterSAP_BW SupportPackage

Latest (32 or >)Latest

(12 or >)

Latest

(23 or >)

SAP_BASIS Support

Package

Latest (32 or >)Latest

(12 or >)

Latest

(23 or >)

SAP_ABA Support

Package

Latest version

6.20(173+)

Latest version

4.6D^

Latest version

4.6D^

Basis Kernel version

3.1/3.2/3.32.1C2.0BSAP BW System

Executable versions (min):

tp OS/390: 320.56.57

All other tps: 320.56.56

R3trans: 09.07.2002

Source: SAP note 658992

PREPARE now checks the versions of executables

^ See SAP Note 318846 for Kernel (upgrade) installation info

* See SAP Note 655941 for Plug-in upgrade info

Note: All recommended OS patches/patchsets should beapplied. See specif ic OS/DB SAP notes for details.

8/22/2019 rmc_1250813687

11/86

SAP AG 2005, 11

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 unti l Jun 2005

SP 0

SP 0

PI_Basis

2004_1_620

4.7/SP4.6C/SP4.6B/SP4.5B/SP4.0B/SP3.1I/SPPlug-In/ Release SP level

SP 1SP 3SP 16SP 38SP/HR

B0/B4

PI 2003.1

SP 1SP 3SP 19SP 38SP/HR

B2/C9

PI 2004.1

(SP lvls to be conf irmed

Check SAP notes)

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)

Key tip: Source system plug-in can be the longest timeline in an upgrade projectPlan accordingly!

8/22/2019 rmc_1250813687

12/86

Overview




Prepare and upgrade

SAP BW upgrade

8/22/2019 rmc_1250813687

13/86

SAP AG 2005, 13

Upgrade Prep: SAP BW 3.x Landscape and the Web

WEB

Browser

HTTP

ITS

SAP BW 2.0

Web

Server.

ITS

Mainly used for Web-enablingexisting SAP applications

Dynpro-based

SAP BW used ITS only as a

gateway (WEBRFC)ITS Flow Logic was only used

in special cases

mySAP Web AS

Enhanced scalability,performance, and robustness

Generation of charts and mapson Internet Graphic Server (IGS)

Support of background

processingGeneration of mobi le report ing

types in SAP BW server

Easy administration

SAP BW 3.0 with

mySAP Web AStechnology

IGS

8/22/2019 rmc_1250813687

14/86

SAP AG 2005, 14

IGS Installation and Requirements

If you are upgrading from BW 2.x, you must installthe 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 conf iguring

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 solut ions, seeOSS Note 459674

8/22/2019 rmc_1250813687

15/86

SAP AG 2005, 15

BW 3.x

Web AS

The IGS Landscape for SAP BW

IGSGIS

Engine

Chart-

Engine

Internet

External system

RFC/HTTP

RFC

HTTP

HTML +Java

SAP Dialog-Protocol and Automation-Calls

HTTP Protocol, for HTML, J avaScript, J avaApplets, etc.

EP 5.0

The user never calls IGS directly; graphics generation is server : server

8/22/2019 rmc_1250813687

16/86

SAP AG 2005, 16

IGS Installation and Upgrade:Distributed Architecture Standalone

Component

Communication component

Data interpreter (semantics)

System boundaries*

Network

Data conversion (syntax)

Workload-balancing check

PWPortwatcher

PWPortwatcher

ZipperZipper

PWPortwatcher

PWPortwatcher

Zip InterpreterZip Interpreter

Chart

Control

ChartControl

SAP BWChart Interpreter


PWPortwatcher

PWPortwatcher

Chart

Control

ChartControl

SAP BWChart

Interpreter

SAP BWChart

Interpreter

GeocoderGeocoder

Interpreterfor GIS

Interpreterfor GIS

RFCListener

RFCListener

HTTPListener

HTTPListener

MUXMultiplexer

MUXMultiplexer

ICM

WP

WP

WP

dispdisp

ICM

WP

WP

WP

dispdisp

ICM

WP

WP

WP

dispdisp

SAP BW System RFC Dest

8/22/2019 rmc_1250813687

17/86

SAP AG 2005, 17

IGS Installation and Upgrade: Distributed Architecture Application Server Installation

Component

Communication component

Data interpreter (semantics)

System boundaries*

Network

Data conversion (syntax)

Workload-balancing check

Note: On differentapplication

servers!

PWPortwatcher

PWPortwatcher

ZipperZipper

PWPortwatcher

PWPortwatcher


ChartControl

ChartControl



PWPortwatcher

PWPortwatcher

ChartControl

ChartControl

SAP BWChart

Interpreter

SAP BWChart

Interpreter

GeocoderGeocoder

Interpreterfor GIS

Interpreterfor GIS

RFCListener

RFCListener

HTTPListener

HTTPListener

MUXMultiplexer

MUXMultiplexer

PWPortwatcher

PWPortwatcher

ZipperZipper

PWPortwatcher

PWPortwatcher


ChartControl

ChartControl



PWPortwatcher

PWPortwatcher

ChartControl

ChartControl

SAP BWChart

Interpreter

SAP BWChart

Interpreter

GeocoderGeocoder

Interpreterfor GIS

Interpreterfor GIS

RFCListener

RFCListener

HTTPListener

HTTPListener

MUXMultiplexer

MUXMultiplexer

CI MSMS

ICM

WP

WP

WP

dispdisp

ICM

WP

WP

WP

dispdisp

RFC Dest RFC Dest

8/22/2019 rmc_1250813687

18/86

SAP AG 2005, 18

SAP BW 3.5 Upgrade Requirements IGS ChartMigration

Converting chart settings (BLOB to XML)

The conversion of chart settings is mandatory when you used charts in SAP BW Webapplications 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 storedin 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 theWeb objects successfully see Upgrade Guide

The conversion of the chart settings is based on the prior successful conversion of theWeb Objects

If you start the conversion of the chart settings although the Web objects conversion didnot succeed, you can no longer repeat the Web Objects conversion. Then, you must

correct all open problems manually!

8/22/2019 rmc_1250813687

19/86

Overview




Prepare and upgrade

SAP BW upgrade

8/22/2019 rmc_1250813687

20/86

SAP AG 2005, 20

Upgrade Preparation and Prerequisites: AlphaConversion

After the check has executed, the user must decide whether to: Remove the conversion exit

Convert the characterist ic

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

All characteristics found are listed in three groups

Characterist ics 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 wi thout 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

8/22/2019 rmc_1250813687

21/86

SAP AG 2005, 21

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

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

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

was given only i f transfer rules in SAP BW and R/3 extraction were dif ferent

(some content InfoObjects were initially delivered incorrectly)

Upgrade Preparation and Prerequisites: AlphaConversion (cont.)

111 0000000111

11 1 11 1

11A1 11A1

0001110 0000001110

Internal format

0000000111 111

11A1 11A1external format

0 0 0 1 0 0 0 1

0 1 0 1

Trans. Structure Char 4 Comm. Structure Char 6

Values are not

found when

entered on Dynpro

8/22/2019 rmc_1250813687

22/86

SAP AG 2005, 22

Upgrade Preparation and Prerequisites: AlphaConversion (cont.)

The Alpha converter:(Trx: RSMDCNVEXIT)

Start the check job

Check job

status

Conversion status

Conversion jobstatus

Start the

conversion job

Conversion decisions

8/22/2019 rmc_1250813687

23/86

Overview


Foundations and Requirements


Prepare and upgrade

SAP BW upgrade

8/22/2019 rmc_1250813687

24/86

SAP AG 2005, 24

PREPARE Upgrade Process

Features:

May run any time before the upgrade

Only minor influence on production operation

Check system prerequisites

Run PREPARE early to determine necessary actions

Configure the upgrade

Specify support packages

Supply add-on upgrade CDs

Specify languages

Check system status

Open repair requests Incomplete imports

Update tasks

SAP BW-specif ic checks ...

Extension

Integration

Initialization

CHECK modules

8/22/2019 rmc_1250813687

25/86

SAP AG 2005, 25

System Switch Upgrade Strategy

Overview of the Process:

4.6x* 6.40SAP BW

DATA

6.40SAP BW

DATA

DATAconversion

4.6x*

4.6x*

6.40

6.40

Shadowactivation

Shadowinstallation

SPDD

Import

XPRAPhase

4.6x*SAP BW

DATA

* Example:

2.x -> 3.5 upgrade (4.6x)

3.x -> 3.5 would use 6.20

8/22/2019 rmc_1250813687

26/86

SAP AG 2005, 26

System Switch Upgrade Strategy (cont.)

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

Benefits:

Almost constant downtime even with packages

Modif ication adjustments during uptime Destination release features in Basis database objects

Data dictionary and SPDD (at f ixed support package level 0)

Patches of central Basis dictionary objects

Ability to distribute upgrade processing to different servers

Costs:

Increased overall runtime

Start-to-finish time is increased

Increased system resources

Shadow instance requires additional CPU and memory

off

off

o

n

o

n

8/22/2019 rmc_1250813687

27/86

SAP AG 2005, 27

Downtime Minimized An SAP BW Perspective

The system switch and upgrade strategies provide options for thecontinued productive use of SAP BW

Productive use:

From an SAP BW perspective, this refers to the abil ity to execute

queries against the SAP BW system

If Downtime minimized is selected, users can expect approximately2-4 hours of upgrade-processing-related downtime for executionsof queries

Other SAP BW operations: Note: Operations such as Data loading, Data and SAP BW object

administration, and SAP BW query element building should ceaseat the start of R3up

These SAP BW operations create objects in the Data Dictionaryand Database

Plan accordingly to cease admin operations!

No automated SAP BW lock process

System objects l ike DDIC will be locked automatically

8/22/2019 rmc_1250813687

28/86

SAP AG 2005, 28

System Switch Upgrade: Timing Diagram

Up

time

Down

time

Resource-Minimized

Bac

kup

Inst.

Sha

dow

Ins

tance

(on

targe

tre

lease

)

New

Rel.

Stop of

Productive use

(Strategy dep.)

Production Downtime

resource-minimized

Upgrade

Post

Imp.

Bac

kup

Downtime-MinimizedDowntime-MinimizedBac

kup

Ac

tiva

tion

Distributio

n

Support

Pac

ks

Add-On

s

Mo

dificati

on

Adjus

tme

nt

Importo

fCon

tro

lDa

ta

inCopyTa

bles

ICNV

Importo

f

Su

bs

titution

Se

t

Upgrade

Production Downtime

downtime-minimized

Bac

kup

PREPARE Upgrade

8/22/2019 rmc_1250813687

29/86

SAP AG 2005, 29

The Upgrade Itself: Best Practices and Tips

Some R3up phases do not have individual logs

useCONNECT.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.

Key Upgrade Resources: Service Marketplace

8/22/2019 rmc_1250813687

30/86

SAP AG 2005, 30

Key Upgrade Resources: Service MarketplaceAlias BW

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

8/22/2019 rmc_1250813687

31/86

SAP BW system copy

SAP BW upgrade


Wrap-up

What Well Cover

8/22/2019 rmc_1250813687

32/86

Overview


Unicode concepts

SAP BW and Unicode



8/22/2019 rmc_1250813687

33/86

Overview


Unicode concepts

SAP BW and Unicode



Unicode Essentials

8/22/2019 rmc_1250813687

34/86

SAP AG 2005, 34

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

ISO 639 Languages Supported by Unicode

8/22/2019 rmc_1250813687

35/86

SAP AG 2005, 35

Afar

AbkhaziaAvestanAfrikaansAmharicArabicAssameseAymaraAzerbaijani

BashkirBelarusiaBulgarian

Uzbek

VietnameseVolapkWolofXhosaYiddishYorubaReserved- cust.ZhuangChinese trad.

ChineseZulu

BihariBislamaBengali

TibetanBretonBosnianCatalanChechenChamorroCorsicanCzechChurch Slavic

ChuvashWelshDanishGerman

TeluguTajikThaiTigrinyaTurkmenTagalogTswanaTongaTurkishTsongaTatarTwi

TahitianUighurUkrainianUrdu

DzongkhaGreekEnglishEsperantoSpanish

EstonianBasquePersianFinnishFijianFaroeseFrenchFrisianIrish

GaelicGalleganGuaraniGujarati

ManxHausaHebrewHindiHiri MotuCroatian

HungarianArmenianHereroInterlinguaIndonesianInterlingueInupiakIcelandicItalian

InuktitutJapaneseJavaneseGeorgianKikuyu

KuanyamaKazakhGreenlandicKhmerKannadaKoreanKashmiriKurdish

KomiCornishKirghizLatinLetzeburgeschLingalaLaoLithuanianLatvianMalagasyMarshalleseMaoriMacedonianMalayalamMongolianMoldavian

MarathiMalayMalteseBurmeseNauruNorwegian Bokml

NdebeleNepaliNdongaDutchNorweg. NynorskNorwegianNdebeleNavajoNyanja

OccitanOromoOriyaOssetianPanjabi

PaliPolishPushtoPortugueseQuechua

Raeto-RomanceRundiRomanianRussianKinyarwandaSanskritSardinianSindhiNorthern SamiSangoSerbo-CroatianSinhaleseSlovak

ISO-639 Languages Supported by Unicode

SAP Languages and Code Pages: Pre-Unicode

8/22/2019 rmc_1250813687

36/86

SAP AG 2005, 36

Choose one ellipsis:

All languageswithin this ellipsis

can be combined

within one (non-

Unicode) R/3System

Example:

With ISO-8859-2,

you can use all the

following languages:Croatian

Czech

Hungarian

Polish

Romanian

Slovak

Slovenian

German

English

SAP Languages and Code Pages: Pre-Unicode

Croatian

Czech

HungarianPolish

Romanian

Slovak

Slovenian

English

German

Turkish

Danish

Dutch

Finnish

French, Italian

Norwegian

Portuguese

Spanish

Swedish

Russian

Ukrainian

Greek

Hebrew

Thai

Korean

Chinese(Trad.)

Chinese

(Simp.)

Japanese

8/22/2019 rmc_1250813687

37/86

Overview


Unicode concepts

SAP BW and Unicode



SAP BW 3.5 Languages/Unicode

8/22/2019 rmc_1250813687

38/86

SAP AG 2005, 38

SAP BW 3.5 Languages/Unicode

The fol lowing languages are delivered with SAP BW 3.5

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 MDMPsource systems

SpanishSlovenianSlovakianRussianRomanian

TurkishSwedish

PortuguesePolishNorwegianKoreanJapaneseItalianHungarianHebrewGreekGerman

FrenchFinnishEnglishDutchDanish

CzechCroatianChinese trad.ChineseBulgarian

Unicode-Compliant SAP BW

8/22/2019 rmc_1250813687

39/86

SAP AG 2005, 39

Unicode Compliant SAP BW

Unicode compliance means: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 pageconversion

Unicode Release Planning

8/22/2019 rmc_1250813687

40/86

SAP AG 2005, 40

Unicode Release Planning

Which versions of SAP BW are released for Unicode andWhich versions of SAP BW are released for Unicode andwhen are they available?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 BW Unicode Installation and Conversion

8/22/2019 rmc_1250813687

41/86

SAP AG 2005, 41

How can I make my SAP BW UnicodeHow can I make my SAP BW Unicode--compliant?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 export ing the

database, realigning the database, and import ing 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

Resource Requirements for Unicode-Compliant SAP BW

8/22/2019 rmc_1250813687

42/86

SAP AG 2005, 42

q p

Additional resource requirements after a Unicode conversion: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 addit ional 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 similarto the SAP R/3 requirements

Disk Storage

Disk Storage depends strongly on the underlying DBMS and the given data

model/volume. For a signif icant share of InfoCube data (only numeric keys!), theremight 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

8/22/2019 rmc_1250813687

43/86

Overview


Unicode concepts

SAP BW and Unicode



The Unicode Conversion Project: Overview

8/22/2019 rmc_1250813687

44/86

SAP AG 2005, 44

PreparationPreparationPreparation

Set up the UnicodeSet up the Unicode

upgrade projectupgrade project

Perform list of tasks toPerform list of tasks to

prepare system forprepare system for

migrationmigration

ConversionConversionConversion

To be done duringTo be done during

system downtimesystem downtime

Export/import processExport/import process

entire database contentsentire database contents

Use of SAP BWUse of SAP BW

migration toolmigration tool

Post-ConversionPostPost--ConversionConversion

Up and Running

Verification of

Data Consistency

Integration Testing

focused on

language handling

Conversion Preparation: Transaction SPUMG

8/22/2019 rmc_1250813687

45/86

SAP AG 2005, 45

Pre-ConversionUnicode Conversion

Post-ConversionSet up the

Conversion

Project

Check

Prerequisites

Plan database

downtime during

conversion

Enable Customer

Developments

Unicode system is

up and running

Verification of

Data Consistency

Integration

Testing focused

onlanguage

handling

SUMG

Post-ConversionRepairs

in Unicode

system

SAPInst

(R3load)

Database

Export,

Conversion

& Import

SPUMG

Conversion

Preparation

in

non-Unicodesystem

Database Export, Conversion, and Import

8/22/2019 rmc_1250813687

46/86

SAP AG 2005, 46


Post-Conversion

SUMG

Post-ConversionRepairs

in Unicode

system

SPUMG

Conversion

Preparation

in

non-Unicodesystem

SAPInst

(R3load)

Database

Export,

Conversion,

and Import

Unicode system is

up and running

Verification of

Data Consistency

Integration

Testing focused

onlanguage

handling

Set up the

Conversion

Project

Check

Prerequisites

Plan database

downtime during

conversion

Enable Customer

Developments

Database Export, Conversion, and Import: Basis

8/22/2019 rmc_1250813687

47/86

SAP AG 2005, 47

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

Database Export, Conversion, and Import: Tools

8/22/2019 rmc_1250813687

48/86

SAP AG 2005, 48

The system setup tool SAPInst is used for the entire systemcopy 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 otherSAP basis objects (e.g., partitioned tables)

As a system copy to Unicode, database conversion and system

shutdown/Unicode system start will be completely automated

R3Load Export

8/22/2019 rmc_1250813687

49/86

SAP AG 2005, 49

SAPInst is used as Frontend tool Logs are written to the SAPInst directory

Export Files are written to the Export directory

SAP System

non-Unicode

Export DIR:

SAPAPPL0.001 SAPAPPL1.001

...

.

.

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

Database-independent format(big or li ttle endian,

depending on platform)

R3load.exe -datacodepage 4103e ....

Space needed on Export directory:

~10-25% of database size

Multiple processes

possible

Default: One process (STR file) per data class

(see SE11 Technical Settings) Advanced Export options: 50 largest tables get

own process each

Example: fr (0x66 FC 72 0x0066 00FC 0072)Non-UC R3Load

R3Load Import

8/22/2019 rmc_1250813687

50/86

SAP AG 2005, 50

SAPInst is used as frontend tool Non-UC database can be deleted or UC database can be installed on

dif ferent server

Import procedure nearly same as new installation

Special SAP BW objects procedures included

SAP

System

Unicode

Export DIR:

SAPAPPL0.001 SAPAPPL1.001

...

.

.

Multiple processes

possible.

Number of processes

same as during export

(default)

UC R3Load

R3load.exe -i ....

Unicode System: Transaction SUMG

8/22/2019 rmc_1250813687

51/86

SAP AG 2005, 51


Post-Conversion

SPUMG

Conversion

Preparation

in

non-Unicodesystem

SAPInst

(R3load)

Database

Export,

Conversion

& Import

SUMG

Post-

Conversion

Repairs in

Unicode

system

Unicode system is

up and running

Verification of

Data Consistency

Integration

Testing focused

onlanguage

handling

Set up the

Conversion

Project

CheckPrerequisites

Plan database

downtime during

conversion

Enable Customer

Developments

Runtimes

8/22/2019 rmc_1250813687

52/86

SAP AG 2005, 52

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

Runtimes Customer Experiences

8/22/2019 rmc_1250813687

53/86

SAP AG 2005, 53

Customer example Export

Database: Oracle

Operating system: Unix

CPU frequency: 731 MHzSystem: 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 fi les: 194 GB

Runtimes Customer Experiences (cont.)

8/22/2019 rmc_1250813687

54/86

SAP AG 2005, 54

Customer example Import

Database: Oracle

Operating System: Unix

CPU Frequency: 1150 MHzSystem: 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

DB Growth Customer Experience

8/22/2019 rmc_1250813687

55/86

SAP AG 2005, 55

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

UTF-16+41,3%650460

CESU-8-17,0%93112

CESU-8-23,4%674880

UTF-16+63,6%3622

CESU-8-13,0%461530CESU-8-11,4%271306

Unicode

Encoding

Database

Growth in %Size after

Conv.in GB

Size before

Conv.in GB

8/22/2019 rmc_1250813687

56/86

SAP BW system copy

SAP BW upgrade


Wrap-up

What Well Cover

8/22/2019 rmc_1250813687

57/86

Overview


System copy: SAP BW refresh w/o Source System

SAP BW system copy

System copy: Source System refresh w/o SAP BW

System landscape configuration

System copy:SAP BW and Source System together

8/22/2019 rmc_1250813687

58/86

Overview



SAP BW system copy




A Few Words about SAP BW System Refreshes

8/22/2019 rmc_1250813687

59/86

SAP AG 2005, 59

There are essentially four types of SAP BW system refreshes withdiffering 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 systemin parallel

There are many reasons why system copies are performed. It is usuallya 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 isrequired. Example: refresh of an R/3 QAS system from the R/3 Product ion 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

Key Technologies Relevant to SAP BW SystemConfigurations

8/22/2019 rmc_1250813687

60/86

SAP AG 2005, 60

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 c lient cannot have the same logical system name as an SAP BW

client

SAP BW system

Client 100

LogSys: BWCL100

R/3 system

R/3 system

SAP BW system

Client 100

LogSys: BWCL100

R/3 system

R/3 system

Client 000

LogSys: BWCL100

Client 000

LogSys: BWCL000

Client 300

LogSys: R3CL300

Client 200

LogSys: R3CL200

Client 200

LogSys: R3CLT200 Client 200LogSys: R3CL200Client 100

LogSys: BWCL100

Client 200

LogSys: R3CL200

Key Technologies Relevant to SAP BW SystemConfigurations (cont.)

8/22/2019 rmc_1250813687

61/86

SAP AG 2005, 61

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

* Note: The same principle applies to any SAP Source System (SAP APO, mySAP CRM, SAP BW, etc.)

BW

CRM

R/3

DEV QAS PRD

Transports Transports



ALE/RFC ALE/RFC ALE/RFC

ALE/RFCALE/RFCALE/RFC

CRDCRQ CRP

BWD BWQ BWP

R3D R3Q R3P


8/22/2019 rmc_1250813687

62/86

SAP AG 2005, 62

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)

SAP BW

R/3

DEV QAS PRD




BWD BWQ BWP

R3D R3Q R3P

Logical System:

BWCL100

Logical System:

BWCL100

Logical System:

BWCL100

Logical System:

R3CL200

Logical System:

R3CL200

Logical System:

R3CL200

Example:

SAP BW client and

one R/3 client as

a Source System


8/22/2019 rmc_1250813687

63/86

SAP AG 2005, 63

Option 1 is recommended by SAP Development as it simpli fies 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 with in each system type (DEV, QAS, PRD)

SAP BW

R/3

DEV QAS PRD




BWD BWQ BWP

R3D R3Q R3P

Logical System:

BWDCL100

Logical System:

BWQCL100

Logical System:

BWPCL100

Logical System:

R3DCL200

Logical System:

R3QCL200

Logical System:

R3PCL200

Example:

SAP BW client

and one R/3 client as

a Source System


8/22/2019 rmc_1250813687

64/86

SAP AG 2005, 64

Implications of each Logical system naming option:

Support for connections between SAP BW system in a systemlandscape (e.g., QAS BWQ connect ing to both PRD BWP)Support complex ALE scenarios(e.g., DEV BWD connecting to both DEV R3D and QAS R3Q)

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 renaming not required after system copy

Logical System Naming strategy can be changed at a later time(conversion effort can be significant!)

Logical system names unique across system landscapeLogical system names unique across each system type

Option 2Option 1


8/22/2019 rmc_1250813687

65/86

SAP AG 2005, 65

Relationships between SAP BW Objects in SAP BW andSource Systems

Critical relationships exist between objects in each of your SAP-basedSource 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 objectrelationships

Failure to consider this could leadto object and data inconsistencies,and in the worst cases, incompatible

data load scenarios Additionally, the Data consistency

between SAP BW and your SourceSystems should be considered.Will old data be compatible with new?

DataSources, Transfer structures,Extraction enhancement, Deltaextraction status, Data compatibi lityshould all be considered

8/22/2019 rmc_1250813687

66/86

Overview



SAP BW system copy




System Copy of Both the SAP BW and Source Systems

S i A t f th SAP BW d S S t (i ll l) i

8/22/2019 rmc_1250813687

67/86

SAP AG 2005, 67

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 exist ing systems

Examples of such uses: creation of a test upgrade landscape or production f irefighting 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

R/3

DEV QAS PRD

Logical System:

R3CL200

Logical System:

R3CL200

Logical System:

R3CL200

Example:

Create an upgradeTesting system

TST

Logical System:

R3CL200


R3D R3Q R3P R3T

Copy

SAP BWTransports Transports

BWD BWQ BWP

Logical System:

BWCL100

Logical System:

BWCL100

Logical System:

BWCL100

BWT

Logical System:

BWCL100

Copy

ALE/RFCALE/RFCALE/RFC ALE/RFC

System Copy of Both the SAP BW and Source Systems(cont.)

2) Using unique LSNs across systems in the same landscape (see diagram below):

8/22/2019 rmc_1250813687

68/86

SAP AG 2005, 68

) g q y p ( g )

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 exist ing 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

SAP BW

R/3

DEV QAS PRD

Logical System:

BWDCL100

Logical System:

BWQCL100

Logical System:

BWPCL100

TST

Logical System:

BWTCL100

Logical System:

R3DCL200

Logical System:

R3QCL200

Logical System:

R3PCL200

Logical System:

R3TCL200


R3D R3Q R3P R3T

Copy


BWD BWQ BWP BWTCopyExample:

Create an upgradeTesting system

ALE/RFCALE/RFCALE/RFC ALE/RFC


8/22/2019 rmc_1250813687

69/86

SAP AG 2005, 69

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 toBWTCL100

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/3system for certain documents.

If so, a large number of documents (sales orders, etc.) may be tagged with thelogical system name for ALE purposes. These would have to be converted.

It is suggested that you analyze your R/3 system before executing thisconversion (BDLS has a test function, but runtimes can be just as long as theconversion itself)Note: Connecting SAP BW to your R/3 system does not enable this ALEfunctionality!


8/22/2019 rmc_1250813687

70/86

SAP AG 2005, 70

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

parallel is the simplest choice for system refreshyet 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

outl ined in the system copy procedure

Optional: You can add steps to save SAP BW Objects from the old SAP BW

System and Source systems

R/3

DEV QAS PRD

Logical System:

R3CL200

Logical System:

R3CL200

Logical System:

R3CL200


R3D R3Q R3P

Copy

SAP BWTransports Transports

BWD BWQ BWP

Logical System:

BWCL100

Logical System:

BWCL100

Logical System:

BWCL100

Copy



P

8/22/2019 rmc_1250813687

71/86

SAP AG 2005, 71

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

mult iple Source Systems

Cons:

Coordination of timing for the system refresh

Al l work in QAS systems must be completedand imported into PRD or reapplied after refresh

8/22/2019 rmc_1250813687

72/86

Overview



SAP BW system copy



System copy:

SAP BW and Source System together

SAP BW System Refresh Without Source Systems

Scenario: The SAP BW system is refreshed without refreshing the Source System in

8/22/2019 rmc_1250813687

73/86

SAP AG 2005, 73

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 wil l 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 mult iple Source Systems may want to consider using the InfoObject0LOGSYS in data models as it provides an easier mechanism for selecting data during Datasynchronization

BW

R/3

DEV QAS PRD




BWD BWQ BWP

R3D R3Q R3P

Logical System:

BWDCL100

Logical System:

BWQCL100

Logical System:

BWPCL100

Logical System:

R3DCL200

Logical System:

R3QCL200

Logical System:

R3PCL200

Example:

SAP BW client and one

R/3 client as a Source

System Unique LSNs

Copy

SAP BW System Refresh Without Source Systems(cont.)

Steps to connect your SAP BW and Source System after the refresh

8/22/2019 rmc_1250813687

74/86

SAP AG 2005, 74

p y y

Also see SAP note 184754 for more detailed information

We are using the example on the previous sl ide

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, deletethe 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 forthe BWQ Source System and delete the old BWP RFC destination

4. In the newly refreshed SAP BW system, delete the original Source Systemconnection. (connection to R3PCL200 in our example)

1. Warning: Ensure that the RFC Destination is not funct ioning (dummy)!

2. In the Admin Workbench, delete the R/3 Source System (R3PCL200). This maytake some time as all the transfer rules and PSA tables are deleted

SAP BW System Refresh Without Source Systems(cont.)

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

8/22/2019 rmc_1250813687

75/86

SAP AG 2005, 75

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 BWQCL100to 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

8/22/2019 rmc_1250813687

76/86

Overview



SAP BW system copy



System copy:

SAP BW and Source System together

Source Systems Refresh Without SAP BW System

Scenario: The Source system is refreshed without refreshing the connectedSAP BW system in parallel

8/22/2019 rmc_1250813687

77/86

SAP AG 2005, 77

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 Al l 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 InfoObject0LOGSYS in data models, as it provides an easier mechanism for selecting dataduring Data synchronization

SAP BW

R/3

DEV QAS PRD




BWD BWQ BWP

R3D R3Q R3P

Logical System:

BWDCL100

Logical System:

BWQCL100

Logical System:

BWPCL100

Logical System:

R3DCL200

Logical System:

R3QCL200

Logical System:

R3PCL200

Copy

Example:

SAP BW client and one

R/3 client as a Source

System Unique LSNs

Source Systems Refresh Without SAP BW System(cont.)


8/22/2019 rmc_1250813687

78/86

SAP AG 2005, 78


Also see SAP note 184322 for more detailed information

We are using the example diagrammed on the previous sl ide

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

Source Systems Refresh Without SAP BW System(cont.)

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

8/22/2019 rmc_1250813687

79/86

SAP AG 2005, 79

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 connectionto 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 bere-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

8/22/2019 rmc_1250813687

80/86

SAP BW system copy

SAP BW upgrade


Wrap-up

What Well Cover

7 Key Points to Take Home

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

8/22/2019 rmc_1250813687

81/86

SAP AG 2005, 81

The preparation steps are often more time consuming than the actualupgrade runtime itself

2. Unicode is a global effort towards handling all characters in the worldsmajor and minor languages in systems

3. Converting an SAP BW system to Unicode requires significant effort, asan SAP BW system migration is part of the process

4. An SAP BW Unicode system migration is similar to a heterogeneousDB/OS migration, which is a pilot project for SAP BW systems

5. SAP BW system copies require system landscape planning, and thelogical system naming convention has a big impact

6. Carefully plan any system copy activities, as object dependencies withSource System objects must be considered

7. System refreshes can be avoided through good change managementtechniques, avoiding disruption to the landscape

Further Information on the SAP Service Marketplace

SAP BW

SAP R/3 Enterprise

8/22/2019 rmc_1250813687

82/86

SAP AG 2005, 82

http://service.sap.com/bw

SAP NetWeaverhttp://service.sap.com/NetWeaver

Unicodehttp://service.sap.com/globalization

p

http://service.sap.com/enterprise

New Release Strategyhttp://service.sap.com/releasestrategy

Release Noteshttp://service.sap.com/releasenotes

Upgrade Information Centerhttp://service.sap.com/upgrade

SAP Plug-Inhttp://service.sap.com/R3-Plug-In

Services from SAP Support and SAP Consulting

SAP SDNhttp://sdn.sap.com

Safeguardinghttp://service.sap.com/safeguarding

Maintenance Strategyhttp://service.sap.com/maintenancestrategy

Safeguarding Upgradehttp://service.sap.com/safeguardingupgr

ade

For More Information: Access the SAP Developer Network www.sdn.sap.com

The central hub for the SAP technology

community

8/22/2019 rmc_1250813687

83/86

SAP AG 2005, 83

y

Everyone can connect, contr ibute, 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

Questions?

8/22/2019 rmc_1250813687

84/86

SAP AG 2005, 84

Feedback

8/22/2019 rmc_1250813687

85/86

SAP AG 2005, 85

Please complete your session evaluation

and drop it in the box on your way out.

[email protected]

8/22/2019 rmc_1250813687

86/86

Date post:	08-Aug-2018
Category:	Documents
Upload:	papalinux
View:	213 times
Download:	0 times

rmc_1250813687

Documents