Community
Technology Blog Posts by Members
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

Maintain Popup Text in Different Languages Using SE63 (Program Example)

Guru_Sah79
Explorer
4 weeks ago
482

Introduction
In this SCN blog, we will learn how to maintain popup text in different languages using transaction SE63. The same method can be applied to translate text for programs, function groups, and other development objects.
In this blog, we will specifically demonstrate the translation process for a program, converting text from English to German language.

Step 1: Create Program in SE38
Open transaction SE38 and create a program with the following code:

 

REPORT ZRP_POPUP_DEMO.
DATA: lv_answer TYPE c.
CALL FUNCTION 'POPUP_TO_CONFIRM'
  EXPORTING
    titlebar              = TEXT-000
    text_question         = TEXT-001
    text_button_1         = TEXT-002
    text_button_2         = TEXT-003
    default_button        = '1'
  IMPORTING
    answer                = lv_answer.
IF lv_answer = '1'.
  WRITE: TEXT-004.
ELSE.
  WRITE: TEXT-005.
ENDIF.

 

Step 2: Maintain Text Elements
Maintain text elements for all hard-coded values to enable easy translation and improve program maintainability.

Guru_Sah79_0-1775475942935.pngOutput:

Guru_Sah79_1-1775476000561.pngStep 3: Translate Text Using SE63
Navigate to transaction SE63 to translate the popup text into German language.

Guru_Sah79_3-1775476118455.pngClick on Transport Object
Transport Object option in SE63 is used to translate all texts belonging to a transport request. It helps translate program text, CDS labels, message text, and UI text together from source language to target language.

Guru_Sah79_4-1775476157902.png

Enter:

  • Transport Request number OR
  • Object type (PROG, TABL, DTEL, etc.)
  • Object name

 Select:

  • Source Language (EN)
  • Target Language (DE)

Guru_Sah79_6-1775476252785.pngTransport Object

R3TR PROG ZRP_GS_POPUP

Meaning:

  • R3TR → Repository object
  • PROG → Program object type
  • ZRP_POPUP_DEMO → Custom ABAP Program name

So here, translation is being done for ABAP Program texts.
Source Language
enUS – English
Language in which original text is maintained.

Target Language
deDE – German
Language into which text will be translated.
Click on Edit

Guru_Sah79_7-1775476335583.png

Maintain all the text in german language

Guru_Sah79_8-1775476371814.png

Log in to SAP GUI in German Language:

Guru_Sah79_11-1775476578313.png

Now go to the SE38 transaction, enter the program name ZRP_POPUP_DEMO, and execute it by clicking on F8 or execute button.

Guru_Sah79_12-1775476655938.pngThe popup text is displayed in German, indicating that it has been translated. Such texts can be maintained in multiple languages using transaction SE63.

Conclusion:
In this blog, we explored how to maintain and translate popup text into different languages using transaction SE63. By converting hard-coded text into translatable text elements, we enabled language-dependent behavior in ABAP programs. We also demonstrated how to translate program text from English to German, ensuring that the popup content is displayed according to the user’s logon language.
This approach is not limited to programs—it can be applied to function groups, classes, and other development objects as well. Using SE63 effectively helps improve usability and supports multilingual environments, making applications more flexible and user-friendly across different regions.

2 Comments