Collective Output Documents
Use
The SSR collective output function allows you to group documents of different types such as movement documents, billing documents, financial documents, or other collective output documents into a single SAP document for output in hard copy or electronic format.
For example, you can use the SSR collective output function to produce a service station partner daily claim output document consisting of:
Credit card service station partner invoices
Fleet card service station partner invoices
Credit card service station partner credit memos
Fleet card service station partner credit memos
It is also possible to group daily collective output documents into a single periodic collective output document , that is, to produce hierarchical output documents. You can therefore also produce a service station partner monthly statement consisting of the individual daily claim output documents.
Integration
The SSR collective output document contains:
A document header, providing a unique document number for both internal and external reference
One or more document items representing the source (application) documents included in the print document
The SSR collective output document uses the standard SAP output determination function to produce output in either printed or electronic format.
Prerequisites
In order to produce a collective output document, you must define:
Data capture, that is, what source (application) documents are to be used, and under what circumstances to trigger the production of an SAP collective output document.
Output production (configuration of the output procedure and output condition types), that is, what does the output of a specific document type look like, in what format should it be produced, and where should it be sent.
In the Customizing for
Industry Solutions Oil & Gas (Downstream)
, choose
SSR
Settlement and Invoicing
Collective printing
Print grouping parameters
to define the following regarding data capture:
The types of collective output document that are to be produced (print type groups), such as a daily statement or monthly statement.
The application documents that are to be used as source documents for each collective output document type, such as billing documents or output documents.
The attributes that are to be used to select the source documents, such as invoice date, location number, or bill-to party.
Note
You can also define a business add-in (BAdI) to determine when an application document should not be included.
You do this in the Customizing for
Industry Solutions Oil & Gas (Downstream)
by choosing
SSR
Settlement and Invoicing
Collective printing
Maintain Business Add-Ins for Collective Printing
Business Add-in to Skip Update to Print Index Table
.
In the Customizing for
Industry Solutions Oil & Gas (Downstream)
, choose
SSR
Settlement and Invoicing
Collective printing
Output determination for Collective Printing
to define the following regarding output production:
The output types and access sequences.
The output procedure.
The output procedure to the print type group.
If you want to use the location-based collective print document creation process, the process execution BAdI and prerequisite processes must be defined using the SSR process control tool. For more information, see Process Control .
Features
Collective output documents can either be produced individually, using the create print document transaction (O3RAPR1), or en masse using the location-based group output processing transaction (O3RAPL1) as an SSR process controlled process.
An SSR collective output document that is associated with invoices displayed in the daily claim report (O3RI02) will be identified as a sub-tree level under the invoice document to which it belongs. It is possible to drill down from the daily claim report to the underlying output document by double-clicking on the output document.