Hierarchy

⤷

⤷

Basic Data
Data Element | /BOBF/VAL_NET_KEY |
Short Description | Validation Dependency |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /BOBF/CONF_KEY | |
Data Type | RAW | Uninterpreted sequence of bytes |
Length | 16 | |
Decimal Places | 0 | |
Output Length | 32 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
A validation sequence defines the sequence of a validations
Use
The business object processing framework ensures that if multiple validations are executed, the validations are executed in a defined sequence.
If a validation sequence is not defined, the sequence of executing these validations is arbitrary.
The validation sequence can be used with the "execute if failed" indicator.
Dependencies
The validation sequence is defined for all validations, but evaluated separately for all validations assigned to an action.
Example
A V1 validation is defined to check an A1 action. A V2 validation is also defined to check the A1 action. A V2 validation is time consuming and should only be executed if all other validations have not yet failed.
The "execute if failed" indicator should be set for the V1 validation and the V1 validation should be executed before V2 validation.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |