Key Steps to Make Enhancements to a Payment Medium Workbench File
- by Mary Loughran, Independent Consultant
- Brent Olsen, Sr. Technical Consultant, e5 Solutions Group
- April 4, 2016
Learn how to add key data to the SWIFT (Society for the Worldwide Interbank Telecommunication) MT101 payment file that is not delivered in SAP standard systems using event-based function modules. Discover how dynamic function calls enable you to create country- or bank-specific logic that allows you one MT101 payment file format with an unlimited number of output format possibilities.
Reading this article, you will learn:
- The steps of an efficient payment process
- How to make key enhancements to the payment file contents
- The sequence of function calls in building a payment file
Payment format creation can be event driven based on function modules or an SAP Data Medium Exchange Engine (DMEE) tree.
SAP payments are critical to standard business operations, and the automated reconciliation of payments is key to efficient processing and catching fraudulent payments. When payments are made from an SAP system, a unique identifier to the payment needs to be passed to the bank as the transaction reference with payment. This transaction reference is then passed back to the company in the electronic bank statement, and should be used in the automatic bank reconciliation of payments. This should be done for all payments across banks and countries. The framework mentioned in this article describes where and how changes to the Payment Medium Workbench (PMW) payments can be made.
This article is the third of three that detail enhancing the SAP standard payment processing functionality with custom development. The preceding articles were specific to SAP’s Bank Communication Management module. The enhancement mentioned here is specific to Payment Medium Workbench (PMW) payments and is not dependent on SAP’s Bank Communication Management module.
To add the enhancements mentioned in this article, an ABAP developer is needed. As ABAP code changes are being made, a developer’s key is needed. The ABAP team would normally have a developer’s key.
As mentioned in “SAP Bank Communication Management: What You Need to Know,” the payment methods used for payments routed to SAP Bank Communication Management should be defined as PMW payments. In this article, we assume the format of the payment file is an MT101 file, though the information about events mentioned here applies to other PMW file formats as well. An event is an ABAP function module.
For our example, we add the payment document number in the :21: tag of the MT101 file. The :21: tag in a SWIFT MT101 payment file is the transaction reference. The bank sends the information passed with the payment back to the customer in the electronic bank statement. The document number is then used for electronic bank statement clearing in the SAP system.
The SAP function modules that build the header level, transaction level, and footer or trailer records for an MT101 file are shown in Table 1.
Would you like to see this full item?