Unicode impact on abap programming

[Former Member]

We are on SAP 4.7 (non-unicode) system. Now we are planning for unicode version in SAP 6.0.. Can u please explain me the difference between non-unicode, unicode version and also tell me what would be the impact on abap object while moving from non-uncode version to unicode version.

Thanks

Mohit khandelwal

[Former Member]

Hi,

Non Unicode system

Since 4.6c every character can occupy 1 byte(ie 8 bits or single byte code pages) to display the characters. These characters are not sufficient to display the East Europian languages... So we need to double byte code pages required.(ie 2 bytes that means 16 bits)

Unicode system

From the 4.7(Enterprise edition Version) SAP system is a unicode system, From now onwards every character can occupy 2 bytes. this is called Unicode system

In SE38 program attributes we will get the check box unicode checks active , this option we will get the from 4.7 EE versions.

Non unicode system below function modules are obselete

ws_upload

ws_download

open dataset p_file for ouput

open dataset p_file for input

Replaced in unicode system

GUI_UPLOAD

GUI_DOWNLOAD

OPEN DATASET P_FILE FOR OUTPUT ENCODING DEFAULT

OPEN DATASET P_FILE FOR INPUT ENCODING DEFAULT

while upgrading from one version to another version the below Tcode which suppose to frequently

SPAU(For sap object like programs and function modules)

SPDD (For sap data dictionary objects)

UCCHECK(unicode adjust ments)

Thanks

Ramakrishna Pathi

[Former Member]

Hello,

The main difference is that a unicode sap system will support multi-languages. that is any person can log on the system with different languages and everything will be translated according.

SAP supports over 30 languages on Non-Unicode systems, but due to the technical limitations of code pages, only certain combinations of languages to be used without restrictions. The following options are available:

1. Single standard code pages, which can support specific sets of languages. The number and combination of languages that are supported cannot be altered, but there are no restrictions on users.

2. Unambiguous Blended Code Pages, which are SAP proprietary code pages that contain characters from one or more standard code pages. This increases the combinations of languages that can be used. Functionally, a Blended Code Page system uses a single code page.

3. Multi-Display / Multi- Processing

(MDMP)__which allows dynamic code page switching on the application server, and therefore permits any combination of standard code pages on one system. The log-on language determines the code page that is active for each user. Some restrictions must be followed..

[awin_prabhu]

Hi friend,

Unicode provides a unique number for every character, independent of platform and programming language. That is why every system is getting upgraded to unicode one(ECC 6.0)

See some other statements also,

1.

Non-unicode:

DESCRIBE FIELD PWD LENGTH LEN.

The above statement is obsolete in ECC. So, replace it with the following statement:

Unicode (ECC 6.0):

DESCRIBE FIELD PWD LENGTH LEN IN CHARACTER MODE. <-- character or byte mode

2.

Non-unicode:

In unicode programs the "-" character cannot appear in names. Ex: DATA name-new type c.

Unicode (ECC 6.0):

Use '_' (underscore) for names. Ex: DATA name_new type c.

3.

Non-unicode:

Search 'Hello SAP' for 'SAP'. <-- will work

Unicode (ECC 6.0):

Search 'Hello SAP' for 'SAP'. <--- will not work and will not give any syntax error.

So, use --> FIND FIRST OCCURRENCE OF 'SAP' in 'Hello SAP'.

4.

Non-unicode:

Explicit length is not required. Ex: DATA name type c.

Unicode (ECC 6.0):

Explicit length is required Ex: DATA name(5) type c.

Use T-code UCCHECK for checking unicode errors.

Thanks..

Edited by: Sap Fan on Mar 13, 2009 10:11 AM

Edited by: Sap Fan on Mar 13, 2009 10:12 AM

Edited by: Sap Fan on Mar 13, 2009 10:13 AM

[kamesh_g]

hi

difference between SAP UNICODE and NON-UNICODE UPGRADE?

UNICODE: From Release 6.10, ABAP supports multi-byte coding for characters in Unicode. Prior to Release 6.10, ABAP used only character sets that were based on single-byte codes u2013 such as ASCII and EBCDIC u2013 or double-byte codes, such as SJIS and BIG5.

NON-UNICODE: This non-unicode error removal is just to replace any obsolete commands or function modules, tables such as, WS_UPLOAD, UPLOAD, etcu2026

[Former Member]

Hi,

You will get more on Unicode, click the following link.

http://unicode.org/standard/WhatIsUnicode.html

Regards,

Sathish

[uwe_schieferstein]

Hello Mohit

The SAP documentation is quite comprehensive about the impact of Unicode on ABAP programming:

[ABAP and Unicode|http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm]

Another useful document is:

[Unicode Enabling of ABAP Programs|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1c17a590-0201-0010-d4b6-9c742ffe3633]

Very important you have to check every file interface:

[Unicode File Handling in ABAP|/people/ulrich.brink/blog/2005/08/18/unicode-file-handling-in-abap]

Regards

Uwe