Combined Upgrade and Unicode Conversion Session Code 1104

Nils Buerckel, SAP Globalization Services, SAP AG

Agenda

1. Why to upgrade and convert to Unicode 2. Upgrade Procedure 3. Unicode Conversion Steps on SAP System Level
ABAP Enabling Interface adaptation Export / Import Optimization Vocabulary Handling

4. Combination of Upgrade and Unicode Conversions 5. Best Practices 6. Wrap-Up and Appendix

© SAP 2009 / Page 2

SAP ERP 6.0 Is the Go-To Release

Provides a long-term foundation for excellence and innovation

300+ functional enhancements Dramatic user experience improvements

Enterprise services enabled Delivers 28 configurable industry solutions

Continuous innovation
© SAP 2009 / Page 3

Unicode Essentials: What is Unicode? Unicode is a character encoding schema containing (almost) all characters used world wide.unicode. Unicode provides a unique number for every character. no matter what the language. no matter what the platform. no matter what the program.org for complete code charts © SAP 2009 / Page 4 . See www.

SAP Non-Unicode World – „Code Page Islands“ „Code Page Islands“ Local Characters not supported Latin-1 Latin-2 Turkish Baltic Cyrillic Greek Chinese (Trad) Chinese (Simpl) Japanese Korean Thai © SAP 2009 / Page 5 .

Without Language Limits Unicode © SAP 2009 / Page 6 .SAP Unicode World .

Italian Norwegian Portuguese Spanish Swedish Turkish Icel and ic *MDMP: Multiple Display Multiple Processing code page © SAP 2009 / Page 7 . German Finnish French.Single Code Pages in SAP Systems Japanese Hebrew Greek Chinese Korean Taiwanese Russian Ukrainian English Thai Croatian Czech Hungarian Polish Rumanian Slovakian Slovene Every Ellipse represents one code page Single Code Page System means that only languages within ONE ellipse can be used MDMP*: More than one code page / ellipse is used within one system Danish Dutch.

UNICODE: Example Languages supported in Unicode Japanese Hebrew Greek Arabic Azerbaijani Russian Ukrainian Belarusian Bengali Danish Dutch Finnish. Italian Norwegian Portuguese Spanish. French. Swedish Unicode Ellipse Chinese Korean English Farsi Hindi Taiwanese Bashkir Panjabi Sanskrit Thai Icel and ic German Croatian Czech Hungarian Polish Rumanian Slovakian Slovene Urdu Vietnamese Turkish © SAP 2009 / Page 8 .

Unicode Support: Market Situation Unicode is the established international standard to support multiple character sets within one consolidated character set and within one system Unicode is a prerequisite for all new technologies Java is fully Unicode based XML is fully Unicode based The 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 for Standardization (ISO) and is supported on most operating systems and all modern browsers © SAP 2009 / Page 9 .

NET integration (Java speaks Unicode only!) Collaborative business: integration of third-party products that run on different code pages Companies want to make use of “language dialects” (e.Who Needs Unicode? Acting in global business requires support of a global character set and many more language features! Companies running global business processes such as global HR systems or global Master Data Management Companies offering Web services to their customers: global master data containing multiple local language characters Companies using open standards: J2EE and .. Companies want to enter new countries requiring local languages for legal reasons such as FI reporting. Vietnamese language has a complex script and is only supported with Unicode – SAP delivers the Vietnamese Translation as of February 2009 © SAP 2009 / Page 10 .g. Brazilian Portuguese and Portuguese Portuguese) require new Unicode-only language keys. Example: Vietnam.

NET DB and OS Abstraction DB and OS Abstraction WebSphere © SAP 2009 / Page 11 . and business processes no Information Integration Business Intelligence Knowledge Management no The business foundation for SAP and no partners Integrates across technologies and organizational boundaries A safe choice with full .SAP NetWeaver™ With Non-Unicode ABAP Stack Limited SAP NetWeaver™ People Integration Multi-Channel Access Composite Application Framework Portal Collaboration Evolution of SAP technology Unifies and aligns people.NET and J2EE interoperability Lifecycle Management Master Data Management Process Integration Integration Broker Business Process Management Powers business-ready solutions that reduce custom integration Its Enterprise Services Architecture increases business process flexibility … Application Platform J2EE non-Unicode ABAP … . information.

information.NET and J2EE y with interoperability The business foundation for SAP and es y partners … Powers business-ready solutions that reduce custom integration Its Enterprise Services Architecture increases business process flexibility Unifies and aligns people.SAP NetWeaver™ With Non-Unicode ABAP Stack Limited • Java runs on Unicode only • If ABAP stack runs in non-Unicode. and business processes .NET © SAP 2009 / Page 12 DB and OS Abstraction DB and OS Abstraction WebSphere . conversion from/to Unicode and nonUnicode required! Can lead to data loss! • Full language data consistency only with both ABAP and Java stack in Unicode SAP NetWeaver™ People Integration Multi-Channel Access Composite Application Framework Portal Collaboration Life Cycle Management Information Integration Business Intelligence Knowledge Management Evolution of SAP technology Master Data Management Process Integration Integration Broker Business Process Management … Application Platform J2EE Unicode ABAP es y Integrates across technologies and organizational boundaries A safe choice esfull .

Multi-Processing (Mixed Code Page) system .0 6 *MDMP = Multi-Display.Pre-Unicode Solution for Multiple Languages: MDMP* West European View Japanese View Korean View N © SAP 2009 / Page 13 s o pp u ta or of s AP S RP E .

but no longer recommended Support restricted (No new installs) Support very restricted (No new installs) Support very restricted (No new installs) R/3 Enterprise Supported and recommended Supported (for limitations see SAP Note 838402) Supported (for limitations see SAP Note 838402) Conditionally supported (for limitations see SAP Note 838402) Supported.Native Language Support in SAP ERP (SAP Note 79991) Language technology ERP release Unicode Single code page system MDMP Blended code page system* R/3 4.0 Supported and recommended No support (SAP Note 79991) No support (SAP Note 79991) 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 / Page 14 . but no longer recommended ERP 2004 Supported and recommended Support restricted (SAP Note 747036).6C Not possible Supported Supported. (No new installs) ERP 6.

target release Unicode enabled © SAP 2009 / Page 15 * : Web AS = SAP Web Application Server .0 (ERP 2004) (Web AS 6.00) Twin Upgrade and Unicode conversion (TU & UC) Release independent.40) Target release: ECC 6.7 (Web AS 6.40) Combined Upgrade and Unicode conversion (CU & UC) Source releases: R/3 4.20) * ECC 5.Ways to Your Unicode SAP System Supported Unicode conversion paths Unicode conversion without upgrade Releases: R/3 Enterprise 4.6C R/3 Enterprise 4.0 (ERP 6.7 Ext. 110 and 200 (Web AS 6.0 (ERP 2004) (Web AS 6.0) (NW AS 7.20) ECC 5.

Unicode Conversion Steps on SAP System Level ABAP Enabling Interface adaptation Export / Import Optimization Vocabulary Handling 4. Best Practices 6. Why to upgrade and convert to Unicode 2.Agenda 1. Combination of Upgrade and Unicode Conversions 5. Wrap-Up and Appendix © SAP 2009 / Page 16 . Upgrade Procedure 3.

Downtime Downtime-minimized Upgrade Uptime ICNV Prepare Upgrade Downtime-minimized New Release Backup Backup Imp. EhP’s and Add-ons does not impact significantly the downtime! Import of Substitution Set Support Pack’s Add-Ons Prod.Upgrade: Up. post Upgrade Downtime Backup Resourced-minimized Stop of Production (strategy-dep.) © SAP 2009 / Page 17 . Downtime Resourced-minimized Shadow Instance (on target release) Modification Adjustments Inst. Activation Distribution EhP’s Prod.and Downtime: The Timing Diagram Binding SP’s.

1I Main upgrade tools are PREPARE and SAPup Improved usability for including additional packages into upgrade Wizard based.Features of the ABAP Upgrade to ECC 6. keeps your upgrade to latest state Support for Switch framework SAPup migrates former Industry Solutions Add-ons into Switch Framework technology Support for combined upgrade and Unicode conversion © SAP 2009 / Page 18 . all “decisions” on one screen Allows changes to decisions without restart of prepare phase Reduced downtime through parallel import of software packages (shadow import and main import) Improved fixpack (corrections) concept Includes improvements and error corrections to upgrade tool.0 Oldest SAP start release 3.

Best Practices 6. Upgrade Procedure 3.Agenda 1. Combination of Upgrade and Unicode Conversions 5. Wrap-Up and Appendix © SAP 2009 / Page 19 . Unicode Conversion Steps on SAP System Level ABAP Enabling Interface adaptation Export / Import Optimization Vocabulary Handling 4. Why to upgrade and convert to Unicode 2.

D. T. STRING) Non-Unicode kernel Non-Unicode database 1 character = 2 bytes (UTF16). STRING) Unicode kernel Unicode database Unicode SAP R/3 Single ABAP source for Unicode and non-Unicode systems No explicit Unicode data type in ABAP All character like data types are stored as Unicode in a Unicode system and Non-Unicode in a Non-Unicode system This requires a clear distinction between character and byte processing in Unicode: One Character One Byte Additional Syntactical restrictions © SAP 2009 / Page 20 . N. (types C.ABAP Enabling of Customer Developments I ABAP ABAP ABAP source source source NonUnicode SAP R/3 1 character = 1 byte (types C. D. T. N.

6C (CU&UC or TU&UC*) Execute the whole UCCHECK procedure in the SBX Unicode system Upgrade the DEV system to SAP ERP 6.20 UCCHECK can be run before or during Unicode conversion Start release <= 4. 10 objects can be fixed by a developer per day Transaction UCCHECK available as of SAP NetWeaver AS 6.ABAP Enabling of Customer Developments II Unicode flag ( “Unicode checks active”) is used as a Program Attribute to control 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 coding Experiences: Approx.sap.0 (Non-Unicode or Unicode) and execute UCCHECK (Additional Maintenance System necessary) Customer Quote: *CU&UC = Combined Upgrade and Unicode Conversion *TU&UC = Twin Upgrade and Unicode Conversion For more information please see http://service.20 Start release >= SAP NetWeaver AS 6.com/unciode@SAP Monitor and identify obsolete programs upfront © SAP 2009 / Page 21 .

Combination of Upgrade and Unicode Conversions 5. Upgrade Procedure 3. Why to upgrade and convert to Unicode 2. Best Practices 6. Unicode Conversion Steps on SAP System Level ABAP Enabling Interface adaptation Export / Import Optimization Vocabulary Handling 4.Agenda 1. Wrap-Up and Appendix © SAP 2009 / Page 22 .

.6C ISO8859-1 SJIS RFC Client (char) SAP_CODEPAGE = 1100 SAP NetWeaver BI ISO8859-1 3rd Party EBCDIC SAP R/3 Enterprise Internet 1251 IS0-1 IS0-8 ..Interface Adaptation: Unicode and NonUnicode JAVA Application (Portal) Conversions between incompatible code pages possible Only a common subset of language characters exchangeable Special rules have to be obeyed to make communication possible .... SAP R/3 4..charset=Shift_JIS" > .charset=utf-8" > Files IS0-9 SJIS BIG-5 697/ 0500 697/ IS0-3 0277 IS0-2 IS0-7 1252 © SAP 2009 / Page 23 ...charset=iso-8859-1" > .charset=windows-1257" > ...

Determination of specific Non-Unicode character set to use (Default: Logon Language) Code Page 1500 Code Page 1100 Code Page 1401 Code Page 8000 UTF-16 …. Determination of Non-Unicode or Unicode (Default: SM59) Non-Unicode Logon Language Unicode Interface Type Non-Unicode *in case of ABAP Non-Unicode to ABAP Unicode transfer. the Unicode system converts the data 2. UTF-8 © SAP 2009 / Page 24 .Example: Interface Handling in Non-Unicode and Unicode via RFC ABAP Non-Unicode Usually no conversion necessary* ABAP Unicode SM59 Settings 1.

and Download Communication between SAP Unicode Non-SAP Non-Unicode System Logon Language is changeable in programs via SET LOCALE LANGUAGE <lang> Customer Quote: Don’t forget your Interfaces ! © SAP 2009 / Page 25 .and Upload In case of Unicode .Interface Adaptation: Rules and Restrictions Choice for Data Transfer: Non-Unicode or Unicode Changeable in RFC Connections (Transaction SM59) on the Unicode system Can be specified in File Down.Non-Unicode Communication Rule 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 in table) File Up.

Wrap-Up and Appendix © SAP 2009 / Page 26 . Upgrade Procedure 3. Best Practices 6. Combination of Upgrade and Unicode Conversions 5. Why to upgrade and convert to Unicode 2.Agenda 1. Unicode Conversion Steps on SAP System Level ABAP Enabling Interface adaptation Export / Import Optimization Vocabulary Handling 4.

Conversion and Import: Overview System Copy procedure used for Unicode Conversion Import and export during downtime Unicode Conversion during Export Usually downtime optimization necessary Unicode View: SPUMG System Vocabulary: Reprocess Log Control Table Vocabulary non Unicode © SAP 2009 / Page 27 EXPORT + Conversion R3load Data R3load Unicode IMPORT .Database Export.

Unicode Conversion Downtime Dependencies Overall Database size Size of specific Tables Size of largest tables Size of cluster tables Customer Quote: Archive data if possible upfront Available Hardware Number and speed of CPUs I/O Performance of disks Separate server available for PRD Unicode system Additional (temporary) hardware available for export and import Settings Special r3load export / import options (e..g. unsorted export) Profile parameters (see SAP Notes 784118 and 857081) Time and number of tests spent on optimization © SAP 2009 / Page 28 .

Export / Import Optimization .com) Do a test on a Customer Quote: Hardware comparable to your PRD environment © SAP 2009 / Page 29 .Options Use Standard run time Optimization Tools Optimize database settings during Export / Import Optimize R3Load Settings – Unsorted Export – Loadprocedure fast for import Enhance hardware – Use new hardware for Unicode System and execute export and import on different systems with Migration Monitor Table Split – Large tables need to be split and table parts can be processed in parallel Distribution Monitor – Additional Application Servers can be used If the Optimization enhancements outlined above do not result in an acceptable downtime Minimized Downtime Service (MDS) is offered by SAP Consulting (Email address: MDS@sap.

Customers with “larger” systems. lower downtime requirements and/or smaller Hardware capability Smaller Investment in Downtime Opt. Back-up. Tests after the conversion … etc) • Most of the shown examples used two Servers (Export on Server 1 and Import on Server 2 in parallel).g. Prepare Jobs. higher downtime requirements and/or higher Hardware capability Higher Investment in Downtime Opt. © SAP 2009 / Page 30 .g. • Experiences show that the reduction can be significantly high when using the Two Servers Scenario (e. 2800 4800 6800 8800 10800 Note: These numbers do not include upgrade downtime DB size in GB (be fore Conve rsion) • Net Runtimes on PRD systems: Time needed from begin of Export until end of Import (w/o e. Upgrade.Runtimes – Customer Experiences Examples for Technical Unicode Conversion Downtime (Database Size > 1000GB) 60 Technical Downtime in hours 50 40 30 20 10 0 800 Standard Conversion MDS Customers with “smaller” systems. from 50 h 28 h for the runtimes).

older processors up to 30%. Nearly no change due to efficient compression Network 0% * We observed dependencies in the processor type. Modern processors showed 10% increase. So if you update your hardware you'll have to expect less increase than when you continue to use your old hardware Note The table includes the additional resource consumptions as measured in the benchmark tests as well as headroom to accommodate a mixture of different transactions DB vendors must additional CPU/RAM Hardware resource requirements on standalone DB servers © SAP 2009 / Page 31 . application servers are based on UTF-16 10% is the observed maximum for larger systems (DB size > 200 GB). double byte) OLTP Internally.Overview of Likely Unicode Hardware Requirements KPI Range of Additional Resource Consumption Comments CPU RAM Database +10-30%* +40-50% UTF-8: +10% UTF-16: +30-60% Depends on transaction mix (MDMP. 35% is the observed maximum in growth for small systems (DB size < 200 GB).

Upgrade Procedure 3. Wrap-Up and Appendix © SAP 2009 / Page 32 . Why to upgrade and convert to Unicode 2. Unicode Conversion Steps on SAP System Level ABAP Enabling Interface adaptation Export / Import Optimization Vocabulary Handling 4.Agenda 1. Combination of Upgrade and Unicode Conversions 5. Best Practices 6.

Vocabulary Handling: MDMP* Preparation – Transaction SPUMG MDMP system is a “Mixed code page solution” Database contains textual data from several code pages. ALL table rows in the database must be assigned a certain code page before the Unicode conversion of an MDMP system is possible ! Data with a language key can be converted without additional effort Database is scanned in order to find problematic texts without a language key Transaction SPUMG is used to scan the database and insert the problematic words without language information into a system vocabulary System Vocabulary needs to be fully maintained using different methods Find additional fields of the table in order to determine the code page Use Statistical methods System Vocabulary: Maintain manually by native speakers The system vocabulary information is used during the Unicode conversion (Database Export) *MDMP: Multiple Display Multiple Processing code page © SAP 2009 / Page 33 .

20 (4.6C: SPUM4 is available) Full SPUMG scans necessary for MDMP / Ambiguous Blended Codepages before the conversion (export / import) Manual maintenance necessary by native speakers Best Practices Create sandbox as copy of PRD system and run SPUMG/SPUM4 and conversion on this Sandbox Maintain SPUMG (Vocabulary and Reprocessing logs) properly during this conversion and transfer results to other systems in landscape Repair data in SUMG © SAP 2009 / Page 34 .Vocabulary Handling: MDMP Preparation – SPUMG / SUMG SPUMG Requirements Available as of SAP NetWeaver AS 6.

MDMP Post-Processing: Repair Incorrectly Converted Data © SAP 2009 / Page 35 .

Cyrillic. Latin-5 (TR). effort for an MDMP conversion © SAP 2009 / Page 36 . the higher the effort ONE Latin code page combined with ONE Non-Latin Code Page (see below for definition) usually causes low effort for the vocabulary and reprocess log maintenance The combination of more than one Non-Latin code page causes very high effort What is a Latin and Non-Latin code page ? Latin Code Pages Latin-1. HE Customer Quote: Do not underestimate add.MDMP: Code Page Combinations and Vocabulary I The following topics influence the effort for the vocabulary and reprocessing log work The more code pages in use. Baltic Non-Latin Code Pages Asian Code pages. EL. Latin-2.

Combination of Upgrade and Unicode Conversions 5. Wrap-Up and Appendix © SAP 2009 / Page 37 .Agenda 1. Upgrade Procedure 3. Best Practices 6. Why to upgrade and convert to Unicode 2. Unicode Conversion Steps on SAP System Level ABAP Enabling Interface adaptation Export / Import Optimization Vocabulary Handling 4.

Conversion to Unicode SAP ECC 6.0 nonUnicode 2.6C MDMP Preparation 1.6C and MDMP Also possible for start releases > 4.0 Unicode PRODUCTION TIME © SAP 2009 / Page 38 DOWNTIME PRODUCTION TIME . Upgrade SAP ECC 6.6C and/or single code page (SCP) systems Please read SAP Note 928729 for details SAP R/3 4. then Unicode conversion) for most other steps Primary focus: customers on start release = 4.0 Unicode SAP ECC 6.Combined Upgrade and Unicode Conversion (CU & UC) CU&UC (Combined Upgrade and Unicode Conversion) is a procedure to integrate Upgrade and Unicode Conversion in one Weekend MDMP scans can be executed before Upgrade Sequential approach (first Upgrade.

Twin Upgrade and Unicode Conversion (TU & UC)
TU&UC (Twin Upgrade and Unicode Conversion) is an alternative procedure to CU&UC
Additional scan system (copy of PRD - called Twin system) needed for MDMP scans Results 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. Conversion SAP ECC 6.0 to Unicode

SAP R/3 4.5B MDMP PRODUCTION TIME

nonUnicode
Import results

SAP ECC 6.0 Unicode

SAP ECC 6.0 Unicode

DOWNTIME

PRODUCTION TIME

Upgrade System Copy SAP ECC 6.0 SAP R/3 4.5B non-Unicode MDMP
SPUMG
© SAP 2009 / Page 39

TWIN RUN

Overview: Support Matrix for Combination of Upgrade and Unicode Conversion

Conversion Type Source Release

Upgrade and Unicode Conversion separated*

CU&UC

TU&UC

SCP: Single Code Page System

MDMP: Mixed Code Page System

SAP ERP 2004 SCP SAP R/3 Enterprise SAP R/3 4.6C SCP Releases < SAP R/3 4.6C SCP/MDMP MDMP SCP/MDMP MDMP

SCP

SCP/MDMP

MDMP

SCP

Not supported

MDMP

*Might be also combined in one weekend
© SAP 2009 / Page 40

Agenda

1. Why to upgrade and convert to Unicode 2. Upgrade Procedure 3. Unicode Conversion Steps on SAP System Level
ABAP Enabling Interface adaptation Export / Import Optimization Vocabulary Handling

4. Combination of Upgrade and Unicode Conversions 5. Best Practices 6. Wrap-Up and Appendix

© SAP 2009 / Page 41

SPAU (DEV) 3.Downtime Optimization (SBX / QAS) Redo UC conversion n times (SBX) 1. Enabling of Customer DevelopmentsUCCHECK (DEV / SBX) 4. Integration Testing with focus on Adapted customer ABAP programs Interfaces (SBX / QAS) Technical Upgrade and Conversion Post-Conversion Unicode System All Systems = © SAP 2009 / Page 42 DEV = Development System SBX = Sandbox System QAS = Quality Assurance System PRD = Production System .6C Preparation-Tasks Non-Unicode System PREPARE (all systems) MDMP preparation – SPUM4 (all systems) Interface – Evaluation (DEV / QAS / SBX) Downtime (all Systems) Upgrade + SPDD (all Systems) Unload /reload process (all Systems) Test .Example for Sequence: CU&UC with Source Release 4. Check and Repair problematic Data – Transaction SUMG (all systems) 2.

Create sandbox (SBX) as copy of productive system (PRD) SPUM4/language scans/vocabulary 2. Unicode conversion of quality (QAS) system of SBX – PRD dress rehearsal (n times. Unicode conversion of PRD Note: Additional maintenance system(s) might be needed to support PRD system after Upgrade of DEV © SAP 2009 / Page 43 . n >= 2) conversion of development (DEV) system Downtime Optimization / SUMG Handling 3. Upgrade and Unicode conversion of SBX (repeat UC conversion n times.0 (Unicode) ABAP Unicode enabling Combine ABAP Unicode enabling with SPAU (synergy!) 4. depends) 5. Conversion Last dress rehearsal should be “as near as possible” to the PRD conversion 6. Unicode ABAP reconciliation/SPAU in ECC 6.Example: Sequence for CU & UC Conversion 1.

Example for a Conversion Landscape DEV QAS Maintenance Landscape DEV QAS PRD Standard Landscape SBN SID Unicode SBU SANDBOX Landscape Highly recommended SID NonUnicode System Copy / Backup & Restore Transport Unicode Conversion Customer Quote: The more planning and practice the better © SAP 2009 / Page 44 .

Typical 3 System Landscape CU&UC: Planning Assumption: Start Release: 4.6C MDMP Customer DB Size: ~ 1TB Downtime Window: 48 h 2009 Jan Kickoff CU&UC Project Feb Mar Apr May Development Development Freeze highly recommended or additional DEV system and double maintenance mandatory Quality Assurance Production All ABAP Objects are Unicode enabled Sandbox Environment* Dress Rehearsal Unicode GO-Live Customer Quote: Plan sufficient time © SAP 2009 / Page 45 * Ideally this Sandbox Environment consists of two systems – one for Non-Unicode and one for Unicode system with the Hardware comparable to the PRD conversion ABAP Enabling PREPARE + SPUM4 + Upgrade + Export/Import Testing (Upgrade + Unicode) Performance Optimization test (Export / Import) .

CU&UC: How long does it take and how much does it cost ? How long does it take to convert a system landscape ? Shortest Project time: ~ 3 months Very long projects: ~ One year Average Project time: MDMP systems: ~ 29 weeks (Sample: 18 customers) Single Code Page systems: ~ 24 weeks (Sample: 27 customers) Strong Influence: MDMP or single code page Database 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 / Upgrade Staff for Testing Native speakers for vocabulary work (MDMP systems) External consulting Additional Hardware requirement Additional Hardware required on landscape due to release change and upgrade Temporarily required Hardware © SAP 2009 / Page 46 .

0 SAP Single code page 4. …) Large Amount of Customer Objects Difficult Objects (Offset) (Technical) Upgrade Efforts Number of Customer Developments and Modifications © SAP 2009 / Page 47 Low Number High Number .6C SAP MDMP + TABLES Difficult / Long Releases < 4.6C SAP MDMP + ALE (Container) Single Code Page Asian Upgrade and Unicode Efforts Source Release (ERP) Interfaces to SAP systems Interfaces to Non-SAP systems (SAP ECC 6.Which Factors influence the Combined Approach (Upgrade and Unicode Conversion) Easy / Short Medium R/3 Enterprise Or ECC 5.0) SAP Unicode Systems Unicode based Systems Single Code Page Latin Unicode Efforts Used Language Technology System properties: Database Size Downtime Hardware performance Single Code Page Small database size Long Downtime window Good performing Hardware Asian Code Page Multiple Code Pages (MDMP) Large database size Small Downtime window Bad performing Hardware ABAP Enabling (UCCHECK) Small Amount of Customer Objects Easy objects (CS.

Two Examples for Upgrade and Unicode Conversion Combination in one Project 0 Unicode Conversion without Upgrade (MDMP) SPUMG (MDMP) Add Prep UC RADCUCNT Export Import SUMG Add Post UC Unicode Conversion 1 CU&UC with MDMP and start release 4.6C SPUM4 (MDMP) RADCUCNT (Delta) UPGRADE Post UPG Add Prep 1 PREPARE UC SPUMG (Delta) Add Prep UC Upgrade Unicode Conversion Export Import SUMG Add Post UC 2 Combined Sequential Approach with Single code page System (SCP) (NOT CU&UC) Upgrade Export Import Add Post UC PREPARE UPGRADE Post UPG SPUMG (SCP) Add Prep RADCUCNT UC Unicode Conversion © SAP 2009 / Page 48 .

Focus on Unicode Application Tests All business critical scenarios need to be tested Especially all business critical Interfaces Customer specific ABAP objects (UCCHECK objects) Netweaver Tests Export / Import in general Export / Import with focus on runtime Optimization MDMP specific SPUM4 / SPUMG tests in general MDMP specific SPUM4 / SPUMG runtime Optimization SUMG (runtime) General Tests (Cross Application – language specific) – mainly for MDMP SPUM4 / SPUMG: Vocabulary and reprocessing assignment SUMG: Manual repair (assignment) Check / test proper conversion of texts containing special characters Test. Test. Customer Quote: Test. Test ! © SAP 2009 / Page 49 .Areas of Testing .

Test and Execution of Unicode Tasks in a Combined Approach (Upgrade and Unicode) Step System SBX Execute: Medium Test: Medium Execute: Medium Test: Low Execute: High Test: High Abap Enabling Interface Adaptation Export/Import Optimization Vocabulary Handling and DB Scans Execute Scans: High Maintain vocab and reprocessing: high Test: High Execute Scans: Yes Maintain vocab and reprocessing: Low Execute Scans: Yes Maintain vocab and reprocessing: Medium DEV QAS Execute Medium Test Medium Execute: No Test High Execute: Medium Test: Medium Execute: No Test High Execute: Low Test: Low Execute: Medium Test: Medium PRD Execute: No Execute: No Execute: Yes Execute Scans: Yes* Maintain vocab and reprocessing: High needed for ALL Unicode conversions *except for TU&UC only needed in MDMP / Blended CP systems Customer Quote: © SAP 2009 / Page 50 Sandbox is very necessary for determining “timing” and “complicating factors” .

effort for an MDMP conversion . Test ! Plan sufficient time Archive data if possible upfront Don’t forget your interfaces © SAP 2009 / Page 51 Monitor and identify obsolete programs upfront Do not underestimate add.Summary: Recommendations and Quotes from Customers who did a Unicode Conversion I Sandbox is very necessary for determining “timing” and “complicating The more planning and factors” practice the better Do a test on a Hardware comparable to your PRD environment Test. Test. Test.

Practical Advice Have a Step by Step document for the conversion weekend © SAP 2009 / Page 52 .Summary: Recommendations and Quotes from Customers who did a Unicode Conversion II Use partners who did it before Expert consulting with prior experience is essential Mainly a timing issue Build an FAQ project database.

Unicode Conversion Steps on SAP System Level ABAP Enabling Interface adaptation Export / Import Optimization Vocabulary Handling 4.Agenda 1. Wrap-Up and Appendix © SAP 2009 / Page 53 . Upgrade Procedure 3. Best Practices 6. Why to upgrade and convert to Unicode 2. Combination of Upgrade and Unicode Conversions 5.

20 all SAP Products are available in Unicode Up from SAP ERP 6. All new SAP applications released since 2007 are delivered in Unicode only Combined and optimized upgrade and Unicode conversion procedures CU & UC and TU & UC are available Good planning and downtime optimization makes your combined upgrade and Unicode conversion successful 1 2 3 4 5 6 7 © SAP 2009 / Page 54 .0 MDMP (mixed codepage) solution is no more supported.7 Key Points to Take Home Unicode is THE ONLY TRUE technical language solution to meet global customers’ language requirements Unicode is THE ONLY SAP future technical language support strategy Up from SAP WEB AS 6.

com/product.cfm?account=&product=H1984 © SAP 2009 / Page 55 .Book “Unicode in SAP Systems” SAP PRESS 340 pages ISBN 978-1-59229-135-9 http://www.sappress.

sap.sap.com * Only available for SAP Customers © SAP 2009 / Page 56 .com/irj/sdn Quick link I18N (https://www.com/irj/sdn/i18n) Technical Unicode Info (https://www.sap.com/GLOBALIZATION)* Quick link UNICODE (http://service.sap.Information Resources SAP Service Market Place: SAP Globalization home page: SAP Unicode home page: http://service.com Quick link GLOBALIZATION (http://service.sap.sdn.com/UNICODE)* SDN: SAP Internationalization: https://www.sap.sdn.com/irj/sdn/i18n Unicode ) Questions ? Write to: globalization@sap.sdn.

type and combination of used code pages (see next slide) Database Size Netweaver Experts Native Speakers (Application Experts) Effort Dependencies Number and type of ABAP Objects Number and Type of Interfaces Database Size of System Downtime Requirements Hardware ressources Netweaver Experts Needed Skills Application Experts Development Experts Application Experts Development Experts Netweaver Experts Typical Duration Weeks to Months ~10 Abap objects per developer and day Weeks to Months A few complicated interfaces can take long time Test as soon as possible Weeks to Months Several tests might be necessary Weeks to Months Scans can potentially run long times Recommendation Test as soon as possible Table Split Distribution Monitor 2-Server-Method Test n times Test with PRD copy as soon as possible Full maintenance of the vocabulary and reprocessing log Large Tables: Use Table Split needed for ALL Unicode conversions © SAP 2009 / Page 57 only needed in MDMP / Blended CP systems .Appendix: Overview: Unicode Conversion Areas for an SAP System Abap Enabling Interface Adaptation Export/Import Optimization Vocabulary Handling and DB Scans Number.

L2 L1/Cyrillic Low Rather Low Reason for Classification Comments German Words are usable in both code pages Distinguishing between L1 and Cyrillic is easy Relatively small number of words in the vocab High number of words in vocab. . Assignment of one-byte words can be problematic L1.. KO. EL or HE is very complex Latin 1 and Latin 2 languages and Asian languages need to be distinguished High number of words in vocab and high difficulty to assign High number of words in vocab and high difficulty to assign High number of words in vocab. but easy to assign JA. KO Very High © SAP 2009 / Page 58 . L2.Appendix: MDMP: Code Page Combinations and Vocabulary Unicode Conversion Classification (Vocabulary and Reprocess Logs) L1. EL. JA. but easy to assign High number of words in vocab and medium difficulty to assign L1. ZH. JA Rather Low Distinguishing between L1 and Asian languages is easy High number of words in vocab. L2. German Words). and very high difficulty to assign Cyrillic.g. High to Very High Distinguishing between different Asian languages is very complex Distinguishing between Cyrillic. Cyrillic Medium to High Adding Cyrillic to L1/L2 causes additional vocabulary entries (e. HE High L1..

com/education/ Related Workshops/Lectures at ASUG 2009 1906 Upgrading to SAP ERP Central Component (SAP ECC) 6.com Business Process Expert (BPX) Community: www.com Related SAP Education and Certification Opportunities http://www.Further Information SAP Public Web: SAP Developer Network (SDN): www.sap.0 and Converting to Unicode in a Complex Environment © SAP 2009 / Page 59 .sap.bpx.sap.sdn.

com www. Leon-Rot Germany T +49/6227/7-46410 F +49/6227/7-828792 Nils.buerckel@sap.com © SAP 2009 / Page 60 .sap.Thank you! Nils Buerckel SAP AG Raiffeisenring 44 D-68789 St.

PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. 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. xApp. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. ByDesign. and/or development. SAP übernimmt keine Haftung für Fehler oder Auslassungen in dieser Publikation. © SAP 2009 / Page 61 . Links und sonstigen in dieser Publikation enthaltenen Elementen. special. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind. SAP NetWeaver. ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. or consequential damages that may result from the use of these materials. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. or other items contained within this material. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Data contained in this document serves informational purposes only. zu welchem Zweck und in welcher Form auch immer. copied. die aus der Nutzung dieser Materialien entstehen können. Dies gilt u. Dies gilt u. Die in dieser Publikation enthaltene Information ist Eigentum der SAP. This document contains only intended strategies. The information in this document is proprietary to SAP. Entwicklungen und Funktionen des SAP®-Produkts. xApps. links. die nicht Ihrem gültigen Lizenzvertrag oder anderen Vereinbarungen mit SAP unterliegt. SAP. zu welchem Zweck und in welcher Form auch immer. graphics. Bei dieser Publikation handelt es sich um eine vorläufige Version. or transmitted in any form or for any purpose without the express prior written permission of SAP AG. die Eigentum anderer Softwarehersteller sind. a. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind. including but not limited to the implied warranties of merchantability. SAP Business ByDesign. PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. R/3. Alle Rechte vorbehalten. The statutory liability for personal injury and defective products is not affected. SAP NetWeaver. This limitation shall not apply in cases of intent or gross negligence. ByDesign. Diese Publikation wird ohne jegliche Gewähr. No part of this document may be reproduced. Grafiken. either express or implied. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. The information contained herein may be changed without prior notice. fitness for a particular purpose. Die gesetzliche Haftung bei Personenschäden oder Produkthaftung bleibt unberührt. weder ausdrücklich noch stillschweigend. product strategy. Produkte können länderspezifische Unterschiede aufweisen.Copyright 2009 SAP AG All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. SAP. Alle anderen in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. indirect. bereitgestellt. text. SAP does not warrant the accuracy or completeness of the information. xApp. Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen. nur mit ausdrücklicher schriftlicher Genehmigung durch SAP AG gestattet. und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab. xApps. SAP shall have no liability for damages of any kind including without limitation direct. SAP Business ByDesign. or non-infringement. Texte. All other product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Duet. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. National product specifications may vary. Diese Publikation enthält nur vorgesehene Strategien. auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen.. SAP assumes no responsibility for errors or omissions in this document.oder Produktstrategie und/oder bestimmten Entwicklungen. Die Informationen. Please note that this document is subject to change and may be changed by SAP at any time without notice. Duet. Des Weiteren übernimmt SAP keine Garantie für die Exaktheit oder Vollständigkeit der Informationen. SAP haftet nicht für entstandene Schäden. a. besondere und mittelbare Schäden oder Folgeschäden. SAP entsteht aus dieser Publikation keine Verpflichtung zu einer bestimmten Geschäfts. Diese Publikation kann von SAP jederzeit ohne vorherige Ankündigung geändert werden. developments. und uneingeschränkt für konkrete. aber nicht ausschließlich. This document is provided without a warranty of any kind. R/3. unterliegen nicht dem Einfluss von SAP.

Sign up to vote on this title
UsefulNot useful