Authorization group will work as customizing object
[authorization] [authorization code] [http authorization] [sole authori]
Related:
- DB2-z/OS: Essential authorization for problem analyzisSymptom A problem on component BC-DB-DB2 was reported. Which authorizations...
- Authorization errors in Java components after upgradeSymptom After the upgrade of your system, you get an...
- Authorization objects are listed in SU24 – no proposalSymptom In the transaction su22 ‘Maintain the Assignment of Authorization...
- 401 Authorization Issue with Web Dispatcher MonitorSymptom You received “401 Authorization required” when trying to logon...
- Authorization objects are listed in SU24 – no proposalSymptom In the transaction su22 ‘Maintain the Assignment of Authorization...
- General procedure for S_TCODE authorization default valuesSymptom Within the authorization administration using the Profile Generator, the...
- Reports with authorization groups in jobsSymptom When you schedule a report (that has been assigned...
- No authorization to log on as a trusted systemSymptom After creating a trusted relationship via transaction SMT1 the...
Symptom
Authorization group is created in workbench request.
Other terms
Authorization group, Workbench, Customization, Request, SOBJ, V_BRG_54, Object, CUST, SYST, Category, View, SE54.
Reason and Prerequisites
Any authorization group that is created from transaction SE54 is saved in workbench request. So, same authorization group is not visible in different clients and hence can not be used.
Wrong property was set for view V_BRG_54, which is responsible for authorization groups.
Solution
Kindly perform the below steps:
1. Goto transaction SOBJ
2. Click on Display
3. Click on position and write V_BRG_54 in Object
4. Once it appears, double click on Object V_BRG_54
5. In “Object Header Data”: Details, goto change mode and change category to CUST from SYST
6. Save it
For WebAS 640:
- Apply Support Package 25
For WebAS 700:
- Apply Support Package 20
For WebAS 701:
- Apply Support Package 05
For WebAS 702:
- Apply Support Package 02
For WebAS 710:
- Apply Support Package 09
For WebAS 711:
- Apply Support Package 04