• Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Guide to the Combined Unicode Conversion and Upgrade Wednesday March 03, 1-2pm CST Josh Fisher Basis Consultant
  • 2. Download the presentation recording with audio from the Symmetry Knowledge Center www.sym-corp.com/knowledge-center
  • 3. Symmetry’s 21st Century Approach to Managed Services Quality – proactive support delivered by US-based experts Accessibility – 24x7 direct access to your support team Affordability – highly competitive, fixed price contracts Lifecycle Support for any SAP application on any platform combination SAP NetWeaver Security design Implementation SAP certified Upgrade & / Basis & Support Hosting project support administration administration
  • 4. Introducing Josh Fisher Basis Consultant
  • 5. Overview Unicode Overview – Why, What & How Unicode & ECC 6.0 2.1. Project comparison 2.2. Paths to target 2.3. Complicating factors Case Study Resources Wrap-Up
  • 6. Moving from R/3 Non-Unicode (NUC) To be: up to ERP 6.0 Unicode (UC) SAP ERP 6.0 UC Outage Production Database windows? Testing? migration? 32->64 bit? HW migration? SAPGUI OS upgrade? MDMP or SCP? Rollout? HW upgrade? Database upgrade? SAP Solution Manager? ABAP work? As is: Sandbox hw? Training? Backout SAP R/3 NUC strategies? Production
  • 7. Unicode Overview – Why, What & How Unicode & ECC 6.0 2.1. Project comparison 2.2. Paths to target 2.3. Complicating factors Case Study Resources Wrap-Up
  • 8. Why Convert – SAP Customer letter Apr 2006. – SAP Customer letter Apr 2006. ―It is a strategic target of SAP to move our customer base to Unicode. End of support for non Unicode based systems for future releases is being discussed internally.‖
  • 9. Why Convert – more reasons Inherently a non-Unicode system cannot ―understand‖ all the characters that could be sent from a Unicode system SAP Java systems are only Unicode Mixed landscapes may or may not work even in Single Code Page environment. Note 838402 - Problems within non-Unicode system landscapes Note 975768 - Deprecation of Java features with non-Unicode Backend
  • 10. Why Convert ―Non-Unicode code pages support only a small portion of the world- wide existing character sets. Any character conversion based on these code pages therefore bears the risk of silent data loss.‖ ―Existing non-Unicode systems are still supported, but due to the intrinsic limitations of non-Unicode code pages SAP recommends a conversion to Unicode, especially when upgrading system to Netweaver 7.0 (ERP 2005) and higher releases.‖
  • 11. Why Convert SAP Note 838402 – Problems with Non-Unicode SAP Landscapes Only languages that can be covered by one single non-Unicode code page can be supported within each non-Unicode system. Some characters that are used in your language are not supported by the installed non-Unicode code page. Integration with Unicode based technologies: Most technologies used within an SAP application context are Unicode based When using these technologies together with a non-Unicode SAP system uncontrolled data loss can occur.
  • 12. Release strategy well in progress Source: p 30 Figure 6 FAQ Upgrading to myERP 2005
  • 13. http://service.sap.com/maintenance
  • 14. Terminology CU&UC — Combined Upgrade and Unicode Conversion Common abbreviation used in documentation UTF — Unicode Transformation Format Flavors differ in storage UTF-8, UTF-16, UTF-32 UC / NUC — Unicode / non-Unicode Used in SAP documents/websites/ ―exe directory names‖ NUC system types SCP — Single Code Page MDMP — Multi-Display Multi-Processing (i.e. multiple code pages) Blended CPs — Special Code Pages for certain language combinations
  • 15. The “What” is about Characters American Standard Code for Information Interchange (ASCII) . There are 95 printable ASCII characters, numbered 32 to 126
  • 16. What is a code page? Code Page (from SAP Glossary) Character set that defines the symbols that can be used in programs and displayed by output devices such as printers and terminals. 1 character = 1 byte
  • 17. What is Unicode? International standard Characters from virtually every language and script assigned a unique Unicode Scalar Value Unicode Scalar Value: a number written in hexadecimal notation. Notational convention "U+" is prefixed to the Scalar Value. UTF - Unicode Transformation Format Note: Unicode only specifies text storage not translation. It does not automatically make more languages available.
  • 18. Unicode Storing Characters Byte Order Reversed 8-bit Mostly 16 bit
  • 19. Required code pages depend upon languages used Multiple languages ≠ multiple code pages (e.g. code page 1100) Source: SAP Note 73606 attachment “R3languages.pdf”
  • 20. Do I have to Convert in Order to Upgrade to ECC 6.0? Yes No MDMP or SCP BCP
  • 21. Code Pages in Use? RSCPINST or SE16 TCPDB
  • 22. Blended code pages?
  • 23. Basic Unicode Conversion Uptime Processing SPUMG & UCCHECK Downtime Processing R3Load R3Load SAP Database (Export & (Install & SAP Database With Conversion) Import) With Non-Unicode Unicode Data
  • 24. Unicode Conversion Phases Tcode UCCHECK * Tcode SPUMG * Export/SAPINST Post Process * UCCHECK & SPMUG not available in 46C and below
  • 25. Unicode Overview – Why, What and How Unicode & ECC 6.0 2.1. Project comparison 2.2. Paths to target 2.3. Complicating factors Case Study Resources Wrap-Up
  • 26. Unicode & ECC Project Comparison HW, OS, DB, SAN, Basis Unicode Conversion Dependent mostly technical upon number & ABAP effort of “Z” objects
  • 27. Paths to Unicode ECC 6.0 Separate projects If R3 4.7 or Unicode ECC 5.0 Upgrade Conversion If Single Unicode Upgrade Code Page Conversion Note: CU&UC Downtime is normal SAPup downtime plus DB export/import
  • 28. Project complicating factors Hardware factors Sandbox availability Storage (exports, extra systems) OS Upgrade / patches Migration (new hw and/or new architecture eg x86->x64) Can be Parallel development (existing and upgraded) significant Database factors efforts but do not Upgrade / patches change Conversion (if source not Unicode compatible) business Size process Export/Import time Backup/Restore time Other factors MDMP requires more Unicode preparation steps than SCP Number of ―Z‖ Objects – Unicode syntax corrections / Upgrade driven changes
  • 29. Path to Unicode ECC 6.0 Yes Separate Projects Get these May be done DB > ~500GB done as days/weeks & early as possible before SCP Gui Rollout Hw migration Min SP for Unicode CU&UC No DB upgrade Latest kernel & spam/saint vers.
  • 30. CASE STUDY
  • 31. Source - Target Source R3 46C Windows X86 MSSQL 2000 MDMP ~300GB Target ECC 6.0 Windows x64 MSSQL 2005 Unicode Complicating factors: HW change x86 –> x64 Database upgrade MSSQL 2000 -> 2005 MDMP preprocessing Interim 47/200 upgrade for Unicode prep
  • 32. Timeline Oct Nov Dec Jan  47/200 Interim System  Sol Man 4.0  Sandbox ECC 6.0  Development ECC 6.0  QA ECC 6.0 (system copy of Dev)  Production Rehost & DB upgrade  Production ECC 6.0
  • 33. Go-Live Strategy Weekend 1: HW migration & DB upgrade Re-host 46C MSSQL 2000 onto new (x64) hw Upgrade database to MSSQL 2005 During week: Perform (online) PREPARE and SPUMG for CU&UC Weekend 2: Complete CU&UC SAPup and Export/Import (UC) Transports & Acceptance Testing
  • 34. Resources http://service.sap.com/unicode (Start with the ―News‖ link)
  • 35. Wrap up Unicode Conversion is inevitable and primarily technical CU&UC downtime: ―SAPup‖ plus DB export/import DB Size key driver for UC downtime Number of ―Z‖ objects affect both upgrade and UC DB upgrades and hw changes are primarily technical – avoid go- live Sandbox very necessary for determining ―timing‖ and ―complicating factors‖ Visit http://service.sap.com/unicode
  • 36. Download the presentation recording with audio from the Symmetry Knowledge Center www.sym-corp.com/knowledge-center
  • 37. Heather Mickelson Phone: 414 732 2738 Email: hmickelson@sym-corp.com