Hierarchy

⤷

⤷

Basic Data
Data Element | BANK_DTE_MR_VBMODE |
Short Description | Update Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BANK_DOM_MR_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 | UpdateType |
Medium | 15 | Update Type |
Long | 20 | Update Type |
Heading | 14 | Update Type |
Documentation
Definition
Ensures that the system defines the update type within a process. This can be asynchronous (see Asynchronous Update Task (BC-CST-UP)), synchronous (seeSynchronous Update Task (BC-CST-UP)), or Not Defined. If you or the system have not yet started a process, or if a current process has ended, the update type is not defined.
The system specifies an update type automatically for most of the processes. In processes that you start in the dialog, the update type is synchronous. In processes that you start in the background, or in mass processing processes, the update type is asynchronous. If both update types are possible, you can specify this in the respective initial screen.
Further notes
If the update type is changed during a process, an error message is issued and the processing is stopped. This can, for example, happen in customer BAdI implementations within the SAVE event where your own data is written to the database. We recommend that you use the predefined update type for each BAdI interface.
Further information
Function group BCA_PROCESS
Definition
Use
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 300 |