Describing Correspondence

Objective

After completing this lesson, you will be able to explain FI-CA correspondence

FI-CA Correspondence

A descriptive document defines Correspondence, Inbound Correspondence, Correspondence History, and Print Workbench. The definitions focus on written business communication and tools for generating printed correspondence.
Options to create correspondence include mass run (invoice, account statement), individual on demand (online check, receipt), and connection with other processes (dunning letter).

SAP delivers a range of correspondence types, such as:

  • Business partner statement: all open items that were posted after the last statement

  • Account information: all items for a certain contract account

You can use the business partner statement in the following cases:

  • If multiple contract accounts exist for a business partner and you only want to use one correspondence to inform the business partner of the status of the account relationship.

  • If multiple contracts exist for one business partner and you only want to use one correspondence to inform the business partner of the status of the customer relationship.

You can use the account information in the following cases:

  • If external auditors want to inform a group of customers about the current status of their customer accounts.

  • If customers need to be informed about the account balance once in each period (requirement in specific countries).

Flowchart titled Correspondence Type 0002 Account Statement outlines control considerations for recipient, events, printing, and other factors related to account correspondence. Sections include questions about additional recipients, simulation, event generation, print events, test and repeat printouts, application areas, periodic correspondence, gaps, suppression of correspondence, and inbound correspondence.

Recipient control is set at the level of correspondence type. For example, you can specify for a given correspondence type that no alternative recipient is allowed.

There are two necessary events associated with a correspondence type:

  • The print event function module is needed to print a correspondence request for a given correspondence type after the correspondence container has been read.
  • The generation event function module is needed to create a correspondence request.

Log in to track your progress & complete quizzes