How to use OKEON - Change Standard Hierarchy

SAP Transaction Code - Details

• Transaction Code: OKEON

  Description: Change Standard Hierarchy

  Release: S/4HANA and ECC 6

  Menu Path:

  • Accounting > Controlling > Cost Center Accounting > Master Data > Standard Hierarchy > Change

• • Program: KEO_START_NF_STDHIERARCHY

    Screen: 1000

    Authorization Object:

  • Development Package: KBAS

    Package Description: Overhead Cost Controlling

    Parent Package: APPL

  • Module/Component: CO-OM

    Description: Overhead Cost Controlling

Smart SAP Assistant

• SAP Tcode: OKEON - Change Standard Hierarchy

  
  Overview:
  The SAP transaction code OKEON is used to change the standard hierarchy in the SAP system. This transaction code is used to maintain the organizational structure of a company, such as the company's departments, divisions, and other organizational units. 
  
  Functionality: 
  The OKEON transaction code allows users to create, modify, and delete standard hierarchies in the SAP system. It also allows users to assign organizational units to a hierarchy and to assign a parent node to an organizational unit. Additionally, it allows users to view and maintain the relationships between different organizational units. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code OKEON in the command field. 
  2. Select the “Create” option from the menu bar. 
  3. Enter a name for the new hierarchy and select “Save”. 
  4. Select the “Change” option from the menu bar. 
  5. Select an organizational unit from the list and assign it to the hierarchy by selecting “Assign”. 
  6. Select a parent node for the organizational unit by selecting “Assign Parent Node”. 
  7. Select “Save” when finished making changes. 
  8. Select “Back” to return to the main menu or “Exit” to exit the transaction code. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with the different options available in this transaction code before making any changes to an existing hierarchy or creating a new one. Additionally, users should always make sure that all changes are saved before exiting the transaction code in order to ensure that all changes are properly applied in the system.