SAP ABAP IMG Activity SIMG_CFMENUORFCOC42 (Define validation)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
FK (Package) FI-LC Consolidation

⤷

⤷

⤷

IMG Activity
ID | SIMG_CFMENUORFCOC42 | Define validation |
Transaction Code | S_ALR_87002450 | IMG Activity: SIMG_CFMENUORFCOC42 |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUORFCOC42 | Define validation |
Customizing Activity | SIMG_CFMENUORFCOC42 | Define validation |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUORFCOC42 |
In this step, you define the validation of postings. The objective of the validation is to have the system check postings using certain rules.
Example
You may want to determine the following rules for postings:
- Only post to certain financial statement items using certain transaction types.
- Certain employees (users) may only make entries within certain value limits.
- The total amount of the depreciation posted to asset items using certain transaction types must equal the total value of the corresponding depreciation item.
There are three individual validation points:
- Document header
You can validate global fields, e.g, ledger, version, year, period, document type, etc. - Document lines
You can validate document header fields as well as document line fields, such as FS item, transaction type, trading partner, and also user-defined additional fields. - Posting
During posting, validations can be carried out across all document lines.
Standard settings
In the standard SAP R/3 System, the three validation points are preset. Each of the validation rules must be defined by the user.
Activities
- Determine which rules you need for every validation point.
- For every validation rule, define the prerequisite for the validation as well as the validation itself.
If you would like to apply sets in the validation rule, you must define the sets in table FILCA, which contains the fields for the conditions. - Determine which message is displayed when the prerequisite is met and when the validation is not fulfilled. The message can contain a maximum of four display parameters (e.g., the output of the user ID). You may want to define a message class.
- Store the validation rules in the system.
You can determine a level of activation for each validation point. Choose between the levels "Active", "Inactive" and "Active except for batch input".
Additional Information
For more information, please refer to the manual FI-SL - Validation/Substitution.
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 |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_CFMENUORFCOC42 | 0 | HLA0001239 | Posting |
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 |
V_T876V | V - View | OC42 | 9999999999 | Generated table for view V_T876V |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |