Substitution & Validation in Group Reporting(FIN-CS-COR-DT / FIN-CS-JE)

[bowen_cao]

1) There are two different FIORI APP "Manage Substitution and Validation Rules - Journal entries" and "Manage Substitution and Validation Rules - Journal entries", which shared the same fiori app ID F4406.

2) If GRPL is used in your system, below 7 Group reporting fields will be presented in Universal Journal Entry(table ACDOCA). With this, when you create Universal Journal Entry, the substitution/validation rules defined in app "Manage Substitution and Validation Rules - Journal entries", under substitution scenario event "FINS_ACC_CS_1 - GRPL core fields" and "FINS_ACC_CS_2  - GRPL subassignments to FS item" will be used.

3) If GRPL is not used, then app "Manage Substitution and Validation Rules - Journal entries" is not related to Group reporting directly.

4) Substitution/validation rules defined in app "Manage Substitution and Validation Rules - Group Journal Entries" FINS_GR_JEI_1, is used for post Group journal entries(e.g.  in the app "Post Group journal entries" or "Import Group Journal Entries")

5) In t-cd: FIN_RE_MAINT, you may display/simulate the substitution/validation rules.

6) If you find issues in your system for GRPL cores field in table ACDOCA. Please check the SAP Note: 3468806 - Preparation Ledger: Collection of notes
6.1)Make sure all note listed from note analyzer are implemented.
6.2)And then check the part below in this note:
------------------------------
How to check manual activities in substitution/validation rules

Substitution/Validation rules define their context in a view cluster. Some SAP Notes requires you to edit these fields in view cluster FIN_RE_CONTEXT using transaction SM34.

After implementing all SAP Notes from the attached list, you can check this context as follows:

Download the attached file with “Check Context” in the name. It contains a native SQL statement checking the expected fields. Please request assistance from your NetWeaver Administrator on how to execute this SQL statement in your system.

An empty result set is the expected result. If you get a non-empty result set, it lists those fields which need to be added or deleted and the SAP Note number where you get detailed instructions on how to do it. If a non-empty result set contains a record with the string “Initial Delivery” as SAP Note number, please create a support case on component FIN-CS-COR-DT requesting a check by SAP Support personnel.
------------------------------

7) If you find issues in "Post Group journal entries" /"Import Group Journal Entries" with substitution/validation rules, please simulate run the substitution/validation rules in t-cd: FIN_RE_MAINT(refer to the picture in step5).  And below notes are quite important, implement below notes can sovle the issue or avoid potential issue:
3281752 Substitution&Validation - Field 'PartnerUnit' prevents rule activation
3286501 Post Group Journal Entries: Empty line-items trigger Sub&Val rule evaluation
3329397 Substitution&Validation: Field 'Product Sold Group' is not available
3365079 Substitution&Validation: Custom function does not propagate error message
3457322 PGJE - Affected Field is not Highlighted
3517183 Validation Rules for Group Reporting Journal Entries ignored
3537413 PGJE - Check Triggers an Exception
3548598 Multiple improvements and fixies in customer validation and substitution
3561423 Change of semantic action for Fiori app. F4407/F4406
3589711 Substitution and Validation - Allowance of Unit of Measure Characteristics
3596379 Avoid duplicate messages in customer validation and substitution
3600726 FI fields as a Dimension in SAP Group Reporting

😎Useful program for debug:

Class: CL_FINCS_JE_RULE_ENGINE_CLIENT (post Group journal entries)
Class: CL_FINCS_ACC_INT_SUBVAL_FUNCT (post  journal entries)