Skip to Content

Often we come across the requirement of having the same layout of form for multiple languages.The best way to achieve this is by implementing the translations.

The following are the ways for translation of a original form (EN) to many other languages.

1.Translation available at the form level in SFP txn of the adobe forms.Menu–>Goto–>Translation.

2.Using Standard Texts (SO10)

3.Using Text Modules.(Smartforms)

The best way and easy maintenance in future, I suggest you to go for Textmodules.

These text modules can be created in the original language “EN” and can be converted in to differenet languages using txn SE63 using target language.

This way when you pass the the texmodule and the login language to the fileds of Text created in the Context node i.e.

Text Name — ‘ABC’ (Name of the Text module created)

Textlanguage — Langu. (This langu is the variable which is passed either from interface or from print pgm as import parameter where langu = sy-langu).

Now as you have converted all the text modules in the required languages,when you run the form in that particular login you get the necessary out in that particular language.

As per me this is the best and easiest way to proceed.

The second approach you can opt for is the standard text.(S010).But the probelm here is we need to be careful of insert the standard text in the Transport Request as the creation of standard text explicitly does not ask for TR.This is the only difference apart from that this is equivalent to textmodules.

The last option Translation at form level is not recomended as this needs the form to be developed statically.And when you have a requirement of translating the forms in multiple languages the form takes the changes fine for the first initial time.But when the changes are requested at later point of time to the translated text,we face issues with New text not getting reflected in the latest generated form(Not immediately).

Looking at all the available options,I suggest you to go for textmodules.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Florian Henninger

    But there might be problems left.

    What here is not explained, is that you got a lot of identifier for fields, For example in the infobox and as header of the position table.

    I mean, yes this is a solution which works for longer textes, but not general to develop a whole adobe.

    The same problems we all are facing also in sapscript or smartforms btw.

    But I don’t want to be annoyed, there are solutions out there. But maybe you got one you can show to us.

    Regards

    Florian

    (0) 

Leave a Reply