OT81 - Process Repetitive Codes

SAP Transaction Code - Details

• Transaction Code: OT81

  Description: Process Repetitive Codes

  Release: S/4HANA and ECC 6

  Menu Path:

  • Accounting > Financial Accounting > Banks > Master Data > Repetitive Codes
  • Accounting > Financial Supply Chain Management > Treasury and Risk Management > Basic Functions > Master Data > House Banks > Process Repetitive Codes

• • Program: FIBL_RPCODE_MAINTAIN

    Screen: 100

    Authorization Object:

  • Development Package: FIBL_RPCODE

    Package Description: Repetitive Codes

    Parent Package: APPL

  • Module/Component: FI-BL-PT

    Description: Payment Transactions

Smart SAP Assistant

• SAP Tcode: OT81 - Process Repetitive Codes

  
  Overview:
  SAP transaction code OT81 is used to process repetitive codes in the SAP system. It is a part of the SAP Controlling (CO) module and is used to manage and monitor the costs associated with production orders. 
  
  Functionality: 
  OT81 allows users to create, change, and delete repetitive codes. It also allows users to assign cost elements to the repetitive codes, as well as assign cost centers and other controlling objects. Additionally, it allows users to view the cost elements assigned to the repetitive codes and view the cost center assignments. 
  
  Step-by-step How to Use: 
  1. Enter transaction code OT81 in the command field. 
  2. Select “Create” from the menu bar. 
  3. Enter a name for the repetitive code in the “Repetitive Code” field. 
  4. Enter a description for the repetitive code in the “Description” field. 
  5. Assign a cost element to the repetitive code by selecting it from the “Cost Element” drop-down menu. 
  6. Assign a cost center to the repetitive code by selecting it from the “Cost Center” drop-down menu. 
  7. Select “Save” from the menu bar to save your changes. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with all of the features of OT81 before using it, as it can be complex and difficult to use without prior knowledge of its functions and features. Additionally, users should ensure that all changes made are properly saved before exiting out of OT81, as any unsaved changes will be lost when exiting out of the transaction code.