Solution : https://service.sap.com/sap/support/notes/1500048 (SAP Service marketplace login required)
Summary :
In SAP transaction SMQR/SMQ2, an issue has been identified where certain READY queues are not processed efficiently, despite similar queues operating normally. This discrepancy is attributed to the configuration of the scheduling parameters within SMQR—Max. Runtime and Scheduler Monitoring. Typically set in seconds, these parameters dictate queue processing rules, but due to a program error, Scheduler Monitoring defaults to an incorrect 30 minutes, leading to premature exclusion of queues whose processing exceeds this period. The proposed resolution involves applying a patch to correct the monitoring time parameter, allowing users to adjust it above the default threshold of 1800 seconds to better meet their operational needs.
Key words :
running queues finish execution, scheduler monitoring parameter configured, queue processing time exceeds, inbound scheduler reason, scheduler monitoring time, terms inbound qrfc, transaction smqr/smq2, processing time, scheduler monitoring, inbound qrfc
Related Notes :
| 1593691 | Scheduler monitoring for outbound queue (qout) scheduler |
| 1497510 | Experiencing deadlocks, lock & waits in inbound processing |
| 1493644 | Long running process reading TRFCQIN blocking execution |
| 1485789 | QRFC: Long running processes in SM50 |
| 1456887 | Many processes select TRFCQIN with SAPLIRFC |
| 1324454 | qRFC scheduler is still set to WAITING status |