cancel
Showing results for 
Search instead for 
Did you mean: 

HI what is use of unicode conversion in NW.

Former Member
0 Kudos

Hi all, im ABAPer.

n i hv been assigned a proj to convert ABAP(HR module ) project into uncode conversion.

i read that everybody using Net Wearer make use of unicode conversion. what exactly use of unicode conversion in netwearer.

and im planning to take netwear training in future.

will it be helpful for me to handle this proj or not.

my job is only conversion not any coding parts. thats y im afraid of this conversion. if i wont get any development work after this.. ...

.please help. me clearing my doubt.

..

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
0 Kudos

<i>what exactly use of unicode conversion in netwearer.</i>

Unicode — the international characterencoding standard that allows your systems to handle text data from multiple languages simultaneously and consistently. In a Unicode system, users enter and display any character from any script, no matter which logon

language they use.

<i>and im planning to take netwear training in future.

will it be helpful for me to handle this proj or not.</i>

whatever work u do.. its always helpful

In XI perspective, limited usage based on client requirements

Unicode is an important factor when overall business process flow of whole organization is takn into account

Regards,

Prateek

Answers (2)

Answers (2)

Former Member
0 Kudos

Thnxs for valuable information.

Former Member
0 Kudos

Hi Patil,

If u r planning to take up Netweaver training, thats great as its one of the latest and upcoming tech...but u have mentioned.....<i>and im planning to take netwear training in future. will it be helpful for me to handle this proj or not.</i>......

Netweaver has got its own demands, i dont think u shud consider this from ur current project point of view.

About brief idea about unicode

In the past, SAP developers used various codes to encode characters of different alphabets, for example, ASCII, EBCDI, or double-byte code pages.

ASCII (American Standard Code for Information Interchange) encodes each character using 1 byte = 8 bit. This makes it possible to represent a maximum of 28 = 256 characters to which the combinations [00000000, 11111111] are assigned. Common code pages are, for example, ISO88591 for West European or ISO88595 for Cyrillic fonts.

EBCDI (Extended Binary Coded Decimal Interchange) also uses 1 byte to encode each character, which again makes it possible to represent 256 characters. EBCDIC 0697/0500 is an old IBM format that is used on AS/400 machines for West European fonts, for example.

Double-byte code pages require 1 or 2 bytes for each character. This allows you to form 216 = 65536 combinations where usually only 10,000 - 15,000 characters are used. Double-byte code pages are, for example, SJIS for Japanese and BIG5 for traditional Chinese.

Using these character sets, you can account for each language relevant to the SAP System. However, problems occur if you want to merge texts from different incompatible character sets in a central system. Equally, exchanging data between systems with incompatible character sets can result in unprecedented situations.

One solution to this problem is to use a code comprising all characters used on earth. This code is called Unicode (ISO/IEC 10646) and consists of at least 16 bit = 2 bytes, alternatively of 32 bit = 4 bytes per character. Although the conversion effort for the R/3 kernel and applications is considerable, the migration to Unicode provides great benefits in the long run:

The Internet and consequently also mySAP.com are entirely based on Unicode, which thus is a basic requirement for international competitiveness.

Unicode allows all R/3 users to install a central R/3 System that covers all business processes worldwide.

Companies using different distributed systems frequently want to aggregate their worldwide corporate data. Without Unicode, they would be able to do this only to a limited degree.

With Unicode, you can use multiple languages simultaneously at a single frontend computer.

Unicode is required for cross-application data exchange without loss of data due to incompatible character sets. One way to present documents in the World Wide Web (www) is XML, for example.

ABAP programs must be modified wherever an explicit or implicit assumption is made with regard to the internal length of a character. As a result, a new level of abstraction is reached which makes it possible to run one and the same program both in conventional and in Unicode systems. In addition, if new characters are added to the Unicode character set, SAP can decide whether to represent these characters internally using 2 or 4 bytes.

A Unicode-enabled ABAP program (UP) is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system (NUS) as in a Unicode system (US). In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.

In a US, you can only execute programs for which the Unicode flag is set. In future, the Unicode flag must be set for all SAP programs to enable them to run on a US. If the Unicode flag is set for a program, the syntax is checked and the program executed according to the rules described in this document, regardless of whether the system is a US or an NUS. From now on, the Unicode flag must be set for all new programs and classes that are created.

If the Unicode flag is not set, a program can only be executed in an NUS. The syntactical and semantic changes described below do not apply to such programs. However, you can use all language extensions that have been introduced in the process of the conversion to Unicode.

As a result of the modifications and restrictions associated with the Unicode flag, programs are executed in both Unicode and non-Unicode systems with the same semantics to a large degree. In rare cases, however, differences may occur. Programs that are designed to run on both systems therefore need to be tested on both platforms.

U can chk out this thread:

also, can refer:

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/communication%2binterfaces

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/exercising%2ba%2bunicode%2bconversion%2bp...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5001004f-ce99-2910-8fa9-c5e564a5...

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/82c445c2-0d01-0010-4ab2-fc7e1a25...

Hope this is helpful

kanan