Defining Language Load
The problem of language load arises because the outdated or deleted texts are still displayed when you display the relevant screens, menus and so on. This occurs because only the texts were changed in the database. However, on the screen, the runtime representation (the load) of the relevant objects, which has not changed, is displayed.
Usually, this problem does not occur because all language transport programs delete or invalidate the runtime representations after the texts were changed in the database so that the system automatically regenerates the load with the changed texts during the next access.
However, in rare cases, the system may incorrectly or incompletely delete the load and still display the outdated texts.
Technical information
The following load types are relevant for the language transport.
Screen load
Here, a language-independent runtime representation (tables D020L, D020LINF or DYNPLOAD) and a language-dependent runtime representation (tables D021L, D021LINF or DYNTXTLD) of the screen fields are available.
Screen Painter load (table DDFTX)
This table buffers texts from the ABAP Dictionary.
CUA load (tables D345T, D346T and D342L)
Texts of menu bars and application toolbars
Easy Access Menu (table TTREELOADT) - as of Release 4.6
Texts of ALV grid control (table LTDXT) - as of Release 4.6
Caution:
Resetting the buffer does not cause any damage within the system because missing data is automatically reselected or regenerated. However, resetting the buffer using the report mentioned below may cause problems.
Since buffers are reset, the performance may temporarily deteriorate.
Resetting the language-independent screen load and the screen painter load may result in lock situations. This occurs if a program generates a selection screen while it is running in a background process and users want to simultaneously use the same screen in dialog mode. If this occurs, users may be blocked until the background job is completed.Therefore, be careful when you start the report in the production system, and start the report only if no background processes are scheduled that have a long runtime. Note the following: After you run the report RSLANG20, do NOT execute /$SYNC", even if this is recommended in a text line output because this may result in negative side effects (for example, for the number range management). Instead, use the commands /$CUA and /$DYN.
Solution
To explicitly delete the runtime representations, proceed as follows:
1. For Releases 3.1 and 4.0:
First, import the transport request SAPKL31H05 from the directory ~ftp/general/R3server/language/del_load from sapserv.
Subsequently, execute the report RSLANG20 in the background.
The following load types are deleted: screen load (language-independent part, language-dependent part), Screen Painter load and CUA load.
2. Release 4.0B as of Support Package #77:
Execute the report RSLANG20 in the background.
The following load types are deleted: screen load (language-independent part
and language-dependent part), Screen Painter load and CUA load.
3. Release 4.5:
Execute the report RSLANG20 in the background.
The following load types are deleted: screen load (language-independent part, language-dependent part), Screen Painter load and CUA load.
4. Release 4.6:
Execute the report RSLANG20 in the background.
The following load types are deleted: screen load (language-independent part, language-dependent part), Screen Painter load and CUA load.
Change due to Basis Support Package #25(46B), #15(46C) or #6(46D): The language-independent part of the screen load is deleted only when the parameter "FORCE" is set; the buffered entries in the Easy Access Menu are automatically invalidated. You no longer have to perform the postprocessing steps mentioned below.
5. Release 6.x and 7.x:
Execute the report RSLANG20.
You can use the selection screen to select the load types that must be reset. For more information, see the system documentation for this report.
In various database systems (DB2, DB6, MSSQL, INF), you may not be able to successfully delete the screen load. This is corrected with Basis Support Package #9 (SAPKB61009).
If you use application servers with different hardware architectures, refer to Note 497561. Otherwise, you must start RSLANG20 on each application server to completely delete the CUA load. This is corrected with Basis Support Package #14 (SAPKB61014).
Postprocessing
Resetting the CUA buffers and the screen buffers
After the report is completed, you must reset the CUA buffers and the screen buffers on the individual application servers to reload the buffered menu representations and screen representations.
To do this, call transaction SM51 and navigate to each listed application server by double-clicking it. Subsequently, enter the command "/$CUA" in the OK code field for the relevant server to reset the CUA buffer of this server. Then, enter "/$DYN" to empty the screen buffer. For more information, also see Note 26171.
As of Support Package #40 (4. 5B) or Basis Support Package #25 (4.6B), #15 (4.6C) or #6 (4.6D), the CUA buffer is automatically emptied on all application servers.
Resetting the Easy Access Menu buffer
Call the report BMEN_CORRMEN1
As of Basis Support Package #25 (4.6B), #15 (4.6C) or #6 (4. 6D) this is done automatically.
Resetting the buffers of the ALV grid control
This is required for Releases 4.6 and 6.1.
The report BALVBUFDEL resets the buffered data. Before you run the report.
Additional information
In systems with Release 4.6x and kernel 4.6D, patch level lower than 600, problems may occur during the screen generation. Due to these problems, German texts may be displayed on the screen, even if translations are available in the system. If the execution of the report RSLANG20 does not solve this problem, import the most current kernel for the system.