Hierarchy
⤷ BC-MID-RFC-BG (Application Component) Background RFC (bgRFC)
⤷ SQRFC2 (Package) ABAP Development for bgRFC
Basic Data
Data Element | BGRFC_TASK_CNT_MAX |
Short Description | Number of Open Connections (Tasks) per Destination |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BGRFC_TASK_CNT_MAX | |
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 11 | |
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 | Conn. |
Medium | 20 | Open Connections |
Long | 37 | Number of Open Connections (Tasks) |
Heading | 37 | Number of Open Connections (Tasks) |
Documentation
Definition
Maximum number of open connections (tasks) per destination
- 0: Destination is locked against bgRFC calls.
Use
This parameter defines how many open connections (tasks) can be held by a destination. All non-processed bgRFC calls for this destination are counted. You can use this parameter to prevent destinations from being overloaded by bgRFC calls.
Dependencies
For TCP/IP connections (external server programs), generally only one connection should be permitted.
You can also specify the number of open connections at the scheduler level. If the number of possible connections per scheduler is lower than the maximum number of connections per destination, or if these connections are distributed to multiple destinations, the maximum number of open connections per destination might not be reached.
The maximum number of open connections that can be held by the task handler is a further restriction.
Example
History
Last changed by/on | SAP | 20100420 |
SAP Release Created in | 710 |