Disclosure Management - SAP

Disclosure Management iXBRL for ESEF Author: Marc Kuipers

DISCLOSURE MANAGEMENT – IXBRL FOR ESEF (V2.0)

2

TABLE OF CONTENT Introduction ................................................................................................................................................ 3 Setup .......................................................................................................................................................... 4 Components ................................................................................................................................................ 4 Plugins ........................................................................................................................................................ 4 Report types ................................................................................................................................................ 6 Taxonomies ................................................................................................................................................. 9 Instance document......................................................................................................................................14 Operational documents ...............................................................................................................................18 Operational Process .................................................................................................................................19 Mapping in Excel ........................................................................................................................................19 Mapping in Word .........................................................................................................................................26 Generating the iXBRL instance ...................................................................................................................31 View the files ..............................................................................................................................................34

VALIDATION ..............................................................................................................................................36 Useful Resources and KBAs ....................................................................................................................40


3

Introduction Since Stack 1400 (https://blogs.sap.com/2019/03/27/dm-stack-1400-available/ ) the Disclosure Management application supports the creation of iXBRL instances for the ESMA regulator. This European Single Electronic Format (ESEF) will require all public companies across Europe to submit

their Annual Financial Reports digitally as Inline XBRL documents and in accordance with the IFRS

standards

For more information, see https://www.xbrl.org/news/esef-becomes-european-law/

This document will outline the setup of ESEF in SAP Disclosure Management.

https://blogs.sap.com/2019/03/27/dm-stack-1400-available/

https://www.xbrl.org/news/esef-becomes-european-law/


4

Setup Components For iXBRL, there are 2 additional components needed (besides the usual server and client

- XBRL mapper - Task Engine

Plugins For ESEF iXBRL reporting, there are 2 plugins required, which can be downloaded from the SAP Software Center SAP.DM.XBRL.MappingInlineCreate.Plugin.dll SAP.DM.XBRL.MappingInline.PreviewWeb.Plugin.dll Note: on SMP the inline creation plugin is named “UK HMRC IXBRL CREAT. PLG 10.1”

After uploading, you should have these two entries in the plugin setup.

https://wiki.scn.sap.com/wiki/download/attachments/452566079/DM_USSEC_XBRLMapper.pdf

https://blogs.sap.com/2015/11/26/sap-disclosure-management-101-installation-configuration-of-task-engine/

https://launchpad.support.sap.com/#/softwarecenter/support/index

https://launchpad.support.sap.com/#/softwarecenter/support/index


5


6

Report types Besides the ‘normal’ report types (for Excel data cache, and Word documents), you need two specific report types: - Taxonomies - iXBRL Instance For the taxonomy, create a report type with Report Category set to “XBRL Taxonomy” and Standard output format = “None”

The chapter content needs to be set to “XBRL (zip)” and there is no Output format needed.


7

For the iXBRL instance, create a report type with Report Category set to “XBRL - Mapping inline - Create” and Standard output format = “XBRL”

The Chapter Content is left blank, and the “output format” needs to be set as follows (note: if the plugins are


8

not registered, these options will not appear)


9

Taxonomies Disclosure Management will require both the ESMA ESEF taxonomy files (referred to as “base”) and the customer specific extension files (the “extended” taxonomy) to be uploaded in the system Do not download the base directly from the ESMA site (e.g. https://www.esma.europa.eu/document/esma-esef-taxonomy-2017 ) as this file is (for DM) incomplete and also does not have the required structure. You can download the base from this note: 2827882 - How to get ESEF taxonomy files For creation and maintenance of the extended taxonomy, SAP recommend using the Fujitsu XWand tool (http://www.fujitsu.com/global/products/software/middleware/applicationinfrastructure/interstage/solutions/xbrl/ ). Note: this tool is also available on SMP First, create a report in the appropriate period with the report type created in previous section.

Second, create two chapters in this report (commonly named, base and extension), both of Content Type = “XBRL Taxonomy”

https://www.esma.europa.eu/document/esma-esef-taxonomy-2017

https://www.esma.europa.eu/document/esma-esef-taxonomy-2017

https://service.sap.com/sap/support/notes/2827882


10

You should end up with something like this:


11

On the base, go to the “Upload” tab, select the Base Taxonomy.zip file and upload it (click “Add document”) NOTE: set the Taxonomy Type to “Base Taxonomy”

After uploading you should see this message:

On the extended chapter, select the “Upload” tab Select the extended zip file and set the Taxonomy Type = ‘Extended Taxonomy” An extended taxonomy needs to be linked to a base-taxonomy (the chapter just created) In the dialog box, select the corresponding base period/report/chapter


12

Note: the zip file should contain: - Schema file (.xsd) - Label Linkbase (<name_space>-date_lab.xml) - Reference Linkbase (<name_space>-date _ref.xml) - Optional - Calculation Linkbase (<name_space>-date _cal.xml) - Definition Linkbase (<name_space>-date_def.xml) - Presentation Linkbase (<name_space>-date_pre.xml) (see https://en.wikipedia.org/wiki/XBRL#XBRL_Taxonomy on explanation of these)

https://en.wikipedia.org/wiki/XBRL#XBRL_Taxonomy


13

After clicking ‘add’ the file will be uploaded

On the extended chapter, go to the “Taxonomy Entry Points” After the initial upload, the Status will be “New”


14

Select the entry point and click “Import Entry Point”

Instance document The instance document will form the basis of the iXBRL file (.html) that will be submitted to the regulator. First, create a report with the ‘report type’ that was defined in the first section

If you open this report, it will already have the chapters created. These are pre-defined and no manual chapters need to be added.


15

For the report and each chapter, some settings need to be defined. Note: see https://www.sec.gov/structureddata/xbrl-glossary for some commonly used terminology. 1. Main report, tab “Configuration”

Specify the Dimension Container (use “Scenario”) and the encoding needs to be set to UTF-8 The document name will be the name of the iXBRL instance file that DM will generate – an often-used naming convention is <company>-<date> 2. Chapter XBRL Units, tab “XBRL Units” Here you define the units that will be reported in the iXBRL instance

https://www.sec.gov/structureddata/xbrl-glossary


16

Note: most units are pre-defined, see http://www.xbrl.org/utr/2013-05-17/utr.xml In DM, you would define a pre-defined code as follows (e.g. USD, EUR) You can create your own units.

3. Chapter XBRL Contexts, tab “XBRL Contexts” Contexts define the entity, e.g., company or individual, to which the fact applies, the period the fact is relevant etc. A typical setup of a duration (e.g. CY, CYQTR etc.)

Note: setting the URI code to http://standards.iso.org/iso/17442 is a common best practice 4. Chapter XBRL Taxonomy, tab “XBRL Taxonomy” In here, you link the Instance document to the taxonomy you want to use. Select the period, report, and taxonomy chapter (note: these were defined in previous chapter)

Click on “save” so that the status is set as “Imported”

http://www.xbrl.org/utr/2013-05-17/utr.xml


17

5. Chapter XBRL Footnotes, tab “XBRL Footnotes” This is not applicable for iXBRL


18

Operational documents In the report settings of the operational documents (e.g. Annual report, Quarterly report, data cache etc.) you need to link these to the correct iXBRL instance document. With this, any mapping made in these documents will be included in the iXBRL instance. For example, in the Excel (data cache)

For example, in the Word report(s)


19

Operational Process Once all components have been installed and configured, the operational part can start. The goal is to tag the data and then generate the “instance document” For more information on the XBRL Mapper, please also check section “4.10.7 Using the SAP Disclosure Management XBRL Mapper” of the SAP Disclosure Management User Guide The instance document that DM generates will include all the tagged data as ‘facts’ and references the taxonomy that has been defined. Note: all examples and screenshots come from SAP’s 2017 annual report, see:

https://www.sap.com/docs/download/investors/2017/sap-2017-integrated-report.pdf

Mapping in Excel Each Excel report that is linked to the XBRL instance can be opened and used by the XBRL mapper Start by checking out the chapter/report (via Edit)

Start the SAP XBRL Mapper

https://www.sap.com/docs/download/investors/2017/sap-2017-integrated-report.pdf


20

On the left, all the concepts in the taxonomy are listed (note: it is best practice to start the concepts with the Level number). Expand the concept tree to see the individual concept. Place the cursor in the cell that represents the value of the fact and tick the concept. The cell will turn “yellow”


21

Note: make sure the highlighting is enabled

Next, go to the “Context” tab in the Mapper and select the appropriate context. Note: the contexts that are shown are the ones defined on the iXBRL instance document.

Note that the XBRL Mapper checks “period” in both Taxonomy and Defined context. Therefore, if the context is ‘duration’ in the taxonomy….


22

…only contexts with ‘duration’ can be selected in the tool.

The 3rd step is the “unit” (again, pre-defined in the iXBRL instance document) Once the unit has been selected, the cell will turn ‘green’, indicating that the fact is complete.


23

The 4th tab are the dimensions. Dimensions provide a way to express complex or multidimensional relationships in disclosures. They allow you to further describe reported information by associating the information with more than one characteristic. Dimensions are comprised of Tables, Axis, Domains, Members and Line Items It depends on the taxonomy whether a concept has been defined with dimensions or without. The DM XBRL mapper is aware of this and will show the dimension values only if they are present.


24

Once all parts are defined, the tab “mapping overview” shows all the selected items (the Reference is the sheet/cell number in Excel)


25

Note: you can remove mappings (or individual context, concept etc.) by de-selecting the tick box, or use the options below in the ribbon

Once the tagging is complete, please use the “apply changes” of the DM client, to check the chapter back in.

Final remark: technically, the mappings are stored on a sheet called “DM_Variables” See: 2397126 - DM - How to show DM_Variables sheet for more details.



26

Mapping in Word

In Word, you would add the mapping of notes – the concepts for these are text blocks that will appear as tags in the iXBRL instance. You can also map the DEI information directly in Word. When you open a Word chapter which contains data-linked tables (or formula fields) that have been tagged in Excel, you will see these tags in Word as well The tags show as brackets [ ] around the tagged values. If tagging changes in Excel, you simply need to run a ‘content refresh’ to see the updated information in Word.

If you start the XBRL mapper, you will see all the information as you do in Excel (and cells will be highlighted if that option is set) The actual tagging of text in Word is similar to Excel First, you need to select the text you want to tag – simply by selecting it with your cursor…


27

Then, tick the concept

Note: the tagged text will appear ‘green’ instantly – there is no 2 step (yellow/green) approach in Word tagging. If you tag text 2x (or multiple), the color changes (the colors show the ‘nesting’). Note: that it is best practice to tag level-up (i.e. start at the lowest) The colors used are green/blue/purple/grey


28

After this, you add the context.

Note : you will rarely add a unit, as you are tagging text blocks (notes), not individual numbers. Technically, the tagged text is stored as a “bookmark” (starting with DM_Map*)


29

Once complete, don’t forget to apply the changes.

If all tagging is done, you must create the report at the top level, as this will be the report that will be converted to iXBRL (html) In this example, the annual report consists of several chapters.


30

The Consolidated Financial Statement contains the tagged Excel tables (data-links to the Cache) and the Notes contains the Word tags. Create the report at top level


31

Generating the iXBRL instance

The final step is generating the iXBRL instance In the iXBRL instance report, select the option “create”

The option to generate the “preview file” is optional, but it is recommended to tick this, so that checking the iXBRL file is easier. You should get this message. Note: the instance is created by the Task Engine, so this component needs to be running

Once the task completes, you should see this message


32

In the instance, go to the revisions tab


33


34

View the files You can view the generated file, with any HTML editor, or simply Notepad You will see the various tags and all created facts

However, it is far easier to view the generated preview file with a browser that has an iXBRL plugin With this, each tagged fact can be clicked on, and the details will show. Examples of Chrome and IE


35


36

VALIDATION

Since Disclosure Management Stack 1700, you can also validate the instance It will use the ESMA validation rules, see https://www.esma.europa.eu/document/esef-validation-rules First, you will need the (new) plugin called “SAP.DM.XBRL.MappingInlineValidate.Plugin.dll”

On the report type for the iXBRL instance, you need to add this plugin as an ‘output format’

https://www.esma.europa.eu/document/esef-validation-rules


37

On the iXBRL Instance, there are some new parameters Set the ‘Transformation Registry’ to Version 4 See: https://www.xbrl.org/news/new-xbrl-specifications-to-recommended-status/ For the Validation level, select ESEF

Now, when you create the instance, you will now have the option to ‘validate’

Once the Instance creation has completed, you will see an additional file in the revisions

https://www.xbrl.org/news/new-xbrl-specifications-to-recommended-status/


38

If you download these, the zip file will contain an Excel file called “XBRL - Mapping inline - Validate.xlsx”

This file contains the validation – there are a number of sheets for the different types of issues (e.g. there is a distinction between ESEF specific errors and iXBRL errors.)


39


40

Useful Resources and KBAs SAP Disclosure Management User Guide 2216987 - After roll-forward, import of entry points in extended taxonomy fails 2274705 - DM - XBRL import entry point errors 2820522 - Message "Error while import of taxonomy. No labels available" 2825506 - Unable to download XBRL Instance revision 2779653 - XBRL Mapper does not load taxonomy 2305886 - Error when starting XBRL mapper 2452614 - No data when generating XBRL instance 2827882 - How to get ESEF taxonomy files

https://help.sap.com/viewer/6fda503523d6413597f5cd81be59fa8a/DM%20Stack%2014xx/en-US/3db93b3053e54ef082466b0c0214f78b.html

https://help.sap.com/viewer/6fda503523d6413597f5cd81be59fa8a/DM%20Stack%2014xx/en-US/3db93b3053e54ef082466b0c0214f78b.html









©2019 SAP AG. All rights reserved.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign,

SAP BusinessObjects Explorer, StreamWork, and other SAP products

and services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and

other countries.

Business Objects and the Business Objects logo, BusinessObjects,

Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and

other Business Objects products and services mentioned herein as

well as their respective logos are trademarks or registered trademarks

of Business Objects Software Ltd. Business Objects is an SAP

company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL

Anywhere, and other Sybase products and services mentioned herein

as well as their respective logos are trademarks or registered

trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks

of their respective companies. Data contained in this document serves

informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials

are provided by SAP AG and its affiliated companies (“SAP Group”)

for informational purposes only, without representation or warranty of

any kind, and SAP Group shall not be liable for errors or omissions

with respect to the materials. The only warranties for SAP Group

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.

www.sap.com

Documents

Disclosure Management - SAP