Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BF-CAT (Application Component) Catalogs⤷
QSKT (Package) QM Basic Data: Catalog Data
Basic Data
| Data Element | QKZSYNCVB |
| Short Description | Synchronous Update |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | QKZ | |
| 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 | SyncUpdate |
| Medium | 15 | Sync. update |
| Long | 20 | Synchronous update |
| Heading | 8 | SyncUpdt |
Documentation
Use
If the indicator is set, the dialog transaction and follow-up action are updated synchronously.
This means: The updates triggered by COMMIT WORK for the dialog transaction are completed before the function module for the follow-up action is started.
If the indicator is not set, the update is performed asynchronously.
Explanation
The indicator is not set, the update is performed asynchronously.
This setting is always useful if the follow-up action module is accessed before COMMIT WORK for the transaction. This means that the indicator Function module called after COMMIT WORK is not set.
If the follow-up action is accessed after COMMIT WORK for the transaction, no changed data can be read from the database because this could still be inconsistent.
Normally, the asynchronous update should be chosen, because this minimizes the response times for the dialog user.
The indicator is set, the update occurs synchronously.
As a result, you can make sure that the function module for the follow-up action can access data, that has been created or changed in the dialog transaction and stored consistently in the database.
The user must wait until the updates are completed and all data is saved to the database before another dialog is created.
History
| Last changed by/on | SAP | 19931130 |
| SAP Release Created in |
