How to use /EACC/CONFIGS - Journal Configurations

SAP Transaction Code - Details

• Transaction Code: /EACC/CONFIGS

  Description: Journal Configurations

  Release: S/4HANA and ECC 6

• • Program: /EACC/JOURNAL_CONFIGS

    Screen: 1000

    Authorization Object:

  • Development Package: /EACC/ABSTRACT_JOURNAL

    Package Description: Abstract Journal in e-Accounting

    Parent Package: FINB_ACCOUNTING_ENGINE

  • Module/Component: FIN-BAC-AE

    Description: Accounting Engine

Smart SAP Assistant

• SAP Tcode: /EACC/CONFIGS - Journal Configurations

  
  Overview: 
  The SAP transaction code /EACC/CONFIGS is used to configure the journal entries in the SAP system. It allows users to set up and maintain the journal entries for their company. This transaction code is part of the Financial Accounting (FI) module. 
  
  Functionality: 
  The /EACC/CONFIGS transaction code allows users to configure the journal entries in the SAP system. This includes setting up and maintaining the journal entries for their company, such as setting up the document types, field status groups, and other related settings. It also allows users to view and edit existing journal entries, as well as create new ones. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code /EACC/CONFIGS in the command field. 
  2. Select the “Create” button to create a new journal entry configuration. 
  3. Enter the required information such as document type, field status group, and other related settings. 
  4. Select “Save” to save your changes. 
  5. To view or edit existing journal entries, select “Display” or “Change” from the menu bar. 
  6. To delete an existing journal entry configuration, select “Delete” from the menu bar. 
  7. Select “Save” to save your changes and 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 or creating new configurations. Additionally, it is important to ensure that all changes are properly tested before they are implemented in a production environment.