KE28A2 - Maintain KE28 Authorization Objects

SAP Transaction Code - Details

• Transaction Code: KE28A2

  Description: Maintain KE28 Authorization Objects

  Release: S/4HANA only

• • Program: SAPMKEFB

    Screen: 90

    Authorization Object: K_KEB_BER

  • Development Package: KE

    Package Description: Profitability Analysis

    Parent Package: APPL

  • Module/Component: CO-PA

    Description: Profitability Analysis

Smart SAP Assistant

• SAP Tcode: KE28A2 - Maintain KE28 Authorization Objects

  
  Overview:
  KE28A2 is a transaction code used in SAP to maintain authorization objects in the KE28 authorization object class. This transaction code is used to create, change, and delete authorization objects in the KE28 authorization object class. 
  
  Functionality:
  The KE28A2 transaction code allows users to maintain authorization objects in the KE28 authorization object class. This includes creating new authorization objects, changing existing authorization objects, and deleting authorization objects. The KE28A2 transaction code also allows users to assign values to the authorization objects, such as user groups or roles. 
  
  Step-by-step How to Use:
  1. Enter the KE28A2 transaction code into the SAP command field. 
  2. Select the “Create” option to create a new authorization object in the KE28 authorization object class. 
  3. Enter the name of the new authorization object and select “Save”. 
  4. Select the “Change” option to change an existing authorization object in the KE28 authorization object class. 
  5. Enter the name of the existing authorization object and select “Save”. 
  6. Select the “Delete” option to delete an existing authorization object in the KE28 authorization object class. 
  7. Enter the name of the existing authorization object and select “Save”. 
  8. Assign values to the authorization objects, such as user groups or roles, by selecting “Assign Values” from the menu bar and entering the appropriate values for each field. 
  9. Select “Save” when finished assigning values to save your changes. 
  
  Other Recommendations:
  It is recommended that users familiarize themselves with SAP security concepts before using this transaction code, as it is important to understand how security works in SAP before making changes to security settings. Additionally, it is recommended that users test any changes made with this transaction code in a non-production environment before deploying them into production systems, as this will help ensure that any changes made are valid and do not cause any unexpected issues or errors in production systems.