Lesson Overview
To print invoices, SAP delivers a form class to assist with invoice design. This lesson demonstrates where you can find this, and how to start the printing process.
Business Example
Print Service Corporation uses form classes delivered by SAP as a data container for invoice design. Printing is done in mass processes.
Invoice Printing

Correspondence is created based on the print workbench (invoice printing /row data interface).
An application form based on the invoice correspondence type is defined for the invoicing process.
You can use all the data from the invoicing document, the billing document, and customer master data to create the invoice.
Correspondence Definition:
- Correspondence: All written output you send to your business partner as well as printed evaluations, reports, statements, and so on.
- Inbound Correspondence: A business partner’s obligation to file a written item without reminder
- Correspondence history: Contains entries for written correspondence and stores requests and receipt of incoming correspondence
- Print workbench: A tool for generating printed correspondence.
SAP delivers the correspondence type 0042 invoice for bill presentment in contract accounts receivable and payable.
You can find the customizing settings for correspondence type 0042 under Financial Accounting → Contract Accounts Receivable and Payable → Basic Functions → Correspondence → Define Correspondence Type.
SAP Customizing Implementation Guide → Financial Accounting → Contract Accounts Receivable and Payable → Basic Functions → Correspondence → Define Correspondence Type → Select Correspondence Type 0042.

The two main events for the correspondence process are in general:
The generation event for the correspondence process and storage of correspondence request at event 2685.
When you create invoicing documents, invoicing in contract accounts receivable and payable creates a correspondence container for event 2685:
For every posted invoicing document, provided that it does not have a print lock.
If an invoicing document is not to be printed, you can put a print lock on it in event 2645 (field PRINTLOCK in the invoicing document header).
For every reversed invoicing document, provided that the reversed document has already been printed.
If the document has not yet been printed, the system deletes the reversed document when the correspondence container is deleted.
Print time for printing correspondence at event 2685 from the correspondence container.
The correspondence data container is a set of tables (technical hint: the main one is DFKKCOH). Each entry in a table represents correspondence that can be sent to a business partner.
Printing is done in a separate step within the correspondence section using the tile Print Correspondence in the SAP Fiori launchpad (Corresponding back-end transaction FPCOPARA)..

You can select any data, such as the contract account or correspondence type.
For each correspondence container, correspondence printing calls one application form and creates one print document with this form. If the actual printout was successful, correspondence printing sets the print date in the correspondence container and in the header of the invoicing document that you want to print.

Simulation of invoice printing:
With the invoicing document, you can also display a simulation of the invoice printing and the invoice preview. However, the print date and customer-defined fields are not updated. You can also simulate the invoice for simulated invoicing documents. You start the process from the display of the invoicing document.

For training purposes, we designed a printed invoice with a billable item list on the second page. This can be done easily, because the form class already delivers single and sum information over the whole billing and invoicing process, starting with the billable item and ending with historical invoices.