How to check validation related issues in Group Reporting(FIN-CS-VE)

[bowen_cao]

Before read this article, please be noted that, in SAP Group Reporting, there are two concept named "validation",  one is "Validation unversal Journals" in Data Donitor.
Another one is "Reported data validation or Standardized data validation" and "Consolidated data validation" in Consolidation Monitor.
Task "Validation unversal Journals" is used to check if errors exist in universal journals in the form of missing or incorrect subassignments for financial statement (FS) items.  Which is not in the scope of this artile. If you have issues regarding Task "Validation unversal Journals", make sure the notes in "3581767  - VUJ: Collection of notes" are all implemented.

In this article, I'm going to focus on "Reported data validation or Standardized data validation" and "Consolidated data validation" in Consolidation Monitor.  Component for it is FIN-CS-VE.
A) "Reported data validation” - validate the reported financial data in the local currency according to the validation method you assigned to your consolidation unit.
B) "Standardized data validation" - validate the financial data in the group currency according to the validation method you assigned to your consolidation unit.
C) "Consolidated data validation" - validate the consolidated data in group currency (or in transaction currency and tolerance currency, and quantity-type data as you specified in the relevant validation rules) for your specified fiscal period and consolidation groups.
*This is the reason why we put the task  "Reported data validation” before currency translation, and task “ Standardized data validation" after translation.

1) There are some configurations in order to run the validation tasks, almost all of the issues are related with the configration.  The process for the configration is below:
App: Define validation rules -> App: Define validation methods -> App: Assign validation methods 
here are all of the table which used for save the configurations:

Validation Engine: Rule	VEC_RULE
Validation Engine: Rule Text	VEC_RULET
Rule Definition and Data Source Mapping Relationship	VEC_RULE_DS
Validation Engine: Validation Rule Expression	VEC_RULE_EXP
Validation Engine: Tagged Amount	VEC_RULE_TAMT
Validation Engine: Tagged Amount Text	VEC_RULE_TAMTT
Drill through report for VEC validation rule	VEC_RULE_DT_REP
Tagged Amount Expression	VEC_TAMT_EXP
Operand text	VEC_TAMT_OPDT
Validation Engine: Rule Expression	VEC_TAMT_OPERAND
Validation Method	VEC_MTD
Validation Method Text	VEC_MTDT
Validation Method Group	VEC_MTD_GRP
Validation Method Group Text	VEC_MTD_GRPT
Validation Method Group Drill-through Report	VEC_MTD_GRP_DR
Validation Method Rules	VEC_MTD_RULE
Unified Selection Header	FINCS_USEL
Text of Unified Selection	FINCS_USELT
Unified Selection Options	FINCS_USELOPT

2) In "Define validation rules", the rules will be translated to a AMDP class, e.g.  /1VEC/500FINCSRTESTA
500 means client FINCSR is Validation Scenario, and TEST is the validation rule, A is the status.
if there is any changes to the validation rule, or selection objects which used the validation rule operands, you will need to re-activate the validation rules.  You can check the class  /1VEC/500FINCSRTESTA in SE24, but unfortunately, which cannot be used for debug .  In lower release enviroment, make sure below note is implemented when you got the issue: Hieararchy node is missing:

3282290 - Hierarchy node list not available for selection in Define Validation Rules

3) Use the app "Import/Export Validation Settings" to import/export validation settings. Please be noted that, there might be some changes for the template between different release. If you export the setting in a lower release enviroment, and try to import into the system after upgraded to higher release enviorment, there might be some errors, Make sure you download the template from the higher release enviorment, and edit it before import. The SAP Note below is also quite important:

3439330 - Download screen not working correctly in Import/Export Validation Settings app 

4) Use the app "Schedule mass activation jobs" to re-activate validation rule/selection objects/validation method. This is quite useful if there are a lot of changes for validation rule/selection objects. Or after you used the app  "Import/Export Validation Settings" .  And there might be another issue that, you found a lot of inactive objects in SE80 which start with /VEC/*, in that case, Please read the note descriptions carefully, as SAP Note 3055061 - Remove Inactive AMDP Objects of Validation Rules and Methods has some manual activities as well.

5) Make sure the support package level consistency for frontend system and backend system, for more information, please refer to the note: 3336823 - SAP FIORI FOR SAP S/4HANA 2023: Release Information Note. 

There is a strict (1:1) dependency between SAP Fiori for SAP S/4HANA version (containing the Fiori UIs) and the SAP S/4HANA back-end version. SAP FIORI FOR SAP S/4HANA 2023 is released for SAP S/4HANA 2023 only.

6) The validation tasks select data from The CDS view is P_VECFINCSUNION instead of ACDOCU directly. But you can always use the app "Group Data Analysis" when you want to do analysis for the output results, based on the setting of the validation rule where condition.

7) Check the project CONS_VECRESULT(Validation Rule Result) or CONS_VECRULE(Validation Rule), if you want to check technical details regarding validation rule or validation results. You can find the dataset entity or even the MVC programs there. Below is an example if I want to know the program for get the rule header information:


8）Performance issue, please make sure below notes are implemented:
3083539 Performance Issue in Hierarchy Node Value Help When Defining Validation Rules
3083540 App: Define Validation Rules, Performance Issue in Hierarchy Node Value Help
3120232 Improve the performance of app Define Validation Rules
3355804 Validation - Performance Improvement for AMDP on the runtime
3364993 Group Reporting - Excessive CPU and memory consumption during validation run
3459639 Validation Performance - Switch CDS Views to Optimize Memory Consumption
3480333 Validation Performance - Remove union parts from reported and standardized data validation to optimize memory consumption
3519644 Improve performance in assignment and snapshot for total validation in Group Reporting

===