Hierarchy

⤷

⤷

Basic Data
Data Element | VBMODE |
Short Description | Execution Mode of an Update Module |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | VBMODE | |
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 | Mode |
Medium | 15 | Mode |
Long | 20 | Execution Mode |
Heading | 55 | Execution Mode |
Documentation
Processing mode of the update module
An update record consists of update modules, which are processed differently depending on the type of system. If processing is terminated, the update record can be subsequently updated only if it exclusively contains update modules that are able to be upated (that is, it must not contain update modules of type
V1 non-updatable).
Update Module Processing Mode
V1 Immediate processing.
V1 (non-updatable) Immediate processing, subsequent updating is not possible. The module is dependent on enqueue locks that are inherited from the update process. Since these locks are deleted if the update process is terminated, these modules cannot be updated.
V2 Delayed processing
Collective run These update modules are not executed immediately; they are collected together and then processed with same-type modules belonging to other update requests. This processing must be triggered explicitly.
Asynchronous RFC An update request can contain at most only one module of this type. For technical reasons this module is used for tRFC (and qRFC). It is implictly appended to the update request at the end of a transaction.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 50A |