topic Re: unicode upgrade in Application Development and Automation Discussions

unicode upgrade

Former Member — Mon, 31 Mar 2008 11:09:35 GMT

do need detail info about unicode environment.

kindly share the useful info

Re: unicode upgrade

Former Member — Mon, 31 Mar 2008 11:13:24 GMT

Hi,

Check out this thread.

Reward if helpful.

Regards,

Ramya

Re: unicode upgrade

Former Member — Mon, 31 Mar 2008 11:16:10 GMT

Hi,

Hope this link resolves ur issue.

[original link is broken]

Reward points if useful.

Regards

Rose

Re: unicode upgrade

uwe_schieferstein — Mon, 31 Mar 2008 11:16:53 GMT

Hello

You may have a look at the links provided in

Regards

Uwe

Re: unicode upgrade

Former Member — Mon, 31 Mar 2008 11:23:23 GMT

Hi Sundeep,

A Unicode SAP system

 enables you to harness internet technologies better.

 allows better integration with non-SAP products and seamless integration with existing SAP systems.

 offers a superior platform for collaborative, cross-system business applications.

 all languages and language combinations in the world!

 allows you to install a central system for worldwide business processes, e.g. to gather and store aggregate customer data.

 enables you to optimize your system landscape and reduce your costs.

What is Unicode?

Unicode is an international standard that assigns characters from virtually every language and script a unique Unicode Scalar Value, which is a number written in hexadecimal notation. As a notational convention "U+" is prefixed to the Scalar Value.

Unicode provides the solution to the problem of multiple, possibly incompatible code pages:

 Unicode currently defines over 98,000 characters, with room for over 1 million characters.

 Unicode defines each character only once

 Unicode can be used for the system code page, front end, and printing

 In a Unicode SAP system you can display and maintain character data from any language with any logon language. For example, you can logon to your system in Japanese and maintain Russian data.

The size and scope of Unicode have made it the default character encoding of the Internet communication, such as XML, Java, and HTML, because Internet communication has to function no matter what the platform, no matter what the program, no matter what the language.

Unicode attempts to support all of the scripts used in the world. Where more than one language shares a set of symbols that have a historically related derivation, the union of the set of symbols of each such language is unified into a single collection identified as a single script. These scripts then serve as inventories of symbols which are drawn upon to write particular languages. In many cases, a single script may serve to write tens or even hundreds of languages. The Latin script is used for example by English, German and Vietnamese, the Arabic script is used by Arabic, Farsi and Urdu. In other cases only one language employs a particular script (e.g., Hangul, which is used only for the Korean language). The writing systems for some languages may also make use of more than one script; for example, Japanese traditionally makes use of the Han (Kanji), Hiragana, and Katakana scripts, and modern Japanese usage commonly mixes in the Latin script as well.

 If your non-Unicode system is on a Unicode-enabled release (SAP_BASIS 6.20 onwards) and you do not plan to upgrade to a higher release, you can use the standard Unicode conversion path. This applies to all code page configurations (Single Code Page, Blended Code Page, MDMP).

Please read the Unicode Conversion Guide which is the official documentation for this method. You can download all valid versions on this website from Unicode Library -> Unicode Conversion Library -> Unicode Conversion Guide (6.20/6.40/7.00).

 If your non-Unicode system is on release SAP_BASIS 4.6C and you plan to upgrade to SAP ERP 2005 exclusively, you can use the Combined Upgrade & Unicode Conversion path. This applies for all code page configurations (Single Code Page, Blended Code Page, MDMP).

Please read the Combined Upgrade & Unicode Conversion Guide which is the official documentation for this method. You can download this documentation on this website from Unicode Library -> Unicode Conversion Library -> Combined Upgrade & Conversion.

Further information about this method is available in SAP Note 928729.

 If your non-Unicode system is on a release lower than SAP_BASIS 4.6C or on SAP_BASIS 6.10 and you plan to upgrade to a Unicode-enabled release, you can use the Twin Upgrade & Unicode Conversion path. This method is available for pilot customers only. Please read SAP Note 959698 for details.

Re: unicode upgrade

Former Member — Mon, 31 Mar 2008 11:29:21 GMT

hope it will help you.

Reward iff help.

The Link will be helpful to you.

Very good document:

http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d37d1ad9-0b01-0010-ed9f-bc3222312dd8

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/589d18d9-0b01-0010-ac8a-8a22852061a2

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f8e316d9-0b01-0010-8e95-829a58c1511a

You need to use the transaction UCCHECK.

The report documentation is here

ABAP Unicode Scan Tool UCCHECK

You can use transaction UCCHECK to examine a Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. From the list of Unicode syntax errors, you can go directly to the affected programs and remove the errors. It is also possible to automatically create transport requests and set the Unicode program attribute for a program set.

Some application-specific checks, which draw your attention to program points that are not Unicode-compatible, are also integrated.

Selection of Objects:

The program objects can be selected according to object name, object type, author (TADIR), package, and original system. For the Unicode syntax check, only object types for which an independent syntax check can be carried out are appropriate. The following object types are possibilities:

PROG Report

CLAS Class

FUGR Function groups

FUGX Function group (with customer include, customer area)

FUGS Function group (with customer include, SAP area)

LDBA Logical Database

CNTX Context

TYPE Type pool

INTF Interface

Only Examine Programs with Non-Activated Unicode Flag

By default, the system only displays program objects that have not yet set the Unicode attribute. If you want to use UCCHECK to process program objects that have already set the attribute, you can deactivate this option.

Only Objects with TADIR Entry

By default, the system only displays program objects with a TADIR entry. If you want to examine programs that don't have a TADIR entry, for example locally generated programs without a package, you can deactivate this option.

Exclude Packages $*

By default, the system does not display program objects that are in a local, non-transportable package. If you want to examine programs that are in such a package, you can deactivate this option.

Display Modified SAP Programs Also

By default, SAP programs are not checked in customer systems. If you also want to check SAP programs that were modified in a customer system (see transaction SE95), you can activate this option.

Maximum Number of Programs:

To avoid timeouts or unexpectedly long waiting times, the maximum number of program objects is preset to 50. If you want to examine more objects, you must increase the maximum number or run a SAMT scan (general program set processing). The latter also has the advantage that the data is stored persistently. Proceed as follows:

- Call transaction SAMT

- Create task with program RSUNISCAN_FINAL, subroutine SAMT_SEARCH

For further information refer to documentation for transaction SAMT.

Displaying Points that Cannot Be Analyzed Statically

If you choose this option, you get an overview of the program points, where a static check for Unicode syntax errors is not possible. This can be the case if, for example, parameters or field symbols are not typed or you are accessing a field or structure with variable length/offset. At these points the system only tests at runtime whether the code is sufficient for the stricter Unicode tests. If possible, you should assign types to the variables used, otherwise you must check runtime behavior after the Unicode attribute has been set.

To be able to differentiate between your own and foreign code (for example when using standard includes or generated includes), there is a selection option for the includes to be displayed. By default, the system excludes the standard includes of the view maintenance LSVIM* from the display, because they cause a large number of messages that are not relevant for the Unicode conversion. It is recommended that you also exclude the generated function group-specific includes of the view maintenance (usually L<function group name>F00 and L<function group name>I00) from the display.

Similarly to the process in the extended syntax check, you can hide the warning using the pseudo comment ("#EC *).

Applikation-Specific Checks

These checks indicate program points that represent a public interface but are not Unicode-compatible. Under Unicode, the corresponding interfaces change according to the referenced documentation and must be adapted appropriately.

View Maintenance

Parts of the view maintenance generated in older releases are not Unicode-compatible. The relevant parts can be regenerated with a service report.

UPLOAD/DOWNLOAD

The function modules UPLOAD, DOWNLOAD or WS_UPLOAD and WS_DOWNLOAD are obsolete and cannot run under Unicode. Refer to the documentation for these modules to find out which routines serve as replacements.