Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WBON (Package) WWS: Bonus
Basic Data
| Data Element | UPDATEVF |
| Short Description | Update Procedure (Subsequent Settlement) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | UpdateProc |
| Medium | 15 | Update Proc. |
| Long | 20 | Update Procedure |
| Heading | 15 | Update Proc. |
Documentation
Definition
If this indicator is not set, then there can be a deadlock in tables S074, S015 or EKBO when the "Retrospective business volume update/setup of business volume data" function and "Setup income statistics" are executed.
Purchase orders, goods receipts, invoices, vendor billing documents and settlement requests cannot, or can only, be updated with some delay.
The "Retrospective business volume update/setup business volume data" function and "Setup income statistics" are affected the most, as very large rebate arrangements (many updates) can lead to longer runtimes for each rebate arrangement. A deadlock results if the rebate arrangemnt that has just been processed is being updated at the same time as the program from the above-mentioned documents is running.
No settlement should be made while income statistics are being set up.
We recommend you execute the "Retrospective business volume update/setup income statistics" function for large rebate arrangements (many updates) in a time frame where none, or as few as possible, of the above-mentioned documents are being created, for example, during the night.
By setting the switch, the risk which remains is small that an update - business volume data - will be lost. The transactions MEBA/MERA read the document data that is to be processed at the start of the processing. Shortly afterwards, a goods receipt is posted. The business volume update for the purchase order was already processed in the setup of statistical data (without the business volume update of the new goods receipt). The business volume update for the new goods receipt is updated (the statistical data is not locked). At the end of the processing the business volume data is deleted and updated again. The business volume data from the new goods receipt is deleted but not recompiled from the setup of statistical data. This problem usually only affects rebate arranngements with a large number of updates.
A "perfect" technical solution to this would be very costly and the risk of such a collision happening is very small anyway.
History
| Last changed by/on | SAP | 20020124 |
| SAP Release Created in | 470 |
