Activating the Translation Object Detective

1. Log onto the system and client that contains the cross-client and client-specific objects for which the report must run.
2. Call transaction SE38.
3. Enter RS_LXE_FILL_TECH_LANG in the Program field.
4. Choose Execute.

The Fill Technical Language (1Q) with Translation Object Information screen appears.

5. At the top of the screen, select the translation object types that you want the report to fill with translation object information.

• If you want the report to run for all ABAP short text and/or SE61 long text object types, leave the default value * in both fields. The advantage of this default setting is that the report runs for all object types, which maximizes the benefits of the translation object detective. The disadvantage of this default setting is that the report takes longer to complete, because it needs to process every object type in the system.
• If you only want the report to run for specific object types, use the input help to select the object types that you require. For example, if you want to restrict the report to texts that appear on the user interface, use the input help for the Object Types (ABAP Short Texts) and Object Types (SE61 Long Texts) fields to select all of the object types that belong to object group A5 User Interface Texts. The advantage of restricting the report to specific object types is that the report takes less time to complete, because it does not need to process every object type in the system. The disadvantage of restricting the report to specific object types is that it does not maximize the benefits of the translation object detective, because the object type and technical name of translation objects skipped by the report will not appear on the screen when you log onto the system with technical language key 1Q.

6. Maintain the parameters in the Mode group box.

• Periodic (Initial + Delta)

  If you select this radio button and schedule the report to run periodically, the initial run evaluates all of the objects that you selected for the report. All subsequent delta runs are restricted to transport requests that were created or modified since the last report run.

  The time stamp is refreshed every time that the report starts to run. If you choose Reset Date, an initial run takes place the next time that the report is executed.

• Single Run

  If you select this radio button, you can execute the report just once without the report preparing itself for subsequent delta runs.

• Transport/Task

  If you select this radio button, you can restrict the report to a transport request or task. Use the input help to select the transport request or task that you require.

• Translation Object List

  If you select this radio button, you can restrict the report to objects in an object list. To do this, you must first create an object list in transaction LXE_MASTER. For more information, see Object Lists.

7. Maintain the parameters in the Filters group box.

• Client-specific Objects Only

  If you need to "translate" texts in client-specific objects in several different clients, then you must execute RS_LXE_FILL_TECH_LANG in each of them. If you have already executed the report in one client, select this checkbox to restrict it to client-specific objects in all other clients so that you do not waste time running the report more than once for the same cross-client objects.

• Exclude Translation Exceptions

  If you select this checkbox, the report ignores all of the translation objects that are listed in tables LXE_PEXPT (which you are not allowed to maintain) and LXE_LEXPT. There are two ways for you to add translation objects to table LXE_LEXPT:

  • You can maintain the table directly in transaction SE16. For more information, see Locking Individual Objects for Translation.
  • You can choose Define Exception, specify a transport object in the Enter Transport Object dialog box, and choose Enter. This creates one or more entries in table LXE_LEXPT with the note RS_LXE_FILL_TECH_LANG, which clearly indicates why the entries were added to the table.
• Exclude Local Objects
• Exclude Tables with Local Data

• Exclude MIME Descriptions

  You are advised to select this checkbox, because MIME description objects can cause the report to cancel.

8. Maintain the parameters in the Abbreviate Critical Object Types in Text Fields of Insufficient Length group box.

• Activate

  If you select this checkbox, the report abbreviates the object type description of the critical object types listed under Mappings.

• Field Length Threshold (max)

  If you select the Activate checkbox, the value in this field determines the field length as of which object type descriptions are abbreviated.

Example

The full name of a translation object is DTEL SPRAS, which consists of 10 characters. The report needs to write this information to a field that is only 6 characters long.

• If the abbreviate function is inactive, the report writes DTEL>S to the field. For information on the meaning of the > sign in this context, see the notes below.
• If the abbreviate function is active with a threshold of 8 characters, the report reduces the number of characters needed for the object type description to just one, which means there are still enough characters for the full object name. It therefore writes 1SPRAS to the field instead of DTEL>S.

Under Mappings, you can see that 1 stands for object type DTEL, 2 for object type RPT1, 3 for RPT4, etc. If you activate the abbreviate critical object types function, remember to make this legend available to the users who intend to log onto the system with technical language key 1Q after you have finished activating it.

9. If you are running the report in an ABAP backend system for SAP Fiori, you are advised to select the Add System ID checkbox in the Options group box. On the SAP Fiori interface, you can then see the object type and technical name of the translation object to which a text is mapped and in addition the ID of the ABAP backend system in which the object is stored. If you are not running the report in an ABAP backend system for SAP Fiori, do not select the Add System ID checkbox.
10. Execute the report in the background, or schedule the report to run periodically (such as once a week) if you know that new objects will become available in the system in future.
    Note

    • Technical language key 1Q is installed just like any other standard language.
    • If you display the spool for report RS_LXE_FILL_TECH_LANG after it has finished running, you may discover a list of error messages that are frequently triggered by incorrectly defined text tables. Please ignore them. As long as the report did not cancel, everything is fine.
    • If the message Selected language not completely installed appears in a dialog box when you log onto a system with technical language key 1Q, you can simply ignore it.
    • Some translation objects under technical language key 1Q include the wildcard *. The wildcard represents blank characters. Copy the technical name of the translation object (including the wildcard) to the Object Name field in transaction SE63, and use the input help function to replace the wildcard with the blank characters that complete the translation object's technical name.
    • Some translation objects under technical language key 1Q have the greater than symbol > at the 5th position. This means that the string has been cut off because of length restrictions in the corresponding screen element. Copy the technical name of the translation object to the Object Name field in transaction SE63, add the wildcard * to the end of the string, and use the input help function to replace the wildcard with the characters that complete the translation object's technical name.
    • If you log onto a system with technical language key 1Q to conduct tests, you run the risk of executing functions that (for example) trigger automated email dispatches or book goods and services in the technical language. Make sure that you do not save or change anything in the system in the technical language. If you must save or change data for tracing purposes, make sure that the settings are reset or removed or deleted afterwards.
    • Some transactions, such as SE16 and SE92, enable you to display texts in all available languages. If a text is available under technical language key 1Q, then it is also displayed.
    • The report only works for the ABAP object types that are listed when you use the input help function for the Object Types (ABAP Short Texts) and Object Types (SE61 Long Texts) fields at the top of the selection screen.
    • There are certain objects for which "translation" into technical language key 1Q is not (or not always) possible. For example:
      • Generated objects
      • Objects with a missing TADIR entry
      • Dynamic texts
      • Texts that do not exist in the original language of the object
      • Text tables with special features or an incorrect definition such as T006A, CNV_ORG_TAB_TEXT, CNV_00001_STATUS, and TBZ3X that can cause the system to dump when they are saved
      • Text tables for which unique secondary indexes exist