Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-RFC (Application Component) RFC⤷
SRFC (Package) Middleware Runtime Environment
Basic Data
| Data Element | SCHED_WATCH_TIME |
| Short Description | Monitoring Time for Destination/Queue Scheduler |
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 | 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 | Number |
| Medium | 15 | Number |
| Long | 20 | Natural Number |
| Heading | 0 |
Documentation
Definition
Timeout value (in seconds) for queue monitoring by the scheduler
Use
The runtime of LUWs is restricted to prevent the scheduler from being blocked by too many terminated asynchronous RFCs (aRFCs) with responses.
If the LUW runtime of 1800 seconds is exceeded, the system assumes that the aRFC has terminated without a confirmation being sent. The connection is removed from the connection table (because no response is expected), but the LUW is still processed correctly without interruption.
If the LUW is still running, but responds to the calling program after more than 1800 seconds, it can no longer be handled and the runtime error CALL_FUNCTION_SEND_ERROR occurs.
You can change the scheduler's monitoring time to avoid the runtime error described above. The default value is 1800. It only makes sense to change this value to a value greater than 1800.
See also SAP Note 1065551.
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 711 |
