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_CFMENUORFCAVAL | Maintain validation |
| Transaction Code | S_ALR_87003064 | IMG Activity: SIMG_CFMENUORFCAVAL |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORFCAVAL | Maintain validation |
| Customizing Activity | SIMG_CFMENUORFCAVAL | Maintain validation |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORFCAVAL |
In this step you can define validations for remote data entry using MS Access. Data entered locally using a PC data entry program must be checked for consistency before being exported.
Validations can be defined centrally in the R/3 System or locally in the PC data entry program by the system administrator.
When creating the validation steps, please note the following:
- A validation step consists of a precondition and a check. No precondition is required for PC data entry validations.
- Define the check using the mathematical formulas supported by the validation. The structure of the check must must correspond with the following outline syntax:
MATHS( <FILCT> SUM(*Value/Quantity field*) WHERE *Val.rule* *Operator* SUM(*Value/Quantity field*) WHERE *Val.rule*The following applies to entry variables marked "*":
- *Value/Quantity field*: Local/transaction/group currency or quantities.
17 period fields are available for each currency type or quantity. However, you only need to enter one of these fields. When downloading the validation rules, the system uses the period field to identify the currency type/quantity.
This arrangement currently means that a comparison of periods cannot be supported for validation. - *Operator*: Comparison operator (< , > , >= , <= , =)
- *Val.rule*: Validation rule containing all selection criteria. You can use the fields of the structure FILCT in a validation rule.
Standard settings
A breakdown check is preset in the PC data entry program in the standard SAP system. This cannot be subsequently changed.
Activities
Define the validations which you require in addition to those supplied as standard. You do this as follows:
- Enter an ID with a maximum of 7 characters.
- Select LC as the business application component 0010 as the callup point.
- Specify the validation steps.
Notes on transports
You can manually transport validations into the productive system using the function Validation -> Transport.
In addition, you can use a Customizing function specially designed for transporting validations. You do this in the Special Purpose Ledger Implementation Guide, under Tools -> Transport -> Transport validations.
Further notes
For further information, see:
- the Online-Help on how to create a validation step check
- the manual "FI-SL Validations and Substitutions" (R/3 library).
Business Attributes
| ASAP Roadmap ID | 255 | Create Interfaces |
| 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_CFMENUORFCAVAL | 0 | HLA0001250 | Data Entry with MS Access |
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 |
| IMGDUMMY | D - Dummy object | OC95 | ORFC_00005 | Validation Maintenance |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
