How to use SI24_13 - KW: Customizing Authorizations

SAP Transaction Code - Details

• Transaction Code: SI24_13

  Description: KW: Customizing Authorizations

  Release: S/4HANA and ECC 6

• • Program: RSIWB_CUST_AUTH_FOR_PROPS

    Screen: 1000

    Authorization Object:

  • Development Package: SIWB

    Package Description:

    Parent Package:

  • Module/Component:

    Description:

Smart SAP Assistant

• SAP Tcode: SI24_13 - KW: Customizing Authorizations

  
  Overview:
  SI24_13 is a SAP transaction code used to customize authorizations in the SAP system. It is used to create, change, and delete authorization objects and assign them to users. This transaction code is part of the Security Audit Log (SAL) and is used to monitor user access to the system. 
  
  Functionality: 
  SI24_13 allows users to customize authorizations in the SAP system. This includes creating, changing, and deleting authorization objects and assigning them to users. It also allows users to view the authorization objects that have been assigned to them. Additionally, it can be used to monitor user access to the system by creating a Security Audit Log (SAL). 
  
  Step-by-step How to Use: 
  1. Enter transaction code SI24_13 in the command field. 
  2. Select the authorization object you want to customize from the list of available objects. 
  3. Create, change, or delete the authorization object as needed. 
  4. Assign the authorization object to a user or group of users as needed. 
  5. Activate the changes by clicking on “Save” or “Activate” button. 
  6. To view the authorization objects that have been assigned to a user, select “User Authorization” from the menu bar and enter the user name in the search field. 
  7. To create a Security Audit Log (SAL), select “Security Audit Log” from the menu bar and enter the required information in the fields provided. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with SAP security concepts before using this transaction code. Additionally, it is important to ensure that all changes made using this transaction code are properly tested before they are activated in order to avoid any potential security risks or other issues that may arise from incorrect configurations.