Printing an invoice based on existing correspondence type for journal entries with one customer

When you post journal entries with one customer account per document to create a simple outgoing invoice in SAP S/4HANA Cloud, you might face some issues when trying to print the invoice within Accounts Receivable. 

The good news is that there’s a workaround available to enable you to print the invoice by maintaining the form based on a pre-delivered template. The form template for FI invoice enables you to cover specific cases for invoices in Financials, such as when you have one customer line item per document or use only G/L account line items with revenue accounts. 

Let’s have a look at the steps below for creating a form template for FI invoice based on a pre-delivered template. 

Maintain Form Template 

The first thing you need to do is to get data from correspondence type SAP09. 

To do that, proceed as follows:  

1. Go to the Maintain Form Template app. 
2. In the Pre-delivered Templates section, select the FIN_FO_CORR_INTDOC_ENTRY standard form template from the list and copy it to create a custom template.  
   Enter a name for the new form template. For example, you can use FO_CORR_SAP09_FI_INVOICE. The system creates a custom template named YY1_FO_CORR_SAP09_FI_INVOICE. 
3. Download the template. 
4. Make the required changes in the local template file via Adobe LifeCycle Designer. Information you might consider changing: you might want to include the customer’s name from the customer line item in the header or even define which fields should be displayed in the form.
   You can find an example on how to adapt the layout of the custom form template in the SAP Knowledge Base Article 3312120.
5. Test the form template with an XML data file from some correspondence to check how the information will be displayed with the current setting. 
6. Upload the form template file you’ve changed to the Maintain Form Template app. Make sure the data source remains FDP_FFO_INTDOC_ENT_SRV as defined in the pre-delivered template. 

Assign Form Template 

In your configuration environment, use the search function to open the following activity: Maintain the Assign Form Template. Proceed as follows: 

1. Maintain this configuration activity with the new form template that you created in a previous step. For example, YY1_FO_CORR_SAP09_FI_INVOICE. 
2. Assign this new form template to Application Object Type FFO_CORR_INTDOC and Output Type INTDOC.  

This way this form can be used for the SAP09 Entry View correspondence. 

For more information about the configuration environment, see Configuration Environment of SAP S/4HANA Cloud.

Assign Labels and Company Codes to Correspondence Type Variants 

In your configuration environment, use the search function to open the following activity: Assign Labels and Company Codes to Correspondence Type Variants. Proceed as follows: 

1. Copy the row for variant S09EN and create a new row. For example, you can create a new row with ID Z09IV for the FI invoice.  
2. Rename the new entry to FI Invoice.

Determine Output Parameter 

In the Output Parameter Determination app, proceed as follows: 

1. Edit the rules for internal document in the Form Template determination step.  
2. Add a new row for output type INTDOC and, in the Corr. Identifier column, enter the ID that you created in the previous activity. For example, Z09IV.  
3. In the Form Template column, enter the name of the custom template which you created previously. 

Make sure you don’t change the existing rows for the internal document. The entry view S09EN and ledger view S09LE are still needed to enable the printing of an internal document. 

Done. You’re now ready to print your invoice based on existing correspondence type in SAP S/4HANA Cloud. 

Here’s an example on how this new correspondence type looks like: 

Here’s an example of a simple invoice printout:

For more information about configuring SAP S/4HANA Output Control, see SAP S/4HANA Output Control. 

For more information about the creation of a custom form template based on the internal document, see SAP Knowledge Base Article 3312120.

We hope this blog post helps you. Feel free to leave your questions and comments in the space provided below.

See you next time,

Ailane