SAP Basis Tech Supports

Symptom

This Note is for SAP internal use only
A Text Language Flag in a delivered release needs to be changed
Other terms
Text Language Flag, RADNTLANG
Reason and Prerequisites
The Text Language Flag indicates whether a (and if so: which) structure component of type LANG indicates the encoding of text data components of the same structure.
Note 480671 “The Text Language Flag of LANG Fields” gives the background information.
Changing the Text Language Flag setting (OFF/ON) requires several actions by different departments. The section “Consistency Check” describes a validation of these actions.
We have seen incidents where a correct Text Language Flag was corrupted in later deliveries, Support Packages, etc, e.g. by irregular transport.
An important user of this flag is the Unicode Conversion which determines the data encoding code page from it.
Solution
Workflow Summary (ideally cut + paste into an internal message):
1. relevant for tables only: When setting the Text Language Flag to OFF, check if the condition meets for the table [The requestor of change]2. Create an internal message [The requestor of change]3. Change the Text Language Flag in its original system [The developer responsible for the object]4. Update report RADNTLANG for SAP_BASIS 620 [BC-DWB-DIC]5. Update Unicode Conversion Tools and Data [BC-I18-UNI]

Workflow Descriptions:
1. When setting the Text Language Flag to OFF, check if the condition meets for the table [BY: the requestor of the change]
For setting the flag to ‘OFF’, the table must be classified as “not translation-relevant”. You can check this from one of the following ways:a) Go to Transaction SE11 Display Table > Technical Settings… > Menu “Edit” > “Translation type”.b) If “Table is language-dependent but not translation-relevant” is set or Table DD09L-UEBERSETZ = ‘N’, then you can go ahead with further steps in this workflow.2. Create an internal message [BY: the requestor of the change]a) Create an internal message and mention this Note 963252b) Choose the component responsible for the table3. Change the Text Language Flag in its original system
[BY: the responsible developer of the table]a) In the original system of each affected release, change the text language flag. See Note 480671 “The Text Language Flag of LANG Fields” for details.b) Create a note describing the change and its delivery information4. Update report RADNTLANG for SAP_BASIS 620 [BY: BC-DWB-DIC]a) Applies when the change is the removal of the Text Language Flag and the structure has 1 (exactly one) LANG field: add this object to the exception list in report RADNTLANG (which turns this flag ON in Release 6.20 for all structures with exactly 1 LANG field, respecting the built in exception list).b) Attach the transport files for the modified report to Note 480671 “The Text Language Flag of LANG Fields”
A cookbook for packaging these transport files is attached to this Note. To determine the SP delivering this change: in CSN search for Correction Request by the transport; the Correction Request has a field “Hot Pack.”.c) REFERENCE: Note 480671. This applies only to release 620; in newer releases RADNTLANG does not modify SAP objects (only customer objects).5. Update Unicode Conversion Tools and Data [BY: BC-I18-UNI]a) Update SPUMG/SPUM4 Exception List
See “SPUMG Design (Preparation for the Unicode Conversion)”
http://bis.wdf.sap.corp:1080/abap/docs/I18n/Unicode/Conversion/Tools/SPUMG/spumg_design.doc
Section 3.4.3.1 “How to maintain the SPUMG/SPUM4 Exceptions Lists”b) Update Table UM4TXFLAG (4.6C)
Go to SE16 and delete the table manually from UM4TXFLAG. Currently (2008-10-16) there is no other maintenance possible for UM4TXFLAG. If the table does not exist in UM4TXFLAG you do not need to do any other actions here.c) Update Report UM4_DEFINE_LANG_TABLES(4.6C)
Go to SE38 and edit the report UM4_DEFINE_LANG_TABLES. Append the table to the internal exception list of the report in the subroutine form build_exception_list.
After you have finished the changes, create a patch transport request for Note 867193 as described in Section 4.2.1 “How to do a patch for note 867193″d) Update Note 867193 and its attachment
See “SPUM4 Design (Preparation for the Unicode Conversion CU&UC procedure)”
http://bis.wdf.sap.corp:1080/abap/docs/I18n/Unicode/Conversion/Tools/SPUM4/spumg46_design.doc
Section 4.2.1 “How to do a patch for note 867193″e) Update Note 672835 and its attachment 672835check.xls
There is a “last minute” check list of the Text Language Flag in Note 672835 “Textflags could cause problems during Unicode conversion”, for manual application. The file 672835check.xls provides the information such as; the newly set flag value, the table/field names and Release and Support Package which include the change, the relevant SAP Note.
This information is especially useful for customers who prefer Support Package installation over manual Text Language Flag changes.
Check-out the 672835check.xls from BIS via Perforce: //bis.wdf.sap.corp:1080/abap/docs/I18n/Unicode/TextFlags/672835check.xls
Select the worksheet according to the change:”OFF”(the flag newly set to ‘OFF’)”ON”(the flag newly set to ‘ON’)
Add the table/field names and the Support Package which includes the change.
How to retrieve the corresponding SAP_BASIS release information based on the Support Package name (e.g. SAPKE50010):
Support Portal – SAP Software Distribution Center at service.sap.com/swdc > “Download” > “SAP Support Packages and Patches” > “Search for Support Packages and Patches” > In “Search Term” field, type Support Package name (eg. SAPKE50010) and click “Search” > Click “View content info” icon > Under “Package Attributes”, find “Basis Release” information.
Technical Support Package name examples:ComponentSP NameSAP_BASISSAPKBrrrnnSAP_ABASAPKArrrnnSAP_APPLSAPKHrrrnnSAP_HRSAPKErrrnn
Zip the updated 672835check.xls and attach the zip file to Note 672835.
Check-in the updated 672835check.xls via Perforce.f) Perform Consistency Check
Download RADNTLANG source from Y6B (the 620 repair system) into file R;
SE16 in BIO, download UM4TXFLAG unconverted into local file U.
Note 672835: download the .xls document (with tables/structures with 1 LANG field, but where the text flag should not be set) attached to that Note into file N, in .CSV format.
Get the script tfCheck that is attached to this note. The following script calls (on Unix) show inconsistencies with the exception list built into report RADNTLANG:
tfCheck -4 R < U
tfCheck -c R < N
(The origin of this script is ~d019038/BIN/tfCheck.)
After everything is verified correctly, set the internal message’s status to ‘Completed’ to notify the requestor of the change.