SAP ABAP Data Element SX_COMMIT (SAPconnect: No. of Send Requests Followed by Commit Work)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
⤷
SCON (Package) SAPconnect - External Communication

⤷

⤷

Basic Data
Data Element | SX_COMMIT |
Short Description | SAPconnect: No. of Send Requests Followed by Commit Work |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Commit |
Medium | 15 | CommitAfter |
Long | 20 | CommitAfter |
Heading | 47 | No. of Send Requests Followed by Commit Work |
Documentation
Definition
While the send process is running, this parameter determines after how many processed send requests a "Commit Work" is sent.
Use
If the send process terminates, the send requests that were processed after the last "Commit Work" are not deleted in the queue, which means that they have to be sent again with the next send job. If you do not want this to happen in the relevant business process, set this value to "1". Higher values, on the other hand, can have a positive effect on performance. The value "0" triggers a single "Commit Work" once all pending send requests have been processed. If the value is higher than the number of processed send requests, a single "Commit Work" is sent at the end, too.
Dependencies
Example
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 640 |