Top Banner
SPC203 Integration Between Heterogeneous SAP Unicode and Third Party Systems
56

Integration Between Heterogeneous SAP Unicode and Third ...

Nov 28, 2021

Download

Documents

dariahiddleston
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Integration Between Heterogeneous SAP Unicode and Third ...

SPC203

Integration BetweenHeterogeneousSAP Unicode andThird Party Systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 2

Dr Alexander DavidenkoffGlobalization Services SAP AG

Contributing Speakers

SAP AG 2006 SAP TechEd rsquo06 SPC203 3

Learning Objectives

As a result of this workshop you will be able toUnderstand the challenge of communication between SAPUnicode and external third party systemsUnderstand the architecture of Unicode and non-Unicode inSAP systemsGet the basics of communication between SAP and externalUnicode and non-Unicode systemsGet a methodology for interface solutionsSee some integration examples

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 5

Who Needs Unicode

Companies running global business processes like Global HR Systemsor Global Master Data Management

Companies offering Web Services to their customers Global Master Datacontaining multiple local language characters

Companies using Open Standards J2EE and NET integration (JAVAspeaks Unicode only )

Collaborative Business Integration of Third Party Products that run ondifferent code pages

Acting in global business requiressupport of a Global Character Set

SAP AG 2006 SAP TechEd rsquo06 SPC203 6

English

German

Turkish

DanishDutch

FinnishFrench Italian

NorwegianPortugueseSpanish

Swedish

CroatianCzechHungarianPolish

RumanianSlovakian

Slovene

RussianUkrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

Taiwanese

Icel

andi

c

And morelanguagescan besupportedeasilywithout theneed fornew code

pages orother new

methods

Solution Unicode One Code Page For All Scripts

SAP AG 2006 SAP TechEd rsquo06 SPC203 7

ASCIIGeneral Scripts

Symbols

CJK Ideographs

Hangul

Compatibility

Surrogate Area

65000 characters

Additional1000000 characters

Solution Unicode Characters

SAP AG 2006 SAP TechEd rsquo06 SPC203 8

SAP NetWeavertrade The Integration Platform

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 9

SAP NetWeavertrade With Non-Unicode ABAP Stack Limited

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and businessprocesses

Integrates across technologiesand organizational boundariesA safe choice with full NET andJ2EE interoperability

The business foundation for SAPand partners

Powers business-readysolutions that reduce customintegrationIts Enterprise ServicesArchitecture increases businessprocess flexibility

DB and OS AbstractionNET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeavertradetrade

DB and OS Abstraction

Master Data Management

helliphellip

no

no

no

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 2: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 2

Dr Alexander DavidenkoffGlobalization Services SAP AG

Contributing Speakers

SAP AG 2006 SAP TechEd rsquo06 SPC203 3

Learning Objectives

As a result of this workshop you will be able toUnderstand the challenge of communication between SAPUnicode and external third party systemsUnderstand the architecture of Unicode and non-Unicode inSAP systemsGet the basics of communication between SAP and externalUnicode and non-Unicode systemsGet a methodology for interface solutionsSee some integration examples

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 5

Who Needs Unicode

Companies running global business processes like Global HR Systemsor Global Master Data Management

Companies offering Web Services to their customers Global Master Datacontaining multiple local language characters

Companies using Open Standards J2EE and NET integration (JAVAspeaks Unicode only )

Collaborative Business Integration of Third Party Products that run ondifferent code pages

Acting in global business requiressupport of a Global Character Set

SAP AG 2006 SAP TechEd rsquo06 SPC203 6

English

German

Turkish

DanishDutch

FinnishFrench Italian

NorwegianPortugueseSpanish

Swedish

CroatianCzechHungarianPolish

RumanianSlovakian

Slovene

RussianUkrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

Taiwanese

Icel

andi

c

And morelanguagescan besupportedeasilywithout theneed fornew code

pages orother new

methods

Solution Unicode One Code Page For All Scripts

SAP AG 2006 SAP TechEd rsquo06 SPC203 7

ASCIIGeneral Scripts

Symbols

CJK Ideographs

Hangul

Compatibility

Surrogate Area

65000 characters

Additional1000000 characters

Solution Unicode Characters

SAP AG 2006 SAP TechEd rsquo06 SPC203 8

SAP NetWeavertrade The Integration Platform

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 9

SAP NetWeavertrade With Non-Unicode ABAP Stack Limited

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and businessprocesses

Integrates across technologiesand organizational boundariesA safe choice with full NET andJ2EE interoperability

The business foundation for SAPand partners

Powers business-readysolutions that reduce customintegrationIts Enterprise ServicesArchitecture increases businessprocess flexibility

DB and OS AbstractionNET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeavertradetrade

DB and OS Abstraction

Master Data Management

helliphellip

no

no

no

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 3: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 3

Learning Objectives

As a result of this workshop you will be able toUnderstand the challenge of communication between SAPUnicode and external third party systemsUnderstand the architecture of Unicode and non-Unicode inSAP systemsGet the basics of communication between SAP and externalUnicode and non-Unicode systemsGet a methodology for interface solutionsSee some integration examples

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 5

Who Needs Unicode

Companies running global business processes like Global HR Systemsor Global Master Data Management

Companies offering Web Services to their customers Global Master Datacontaining multiple local language characters

Companies using Open Standards J2EE and NET integration (JAVAspeaks Unicode only )

Collaborative Business Integration of Third Party Products that run ondifferent code pages

Acting in global business requiressupport of a Global Character Set

SAP AG 2006 SAP TechEd rsquo06 SPC203 6

English

German

Turkish

DanishDutch

FinnishFrench Italian

NorwegianPortugueseSpanish

Swedish

CroatianCzechHungarianPolish

RumanianSlovakian

Slovene

RussianUkrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

Taiwanese

Icel

andi

c

And morelanguagescan besupportedeasilywithout theneed fornew code

pages orother new

methods

Solution Unicode One Code Page For All Scripts

SAP AG 2006 SAP TechEd rsquo06 SPC203 7

ASCIIGeneral Scripts

Symbols

CJK Ideographs

Hangul

Compatibility

Surrogate Area

65000 characters

Additional1000000 characters

Solution Unicode Characters

SAP AG 2006 SAP TechEd rsquo06 SPC203 8

SAP NetWeavertrade The Integration Platform

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 9

SAP NetWeavertrade With Non-Unicode ABAP Stack Limited

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and businessprocesses

Integrates across technologiesand organizational boundariesA safe choice with full NET andJ2EE interoperability

The business foundation for SAPand partners

Powers business-readysolutions that reduce customintegrationIts Enterprise ServicesArchitecture increases businessprocess flexibility

DB and OS AbstractionNET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeavertradetrade

DB and OS Abstraction

Master Data Management

helliphellip

no

no

no

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 4: Integration Between Heterogeneous SAP Unicode and Third ...

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 5

Who Needs Unicode

Companies running global business processes like Global HR Systemsor Global Master Data Management

Companies offering Web Services to their customers Global Master Datacontaining multiple local language characters

Companies using Open Standards J2EE and NET integration (JAVAspeaks Unicode only )

Collaborative Business Integration of Third Party Products that run ondifferent code pages

Acting in global business requiressupport of a Global Character Set

SAP AG 2006 SAP TechEd rsquo06 SPC203 6

English

German

Turkish

DanishDutch

FinnishFrench Italian

NorwegianPortugueseSpanish

Swedish

CroatianCzechHungarianPolish

RumanianSlovakian

Slovene

RussianUkrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

Taiwanese

Icel

andi

c

And morelanguagescan besupportedeasilywithout theneed fornew code

pages orother new

methods

Solution Unicode One Code Page For All Scripts

SAP AG 2006 SAP TechEd rsquo06 SPC203 7

ASCIIGeneral Scripts

Symbols

CJK Ideographs

Hangul

Compatibility

Surrogate Area

65000 characters

Additional1000000 characters

Solution Unicode Characters

SAP AG 2006 SAP TechEd rsquo06 SPC203 8

SAP NetWeavertrade The Integration Platform

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 9

SAP NetWeavertrade With Non-Unicode ABAP Stack Limited

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and businessprocesses

Integrates across technologiesand organizational boundariesA safe choice with full NET andJ2EE interoperability

The business foundation for SAPand partners

Powers business-readysolutions that reduce customintegrationIts Enterprise ServicesArchitecture increases businessprocess flexibility

DB and OS AbstractionNET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeavertradetrade

DB and OS Abstraction

Master Data Management

helliphellip

no

no

no

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 5: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 5

Who Needs Unicode

Companies running global business processes like Global HR Systemsor Global Master Data Management

Companies offering Web Services to their customers Global Master Datacontaining multiple local language characters

Companies using Open Standards J2EE and NET integration (JAVAspeaks Unicode only )

Collaborative Business Integration of Third Party Products that run ondifferent code pages

Acting in global business requiressupport of a Global Character Set

SAP AG 2006 SAP TechEd rsquo06 SPC203 6

English

German

Turkish

DanishDutch

FinnishFrench Italian

NorwegianPortugueseSpanish

Swedish

CroatianCzechHungarianPolish

RumanianSlovakian

Slovene

RussianUkrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

Taiwanese

Icel

andi

c

And morelanguagescan besupportedeasilywithout theneed fornew code

pages orother new

methods

Solution Unicode One Code Page For All Scripts

SAP AG 2006 SAP TechEd rsquo06 SPC203 7

ASCIIGeneral Scripts

Symbols

CJK Ideographs

Hangul

Compatibility

Surrogate Area

65000 characters

Additional1000000 characters

Solution Unicode Characters

SAP AG 2006 SAP TechEd rsquo06 SPC203 8

SAP NetWeavertrade The Integration Platform

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 9

SAP NetWeavertrade With Non-Unicode ABAP Stack Limited

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and businessprocesses

Integrates across technologiesand organizational boundariesA safe choice with full NET andJ2EE interoperability

The business foundation for SAPand partners

Powers business-readysolutions that reduce customintegrationIts Enterprise ServicesArchitecture increases businessprocess flexibility

DB and OS AbstractionNET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeavertradetrade

DB and OS Abstraction

Master Data Management

helliphellip

no

no

no

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 6: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 6

English

German

Turkish

DanishDutch

FinnishFrench Italian

NorwegianPortugueseSpanish

Swedish

CroatianCzechHungarianPolish

RumanianSlovakian

Slovene

RussianUkrainian

Greek

Hebrew

Thai

Korean

Japanese Chinese

Taiwanese

Icel

andi

c

And morelanguagescan besupportedeasilywithout theneed fornew code

pages orother new

methods

Solution Unicode One Code Page For All Scripts

SAP AG 2006 SAP TechEd rsquo06 SPC203 7

ASCIIGeneral Scripts

Symbols

CJK Ideographs

Hangul

Compatibility

Surrogate Area

65000 characters

Additional1000000 characters

Solution Unicode Characters

SAP AG 2006 SAP TechEd rsquo06 SPC203 8

SAP NetWeavertrade The Integration Platform

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 9

SAP NetWeavertrade With Non-Unicode ABAP Stack Limited

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and businessprocesses

Integrates across technologiesand organizational boundariesA safe choice with full NET andJ2EE interoperability

The business foundation for SAPand partners

Powers business-readysolutions that reduce customintegrationIts Enterprise ServicesArchitecture increases businessprocess flexibility

DB and OS AbstractionNET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeavertradetrade

DB and OS Abstraction

Master Data Management

helliphellip

no

no

no

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 7: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 7

ASCIIGeneral Scripts

Symbols

CJK Ideographs

Hangul

Compatibility

Surrogate Area

65000 characters

Additional1000000 characters

Solution Unicode Characters

SAP AG 2006 SAP TechEd rsquo06 SPC203 8

SAP NetWeavertrade The Integration Platform

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 9

SAP NetWeavertrade With Non-Unicode ABAP Stack Limited

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and businessprocesses

Integrates across technologiesand organizational boundariesA safe choice with full NET andJ2EE interoperability

The business foundation for SAPand partners

Powers business-readysolutions that reduce customintegrationIts Enterprise ServicesArchitecture increases businessprocess flexibility

DB and OS AbstractionNET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeavertradetrade

DB and OS Abstraction

Master Data Management

helliphellip

no

no

no

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 8: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 8

SAP NetWeavertrade The Integration Platform

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 9

SAP NetWeavertrade With Non-Unicode ABAP Stack Limited

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and businessprocesses

Integrates across technologiesand organizational boundariesA safe choice with full NET andJ2EE interoperability

The business foundation for SAPand partners

Powers business-readysolutions that reduce customintegrationIts Enterprise ServicesArchitecture increases businessprocess flexibility

DB and OS AbstractionNET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeavertradetrade

DB and OS Abstraction

Master Data Management

helliphellip

no

no

no

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 9: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 9

SAP NetWeavertrade With Non-Unicode ABAP Stack Limited

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and businessprocesses

Integrates across technologiesand organizational boundariesA safe choice with full NET andJ2EE interoperability

The business foundation for SAPand partners

Powers business-readysolutions that reduce customintegrationIts Enterprise ServicesArchitecture increases businessprocess flexibility

DB and OS AbstractionNET WebSphere

People Integration

Com

posi

te A

pplic

atio

n Fr

amew

ork

Process IntegrationIntegration

BrokerBusiness Process

Management

Information IntegrationBusiness

IntelligenceKnowledge

Management

Life Cycle M

anagement

Portal Collaboration

J2EE non-Unicode ABAP

Application Platform

Multi-Channel Access

SAP NetWeaverSAP NetWeavertradetrade

DB and OS Abstraction

Master Data Management

helliphellip

no

no

no

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 10: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 10

Only Solution For Full Integration With Unicode

yes

yes

yes

Evolution ofmySAP Technology

Unifies and aligns peopleinformation and business processes

Integrates across technologies andorganizational boundaries

A safe choice with full NET and J2EEinteroperability

The business foundation for SAPand partners

Powers business-ready solutionsthat reduce custom integration

Its Enterprise Services Architectureincreases business process flexibility

SAP NetWeavertradeC

ompo

site

App

licat

ion

Fram

ewor

k

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

IntegrationBroker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

Unicode ABAPLife-C

acleM

gmt

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 11: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 11

Netweaver Application Server With ABAP And JAVA Stack

Impact of Combined ABAP andJAVA Stack instance on languagearchitecture

ABAP and JAVA stack running onone instanceCommon Database differentABAP and J2EE table schemaCommunication between ABAPand JAVA through fast JAVAconnector (JCo)JAVA runs on Unicode onlyIf ABAP stack runs in non-Uniocde conversion fromtoUnicode and non-Uniocderequired Can lead to data lossFull language data consistencyonly with both ABAP and JAVAstack in Unicode

Netweaver ASCentral Instance

Java

J2EEDispatcher

SDM

ABAPICM

ServerProcesses

Database Instance

J2EE SchemaABAP Schema

EnqueueService

MessageService

J2EE CentralServices

Dispatcher

EnqueueService

Gateway

MessageService

ServerProcesses

FastJCo

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 12: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 12

Open Integration And Connection SAPnon-SAP Everywhere

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 13: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 13

Communication The Ideal Picture

The ideal Picture only Unicode components

mySAP ERP

3rd Party

mySAP BI

mySAP ERP

FilesInternet

ExternalRFC Client(SAP_UC)

JAVAApplication

(Portal)

Ideal Large IT systemlandscape with Unicodesystems onlyConversions are donealgorithmically (11relation)No datamisinterpretationNo data lossAll business relevantcharacters available atthe same time

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 14: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 14

Communication Reality

R3 46C MDMP

3rd PartyEBCDIC

mySAP BWISO8859-1

mySAP ERP

BIG-5SJIS

IS0-8IS0-1 1251

IS0-9

IS0-2IS0-3IS0-7

6970277

6970500

1252

Files

ISO8859-1SJIS

charset=iso-8859-1 gtcharset=windows-1257 gt

charset=utf-8 gtcharset=Shift_JIS gt

Internet

ExternalRFC Client

(char)SAP_CODEPAGE

= 1100

JAVAApplication

(Portal)

The reality Unicode and non-Unicode components

Large IT landscape withmixed SAP and non-SAPsystemsTypical Unicode andnon-Unicode systemsSystems with oldreleasesConversions betweenincompatible code pageseverywhereOnly common subsetexchangeableSpecial rules have to beobeyed to makecommunication possible

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 15: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 15

The main interface challengesMany SAP systems in Unicode and non-Unicode Single Codepageand MDMP existMany interfaces to non-SAP systems existNo or incomplete list of all main interfaces is available no orincomplete information which interfaces exchange business textdata in which languagesEven if it is planned to convert all SAP systems to Unicode it ismostly only possible to convert one SAP system only at one timeDuring an Unicode conversion the effort for interface testing andadjustment is often underestimatedPartner systems or their interfaces to SAP are often old sometimeseven no more supported When re-connecting such an interface to anUnicode converted SAP system often even technical connectionsare no more possibleIf add-on software or non-SAP interface is not Unicode enabled anearly discussion with and solution from vendor is required

Communication Challenges in Large System Landscapes

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 16: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 16

Preparation For Interface Solutions

Complete lists of all interfaces required for efficient workInterface list for SAP ndash SAP system connectionsndash SAP Component Release Support Packagendash Additional installed software add-ons IS-solutions etc and

information if Unicode enabledndash Codepage and language configurationndash Interface language critical yesno ndash which languages

exchanged

Interface list for critical non-SAP system connectionsndash Name and vendor of interfacendash Technical information about interfacendash Codepage and Unicode informationndash Interface language critical yesno

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 17: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 17

UnicodeSP260EP

Unicode since1003

Unicode40CRM

110030APOWith BW1100(missing)35SEM

1100(missing)31BW

110028 14 1747 x 110R3

110040 530SRM

640 for Asiarequired

Allgt 40 620 640SAPGUI

Unicode39 20 2847x110R3

CommentCode PageSP LevelReleaseSAPComponent

Example List of SAP ndash SAP Interfaces at a Customer

Issue SAP Unicode ndash Unicode and Unicode ndash Single Codepage Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 18: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 18

Example List of SAP ndash non-SAP Interfaces at a Customer

Not UC compliantcheckdiscuss with(vendor)

BMC

Not UC compliant checkwith (vendor)

Readsoft Datamail Scanner

Critical Interfaces since not Unicode compliant

Supports LATIN-1 onlyLanguage Requirementsunclear

Global Passport (GP)Lotus QuickPlaceX1329IBM WEB ServerX73Vignette ( Portal)-AD2003MS Active Directory ServerX502Websphere Application ServerX61 213WEBMETHODS SAP JCo

Language critical = X = unknown - = unlikely

VersionAdapter Product Component

- Issue Most interfaces language critical- Issue 2 interfaces not Unicode compliant action needed

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 19: Integration Between Heterogeneous SAP Unicode and Third ...

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 20: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 20

Communication Technology tofrom SAP Systems (1)

RFC is the most used technology for the connection with SAP systemsSAP Unicode ndash Unicode or SAP non-Unicode ndash non- Unicodeconnections are called ldquohomogenousrdquo mixed connections SAP Unicodendash non-Unicode or vice versa are called ldquoinhomogeneousrdquoRFC automatically converts between Unicode and non-Unicode in caseof an inhomogeneous connection always on the Unicode systemFor the Unicode ndash non-Unicode single codepage conversion acommunication codepage ( connection codepage) is determined duringthe connection which is determined according to several rulesA special RFC function is available between a SAP Unicode ndash SAPMDMP ABAP based connection only which however requires specialinterface development in most scenarios In all other cases oneseparate connection (ldquochannelrdquo) per codepage between a non-ABAPUnicode and SAP MDMP system is needed

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 21: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 21

Communication Technology tofrom SAP Systems (2)

The communication between SAP and non-SAP systems is often donethrough special connectors and adapters which have been developedby SAP or partners for the dedicated connection The connectors areoften using the RFC technology with basically the same conversionrules as SAP-SAP in case of an inhomogeneous connection betweenUnicode and non-Unicode The connectors usually support Unicode andsingle codepage partners however supported versions and newestpatch levels are requiredThe proper RFC Unicode related settings for a SAP ndash non-SAPconnection (SAP caller non-SAP caller) are crucial and should beanalyzed and checked carefullyIf an external RFC client server program (eg written in C or C++) isused it should be clarified if it shall support single code page only orUnicode In case of Unicode support the external C-program must beadjusted for Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 22: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 22

E3 91 B979 3434 79U+3479

CE B1B1 0303 B1U+03B1

C3 A4E4 0000 E4U+00E4auml6161 0000 61U+0061a

UTF-8UTF-16little endian

UTF-16big endian

Unicodescalar value

Character

Representation of Unicode Characters

UTF-16 ndash Unicode Transformation Format 16 bit encodingFixed length 1 character = 2 bytes (surrogate pairs = 2 + 2 bytes)Platform-dependent byte order (biglittle endian)2 byte alignment restriction

UTF-8 ndash Unicode Transformation Format 8 bit encodingVariable length 1 character = 14 bytesPlatform independentno alignment restriction7 bit US ASCII compatible

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 23: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 23

Legend asc = ASCII as = Asian nas = non-Asian

CD E0 C5 A1AB

CD E0 C5 A1AB

E0B8AD E0B980E0B8A5 E0B881E0B88B

0E2D 0E40 0E250E01 0E0B

Thai

8341 838C8362 834E8358

8341 838C8362 834E8358

E382A2 E383ACE38383 E382AFE382B9

30A2 30EC 30b330AF 30B9

Japanese

C0 EB E5 EAF1

B0 DB D5 DAE1

D090 D0BB D0B5D0BA D181

0410 043B 0435 043A0441

Russian

41 6C 65 7841 6C 65 7841 6C 65 780041 006C 0065 0078AlexGerman

1 Byte nas2 Byte as

1 Byte nas2 Byteas

1 Byte asc2 Byte nas3 Byte as

2 Byte perCharacter

WindowsISOUTF-8UTF-16Big Endian

(sameword)

CodepageWordLanguage

Conversion Example Unicode tofrom Single Code Page

Conversion between Unicode and non-Uniocde in particular difficultfor Asian languages

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 24: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 24

In case of an Unicode Unicode combination RFC passes all characterdata without code page conversion or merely with adaptation of theendianness

UTF-16 big endian = SAP code page 4102UTF-16 little endian = SAP code page 4103

Information about the destination is maintained in SM59special options character width in target system

1 Byte = non-Unicode2 Byte = Unicode

SAP RFC Unicode Unicode

mySAP ERP mySAP ERP

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 25: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 25

In case of an Unicode non-Unicode single code page combinationRFC passes all character data with code page conversion betweenUnicode and the single code page

As Unicode is a true superset of any old standard codepage not allUnicode characters can be transferred to the non-Unicode systemIf the partner is an external single code page system the same conversionrules between Unicode and single code page apply

Auml Aumlszlig szlig

RFC SAP Unicode Non-Unicode Single Code Page

R3 46CISO8859-1

mySAP ERP

Invalid charactersin ISO-8859-1 MS

1252 systemUnicode to Single Codepageonly allows valid charactersfor target codepage

ExternalMS 1252

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 26: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 26

In case of an Unicode non-Unicode MDMP combination RFC passesall character data with code page conversion between Unicode and thedifferent old code pages if RFC transfer structure contains a language key

Which of the MDMP code pages is chosen depends on the language

Auml DE Aumlszlig DE szlig

JAJA

JA JA

RFC SAP Unicode SAP Non-Unicode MDMP

R3 46CISO8859-1

SJIS

mySAP ERP

Mixed codepage payload communication between SAP MDMPand 3rd party system NOT supported

Invalid in ISO-8859-1 and SJIS

Unicode to MDMP onlyallows valid charactersof configuredcodepages

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 27: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 27

homogeneous

homogeneous

inhomogeneous

4102 Big Endian Unicode4103 Little Endian Unicode8000 Japanese SJIS Non-Unicode

Codepage Conversion in RFC Communication

Conversion alwayson Unicode server

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 28: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 28

SM59 SAP Unicode Calls External Unicode System (640)

The RFC connection to anexternal (Type T) Unicode

system is marked withcharacter width Unicode TheUnicode test can be used to

verify

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 29: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 29

The registered externalprogram should beUnicode enabled

SM59 Check if Registered Server in Unicode (640)

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 30: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 30

SM59 SAP Unicode Calls External Non-Unicode

Conversion code pageSAP Unicode ndash externalnon-Unicode derivedform logon Languagehere ENUnicode LATIN-1

external programis non-Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 31: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 31

RFC ClientCallerExternalProgramUnicode

non-Unicode

mySAP ERPUnicode

External Program Calls SAP Unicode Via RFC Library

RFC Call to SAP

Conversion requiredif external caller is

single code page noconversion if Unicode

Many SAP connectors and other certified interfaces use RFC librariesto connect to SAP systems

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 32: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 32

Determination of RFC Communication Code Page

External Program is UnicodeHomogenous communication no data lossAutomatic recognition of Big and Little Endian

External Program is non-Unicode (Single Code Page)RFC determines communication code page and convertsbetween this code page and Unicode

Default code pagendash Environment parameter SAP_CODEPAGE

Example in UNIX setenv SAP_CODEPAGE 8000ndash RFC API RfcSetSystemCodepage

Expicit code pagendash RfcOpenEx at connection time

Example RfcOpenEx (ldquohellip CODEPAGE=8000 helliprdquohellip)

ndash RfcSetCodepage at runtimeExample RfcSetCodepage (handle ldquo8000rdquo)

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 33: Integration Between Heterogeneous SAP Unicode and Third ...

SAP Connectors and Unicode

Communication Examples

Introduction and Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 34: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 34

JAVA Connector And RFC Library (Non-Unicode Backend)

SAP Backendnon-Unicode

Java Appeg SAP EP orexternalapplicationsJAVA alwaysUnicode

RFC LibJCo RFCKernel

34

1 2

Local Code Page

Dataflow from Java application to SAP backend system1 Conversion from UTF-16 (JAVA) into local Code Page (CP)2 Conversion from local CP into one SAP CP controlled by JCo logon language

Dataflow from SAP backend system to Java application3 Conversion from one SAP CP into local CP controlled by Backend logon

language4 Conversion from local CP into UTF-16 (JAVA)

Conversion only correct for one code page per connection

JCo Logon lang

BackendLogon lang

Connects the ABAP and JAVAworld

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 35: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 35

Visual Basic And NET Connector Unicode ndash Unicode

UnicodeRFC

direct or viawdtU ocx

Unicode VisualBasic

Unicode

With Unicode RFC Unicode wdtU ocx no code page conversion neededStandard Visual Basic UI controls do not support UnicodeMS Office controls doVisual Basic NET uses UnicodeVia NET Connector communication with Unicode and non-Unicodepartners possible

mySAP ERP

Unicode

Connects the ABAP and NET world

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 36: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 36

Communication With Visual Basic Unicode ndash Single CP

non-UnicodeRFC

direct or viawdt ocx

Unicode=gt

RFC com-municationcode page

VisualBasic

Windowsdefault

code page=gt

Unicode

Data transfer is restricted to Windows default code pageto configure in Windows Control Panel Regional and Language Options

RFC partner code page must match to Windows default code page(eg LATIN-1 MS 1252 SAP Codepage 1160)

mySAP ERP

Unicode

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 37: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 37

Business partners

Third-party

Third-partyThird-

party

SAPSAP

Mainframeapplication

SAP

WebsphereNET

Businesspartner

application

Third-party

SAP

RosettaNetmiddleware

SAP

SAP

Other integrationsolution

SAP NetWeaver

SAP XI

SAP XI

Other integrationsolution

Integration of External Systems Through SAP XI PI

SAP XI PI runs on Unicode only

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 38: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 38

Huge Number of Adapters For Open Communication

The Adapter Engine hosts a set of adaptersSAP Adaptersndash File FTPndash JDBC (Database)ndash JMS (MQSeries SonicMQ hellip)ndash RFCndash SOAPndash Mailndash Business Connector (B2B protocol)ndash Marketplace Adapterndash RosettaNet (RNIF 20) Adapterndash CIDX (RNIF 11) Adapter

3rd Party Adaptersndash iWay UCCnet more to come hellip (Peoplesoft- Siebel- Oracle UCCnet-

Transora- and AS2- adapters already certified for SAP XI 30) hellipndash Seeburger numerous EDI adapters AS2 Generic EDI OFTP VAN Access

Payment several Industry Specific Adapters (incl mappings)ndash Optional Adapters developed by partners certificated by SAP

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 39: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 39

Supporting Unicode And Single Codepage

Permitted values for the filecode page are the existingcharsets of the Javaruntime as egUS-ASCIIISO-8859-1UTF-8 UTF-16BE

Example XI File Adapter

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 40: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 40

Code Page Information About XI Adapters

httpservicesapcomxi --gt XI in Detail Connectivity

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 41: Integration Between Heterogeneous SAP Unicode and Third ...

SAP Connectors and Unicode

Communication Examples

Introduction ndash The Challenge

Basics of Communication

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 42: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 42

Example Connecting WebMethods to SAP Unicode System

The webMethods for SAP solution extends the benefits of theSAP Netweaver architecture and avoids time-consuming andcostly recoding by delivering powerful new functionalityincluding ( see wwwwebmethodscom for information)

An out of the box graphic mapping tool

Strong support for XSLT FLOW and Java mappings

Integration to heterogeneous operating environmentsImproved multi-enterprise multi-application functionality

Best-of-breed trading partner management

Automated message delivery and system of record managementCommunication with Unicode Systems

How to configure the SAP Unicode ndash webMethods connection

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 43: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 43

Connecting WebMethods to a SAP Unicode Systen

STEP1Check and verify that SAP webMethods Adapter supports Unicode

STEP2Use webMethods latest SAP Adapter to connect to the Unicode SAPSystem The newest version of SAP webMethods supports an UnicodeSAP System Use latest Jco archives to connect with the SAP system

STEP3In SAP System configure RFC Destination with Character Width Communication Type in Target System as Unicode

STEP4RFC Listener should be configured with Unicode in webMethods SAPAdapter improved multi-enterprise multi-application functionality

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 44: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 44

Configure RFCDestination with

Communication TypeUnicode

RFC Settings in SAP For WebMethods Destination

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 45: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 45

ConfigurewebMethods SAPRFC Listener withUnicode Option

WebMethods Settings For SAP RFC Unicode Listener

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 46: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 46

Example Excel ndash Upload Download of Turkish (TR) Files

SAP UC

csv xls csv

SAP UC

SAPLogon TR

4102 1614

SAPLogon TR

1614 4102

Win System CP TRExcel Sheet

Insert TR charsldquo

MS Excel

SAP Unicode

1614 Windows CP Turkish(LATIN-5)

4102 Unicode UTF-16 BE

AbbreviationsCP Code PageTR TurkishUC Unicode

How to manage in SAP to uploaddownload Excelfiles with Turkish texts ( LATIN-5 character set )

Win System CP TR

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 47: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 47

Code Page Settings in SAPLogon And Windows

SAPLogon Settings per system entry(UploadDownload Encoding)

Can be changed by users and per SAPLogon entryIndependent of the Windows System Code PageWindows System Code Page (bdquoLanguage for Non-Unicode Programsldquo)Excel Code Page Handlingndash Creation of new Excel sheets

- Excel allows to use Unicode and Non-Unicode via ldquoFont Switchingrdquo only (changefont to eg Arial Unicode MS) This is done automatically if you insert specialcharacters from different former code pages

ndash XLS CSV conversion- The ldquoSAVE AS CSVrdquo function supports only the creation of Non-Unicode files The

code page of the CSV file is determined by the Windows System Code Pagedescribed above

ndash XLS TXT- The SAVE AS function allows the creation of Unicode files The encoding format is

UTF-16 Little Endian

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 48: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 48

SAPLogon 640 Settings

Encoding set used forClient - BackendCommunication

(eg Excel upload)

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 49: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 49

Windows XP System Code Page

Start Control Panel Regional and Language Optionstabstrip ldquoAdvancedrdquo select the language you wish to

work with

ldquoLanguage for non-Unicode programsrdquo- Also called ldquoDefault or system

code pagerdquo- Some SAPGui components in

Unicode still refer to thisnon-Unicode locale

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 50: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 50

Summary

Ideal integration and communication for Unicode based SAPand external systems only

Have a complete list of all critical interfaces in the systemlandscape with information about communication technologyand information if language relevant and which languagesexchanged

Check early with vendor of external system if Unicode enabled

In case of inhomogeneous SAP Unicode to single codepageexternal system connection be aware of code page conversion

SAP systems with ABAP and JAVA stack work ideally togetherin Unicode only

Consider the deployment of SAP XI PI to connect to externalsystem

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 51: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 51

Public Webhttpwwwservicesapcomunicode Customer contacthttpwwwservicesapcomunicodesap Technologywwwsdnsapcomsdndevelopersguidesdn NetWeaver Developerlsquos Guide

Related WorkshopsLectures at SAP TechEd 20052006SPC200 Conversion of SAP Systems to Unicode lectureSPC251 Making Programs Unicode EnabledEPI108 Unicode Everywhere Now How Can You Deal with Different

Encodings in Your IT Ecosystem ASUGSPC205 ASUG Influence Update Computing Infrastructure

Related SAP Education Training Opportunitieshttpwwwservicesapcomglobalization Service Offerings Unicode

Further Information

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 52: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 52

New Book ldquoUnicode in SAP-Systemenrdquo

httpwwwsap-pressdekatalogbuechertitelgptitelID-1321

SAP PRESS340 pagesISBN 3-89842-832-X

Availableend October 2006in German firstEnglish follows

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 53: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 53

QampA

Questions

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 54: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 54

THANK YOU FOR YOURATTENTION

QUESTIONS ndash SUGGESTIONS ndash DISCUSSION

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 55: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 55

Please complete your session evaluation

Be courteous mdash deposit your trashand do not take the handouts for the following session

Feedback

Thank You

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved

Page 56: Integration Between Heterogeneous SAP Unicode and Third ...

SAP AG 2006 SAP TechEd rsquo06 SPC203 56

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 informationcontained herein may be changed without prior noticeSome software products marketed by SAP AG and its distributors contain proprietary software components of other software vendorsMicrosoft Windows Outlook and PowerPoint are registered trademarks of Microsoft CorporationIBM DB2 DB2 Universal Database OS2 Parallel Sysplex MVSESA AIX S390 AS400 OS390 OS400 iSeries pSeries xSeries zSeries zOS AFPIntelligent Miner WebSphere Netfinity Tivoli and Informix are trademarks or registered trademarks of IBM Corporation in the United States andor othercountriesOracle is a registered trademark of Oracle CorporationUNIX XOpen OSF1 and Motif are registered trademarks of the Open GroupCitrix ICA Program Neighborhood MetaFrame WinFrame VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems IncHTML XML XHTML and W3C are trademarks or registered trademarks of W3Creg World Wide Web Consortium Massachusetts Institute of TechnologyJava is a registered trademark of Sun Microsystems IncJavaScript is a registered trademark of Sun Microsystems Inc used under license for technology invented and implemented by NetscapeMaxDB is a trademark of MySQL AB SwedenSAP R3 mySAP mySAPcom xApps xApp SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world All other product and service names mentionedare the trademarks of their respective companies Data contained in this document serves informational purposes only National product specificationsmay vary

The information in this document is proprietary to SAP No part of this document may be reproduced copied or transmitted in any form or for any purposewithout the express prior written permission of SAP AGThis document is a preliminary version and not subject to your license agreement or any other agreement with SAP This document contains only intendedstrategies developments and functionalities of the SAPreg product and is not intended to be binding upon SAP to any particular course of business productstrategy andor development Please note that this document is subject to change and may be changed by SAP at any time without noticeSAP assumes no responsibility for errors or omissions in this document SAP does not warrant the accuracy or completeness of the information text graphicslinks or other items contained within this material This document is provided without a warranty of any kind either express or implied including but not limitedto the implied warranties of merchantability fitness for a particular purpose or non-infringementSAP shall have no liability for damages of any kind including without limitation direct special indirect or consequential damages that may result from the useof these materials This limitation shall not apply in cases of intent or gross negligenceThe statutory liability for personal injury and defective products is not affected SAP has no control over the information that you may access through the useof 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-partyWeb pages

Copyright 2006 SAP AG All Rights Reserved