Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-DCM (Application Component) Data Transfer⤷
BKD (Package) Tools for (external) data transfer
Basic Data
| Data Element | JCHECK |
| Short Description | External data transfer: Intensity of checks |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | JCHECK | |
| 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 | Check |
| Medium | 15 | Check |
| Long | 20 | Intensity of check |
| Heading | 0 |
Documentation
Definition
With some transfer types (see documentation on transfer types in the Implementation Guide), you can determine the intensity of the checks here.
Different checks are performed depending on the validation level that you specify here:
Check 0: No checks
Check 1: Check mandatory/optional fields, fixed values and value tables
Check 2: Check mandatory/optional fields, fixed values and value tables, check against database, mode field is overridden (If a record that already exists in the database is to be added, the mode field is set to "U".)
Check 3: Check mandatory/optional fields, fixed values and value tables, check against database, mode field is not overridden (If a record that already exists in the database is to be added, the mode field is not changed. Instead, the system issues an error message and the record is marked as faulty.)
Note that not all transfer types offer all validation levels.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |
