Skip to Content
The blog post has been successfully published.
Product Information
Author's profile photo Tomas Pavlicek

Performance Acceleration in DMEE(X)

Empty Element Processing for DMEE and DMEEX  

Bank institutions often require their clients to exclude empty nodes from the XML file. Formerly was this function accomplished via XSL Transformation in On-Premise. As for Cloud, this function was achieved with a functional module in the Post-Processing Functions tab. Nevertheless, XSLT Transformation lacks the capability of processing a large amount of the data inside the payment file because of insufficient memory resources. We solved this issue with the introduction of Empty Element Processing functionality, which simplifies deleting empty nodes.   

Functionality was initially delivered in SAP S/4HANA Cloud 2011 release and SAP S/4HANA On-Premise 2020 releaseand is also available across all S/4HANA OnPremise releases via SAP Note 2935888 – DMEEX – Correction Pack 2011 for DMEEX and for EHP releases via SAP Note 2858440 – DMEE – memory efficiency of DMEE_END_ABA for DMEE. 

The new functionality will ease deleting empty nodes. You can find it under the Post-Processing tab, there was also the XSL Transformation box relocated from Format Attributes tab. “Empty Element Processing” function allows you to choose from the following options:   

If you select Remove elements w/o content disregarding attribute values, all the elements without content will be removed from the tree whether they do have or don’t have attributes.   

In case you select Remove elements w/o content if they have empty/no attributes, all the elements without content will be removed from the tree only in case they have empty attributes or no attributes at all. This option will also remove all empty attributes from the output file.  

Deleting empty nodes with the new Empty Element Processing functionality is more transparent and effective than before.  




Deactivation of redundant nodes of SAP-delivered format trees  

The SAP-delivered format trees cover the entire functionality of the format because not every customer uses the same parts of the format. When you use the SAP-delivered format tree, while the entire format tree functionality is not necessary for communication with your financial institution, the engine still processes and keeps in memory the whole format tree. This decreases performance in a substantial way.  

In order to significantly increase the engine performance of format trees in DMEEX, you can copy the SAP-delivered tree to the customer namespace and deactivate nodes that are not needed for your bank institution. Therefore, the engine will process only the necessary (active) parts and its performance will accelerate.  

For example, you can hide an entire cluster of nodes that cover address information in the FI format tree, if it is not required by your financial institution. Open your format tree, right-click on the redundant node, and from the options choose “Deactivate”. Deactivation of the parent node will deactivate the whole subtree.   

You can proceed with the deactivation of redundant nodes in other formats likewise. The greatest impact will be in FI and FI-CA format trees because they consist of an enormous number of nodes.   

In addition to that, when you create a copy as a child of the SAP pre-delivered format, the parent tree remains updated by SAP and you can use synchronization to get updates from the SAP-delivered parent tree to your child tree. Nodes will remain updated even after deactivation.  

This solution is relevant for all DMEEX format trees. 


Also read an interesting blog about integration into FICA Payment Formats in Contract Accounting in SAP S/4HANA


Learn more about DMEE, DMEEX, and Map Payment Format Data.

To find out more about functionalities for payment formats, visit our Payment Formats blog.

Do you have any further comments regarding this topic? Do not hesitate to share them in the comment section below. You are also welcome to ask any questions about SAP S4/HANA Finance in the Community Q&A section.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Rob McNally
      Rob McNally

      Hi Thomas,

      Many thanks for this blog & the others in the series.

      Straight to the point & great source of information.

      I've found them very useful & practical when creating payment trees over the last year.


      Author's profile photo SAP Basis Siemens Healthcare
      SAP Basis Siemens Healthcare


      I found that Empty Element Processing function is not working. I need to have the empty element in the output xml-file. I choose the option Do not remove but the element is deleted.

      Thank you.