An object that converts incoming and outgoing XML-based payment files.
XML converters enable the File Handler to convert incoming files from their external XML format into an internal metaformat used for internal processing of payment orders and payment items and to convert outgoing orders from the internal metaformat to the required external XML format.
The implementation for a specific format is based on the XML schema. Multiple related schemas can share one basic converter implementation, which is an implementation of a filter BAdI. The standard system provides, for example, a converter implementation for the schema PAIN.008.001.02. You can also use this for an extended XML schema PAIN.008.00x.xx with additional tags. The basis mapping is identical, but the schema validation differs. In a BAdI for payment orders, you can add further mappings and checks for the specific formats. The XML format converters derive the XML schema and basic converter implementation.
In the Customizing activity Define Converter Implementation for Format Converter, you can control the XML schema and converter implementation, alternatively you can do so by using the following BAdIs.
Choose
and .The BAdIs use the filter criteria Converter Package. Each converter package can have its own derivation rules. A converter implementation is a filter BAdI implementation for the following BAdIs:
BAdI: Conversion of XML Input for Message Identifier
BAdI: Conversion of XML Output for Message Identifier
There are individual implementations for XML schemas such as PAIN.008 and PACS.003. The interface does not specify the business object, which can be a payment order, recall, or any other object type. Default converter implementations are available for specific formats.
You can either create your own converters for this interface or use special BAdI interfaces for business objects, which are available in the converter implementations provided in the standard system as follows:
Payment Orders
BAdI: Customer Extensions for PO in Input Converters
Recalls
BAdI: Customer Extensions for Recall in Input Converters
You can use these BAdI interfaces to add more attributes to business objects. XML format converters use the following logical paths for directory checks:
Input Manager (IPM)
Logical filename: /PE1/XML_CONVERTER_INPUT_FILE Payment Engine (FS-PE) XML converter input file (directory)
Logical path: /PE1/XML_CONVERTER_INPUT_PATH Payment Engine (FS-PE) XML converter input path
Output Manager (OPM)
Logical filename: /PE1/XML_CONVERTER_OUTPUT_FILE Payment Engine (FS-PE) XML converter output file (directory)
Logical path: /PE1/XML_CONVERTER_OUTPUT_PATH Payment Engine (FS-PE) XML converter output path
XML converters are integrated in the File Handler component in Customizing for Payment Engine (FS-PE).
You can assign XML converters with a converter ID. Choose
For more information, see SAP Note 1559115.