Skip to Content

Wrong English translation of GET BADI about CL_BADI_BASE

Jan 03 at 04:08 PM


avatar image

Hello, (Horst ;-))

The English documentation of the dynamic variant of GET BADI

GET BADI badi TYPE (BAdI name)

tells that "The static type of the reference variable badi must be a superclass for all CL_BADI_BASE BAdI classes."

It's a little bit unclear (although one easily guesses what it means). It should be:

"The static type of the reference variable badi must be CL_BADI_BASE, which is the superclass of all BAdI classes."

What is the best way to ask for ABAP documentation/translation correction?

PS: In German, it's currently: "Der statische Typ der Referenzvariable badi muss die Oberklasse aller BAdI-Klassen CL_BADI_BASE sein."



10 |10000 characters needed characters left characters exceeded

The English is a technically correct translation of the German version, as this also reads like CL_BADI_BASE is a plural. The original could benefit from some commas:

Der statische Typ der Referenzvariable badi muss die Oberklasse aller BAdI-Klassen, CL_BADI_BASE, sein.

Now even Google translates it correctly :-)


I changed the original to "muss die Oberklasse CL_BADI_BASE aller BAdI-Klassen sein" ...


Oh yes, nice!

gvbt0.png (23.6 kB)

The best way might be to just call Horst Keller here. :)

I agree the English text sounds confusing. "Eats shoots and leaves"

Jelena Perfiljeva

Thanks Jelena :)

* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Horst Keller
Jan 03 at 09:35 PM

Recently, I started a project to switch the original language of the ABAP Keyword Documentation from German to English. And in preparation for that, I want to edit/correct the English translation. In fact, such problems appear in all of the around 6000 documents. The main problem is, that the translation was done by many different people (no programmers, of course) over the last 20 years. As one result (apart from all the "normal" errors as above), there is no unique terminology as I have it in German and I can't do simple global replacements. E.g., there are links to glossary terms, where the link text differs from the link target, and so on. After starting (since the texts are still stored in SAPScript, I had to program a correction framework first, involving shadow tables and such), I found that it will take me around 500 days, and that only, if I could do it full-time, what I can't. I'm afraid, I will not be able to do it. And in fact, there's no real pressure. If there would be hundreds of incidents, maybe. But in the moment, I get error messages very rarely. I see all the problems and it drives me nuts, but as long as I'm the only one, well.

Show 7 Share
10 |10000 characters needed characters left characters exceeded

I read only the English documentation, but I think that the overall quality is excellent and is very precise, as needed by the complexity of the language constructs. Personally, I rarely see vague texts, each term of a sentence has a clear meaning (if one spends time to read the explanation of course). I agree about the glossary, in fact I always read quickly the short description and press the "more" link to read the long precise documentation.

So, thank you very much for that, and keep up doing this very good work !


Hmm, maybe if you don't compare it to the original language. My problem is, I'm writing that stuff in German, and because of that, I see what's amiss or wrong in the translation. I don't want to do finger-pointing now.

But in the end it is reassuring that my managers are right to say that the english translation is good enough. But somehow, it is a pity that only some few percent of the readers see the original documentation while 90-plus percent see a translation only.


Outsourced and/or uninformed translation can be hilarious. Stuff like Buchungskreis (Company Code) becomes "Booking circle" :-)


My favorite is "Schnittstellenerbauer" for "Interface Builder" (this time from English to German) ...


High on my list is Anlagenkenner (Asset ID) translated to an Asset Expert.

For non German speakers: A Kennzahl (ID number, literally "know-number") is often abbreviated to Kenner (literally "knower").


Hmm, I would never say "Kenner" but "Kennung". It is true that we have many funny SAP specific German words too, see

Show more comments