KE18 - Display planning authorization obj.

SAP Transaction Code - Details

• Transaction Code: KE18

  Description: Display planning authorization obj.

  Release: S/4HANA and ECC 6

• • Program: SAPMKEFB

    Screen: 90

    Authorization Object: K_KEPL_BER

  • Development Package: KE

    Package Description: Profitability Analysis

    Parent Package: APPL

  • Module/Component: CO-PA

    Description: Profitability Analysis

Smart SAP Assistant

• SAP Tcode: KE18 - Display planning authorization obj.

  
  Overview:
  The SAP transaction code KE18 is used to display the planning authorization objects in the system. This code is used to view the authorization objects that are used to control the access of users to certain planning functions. 
  
  Functionality: 
  The KE18 transaction code allows users to view the authorization objects that are used to control access to certain planning functions. This includes viewing the authorization objects for planning functions such as creating, changing, and deleting planning objects. It also allows users to view the authorization objects for other planning functions such as creating, changing, and deleting planning profiles. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code KE18 in the command field. 
  2. The system will display a list of all the authorization objects that are used for planning functions. 
  3. Select an authorization object from the list and click on “Display” button. 
  4. The system will display all the details related to the selected authorization object. 
  5. To view more details about a particular authorization object, click on “Details” button. 
  6. The system will display all the details related to the selected authorization object including its description, fields, and values. 
  7. To exit from this transaction code, click on “Back” button or press F3 key on your keyboard. 
  
  Other Recommendations: 
  It is recommended that users should be familiar with the different authorization objects before using this transaction code as it can be difficult to understand all the details related to each authorization object without prior knowledge of them. Additionally, it is important to note that this transaction code can only be used by users with appropriate authorizations as it can be used to view sensitive information related to planning functions in the system.