Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction...

26
Purpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships between the particular transaction and its authorization objects. It is possible to add or subtract the checks performed in the transaction by changing the appropriate flag. The addition (check or check/maintain) flag of an authority-check only works if SAP had provided the authorization object as standard in the calling program. Do not expect the system to perform an authority- check automatically when an object is added in the list of other objects for a particular transaction code because the calling program will have no knowledge of these objects. The subtraction (or no check) of an authority-check is possible to all transaction and all objects except HR and BASIS related authorization objects. The benefit of transaction SU24 occurs when transactions are added or deleted from Role Groups using the Profile Generator. When deleting transaction the Profile Generator will remove all authorization values that were needed for that transaction. When new transactions are added, the Profile Generator will add all authorization values needed to run the transaction(s). The addition or removal of authorization values is based upon values entered in SU24.

Transcript of Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction...

Page 1: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

Purpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships between the particular transaction and its authorization objects. It is possible to add or subtract the checks performed in the transaction by changing the appropriate flag.

The addition (check or check/maintain) flag of an authority-check only works if SAP had provided the authorization object as standard in the calling program. Do not expect the system to perform an authority-check automatically when an object is added in the list of other objects for a particular transaction code because the calling program will have no knowledge of these objects. The subtraction (or no check) of an authority-check is possible to all transaction and all objects except HR and BASIS related authorization objects.

The benefit of transaction SU24 occurs when transactions are added or deleted from Role Groups using the Profile Generator. When deleting transaction the Profile Generator will remove all authorization values that were needed for that transaction. When new transactions are added, the Profile Generator will add all authorization values needed to run the transaction(s). The addition or removal of authorization values is based upon values entered in SU24.

Page 2: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

Section A. Check/Maintain Authorization ValuesThis section will explain the steps to maintain an existing authorization object for a TCODE.

1. Log in into SAP

2. Type SU24 in the command field and hit enter

Page 3: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

3. Maintain Assignment of Authorization Objects to Transactions Screen will be displayed.

4. Provide the Transaction code in the Transaction Code field in the Define Interval for Transaction code section.

5. Click Execute Button

Page 4: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

6. Transaction List Screen Will be displayed

7. To Maintain an Authorization Object Click Check Indicator(Pencil Icon)

Page 5: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

Select the TCODE and click on Check Indicator

8. A popup window “Prompt for work bench request” will be displayed for a transport request.

Page 6: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

9. Click on New Request Icon to create a new transport request for the Authorization Object maintenance. Create Request Screen will be displayed

10. Enter Short Description in The “Short description field”

Page 7: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

11. Click Save to Start the Changes, Prompt for Work Bench Requests Screen will be displayed with New Transport Request ID

12. Click “Continue” Button to Proceed

Page 8: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

13. Authorization object maintenance screen will be displayed with the list of authorization objects which are already assigned to the Tcode.

14. In order to make an authorization object to be check maintained change check flag to CM as shown in the picture

15. Click SAVE.

Page 9: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

IF USER JUST WANTS TO CHANGE THE INDICATOR THEN THE PROCESS STOPS HERE. IF USER WANT TO DO ANY CHANGES FURTHER THEN THE CHECK INDICATOR SHOULD BE IN “CM”

Page 10: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

16. If User want to change Authorization Values then the Check should be at CM (Check Maintain). User Clicks on “Field Values” Button to ADD/DELETE/CHANGE Auth Values

17. Change Field values for authorization object Screen will be displayed with the Authorization Object and related Fields.

Page 11: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

18. To edit(Add/delete/update) the fields Click on Pen Icon displayed next to Authorization Field. “Define Values “ Screen Will be displayed

Authorization Object

Fields

Page 12: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

19. Select/Deselect or enter Appropriate values(As requested by customer) in the “Define Values” Screen and Click Save

Page 13: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

Follow Steps 17- 19 for maintaining values for all other Authorization Fields.

20. Click Save and then Exit out of the screen.

Save Button

Page 14: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

Section B. Addition of Authorization Object to a TCODE This Section will provide the details of adding an authorization object to a TCODE.

1. Login to SAP

2. Type SU24 in the Command field and Click Enter

Page 15: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

3. Maintain Assignment of Authorization Objects to Transactions Screen will be displayed. Click on Execute button

4. Transaction List Screen will be displayed. , Select a Record and Click on “Check Indicator “ Button.

Page 16: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

4. Prompt for work bench Request Screen will be displayed.

5. Select Create New Request Button , Create Request Screen will be displayed.

Page 17: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

6. Enter Short Description in the “Short Description field and click Save Button.

7. Prompt for Workbench Request screen will be displayed , Click on Continue(enter) button to proceed

Save Button

Short Description Field

Continue Button

Page 18: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

8. “Change Check Indicator for TCODE” Screen will be displayed with Check indicators for all Authorization Groups.

9. Click on Auth Obj(Insert) Button to Add New Authorization Group.

Auth Obj(Insert) button

Page 19: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

10. Add authorization Object for Tcode button will be displayed.

11. Enter the Authorization Object to be added to the TCODE in the Authorization Obj field. And Click Enter

12. The Authorization Object is added successfully to the Tcode , as shown in the “Change Check indicator for TCODE” screen. Click Save button.

13. Maintain the Authorization Values as shown in the Section A, Steps 16-20.

Save

Page 20: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

Section C. Delete Authorization Object Linked to a TCODEThis Section will provide the details of deleting an existing authorization object from a TCODE.

1. Refer to Section B and Execute Steps 1 thru 92. Go to Screen “change Check Indicator for TCODE” Screen

3. Select the Authorization Object, To – Be Deleted.

4. Select “Authorization Objs“ button from the main menu.

Page 21: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

5. Click Delete from the Dropdown menu. “Object Delete” Message box will be displayed .

Page 22: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships

6. Click Continue to proceed and delete the Authorization Object linked to Tcode .

7. Authorization Object is deleted from the “Change Check Indicator for TCODE” screen.

8. Click Save button to save the changes.

Page 23: Purpose: Transaction SU24 maintains the USOBT_C and USOBX ...  · Web viewPurpose: Transaction SU24 maintains the USOBT_C and USOBX_C tables. These tables hold the relationships