Ir al contenido principal

Traducciones en SAP

Respecto a las traducciones, que SAP las permite, pero no de manera automática, es mas bien artesanal.

La idea está tomada de un Blog en ingles, pero funciona correctamente:

When working on international projects, there is a need to translate new developments done in ABAP. In standard SAP provides SE63 tool, which help executing the translations for many objects at the same time. You can complain it is not intuitive and user friendly, but it if you have many translations to be done you cannot do much about it. After completing the translations in SE63, you need to put the translations in a transport request, as opposite to translation of customizing, the system does not prompt for transport request nor assigns the entries to a transport request when saving in SE63. In most cases you are just about to face new challenges. It is quite often nowadays, that you do not have authorization for transport request creation, as it is managed by central support team using SolMan, or you do not have authorization to SLXT transaction, which is provided in standard SAP to put all the translations done in SE63 into a transport request to be able to import it trough system landscape. When you do many translations, you can spent some time on getting proper authorization or request creation of the transport request with translation by central support team, but if you have just a few additional/new translations to be done, it seems to be too much hustle. In such a case there is a workaround to create the entries in transport task manually, it takes 15 minutes and you’re done 🙂

List of objects translated in SE63

First get the list of translations done in SE63 or in ABAP dictionary or directly ABAP workbench objects. The list is stored on DB table LXE_LOG:

LXE_LOG.JPG

You can select the entries based on you user name or the date and time of translation:

LXE_LOG+sel.JPG

Mapping of translation objects to transport objects

Seems easy and what would you do is to put the entries from LXE_LOG directly to entries in the transport task, however some adjustments are required before doing that. Namely the object type has to be adjusted, as the ones used in transport request are different that stored in the table (strange, but it’s like that). But there is nothing that cannot be done without some analysis of ABAP code. SLXT uses FM LXE_OBJ_CREATE_TRANSPORT_ENTRY to conver the LXE_LOG entries into transport request entries. So actually the work is a piece of cake now.

All you need to do is take the object type from LXE_LOG entry and lookup the proper object type to be used in the transport entry.

Let’s take object type DOMA for a domain from LXE_LOG as example. You go to the FM and find the object type in the big CASE statement:

FM.JPG

You see that for LXE_LOG object type DOMA (domain) the object type DOMD should be used in the transport entry.

Create transport entries for translated objects

So all you need to do now is edit a workbench Development/Correction task and add a new entries to it:

TR.jpg

After putting the key (LANG/DOMD/<object name>) you will get a pop-up to provide the language of the translation (in our case it’s NL). After you provide it once, the language is used as default for all new translation entries you create in the transport request task.


Fuente:

https://blogs.sap.com/2012/07/26/of-how-to-transport-translations-made-in-se63-without-access-to-slxt-or-authorization-for-transport-request-creation/



Etiquetas:

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