Question:
I'm trying to change a role and I get an error S#606 Text maintenance only possible with logon in original language DE of role. I can change the text on other roles quite hapily but not on this one. Any ideas? Cheers Q.
Answer:
Could be that the role you are modifying was a SAP original role and the language was DE (German) when it was created. What's the name of the security role?
Moggie
Answer:
I created the role completely from new. I didnt copy anything. I changed it a day or two ago and it was fine. Other roles are fine and dont give me any earache about Text Maintenance and the German language. I blame the fact they got knocked out of the world cup by the Italians.
Answer:
this one pops up a lot - the search will reveal more but from memory try running AGR_ACTIVITY_GROUPS_TRANSLATE
Answer:
belay that last one - Z_ROLE_SET_MASTERLANG
Answer:
Sorry I'm being thick. How do you mean run Z_ROLE_SET_MASTERLANG? I've been to SE38 but there is no program Z_ROLE_SET_MASTERLANG etc? Where anf how do I run it? If it begins with a Z isnt it something user configured? I've seen a SAP note about it but didnt think it was entirely apprpriate - why would it only effect certain roles and roles that previously I could change. I'm informed by Basis that no ptaches nad chnges have gone on. Weird.
Answer:
Hi
Try OSS note 854311 - it sounds like you're having the same problem we had some time ago
Good luck
Answer:
SE63: Translation of role texts fails Help
SAP Note Number Note Language DEENJA Display Versions 51213
Print SSCR Download
Text Header Data Release Correction Instructions Support Packages >>
Symptom
An attempt to translate the description of a role in Transaction SE63 is rejected with an error message.
Other terms
Role maintenance S#606
Reason and Prerequisites
This problem is caused by a program error.
After you implement Note 725040, no original language is saved when you create the role of Profile Generator to be edited. However, an original language is a prerequisite for translating with SE63.
Solution
Use SNOTE to implement both correction instructions, or import the second Support Package.
Manual activity
If you use the correction instructions, you need to create message 606 in message class S# with the following short text:
Text maintenance only possible when you log on in the original language &1 of the role
Select the "Self-explanatory" option in the message.
Explanations
After you import the two sets of corrections, the current logon language is always saved as the original language when you create a role in Transaction PFCG. When you copy a role, the current logon language is also used as the original language of the copy, regardless of the original language of the copy template. Changes to the short text ("Description" input field) and the long text on the "Description" tab can then only be carried out when you log on in the original language. The logon language is irrelevant for all other maintenance functions (menu, authorizations, and so on). These functions are always available.
However, note that when you add additional authorizations, their texts are always stored in the current logon language. If role maintenance is carried out in different logon languages, authorization texts may appear in several languages within the same role. These texts cannot be translated.
Additional solution
The original language always applies for the entire lifetime of the role. There is therefore no standard procedure for changing it. If you really need to make a change, use report Z_ROLE_SET_MASTERLANG attached to this note.
If you use SE38 to implement the change, maintain the following attributes:
Title: Changing the original language of roles
Type: Executable program
Status: Live customer program
Application: Basis (System)
The selection screen of the report contains the input fields AGR_NAME and ORIG_LAN. Enter the roles, the languages of which you want to change, in field AGR_NAME. There is an input help with multiple selection available for this. In field ORIG_LAN, specify the new original language of the selected roles.
Answer:
As stated below See OSS note 854311. Error caused by SP update. Fixes the problem.