Queue Status in SMQ2 and Table ARFCRSTATE 

Use

Depending on the way a Logical Unit of Work (LUW) is processed, an inbound queue or the table ARFCRSTATE (status table of the LUWs in the tRFC/qRFC target system) can have various statuses.

 

Inbound Queue

●      The following statuses may be displayed in transaction SMQ2:

●       

●      READY

●      The queue is ready for processing. This status should only be temporary. This status can be permanent, however, if a queue has been locked manually in transaction SMQ2 or in a program and then unlocked but not activated. This queue must be activated explicitly.

●       

●      RUNNING

●      The first LUW in this queue is currently being processed. If a queue with this status hangs for more than 30 minutes, the work process responsible for processing this LUW might have been terminated. If this is the case, you can activate this queue again. Note that activating a queue with status RUNNING may cause a LUW to be executed several times if this LUW is still being processed in the target system. We therefore recommend that you wait at least 30 minutes before reactivating the queue.

●       

●      SYSFAIL

●      A serious error has occurred during execution of the LUW in this queue. Execution has been stopped. By double-clicking the status, you can view an error text. You can find more information about this error in its short dump (ST22). No background jobs are scheduled for a retry, and the queue is not processed any further. To solve the problem, you need to inform the relevant application. See SAP Note 335162 for the error text "connection closed".

●       

●      CPICERR

●      A network or communication has error occurred during execution of the first LUW. By double-clicking the status, you can view an error text. You can find more information about this error in the syslog (SM21) and in the trace files dev_rd or dev_rfc*. Depending on how the queue was registered (SMQR), a batch job might be scheduled for retry. See SAP Note 369524 for the error text "connection closed". Status CPICERR can also occur in the following cases, event though no communication errors have occurred: A qRFC application finds out that a LUW cannot be processed due to a temporary error in the application. It therefore calls the RESTART_OF_BACKGROUNDTASK function module to prompt the qRFC Manager to cancel the execution of this LUW and to repeat this LUW later in accordance with the settings in transaction SM59. qRFC then simulates a communication error with the text "Command to tRFC/qRFC: Execute LUW once again." If this error occurs regularly, you need to contact the relevant application.

●       

●      STOP

●      A lock has been set explicitly (SMQ2 or programs) on this queue or on a generic queue (such as BASIS_*) . The qRFC never locks a queue during processing. Once you have informed the relevant application, you can unlock this queue using transaction SMQ2.

●       

●      WAITSTOP

●      The first LUW in this queue has dependencies with other queues, and at least one of these queues is currently still locked.

●       

●      WAITING

●      The first LUW of this queue has dependencies with other queues, and at least one of these queues currently still contains other LUWs with higher priorities.

●       

●      ARETRY

●      The application diagnosed a temporary problem while processing the LUW and has used a specific qRFC call to prompt the qRFC Manager to schedule a background job for a retry, using the registration in SMQR.

●       

●      ANORETRY

●      The application diagnosed a serious error while processing the LUW and has used a specific qRFC call to prompt the qRFC Manager to stop processing this LUW. To solve the problem, you need to inform the relevant application.

●       

●      MODIFY

●      Processing of this queue is locked temporarily because the LUW data is being modified.

●       

Table ARFCRSTATE

●      You can use transaction SE16 to display the status:

●       

●      EXECUTED

●      Execution of the related LUW has been completed in the target system. The system waits for an internal tRFC/qRFC confirmation from the sending system before this entry is deleted.

●       

●      HOLD

●      The corresponding application has processed this LUW in part and does not want it to be retried if subsequent network or communication errors occur (see SAP Note 366869 if a large number of entries have this status).

●       

●      WCONFIRM

●      During execution of a LUW, the application has prompted the tRFC/qRFC Manager to set status HOLD. If execution of the LUW execution has already been completed, but the application has not yet signaled the logical LUW end, and the tRFC/qRFC-internal confirmation has been received from the sending system, the LUW has the status WCONFIRM.

●      If the relevant application informs the tRFC/qRFC Manager about the logical LUW end, this entry is deleted (see SAP Note 366869 for more details).