Ansicht
Dokumentation

UMG_FIND_SJIS_DUPLICATES_INDX - Find SJIS duplicates in INDX type tables

CPI1466 during Backup   General Material Data  
This documentation is copyright by SAP AG.

Purpose

The report UMG_FIND_SJIS_DUPLICATES_INDX can be used to search for characters from the Unicode private use area (PUA). Such characters can exist after a Unicode conversion because SAP code page 8000 (SJIS) defines characters - so called NEC vendor specific characters - which are mapped to the PUA for reasons of round trip compatibility. Additionally broken multi byte characters are mapped to the PUA also.

Since the processing of PUA characters has implications ( e.g. when display, search, printing) they should be replaced with duplicate characters from the standard Unicode range.

Integration

Prerequisites

Features

Currently UMG_FIND_SJIS_DUPLICATES_INDX is designed only as analysis tool because the repair of INDX data is not possible in general but might need application specific knowledge on the structure of the compressed data in the INDX records.

Selection

The selection screen offers two parameters

• Table Name (technical name P_TABLE)

Defines the name of the INDX like table you want to analyze.

• Plugin (technical name P_CLAS)

Defines the method which should be used to analyze the texts. Currently three methods are supported.

Search for NEC vendor specific characters

CL_I18N_DBS_UC_PUA_SJDUP for the execution of the report in Unicode system and CL_I18N_DBS_SJIS_DUPLICATES for non Unicode systems. These methods are used also in the search and replace tool RSI18N_SEARCH for the analysis of transparent tables.

Search for broken multi byte characters

CL_I18N_DBS_BROKEN_8000 for non Unicode systems.

In Unicode systems the analysis is restricted to records which were stored with one of the following code pages: 8000 (SJIS), 4102 (UTF-16BE) or 4103(UTF-16LE).

In non Unicode systems the analysis is restricted to records which were stored with code page 8000 (SJIS).

Standard Variants

Output

The results of the analysis are written to an ABAP list.

Example for table STXL

Analysis for table STXL

Plugin used: CL_I18N_DBS_UC_PUA_SJDUP

Key: 000TXFORM      FORN_PT1                                               TXT J

Key: 809TXTEXT      I18N_PRINT_TEST_SC_JA                               ST  J

Total number of records which were analyzed: 12345

Number of records with duplicates: 2

Number of records which could no be analyzed: 5

In the example 12345 records were analyzed, 2 records contain texts with characters from the PUA area, 5 records could not be analyzed. The reason for records which cannot be analyzed is the following: reading texts from INDX like tables is in general possible only with the knowledge about the structure of the compressed data stored in the INDX records. Therefore the analysis is based on a specific C-Call which was designed for the Unicode conversion. This C-Call can read text data from any INDX like table but does not return results for "old" records having a specific version number. "Old" records are defined as records which were created with a kernel patch level < 1204(46D).

The key of an affected record is displayed as concatenated string of the single components. For table STXL, key values can be assigned to the components in the following way

MANDT = 000

RELID = TX

TDOBJECT = FORM

TDNAME = FORN_PT1

TDID = TXT

TDSPRAS = J

Activities

It is recommended to execute the report in background because an analysis can take very long, depending on the amount of records to be analyzed. The result can be found in the spool request created by the background job.

Example

TXBHW - Original Tax Base Amount in Local Currency   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 5266 Date: 20240520 Time: 130449     sap01-206 ( 78 ms )