Unicode conversion preparation: Container table T5GEFDATA

[] [] [] [] []

Related:

  1. Conversion to UnicodeSymptom *********************************************************************** * Conversion from non-Unicode to Unicode / *...
  2. Unicode Conversion DocumentationSymptom You are searching for documentation for conversion of SAP...
  3. Conversion of Single Code Page Systems to UnicodeSymptom You plan to convert your non-Unicode SAP system to...
  4. Reducing data volume before Unicode ConversionSymptom You want to reduce large data volume in particular...
  5. Unicode conversion: Number of rows of table clusters changedSymptom You are executing a Unicode conversion. After the Unicode...
  6. Problems with old spool requests after Unicode conversionSymptom After a Unicode conversion, you encounter the following problems...
  7. Distribution MonitorSymptom You want to use the Distribution Monitor for your...
  8. Unicode Conversion: TroubleshootingSymptom Problems or errors occur during conversion from non-Unicode SAP...

Symptom
You have recently done a Unicode conversion of a system. The non Unicode system was configured as Single Codepage, MDMP or Blended Codepage system.You execute transaction HREFI_UPDATE and display forms using the reporting tabThe tax code field of incoming P6/P9 forms are not displayed correctly (e.g. as 0000). Before the Unicode conversion the tax code field has been displayed correctly

or

You prepare a system for the Unicode conversion. The system is confiured as MDMP or Blended Codepage system. After the scan “Tables without Lang. Info.” you find “strange words” in the SPUMG vocabulary for table T5GEFDATA to which no language can be assigned.

Other terms

Unicode conversion, HREFI_UPDATE, UMGCONTAINER, SPUMG:$WA
Reason and Prerequisites

The table T5GEFDATA is a so called container table, i.e. structured data (text and binary data) are stored in the character like field T5GEFDATA-DATA1. For the Unicode preparation a special handling has to be done for table T5GEFDATA, taking the substructure of the container field into account.
Solution

The only solution to this problem is to create container control informationbeforethe Unicode conversion takes place. The control information for table T5GEFDATA is delivered by SAP, but it is possible that not all information is available at customer site because the basis support package level is too low.
Currently there is no tool available which can repair the affected records after the Unicode conversion took place.
Check if the control information for table T5GEFDATA is available:
-> Transaction SE38, execute report UMG_INSERT_CONTAINER and check if the following records exist:
Owner TableName Container Type Underly.Struc. Struc.Ref LogType
S T5GEFDATA DATA1 I FORM E
S P6 R PS0065
S P6B R PS0065
S P9 R PS0065
S SL1 R PS0070
S SL2 R PS0070

No additional action is necessary if the records exist.
If the records do not exist, please add them using the “Create” button from the menu bar. The records will be created with “Owner = ‘C’” which does not make any difference for the Unicode conversion.
After you created the records you can proceed with the Unicode preparation procedure. If the table T5GEFDATA has been scanned already you have to reset the table in the SPUMG scan “Tables without Language Information” and execute the scan for the table after the creation of the container control information.
The records are delivered in the following basis support packages:
SP03(7.01)
SP18(7.00)
SP23(6.40)
SP66(6.20)

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment