Skip to Content
Technical Articles

** TEAM FPM ** – All about Translation and Texts of FPM applications

In the last weeks I was confronted quite often with the topic, how FPM texts are stored and more interesting – how they could be translated at all…

Of course there is a very helpful note available (#1646142, Storage of FPM texts), but nevertheless a kind of “bring it all together explanation” is still missing. This is why I started writing this blog…

So what are the most important points to address?
1) Everybody should know that texts of an FPM application can be stored in 4 different ways:
a) Data element
b) OTR (Online Text Repository), e.g. as OTR-alias in your component configuration ($OTR:<alias>)
c) Text elements of an ABAP OO class (e.g. your feeder class)
d) Configuration of a Web Dynpro Component (e.g. your List UIBB configuration)


2) How can I translate texts of my own created component configuration?
The translation process of texts stored within component configurations starts with transaction SE63. The object type for these texts is “TLGS” (Lockable Logical Objects, Short Texts).
To reach the Standard Translation Environment, navigate within the menu via Translation –> ABAP Objects –> Transport Object.



Remark for texts within customizing of component configurations:

You have 2 options to translate customizing texts:

a) via the Translation Tool for Customizing (only if customizing has already been created!)

b) via SE63 (as described for configuration Texts above but in a slightly different way, read below)

The Translation Tool you reach via WD application wd_admin_configuration, entering the name of the component configuration, then select the customizing link of this configuration and you will get a link displayed on the following screen (“Translation Tool for customizing”) which leads you to the Translation Tool.


Within SE63 you choose “ABAP Objects –> Short Texts”.

Depending on your release follow one of the following two descriptions:

  • There you choose entry “A6” for table entries (TADC Tables, Customizing – maintenance by customers only). From there open the F4 help and find string “WDY_CONF_USERT2”.
  • There you choose entry “00” for tables (TABL Tables (Meta)). Enter Object Name “WDY_CONF_USERT2”.

Enter the appropriate source and target languages and press edit. On the popup enter user scope = “A”. Additionaly you can search directly for the affected configuration ID. Now you get the well known SE63 list for translating texts.

Now you come to the well-known overview screen where you enter the transport entry of your object and source as well as the target language.




Pay attention to the Object Name! It is not only the name of your component configuration… You have to take the name of the object directory entry which you can find either within your transport request or within table TADIR or within se80:






You will recognize that within the object directory entry the configuration name is concatenated with “00” at the very end – copy this string and you can continue with transaction SE63.







After you have entered the transport entry of the object as well as source and target language, press “Edit”.


In the following screen all texts stored within configuration are displayed with their translated text or – if translation has not yet been done – with empty fields.




3) Application Hierarchy Browser
You came to the idea to copy a standard delivered FPM application via the FPM Application Hierarchy Browser and you are wondering, why texts are not translated afterwards.
This issue is known (until 7.31 SP04) and a solution is provided with note #1710822, which provides a report called WDR_CFG_TEXT_COPY. This report copies the text in the missing languages. Please have a deeper look within the given note to get further details how to run this report correctly.
For future releases all texts in all languages will be copied automatically by the FPM Application Hierarchy Browser.


4) Texts stored within GUIBB configurations (e.g. List, Form, Search, …)
Texts within GUIBBs, e.g. the text of an input field label, can be provided by several instances:
a) Component Configuration

b) Feeder Class (text has been defined within method GET_DEFINITION)
c) Data element (of the respective feeder class field)

A certain sequence exists how those texts are applied when it has been maintained in all of the above entities. At the very end the text stored within the component configuration wins, then feeder class and afterwards the data element. So if nothing else has been stored the text will come out of the data element.


5) What to do when the translation exists but it is not applied at runtime?
If this issue comes up mainly GUIBBs are affected where the source is a data element. Just activate the respective data element again and your application is showing the translated text. The root cause of this issue can be found within the language load. For further technical details you can also have a look into note #110910.


If you have checked the existence of all translations successfully and even then the texts are not applied, you have the possibility to invalidate the area CL_WDR_CFG_COMP_SHM_TRANS of the Shared Memory via transaction SHMM. You have to do that on every application server. Use the button “Invalidate” left-hand sided of the delete-button. See also note #1909945 for more information.


6) Last but not least: The FPM provides a Text Tool from NW 7.31 onwards…
To determine which static texts are used within your component configuration or application configuration, you can use report FPM_TEXT_TOOL to find out, which text types are used (e.g. “D” stands for data element, “C” for Configuration, …)




Additionally a direct navigation is possible via double-click to the named entities, like data elements, component configurations, …




Furthermore a very good documentation is included within the report so you can understand every detail presented by the FPM Text Tool.

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

    Thanks for the blog. It was explained very nicely...

    Recently I have created a new variant for an existing custom component configuration ( This existing component configuration was copied from standard one). The problem is when we access existing component configuration in different languages we are able to see translation correctly. But, when we access the new variant, everything appears in English only irrespective of what language we logged in. What do you think is the problem?



    • Hello Sankar,

      thanks for your positive feedback!

      You said that everything appears in English only for the variant you have created on your own. Have you copied this variant from the existing variant? Or have you  created the variant from scratch? In the latter case you have to do translation on your own if needed.

      Best regards,


      • hi,

        we first enhanced the standard component configuration to a Z one  ( basically delegation ). This has a default variant which is standard. For this Z configuration i created another variant by copying the standard variant.  Surprising thing is I see translation for few buttons.

        • Hello Sankara,

          I have just reproduced your described issue as well. Please open up a customer message with a detailed scenario description as well as an example to reproduce the issue.

          It is probably an issue within WD ABAP - we first have to analyse it internally.

          Put the message on the application component and ask them to forward the message directly to FPM.

          Thanks in advance and best regards,


  • Hi Julia, nice blog, really useful.
    I have however a question; what if I enhanced a Component Configuration, for example, by adding a new Main view or buttons? In such a scenario, I added some label (hardcoded, in the sense we cannot use $OTR elements) which DO NOT belong to the original component configuration, but to the enhancement itself.
    I can't find a way to retrieve such label elements in order to translate them... would you help me out on the task ?
    Thanks again for your valuable feedback on the issue.

    • Hello Matteo,

      I tried your procedure from above and struggled also... I have contacted colleagues responsible for enhancement topics and as soon as I have an answer/solution for you, I will come back to you within this blog with further information.

      Stay tuned!

      Best regards,


      • Hello Matteo,

        my colleagues have solved this issue with note 1845777 (still in German as it has not yet been translated). Please implement it as soon as it has been released and the object should be then visible also via SE63.

        Best regards,


        • Hi Julia, nice blog!

          I implemented note 1845777. Now via SE63 we can translate texts of our component configurator enhancement.

          Unfortunately if we start FPM application, in any language, enhanced objects texts are displayed in DE language ( original language of enhancement is EN !!!).

          Best Regards,


          • Hello Fulvio,

            thanks again for reporting your observation. I have reproduced this scenario as well internally --> I will inform the responsible colleagues. I will keep you up to date.

            Thanks and regards,


          • Hello Fulvio,

            this issue has been corrected with note #1892526. Please implement it after it has been released and the enhancement texts should be applied.

            Best regards,


  • Hi Julia,

    Can you try to correct the allignment of your blog.

    I am unable to view it properly.

    Everything is left alligned in a very small column.



    • Hello Ashish,

      with Internet Explorer and Chrome it is working properly. Which Browser and version do you use?

      Regards, Julia

  • Very very useful blog post Julia. We are migrating many of our WDAs into Hindi language. While the View item labels, message texts, etc. were translated easily, we were clueless about the FPM configuration elements. This post came very handy.

    However I faced trouble locating the TADC under A6 in SE63 > ABAP Objects > Short Texts. In stead, I fell back to the transport request. A transport request has neatly segregated list of all items of WD, viz. Web Dynpro Application Configuration, Web Dynpro Component Configuration, Web Dynpro Application, Web Dynpro Component, etc. Each of these nodes in the transport request has the full technical name of the object. I double clicked on the names and got the Object types from the Object Directory Entry for that name. Using them in SE63 was then straightforward.

    Lastly, your mention of SHMM was very pertinent. Even after doing all translations, verified through report FPM_TEXT_TOOL, the FPM part was still shown non-translated. The invalidation done through SHMM instantly fixed the issue.

    Many thanks!

  • Thanks a lot Julia for this Great Job.

    Do you have any idea how can we translate all others texts like for instance : Title of a chip/of the landing page etc...

    thanks a lot.

  • Thanks for the blog.

    You could even improve it by adding a note for how to get the translations in the right transport request.

    Also export/import of translations could be described somewhere nicely.

    There is a on board functionaliyty to export most of the translatable objects to excel and to reimport it. that would open the door to hand a sheet out directly to professional translators.(But the usage is so hidden and seemingly complicated, that at least i have forgotten it after a while and do not use it, if i don't have to.It's a shame, as i am sure there are hundreds of internaly built translation tools to do the same, because you need to hand out a list to a translation office..)

    The integration  of translation support in FPM could be improved.

  • hi Julia,

    is it possible to translate personalisations of a wd component configuration? Changing the language (sap-language=XX) doesn't work and there is no technical object behind it.

    Kind regards, I.

  • Julia,

    Great blog.  I have little experience with FPM so I need a little help.

    I would like to change the text that is used for the title of the Planning Overview for Compensation.  There is code in a componentcontroller method of WD Comp. HRECM00_PLANNING_OVERVIEW that pulls the text for the title:

    title = wd_assist->if_wd_component_assistance~get_text( key = 'E01' )

    I would like to know where text E01 is stored and can it be "customized" so that we can change the title.

    Component Configuration HCM_ECM_PLANNING_OVERVIEW_OIF is defined for WD FPM_OIF_COMPONENT. Application name is the same as the component configuration.

    • Hi Joyce,

      The texts are maintained in assistance classes associated with the WD component. In this case, the assistance class is CL_HRECM00_A_PLANNING_OVERVIEW. You can find it in SE80, when you open the WD component. Within assistance class, navigate to Goto > Text elements.


      • Abhijeet,

        Thanks for the information.

        I used SE24 to view the class and the text elements for the class.  Is there a way to override the text thru the class?  I'm not sure how to go about doing that.  The easiest thing would be to change the E01 text element but I do not want to do a modification.  Is it possible to do enhancements on the text elements?

  • Hi,

    I added a new field in my z component configurator and the field is of type Char100 and has a manual input help attached to it in my z process. However in se63 i cant see the field getting reflected.Infact any new field added now doest show up in Se63.I am accessing SE63 using object directory entry. Currently there are 112 fields in SE63 for my form.Is 112 the maximum number of fields?

    Please help me to resolve the issue of new fields not showing up in SE63.



  • Hello,

    Thanks for you blog, it is very interresting.

    I have followed every steps you mentioned, but the standard buttons are not translated. I mean the Save/Save and Back are in the right language, but for instance in FR language, I modify the Save button text and it is not reflecting.

    Do you have any suggestion ?

    Kind Regards,


  • Hi Julia,


    Thanks a lot for your blog. I have one small question, I want to maintain translation of title in my custom UIBB component. How to do it, please advice.

    I have tried to follow this process which you had mentioned in blog, probably I have missed something.

    Remark for texts within customizing of component configurations:

    Instead of choosing the above path, for translation of texts within customizing you choose “ABAP Objects –> Short Texts”.

    Depending on your release follow one of the following two descriptions:

    • There you choose entry “A6” for table entries (TADC Tables, Customizing – maintenance by customers only). From there open the F4 help and find string “WDY_CONF_USERT2”.
    • There you choose entry “00” for tables (TABL Tables (Meta)). Enter Object Name “WDY_CONF_USERT2”.”



  • Hi Julia,


    at first thanks for the detailed description. With the TA SE63 it works...But, how will be the translation transported to the Quality / productive System?

    Another question how can I find the Translation Tool for customizing?

    And can you please provide the documentation for FPM_TEXT_TOOL. In our SAP System it is not available.

    Thanks and warm regards from Stuttgart