The payment medium format controls how payment orders and debit memo orders to the bank are created. The specifications (published by the banks or the central banking committees) of the formats serve as the basis for the definition of payment medium formats. To simplify communication with banks using SAP S/4HANA, we are bringing you a solution regarding payment formats in FI-CA.
The ability to define these formats in the system is particularly important as there is no worldwide or regional standard format. In some cases, no country standard exists, and the file must comply with bank-specific standards. Covering such numerous and varied local format requirements is difficult in standard software, but DMEEX allows you to define your specific format yourself.
Customizing of Payment Medium Formats
The initiative we run is to align communication structure between the customer and the bank defined with the payment format in FI-CA (transaction FQP3) and the one already defined with the payment format in SAP S/4HANA Finance (transaction OBPM1). Thanks to that, you can produce and influence the format layout for the payment file for both FI and FI-CA, which saves you time during the fine-tuning of the format structure.
In the new approach, the data collection is done in FI-CA as it was before. The data is then converted into the FI payment media workbench structures. Thanks to this conversion, the formatting from FI can be reused, saving time and costs.
To see how you can influence the structure of the payment format in practice, visit SAP Help Portal.
Payment Medium Formats available in FI-CA
The list of available payment medium formats can be seen at SAP Help Portal.
In order to provide transparency regarding payment medium formats that are no longer in use, we created an overview with status for each payment medium format: available, not available or obsolete. You can check the availability of the payment medium formats in SAP Note 2943353.
Creating Customer-Specific FI-CA Payment Medium Format based on DMEEX
Although banks will follow the general standards outlined for a specific format, sometimes customers may need to change the mapping rules of the format to align with the bank-specific requirements. Examples of such changes include:
- concatenation of fields to support reconciliation
- the setting of fields from optional to mandatory
- replacing the standard mapping for customer-specific mapping
Currently, not all formats supported in FI are delivered for FI-CA, but you can create a Z-format (customer-specific format) and link it to the standard DMEEX tree delivered for the FI format. This guide describes steps to prepare customer-specific payment medium formats in FI-CA based on the DMEEX tree delivered for the FI format.
This step-by-step guide is taken from SAP Note 2860488, where you can find additional information about customer-specific payment medium formats.
1. Create Format Name
In transaction SM30, open the V_TFK042FS maintenance view and enter a format short name, such as ‘ZPTCGIXML_DD’.
2. Create Payment Medium Format
In the Dialogue Structure tree, choose the Event Modules for Payment Formats sheet and add event function modules and a structure name for format parameters.
In the Dialogue Structure tree, choose the Text Fields for Reference Information screen and make any necessary changes to the number and length of text fields as shown below.
3. Maintain Additional Format Data in Posting Area 1066
Call transaction FQC0 for Posting Area 1066 and maintain the format short name and other additional information for:
- Paying Company Code
- Payment Method
- House Bank
Select the format short name you created as described in step 1. Create Format Short Name.
4. Enhancement Implementation
To use the standard DMEEX tree PT_CGI_XML_DD, implement the ABAP code using an enhancement implementation.
- Call transaction SE38, enter include LFKYXXF01, choose Display, then choose Enhance (Shift-F4).
- Go to Edit → Enhancement Operations → Show Implicit Enhancement.
- Create the enhancement implementation at the end of form ‘EXIT_PAYMEDIUM_DMEE_ADJUST_HDR’. Position the cursor to the last line before command ENDFORM. To create the enhancement implementation, go to Edit → Enhancement Operations → Create Implementation.
Choose the type of enhancement and enter the name of the enhancement implementation, short text and composite enhancement implementation, if needed.
- Edit the enhancement implementation (to do so, you can copy and paste the ABAP code below)
Example ABAP code (can be used to generate SEPA payments using DMEEX tree PT_CGI_XML_DD):
DATA: ls_tfpm042f TYPE tfpm042f. CASE iv_formi. *--- CGI_XML_DD for Portugal ------------------------------------------ WHEN 'Z_PT_CGI_XML_DD'. * Get default DMEEx Tree from FI payment format CALL FUNCTION 'FI_PAYM_FORMAT_READ_PROPERTIES' EXPORTING i_formi = 'PT_CGI_XML_DD' IMPORTING e_tfpm042f = ls_tfpm042f EXCEPTIONS not_found = 1 parameters_invalid = 2 OTHERS = 3. IF sy-subrc = 0. cs_fpayhx-tree_id = ls_tfpm042f-tree_id. ELSE. * DMEE Tree not founf in FI customizing, use Formatname cs_fpayhx-tree_id = ls_tfpm042f-formi. ENDIF. PERFORM paymedium_xx_cgi_adjust_h USING is_payh is_payhx it_fpayp_conv CHANGING cs_fpayh cs_fpayhx. WHEN OTHERS. * format is not supported RETURN. ENDCASE. " iv_formi.
- Activate the enhancement implementation (Ctrl+F3)
List of Customer Enhancements
To adjust file output, you can use customer enhancements (implicit enhancement options) in these subroutines (in program SAPLFKYXX, Function Group FKYXX).
|Position (event)||Subroutine||Values to be adjusted|
|File header (20)||EXIT_PAYMEDIUM_DMEE_ADJUST_HDR||FPAYH, FPAYHX|
|File transaction record (30)||EXIT_PAYMEDIUM_DMEE_ADJUST_ITM||FPAY|
|File transaction record (30)||EXIT_PAYMEDIUM_DMEE_ADJ_ITM2||FPAYP|
We also publish news about Payment Formats on our collective blog Payment Formats in SAP.
Do you have any further comments regarding this topic? Do not hesitate to share them in the comment section below.