Ansicht
Dokumentation

RSUNUXS3 - Unicode compatibility of user-exits

BAL_S_LOG - Application Log: Log header data   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Title

Unicode compatibility of user-exits.

Purpose

The old SMOD/CMOD extension mechanism had been built in a specifc way in most of the cases. SAP defined the user exits and deleviered empty functions. Such a function contains only an include-statement for a include, which has a name starting with 'ZX'. SAP does not deliver ZX-files and it is no error, if such files are not existent.

Each customer can activate such a user exit and put his own code into the related ZX-file. By the include technique the customer's code is merged into the frames provided by SAP.

Starting with the Technology release 6.10 there are new features in the ABAP language, that enables a programmer to write ABAP programs, that exceute simmilaryly in Unicode systems and in non-Unicode systems. Programs that follow these new rules can have the Unicode flag on.

As SAP also delivers Unicode-systems, all relevant programs delivered by SAP have the Unicode flag on. This holds also for the empty function groups of the user exit mechanism.

When a customer's system is upgraded from an older release to Enterprese 4.7 or CRM 3.0 this brings together Unicode-enabled functions with customer's code, which meight be not compatible with Unicode.

This report ("RSUNUXS2") scans for such collisions. And it knows, which of the envolved functions and function groups contain no or only very simple code by SAP.

If there are functions groups, which contain customer's code, which is not Unicode compatible and which on the other hand contain no or only harmless code by SAP, then the Unicode flag of such function groups are switched off.

If the customer's code is Unicode compatible, nothing has to be done.

Only if the customer's code is not Unicode compatible and if also SAP's code in the same function group is substantial, then the customer needs to Unicode-enable his code.

Integration

Prerequisites

Features

Selection

The important parameter ist the first one (SWITCHIM, "Change Unicode-flag immediately"). If you are not sure, you should leave it off. In that case the database is scanned and a report is displayed. You can then use interactive reporting to either switch the Unicode-flag where possible. Or to call transaction UCCHECK on the listed objects.

You can restrict the scanner to specific functions, if you know their names.

The report has an additional parameter to select the level of detail. A value of '0' creates a report as short as posible. Higher values add additional information the the report.

Standard Variants

none.

Output

A list of function groups, which have problems.

Then function groups are classified into up to six different kinds.

For each kind, a short description is given.

And finally there are push-buttons to modify the Unicode flag or th start UCCHECK..

(Each part of the list will only show up if needed. So if you are luckly, the list contains only the sentence "There are no problems".)

Activities

Example

ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3393 Date: 20240601 Time: 162559     sap01-206 ( 64 ms )