Reputation: 9
Does anybody know how SAP and other ERP companies deal with localization issues such as Import values? To give a specific example: If I am trying to translate the message: "Value has to be either 'Y' (Yes) or 'N' (No)", we are running into a problem here when translating it to German, since the values Y or N are hardcoded in the source code. Now I don't know how this issue would be handled in SAP, Netsuite, Epicor, Microsoft Dynamics Ax. Do they go all the way to change their source code every time they hit an issue like this or something similar, for every language?
I hope I made myself clear, since I am not a programmer at all ...
Upvotes: 0
Views: 118
Reputation: 27845
How do you ask the question?
Normally you don't enter an answer, you use Screens/Popups with Buttons. An example with function module POPUP_TO_DECIDE_WITH_MESSAGE:
So it does not matter, what you write on the button. The technical result of pushing a button is the same for each language.
I used in similar situations
(Y)es or (N)o <- English
(J)a oder (N)ein <- German
(O)ui ou (N)on <- French
(S)i ?? <- Spanish/Italian
and I test with:
IF answer CA 'YyJjOo'.
* Yes branch
ELSEIF answer ca 'Nn'.
* No-Branch
ELSE.
WRITE 'Please repeat answer'(001).
ENDIF.
CA
means 'contains any' and checks if a letter is used. So I can check for different languages and the usage of small letters or capitals.
Up to now it worked with the languages I need.
If a language would have a 'n' for yes, then you may combine your test with SY-LANGU
.
IF ( SY-LANGU = 'XX' and answer CA 'Nn').
...
Upvotes: 0
Reputation: 1776
I expect they leave the value in place and just translate the meaning. So instead of
'Y'(Yes) or 'N'(No)
It would be
'Y'(Ja) or 'N'(Nein)
Upvotes: 1