How to use DMEE1 - DMEE: Format Tree Maintenance Tool

SAP Transaction Code - Details

• Transaction Code: DMEE1

  Description: DMEE: Format Tree Maintenance Tool

  Release: S/4HANA and ECC 6

• • Program: SAPMDMEE_ABA

    Screen: 200

    Authorization Object:

  • Development Package: ID-DMEEA

    Package Description: INTDEV: ABA services of Data Medium Exchange Engine

    Parent Package: ABA_GEN_GLO

  • Module/Component: CA-GTF-CSC

    Description: Country-Specific Objects

Smart SAP Assistant

• SAP Tcode: DMEE1 - DMEE: Format Tree Maintenance Tool

  
  Overview:
  The SAP transaction code DMEE1 is used to maintain the format tree in the SAP system. It is used to define the structure of payment files that are generated from the SAP system. The DMEE (Data Medium Exchange Engine) is a tool that enables the exchange of data between different systems. 
  
  Functionality: 
  The DMEE1 transaction code allows users to create, edit, and delete payment file formats. It also allows users to define the structure of payment files, such as the order of fields, field lengths, and field types. Additionally, it can be used to define the rules for generating payment files, such as which fields should be included in the file and how they should be formatted. 
  
  Step-by-step How to Use: 
  1. Enter the transaction code DMEE1 in the command field. 
  2. Select a format tree from the list of available trees or create a new one. 
  3. Select a node from the tree and edit its properties, such as its name, type, length, and description. 
  4. Add new nodes to the tree by selecting “New Node” from the menu bar. 
  5. Define rules for generating payment files by selecting “Rules” from the menu bar. 
  6. Save your changes by selecting “Save” from the menu bar. 
  7. Generate a payment file by selecting “Generate File” from the menu bar. 
  
  Other Recommendations: 
  It is recommended that users familiarize themselves with the DMEE1 transaction code before attempting to use it in order to ensure that they are able to use it correctly and efficiently. Additionally, users should always save their changes after making any modifications to ensure that their changes are not lost if an error occurs or if they need to exit out of the transaction code unexpectedly.