Skip to Content

Translation of Z-Entries in SAP-Standard-Customizing

Hi all,

at the moment we are internally discussing a matter with translation of our own customizing and we are searching for a best practice to handle it. So I’m hoping that someone here has an idea or suggestions how to handle this case. I will start with some preliminary information about our landscape:

Conditions:

  • We have a 3-tier system landscape with DEV, QA and PROD systems.
  • There are already six languages installed
  • Our main language is German
  • We filled up with language English after an installing a language pack, because our customer developments are fully available in German and English
  • Translation workbench is configured

What is our goal?

We want to translate our Z-Entries of the SAP Standard Customizing into all installed languages (e.g. HU)

This means not existing translations should be added and wrong translations should be corrected.

Problem description:

I’ll explain the issue with the table “T003P” in the Package “KAUF” but it occurs on every other text table in the system. Here you can see an example of the texts in the table by using the search help with logon language “EN”

All the order types are copies of the “Standard production order” type which is a standard SAP entry.

The table is included in the package “KAUF” as you can see in the next screenshot.

Now we ran a statistic for Customizing entries evaluated the results in transaction SLLS.

As you can see there are 0 new entries and 2267 for table “KAUF”. These 2267 entries include also all SAP-Standard entries which are already translated by SAP.

As these entries are not included in the proposal pool, they will be shown as “yellow” ones (modified).

If we now tell our translation agency to translate the customizing for collection / package “KAUF” they have also to put hands on every SAP-Standard entry and at least add them to the proposal pool.

But we just need to translate all Z* entries in this table.

Sure, we could tell them to just translate table “T003P” and only Z* keys, but this would not be a good solution for maybe thousands of customizing tables that are required.

And even if we would do it in this way, we can’t name all tables that are relevant for translation. It would be a great effort to determine all relevant table names.

Question:

I hope the problem became clear and someone has a suggestion how to handle this with SAP-Standard tools or maybe there is a 3rd party software solution for this?

pic1.png (13.7 kB)
pic2.png (13.9 kB)
pic3.png (21.9 kB)
pic4.png (29.6 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Dec 19, 2012 at 08:17 AM

    Hello Andreas,

    for  detailed support of your inquiry above we propose to open an OSS message at the SAP support. If you look for 3rd party support please follow this link and choose the SAP Language Service Partners. I hope this helps to solve your request. http://www.sap.com/our-partners/find-a-partner.epx

    Kind regards, Petra Irle

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 25, 2012 at 10:02 AM

    Hello Andreas,

    One way to translate only customizing objects is by creating an object list based on transport requests.

    Objects that are developed, enhanced or changed are collected in a transport requests. If you use transport requests as a criterion for your object lists in the translation workbench, you can restrict the translation-relevant objects to those contained in specific transport requests. Furthermore, you can restrict the search to those requests that have a particular type such as customizing.

    Best regards,

    Shay Oberziger

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Shay,

      we discussed this before, but we are not sure what will happen if a customizing entry was created in e.g. Transport1 and was deleted afterwards in Transport2.

      Also we were unsure if this would be wise, because some of our transports older than 5 years.

      But I think we will give it a try and play around with some sort of scenarios like above.

      @ Former Member: We are already working with a 3rd party support on our request, but there seems no really smart solution for this. Also we discussed it with SAP directly.

      So we started this discussion in order to get more opinions about this question :-)

      Thanks & Regards,

      Andreas