Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-GL (Application Component) General Ledger Accounting⤷
FAGL_POSTING_SERV_EHP3 (Package) Services for Posting FI Documents (EhP3)
IMG Activity
| ID | FAGL_VALIDATE | Define Validation Rule for Account Assignment Combinations |
| Transaction Code | S_E4A_94000151 | (empty) |
| Created on | 20080507 | |
| Customizing Attributes | FAGL_VALIDATE | Define Validation Rule for Account Assignment Combinations |
| Customizing Activity | FAGL_VALIDATE_OB | Define Validation Rule for Account Assignment Combinations |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FAGL_VALIDATE_DC |
Use
In this IMG activity, you can define rules for classifying account assignment combinations as valid or invalid. After defining validation rules as part of a validation strategy, you can assign them to a company code as a default validation strategy or assign them directly to a specific ledger group.
When a document needs to be posted, the system applies the validation rules you defined together with the account assignments specified in the document, classifies the document as invalid if applicable, and rejects the posting.
Note
There is an authorization object for validating account assignment combinations (F_FAGL_DRU).
- To update the groups used in the validation rules (such as cost center groups), you need to schedule the program Adjustment of Derivation Rules After Changes to Groups (FAGL_VAL_DERIVATION_TOOL) periodically.
Requirements
Standard settings
Activities
- Create a validation strategy, and define derivation rules with the desired account assignment combinations.
When creating the validation strategy, you have to select the desired validation type (invalid or valid account assignment combinations). The validation type specifies whether the validity of the defined rules or account assignment entries need to be checked (see example below). If validation rules have already been created for a validation strategy, the validation type can no longer be changed.
- In combination with the definition of the derivation rule, specify the objects to be checked, such as cost center 10101 (rule entries).
- Assign the validation strategy to a company code or to a ledger group. Validation strategies can be assigned to multiple company codes or ledger groups.
- Activate the validation strategy for the company code and save your entries.
Example
In your company, postings cannot be made to the account assignment combination "Cost Center 10101 and G/L Account 400000". For this case, you define a validation strategy with the validation type Invalid Account Assignment Combination, and create a derivation step with the source fields Cost Center and G/L Account.
As rule entries, you specify cost center 10101 and G/L account 400000.
If you now assign this validation strategy to a company code as a default validation strategy, documents with this account assignment combination are rejected.
The validation type thus specifies how the system subsequently needs to interpret the rule when posting the document.
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| VC_FAGL_VALIDATION | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 20091211 |
| SAP Release Created in | 604 |
