Hierarchy

⤷

⤷

IMG Activity
ID | CWTY_VALIDATION | Specify Validations |
Transaction Code | S_KA5_12001149 | IMG Activity: CWTY_VALIDATION |
Created on | 20020423 | |
Customizing Attributes | CWTY_VALIDATION | Specify Validations |
Customizing Activity | CWTY_VALIDATION | Specify Validations |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | CWTY_VALIDATION |
In this activity you define the validations for the check routines in Warranty Processing.
For further information see the IMG under Financial Accounting --> Special Purpose Ledger --> Tools --> Maintain Validation/Substitution/Rules --> Maintain Validation.
A validation consists of at least one step. Each step is made up of the three components prerequisite (optional), check and message. The check is only carried out if the prerequiste is met. If the check encounters an error, then a pre-defined message is displayed.
Use
You create validations and susbstitutions at a specific callup point in the application area warranty. Callup points are certain points in an application at which processing of a validation or substitution is called. If you want to have a value validated or substituted, you have to define at which point in time the valdiation or substitution should take place.
The possible callup points in warranty processing are formed from the possible combinations of the following parameters:
- Category: versions from claimant, versions to reimburser, versions from reimburser, versions to claimant
- Claim level: header+version, defect code (on item level), entire item
The data available for the validation and substitution depend on the callup points:
Tab Page Table Fields
In table GB01 you can see which table fields are available for which callup points for the definition of rules. The fields available for selection have class type B or A.
You cannot add fields to this table. However, you can exclude fields from the selection by maintaining view V_GB01C (transaction SM30).
Tab Page Rules
Several terms can be linked by operators (for example, AND, OR) to form complex rules. So that you do not have to create the same rule every time using the editor, you can define and save rules per callup point that are then available for every validation or substitution in this callup point. You can then use these rules directly in a prerequisite or check for validations or only in a prerequisite for substitutions, or combine then to more complicated rules using operators. You define the reusable rules in the menu tree on the left in the node for the rules for each callup point. The rules defined here appear for selection in every validation and substitution of the appropriate callup point on the rules tab page.
Tab Page Exits
On the tab page Exits there are exit programs from the FORM pool SAPFGBEB and customer-specific user exit programs (provided they have been assigned to the work area GBLR in the IMG activity Define Client-Dependent User Exits.
These exits can be used directly as rules (IF exitname IS TRUE) or also as parts of complicated rules (IF exitname IS TRUE AND exitname2 IS FALSE AND x = #X#). The exits should only deliver Boolean results.
Requirements
Standard settings
No validations are delivered in the SAP standard system.
Activities
Example
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 | CWTY_VALIDATION | 0 | ALN0000451 | Warranty Claim Processing |
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 |
GGB0 | T - Individual transaction object | GGB0 |
History
Last changed by/on | SAP | 20020423 |
SAP Release Created in | 471 |