ESEF Validation Errors

[tassos_kapros]

Hello,

we are facing an issue when validating our ESEF report .

We are using SAP DM 17.01 and after validation the ESEF report we are getting the following two errors (ESEF & General TAB).

In ESEF Tab:

[ESEF.2.4.1.transformableElementIncludedInHiddenSection] The ix:hidden section of Inline XBRL document MUST not include elements eligible for transformation. 4 fact(s) were eligible for transformation: ifrs-full:BasicEarningsLossPerShareFromContinuingOperations, ifrs-full:DilutedEarningsLossPerShareFromContinuingOperations

We understand the issue, we have corrected a lot of them in the past but those lines are appeared in report.

(maybe this issue is related to the following error since for every line only two context period types are appeared CYTD, PYTD and not PYE, P2YTD)

In General Tab:

[xbrl.4.7.2:contextPeriodType] Fact ifrs-full:BasicEarningsLossPerShareFromContinuingOperations context PYE has period type duration conflict with context - xxx-2021-12-31.html 123

[xbrl.4.7.2:contextPeriodType] Fact ifrs-full:DilutedEarningsLossPerShareFromContinuingOperations context PYE has period type duration conflict with context - xxx-2021-12-31.html 123

This mapping is not appearing in our data cache and we are not able to delete it manually. We have made visible the sheet DM_Variables, where there is the current mapping list. We have also made a lot of tests, such as delete it from report, delete it from mapping, delete all DM_bookmark, disable all chapters containing the data cache link but all our attempts were bring the same error.

When opening the instance with Arelle, it seems that there are duplicate mapping with wrong contexts.

The last two mapping are wrong in both lines.

Please note that the period / report has been created from rolling forward process. The source period / report used the same contexts but maybe opened in SAP DM with different order.

Can you please advice?

Thank you,

Tassos

[tassos_kapros]

Hello Marc,

Thank you for your support.

I will log a ticket on the Support portal to check if the invalid records could be deleted.

Tassos

[Marc_Kuipers]

Yes, please do

We can check via SQL what exactly is happening

~Marc