07/06/2016

AppendixQueuedRemoteFunctionCall(qRFC)SAPLibrary

TheBestRunBusinessesRunSAP

r3

Appendix

R/3noteno.37890325.01.2002
SetbyDuongHanTranon27.07.2001

ShorttextQueuestatusinSMQ1,SMQ2andtableARFCRSTATE

ResponsibleDuongHanTran
ComponentBCMIDRFCRFC
Causeandprerequisites

Solution:
DependingonthewayaLogicalUnitofWork(LUW)isprocessed,aninboundqueue,outbound
queueortableARFCRSTATE(statustableoftheLUWsinthetRFC/qRFCtargetsystem)canhave
differentstatuses.

Outboundqueue:
ThefollowingstatusesmaybedisplayedintransactionSMQ1:

READY
Thequeueisreadyfortransmission.Thisstatusshouldonlybeatemporarystatus.However,inthe
followingcasethisstatuscanalsobepermanent:Aqueuehasbeenlockedmanuallyviatransaction
SMQ1orviaaprogram,andthenunlockedwithoutbeingactivatedatthesametime.Thisqueue
mustbeactivatedexplicitly.

RUNNING
ThefirstLUWofthisqueueiscurrentlybeingprocessed.Ifaqueueinthisstatushangsformore
than30minutes,thismaymeanthattheworkprocessresponsibleforsendingthisLUWhasbeen
terminated.Inthiscaseyoucanactivatethisqueueagain.
NotethatactivatingaqueueinstatusRUNNINGmaycauseaLUWtobeexecutedseveraltimesif
thisLUWisstillbeingprocessedinthetargetsystematthattime.Wethereforerecommenda
waitingtimeofatleast30minutesbeforeyoureactivatethequeue.

EXECUTED

http://help.sap.com/saphelp_470/helpdata/en/ad/7b623c6374a865e10000000a11402f/content.htm

1/6

07/06/2016

AppendixQueuedRemoteFunctionCall(qRFC)SAPLibrary

ThefirstLUWofthisqueuehasbeenprocessed.ThesystemwaitsforaqRFCinternalconfirmation
fromthetargetsystembeforeprocessingfurtherLUWs.Ifaqueueinthisstatushangsformorethan
30minutes,thismaymeanthattheworkprocessresponsibleforsendingthisLUWhasbeen
terminated.IncontrasttostatusRUNNING,thiscurrentLUWhasdefinitelybeenexecuted
successfully.Youcanreactivatethisqueuewithoutanyproblems.TheqRFCManagerwill
automaticallydeletetheLUWalreadyexecutedandsendthenextLUW.

SYSLOAD
AtthetimeoftheqRFCcall,noDIALOGworkprocesseswerefreeinthesendingsystem.Abatch
jobforsendingtheLUWasynchronouslyhasalreadybeenscheduled(seenote319860formore
details).

SYSFAIL
AseriouserroroccurredinthetargetsystemwhilethefirstLUWofthisqueuewasexecuted.The
executionwasinterrupted.Whenyoudoubleclickonthisstatus,thesystemdisplaysanerrortext.
Formoreinformationonthiserror,seethecorrespondingshortdumpinthetargetsystem(ST22).No
batchjobisscheduledforarepetitionandthequeueisnolongerprocessed.Tosolvetheproblem,
informationfromtheaffectedapplicationisrequired.Seenote335162forthespecialerrortext
"connectionclosed".

CPICERR
DuringtransmissionorprocessingofthefirstLUWinthetargetsystem,anetworkorcommunication
erroroccurred.Whenyoudoubleclickonthisstatus,thesystemdisplaysanerrortext.Formore
informationonthiserror,seethesyslog(SM21),thetracefilesdev_rdordev_rfc*.Dependingonthe
definitionintransactionSM59forthedestinationused,abatchjobisscheduledforsubsequent
sending.StatusCPICERRmayalsoexistinthefollowingcasesalthoughnocommunicationerror
occurred:AqRFCapplicationfindsoutthataLUWcannotbeprocessedanyfurtherduetoa
temporaryerrorintheapplicationandthereforecallstheRESTART_OF_BACKGROUNDTASK
functionmoduletoprompttheqRFCManagertocanceltheexecutionofthisLUWandtorepeatthis
LUWlaterinaccordancewiththespecificationintransactionSM59.Inthiscase,qRFCsimulatesa
communicationerrorwiththetext"CommandtotRFC/qRFC:ExecuteLUWonceagain."Ifthiserror
occursveryoften,youmustcontactthecorrespondingapplication.

STOP
Onthisqueueoragenericqueue(forexampleBASIS_*)alockwassetexplicitly(SMQ1or
programs).NotethattheprocessingofqRFCneverlocksaqueue.Afterhavinginformedthe
correspondingapplication,youcanunlockandactivatethisqueueusingtransactionSMQ1.

WAITSTOP
ThefirstLUWofthisqueuehasdependenciestootherqueues,andatleastoneofthesequeuesis
currentlystilllocked.

WAITING

http://help.sap.com/saphelp_470/helpdata/en/ad/7b623c6374a865e10000000a11402f/content.htm

2/6

07/06/2016

AppendixQueuedRemoteFunctionCall(qRFC)SAPLibrary

ThefirstLUWofthisqueuehasdependenciestootherqueues,andatleastoneofthesequeues
currentlystillcontainsotherLUWswithhigherpriorities.

NOSEND
LUWsofthisqueueareneversentbutretrievedbyaspecialapplication.Thesequeuesareonly
usedinternallyatSAP(BWorCRMduringcommunicationwithMobileClients).EvenifaLUWhas
beenreadbythecorrespondingapplication(BW,CRM),thisstatusdoesnotchange.ThisLUWis
onlydeletedfromthequeueifthisapplicationconfirmscollection(collectiveconfirmationpossible).
UndernocircumstancesshouldthisstatusberesetusingtransactionSMQ1andthequeue
activated.

NOSENDS
DuringtheqRFCcall,theapplicationdeterminesatthesametimethatthecurrentLUWisnotsent
immediately.ThisisusedtodebugtheexecutionofanLUWviatransactionSMQ1.

WAITUPDA
ThisstatusissetifqRFCiscalledwithinatransactionthatalsocontainsoneormoreupdate
functions.Asaresultofthisstatus,theLUWandthusthequeueisblockeduntiltheupdatehas
beencompletedsuccessfully.Ifthisstatustakeslongerthanafewminutes,checkthestatusofthe
updateortheupdaterequestsusingtransactionSM13.Afterasuccessfulretroactiveupdate,the
blockedLUWissentautomatically.YoucanresetthisstatusintheqRFCMonitorSMQ1,and
reactivatethequeue.Notethatthiscanleadtopossibleinconsistenciesintheapplicationdata
betweenthetwosystems.

IfyouareusingReleases4.0x,4.5x,4.6Aor4.6B,andanupdatefunctionwiththe"collectiverun"
typeexistsinaLUW,anerrorinthekernelmaycausethisstatus.Thequeuealsohangsinthis
case.Thiserrorhasalreadybeencorrectedwithakernelpatch(seenote333878).

ARETRY
DuringLUWexecutiontheapplicationhasdiagnosedatemporaryproblemandhaspromptedthe
qRFCManagerinthesendingsystemviaaspecificqRFCcalltoscheduleabatchjobfora
repetitionbasedonthedefinitionintransactionSM59.

ANORETRY
DuringtheLUWexecution,theapplicationhasfoundaseriouserrorandpromptedtheqRFC
ManagerviaaspecificqRFCcalltocancelprocessingofthisLUW.Informationfromtheaffected
applicationisrequiredtosolvetheproblem.Tosolvetheproblem,informationfromtheaffected
applicationisrequired.

MODIFY
ProcessingthisqueueislockedtemporarilybecausetheLUWdataistemporarilybeingmodified.

http://help.sap.com/saphelp_470/helpdata/en/ad/7b623c6374a865e10000000a11402f/content.htm

3/6

07/06/2016

AppendixQueuedRemoteFunctionCall(qRFC)SAPLibrary

Inboundqueue:

ThefollowingstatusesmaybedisplayedintransactionSMQ2:

READY
Thequeueisreadyforprocessing.Thisstatusshouldonlybeatemporarystatus.However,inthe
followingcasethisstatuscanalsobepermanent:Aqueuehasbeenlockedmanuallyviatransaction
SMQ2orviaaprogram,andthenunlockedwithoutbeingactivatedatthesametime.Thisqueue
mustbeactivatedexplicitly.

RUNNING
ThefirstLUWofthisqueueiscurrentlybeingprocessed.Ifaqueueinthisstatushangsformore
than30minutes,thismaymeanthattheworkprocessresponsibleforprocessingthisLUWhasbeen
terminated.Inthiscaseyoucanactivatethisqueueagain.Notethatactivatingaqueueinstatus
RUNNINGmaycauseaLUWtobeexecutedseveraltimesifthisLUWisstillbeingprocessedinthe
targetsystematthattime.Wethereforerecommendawaitingtimeofatleast30minutesbeforeyou
reactivatethequeue.

SYSFAIL
AseriouserroroccurredwhilethefirstLUWofthisqueuewasbeingexecuted.Theexecutionwas
interrupted.Whenyoudoubleclickonthisstatus,thesystemdisplaysanerrortext.Formore
informationonthiserror,seethecorrespondingshortdumpinthetargetsystem(ST22).Nobatchjob
isscheduledforarepetitionandthequeueisnolongerprocessed.Tosolvetheproblem,information
fromtheaffectedapplicationisrequired.Seenote335162fortheerrortext"connectionclosed".

CPICERR
AnetworkorcommunicationerroroccurredwhilethefirstLUWwasbeingexecuted.Whenyou
doubleclickonthisstatus,thesystemdisplaysanerrortext.Formoreinformationonthiserror,see
thesyslog(SM21),thetracefilesdev_rdordev_rfc*.Dependingontheregistrationofthisqueue
(SMQR),abatchjobisscheduledforrepetition.Refertonote369524fortheerrortext"R/3logon
failed".StatusCPICERRmayalsoexistinthefollowingcasesalthoughnocommunicationerror
occurred:AqRFCapplicationfindsoutthataLUWcannotbeprocessedanyfurtherduetoa
temporaryerrorintheapplicationandthereforecallstheRESTART_OF_BACKGROUNDTASK
functionmoduletoprompttheqRFCManagertocanceltheexecutionofthisLUWandtorepeatthis
LUWlaterinaccordancewiththespecificationintransactionSM59.Inthiscase,qRFCsimulatesa
communicationerrorwiththetext"CommandtotRFC/qRFC:ExecuteLUWonceagain."Ifthiserror
occursveryoften,youmustcontactthecorrespondingapplication.

STOP
Onthisqueueoragenericqueue(forexampleBASIS_*)alockwassetexplicitly(SMQ2or
programs).NotethattheprocessingofqRFCneverlocksaqueue.Afterhavinginformedthe
correspondingapplication,youcanunlockthisqueueusingtransactionSMQ2.

http://help.sap.com/saphelp_470/helpdata/en/ad/7b623c6374a865e10000000a11402f/content.htm

4/6

07/06/2016

AppendixQueuedRemoteFunctionCall(qRFC)SAPLibrary

WAITSTOP
ThefirstLUWofthisqueuehasdependenciestootherqueues,andatleastoneofthesequeuesis
currentlystilllocked.

WAITING
ThefirstLUWofthisqueuehasdependenciestootherqueues,andatleastoneofthesequeues
currentlystillcontainsotherLUWswithhigherpriorities.

ARETRY
DuringLUWexecutiontheapplicationhasdiagnosedatemporaryproblemandhaspromptedthe
qRFCManagerviaaspecificqRFCcalltoscheduleabatchjobforarepetitionbasedonthe
registrationinSMQR.

ANORETRY
DuringtheLUWexecution,theapplicationhasfoundaseriouserrorandpromptedtheqRFC
ManagerviaaspecificqRFCcalltocancelprocessingofthisLUW.Informationfromtheaffected
applicationisrequiredtosolvetheproblem.Tosolvetheproblem,informationfromtheaffected
applicationisrequired.

MODIFY
ProcessingthisqueueislockedtemporarilybecausetheLUWdataistemporarilybeingmodified.

TableARFCRSTATE:

ThefollowingstatusesaredisplayedviatransactionSE16:

EXECUTED
TherelatedLUWiscompletelyexecutedinthetargetsystem.ThesystemwaitsforantRFC/qRFC
internalconfirmationfromthesendingsystembeforethisentryisdeleted.

HOLD
ThecorrespondingapplicationhasprocessedthisLUWinpartsandwantsthisLUWtonotbe
repeatedinthecaseofsubsequentnetworkorcommunicationerrors(seenote366869ifthereare
manyentrieswiththisstatus).

WCONFIRM
DuringaLUWexecutiontheapplicationhaspromptedthetRFC/qRFCManagertosetstatusHOLD.
IftheLUWexecutionhasalreadybeencompletedbutthisapplicationhasnotyetsignaledthelogical
LUWendandifthetRFC/qRFCinternalconfirmationfromthesendingsystemhasbeenreceived,
thenthisLUWreceivesstatusWCONFIRM.

http://help.sap.com/saphelp_470/helpdata/en/ad/7b623c6374a865e10000000a11402f/content.htm

5/6

07/06/2016

AppendixQueuedRemoteFunctionCall(qRFC)SAPLibrary

IftherespectiveapplicationinformsthetRFC/qRFCManageraboutthelogicalLUWend,thenthis
entryisdeleted(seealsonote366869formoredetails).

Sourcecodecorrections

Validreleases:

Noteisreleaseindependent

Linkstorelatednotes:

Number,Shorttext

0319860tRFC/qRFCImprovedperformanceafterSYSLOAD
0333878TransactionalRFCisnotexecuted
0335162"connectionclosed"errorintRFC/qRFCmonitors
0366869HOLD/EXECUTED/WCONFIRMentriesinARFCRSTATE
0369524qRFC:Errortext"R/3logonfailed"inSMQ2
0408837CRMMiddlewarerelatedqRFCqueues:LUWwithupdaterecords

C OPYR I GH T BY SAP SE OR AN SAPAF F I LI AT E C OM PAN Y. ALL R I GH T S R ESER VED .

PR I N T ED F R OM SAP H ELP POR TAL. (ht t p: / / help. s ap. c om )

http://help.sap.com/saphelp_470/helpdata/en/ad/7b623c6374a865e10000000a11402f/content.htm

6/6