ABAP Text Translations using SLXT

Ahmet Acar
4 min readMay 20, 2024

ABAP developers have the capability to utilize the SAP transaction code SLXT for transferring text translations of data elements into a transport request. In this programming tutorial, I aim to demonstrate how ABAP developers can utilize the SLXT transaction screen to gather translation modifications for a sample data element object and automatically insert the translations into a specified transport request.

To begin with, to translate, first navigate to the data element by entering SE11 and selecting “Translation” from the “Goto” option in the menu above.

SE11: Goto->Translation

You may proceed by selecting the language you want to translate into. In this example, I will demonstrate translating from Turkish(TR) to English(EN).

Target Language

On this screen, you will see the text that has not yet been translated, indicated in red.

Translation Screen — Red

When you type the English translation and press enter, the text will turn yellow this time.

Translation Screen — Yellow

When you press the marked button, the translation you’ve written will be saved, and it will turn green.

Translation Screen — Green

Now we need to create a workbench request from SE01. The reason is that we need a request to transport the translation we made. Let’s make a note of the number of the empty workbench request we create, as we will need it later in the SLXT.

Workbench Request

Here, you’re seeing the screen you’ll encounter when you first open SE63. We will make some changes on this screen. Now I’ll tell you about those changes.

SE63 — Translation Export

We start by unchecking the checkbox in Create New Request, then the screen refreshes. The reason for this is that we have already created a request a few steps earlier, and to provide the request number we created in the Transport Request field, we also check the checkbox in Grant Non-SLXT Requests. Then, a field appears where we can enter the request number. We write down the request number in this field.

In this example, since I performed the transactions today, I’m entering today’s date in the Processing Date field under the Time Period. You can also perform a faster search by providing the date range of the day you did or if you’re not sure, or you can leave it blank if you wish.

Then, I write my own username in the Filter section and run the program.

SE63

When we run it, we encounter a summary screen. Here, it shows that it found my request and added the translation I made to my request.

SE63 Execute

Later, I go and check my request for verification. I use SE01, while you can use SE09 or SE10.

Request

Successfully implemented, now ready to be moved to the QA system.

Thank you for reading. Stay tuned!

What do you guys think? I love to know your thoughts. Kindly like, share or comment below.

Ahmet Acar.

--

--

Ahmet Acar

SAP ABAP Developer, Computer Engineer, Amateur Basketball Player.