Uni Code

SAP TechEd ‘03 Las Vegas
Unicode
July 7th 2005
Dr. Christian Hansen

Netweaver DT Internationalization,
SAP AG
Agenda
1.What is Unicode?
2.Who needs Unicode?
3.How to go there?
 SAP AG 2005, Dr. Christian Hansen
© 2003 SAP Labs, LLC Session ID, Speaker 1

Agenda
1.What is Unicode?
3.How to go there?
About Code Pages: Conventional Code Pages
Disadvantages of old standard code pages

Each covers only a subset of all characters used
Incompatibilities between different codepages
Only restricted data exchange possible
Too many of them
KYOCERA
Canon
APPLE
HP
IBM
IS0-5IS0-9
IS0-9 Mircosoft
EBCDIC 1250
697/ 1251
IS0-3
697/ 0277 IS0-7 IS0-2
IS0-3 12
0500 IS0-2
IS0-7 12571256 1252
ASCII1252 12
1250
1251
IS0-3
IS0-2
IS0-9
BIG-5
BIG-5 1252 1254
IS0-5
IS0-5 IS0-9
IS0-8 SJIS
IS0-8 SJIS
IS0-4
IS0-3
IS0-4
IS0-3
IS0-2
IS0-7
IS0-7 IS0-6IS0-2
IS0-1
IS0-1IS0-6 SAP:
Languages: 41
Characters: 22,378
 SAP AG 2005, Dr. Christian Hansen Code Pages: 390

Solution: Unicode, one Code Page for all Scripts
Japanese Chinese
Hebrew Korean
Greek
And more
Taiwanese languages
can be
Russian English supported
Ukrainian easily
without the
Danish Thai need for
Dutch,
German Croatian new code
ndic
Finnish
Czech pages or
French, Italian
other new
Icela
Norwegian Hungarian
Polish methods
Portuguese
Spanish Rumanian (e.g. Vietnamese!)
Swedish Slovakian
Turkish Slovene
Solution: Unicode characters

ASCII
General Scripts
Symbols
CJK Ideographs
65,000 characters
Hangul
Compatibility
Additional
Surrogate Area
1,000,000 characters

Representation of Unicode Characters
UTF-16 – Unicode Transformation Format, 16 bit encoding

Fixed length, 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)
Platform-dependent byte order (big/little endian)
2 byte alignment restriction
UTF-8 – Unicode Transformation Format, 8 bit encoding

Variable length, 1 character = 1...4 bytes
Platform independent
no alignment restriction
7 bit US ASCII compatible
Character Unicode UTF-16 UTF-16 UTF-8

scalar value big endian little endian
a U+0061 00 61 61 00 61
ä U+00E4 00 E4 E4 00 C3 A4
α U+03B1 03 B1 B1 03 CE B1
U+3479 34 79 79 34 E3 91 B9
Internationalized Software with Unicode
The Unicode Standard was adopted by IBM and several

other companies including Apple, HP, JustSystem,
Microsoft®, Oracle, Sun™, Sybase, and Unisys.
Unicode is required by modern standards such as XML,

Java™, ECMAScript (JavaScript™), LDAP, CORBA 3.0,
and WML.
Unicode is also the official way to implement ISO/IEC 10646

and is supported in many operating systems and all
modern browsers.
Check out http://www.unicode.org/ !

Agenda
1.What is Unicode?
3.How to go there?
Scenario: System integration and non-Unicode
Jörg Müller
조희정
Web Dynpro
ABAP J2EE
KSC5601: Unicode:
조희정 조희정
J#rg M#ller Jörg Müller
조희정 조희정
J#rg M#ller Jörg Müller
Unicode
Non-Unicode

Scenario: System integration and Unicode
Jörg Müller
조희정
Web Dynpro
ABAP J2EE
Unicode: Unicode:
조희정 조희정
Jörg Müller Jörg Müller
조희정 조희정
Jörg Müller Jörg Müller
Unicode
Non-Unicode
SAP NetWeaver™ the integration platform?
Evolution of mySAP
SAP NetWeaver™
NetWeaver™ Technology
People Integration
Unifies and aligns people,
Multi-Channel Access
information and business
Portal Collaboration processes
Composite Application Framework
Integrates across
Information Integration technologies and
Life Cycle Management
Business Knowledge organizational boundaries

Intelligence Management
A safe choice with full .NET
Master Data Management and J2EE interoperability
Process Integration The business foundation for

Integration Business Process SAP and partners
Broker Management
Powers business-ready
solutions that reduce
… Application Platform … custom integration
J2EE ABAP
Its Enterprise Services
DBDBand
andOS
OS Abstraction
Abstraction Architecture increases
.NET WebSphere business process flexibility

SAP NetWeaver™ with non-Unicode ABAP stack
Evolution of mySAP
SAP NetWeaver™
People Integration
Integrates across


Broker Management
J2EE non-Unicode ABAP
DBDBand
andOS
OS Abstraction
Evolution of mySAP
SAP NetWeaver™
People Integration
no
Integrates across


Broker Management
DBDBand
andOS
OS Abstraction

Evolution of mySAP
SAP NetWeaver™
People Integration
no
Integrates across
no


Broker Management
DBDBand
andOS
OS Abstraction
Evolution of mySAP
SAP NetWeaver™
People Integration
no
Integrates across
no

no

Broker Management
DBDBand
andOS
OS Abstraction

Only solution for full integration: Unicode
Evolution of mySAP
SAP NetWeaver™
People Integration
s
ye
Integrates across
s
ye

Master Data Management
yes
and J2EE interoperability

Broker Management
J2EE Unicode ABAP
DBDBand
andOS
OS Abstraction
Agenda

Everybody making full use of SAP Netweaver

Old solution for multiple languages: MDMP*
West European View Japanese View Korean View
* Check your system type with report RSCPINST current configuration

Old solution for multiple languages: MDMP
West European View Japanese View Korean View
‘0 4
r
a ve
We
e t
h N79991 )
w38402 t
i and
rt
o tes 8
p p ee no
s u (s
o f
d
En
(As of release NetWeaver 04s and moving forward, MDMP will no longer be supported)

Only solution for multiple languages: Unicode
Unicode
Agenda

All Korean customers using more languages than
only English and Korean

Oracle Database setting KO16KSC5601
Default database character set for SAP systems running on Oracle is

WE8DEC.
Note 695899 described a way to change this to the Korean character set
KO16KSC5601.
Several Korean customers used this to make their database transparent

for access by non-SAP products (e.g. DB-Link).
Due to an incompatible change in the Oracle database this will not be

supported in the future (Oracle 10, ERP2005). See SAP note 858869
(still in progress).
The only way to make the database transparent is

a Unicode setup.
Agenda

All Korean customers using more languages than
only English and Korean
All Korean customers that have been using
KO16KSC5601 as Oracle character set
…

Agenda
1.What is Unicode?
3.How to go there?
Unicode Statistics: Current Figures
Unicode shares since 6.10 (%)
8.0
7.5
7.0
6.5
6.0
Shares
5.5
(%)
5.0
4.5
4.0
3.5
3.0
2.5
20 -09 1
20 -10 8
20 -11 6
20 -12 3
20 -12 1
20 -01 9
20 -02 6
20 -03 3
20 -04 3
20 -05 0
20 -06 8
-0 5
13
04 -1
04 -0
04 -0
04 -0
04 -0
05 -2
05 -2
05 -2
05 -2
05 -2
05 -1
05 -1
7-
20 -08
04
20
World wide more than 1700 Unicode systems are already running

How to go there: Unicode availability

Unicode enabled mySAP Components
SAP Web Application Server: WAS 6.20
mySAP Customer Relationship Management (CRM): mySAP CRM 4.0
mySAP Supply Chain Management (SCM): mySAP SCM 4.X
mySAP Supplier Relationship Management (SRM): mySAP SRM 4.0
mySAP Business Intelligence (BW): mySAP BW 3.5
mySAP Product Lifecycle Management (PLM): Ramp up
mySAP Strategic Enterprise Management (SEM): SEM 4.0
SAP R/3 Enterprise: Ext. Set 2.00
SAP Note
79991
How to go there: platform support
SAP supports Unicode systems on the following

platforms:
Platform
W2K Linux3 Solaris1 HP1 Tru641 AIX1 AS/400 OS/390
Database system
SQL ✓ - - - - - - -
Server
Oracle ✓ ✓ ✓ ✓ ✓ ✓ - -
DB/2 ✓ ✓ ✓ ✓ - ✓ ✓ -²
SAP DB ✓ ✓ ✓ ✓ ✓ ✓ - -
164 bit versions only

2OS/390 support is planned for Q3/2004 with DB/2 V8.1.
3Tentatively, 64 bit version will be available in Q2/2004
There will be no support for Informix.
SAP Note
379940

How to go there: Unicode System installation

Unicode is the default for new installations!
How to go there: Unicode System conversion
Unicode System conversions:

Converting existing systems to Unicode needs several steps:
Upgrade to a Unicode compliant version of the application (see note 79991)
Adapt ABAP, C/C++ programs
Convert the database (System Copy)
Install Unicode executables
Check interfaces (3rd party software meight not be ready for Unicode)
Conversion projects need thorough planing and

execution!

What to consider I: Hardware Requirements
based on parallel benchmarking of Unicode / non-Unicode test systems
CPU RAM
+30% +50%
depending on Application Servers
existing scenario are based on UTF-16
(MDMP, double byte) internally
Database size Network Load

UTF-8* :up to +35%
UTF-8
UTF-8** :up to +10%
almost no change
UTF-16 :up to +60..70%
due to efficient
compression
* +35% is the observed maximum in growth

* *first customer conversions indicate: DB
for small systems (db size < 200GB)
size increase due to Unicode conversion is
**+10% is the observed maximum for
outweighed by size decrease due to DB
bigger systems (db size > 200GB)
reorganization – so actually DB shrinks!
What to consider II: Outside communication
Outside communication:
Sapnet quicklink Unicode@sap:
Unicode@sap --> Unicode library --> ABAP and Unicode -->
TechEd 2004: CI253 External Unicode Interfaces

Communication: The Ideal Picture
The ideal Picture: only

Unicode components
JAVA
Application RFC Client
Conversions are done (Portal) R/3 Enterprise (SAP_UC)
algorythmically (1:1
relation)
No data
misinterpretation
mySAP BW
No data loss
3rd Party
All business relevant
characters available at
the same time
... R/3 Enterprise
Internet Files
Communication: Reality
The reality: Unicode and non-Unicode components

JAVA
Application RFC Client
Conversions between (Portal) R/3 4.6C (char)
incompatible code pages ISO8859-1
SJIS
SAP_CODEPAGE
= 1100
everywhere
Only common subset
exchangeable
mySAP BW
Special rules have to be ISO8859-1
obeyed to make 3rd Party
EBCDIC
communication possible
...
R/3 Enterprise
Internet Files
IS0-1 IS0-8
1251
...charset=iso-8859-1" >
IS0-9 SJIS
...charset=windows-1257" > BIG-5697/
...charset=Shift_JIS" > 697/
0500
IS0-3
...charset=utf-8" > 0277
IS0-2
IS0-7
1252

What to consider III: ABAP Programming
ABAP Programming:
Unicode@sap --> Unicode library --> ABAP and Unicode -->
TechEd 2004: CI252 Making ABAP Programs Unicode enabled
Transparent Unicode Enabling of R/3
Character Expansion Model

Separate Unicode and non-Unicode versions of R/3
1 character = 1 byte
ABAP
ABAP Non- (types C, N, D, T, STRING)
ABAP
source
source Unicode Non-Unicode kernel
source
R/3 Non-Unicode database
1 character = 2 bytes (UTF16),

(types C, N, D, T, STRING)
Unicode
Unicode kernel
R/3 Unicode database
No explicit Unicode data type in ABAP

Single ABAP source for Unicode and non-Unicode systems

Transparent Unicode Enabling of R/3
Implications:
Major part of ABAP coding is ready for Unicode without any
changes
Challenge: clear distinction between character and byte processing:
1 Character ≠ 1 Byte
Minor part of ABAP coding has to be adapted to comply with

Unicode restrictions
Find the relevant places with transaction UCCHECK
(Call the transaction today if you are already on SAP_BASIS ≥ 6.10)
Unicode Restrictions – Example
Access To Structures With Offset/Length

Structure must begin with characters
Offset/length counted in characters
Access only allowed within the character type prefix of a structure
N(6) C(4) X(3) C(5)
+off(len)
… = stru+13(5). "Unicode error!

ABAP list layout in Unicode systems
ABAP lists: Difference between memory and display length
Character units Display columns

’ 한’ in the memory
Non-Unicode
2 2
Unicode
1 2
1 Character ≠ 1 Display Column
Example: ABAP list layout in Unicode systems

non-Unicode System Unicode System

What to consider IV: Database conversion
Database Conversion:
Unicode@sap --> Unicode library --> Unicode Conversion Library
--> Basic Information
--> CI206 Conversion of SAP Systems to Unicode
Conversion Preparation: Concept
Before the database conversion to Unicode is

executed, all text data must be assigned a correct
code page.
Single Code Page Systems/

Unambiguous Blended Code Page Systems
y
(ca. 90% of all customer installations) eas
MDMP Systems/
Ambiguous Blended Code Page Systems
(ca. 10% of all customer installations)
x
m ple
co
Why?

Documentation
The following documents are required for the conversion Single

Code Page
of non-Unicode SAP systems to Unicode: and MDMP!
Unicode Conversion System Copy Guide; SAP Note 548016; valid for
Guide; available for available for Web AS Web AS 6.20/6.30/6.40.
Web AS 6.20/6.30/6.40. 6.20/6.30/6.40.
References and Contacts

www.service.sap.com/unicode@sap
Unicode Conversion Library

Summary
1.What is Unicode?
The state of the art technology for internationalized
text processing

All Korean customers using more languages than only
English and Korean
All Korean customers that have been using KO16KSC5601
as Oracle character set
3.How to go there?
New installation
System conversion
Further information
Find more information about Unicode at:

service.sap.com/Unicode@sap
service.sap.com/Unicode
Unicode Conversion
Unicode@sap --> Unicode library --> Unicode Conversion Library --> Basic Information --> CI206 Conversion of SAP Systems to Unicode
Unicode@sap --> Unicode library --> Unicode Conversion Library --> Unicode Conversion Kit 620 --> Unicode Conversion Guide Web AS 6.20/6.30 SP 50
ABAP Unicode programming

Unicode@sap --> Unicode library --> ABAP and Unicode --> TechEd 2004: CI252 Making ABAP Programs Unicode enabled
Unicode@sap --> Unicode library --> ABAP and Unicode --> TechEd 2004: CI253 External Unicode Interfaces
Details for further reading

Unicode@sap --> Unicode library --> ABAP and Unicode --> ABAP Programs in Unicode Systems: Requirements
Unicode@sap --> Unicode library --> ABAP and Unicode --> ABAP List Layout in Unicode Systems: Development Guide
Also recommend: SAP Unicode learning maps available at quicklink rkt-unicode.

Uni Code

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Uni Code

Diunggah oleh

Hak Cipta:

Format Tersedia

SAP TechEd ‘03 Las Vegas

Dr. Christian Hansen

2.Who needs Unicode?

 SAP AG 2005, Dr. Christian Hansen

© 2003 SAP Labs, LLC Session ID, Speaker 1

2.Who needs Unicode?

 SAP AG 2005, Dr. Christian Hansen

About Code Pages: Conventional Code Pages

Disadvantages of old standard code pages

 SAP AG 2005, Dr. Christian Hansen Code Pages: 390

© 2003 SAP Labs, LLC Session ID, Speaker 2

Solution: Unicode, one Code Page for all Scripts

 SAP AG 2005, Dr. Christian Hansen

Solution: Unicode characters

 SAP AG 2005, Dr. Christian Hansen

© 2003 SAP Labs, LLC Session ID, Speaker 3

Representation of Unicode Characters

UTF-16 – Unicode Transformation Format, 16 bit encoding

UTF-8 – Unicode Transformation Format, 8 bit encoding

Character Unicode UTF-16 UTF-16 UTF-8

 SAP AG 2005, Dr. Christian Hansen

Internationalized Software with Unicode

The Unicode Standard was adopted by IBM and several

Unicode is required by modern standards such as XML,

Unicode is also the official way to implement ISO/IEC 10646

Check out http://www.unicode.org/ !

 SAP AG 2005, Dr. Christian Hansen

© 2003 SAP Labs, LLC Session ID, Speaker 4

2.Who needs Unicode?

 SAP AG 2005, Dr. Christian Hansen

Scenario: System integration and non-Unicode

 SAP AG 2005, Dr. Christian Hansen

© 2003 SAP Labs, LLC Session ID, Speaker 5

Scenario: System integration and Unicode

 SAP AG 2005, Dr. Christian Hansen

SAP NetWeaver™ the integration platform?

Business Knowledge organizational boundaries

Process Integration The business foundation for

 SAP AG 2005, Dr. Christian Hansen

© 2003 SAP Labs, LLC Session ID, Speaker 6

SAP NetWeaver™ with non-Unicode ABAP stack

Life Cycle Management

Process Integration The business foundation for

 SAP AG 2005, Dr. Christian Hansen

SAP NetWeaver™ with non-Unicode ABAP stack

Business Knowledge organizational boundaries

Process Integration The business foundation for

 SAP AG 2005, Dr. Christian Hansen

© 2003 SAP Labs, LLC Session ID, Speaker 7

SAP NetWeaver™ with non-Unicode ABAP stack

Life Cycle Management

Process Integration The business foundation for

 SAP AG 2005, Dr. Christian Hansen

SAP NetWeaver™ with non-Unicode ABAP stack

Business Knowledge organizational boundaries

Process Integration The business foundation for

 SAP AG 2005, Dr. Christian Hansen

© 2003 SAP Labs, LLC Session ID, Speaker 8

Only solution for full integration: Unicode

Life Cycle Management

Process Integration The business foundation for

 SAP AG 2005, Dr. Christian Hansen

2.Who needs Unicode?