Skip to Content
Product Information
Author's profile photo Christoph Schroeder

DM Stack 1600 available


DM Stack 1600 of SAP Disclosure Management 10.1 has been released on April 20th, 2020.



These scenarios benefit from this latest release:

  • Core SAP Disclosure Management functionalities
  • Installation, Update and Operations
  • XBRL scenarios using the Mapping Method (e.g. US SEC Filings, UK HMRC, ESEF, ESMA and others)
  • E-Bilanz Tax Filings



The following SAP Notes will provide more details:

Please also see our Installation and Upgrade Guide.




Learn about new features and capabilities in the following.


Multi Instance Installation for Application Server

With earlier DM Stacks, you could install just one single instance of DM SERVER – APPL SERVER 10.1 on the same server machine. This has been improved as since DM Stack 1600, the DM SERVER – APPL SERVER 10.1 setup provides support of multi-instance installation and update on one single server machine.

Further details can be found in SAP Help.





Improved Appearance of iXBRL Instances

With DM Stack 1502 it became possible to render iXBRL reports with pages like the original Word document.
With DM Stack 1600 additionally page numbers and hyperlinks are supported. Images of type SVG (vector graphics) are automatically exchanged by images in PNG format as vector graphics are not allowed to be used in iXBRL filings.


Support of Transformation Rules with Inline XBRL as Format

The Transformation Rules Registry defines how strings that appear in Inline XBRL documents are converted to the formats required by the data types of concepts in an XBRL documents.
The XBRL Mapper has a new tab ‘Format’ where such kind of formats can be applied to any mapping.

Further details can be found in SAP Help.


Full Support of Rollforward for Chapters of Content Type MS PowerPoint

Since DM Stack 1600, chapters of content type PowerPoint (ppt and pptx) will be forwarded and data links will be relinked to the new period. This function is restricted to certain objects (textboxes and linked images).


Support of Server-Side Content Refresh for MS PowerPoint

Additionally to server-side content refresh of MS Word and MS Excel documents, DM Stack 1600 also supports server-side content refresh of linked images and textboxes in MS PowerPoint.



With DM Stack 1600 the DM SERVER – XBRL SERVICE 10.1 does no longer exist. All functions previously executed by it are now executed by the DM SERVER – TASK ENGINE 10.1. This allows better scaling of the DM SERVER – TASK ENGINE 10.1.


Workflows and Reports Can be Set to Outdated

Workflows and Report Types can be set outdated. If this flag is checked, they cannot be used for reports and chapters anymore. This can also be undone.

Further details can be found in SAP Help.





SAP E-Bilanz Templates for Taxonomy 6.3

The technical content of SAP Excel templates for E-Bilanz included in DM Stack 1600 consists of a set of 7 Excel templates representing the new taxonomy 6.3:

  1. SAP E-Bilanz template for Core taxonomy
  2. SAP E-Bilanz template for Core MicroBilG taxonomy
  3. SAP E-Bilanz template for Bank taxonomy
  4. SAP E-Bilanz template for Payment Institutions taxonomy
  5. SAP E-Bilanz template for Insurance taxonomy
  6. SAP E-Bilanz template for Branches taxonomy
  7. SAP E-Bilanz template for Branches MicroBilG taxonomy

All templates can be used with both, SAP Disclosure Management 10.1 and SAP ERP client for E-Bilanz 1.0.

For more information about the new E-BILANZ TAXO6.3 TEMPLATES 1.0 see SAP Note 2916128.


ERiC 31 Library Used in E-Bilanz Scenario

SAP Disclosure Management components for E-Bilanz scenario now use ERiC for the validation and submission of E-Bilanz reports. ERiC 31 supports taxonomy 6.3 test filings and is backwards compatible to older taxonomies.

A major change in this version is that the file encoding changed to UTF-8. Therefore, you need to generate a new E-Bilanz report revision before a validate, preview or submit action can be performed.


© 2020 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.


Assigned Tags

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

      Big thank you for the MS PowerPoint reports enhancements!

      Author's profile photo Marc Kuipers
      Marc Kuipers

      Wunderbar Herr Schroeder !

      Author's profile photo Roger Weinhold
      Roger Weinhold

      Hallo Herr Schröder,

      sind derzeit in den Vorbereitungen der E-Bilanz 2019 für den Konzern. Können wir davon sicher ausgehen, das mit Stack 1600 alle hierfür notwendigen Themen bereitgestellt sind und wir in die Umsetzung gehen können oder steht noch ein Hotfix Package in den Startlöchern auf das wir warten sollten?

      Freue mich auf Ihr schnelles Feedback!

      Author's profile photo Christoph Schroeder
      Christoph Schroeder
      Blog Post Author

      Hallo Herr Weinhold,


      wir planen tatsächlich in nächster Zeit ein neues Update zu veröffentlichen: Den DM Stack 1601. Geplant ist, dort die neue Eric-Version 31.7 einzubauen. Diese wird ab September 2020 für das E-Bilanz-Reporting benötigt (siehe  SAP Note 2863238).


      Viele Grüße,

      Christoph Schröder

      Author's profile photo Roger Weinhold
      Roger Weinhold

      Hallo Herr Schröder,

      nochmals vielen Dank für die Info am 18.06.2020 zum Stand der Dinge. Gibt es mittlerweile ein verbindliches Release Datum für Stack 1601?

      Würde mich freuen.

      Vielen Dank vorab!

      R. Weinhold

      Author's profile photo Christoph Schroeder
      Christoph Schroeder
      Blog Post Author

      Hallo Herr Weinhold,


      Stack 1601 wurde am 13.07. released. Er enthält die neue Eric-Version, die ab September benötigt wird. Siehe Release-Note 2940214.


      Viele Grüße,

      Christoph Schröder

      Author's profile photo Tim Knowles
      Tim Knowles

      Hi Christoph,

      In your blog posting I note that the removal of the XBRL service will lead to improved scaling of the task engine.  Could you kindly elaborate on what that will mean?  In particular I'm keen to know if:

      1. Will it lead to faster XBRL validations?
      2. Will the task engine still be available for other tasks whilst long running XBRL tasks are processed?
      3. Can we schedule XBRL jobs outside of core working hours?

      Thank You

      Tim Knowles