SAP DM - XBRL - Mapping inline - Validate-errors

[IOL]

Hi experts,

While generating in SAP DM ST1700 the XBRL report also receives a new document in DM Stack 1700 - Excel report - XBRL - Mapping inline - Validate.

In ESEF tab there is a message about inconsistency in anchoring.

The structure of anchoring relationships for the extension taxonomy concept has been prepared according to the rules and based on a sample file received from SAP.

The error is received both in the report based on my augmented taxonomy and on the basis of the augmented SAP taxonomy.

[ESEF.3.3.2.anchoringRelationshipsForConceptsDefinedInElrContainingDimensionalRelationships] Anchoring relationships for concepts MUST be defined in a dedicated extended link role (or roles if needed to properly represent the relationships), e.g. http://{issuer default pattern for roles}/Anchoring. http://www.sap.com/role/Anchoring - sap-2019-12-31_def.xml 79, 81, 83, 86, 88, 90, 93, 96, 99, 102, 105, 108, 111, 113, 116

[ESEF.3.3.2.anchoringRelationshipsForConceptsDefinedInElrContainingDimensionalRelationships] Anchoring relationships for concepts MUST be defined in a dedicated extended link role (or roles if needed to properly represent the relationships), e.g. http://{issuer default pattern for roles}/Anchoring. http://www.xxxx.pl/role/Anchoring - xxxx-2020-12-31_def.xml 19, 21, 24, 27, 29, 32, 35, 37, 40, 43, 45, 48, 50, 53, 54, 57, 59, 61, 64, 67, 70, 73, 75, 78, 81, 84, 86, 88, 91, 94, 96, 98, 101, 104, 107

Is it possible that the error is in the validation [ESEF.3.3.2]?

In the IOerror tab, a message appears .

[IOerror] esef_cor-lab-de.xml: file error: [Errno 2] No such file or directory: 'C:\\ProgramData\\SAP\\Input\\c6deb176-6e65-4eae-b4ad-37f7df9bf6cb\\arelle\\cache\\http\\www.esma.europa.eu\\taxonomy\\2019-03-27\\esef_cor-lab-de.xml' - sap-2019-12-31.xsd 11

[IOerror] concept-relation-filter.xsd: file error: [Errno 2] No such file or directory: 'C:\\ProgramData\\SAP\\Input\\c6deb176-6e65-4eae-b4ad-37f7df9bf6cb\\arelle\\cache\\http\\www.xbrl.org\\2010\\concept-relation-filter.xsd' - http://www.esma.europa.eu/taxonomy/2019-03-27/esef_cor-for.xml 5

Unfortunately, I have found nothing about this file or directory.

What is the message error, in fact?

In the AssertionUnsatisfied tab, a message appears .

[formula:assertionUnsatisfied] man_ExplanationOfChangeInNameOfReportingEntityOrOtherMeansOfIdentificationFromEndOfPrecedingReportingPeriod - 'http://www.esma.europa.eu/taxonomy/2019-03-27/esef_cor-for.xml 20498

According to the Regulation, as a first step we have to tag 10 additional pieces of information, including 'Explanation of changes in the name of the reporting entity or other identifying information since the end of the previous reporting period'. -> we do not have this tag used because there has been no such change.

Can I ignore the error?

Does it interpret this error incorrectly?

[Marc_Kuipers · Accepted solution]

Hi Iwona

1. It seems you have not anchored your extended elements

https://www.xbrl.org/guidance/esef-rules-anchoring-extensions/

2. Seems the base is missing http\\www.xbrl.org\\2010\\concept-relation-filter.xsd

I know we provided an early file, where this was missing, You can download the base from

2827882 - How to get ESEF taxonomy files

3. Not sure- you should contact ESMA on this

https://www.esma.europa.eu/about-esma/esma-in-short/contact-info

Marc

[Marc_Kuipers]

Iwona

Coming back to the error on man_ExplanationOfChangeInNameOfReportingEntityOrOtherMeansOfIdentificationFromEndOfPrecedingReportingPeriod

I was working with another customer, who also got this error (10x), however, the regulator marked these as "WARNING" and not as errors that would fail submission

Just an FYI - it is still up to you to correct these or check with your regulator on what they would like to do

Marc

[Marc_Kuipers]

iwonasmartcon

Coming back to this error

[ESEF.3.3.2.anchoringRelationshipsForConceptsDefinedInElrContainingDimensionalRelationships] Anchoring relationships for concepts MUST be defined in a dedicated extended link role (or roles if needed to properly represent the relationships), e.g. http://{issuer default pattern for roles}/Anchoring. http://www.sap.com/role/Anchoring - sap-2017-12-31_def.xml 18, 21, 23,..

This appears to be a bug in the ESEF validation engine that Arelle uses.

It appears when you use extensions for dimension members and anchor the dimension members using the domain-member relations, in accordance with the ESEF Reporting Manual.

Note: it does not apply to standard items, which need to be anchored.

If the error is blocking for the submission to your regulator (Komisja Nadzoru Finansowego), you can simply remove the anchoring for extended dimension members.

[IOL]

Hi,

Marc, thank you very much for your help.

Iwona