cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

SAP Disclosure Management XBRL - ESEF Taxonomy

1,861

Hello,

I have to prepare an XBRL scenario based on ESMA - ESEF taxonomy.

I downloaded the latest taxonomy from ESEF site

https://www.esma.europa.eu/sites/default/files/library/esef_taxonomy_2017.zip

and after making the proper configurations (correct taxonomy folders and SAP DM config), when I opened the DM Mapper, there is the following error message

and the content in the Mapping area is not displayed.

Could you please guide me?

Also is there an available updated How-to instruction guideline for the specific taxonomy?

Thank you,

Tassos

Accepted Solutions (0)

Answers (6)

Answers (6)

Marc_Kuipers
Product and Topic Expert
Product and Topic Expert

Check the following discussion as well

error DM XBRL MAPPER

Marc_Kuipers
Product and Topic Expert
Product and Topic Expert

For some examples of customers' extended taxonomies, you can check this page:

https://www.esma.europa.eu/field-test-esef

Marc_Kuipers
Product and Topic Expert
Product and Topic Expert

Hello Tassos,

OK, there is a misunderstanding here. The file I provided is only the 'base' taxonomy.

For ESEF, filers need to create their own private taxonomy like for the US SEC.

The ESMA has chosen the same “open” approach as the US SEC, i.e. by applying the financial statements of the company, except that the entry-point you extend is not IFRS or US-GAAP directly but the ESEF taxonomy which extends IFRS

See: https://www.esma.europa.eu/policy-activities/corporate-disclosure/european-single-electronic-format

Preparers shall mark-up disclosures using the taxonomy element having the closest accounting meaning to the marked up disclosure; if the closest taxonomy element misrepresents the accounting meaning of the disclosure, issuers shall create a so-called extension taxonomy element and anchor such extension to the core taxonomy element that has the closest accounting meaning.

The codification name of the taxonomy files is the same, i.e. you need to create a zip file that contains the following files

-Schema file (.xsd)

- Label Linkbase (<name_space>-date_lab.xml)

- Reference Linkbase (<name_space>-date _ref.xml) (note: optional )

- Calculation Linkbase (<name_space>-date _cal.xml)

- Definition Linkbase (<name_space>-date_def.xml)

- Presentation Linkbase (<name_space>-date_pre.xml)

You can follow the example described in https://wiki.scn.sap.com/wiki/download/attachments/452566079/DM_US_SEC_Configuration.pdf

To create the extension, SAP recommends using the Fujistu Xwand tool (https://wiki.scn.sap.com/wiki/download/attachments/452566079/DM%20-%20Fujitsu.pdf ) which is available on https://launchpad.support.sap.com/#/softwarecenter/support/index

Thanks

Marc

Marc_Kuipers
Product and Topic Expert
Product and Topic Expert

Hello Tassos,

Your taxonomy file is not correct - you cannot download the file directly from the regulator (ESMA)

DM expects a certain structure (with sub-folders under 'http') and you also need to augment the taxonomy with some 'basic' files that are being referenced, like types, currencies etc.)

This is why there are no labels in your situation

See: https://service.sap.com/sap/support/notes/2511418

..for correct taxonomy files. You can use the 2019 file to test ESMA as well

Thanks

Marc

0 Kudos

Hello Marc,

Thank you for your support.

I created a short extended taxonomy for a dummy company with intend to upload it to SAP DM and import Entry point.

Please find below, the steps I followed:

  • 1.Select and study Imerys company from https://www.esma.europa.eu/field-test-esef,
  • 2.Under “Taxonomy Editor & Instance Creator”, I prepared a short extended taxonomy based on “base_2019.zip” taxonomy file that validated successfully
  • 3.Collected all required files in a zip file with the proper folder structure
  • 4.Under SAP DM, I uploaded the “base_2019.zip” taxonomy as Base taxonomy
  • 5.Under SAP DM, I uploaded my taxonomy as Extended taxonomy of the Base taxonomy based on “DM_ESEF.pdf” document file

After selecting import Entry point to the extended entry point, the following message is displayed.

error-message.jpg

I have also uploaded using the Imerys taxonomy and the error message is the same.

Please find attached the error files from my server.

2019-09-04.txt

2019-09-04-trace.txt

Could you please advise, why the extended entry point is not imported, since it is validated correctly from “Taxonomy Editor & Instance Creator”?

0 Kudos

Hello Marc,

Thank you for your answer.

The same error is displayed when using the base_2019.zip file and attaching the

entry point esef_cor.xsd to my xbrl taxonomy in SAP DM.

I have also added manually the following files:

http://xbrl.ifrs.org/taxonomy/2017-03-09/full_ifrs/labels/lab_full_ifrs-en_2017-03-09.xml

http://xbrl.ifrs.org/taxonomy/2017-03-09/full_ifrs/labels/doc_full_ifrs-en_2017-03-09.xml

but the error message is still displayed.

Please advise.

Thank you,

Tassos