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

DM Stack 1500 available


DM Stack 1500 of SAP Disclosure Management 10.1 has been released on November 13th, 2019.



These scenarios benefit from this latest release:

  • Core SAP Disclosure Management functionalities
  • Installation, Update and Operations
  • Security
  • XBRL scenarios using the Mapping Method (e.g. US SEC Filings, UK HMRC, ESEF, ESMA and others)
  • XBRL scenarios using the Input Schedule Method (e.g. EU XBRL Filings)
  • 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.


Additional Chapter Infos in Cockpit View

The Cockpit view has been enhanced with a new Info column. Here the user can see at a glance which chapters are linked by other chapters, have broken workflow inheritances or broken workflow permissions, where the permission inheritance has been broken and – in case of XBRL reports – where ambiguous data was found (see next chapter).

Further details can be found in SAP Help.


New Ambiguous Data Check for Reports

Values in XBRL reports are always connected to data points from the XBRL taxonomy. Each data point is only allowed to be reported once in an XBRL report, but – when using the template-based approach for XBRL creation – it is possible that the same data point is shown in multiple tables of a single entry point. This is not an issue, if the same value is entered on each occurrence, but it might also happen that different values for the same data point are entered in the different tables of an XBRL report. This leads to ambiguous data, since it is not possible to report multiple values for a single data point.

With previews DM Stacks, ambiguous data could only be seen in the Consistency Validation Report after the XBRL was created.

With DM Stack 1500, it is possible to check for ambiguous data directly on the SAP Disclosure Management website. For this, you can simply click on “Check” on report level and will immediately see the result of the check:

Afterwards, on the Cockpit tab a symbol in the new Info column informs, where ambiguous data was found. After selecting one of these chapters, a new tab “Ambiguous Data” appears, where you can easily see the ambiguous values and directly open the respective chapters in edit mode.

Further details can be found in SAP Help.


Language Configurable per User

With DM Stack 1500 the display language does no longer depend on the current browser settings but can be changed in the user settings.

Each user can do it for himself by clicking on his name in the top left corner of the Disclosure Management website.

More information can be found in the  SAP Help.


An admin user can do it for others in the Security / Users area.





Silent Installation Supports “Windows Authentication” Method for Database Connection

Since DM Stack 1500, it is supported to install DM SERVER – APPL SERVER 10.1 and DM SERVER – TASK ENGINE 10.1 silently with “Windows Authentication” method for establishing a database connection at runtime of SAP Disclosure Management.

This new feature is described in the Installation and Upgrade Guide.


Changed Behavior for Rollout Templates

Prior to DM Stack 1500, only the styles were updated when templates were rolled out.

With DM Stack 1500 this is still an option, but the new standard is that the content of the chapter is transferred to the template and created as a new revision. Header and Footer will not be considered. Only if the chapter does not have any revision yet, a 1: 1 copy of the template is created as the first revision.

If multiple templates exist, you can now also select which template should be rolled out or all of them.

Further details can be found in the SAP Help.


Management of Server-Side Data Sources Changed

Prior to DM Stack 1500 data sources on the SAP Disclosure Management 10.1 Server were changed by uploading a config20.xml file.

With DM Stack 1500, this is no longer possible as this configuration is now written into the database. Instead the administration of the server-side data sources is done via the DM Client 10.1. With it, data sources on the server can easily be added, edited or removed.

Further details can be found in the SAP Help.


Changed Behavior for Configuring the State of Internal and External Data Sources

With recent DM Stacks, users had to configure their data sources manually as “internal” or “external”. Making mistakes here could lead to unnecessary long time for the content refresh as the caching was not used for data sources wrongly marked as “external”. On the other side it could also lead to the caching mechanism being used for data sources marked as “internal”, which were external and therefore could not been cached properly.

To avoid such issues in the future, the status of a data source as external or internal can no longer be configured manually. Instead the system determines this itself, when a data source is selected in the DM Client under “Manage Datasources” and the button “Determine” is clicked.

During the update to DM Stack 1500, all data sources have been set into the state “undetermined”.

More information can be found in the SAP Help.


Support of Microsoft Office 2019

Since DM Stack 1500, the DM CLIENT 10.1 and DM XBRL MAPPER 10.1 support installation with Microsoft Office 2019. Installation of both components was allowed already in the past, but the setup could not distinguish between Microsoft Office 2016 and 2019. This has been fixed with DM Stack 1500.


Support of Microsoft SQL Server 2017

Since DM Stack 1500, SAP Disclosure Management 10.1 is now supported to be installed with Microsoft SQL Server 2017.


© 2019 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

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.