CUpgrade Unicode Conversion

Combined Upgrade and UnicodeConversionSession Code 1104

Nils Buerckel,SAP Globalization Services, SAP AG

© SAP 2009 /

1. Why to upgrade and convert to Unicode2. Upgrade Procedure3. Unicode Conversion Steps on SAP System Level

ABAP EnablingInterface adaptationExport / Import OptimizationVocabulary Handling

4. Combination of Upgrade and Unicode Conversions5. Best Practices6. Wrap-Up and Appendix

Agenda

© SAP 2009 /

SAP ERP 6.0 Is the Go-To Release

Enterprise services enabled

Delivers 28 configurableindustry solutions

Continuous innovation

300+ functional enhancements

Dramatic user experienceimprovements

Provides a long-term foundation for excellence and innovation

© SAP 2009 /

Unicode provides a unique number for every character,no matter what the platform,no matter what the program,no matter what the language.

Unicode Essentials: What is Unicode?

Unicode is a character encoding schema containing(almost) all characters used world wide.

See www.unicode.org for complete code charts

http://www.unicode.orgfor/

© SAP 2009 /

Japanese

SAP Non-Unicode World – „Code Page Islands“

Latin-1

„Code Page Islands“

Latin-2

Cyrillic

Local Characters not supported

Chinese (Simpl)

Korean

Chinese (Trad)

Thai

Greek

TurkishBaltic

© SAP 2009 /

SAP Unicode World - Without Language Limits

Unicode

© SAP 2009 /

Single Code Pages in SAP Systems

Turkish

CroatianCzechHungarianPolish

RumanianSlovakian

Slovene

English

GermanDanish

Dutch,Finnish

French, ItalianNorwegianPortugueseSpanish

Swedish

RussianUkrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

Taiwanese

Every Ellipse representsone code pageSingle Code Page

System means that onlylanguages within ONE

ellipse can be usedMDMP*: More than one

code page / ellipse is usedwithin one system

Icel

andi

c

*MDMP: Multiple Display Multiple Processing code page

© SAP 2009 /

UNICODE: Example Languages supported inUnicode

Turkish

CroatianCzechHungarianPolish

RumanianSlovakian

Slovene

English

GermanDanish

DutchFinnish,

French, ItalianNorwegianPortugueseSpanish,

Swedish

RussianUkrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

Taiwanese

Icel

andi

c

FarsiHindi

BashkirPanjabi

Sanskrit

ArabicAzerbaijani

BelarusianBengali

UrduVietnamese

UnicodeEllipse

© SAP 2009 /

Unicode Support: Market Situation

Unicode is the established international standard to support multiple character setswithin one consolidated character set and within one system

Unicode is a prerequisite for all new technologiesJava is fully Unicode basedXML is fully Unicode basedThe Euro sign (€) is only represented in Unicode

Most software companies offer Unicode only software for some time already

Unicode is the official way to implement International Organization forStandardization (ISO) and is supported on most operating systems and all modernbrowsers

© SAP 2009 /

Who Needs Unicode?

Acting in global business requires support of a global character set and manymore language features!

Companies running global business processes such as global HR systems or global MasterData ManagementCompanies offering Web services to their customers: global master data containing multiplelocal language charactersCompanies using open standards: J2EE and .NET integration (Java speaks Unicode only!)Collaborative business: integration of third-party products that run on different code pagesCompanies want to make use of “language dialects” (e.g., Brazilian Portuguese andPortuguese Portuguese) require new Unicode-only language keys.Companies want to enter new countries requiring local languages for legal reasons such as FIreporting.

Example: Vietnam. Vietnamese language has a complex script and is only supported withUnicode – SAP delivers the Vietnamese Translation as of February 2009

© SAP 2009 /

SAP NetWeaver™ With Non-Unicode ABAPStack Limited

Evolution ofSAP technology

Unifies and aligns people, information,and business processes

Integrates across technologies andorganizational boundariesA safe choice with full .NET and J2EEinteroperability

The business foundation for SAP andpartners

Powers business-ready solutions thatreduce custom integrationIts Enterprise Services Architectureincreases business process flexibility

DB and OS Abstraction.NET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Lifecycle Managem

ent

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeaver™™

DB and OS Abstraction

Master Data Management

……

no

no

no

© SAP 2009 /

SAP NetWeaver™ With Non-Unicode ABAPStack Limited

DB and OS Abstraction.NET

WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeaver™™

DB and OS Abstraction

Master Data Management

……

Evolution ofSAP technology

Unifies and aligns people, information,and business processes

Integrates across technologies andorganizational boundariesA safe choice with full .NET and J2EEinteroperability

The business foundation for SAP andpartners

Powers business-ready solutions thatreduce custom integrationIts Enterprise Services Architectureincreases business process flexibility

yes

yes

yes

• Java runs on Unicode only• If ABAP stack runs in non-Unicode,conversion from/to Unicode and non-Unicode required! Can lead to data loss!• Full language data consistency only withboth ABAP and Java stack in Unicode

© SAP 2009 /

Pre-Unicode Solution for Multiple Languages:MDMP*West European View Japanese View Korean View

No support as of SAP ERP 6.0

*MDMP = Multi-Display, Multi-Processing (Mixed Code Page) system

© SAP 2009 /

Native Language Support in SAP ERP(SAP Note 79991)

Conditionallysupported (forlimitations see SAPNote 838402)

Supported (forlimitations see SAP

Note 838402)

Supported (forlimitations see SAP

Note 838402)

Supported

Single codepage system

No support (SAPNote 79991)

No support (SAPNote 79991)

Supported andrecommendedERP 6.0

Support veryrestricted (No

new installs)

Support restricted(SAP Note 747036),

(No new installs)

Supported andrecommendedERP 2004

Support veryrestricted (No

new installs)

Supported, but nolonger recommended

Supported andrecommendedR/3 Enterprise

Supportrestricted (No

new installs)

Supported, but nolonger recommendedNot possibleR/3 4.6C

Blended codepage system*MDMPUnicode

ERP release

Languagetechnology

The best option is to go for Unicode as soon as possible(*) please check with SAP for details about blended code pages support

© SAP 2009 /

Ways to Your Unicode SAP System

Unicode conversion without upgrade

Combined Upgrade and Unicode conversion (CU & UC)

Twin Upgrade and Unicode conversion (TU & UC)

Supported Unicode conversion paths

Releases: R/3 Enterprise 4.7 Ext. 110 and 200 (Web AS 6.20) *ECC 5.0 (ERP 2004) (Web AS 6.40)

Source releases: R/3 4.6CR/3 Enterprise 4.7 (Web AS 6.20)ECC 5.0 (ERP 2004) (Web AS 6.40)

Target release: ECC 6.0 (ERP 6.0) (NW AS 7.00)

Release independent, target release Unicode enabled* : Web AS = SAP Web Application Server

© SAP 2009 /




Agenda

© SAP 2009 /

Upgrade: Up- and Downtime: The Timing DiagramU

ptim

eD

ownt

ime

Prepare Upgrade

Inst. Prod. DowntimeDowntime-minimized

Resourced-minimized

Bac

kup

NewRelease

Shad

ow In

stan

ce(o

n ta

rget

rele

ase)

Upgradepost

Imp.

Bac

kup

Stop of Production(strategy-dep.)

Bac

kup

Downtime-minimized

ICN

V

Impo

rt o

fSu

bstit

utio

n Se

tSu

ppor

t Pac

k’s

Act

ivat

ion

Dis

trib

utio

n

EhP’

s

Mod

ifica

tion

Adju

stm

ents

Add

-Ons

Upgrade

Prod. DowntimeResourced-minimized

Binding SP’s, EhP’s and Add-onsdoes not impact significantly the

downtime!

© SAP 2009 /

Features of the ABAP Upgrade to ECC 6.0

Oldest SAP start release 3.1I

Main upgrade tools are PREPARE and SAPup

Improved usability for including additional packages into upgradeWizard based, all “decisions” on one screenAllows changes to decisions without restart of prepare phase

Reduced downtime through parallel import of software packages(shadow import and main import)

Improved fixpack (corrections) conceptIncludes improvements and error corrections to upgrade tool, keeps your upgrade to lateststate

Support for Switch frameworkSAPup migrates former Industry Solutions Add-ons into Switch Framework technology

Support for combined upgrade and Unicode conversion

© SAP 2009 /




Agenda

© SAP 2009 /

ABAP Enabling of Customer Developments I

Single ABAP source for Unicode and non-Unicode systemsNo explicit Unicode data type in ABAPAll character like data types are stored as Unicode in a Unicode system andNon-Unicode in a Non-Unicode system

This requires a clear distinction between character and byte processing inUnicode:

One Character One ByteAdditional Syntactical restrictions

1 character = 2 bytes (UTF16),(types C, N, D, T, STRING)Unicode kernelUnicode database

1 character = 1 byte(types C, N, D, T, STRING)Non-Unicode kernelNon-Unicode database

ABAPsource

Non-UnicodeSAP R/3

UnicodeSAP R/3

ABAPsourceABAPsource

© SAP 2009 /

Unicode flag ( “Unicode checks active”) is used as a Program Attribute to control theUnicode enabling procedure

A program without Unicode flag is NOT executable on a Unicode system

Transaction UCCHECK can be used as tool to analyze customer codingExperiences: Approx. 10 objects can be fixed by a developer per dayTransaction UCCHECK available as of SAP NetWeaver AS 6.20

Start release >= SAP NetWeaver AS 6.20UCCHECK can be run before or during Unicode conversion

Start release <= 4.6C (CU&UC or TU&UC*)Execute the whole UCCHECK procedure in the SBX Unicode systemUpgrade the DEV system to SAP ERP 6.0 (Non-Unicode or Unicode) and execute UCCHECK(Additional Maintenance System necessary)

*CU&UC = Combined Upgrade and Unicode Conversion*TU&UC = Twin Upgrade and Unicode Conversion

For more information please see http://service.sap.com/unciode@SAP

ABAP Enabling of Customer Developments II

Monitor and identifyobsolete programs upfront

Customer Quote:

http://service.sap.com/unciode@SAP

© SAP 2009 /




Agenda

© SAP 2009 /

Interface Adaptation: Unicode and Non-Unicode

SAP R/3 4.6C

3rd PartyEBCDIC

SAP NetWeaver BIISO8859-1

SAP R/3 Enterprise

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

697/0277

697/0500

1252

Files

ISO8859-1SJIS

...charset=iso-8859-1" >...charset=windows-1257" >

...charset=utf-8" >...charset=Shift_JIS" >

Internet

RFC Client(char)

SAP_CODEPAGE= 1100

JAVAApplication

(Portal)Conversions betweenincompatible code pagespossibleOnly a common subset oflanguage charactersexchangeableSpecial rules have to beobeyed to makecommunication possible...

© SAP 2009 /

Example: Interface Handling in Non-Unicodeand Unicode via RFC

ABAP Unicode

Non-Unicode Unicode

Code Page 1100

Code Page 1401

Code Page 1500

….

Code Page 8000

SM59 Settings

Logon Language

UTF-8

UTF-16

Interface Type

ABAP Non-Unicode

Non-Unicode

1. Determination ofNon-Unicode

or Unicode (Default:SM59)

2. Determination ofspecific Non-Unicode

character setto use (Default:

Logon Language)

Usually noconversion necessary*

*in case of ABAP Non-Unicodeto ABAP Unicode transfer,

the Unicode systemconverts the data

© SAP 2009 /

Interface Adaptation: Rules and Restrictions

Choice for Data Transfer: Non-Unicode or UnicodeChangeable in RFC Connections (Transaction SM59) on the Unicode systemCan be specified in File Down- and Upload

In case of Unicode - Non-Unicode CommunicationRule of Thumb: Logon Language / Batch Job Language controls in most cases the Unicode –Non-Unicode conversion

SAP MDMP SAP Unicode (Exception: TABLES parameter and language key intable)File Up- and DownloadCommunication between SAP Unicode Non-SAP Non-Unicode System

Logon Language is changeable in programs via SET LOCALE LANGUAGE <lang>

Don’t forget yourInterfaces !Customer Quote:

© SAP 2009 /




Agenda

© SAP 2009 /

Database Export, Conversion and Import:Overview

SPUMG

R3load

ControlTable

Voca-bulary

EXPORT

IMPORT

nonUnicode

+ Conversion

Re-process

Log

UnicodeData R3load

System Copy procedure used for Unicode ConversionImport and export during downtimeUnicode Conversion during ExportUsually downtime optimization necessary

System Vocabulary:

Unicode View:

© SAP 2009 /

Unicode Conversion Downtime Dependencies

Overall Database size

Size of specific TablesSize of largest tablesSize of cluster tables

Available HardwareNumber and speed of CPUsI/O Performance of disksSeparate server available for PRD Unicode systemAdditional (temporary) hardware available for export and import

SettingsSpecial r3load export / import options (e.g., unsorted export)Profile parameters (see SAP Notes 784118 and 857081)

Time and number of tests spent on optimization

Archive dataif possible upfront

Customer Quote:

© SAP 2009 /

Export / Import Optimization - Options

Use Standard run time Optimization ToolsOptimize database settings during Export / ImportOptimize R3Load Settings– Unsorted Export– Loadprocedure fast for importEnhance hardware– Use new hardware for Unicode System and execute export and import on

different systems with Migration MonitorTable Split– Large tables need to be split and table parts can be processed in parallelDistribution Monitor– Additional Application Servers can be used

If the Optimization enhancements outlined above do not result in an acceptabledowntime

Minimized Downtime Service (MDS) is offered by SAP Consulting (Emailaddress: [email protected])

Do a test on aHardware comparable to your

PRD environmentCustomer Quote:

mailto:[email protected])

© SAP 2009 /

Runtimes – Customer Experiences

• Net Runtimes on PRD systems: Time needed from begin of Export until end of Import (w/oe.g. Upgrade, Prepare Jobs, Back-up, Tests after the conversion … etc)• Most of the shown examples used two Servers (Export on Server 1 and Import on Server 2 inparallel).

• Experiences show that the reduction can be significantly high when using the TwoServers Scenario (e.g. from 50 h 28 h for the runtimes).

Examples for Technical Unicode Conversion Downtime(Database Size > 1000GB)

0

10

20

30

40

50

60

800 2800 4800 6800 8800 10800

DB size in GB (before Conversion)

Tech

nica

l Dow

ntim

e in

hou

rs

Standard ConversionMDS

Customers with “smaller” systems,lower downtime requirements and/or

smaller Hardware capabilitySmaller Investment in Downtime Opt.

Customers with “larger” systems,higher downtime requirements and/or

higher Hardware capabilityHigher Investment in Downtime Opt.

Note: These numbers do not includeupgrade downtime

© SAP 2009 /

Overview of Likely Unicode HardwareRequirements

Nearly no change due to efficient compression0%Network

10% is the observed maximum for larger systems (DB size > 200GB).35% is the observed maximum in growth for small systems (DBsize < 200 GB).

UTF-8: +10%UTF-16: +30-60%

Database

OLTPInternally, application servers are based on UTF-16

+40-50%RAM

Depends on transaction mix(MDMP, double byte)

+10-30%*CPU

CommentsRange of AdditionalResource Consumption

KPI

NoteThe table includes the additional resource consumptions as measured in the benchmark tests as well as headroom toaccommodate a mixture of different transactionsDB vendors must additional CPU/RAM Hardware resource requirements on standalone DB servers

* We observed dependencies in the processor type. Modern processors showed 10%increase, older processors up to 30%. So if you update your hardware you'll have toexpect less increase than when you continue to use your old hardware

© SAP 2009 /




Agenda

© SAP 2009 /

Vocabulary Handling: MDMP* Preparation –Transaction SPUMG

MDMP system is a “Mixed code page solution”

ALL table rows in the database must be assigned a certaincode page before the Unicode conversion of an MDMPsystem is possible !Data with a language key can be converted without additional effortDatabase is scanned in order to find problematic texts without a language key

Transaction SPUMG is used to scan the databaseand insert the problematic words without languageinformation into a system vocabularySystem Vocabulary needs to be fully maintained using different methods

Find additional fields of the table in order to determine the code pageUse Statistical methods

Maintain manually by native speakersThe system vocabulary information is used duringthe Unicode conversion (Database Export)

System Vocabulary:

Database contains textual data from several code pages.

*MDMP: Multiple Display Multiple Processing code page

© SAP 2009 /

Vocabulary Handling: MDMP Preparation –SPUMG / SUMG

SPUMG RequirementsAvailable as of SAP NetWeaver AS 6.20 (4.6C: SPUM4 is available)Full SPUMG scans necessary for MDMP / Ambiguous Blended Codepages before theconversion (export / import)Manual maintenance necessary by native speakers

Best PracticesCreate sandbox as copy of PRD system and run SPUMG/SPUM4 and conversion on thisSandboxMaintain SPUMG (Vocabulary and Reprocessing logs) properly during this conversion andtransfer results to other systems in landscapeRepair data in SUMG

© SAP 2009 /

MDMP Post-Processing: Repair IncorrectlyConverted Data

© SAP 2009 /

MDMP: Code Page Combinations andVocabulary I

The following topics influence the effort for the vocabulary and reprocessing log workThe more code pages in use, the higher the effortONE Latin code page combined with ONE Non-Latin Code Page (see below for definition) usuallycauses low effort for the vocabulary and reprocess log maintenanceThe combination of more than one Non-Latin code page causes very high effort

Asian Code pages, Cyrillic,EL, HE

Latin-1, Latin-2, Latin-5(TR), Baltic

Non-Latin Code PagesLatin Code Pages

What is a Latin and Non-Latin code page ?

Do notunderestimate add. effort for

an MDMP conversionCustomer Quote:

© SAP 2009 /




Agenda

© SAP 2009 /

Combined Upgrade and Unicode Conversion(CU & UC)

CU&UC (Combined Upgrade and Unicode Conversion) is a procedure to integrateUpgrade and Unicode Conversion in one Weekend

MDMP scans can be executed before UpgradeSequential approach (first Upgrade, then Unicode conversion) for most other steps

Primary focus: customers on start release = 4.6C and MDMP

Also possible for start releases > 4.6C and/or single code page (SCP) systems

Please read SAP Note 928729 for details

1. Upgrade2. Conversion

to UnicodeSAP R/3 4.6CMDMP SAP ECC 6.0

non-Unicode

SAPECC 6.0Unicode

Preparation

DOWNTIMEPRODUCTIONTIME

PRODUCTIONTIME

SAPECC 6.0Unicode

© SAP 2009 /

Twin Upgrade and Unicode Conversion (TU &UC)

TU&UC (Twin Upgrade and Unicode Conversion) is an alternative procedure toCU&UC

Additional scan system (copy of PRD - called Twin system) needed for MDMP scansResults of MDMP scans are transferred to PRD system during conversion weekend

Primary focus: customers on start release < 4.6C and MDMP

Also possible for other start releases on MDMP, but not available for SCP systems

Please read SAP note 959698

1. Upgrade 2. Conversionto UnicodeSAP R/3 4.5B

MDMPSAP ECC 6.0

non-Unicode

SAPECC 6.0Unicode

DOWNTIMEPRODUCTIONTIME

PRODUCTIONTIME

SAPECC 6.0Unicode

SAP ECC 6.0non-UnicodeSAP R/3 4.5B

MDMP

UpgradeSystem Copy

SPUMG

TWIN RUN

Impo

rtre

sults

© SAP 2009 /

Overview: Support Matrix for Combination ofUpgrade and Unicode Conversion

MDMPNot supportedSCPReleases <

SAP R/3 4.6C

MDMPSCP/MDMPSCPSAP R/3 4.6C

MDMPSCP/MDMPSCPSAP R/3

Enterprise

MDMPSCP/MDMPSCPSAP ERP 2004

TU&UCCU&UCUpgrade andUnicode

Conversionseparated*

SourceRelease

ConversionType

SCP: SingleCode Page System

MDMP: MixedCode Page System

*Might be also combined in one weekend

© SAP 2009 /




Agenda

© SAP 2009 /

Example for Sequence: CU&UC with SourceRelease 4.6C

Preparation-TasksTechnical Upgrade and

Conversion Post-Conversion

PREPARE (all systems)

MDMP preparation –SPUM4 (all systems)

Interface – Evaluation(DEV / QAS / SBX)

Downtime (all Systems)

Upgrade + SPDD (allSystems)

Unload /reload process(all Systems)

Test - DowntimeOptimization (SBX / QAS)

Redo UC conversion ntimes (SBX)

1. Check and Repairproblematic Data –

Transaction SUMG (allsystems)

2. SPAU (DEV)3. Enabling of Customer

Developments-UCCHECK (DEV / SBX)

4. Integration Testing withfocus on

Adapted customer ABAPprogramsInterfaces

(SBX / QAS)

Non-Unicode System

Unicode System

DEV = Development SystemSBX = Sandbox SystemQAS = Quality Assurance SystemPRD = Production System

All Systems =

© SAP 2009 /

Example: Sequence for CU & UC Conversion

1. Create sandbox (SBX) as copy of productive system (PRD)SPUM4/language scans/vocabulary

2. Upgrade and Unicode conversion of SBX (repeat UC conversion n times, n >= 2)Downtime Optimization / SUMG Handling

3. Unicode conversion of development (DEV) systemABAP reconciliation/SPAU in ECC 6.0 (Unicode)ABAP Unicode enablingCombine ABAP Unicode enabling with SPAU (synergy!)

4. Unicode conversion of quality (QAS) system

5. Conversion of SBX – PRD dress rehearsal (n times, depends)Last dress rehearsal should be “as near as possible” to the PRD conversion

6. Unicode conversion of PRD

Note: Additional maintenance system(s) might be needed to support PRD system after Upgrade ofDEV

© SAP 2009 /

Example for a Conversion Landscape

SBN

PRD

SBU

Maintenance Landscape

DEV QAS

DEV QAS

Standard Landscape

SANDBOX Landscape

Unicode Conversion

System Copy / Backup & Restore

Transport

SID Unicode

SID Non-Unicode

Highly recommended

The more planning andpractice the better

Customer Quote:

© SAP 2009 /

Typical 3 System Landscape CU&UC: Planning

2009

Production

Sandbox Environment*

Quality Assurance

Development

Kickoff CU&UC Project

Unicode GO-Live

Jan Feb Mar Apr May

ABAP Enabling

PREPARE + SPUM4 + Upgrade +Export/Import

Testing (Upgrade + Unicode)

Performance Optimization test(Export / Import)

All ABAP Objects areUnicode enabled

Assumption:Start Release: 4.6CMDMP CustomerDB Size: ~ 1TBDowntime Window: 48 h

Development Freeze highly recommended or additional DEV system and double maintenance mandatory

* Ideally this Sandbox Environment consists of twosystems – one for Non-Unicode and one for

Unicode system with the Hardware comparable tothe PRD conversion

Dress Rehearsal

Plan sufficienttime

Customer Quote:

© SAP 2009 /

CU&UC: How long does it take and how muchdoes it cost ?

How long does it take to convert a system landscape ?Shortest Project time: ~ 3 monthsVery long projects: ~ One yearAverage Project time:

MDMP systems: ~ 29 weeks (Sample: 18 customers)Single Code Page systems: ~ 24 weeks (Sample: 27 customers)

Strong Influence:MDMP or single code pageDatabase Size (Export / Import Performance Optimization effort)Number of customer specific development objects and modifications

What are the cost dependencies ?Staff needed

Project Management / Netweaver specialists / Programmer / Application specialists for UCCHECK /Interface / UpgradeStaff for TestingNative speakers for vocabulary work (MDMP systems)External consulting

Additional Hardware requirementAdditional Hardware required on landscape due to release change and upgradeTemporarily required Hardware

© SAP 2009 /

Which Factors influence the CombinedApproach (Upgrade and Unicode Conversion)

Easy / Short Medium Difficult / Long

Used Language Technology SingleCode Page

AsianCode Page

MultipleCode Pages (MDMP)

System properties:Database Size

DowntimeHardware performance

Small database sizeLong Downtime window

Good performing Hardware

Large database sizeSmall Downtime window

Bad performing Hardware

ABAP Enabling (UCCHECK) Small Amount of Customer ObjectsEasy objects (CS, …)

Large Amount of Customer ObjectsDifficult Objects (Offset)

Source Release (ERP) (SAP ECC 6.0) R/3 EnterpriseOr ECC 5.0

4.6C Releases < 4.6C

Number of CustomerDevelopments and Modifications

High NumberLow Number

(Technical) Upgrade Efforts

Unicode Efforts

Upgrade and Unicode Efforts

Interfaces to Non-SAP systems Unicode basedSystems

Single Code PageAsian

Single Code PageLatin

Interfaces to SAP systems SAP Singlecode page

SAP MDMP+ ALE (Container)

SAP MDMP+ TABLES

SAP UnicodeSystems

© SAP 2009 /

Two Examples for Upgrade and UnicodeConversion Combination in one Project

Add PrepUC

SPUMG(MDMP) RADCUCNT Export Import SUMG Add Post

UC

Add Prep 1UC PREPARE SPUM4

(MDMP) UPGRADE Post UPG

Add PrepUC

SPUMG(Delta) Export Import SUMG Add Post

UC

PREPARE UPGRADE Post UPG

RADCUCNTAdd PrepUC

SPUMG(SCP) Export Import Add Post

UC

Unicode Conversion without Upgrade (MDMP)

CU&UC with MDMP and start release 4.6C

Combined Sequential Approach with Single code page System (SCP) (NOT CU&UC)

Upgrade

UnicodeConversion

UnicodeConversion

Upgrade

UnicodeConversion

RADCUCNT(Delta)

SPUMG(Delta)

0

1

2

© SAP 2009 /

Areas of Testing - Focus on Unicode

Application TestsAll business critical scenarios need to be tested

Especially all business critical InterfacesCustomer specific ABAP objects (UCCHECK objects)

Netweaver TestsExport / Import in generalExport / Import with focus on runtime OptimizationMDMP specific SPUM4 / SPUMG tests in generalMDMP specific SPUM4 / SPUMG runtime OptimizationSUMG (runtime)

General Tests (Cross Application – language specific) – mainly for MDMPSPUM4 / SPUMG: Vocabulary and reprocessing assignmentSUMG: Manual repair (assignment)Check / test proper conversion of texts containing special characters

Test, Test, Test, Test !

Customer Quote:

© SAP 2009 /

Test and Execution of Unicode Tasks in aCombined Approach (Upgrade and Unicode)

Execute Scans: Yes*Maintain vocab and

reprocessing: High

Execute: YesExecute: NoExecute: NoPRD

Execute Scans: YesMaintain vocab and

reprocessing: Medium

Execute: MediumTest: Medium

Execute: NoTest High

Execute: NoTest High

QAS

Execute Scans: YesMaintain vocab and

reprocessing: Low

Execute: LowTest: Low


Execute MediumTest Medium

DEV

Execute Scans:HighMaintain vocab andreprocessing: highTest: High

Execute: HighTest: High

Execute: MediumTest: Low


SBX

VocabularyHandling and

DB Scans

Export/ImportOptimization

InterfaceAdaptation

Abap EnablingStep

only needed in MDMP / Blended CP systemsneeded for ALL Unicode conversions

*except for TU&UC Sandbox is verynecessary for determining“timing” and “complicating

factors”Customer Quote:

System

© SAP 2009 /

Summary: Recommendations and Quotes fromCustomers who did a Unicode Conversion I

Test, Test, Test, Test !

Monitor and identifyobsolete programs upfrontPlan sufficient time

Archive dataif possible upfront

The more planning andpractice the better Do a test on a

Hardware comparable to yourPRD environment

Sandbox is verynecessary for determining“timing” and “complicating

factors”

Don’t forget yourinterfaces

Do notunderestimate add. effort for

an MDMP conversion

© SAP 2009 /

Summary: Recommendations and Quotes fromCustomers who did a Unicode Conversion II

Use partners who didit before

Expert consultingwith prior experience

is essential

Build an FAQ projectdatabase.

Have a Step by Stepdocument for the conversion

weekend

Mainly a timing issue

Practical Advice

© SAP 2009 /

Unicode is THE ONLY TRUE technical language solution tomeet global customers’ language requirements

7 Key Points to Take Home

222

111

333

444

555

666

777

Unicode is THE ONLY SAP future technical languagesupport strategy

Up from SAP WEB AS 6.20 all SAP Products are availablein Unicode

Up from SAP ERP 6.0 MDMP (mixed codepage) solutionis no more supported.

All new SAP applications released since 2007 are deliveredin Unicode only

Combined and optimized upgrade and Unicode conversionprocedures CU & UC and TU & UC are availableGood planning and downtime optimization makes yourcombined upgrade and Unicode conversion successful

© SAP 2009 /

Book “Unicode in SAP Systems”

http://www.sappress.com/product.cfm?account=&product=H1984

SAP PRESS340 pagesISBN 978-1-59229-135-9

http://www.sappress.com/product.cfm?account=&product=H1984

© SAP 2009 /

Information Resources

SAP Service Market Place: http://service.sap.com

SAP Globalization home page: Quick link GLOBALIZATION(http://service.sap.com/GLOBALIZATION)*

SAP Unicode home page: Quick link UNICODE(http://service.sap.com/UNICODE)*

SDN: https://www.sdn.sap.com/irj/sdn

SAP Internationalization: Quick link I18N(https://www.sdn.sap.com/irj/sdn/i18n)

Technical Unicode Info(https://www.sdn.sap.com/irj/sdn/i18n Unicode )

Questions ? Write to: [email protected]

* Only available for SAP Customers

http://service.sap.com/

http://service.sap.com/GLOBALIZATION

http://service.sap.com/UNICODE

https://www.sdn.sap.com/irj/sdn

https://www.sdn.sap.com/irj/sdn/i18n

https://www.sdn.sap.com/irj/sdn/i18n

mailto:[email protected]

© SAP 2009 /

Appendix: Overview: Unicode ConversionAreas for an SAP System

Test with PRD copy assoon as possible

Full maintenance ofthe vocabulary andreprocessing log

Large Tables: UseTable Split

Table SplitDistribution Monitor2-Server-Method

Test n times

Test as soon aspossible

Test as soon aspossible

Recommendation

Weeks to MonthsScans can potentially

run long times

Weeks to MonthsSeveral tests might be

necessary

Weeks to MonthsA few complicated

interfaces can take longtime

Weeks to Months~10 Abap objects per

developer and day

Typical Duration

Netweaver ExpertsNative Speakers(Application Experts)

Netweaver ExpertsApplication ExpertsDevelopment ExpertsNetweaver Experts

Application ExpertsDevelopment Experts

Needed Skills

Number, type andcombination ofused code pages(see next slide)Database Size

Database Size ofSystemDowntimeRequirementsHardwareressources

Number and Type ofInterfaces

Number and type ofABAP Objects

EffortDependencies

VocabularyHandling and

DB Scans

Export/ImportOptimization

InterfaceAdaptation

Abap Enabling

only needed in MDMP / Blended CP systemsneeded for ALL Unicode conversions

© SAP 2009 /

Appendix: MDMP: Code Page Combinationsand Vocabulary

CommentsReason for ClassificationUnicode ConversionClassification (Vocabularyand Reprocess Logs)

High number of words invocab, and very highdifficulty to assign

Latin 1 and Latin 2 languages and Asianlanguages need to be distinguished

Very HighL1, L2, JA, KO

High number of words invocab and high difficulty toassign

Distinguishing between Cyrillic, EL or HE isvery complex

HighCyrillic, EL, HE

High number of words invocab and high difficulty toassign

Distinguishing between different Asianlanguages is very complex

High to Very HighJA, KO, ZH, ...

High number of words invocab, but easy to assign

Distinguishing between L1 and Asianlanguages is easy

Rather LowL1, JA

High number of words invocab and medium difficultyto assign

Adding Cyrillic to L1/L2 causes additionalvocabulary entries (e.g. German Words),

Assignment of one-byte words can beproblematic

Medium to HighL1, L2, Cyrillic

High number of words invocab, but easy to assign

Distinguishing between L1 and Cyrillic is easyRather LowL1/Cyrillic

Relatively small number ofwords in the vocab

German Words are usable in both codepages

LowL1, L2

© SAP 2009 /

Further Information

Related Workshops/Lectures at ASUG 20091906 Upgrading to SAP ERP Central Component (SAP ECC) 6.0 and

Converting to Unicode in a Complex Environment

Related SAP Education and Certification Opportunitieshttp://www.sap.com/education/

SAP Public Web:SAP Developer Network (SDN): www.sdn.sap.comBusiness Process Expert (BPX) Community: www.bpx.sap.com

http://www.sap.com/education/

http://www.sdn.sap.com/

http://www.bpx.sap.com/

© SAP 2009 /

Thank you!

Nils Buerckel

SAP AGRaiffeisenring 44D-68789 St. Leon-Rot Germany

T +49/6227/7-46410F +49/6227/7-828792

[email protected]

mailto:[email protected]

http://www.sap.com/

© SAP 2009 /

Copyright 2009 SAP AGAll 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 changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned and associated logos displayed arethe 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 writtenpermission 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 thatthis 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 theaccuracy 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 orimplied, 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 limitationshall 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 thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie diedazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen vonProdukten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Formauch immer, nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. Bei dieser Publikation handelt es sich um eine vorläufige Version, die nicht Ihrem gültigen Lizenzvertragoder anderen Vereinbarungen mit SAP unterliegt. Diese Publikation enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts. SAP entsteht aus dieserPublikation keine Verpflichtung zu einer bestimmten Geschäfts- oder Produktstrategie und/oder bestimmten Entwicklungen. Diese Publikation kann von SAP jederzeit ohne vorherigeAnkündigung geändert werden.

SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen, Texte,Grafiken, Links und sonstigen in dieser Publikation enthaltenen Elementen. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a.,aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.SAP haftet nicht für entstandene Schäden. Dies gilt u. a. und uneingeschränkt für konkrete, besondere und mittelbare Schäden oder Folgeschäden, die aus der Nutzung dieser Materialienentstehen können. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen,unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über InternetseitenDritter ab.

Alle Rechte vorbehalten.

CUpgrade Unicode Conversion

Documents

Transcript of CUpgrade Unicode Conversion