UC Conv Topics

SAP Unicode ConversionTopics

Solution Management Globalization ServicesSAP AGOctober, 2008

© SAP 2008 / Page 2

1. Unicode Introduction2. Unicode Conversion Steps on SAP System Level3. Options for Upgrade and Unicode Conversions4. Unicode Conversion of Complex System Landscapes5. Summary and additional Information

Agenda

© SAP 2008 / Page 3


Agenda

© SAP 2008 / Page 4

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 2008 / Page 5

SAP Unicode World - without Borders

Unicode

© SAP 2008 / Page 6

Single Code Pages and MDMP* (Non-Unicode)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 2008 / Page 7

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 2008 / Page 8

Requirement: One System, Multiple Languages

Engl

ish

German

French

Japanese

© SAP 2008 / Page 9

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

What is Unicode?

© SAP 2008 / Page 10

Application Impact – MDMP Restrictions

West European View Japanese View Korean View

© SAP 2008 / Page 11

No Restrictions on a Unicode System

UnicodeUnicode

© SAP 2008 / Page 12

Is there a Business Requirement for Unicode?

Global Business requires the support of a Global Character Set.

What, if your business is running business processes that are truly global?Example: Global HR System or Global Master Data Management

What, if you open your systems to the Web?Imagine a Web Service offering your customers to enter theircontact data

Using Internet StandardsThe SAP Netweaver technology offers open integration

J2EE integration – JAVA speaks UnicodeEnabling Collaborative Business

Third party products running on any possible code pageSolution of the R/3-centric past – MDMP (Multi Display Multi Processing) is not supportedanymore in SAP ERP 6.0

Mixed code page technology depending on logon languageMeant for well-defined users accessing the solution using SAPGUI

© SAP 2008 / Page 13


Agenda

© SAP 2008 / Page 14

ABAP UnicodeEnabling

InterfaceAdaptation

TechnicalConversion

MDMPHandling

Building Blocks of Unicode ConversionProjects

© SAP 2008 / Page 15

1. Unicode Introduction2. Unicode Conversion Steps on SAP System Level

ABAP EnablingInterface adaptationExport / Import OptimizationVocabulary HandlingSequence and Planning of a Unicode Conversion

3. Options for Upgrade and Unicode Conversions4. Unicode Conversion of Complex System Landscapes5. Summary and additional Information

Agenda

© SAP 2008 / Page 16

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 2008 / Page 17

Problem: Minor part of ABAP coding written before release SAP Netweaver AS6.10 has to be adapted to comply with Unicode restrictions

Different types of errors: “Concatenate“ versus “Access To Structures withOffset/Length”All objects created on a SAP NetWeaver AS 6.20 based SAP system areUnicode enabled by default

Solution: Unicode Enabling can be done before the actual Unicode conversionon the Non-Unicode system as of R/3 Enterprise 4.7Unicode flag ( “Unicode checks active”) is used as a Program Attribute tocontrol the Unicode 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: 5000 – 10000 lines of ABAP code can be enabled by adeveloper per dayTransaction UCCHECK available as of SAP NetWeaver AS 6.20

ABAP Enabling of Customer Developments II

© SAP 2008 / Page 18

ABAP Enabling of Customer Developments III

Start release >= SAP NetWeaver AS 6.20Complete Decoupling of UCCHECK from Unicode Conversion– Enable ABAPs in Non-Unicode Environment, test and transport to PRD (Non-

Unicode)Integrate UCCHECK into the Unicode Conversion project– Enable ABAPs in Non-Unicode Sandbox system, convert SBX system to Unicode

and test ABAPs in Unicode systemIntegrate UCCHECK in the Upgrade (without an integrated Unicode Conversion)Mixed solution:– Decoupling for running projects and Integrating for other existing objects

Start release <= 4.6C (CU&UC or TU&UC*)Execute the whole UCCHECK procedure in the SBX Unicode systemUpgrade the DEV or SBX system to SAP ERP 6.0 (Non-Unicode or Unicode) andexecute 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

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

© SAP 2008 / Page 19




Agenda

© SAP 2008 / Page 20

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 2008 / Page 21

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 2008 / Page 22

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>

See also SAP Note 1021459Asian Languages

Container-Problem (Conversion - Misalignment) can cause additional effort

© SAP 2008 / Page 23




Agenda

© SAP 2008 / Page 24

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 2008 / Page 25

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])

mailto:[email protected])

© SAP 2008 / Page 26

Runtimes – Customer Experiences

• Net Runtimes on PRD systems: Time needed from begin of Export until end of Import (w/oe.g. 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 Two ServersScenario (e.g. from 50 h 28 h for the runtimes).

Examples for Export / Import Runtimes(Database Size > 1000GB)

0

10

20

30

40

50

60

800 1800 2800 3800 4800 5800 6800 7800 8800 9800

DB size in GB

Net

Run

times

in h

ours

© SAP 2008 / Page 27




Agenda

© SAP 2008 / Page 28

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 methodsMaintain manually by native speakers

The 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 2008 / Page 29

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 2008 / Page 30

Vocabulary Handling: SPUM* – Long ScanTimes

How to manage long scan times in The SPUM* Scans:Use Table Split Feature in SPUMG / SPUM4

Large tables can be split in multiple parts and these chunks can be processed in parallel

See also SAP Note 1096903

© SAP 2008 / Page 31

Vocabulary Handling: High Amount ofunassigned Words in Vocabulary

How to manage a high amount of words:Use available vocabulariesUse Language dependent scanMake use of Statistical functionsUse Vocabulary PatternsUse Hints to maintain words

Scan of Language-Dependent Tables

Import of Existing Vocabulary

Statistical Methods based on TechnicalAttributes

Statistical Methods

Use of Vocabulary-Patterns

Creation and Use of Hints

Manual Maintenance

Vocabulary Maintenance:

© SAP 2008 / Page 32

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 ?

© SAP 2008 / Page 33

MDMP: Code Page Combinations andVocabulary II

CommentsReason for ClassificationUnicode ConversionClassification (Vocabularyand Reprocess Logs)

High number of words invocab, and very highdifficulty to assign

Latin 1 and Latin 2languages and Asianlanguages need to bedistinguished

Very HighL1, L2, JA, KO

High number of words invocab and high difficulty toassign

Distinguishing betweenCyrillic, EL or HE is verycomplex

HighCyrillic, EL, HE

High number of words invocab and high difficulty toassign

Distinguishing betweendifferent Asian languages isvery complex

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

High number of words invocab, but easy to assign

Distinguishing between L1and Asian languages is easy

Very LowL1, JA

High number of words invocab and medium difficultyto assign

Adding Cyrillic to L1/L2causes additional vocabularyentries (e.g. German Words)

MediumL1, L2, Cyrillic

High number of words invocab, but easy to assign

Distinguishing between L1and Cyrillic is easy

Very LowL1/Cyrillic

Relatively small number ofwords in the vocab

German Words are usable inboth code pages

LowL1, L2

© SAP 2008 / Page 34




Agenda

© SAP 2008 / Page 35

Sequence in a Unicode Conversion of an SAPSystem

Preparation-TasksTechnical Conversion

Post-Conversion

MDMP preparation –SPUMG (all Systems)

Enabling of CustomerDevelopments-

UCCHECK (DEV / SBX)

Interface – Evaluation /Adaptation (DEV / QAS)

Downtime (all Systems)

Unload /reload process(all Systems)

Test DowntimeOptimization (SBX / QAS)

Redo n times (SBX)

Check and Repairproblematic Data –

Transaction SUMG (allsystems)

Integration Testing withfocus on

-Adapted customer ABAPprograms-Interfaces

(SBX / QAS)

Non-Unicode System

Unicode System

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

All Systems =

© SAP 2008 / Page 36

Typical 3 System Landscape Conversion :Sequence

SBN

PRDDEV QAS

SBN

PRDDEV QAS

SBU

SBN

PRDDEV QAS

SBU SBN

PRDDEV QAS

SBU

SBN

PRDDEV QAS

SBU

1 2

43

5

1) Create Sandbox (SBN) as Copy of Productive System (PRD)

2) Unicode Conversion of SBN SBU (n times)

3) Unicode Conversion of Development (DEV)

5) Unicode Conversion of PRD

4) Unicode Conversion of Quality Assurance (QAS)

SID Unicode

SID Non-Unicode

© SAP 2008 / Page 37

Overview: Unicode Conversion Areas for anSAP 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

Use parameterabap/unicode_checkTest

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 pagesDatabase 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 2008 / Page 38

Typical 3 System Landscape UnicodeConversion: Planning

2008

Production

Sandbox Environment*

Quality Assurance

Development

Kickoff Unicode Conversion Project

Unicode GO-Live

Jan Feb Mar Apr May

ABAP Enabling / Testing

SPUMG + Export/Import

Testing (Unicode)

Performance Optimization

All ABAP Objects areUnicode enabled

Assumption:Release: ECC 5.0MDMP CustomerDB Size: ~ 1TBDowntime Window: 48 h

Development Freeze highly recommended

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

system with the Hardware comparable to the PRDconversion

© SAP 2008 / Page 39

Which Factors influence the UC ConversionProject

Easy / Short medium Difficult / Long

Used Language Support technology SingleCode Page

AsianCode Page

MultipleCode Pages (MDMP)

Type of System SAP ERP SAP CRMwith Mobile Sales

SAP NetWeaver ASstandalone

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 Objects

Easy objects (CS, …)Large Amount of ObjectsDifficult Objects (Offset)

Conversion Methods Standard TableSplitting

Combined Upgrade& Conversion

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 2008 / Page 40

How long does it take and how much does itcost ?

How long does it take to convert one PRD system ?Shortest Project time: ~ 6 weeksVery long projects: ~ One yearAverage Project time: 4 to 5 monthsStrong Influence:

MDMP or single code pageExport / Import Performance Optimization

What are the cost dependencies ?Staff needed

Project management / Netweaver specialists / Programmer / Application specialists for UCCHECK /InterfaceTestingNative speakers for vocabulary work (MDMP systems)External consulting

Additional Hardware requirementAdditional Hardware required on landscapeTemporarily required Hardware

© SAP 2008 / Page 41


Agenda

© SAP 2008 / Page 42

Upgrade and Unicode Conversions – Optionsfor Combination

Typical SituationCustomer wants to combine a Unicode Conversion and an Upgrade

Typical QuestionsWhat is the SAP recommendation regarding sequence for the combination ?Is it possible to do it within one downtime ?Is it possible to combine Upgrade and Unicode Conversion with Relase 4.5B with MDMP ?

© SAP 2008 / Page 43

Upgrade and Unicode Conversion in differentDowntimes (SU&UC* in different Downtimes)

Upgrade and Unicode Conversions are separated

4.5B NUC 6.0 NUC 6.0 NUC 6.0 UC

Upgrade Unicode ConversionDowntime 1

Uptime

Downtime 2

SU&UC*: Separated Upgrade & Unicode Conversion

© SAP 2008 / Page 44

Upgrade and Unicode Conversion separated, but insame Downtime (SU&UC* in same Downtime)

4.5B NUC 6.0 NUC 6.0 NUC 6.0 UC

Upgrade Unicode ConversionDowntime

Upgrade and Unicode Conversions are separated, but both are executed at thesame downtime

SU&UC*: Separated Upgrade & Unicode Conversion

© SAP 2008 / Page 45

Unicode Conversion before Upgrade in oneDowntime

SAP Recommendation is to execute the Upgrade before the Unicode conversion

4.70 NUC 4.7 UC 4.7 UC 6.0 UC

Unicode Conversion UpgradeDowntime

PREPARE* * PREPARE phase has to run in downtime

© SAP 2008 / Page 46

Combined Upgrade & Unicode Conversion:CU&UC

4.6C: Enhanced SPUM4 transaction available as of September 2008

4.6C NUC 6.0 NUC 6.0 NUC 6.0 UC

Upgrade Unicode ConversionDowntimeSPUM4

Scans

PREPARE

© SAP 2008 / Page 47

Twin Upgrade & Unicode Conversion: TU&UC

TU&UC is only necessary / possible for MDMP

4.5B NUC 6.0 NUC 6.0 NUC 6.0 UC

Upgrade (PRD System) Unicode ConversionDowntime

4.5B NUC 6.0 NUC

Upgrade („Twin System“)

SPUMG

4.5B NUC

Copy PRD system

Transfer SPUMG Results(no scans in PRD system needed)

© SAP 2008 / Page 48

Overview: Possible Scenarios for Combinationof Upgrade and Unicode Conversion

Potentially longdowntime


Potentially longdowntimePREPARE duringdowntime


Two tests andDowntimesneeded

Disadvantages

One single testand downtime

No MDMP scanson PRD systemneeded




Root cause(Upgrade orUnicode) ofproblems clear

Advantages

CombinedCombinedCombinedCombinedSeparatedDowntime

MDMP onlyMDMP and SCPMDMP and SCPSingle Code Page(SCP)

Single CodePage (SCP)

Supported forCode Page

All>= 4.6C>= 4.7AllAllSupported forrelease

TU&UCCU&UCUC beforeUpgrade

SU&UC insamedowntime

SU&UC indifferentdowntimes

only necessary in MDMP /Blended CP systems

possible for SCP and MDMPpossible for SCP only

© SAP 2008 / Page 49


Agenda

© SAP 2008 / Page 50

What is Best Conversion Sequence for aComplex Landscape ? (1)

Main Rules for Deciding the Conversion Sequence in a givenLandscape

Convert MDMP Systems firstDo not extend or implement MDMP in existing Systems – Convert these systems toUnicode

The more code pages you implement in an MDMP system, the more complicated theconversion gets

Unicode compatible Release and Support Package Level need to be metCombined Approach (CU&UC or TU&UC) might be necessary

Minimize Unicode – MDMP InterfacesUnicode – MDMP Interfaces cause most effort

Convert the Fast Growing Systems in the first placeThe bigger the system, the more effort needs to be spent on downtime optimization

© SAP 2008 / Page 51

What is Best Conversion Sequence for aComplex Landscape ? (2)

Additional RulesMinimize Unicode Single Codepage Interfaces

Risk of Transfer of Non-supported characters from Unicode to Single Code PageTransfer from Single Code Page System to Unicode System without data loss

Example: Conversion of SCM or BW systems before Backend (Single Code Page)has no “data loss risk”

Conversion of multiple Systems during one Weekend only in case of very complicatedinterface problemsGet Conversion Experiences before Converting complicated SystemsIn case of multiple PRD systems with one DEV system, all PRD systems should beconverted to UnicodeCheck Multi Language Requirements in different systems

Example: SCM System is often operated in EN only – low Unicode priorityLongterm: Go for Unicode for all Systems in your Landscape

© SAP 2008 / Page 52

Example for a Conversion of Complex SystemLandscapes I

1. CU & UC Upgrade SAP R/3 4.6C MDMP toSAP ERP 6.0 (Unicode)

2. Unicode Conversion SAP CRM 5.0

3. Unicode Conversion and Upgrade of SAPNetWeaver BI 3.5 to BI 7.0

4. Unicode Conversion SAP SCM 5.0

Example forLandscape Conversion:

SAP R/34.6CMDMP

SAP SCM5.0

SAPNetWeaver

BI 3.5

SAP CRM5.0

© SAP 2008 / Page 53

Example for a Conversion of Complex SystemLandscapes II

SAP R/34.6CMDMP

SAP SCM5.0

SAPNetWeaver

BI 3.5

SAP CRM5.0

Non-Unicode

SAP ERP6.0

SAP SCM5.0

SAPNetWeaver

BI 3.5

SAP CRM5.0

Mixed

SAP ERP6.0

SAP SCM5.0

SAPNetWeaver

BI 3.5

SAP CRM5.0

Mixed

SAP ERP6.0

SAP SCM5.0

SAPNetWeaver

BI 7.0

SAP CRM5.0

Mixed

SAP ERP6.0

SAP SCM5.0

SAPNetWeaver

BI 7.0

SAP CRM5.0

Unicode only

UnicodeNon-UnicodeData Transfer

1

2 3

4

0

Sol Unicode

Sol Non-Unicode

© SAP 2008 / Page 54

1. Unicode Introduction2. Unicode Conversion Steps on SAP System Level3. Options for Upgrade and Unicode Conversions4. Unicode Conversion of Complex System Landscapes5. Summary and Additional Information

Agenda

© SAP 2008 / Page 55

Seven Key Points to Take Home

Unicode Conversion consists of 3 areas ( ABAP Enabling / InterfaceAdaptation / technical conversion )

222

111

333

444

555

666

777

For MDMP systems, in addition a potentially long running database scanis necessary

A Sandbox conversion is recommended in almost all cases

A Unicode Conversion project needs to be planned properly

A combination of a Unicode conversion and an Upgrade is possible andin many cases recommended by SAP

The conversion road map for the whole system landscape should beinvestigated as soon as possible

For the long run: all IT systems (SAP and Non-SAP) in the landscapeshould be Unicode

© SAP 2008 / Page 56

Thank you!

Nils Bürckel

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 2008 / Page 57

Appendix: General Information Sources onUnicode

Solution Management Globalization Services:Homepage: www.service.sap.com/unicode– Unicode Media Center

Technical InformationHomepage: www.service.sap.com/unicode@sap– Unicode Overview Library– Unicode Conversion Guides– Combined Upgrade & Unicode Conversion– ABAP and Unicode Library

Book „Unicode in SAP Systems“http://www.sappress.com/product.cfm?account=&product=H1984

http://www.service.sap.com/unicode

http://www.service.sap.com/unicode@sap

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

© SAP 2008 / Page 58

Appendix: Information Sources on specificUnicode Topics I

Unicode ABAP Enablinghttp://service.sap.com/unicode@sap ABAP and Unicode Library ProgrammingABAP Programs in Unicode Systems: Requirementshttp://help.sap.com/ SAP R/3 and R/3 Enterprise SAP R/3 Enterprise Release 4.70

mySAP Technology Components SAP Web Application Server ABAPProgramming and Runtime Environment ABAP Programming ABAP and Unicodehttp://help.sap.com/erp2005_ehp_03/helpdata/EN/62/3f2cadb35311d5993800508b6b8b11/frameset.htm

Interfaceshttp://service.sap.com/unicode@sap Unicode Events Events 2005 SAP Teched2005 External Unicode Interfaceshttp://service.sap.com/unicode@sap Unicode Events Events 2006 SAP Teched2006 Integration between heterogeneous SAP Unicode and 3rd party systemsRFC Library Guidehttp://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000047816&_OBJECT=011000358700001892452002E

http://service.sap.com/unicode@sap

http://help.sap.com/SAP

http://help.sap.com/erp2005_ehp_03/helpdata/EN/62/3f2cadb35311d5993800508b6b8b1



http://service.sap.com/~form/sapnet?_SHORTKEY=01200252310000047816&_OBJECT=0110003587

© SAP 2008 / Page 59

Appendix: Information Sources on specificUnicode Topics II

Downtime Optimizationhttps://www.sdn.sap.com/irj/sdn/systemcopy System Copy Optimizationhttp://service.sap.com/slo Minimized Downtime Service

MDMP Unicode conversionhttp://service.sap.com/unicode@sap Unicode Conversion Guideshttp://service.sap.com/unicode@sap Unicode Events Events 2006 SAPTeched 2007 Conversion of MDMP Systems to Unicode

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

http://service.sap.com/slo



© SAP 2008 / Page 60

Appendix: Unicode Conversion Topics –Presentation Table of Content

Unicode Introduction

Unicode Conversion Steps on SAP System LevelABAP EnablingInterface adaptationExport / Import OptimizationVocabulary HandlingSequence and Planning of a Unicode Conversion

Options for Upgrade and Unicode ConversionUpgrade and Unicode Conversion in different DowntimesUpgrade and Unicode Conversion separated in the same DowntimeUnicode Conversion before Upgrade in the same DowntimeCombined Upgrade and Unicode ConversionTwin Upgrade and Unicode ConversionOverview: Possible Scenarios for Combination of Upgrade and Unicode Conversion

Unicode Conversion of Complex System LandscapesRules for Unicode Conversion SequenceGeneral Golden RulesExample for a Conversion of a Complex System Landscape

Summary and additional Information

SAP Unicode ConversionTopics

Solution Management Globalization ServicesSAP AGOctober, 2008

© SAP 2008 / Page 62

Copyright 2008 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, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as theirrespective 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 andassociated logos displayed 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. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains 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. 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, orother 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 ofmerchantability, 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, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Servicessowie die dazugehö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ähntenNamen von Produkten 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 diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrü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 Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, 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 überInternetseiten Dritter ab.

Alle Rechte vorbehalten.

Documents

UC Conv Topics