Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBAS (Package) Financial accounting 'Basis'
Basic Data
| Data Element | COMFR_FZ |
| Short Description | Threshold Value for COMMIT Calls |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM04 | |
| Data Type | NUMC | Character string with only digits |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 20 | COMMIT thrshld val. |
| Heading | 20 | COMMIT thrshld val. |
Documentation
Definition
The threshold value is a control parameter for the frequency of COMMIT calls by the payment program.
Use
If you do not specify a threshold value, a COMMIT occurs after every payment document. This way updating of the documents, transaction figures, etc. is triggered.
A higher performance can, however, generally be achieved by a COMMIT call being carrried out for a bundle of documents.
If you do specify a threshold value, then a COMMIT is only run if the
number of payment documents
+ number of line items in the payment documents * 3
+ number of items to be cleared * 2
exceeds the specified threshold value.
Procedure
If you have performance problems with the payment run (not the proposal run), check to see whether you can speed up the payment run by entering or changing this threshold value.
Note that a bundling of database updates may possibly also make changes to your database system settings necessary (for example, larger rollback segments).
Examples
If a payment document contains 5 line items on average and pays 10 invoices, a weighting of 1 + 5*3 + 10*2 = 36 results for each document. This means that for a threshold value of 500 a COMMIT would be carried out for 14 payments in each case.
History
| Last changed by/on | SAP | 19960409 |
| SAP Release Created in |
