Disclosure Management – US SEC Configuration for US SEC

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

2

TABLE OF CONTENT Introduction ...................................................................................................................................................... 3 Plugins .............................................................................................................................................................. 4 Report Types .................................................................................................................................................... 7 Taxonomies ...................................................................................................................................................... 9 Instance Document ........................................................................................................................................ 14 Operational documents................................................................................................................................. 18 Useful Notes/KBAs ........................................................................................................................................ 19

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

3

Introduction In order to submit a valid XBRL instance to US SEC, Disclosure Management needs to be configured. This document describes the necessary steps.

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

4

Plugins For US SEC, four plugins are required:

US SEC CALC TRACE PLUGIN 10.1 • US SEC PREVIEW PLUGIN 10.1 • US SEC VALIDATION PLUGIN 10.1 • US SEC XBRL CREATION PLG 10.1 Note: these can be downloaded from SMP (https://launchpad.support.sap.com/#/softwarecenter)

Once they are uploaded and registered, you should have the following (note: version can be different)

NOTE: for the US SEC Previewer plugin do not forget that this plugins needs to be augmented with some additional files, this is outlined in section “4.10.2 Preparing the U.S. SEC Preview Plugin” of the Disclosure Management User Guide. First, download the US SEC preview plugin (in this example, the SP07 file)

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

5

Second, download the zip for rendering engine from the U.S. SEC website http://www.sec.gov/spotlight/xbrl/renderingengineconfigurablebinary.zip

Open both zips and in the DM Sec Preview plugin, go to the “SAP.DM.XBRL.USSECPreview.Plugin” folder

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

6

In this folder, add the folders and files from the “renderingengineconfigurablebinary.zip” These are the required files and (sub)folders Resources

Rule Files Aucent.FilingServices.Data.dll Aucent.FilingServices.FilingProcessorBase.dll Aucent.FilingServices.Log.dll Aucent.FilingServices.RulesRepository.dll Aucent.MAX.AXE.Common.Data.dll Aucent.MAX.AXE.Common.Exceptions.dll Aucent.MAX.AXE.Common.Resources.dll Aucent.MAX.AXE.Common.Utilities.dll Aucent.MAX.AXE.Common.XBRLParser_Reader.dll Aucent.MAX.AXE.Common.ZipCompressDecompress.dll Aucent.MAX.AXE.XBRLReportBuilder.ReportBuilder.dll Lucene.Net.dll NxBRE.dll ZedGraph.dll

The result should be like this

Save this archive and upload this plugin file to the SAP Disclosure Management server.

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

7

Report Types Besides the ‘normal’ report types (for Excel data cache, and Word documents), you need two specific report types:

- Taxonomies - XBRL 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

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

8

For the XBRL instance, create a report type with Report Category set to “US SEC XBRL Addon” 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 not registered, these options will not appear)

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

9

Taxonomies Disclosure Management will require both the Standard US GAAP taxonomy files (referred to as “base”) and the customer specific extension files (the “extended” taxonomy) to be uploaded in the system Note: for creation and maintenance of the extended taxonomy, SAP recommend using the Fujitsu XWand tool (http://www.fujitsu.com/global/products/software/middleware/application-infrastructure/interstage/solutions/xbrl/ ). Note: this tool is 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”

You should end up with something like this

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

10

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”

Note: US SEC will publish the US GAAP taxonomies annually, see https://www.sec.gov/info/edgar/edgartaxonomies.shtml Contact SAP support if you have problems with getting the correct Base taxonomy zip file. After uploading you should see this message

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

11

On the extended chapter, select the “Upload” tab Select the extended zip file and set the Taxonomy Type = ‘Extended Taxonomy”

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)

For an extended taxonomy, you need to link it to the appropriate base taxonomy

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

12

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”

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

13

Select the entry point and click “Import Entry Point”

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

14

Instance Document The instance document will form the basis of the XBRL file (.XML) that will be submitted to US SEC 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.

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

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

15

Specify the registrant name, CIK code (see https://www.sec.gov/edgar/searchedgar/cik.htm), the period of reporting. For Dimension Container, use “Segment” and the encoding needs to be set to ASCII (nothing else allowed, see https://www.sec.gov/structureddata/FAQs ) 2. Chapter XBRL Units, tab “XBRL Units”

Here you define the units that will be reported in the XBRL instance Note: most units are pre-defined by US SEC, 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)

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

16

You are allowed to 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 of time the fact is relevant etc.

A typical setup of a duration (e.g. CY, CYQTR etc.)

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

17

Note: setting the URI code to http://www.sec.gov/CIK 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”

5. Chapter XBRL Footnotes, tab “XBRL Footnotes” Here you define the footnote texts that will be reported in the XBRL instance.

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

18

Operational documents In the report settings of the operational documents (e.g. 10-K, 10-Q, data cache etc.) you need to link these to the correct XBRL instance document. With this, any mapping made in these documents will be included in the XBRL instance.

DISCLOSURE MANAGEMENT – US SEC. CONFIGURATION (V1.1)

19

Useful Notes/KBAs 2216987 - After roll-forward, import of entry points in extended taxonomy fails 2274705 - DM - XBRL import entry point errors

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