Show TOC

Function documentationInput Manager Locate this document in the navigation structure

 

This function receives the incoming payment files and payment transaction messages and converts the data relevant for payment transactions to the internal metaformat. After conversion, the Input Manager transfers this data to the relevant components in Payment Engine for processing. The Input Manager can handle payment and recall data.

The Input Manager stores all incoming data in the File Handler database and merges this data into the respective outbound messages.

Integration

The Input Manager is integrated in the File Handler component. It is connected upstream to an external feeder system and downstream to the Payment Processing component. For more information, see Payment Processing (FS-PE-POP). Payment transaction messages received by Payment Engine are converted to the internal metaformat for clearing and settlement. For more information, see Routing Control (FS-PE-RP) and Clearing Processing (FS-PE-CP).

Prerequisites

  • You have made the settings in Customizing for Payment Engine, by choosing   File Handler   Basic Settings  .

  • You have made the settings for external references in Customizing for Payment Engine, by choosing   File Handler   Tools  .

    Note Note

    External references from the feeder system are used to identify payment orders, payment items, recalls, and other payment information from an external system.

    End of the note.
  • You have made the settings for exception handling in Customizing for Payment Engine, by choosing   File Handler   File Handler Exception Handling  .

Features

Based on the available formats, media, and channels, you specify the converters that are to convert the payment or recall data into the business objects used. During the file import and the conversion of the data to the internal metaformat, the Input Manager enriches the business objects created with additional information that is needed for processing in Payment Engine. This includes data such as the posting date and system identification.

Upload of Payment Transaction Data

Various incoming channels are connected to the Input Manager by means of interfaces. The Input Manager provides a batch interface for low-value or non-time-critical mass payment orders received from the feeder systems as payment transaction files. The batch interface does not provide any response to the sending application about the status of the order; it sends only a technical recognition response when the order is received in Payment Engine. The system processes these files in batch. Batch channels can also be message-based channels that send asynchronous messages with payment orders. In addition to batch processing, you can also upload payment transaction data manually.

The Input Manager can also generate recall objects. Using the appropriate converter ID, for example, using the SWIFT MT192 converter, you can import a recall. For more information about the functions available for recalls, see Recall Management.

Conversion of Incoming Payment Transaction Data

For payment processing, the data received is converted into business objects Object List (OL), Payment Order (PO), Payment Item (PI), and Remittance (RM). For recall processing, the data received is converted into business object Recall (RE).

All related business objects of a payment order are mutually referenced (OL, PO, PI, and RM).

The system determines whether to process data immediately or later based on the planned processing date defined in the payment order.

  • If no planned processing date is defined, processing takes place immediately.

  • If the planned processing date is earlier than or the same as the reconciliation date, processing takes place immediately.

  • If the planned processing date is later than the reconciliation date, the system waits until the dates match before processing takes place.

Payment Engine supports conversion of the following inbound message types to the internal metaformat:

  • SWIFT MT 102+

  • SWIFT MT 103/103+

  • SWIFT MT 192 (recall)

  • SEPA (inbound XML)

Activities

  • To upload payment data from the feeder systems to Payment Engine, on the SAP Easy Access screen choose   Payment Engine   File Handler   Import File (Expert)   (transaction /PE1/FH_IPM_EXPERT).

    Note Note

    You can also use transactions /PE1/POLLER and /PE1/PO_EXPERT. For more information, see Import Data (Expert).

    End of the note.
  • To display data stored in the File Handler database during processing, on the SAP Easy Access screen choose   Payment Engine   File Handler   Display File Handler Database   (transaction /PE1/FH_SHOW_DB). For more information, see Display File Handler Database.

More Information

File Handler (FS-PE-FH)

Output Manager

File Handler Database

For more information about the XML converter, see XML Converter and SAP Note 1559115.