CIF Queue STATUS

Outbound Queue STATUS
Please also refer to SAP note 378903.
READY
The queue is ready for transmission. This status should only be a temporary status. However, in the
following case this status can also be a permanent status: a queue was locked manually via transaction
SMQ1 or via a program and then unlocked without being activated at the same time. This queue must
be activated explicitly.
RUNNING
The first LUW of this queue is currently being processed. If a queue in this STATUS hangs for more
than 30 minutes, this may mean that the work process responsible for sending this LUW has terminated.
In this case you can activate this queue again. Note that activating a queue in status RUNNING may
cause a LUW to be executed several times if this LUW is processed in the target system at that time.
We therefore recommend a waiting time of at least 30 minutes before you activate the queue again.
EXECUTED
The first LUW of this queue is processed. The system waits for a qRFC-internal confirmation from the
target system before further LUWs are processed. If a queue in this STATUS hangs for more than 30
minutes, this might mean that the work process responsible for sending this LUW has terminated. In
contrast to status RUNNING, this current LUW has definitely been executed successfully. You can activate this queue again without problems. The qRFC Manager will automatically delete the LUW
already executed and send the next LUW.
SYSLOAD
At the time of the qRFC call, no DIALOG work processes were free in the sending system for sending
the LUW asynchronously. A batch job for subsequent sending has already been scheduled (see SAP
Note 319860 for more details).
SYSFAIL
A serious error occurred in the target system while the first LUW of this queue was executed. The
execution was interrupted. When you double-click on this status, the system displays an error text. You
can find additional information on this error in the corresponding short dump in the target system (ST22).
No batch job is scheduled for a repetition and the queue is no longer processed. To solve the problem,
information from the affected application is required. Refer to SAP Note 335162 for the special error text
"connection closed".
CPICERR
During transmission or processing of the first LUW in the target system, a network or communication
error occurred. When you double-click on this status, the system displays an error text. You can find
additional information on this error in the syslog (SM21), the trace files dev_rd or dev_rfc*. Depending
on the definition in transaction SM59 for the destination used. A batch job is scheduled for subsequent
sending. Status CPICERR may also exist in the following cases although no communication error
occurred: a qRFC application finds out that a LUW cannot be processed any further due to a temporary
error in the application and 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 specification in transaction SM59.In this case, qRFC simulates a communication
error with the text "Command to tRFC/qRFC: Execute LUW once again." If this error occurs very often,
you must contact the corresponding application team.
STOP
On this queue or a generic queue (for example BASIS_*) a lock was set explicitly (SMQ1 or programs).
Note that the qRFC never locks a queue in its processing. After having informed the corresponding
application team, you can unlock and activate this queue using transaction SMQ1.
WAITSTOP
The first LUW of this queue has dependencies to other queues, and at least one of these queues is
currently still locked.
WAITING
The first LUW of this queue has dependencies to other queues, and at least one of these queues
contains other LUWs with higher priorities.
NOSEND
LUWs of this queue are never sent but retrieved by a special application. These queues are only used
internally at SAP (BW or CRM during communication with Mobile Clients). Even if a LUW was read by
the corresponding application (BW, CRM), this status does not change. This LUW is only deleted from
the queue if this application confirms collection (collective confirmation possible). Under no
circumstances should this status be reset using transaction SMQ1 and the queue activated.
NOSENDS
During the qRFC call, the application determines at the same time that the current LUW is not sent
immediately. This is used to debug the execution of an LUW via transaction SMQ1. Contact the
corresponding qRFC application to clarify this status since this is either a programming or configuration
problem.
WAITUPDA
This status is set if qRFC is called within a transaction that also contains one or more update functions.
As a result of this status, the LUW and thus the queue is blocked until the update has been completed
successfully. If this status takes longer than a few minutes, check the status of the update or the update
requests using transaction SM13. After a successful retroactive update, the blocked LUW is sent
automatically. You can also restart the LUWs manually in the WAITUPDA status without a successful
retroactive update (via transaction SMQ1, Reset status, Activate queue). However, you may only
perform this action after having informed the qRFC application (for example, APO, BW, CRM). You must
do this to avoid possible inconsistencies. This WAITUPDA problem may be avoided as follows: If both
qRFC calls and update calls occur within a transaction, qRFC must be executed exclusively within the
update. In this case, the qRFC LUW is only created after the update has been completed successfully.
Caution: If you are using SAP Basis Releases 4.0x, 4.5x, 4.6A or 4.6B, and an update function with the
"collective run" type exists in a LUW, an error in the kernel may cause this status. The queue also hangs
in this case. This error has already been corrected with a kernel patch (see SAP Note 333878).
RETRY / ARETRY
During LUW execution the application has diagnosed a temporary problem and has prompted the qRFC
Manager in the sending system via a specific qRFC call to schedule a batch job for a repetition on the
basis of the definition in transaction SM59 (Menu: Destination > TRFC Options)
ANORETRY
During the LUW execution, the application has found a serious error and prompted the qRFC Manager
via a specific qRFC call to cancel processing of this LUW. Information from the affected application is
required to solve the problem.
MODIFY
Processing this queue is locked temporarily because the LUW data is being modified.
Remark: Report RSQOWKEX reset the status of all queues (CPICERR, RETRY, SYSFAIL) and
restarts the outbound scheduler. This report can be used in exceptional cases; do not schedule this
report on regular basis, investigate the error before restarting the queue.

Inbound Queue STATUS
Please also refer to SAP note 378903.
READY
The queue is ready for processing. This status should only be a temporary status. However, in the
following case this status can also be a permanent status: a queue was locked manually via transaction
SMQ2 or via a program and then unlocked without being activated at the same time. This queue must
be activated explicitly.
RUNNING
The first LUW of this queue is currently being processed. If a queue in this status hangs for more than
30 minutes, this may mean that the work process responsible for sending this LUW has terminated. In
this case you can activate this queue again. Note that activating a queue in status RUNNING may cause
a LUW to be executed several times if this LUW is processed in the target system at that time. We
therefore recommend a waiting time of at least 30 minutes before you activate the queue again.
SYSFAIL
A serious error occurred in the target system while the first LUW of this queue was executed. The
execution was interrupted. When you double-click on this status, the system displays an error text. You
can find additional information on this error in the corresponding short dump in the target system
(ST22).No batch job is scheduled for a repetition and the queue is no longer processed. Information
from the affected application is required to solve the problem. Refer to SAP Note 335162 for the special
error text "connection closed".
CPICERR
During transmission or processing of the first LUW in the target system, a network or communication
error occurred. When you double-click on this status, the system displays an error text. You can find
additional information on this error in the syslog (SM21), the trace files dev_rd or dev_rfc*. Depending
on the registration of this queue (SMQR) a batch job is scheduled for repetition. Refer to SAP Note
369524 for the error text "R/3 logon failed". Status CPICERR may also exist in the following cases
although no communication error occurred: a qRFC application finds out that a LUW cannot be
processed any further due to a temporary error in the application and therefore calls the
RESTART_OF_BACKGROUNDTASK function module in order to prompt the qRFC Manager to cancel
the execution of this LUW and to repeat this LUW later in accordance with the specification in
transaction SM59.In this case, qRFC simulates a communication error with the text "Command to
tRFC/qRFC: Execute LUW once again.". If this error occurs very often, you must contact the
corresponding application team.
STOP
On this queue or a generic queue (for example, BASIS_*) a lock was set explicitly (SMQ2 or programs).
Note that the qRFC never locks a queue in its processing. After having informed the corresponding
application team you can unlock and activate this queue using transaction SMQ2.
WAITSTOP
The first LUW of this queue has dependencies to other queues, and at least one of these queues is
currently still locked.
WAITING
The first LUW of this queue has dependencies to other queues, and at least one of these queues
contains other LUWs with higher priorities.
NOEXEC
During the qRFC call, the application team simultaneously determines that the current LUW is not
processed automatically even if the queue to the QIN Scheduler (SMQR) is registered. This is used to
debug the execution of an LUW via transaction SMQ2. Contact the corresponding qRFC application to
clarify this status since this is either a programming or configuration problem.
RETRY
During LUW execution, the application has diagnosed a temporary problem and has used a specific
qRFC call to prompt the qRFC manager in the sending system to schedule a batch job. This batch job
schedules a repetition after two minutes.
ARETRY
During LUW execution the application has diagnosed a temporary problem and has prompted the qRFC
Manager in the sending system via a specific qRFC call to schedule a batch job for a repetition on the
basis of the registration in transaction SMQR.
ANORETRY
During the LUW execution, the application has found a serious error and prompted the qRFC Manager
via a specific qRFC call to cancel processing of this LUW. Information from the affected application is
required to solve the problem.
MODIFY
Processing this queue is locked temporarily because the LUW data is being modified. 


Source:CIF cookbook.