Hierarchy

⤷

⤷

Basic Data
Data Element | DMC_CHECKTYPE |
Short Description | Classification of Check (Mandatory or Optional) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | DMC_CHECKTYPE | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | 10 | CheckClass |
Medium | 15 | Class.of Checks |
Long | 20 | Class. of Checks |
Heading | 17 | Class. of Checks |
Documentation
Definition
For objects of the migration workbench (especially migration objects and their sub-objects) different kinds of consistency checks can be performed. These checks are implemented in the classes that implement interface IF_DMC_VALIDATE. For this interface you find more detailed information.
Not all of these checks are relevant in all phases of an MWB project, and not all of them are equally important in these phases. Therefore, different steps are defined which constitute a type of milestone in the process. To each of these steps, a subset of the complete set of checks can be assigned. This assignment is stored in table DMC_VALIDATE. There it is also stored if a certain check is mandatory or optional if assigned to a certain phase. This distinction is defined by means of this type DMC_CHECKTYPE.
Example:
In the phase of the definition of migration objects, a check if a selection field (portioning field) is defined in the top-level sender structure is optional, but if the milestone is immediately before the runtime objects are generated, this check is mandatory.
If the checktype is "mandatory" for a certain check and a certain point in time ("STEP"), this means:
- The check is surely performed if the validation activity is invoked for this step
- If the check detects errors, the specified milestone is evaluated as incomplete or incorrect.
If, by contrast, the checktype is "optional" for a certain check and a certain point in time, this means:
- If the validation activity is invoked for this step, the check is only executed if the option "also execution optional checks" is activated
- If the check detects errors, these are listed, but still the specified milestone is not evaluated as incorrect
History
Last changed by/on | SAP | 20141030 |
SAP Release Created in | 620 |