Solution : https://service.sap.com/sap/support/notes/1127555 (SAP Service marketplace login required)
Summary :
When generating SEPA files using PMW, despite the file headers indicating "UTF-16" encoding, the actual file is in UTF-8 due to Unicode activation in the system. To address this mismatch, implement the classic BAdi DMEE_XML_BADI_01 using transaction SE18 with filter values SEPA_CT and SEPA_DD. Additional implementation steps involve creating this implementation in SE18, naming it DMEE_XML_BADID_01, and assigning it to the BFIBL_PAYM package. Ensure the implementation is activated. Furthermore, apply SAP Notes 1136607, 1121260, and 1144841 to manage encoding issues and regenerate the SEPA file to reflect these changes.
Key words :
byte order marks, sepa file generated, sepa_dd filter values, call transaction se18, implementation short text, dmee_xml_badi_01 classic badi, transaction se18, filter values, classic badi, sepa formats
Related Notes :
| 1439975 | BCM: Excessive CRLF in payment files |
| 1401975 | DMEE format for SEPA Direct Debit - Version EPC 3.3 |
| 1305012 | DMEE format for SEPA credit transfer - version EPC 3.2 |
| 1280375 | BNK: Settings for payment medium workbench |
| 1144841 | SEPA file is incorrect |
| 1090321 | DMEE format for SEPA direct debit |
| 1062489 | DMEE format for SEPA credit transfers |