Skip to Content


DM Stack 1200 of SAP Disclosure Management 10.1 has been released on 12 March, 2018.



These scenarios benefit from this latest release:

  • Core SAP Disclosure Management functionalities
  • Installation, Update and Operations
  • Security
  • US SEC Filings and other XBRL scenarios using the Input Schedule Method
  • EU XBRL Filings and other XBRL scenarios using the Mapping Method
  • E-Bilanz Tax Filings
  • API



The following SAP Notes will provide more details:




Learn about new features and capabilities in the following.


Chapter Favorites

Do you have to work on many chapters spread across lots of reports? Were you ever desperated, when searching for the chapters you have to modify? Did you ever wish to have your own list of favorite chapters across all reports?

With DM Stack 1200 this is now possible!

Each user can have their own list of favorite chapters and work on these chapters directly from the favorite list.

Using this brand-new feature is very easy:

You can simply mark each chapter as favorite by clicking the star icon on the General tab.

On the “Favorites” tab, all chapters marked as favorite are shown.

You can directly edit them from here or navigate back to the report, in which the currently selected chapter can be found.

For more information, have a look at the new section “Chapter Favorites in the User Manual.


New Permission for Activating / Deactivating Chapters

Activating and deactivating chapters was previously only possible, if the user had the “Report –> manage” permission. This also meant that the respective user was e.g. able to give local permissions to other users.

This has been improved by adding a new permission “Activate/Deactivate Chapters”. This permission – as its name says – is needed to set chapters to activate or inactive.

This also means that users with only “Report –> manage” permission can no longer do so. They need this new permission additionally.

Note: When updating to DM Stack 1200 this new permission is added to all roles, which previously already had the “Report –> manage” permission.



PDF Attachments inside XBRL Files Now Possible

In the Belgian Solvency II BE v.1.0.1 scenario, it is necessary to include PDF documents in XBRL files, when reporting to the National Bank of Belgium. With DM Stack 1200 this is now supported: The DM Client 10.1 contains scripts for adding the desired PDF files to the already created XBRL file. For a detailed description see the readme.txt file located in the Utilities subfolder of DM Client installation folder.





Support NW RFC Protocol for ERP Data Sources

For connecting to ERP data sources, previously a library called “librfc32.dll” was used. This library was installed with old versions of the “SAP GUI”, but is not present in SAP GUI 7.50 (or newer) any longer.

If SAP GUI 7.50 (or newer) is installed, the NW RFC Protocol needs to be used for ERP data sources. To do so, it is required to configure each ERP data source to “Use NW Protocol”.


Improved Setup of DM SERVER – APPL SERVER 10.1

With DM Stack 1200, the setup wizard of the DM SERVER – APPL SERVER 10.1 has been improved as follows:

  • When updating an earlier DM Stack to DM Stack 1200, you can only select an existing database in the setup wizard. You can only select those database catalogs that belong to an installation of DM Stack 1000 or newer.
  • No system/master database catalogs are selectable for installing/updating DM SERVER – APPL SERVER 10.1 using the setup wizard.
  • The Database selection functionality of the setup wizard has been improved.
  • Uninstallation functionality has been improved as it now automatically recognizes and removes left-over components.
  • Prerequisite checks of the setup wizard have been improved.


Centralized License File

The management of license files of third party vendors was changed with DM Stack 1200: It is no longer necessary to configure the location of these files. Therefore, the tab “Licenses” has been removed from “Administration” –> “System Configuration”.


Extended Administrator’s Guide for AD Authentication

The Administrator’s Guide contains a new section “Enabling Active Directory Authentication that describes all necessary steps to enable Single Sign-On Active Directory (SSO AD) authentication after the installation of SAP Disclosure Management with basic authentication only.


Swagger Documentation Available for RESTful APIs

Now, for all SAP Disclosure Management RESTful APIs a Swagger documentation is available. Within the new Swagger documentation, you can find details about expected request parameters, responses or occurred errors for each API call.

For more information have a look at our Admistrator’s Guide.


Embedding True Type Fonts in Power Point Files is now Optional

In previous DM Stacks, True Type Fonts are embedded automatically in Microsoft Power Point files during checkin. With DM Stack 1200 this feature can be switched off by setting a registry key.

For more information have a look at the Installation and Upgrade Guide in chapter “SAP Disclosure Management Client Registry Keys”.


Improved Usability for Template Creator App

The usage of the Template Creator App is even more easy now! With our latest release, you can simply change the number of rows for all open tables of an entry point with a single setting. Same for the number of iterations for all z-axes tables. For large entry points this can save lots of configuration work and time.


List of Covered Actions in Audit Trail

The chapter “Extended Audit Trail” of the Administrator’s Guide has been improved to explicitly list the different activities covered by the Audit Trail.





Business Content Published for EBA’s Taxonomy

This release contains the Business Content for EBA’s taxonomy. Business Content has been published only for the part Supervisory Benchmarking Portfolios as it includes the only change compared to the Business Content for taxonomy version For more information see SAP Note 2608444.


SAP E-Bilanz Templates For Taxonomy 6.1

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

  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.

Compared to their taxonomy 6.0 predecessors, the taxonomy 6.1 templates include these additions/improvements:

  • Improved “Stammdaten” sheet
    • Updated list of legal forms
  • Improved worksheet “Anlagenspiegel”
    • Table header now show hierarchy information
    • Ability to switch signs for specific columns to adjust to ERP imported data
  • Improved worksheet “Kapitalkontenentwicklung”
    • Table header now show hierarchy information
    • Updated list of account types

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


ERiC 27 Library Used in E-Bilanz Scenario

SAP Disclosure Management components for E-Bilanz scenario now use ERiC 27 for the validation and submission of E-Bilanz reports. ERiC 27 supports taxonomy 6.1 test filings and is backwards compatible to older taxonomies. From April 2018 this will also be the minimum required version for submitting E-Bilanz reports to ELSTER.

ERIC 27 only allows TLS v1.2 with Perfect Forward Secrecy for HTTPS-Protocol.
It only supports the following ciphers:


Make sure your System landscape supports these settings.


© 2018 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.

To report this post you need to login first.


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

  1. Christoph Schroeder Post author

    Hello Mr. Koerfer,

    I was just informed by the SAP ERP colleagues that this works a little bit different:

    Normally new taxonomy versions are supported automatically by the SAP ERP system. Only if code changes are needed, a note is released for this new taxonomy version.

    But such changes were not necessary since taxonomy version 5.4.

    Hopefully this helps and best regards,




Leave a Reply