Skip to Content
Product Information
Author's profile photo Jakub Djablik


This blog covers the latest features and enhancements in the DMEEX (Extended Data Medium Exchange Engine) transaction arriving in the SAP S/4HANA 1809 On-Premise release and being now available across all SAP S/4HANA OnPremise releases for DMEEX. 

Mass Synchronization

In DMEEX, you can create hierarchical tree dependency by copying a format tree as a child tree. The relation can have several levels.

After creating a custom child tree (or multiple) under a country-specific tree, the user is able to pass customization from the parent tree onto the child trees.

Hierarchy is derived from the country-specific trees delivered and regularly updated by SAP

Example: Levels can be imagined as

  • Country-specific
    • Bank Specific
      • Process/industry specific

While in the past user had to manually update all the custom formats when meeting the requirements of his bank institutions one by one, the user is now able to perform mass updates and update either all child trees on one level or update specific country formats according to the bank-specific or vice versa.

Updates are triggered by user individually for each level (country-specific > bank-specific > industry-specific).

Read more about the Mass Synchronization functionality in this article.


Tree Testing

Test Program

In order to test the functionality of a payment format mapped in DMEEX, the user can use the test program feature which previews an output file defined in DMEEX.



While in DMEE the Debug function was in a separate transaction (DMEE_DEBUG), in the 1809 release of DMEEX, the user is now able to easily specify multiple breakpoints (in any node) in which the debug function stops. 

Example situation: Function can be used in order to double-check if the data in the specific segment are properly defined.


Comparison Mode

User can compare two different trees and/or two different versions of a tree. The application will then show every difference between the two trees.

Example situation – SAP delivers a new version of a country-specific payment format and the user has his own custom version – he can compare the two and can decide if he wants to accept the update.


Purpose of the calculation feature is to provide end-user functionality to perform simple mathematical operations right within the app.

This is done by defining variables,

creating calculation nodes and a possibility to map the variables in them.

Example situation: If a bank institution requires sequencing specific data in the output file

  • User can specify a condition in a calculation node and define which segments will be numbered in the output file automatically
  • In the past – ABAP programming was required, currently, this feature is a part of a tree

Read more about calculations in DMEEX.

Format Updates

We newly created or updated formats for United Arab Emirates, Australia, Brazil, Switzerland, China, Finland, Hong Kong, Hungary, Luxembourg, Malaysia, Philippines, Poland, Saudi Arabia, Singapore, Taiwan, and the United States.

In order to see all the payment formats available in DMEEX click here.


Learn more about DMEEX.

Read more about Payment Formats and tools associated with them here.


What do you think about the 1809 release of DMEEX on SAP S/4HANA? Please let us know your thoughts in the comment section below.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Joachim Kösling
      Joachim Kösling

      the comparison mode is really a nice and useful Feature.

      It would be great if it could be created also for ERP 6.0 in DMEE.

      Author's profile photo Jakub Djablik
      Jakub Djablik
      Blog Post Author

      Hi Joachim,

      unfortunately, this feature is and will be only available on SAP S/4HANA releases.

      Author's profile photo Kiran Kumar Panda
      Kiran Kumar Panda

      Hello Jakub,

      I have a requirement to count the no of items the header record has and display the count at the Header record.

      For Example : Here 'P' denotes header and 'I' denotes items. I need to show count 3 at the header because it has 3 line items.





      Please suggest how can we achieve this using DMEEX for the t-code F110.


      Thanks in Advance.

      Author's profile photo Richard Kuba
      Richard Kuba

      Hi Kiran,

      this could be achieved using the aggregations functionality. In the "item" segment define a reference ID on one of the nodes that are part of the iteration. Then, to output the final count, define new element on the header and select mapping procedure "aggregation". In the aggregation tab use the reference ID from "item" segment and select "number of occurrences".

      I hope this helps.

      Best regards,
      Richard Kuba


      Author's profile photo Deloitte team
      Deloitte team

      Hi Jakub,

      Thanks for this nice share. It is very informative and useful.

      However, could you share what happens to the existing DMEE tree in ECC when doing a system conversion (upgrade from ECC to S/4HANA).

      Is the DMEE tree converted and active in S/4HANA after upgrade or additional steps are required?

      Also is it correct understanding that users can continue to use DMEE without converting to DMEEX in S/4HANA?

      There is no DMEE specific migration steps or other documentation / OSS notes available so far to the best of my knowledge.

      Author's profile photo Richard Kuba
      Richard Kuba


      after system conversion DMEE trees remain intact. The conversion to DMEEX has to be manually triggered by opening a tree in DMEEX transaction.

      You can continue using DMEE, however SAP format tree templates are delivered only for DMEEX and you can't use new features of DMEEX.

      Because of this, SAP recommends to migrate all format trees to DMEEX after upgrade to SAP S/4HANA.

      There is no official migration documentation available.

      Let me know if you have any other question.

      Best regards,
      Richard Kuba