Skip to Content

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 a 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 its tools.

 General Articles

Map Payment Format Data SAP S/4HANA Cloud


Requires SAP S/4HANA 1709 OP release or newer


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.


To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Jeroen Verbrugge

    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
    1. Jakub Djablik
      Post author

      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.


Leave a Reply