This function reads the processed payment data and converts the internal metaformat into the external target format. It also transfers message-based payment transaction data to the relevant outgoing channels.
The Output Manager is integrated in the File Handler component. It is connected downstream to an external forwarding system and upstream to the Clearing Processing component.
The outbound data is based on the transaction data created during clearing and settlement. For more information, see Routing Control (FS-PE-RP) and Clearing Processing (FS-PE-CP).
You have made the settings in Customizing for Payment Engine, by choosing
.You have defined the format converters to convert the internal payment order information of the business objects to an external format based on the available formats, media, and channels of the forwarding systems. You do this in Customizing for Payment Engine, by choosing
:SWIFT Format Converter
SEPA Format Converter
Process Integration Format Converter
You have made the settings for exception handling in Customizing for Payment Engine, by choosing
.If required, you have made the settings to enrich output payment information, in Customizing for Payment Engine by choosing
.You can enrich the output file generated by the Output Manager with the following:
Format, medium, and channel
Payment order type
Order account number
Value date of the payment item
Posting date of the order
Date of the offset value clearing for banks
Note
For separate provisions of cover, this is the processing date of the covering order. Otherwise, it is the posting date of the clearing item for the order.
Internal order reference
Clearing area
A processed payment transaction to be transferred from Payment Engine is generated and enriched on the basis of the processed data. The format converters create the specific target format of the outgoing payment data.
Payment Engine supports the following outbound message types (for conversion from the internal metaformat):
SWIFT MT 202
SWIFT MT 103+
SEPA credit transfers (SCT)
SEPA direct debits (SDD)
Errors that occur during the outbound conversion are processed in exception handling. The responses depend on the exception-handling settings you specify in Customizing. An error message is attached to the affected business object, a payment order, or payment items, and is written to the application log. For more information about exception handling, see Exception Control (FS-PE-EH).
The Output Manager merges the information from the incoming payment data that is stored in the File Handler database and calls the relevant forwarding system, such as a file manager or middleware. It then transfers message-based payment orders or payment files to the relevant outgoing channels.
You can bulk payment files and request agent outputs such as CAMT messages into one file (with an optional header), which enables you to restrict the number of files transferred on one day.
Example
You can bulk files for transfer to the Euro Banking Association (EBA). The corresponding EBA XML formats are stored in transaction /PE1/XSD for debits and credits.
To execute processing for outgoing payment orders, on the SAP Easy Access screen, choose
(transaction /PE1/POLLER).To display original payment order data that is stored in the File Handler database, on the SAP Easy Access screen, choose
(transaction /PE1/PO_EXPERT).To bulk outgoing payment files, make the required settings in Customizing for Payment Engine (FS-PE), by choosing
. Next, choose from the SAP Easy Access screen.You can set up bulking for payment orders on the screen for routes and clearing agreements. From the SAP Easy Access screen, choose
.Note
To set up bulking with request agents on the SAP Easy Access screen, choose
.For more information about bulking, see the report documentation.
For more information about the bulk assignment of request agents, see Request Agent and Entering Master Data for Bulk Assignment of Request Agent.