M806 - Message Types (Invoice Verification)

SAP Transaction Code - Details

• Transaction Code: M806

  Description: Message Types (Invoice Verification)

  Release: S/4HANA and ECC 6

• • Program:

    Screen: 0

    Authorization Object:

  • Development Package: MR0C

    Package Description: Customizing R/3 Invoice Verification

    Parent Package: APPL

  • Module/Component: MM-IV-GF

    Description: General Functions

Smart SAP Assistant

• SAP Tcode: M806 - Message Types (Invoice Verification)

  
  Overview:
  M806 is a transaction code used in SAP to manage message types for invoice verification. It is used to create, change, and display message types for invoice verification. 
  
  Functionality: 
  M806 allows users to create, change, and display message types for invoice verification. This includes setting up the message type, assigning it to a document type, and assigning it to a message class. It also allows users to define the number range for the message type and assign it to an output type. 
  
  Step-by-step How to Use: 
  1. Enter M806 in the command field. 
  2. Select “Create” from the menu bar. 
  3. Enter the name of the message type you want to create. 
  4. Assign the message type to a document type and a message class. 
  5. Define the number range for the message type and assign it to an output type. 
  6. Save your changes. 
  7. To change or display an existing message type, enter M806 in the command field and select “Change” or “Display” from the menu bar. 
  8. Enter the name of the existing message type you want to change or display and make your changes or view your information as needed. 
  9. Save your changes or exit out of the transaction code when finished viewing information. 
  
  Other Recommendations: 
  It is important to note that M806 is only used for invoice verification message types and cannot be used for other types of messages such as purchase orders or sales orders. Additionally, users should be aware that changes made in M806 will affect all documents associated with that message type, so caution should be taken when making any changes in this transaction code.