Persons, who are working with XBRL reporting for CoRep / FinRep or Solvency II, are often faced with validation rules that have been officially deactivated by the European supervisory authorities, but are still marked as active within the taxonomies. The reason for this is that the official lists with validation rules are updated more often than the corresponding XBRL taxonomies.
These official lists with all validation rules can be found at the EBA Homepage for CoRep / FinRep (https://www.eba.europa.eu/regulation-and-policy/supervisory-reporting/implementing-technical-standard-on-supervisory-reporting-data-point-model-) and at the EIOPA homepage for Solvency II (https://eiopa.europa.eu/Pages/Supervision/Insurance/Reporting-formats.aspx). Within these lists many rules are marked as “deactivated” for different reasons.
Most of the time users simply need to ignore the validation results for those deactivated rules, but sometimes those rules are so faulty that they cause serious performance problems. So it is really advantageous to exclude these rules from the validation process.
The deactivation of validation rules is possible since SP06. A description of how to do so can be found in SAP Note 2296488, but I want to describe it here in more detail, because this process might not be as intuitive as needed.
Currently there is no User Interface for deactivating validation rules. All rules, that should be deactivated, have to be contained in a file “excludedRules.txt”, which is located in the top folder of the taxonomy zip file.
1. Step: Find out, which rules you want to deactivate
- If you want to deactivate all officially deactivated validation rules, you can simply open the list with validation rules, filter for all rules with an entry in column “Deactivated on” (and in case of the EBA taxonomy with NO entry in column “Reactivated on”) and then copy the content of the column with the assertion IDs to a new text file “excludedRules.txt”
- If you only want to deactivate validation rules, that need a very long time to evaluate, you will have to run one validation process and then have a look at the log files. You can see in the log files from the XBRL Service, when the evaluation of each assertion started. The timestamps are a very good indication, which rule took how long to evaluate. So you can figure out yourself, which rule needs which time.
- If you only want to deactivate validation rules that are known to cause problems, please have a look at the list of known issues. It exists only for the EIOPA taxonomy (https://dev.eiopa.europa.eu/Taxonomy/Full/2.0.1/EIOPA_SolvencyII_List_of_Known_Issues_2.0.1.xlsx).
All rules, from which we currently know that they cause performance issues, are mentioned in #15 (row 23) of the version updated 18th March 2016.
2. Step: Create the excludedRules.txt file
If you have in the previous step copied a complete column from the Excel document to the “excludedRules.txt” file, this is fine. Otherwise you have to create this text file now by entering each validation rule, you want to ignore, in a single line.
Note: You can either decide to ignore all assertions that include e.g. “BV364” or enter the assertion IDs correctly as “s2md_BV364-1”, “s2md_BV364-2”, “s2md_BV364-4”, “s2md_BV364-4”, “s2md_BV364-5”, “s2md_BV364-6”, “s2md_BV364-7”, “s2md_BV364-8” or as a mixture of it: “s2md_BV364”. All assertion IDs are ignored that contain the given string, so be sure not to enter something too general (like “s2md”). Each value has to be entered in a single row without quotation marks. You can find an example in the attachment of the named SAP Note 2296488.
Please note that this example contains the rules that were deactivated by the EIOPA in the official list of validation rules, released 18th March 2016. The list of validation rules has been updated since then (e.g. on 10th May 2016).
3. Step: Copy this file in the top folder of your taxonomy zip file
You should already have a taxonomy on your SAP Disclosure Management server. Download the latest revision of this taxonomy, extract it, copy the “excludedRules.txt” to the top folder (on the same level, where the “http” folder is), compress it again and upload it to the same chapter as before.
Putting the file inside the taxonomy makes sure that the file is transferred to all TaskEngines and that each system does the validation in the same way.
Now you can run your validations in the same way as before. The log files will tell you, which validation rules are executed and which are ignored.