Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBZ (Package) Payments
Basic Data
| Data Element | ENLIM_FZ |
| Short Description | Maximum Number of Lock Entries |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM06 | |
| Data Type | NUMC | Character string with only digits |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| 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 | 18 | Max. No. Locks |
| Long | 25 | Max. No. of Lock Entries |
| Heading | 29 | Maximum No. of Lock Entries |
Documentation
Definition
Use
When you are using customer/vendor clearing it is not immediately clear which customers and vendors are being processed in a payment run. This is why locks are set to prevent update terminations by reason of multiple selection in parallel payment runs.
To avoid the lock table overflowing, the number of lock entries can be restricted. To achieve this, a field for the maximum number of lock entries has been included in table T042C. When this value is reached, the locks are deleted to prevent an overflow of the lock table.
As choosing not to set locks can result in update terminations, the lowest number of locks is defined in the program at 5000.
Dependencies
Example
Two payment runs are started at the same time. The first payment run only selects the vendors from 1000 to 5000. The second payment run selects only the customers from 6000 to 8000.
Vendor 1500 has clearing with customer 6512 active.
Through the clearing, customer 6512 is taken into account in the first payment run, and vendor 1500 in the second. None of them is visible based on the selection.
Due to the locks, the selection is only made in one payment run.
If a large number of company codes are processed in a payment run, and vendor/customer clearing used intensively, this results in a large number of locks during the selection phase in the payment program.
Example:
100 company codes are paid in a payment run. Clearing is used on average with 250 accounts for each company code.
This leads to 100 * ( 2 * 250 ) = 50,000 lock entries.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 605 |
