Skip to Content
Product Information

Payment Formats in SAP

 

Following information is obsolete. You can find the latest information about Payment Formats here.

In SAP we are simplifying your communication with banks using SAP S/4HANA and SAP S/4HANA Cloud by bringing you solutions regarding Payment Formats. It is my pleasure to introduce you to the new Payment Formats Blog. In this blog, We will be posting articles about the functionality of payment formats and tools associated with them. I’d like to be introducing newly delivered formats as well as enhancements and improvements of the tools used for their creations and modifications. This blog is not a replacement of the documentation, it is more like its extension. Articles will be about new functionality, which we think may be interesting and could help you with your communication with banks. I will post new articles on a regular basis, so you can always look forward to new content. The blog focuses on describing the work of teams developing new payment formats (outgoing and incoming) for S/4HANA and SAP S/4HANA Cloud for tools DMEE, DMEEX, and Fiori Map Payment Format Data. Check out all of the articles posted regarding Payment Formats and their tools.

General articles

  • (New) Instruction Key Mapping to Payment Media File
  • CUP, CIG and MGO codes in Italy
  • Assign External Transaction to Payment Symbols (Czech Republic and Slovakia)
  • Structured Format for Field :86: in MT940 Bank Statement
  • Source of Information for Field in structures FPAYH-FPAYHX-FPAYP
  • Unique End-to-End Reference (UETR) Reporting
  • (Useful) Converting DMEE formats into DMEEX and Manage Payment Formats
  • The difference between DMEEX, DMEE and Manage Payment Formats
  • The integration of SEPA_CT and SEPA_DD into CGI_XML_CT/CGI_XML

Outgoing Formats

Payment Medium Formats

SAP S/4HANA Cloud
  1. Create, Copy, Delete & Release in Map Payment Format Data
  2. Create, Copy & Delete Payment Medium Format
  3. Linking Payment Medium Format to a Payment Method
  4. Create Selection Variants for Payment Medium Formats
  • How to export custom field (e-mail) in the payment file
SAP S/4HANA
  • An Overview of the Payment Process in SAP S/4HANA

Map Payment Format Data

SAP S/4HANA Cloud
  • (New) Version Management for Map Payment Format Data and Map Treasury Correspondence Format Data
  • Releasing Format Mappings
  • (Useful) Map Payment Format Data – Video Guide
  • Calculations in Manage Payment Formats
  • SAP S/4HANA Cloud 1811 – Map Payment Format Data
  • SAP S/4HANA Cloud 1808 – Manage Payment Formats
  • SAP S/4HANA Cloud 1805 – Manage Payment Formats
  • SAP S/4HANA Cloud 1802 – Manage Payment Formats

DMEEX

SAP S/4HANA

Requires SAP S/4HANA 1709 release or newer

  • Mass Synchronization in DMEEX
  • Calculations in DMEEX
  • SAP S/4HANA 1809 – DMEEX

Incoming Formats

  • Excel Import Feature – Manage Bank Statements 

Don’t hesitate to share your thoughts, ideas or questions regarding Payment Formats in the comment section below. We will do our best to answer them all swiftly. Any suggestions regarding what should the next topic be about are very welcome.

/
5 Comments
You must be Logged on to comment or reply to a post.
  • Will DMEEX fix some shortcomings (imho) of the classic DMEE approach?

    • automatic and full version management ( get a complete history overview of all changes and option to go back to an old tree)
    • dynamic conditions (ex. like exit function module exist for mapping)
    • empty element/node/parent node behaviour: skipped in processing or remove at the end via xslt taking into account performance
    • Hi Jeroen,

      thank you for reading our blog.

      To answer your questions

      Since the 1809 release of DMEEX in SAP S/4HANA, there is a semi-automatic version management feature in the DMEEX. A DMEEX tree version is backed up automatically in the following situations:

      • when you import an XML file with the tree definition
      • when you synchronize your tree with the parent newer version

      However, the user can generate multiple versions of the DMEEX tree at any time himself, compare them or return to them at any time.

      We do not plan to track all changes that are related to the transport request.

      As far as the dynamic conditions, the idea of the DMEEX in the future is to be a completely ABAP-free tool. We are investigating possibilities that will make conditions (and also calculations) much easier to define and understand.

      Can you describe the situation in which you would use a dynamic condition?

      Concerning the Empty node behavior – could you please describe your issue in more detail? The empty tags in the generated XML are in many formats removed via post-processing function that encapsulates the XSLT transformation.

      If you have performance issues, please create an incident.

  •  

    Hi Jakub Djablik

    thanks for the information, we have done the required payment  format  configuration steps for vendor bank payment details.

    here we are facing the issue to send the above generated data  (XML or File) to middleware(CPI).

    we have followed the below steps

    config your solution->Map payment  format data  for US->US_ACH_DD(US format)

    Regards

    Anil