Ir al contenido principal

Traduccion elemento de datos

Transfer ABAP Text Translations using SAP Transport Request with SLXT

ABAP developers can execute SAP transaction code SLXT to transfer data element text translations into a transport request. In this programming tutorial, I want to show how ABAP developers can use SLXT transaction screen to collect translation changes for a sample data element object and put automatically the translations into a specified transport request.
Let's create a sample data element.
I have already created one named Z_TEXT80 and now I will create another data element using SE11 tcode as follows:
Logon to SAP GUI
Launch SE11 transaction
Select option "Data Type" and type the name of the new data element DDIC object. For the sake of this ABAP tutorial, I used Z_TEXT120
create ABAP data element using SAP SE11 transaction
Press Create button for the data element definition screen. Choose the object type as "Data Element".
ABAP DDIC Object Type as Data Element
Press Continue or Enter
On Data Element definition screen, provide a short description and type TEXT120 as the domain of this data element.
ABAP data element definition
Switch to Field Label tab.
You see there are 4 text fields that are used automatically where the data element is used or displayed for example on an ALV display.
Provide some text for each of the 4 field labels. We will create translations of these text in the following steps. Then place the text translations into a transport request using SLXT tcode.
ABAP data element field labels for text translation
Save and activate the data element.
Now get out of the data element definition screen to SE11 and re-enter into the new data element definition with Display button.
Go to translation screen.
ABAP programmers can follow menu options: Goto > Translation
translation screen for ABAP data element text on SE11
Choose your target language here. This is the language that you are translating default definitions into.
I choose German "DE" as target language.
And the original language was EN. I created this data element in EN.
target language for text translation
Press Enter or Continue for next screen.
In the next screen, ABAP programmers can provide translations for text elements or fields labels of the data element ABAP DDIC object.
As seen in below screenshot, I have already type some German text as translations of its originals in EN.
Sorry for the translation, just assume them as sample text for this tutorial :)
ABAP data element text translation using SE11 tcode
Save entries and exit from SE11.
To transfer text translation we have made using a transport request, first we need to create it.
So launch SE09 for example and create a workbench request.
SAP workbench transport request for text translation transfer
In following steps we will use this transport request so keep its number.
Now launch SLXT transaction code (SE63 Translation Export)
First, choose Target Language by using language selection displayed with F4 on target language text field.
I choose deDE for German
In Transport Request section, clear "Create New Request" checkbox since we have already created our transport request.
When you clear the checkbox tick, screen will change slighly.
Now mark "Grant Non-SLXT Requests" option.
This mark will enable "Transport Request" textfield. Now on that field enter our transport request number or use search help to select it.
In Time Period section, you can limit your text translations according to their creation date.
For example, I am interested in to transport only the translations I have made today.
So in "Processing Date" I choose today
Filter section provides further limitations for the ABAP programmer to select related text translations.
I will only enter my user name as "Object Processor" so I will transfer only the text translations done by me.
That is enough for me generally. Here is the final SLXT selection screen before I execute the report.
SE63 Translation Export program SLXT tcode screen
Now ABAP developers can execute the program using F8
The SE63 Translation Export program or SLXT transaction executes and displays the summary as result of the execution.
This is what I get after I execute SLXT with previous select-options applied.
SAP text translation export results into transport request
Please look at the results section. You will see there are two recorded objects.
One of them is the one we have done together following the steps in this tutorial.
The other one is the data element I have created before.
Let's check our transport request how these text translations are seen in the TR.
translations for data element in transport request

Fuente:



Comentarios

Publicar un comentario

Entradas más populares de este blog

A to Z of OLE Excel in ABAP 7.4

  SAP users, both business and end users always need to download the output of a report to spreadsheet and do their analytics.   The standard excel output from a report is very simple process but it is old fashioned and the spreadsheet looks quite boring.  There is no default formatting and the users have to do all the hard work of changing the fonts, coloring the texts, marking the borders etc. Updated 16th Aug 2019  –  If you are working in non-ABAP 7.4 (below), there is complete reference program for you too. Go to the end of this article.  Thank you  Legxis  ( LeonievonK ) for the share. I acknowledge, whatever I mentioned above can be achieved in many ways programmatically. We can do it in the old traditional ABAP way but  providing multiple tabs in the spreadsheet and formatting is quite tricky with non  OLE  method. OLE = Object Linking and Embedding The high level agenda of this article is to be the  G.O.A.T.  (please google it if you do not know the full form)  of OLE Excel Gu
Publicar un comentario
Leer más
How to add custom field in Additional B Tab for SAP Sales Order In this article we want to explain step by step how to add custom field in SAP Sales Order transaction VA01/VA02/VA03. This time Mr ABAPGurus will give the tutorial of enhancement to add custom field in SAP Sales order. In this sample we will add new custom field for comments and customer satisfaction, this data will save into separate table from SAP Standard table ( VBAK / VBAP ). SAP provided us with ADDITIONAL TAB in the sales order transaction ( VA01/VA02/VA03 ) which allow customer to add custom fields.  T he different between ADDITIONAL A and ADDITIONAL B is the ADDITIONAL A for field which already predefine in Sales Order Header ( VBAK ) fields and ADDITIONAL B is for field that freely define. This sample we will use ADDITIONAL B because we will store data from customer satisfaction into Z database table. 1. Create one Z table using SE11 SAP Transaction code. 2.Using SE38 Transaction code and ope
Publicar un comentario
Leer más

VOFM

Creating VOFM custom routine, functionality same as SAP standard routine 103 with Additional Functionality 1.    Introduction 1.1   Document Purpose 1.2    This is the document helps you to create custom routine for sales order for below specific requirement: Functional description: In case of sale order with the SD document category ‘K’ or ‘L’ or ‘H’ related to an invoice, we need to fill the fixed value date (VBKD_VALDT) with the billing reference date (VBRK_FKDAT). For example: Invoice 90001111, the billing date is 22.07.2013 If we create a sale order related to this invoice, we want the fixed value date equal to the billing reference date. As per the requirement: Sap standard routine ‘103’ triggers whenever sales order is being created with reference. Sap standard routine is configured in VOFM transaction as: Sap standard routine ‘103’ has the functionality of copying the billing document header data and billing document line item data into the
Publicar un comentario
Leer más