Hierarchy
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services⤷
IS-B-DP (Application Component) Transaction Data Pool⤷
JBDC (Package) Customizing IS-B Data Pool
Basic Data
| Data Element | JBRVMODE |
| Short Description | Documentation Element on T242I-VMODE |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | Docu. |
| Medium | 15 | Documentation |
| Long | 20 | Documentation |
| Heading | 0 |
Documentation
Definition
The validation indicator determines how intensively entered data is checked. The higher the number of the validation indicator, the more intensive the check. A higher validation level represents a greater drain on system resources which will affect the run times for external data transfer.
0 = No check. The quickest way of importing data. The delivered records must be completely free of errors since otherwise faulty records may be written to the data pool. This mode is only recommended for experts after a long induction phase.
1 = Check against required/optional control. Here the system checks whether all required fields are delivered. The mode field, which has to be delivered by the user, determines whether the record is inserted or updated. The system does not check whether the database error could occur. If, for example, a record which already exists is inserted, the system notifies you of a runtime error. The same occurs when you attempt to update a record which does not yet exist.
2 = Check against required/optional control and database. The insert and update functions are checked to make sure no database errors occur. The mode field delivered by the user is ignored. IS-B independently determines whether the record already exists. If it exists, the record is updated, if it does not yet exist, the record is inserted. The system then checks whether inconsistencies may occur. If this is the case, the function permitted by the database is carried out and the mode field is ignored. The user is informed of this in the log.
3 = Check against required/optional control, database and mode field. As for 2, except that in the case of an inconsistency the record is not processed any further. An error message then appears in the log. The record is then forwarded to the error exit routine. This mode is particularly useful when external data transfer is first implemented since it checks for all determinable errors.
History
| Last changed by/on | SAP | 20011002 |
| SAP Release Created in |
