Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to provide information about which steps have to be done before we start a Conversion.

Overview

The proper Single Codepage Conversion guide has been downloaded in step 2: How do I find the proper Unicode Conversion guide?

Now let's assume we have a Netweaver 7.40 system with below system state: 

Requirements and Restrictions

Please work through your Unicode Conversion Guide. The chapters "Requirements" and "Restrictions" are directly at the beginning of the guide. 

Not all of the listed requirements have to be checked. So if you have a Linux system with MaxDB database then the DB2-z/OS restrictions are not of interest. 

It is the same with the Component-specific requirements. An example: If you do not use EasyDMS or Credit Card Encryption then you can skip these requirements. 

 

In case one of the requirements fits then please work through the mentioned SAP Note and all referenced one to ensure a smooth and consistent conversion, e.g. SAP Note 573044 for HR functionality.

Starting with the Preparations

The preparation phase consists of several steps which have to be done weeks before the preconversion, as they can be very time consuming.

Consistency Check of Cluster Tables

To perform this action report SDBI_CLUSTER_CHECK has to be executed. This report checks and analyzes inconsistencies in Cluster Tables.

SDBI_CLUSTER_CHECK is not restricted to systems which will be converted to Unicode afterwards. You can use it as a regular maintenance task in all systems. You can execute the report anytime and as often as needed independent from SPUMG.
The runtime of SDBI_CLUSTER_CHECK is dependent on the size of the table clusters.

+++ Please Note +++

For very large table clusters it might take up to several days. Therefore you should execute this check at a very early stage of the Unicode Conversion Project.

Conversion of customer-defined Codepages

Customer Codepages start with '9' and can be converted using report RSCP0126.If no codepage exist then this step can be skipped.

In most cases printer codepages are used. 

Remote Code Page Check

Before the Unicode Conversion it is useful to check your own TCP/IP-connections and adjust the code page information if required. Run report UMG_CHECK_RFC in SE38 as described in the online documentation to check if the connection between the local system where you run UMG_RFC_CHECK and a remote TCP/IP destination is consistent regarding the involved local and remote code pages. 

UCCHECK 

This transaction has to run in order to enable your customer coding for Unicode. Please check SAP KBA 2575591 for more information or directly go to the UCCHECK specific page.

Delete Matchcode IDs

Run report TWTOOL01 to find all active pool-matchcode IDs. This is important because matchcode IDs are not supported in Unicode SAP systems.

Reducing Data Volume

Before starting the Unicode preconversion SAP recommends that you delete and/or archive obsolete data from these tables in order to improve the system performance during the conversion procedure

Language Flag Maintenance

As of Release 6.20 all LANG fields have a Data Dictionary (DDIC) attribute Text Lang. (indicator for a language field). This flag specifies that the LANG field determines the code page of the character data in that table. Text Lang. flags are evaluated during RFC communication between Unicode and non-Unicode systems to ensure that the correct character conversion is used.

Run report RADNTLANG to set the Text Lang. flag for all tables with one LANG/SPRAS field. 

Additional Preparation Steps

Printing Old Spool Requests after the Unicode Conversion

After the conversion it will be problematic to print out spool requests which have been created before the conversion. There is no possibility to recover the spool requests after the Unicode conversion.
SAP Note 842767 provides a step-by-step description on how to handle such spool requests before beginning the conversion procedure.

OTF Documents after the Unicode Conversion

OTF documents that were created before the Unicode conversion can not be processed after the Unicode conversion and they cannot be created again in the Unicode system. To save your OTF documents you can convert them into PDF using report RSBCS_CONVERT_OTF_FOR_UNICODE. This report is delivered with SAP Note 1349413. Follow the instructions in SAP Note 1349413 BEFORE beginning the conversion procedure.

Translation Environment 

If you use the SAP translation environment (transaction SE63) you must export the Proposal Pool in the non-Unicode system.

When the Unicode Conversion is finished, you must import the Proposal Pool into the Unicode system (see chap. 4.Unicode Conversion Completion. Follow the instructions in SAP Note 1055820.

Related Content

Related Notes

  • SAP KBA 2487397 - Which Unicode Conversion guide do I have to use? - Guided Answers
  • SAP KBA 2575591 - How to start with UCCHECK? - I18 WIKI
  • SAP Note 1348055 - Initial cluster records for Unicode migration
  • SAP Note 1077403 - Cluster table check with SDBI_CLUSTER_CHECK
  • SAP Note 485455 - Change in code page structure for Release >= 6.10

  • SAP Note 511732 - Removed code pages in 6.10

  • SAP Note 534720 - Converting customer-specific 9* code pages does not work

 

  • No labels