Show TOC

Object documentationCorrespondence Type

 

Correspondence types group correspondence of the same type and they are assigned to an application area.

 

Correspondence types define which data can be stored in the correspondence container for creating correspondence. The correspondence output run accesses this data. Bank statements, dunning notices, and invoices are examples of correspondence types.

Structure

A correspondence type saves the following data:

  • Application area

    Each correspondence type is assigned to an application area.

  • Application indicator of the application area

    The application indicator is used to select the function modules of the Business Transaction Events (BTE) for the creation and output of correspondence. These function modules are specific to one correspondence type and are made available by the application. In addition, the application indicator is used to select function modules created by the application to define the events of the correspondence tool. If no application indicator was specified, the application indicator of Contract Accounts Receivable and Payable (FI-CA) is used.

  • Event for creation and output

    An event can be defined as:

    • An event of the event concept in Contract Accounts Receivable and Payable (FI-CA)

    • Business Transaction Event

    • Business Add-In

      Note Note

      Do not use this concept for new implementations. To improve performance, you can partially migrate classic BAdIs. A complete migration is only possible if you use the interface IF_FKK_CORR_OUTPUT_REQUEST for the definition of the method for output when you create the BAdI in the BAdI interface. After the complete migration, you have to adapt the definition of the correspondence type.

      End of the note.

    • New Business Add-In (in Enhancement Framework)

    Depending on the event concept used, the application sets the time of creation and output:

    • Events for creation and output in Contract Accounts Receivable and Payable

    • Business Transaction Events for creation and output

    • Name of the definition of the classic BAdI and name of the BAdI methods for creation and output

    • Name of the definition of the new BAdI

  • Archive structure that defines the long archive ID for creating the online index of the ArchiveLink in the ArchiveLink Document Finder

SAP provides correspondence types. They are predefined in the system and you cannot change them. In addition to the correspondence types delivered by SAP, you can define your own installation-specific correspondence types.

You make settings for correspondence types in SAP Customizing under Start of the navigation path Cross-Application Components Next navigation step General Application Functions Next navigation step Correspondence Next navigation step Define Correspondence Types End of the navigation path or in Customizing for each application component.

For information about the correspondence types an application makes available, see the documentation of the application. For information on the application components that use the correspondence tool and on the naming conventions for creating correspondence types, see SAP Note 684657.

The following correspondence types are assigned to the application area 0 Correspondence Tool (Test):

  • 9991 Test correspondence with BTE

  • 9992 Test correspondence with BadI

  • 9993 Test correspondence with BAdI in Enhancement Framework

  • 9994 Test correspondence with BTE and logging interface

  • 9995 Test correspondence (0) with BAdI in EFW WD

Correspondence type 9996 Test Correspondence (0BAI) with BAdI in EFW is assigned to the application area 0BAI Correspondence Tool (Test, BAdI).

Integration

SAP delivers the events with a default implementation. The application calls up the creation event directly when it creates correspondence requests. The correspondence tool processes the output event when it outputs the correspondence container.