SAP ABAP IMG Activity SIMG_CFMENUCX01_PO05 (Define Validations)
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷ EC-CS (Application Component) Consolidation
⤷ FC00 (Package) Cons: General consolidation (cannot be assign.to FC01-FC09)
⤷ EC-CS (Application Component) Consolidation
⤷ FC00 (Package) Cons: General consolidation (cannot be assign.to FC01-FC09)
IMG Activity
ID | SIMG_CFMENUCX01_PO05 | Define Validations |
Transaction Code | S_ALR_87003120 | IMG Activity: SIMG_CFMENUCX01_PO05 |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUCX01_PO05 | Define validations |
Customizing Activity | SIMG_CFMENUCX01_PO05 | Define validations |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUCX01_PO05 |
In this step you define rules for the validation of manual entries. The purpose of a validation is to have the system check certain rules during manual postings to ensure the consistency of the entries.
The validation guarantees the consistency of postings, by checking certain rules through the system.
- Document header
Common fields such as the ledger, version, fiscal year, period, document type, etc. are checked. - Document line items
The fields in the document header as well as line item information such as the FS item, subitem or partner unit can be checked. - The update
Validations across all line items are performed.
Example
You might define the following posting rules:
- Certain items may only be posted with certain subitems.
- Certain staff members (users) may only post entries that do not exceed certain value limits.
- The total amount of depreciation posted to asset items with certain transaction types must match the total value of the corresponding depreciation items.
Activities
- For each callup point (= document header, item, complete document) determine which validation rules you need for your entries.
- For each validation rule determine the prerequisites for performing the validation and related checks.
If your validation rule uses sets, these must be defined in table FIMC, which contains the fields for the conditions. - Determine which message is to be displayed when the validation requirements are met or not met. The message features up to four (4) display parameters--for instance, for displaying the user name. If needed, define a message class.
- Save the validation rules.
You can determine whether the rule applies to each callup point. Available options are: Active, Inactive, and Active except for batch input.
Further notes
The manual FI-SL Validation/Substitution contains additional information.
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_CFMENUCX01_PO05 | 0 | HLA0100228 A HLA0100229 |
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_TF510 | V - View | CX55 | 9999999999 | Validation of Documents |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |