How to use GJNR_OHKEY - Maintain Overhead Key Number Range

SAP Transaction Code - Details

• Transaction Code: GJNR_OHKEY

  Description: Maintain Overhead Key Number Range

  Release: S/4HANA only

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: GJVA

    Package Description:

    Parent Package: JVA_JV

  • Module/Component: CA-JVA

    Description: Joint Venture und Production Sharing Accounting

Smart SAP Assistant

• SAP Tcode: GJNR_OHKEY - Maintain Overhead Key Number Range

  
  Overview: 
  GJNR_OHKEY is a SAP transaction code used to maintain the overhead key number range. This transaction code is used to define the range of numbers that can be used for overhead keys. It also allows users to assign a description to each overhead key. 
  
  Functionality: 
  The GJNR_OHKEY transaction code allows users to maintain the overhead key number range. This includes defining the range of numbers that can be used for overhead keys, as well as assigning a description to each overhead key. The transaction code also allows users to view and edit existing overhead keys, as well as create new ones. 
  
  Step-by-step How to Use: 
  1. Enter the GJNR_OHKEY transaction code in the command field. 
  2. Select the “Create” button to create a new overhead key. 
  3. Enter the desired number range and description for the new overhead key. 
  4. Select the “Save” button to save the new overhead key. 
  5. To view or edit an existing overhead key, select the “Display” button and enter the desired number range in the command field. 
  6. To delete an existing overhead key, select the “Delete” button and enter the desired number range in the command field. 
  7. Select the “Save” button to save any changes made to an existing overhead key or delete an existing one. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with SAP’s security settings before using this transaction code, as it can be used to make changes to sensitive data. Additionally, users should ensure that they have sufficient authorization before making any changes or creating new overhead keys.