SAP ABAP Data Element ALLGCOMM (Maximum Number of Transactions before Session Is Updated)
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'
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 | ALLGCOMM |
| Short Description | Maximum Number of Transactions before Session Is Updated |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUMC4 | |
| 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 | 20 | Session update |
| Long | 40 | Session update |
| Heading | 4 | SeUp |
Documentation
Definition
Using this parameter, you can determine the maximum number of transactions until the next session is updated (in general: data base commit). During the session update, the transactions are written into the data base and the session is created. When the session has been created, it is always updated.
Via the number of transactions after which a session is updated, you can optimize the amount of data in the rollback buffer and the reduction in performance due to the update.
History
| Last changed by/on | SAP | 19930316 |
| SAP Release Created in |
