QRFC Monitor(Inbound Queue)

Hi Group,
Can any one please explain the purpose of qRFC Monitor, i mean from this what inforamtion we can monitor, and when this queue is filled..............
Thanks in Advance,
Regards
Ramakrishna Kamurthy

If youhave a look at this, it might be helpful
http://help.sap.com/saphelp_nw04/helpdata/en/0b/80f83b0255a206e10000000a11402f/frameset.htm
Assign points if useful

Similar Messages

  • Why i can't use SMQ2 to monitor inbound queue?

    i modified BP data in ECC. There should be R3AD_CUSTOMExxxxxxx(BP number) in inbound queue, but i can't find that.

    Helo,
    There would be queue entry waiting in R3AD_CUSTOME* queue only if you have de-registered this queue in txn:SMQR.
    Or else this queue entry would get processed automatically.
    Have you checked the BDoc in txn:SMW01to see whether detla changes from ECC is coming to CRM?
    Best Regards,
    Shanthala Kudva.

  • QRFC Monitor (Outbound Queue) Destination

    Hi Experts,
    In t-code SMQ1, there is no destination defined for the queue name "MCEX03". Although there are LUW entries in the same table column, but no records in rsa7.
    How can we input the destination name? Please advise.
    Regards.

    HI,
    MCEX jobs doesn't show any Destination as this job will process the LUW entries of extraction queue....
    i.e there'll be corresponding job running in SM37 for MCEX jobs periodically when this is successful the LUW entries from extraction queue will processed to delta queue i.e RSA7.
    For eg: if u chk the log of that particular job it'll show the no of LUW's entries moved from extraction queue to Delta Queue for that applciation component, in this case it is '03'.
    After every successful job if u monitor closely, the count of MCEX will be reduced and the count in Application component '03' will be increased.
    rgds,
    Edited by: Krishna Rao on Aug 15, 2009 5:30 PM

  • About qRFC Monitor (outbound queue)

    Hi Experts,
    we are upgrading the r/3 system from 4.6 to 4.7 and i am responsible for BW activities, i was asked to take care of the outbound queue what does that mean? and what needs to be done with this queue during r/3 upgrade? and there are some queues(in SMQ1) with destination None and entries 1 what are those???
    Does any one have the check list what needs to be done on the BW side during R/3 upgrade?
    Thanks in Advance.

    all the guides can be found on sapnet
    https://www010.sap-ag.de/instguides
    the particular guide for your particular upgrade is THE place to look for help.  it's very detailed w/ links to all the oss notes you need to review as well.

  • QRFC Monitor (Outbound queue)

    Hello friends,
    I have to delete and fill up the setup tables for the application 18. I have successfully deleted the data from the setup tables in LBWG. But when I am going to delete the entries in extraction queue(LBWQ), I find two queus for application 18. They are MCEX18 & MCEX18_1. Could you pls let me know the reason for the 2 entries. Should I delete both? Same is the case for allication 17.
    Thanks in advance.
    Vishwa

    Hi,
    The entries in LBWQ are those which have only been captured in outbound queues and have not reached RSA7. It is absolutely normal for them to have destination as NONE.
    Go to SMQ1, and execute, there you would find multiple entries for application 18
    e.g.
    Queue Name                                   Destination                      Entries
    BWXXX2LIS_18_I0NOTIF               BWCLNTXXX                      100
    BWXXX2LIS_18_I0TASK               BWCLNTXXX                       200
    MCEX18                                         NONE                                   2000
    The first two entries here are the ones which have already been processed from outbound queue to RSA7. Therefore now they have destination as BW system.
    Please check if here you get entries for 2 different BW systems. This may be the reason for 2 entries MCEX18 and MCEX18_1 in LBWQ.

  • QRFC Monitor in R/3

    Hey friends
    What is the transaction to go to the qRFC Monitor ( Outbound Queue ) in SAP R/3 system ?
    thanks

    Hi,
    SMQ1  is the Tcode.
    With rgds,
    Anil Kumar Sharma .P

  • Why XBTO* is visible in inbound queues monitor if it is an outbound queue

    Hi all,
    why XBTO* is visible in inbound queues monitor if it is an outbound queue?
    Any help will be really appreciated.
    Regards,
    Ivá

    Similar question...
    XBTO and XBTS Queues

  • Error in inbound queue

    Hi,
    I have to monitor queues, when i use tcode smq2 for inbound queues, i see 4 queues with stuck messages. The status  is sysfail, so i do like this edit-> reset status ,then the status of the message has changed to transaction recorded. now i went to previous page and click unlock. when checked the first message status, it is XI  restart in qRFC not allowed.
    Suggest me where i went wrong and what to do to solve the issue.
    Thanks
    Jhansi

    Dear Jhansi,
    in his answer Chirag exactly describes how to proceed in this situation. For further information on how to process failed XI messages you might also have a look at OSS note 813029.
    Best Regards,
    Harald Keimer
    XI Development Support
    SAP AG, Walldorf

  • Inbound queue

    Hi Guru's,
    I am still having problems with my inbound queue on the SRM system. The scenario is that XI sends a message to the SRM system, the messages comes in the queue of the SRM system but needs to be manually be processed.
    What tried to do is to use the transaction sxmb_adm and registered and actived all queue's, still now luck. How can I fix this?
    Hope some can help me out.
    Best regards,
    Guido Koopmann

    Hi Guido
    Go tcode "sxmb_adm" -> integration engine configuration.
    You will find Destination there.
    Go to tcode SM59 find whether that destination is working fine or not
    Register the queues via t.code sxmb_adm where u have an option manage ques.
    Once you register the queues, they default activated.
    If u want to manually unlock then u need to go to transaction SMQR,SMQ1,SMQ2 for queue management. There u have to select the queue and activated all entries.
    SMQ1 u2013 qRFC Monitor for the outbound queue You use this transaction to monitor the status of the LUWs in the outbound queue and restart any hanging queues manually.
    SMQ2 u2013 qRFC Monitor for the inbound queue. You use this transaction to monitor the status of the LUWs in the outbound queue.
    U may schedule the report RSQOWKEX (Outbound Queues) and RSQIWKEX (Inbound Queues) to restart the queues automatically.
    To Cancel the messages from MONI with the Status Scheduled for Outbound Process
    Schedule the Report RSXMB_CHECK_MSG_QUEUE
    SAP_BC_XMB_DELETE
    Regards
    Abhishek

  • Messages stuck in SMQ2 Inbound Queue.

    Scenario: File->XI->Proxy
    When I put 50 files at the same time in a directory, channel is configured Exactly Once in Order and we have created queue with the name GATQUEUE. The messages are picked up from directory and sent one by one to BPM process. 31 messages out of 50 poccesed succesfully but 19 of them get stuck in the queue always. Though GATQUEUE is released lately but they are stuck in 'XBQO$PE_WS90000013' queue. This is seen in SMQ2 Inbound Queue.
    Could you please tell me how to release this message which are already stuck and what bit of configuration required so that it works for 1000s of files/messages at a time?
    Thanks
    K

    Hi Kiran,
    Just add the below parameter in XI tcode : SXMB_ADM
       Execure Integration Engine and Configuration.
      Click on Specific Configuration, go to change mode
       Click on New entries
      Category : MONITOR
      Parameter :QRFC_RESTART_ALLOWED
      Current Value : 1
      Save.
    Regards,
    Venu.

  • Inbound Queues stuck with RFC errors

    Hi Experts,
    Greetings for the Day !
    We have BDOC related issue and we need your expert help ASAP in resolving the same.
    We ahev a few BDOCS lying in intermediate state in transaction SMW01, which we found using BDOC monitoring on daily basis. When we check the same in SMQR - inbound queue, we found that the queues are stuck with an RFC error message.
    We are re-activate these queues to actually resolve the intermediate bdocs. But, my query is
    1> The raeson for getting these BDOCS in intermediate state & stuck queues
    2> A permanent resolution for the same.
    Please help and  let us know if you need more details.
    Regards,
    Kanika

    Hi Kanika,
    RFC error can be due to a bad connection as well. If the server is down, there might be a problem in communication with the connected system and the queues will not be processed further. You need to reactivate or unlock to get the queues processed.
    But if there are any specific errors for which the queues are stuck do state the same, so that we can look into an actual resolution.
    Regards,
    Venkat

  • Inbound Queuing in SAP XI

    Hello Friends,
                       please help me on the below issue. my error is when i am sending 1000 messages from jms to jms through  SAP XI all the
    inbound queues are residing in smq2 . can i release all the queues at  a time once. please help me.

    Hi!
    As our SDN contributors already provided few links I  want t provide some information which is useful to you..
    NOTE: Also please try to send one by one or atlease few messages other than sending 1000 at at time
    I hope it will be useful to you in final case...because even I faced the same problem in BW- XI Integration but in those times I did the same... and also in final case if they restart the server once...all the messagse are gone I mean went to BW from XI by next day when I came there were no of messages
    But before doing this please note these points:::
    Even though you did this please make sure ...
    1. Actually First check what is your Service Pack..as you told that it is XI check are you using SP22...in
        XI 3.0
    2. Next check whether is it correct way to send 1000 messaegs at a time because may be your system  
        may be using some one and also if they are sending at the same time means...both of your queues wil
        be strucked..
    3 First Go to SMQ1 (Outbound queue) and SMQ2 (Inbound Queue)and check how many messaegs are
       there See also make sure the status of those queues some may be SYS FAIL means system fail first
       delete those queues and then RESEND the remaining queues...
    4.Also please go to RWB-->Communication monitoring and check your Communication Channel Status
        whether it was green or RED...and also check the AUDIT LOG..
    5. Suppose if any errors are there or not even though once go to RWB--MEssage Monitoring and check on
        which basis and on which part it was strucked I mean whether the partiular message fails at Integration
        Engine level or else ADapter Engine level... and finally Check AUdit log...on due to which basis the
        messages are queues I mean due to huge size... of for what reason..
    5.  Once do this if Still if you are facing same problem go to Transaction Code: SXI_CACHE and do cache
        refresh so that it may be reflected by refreshing all the IR and ID objects.
        Also do ADapter cache refresh...refresh in same Transaction code...
        Or else if you are adminstrator go to TCode : SMICM and go to MEnu--> As JAva and --> Do j2EE soft   
        Restart instead of Soft Restart...or else ask your basis poeple to do the same...
    Note: WHile doing J2EE engine restart please make sure any Transactions or else any one or working on PI because it may take 20-25 mins to become server up again ...
    NOTE: Also please try to send one by one or atlease few messages other than sending 1000 at at time
    I hope it will be useful to you in final case...
    I hope it will be useful to you in final case...Suppose if it is useful to you please close this and award points to the repective contributors if it is useful to you..
    Regards:
    Amar Srinivas ELi

  • XI inbound queues status "RETRY" in a new XI Production system

    Hi
    All the queues (XBT00* AND XBT02*) in XI Production system are not moving. Status is "Retry" all the time. The system is idle. Do you know what is happening here?
    I also see the following error in the queue:
    Command to tRFC/qRFC: Execute LUW again
    Also, lot of errors (below) in the system log (SM21):
    XIRWBUSER - Communication Error CPIC return code 027
    XIAPPLUSER - Perform rollback
    Any ideas?
    Regards
    Chandu

    Hi,
    When any message is sent from any other system to XI, the Inbound queue in XI is processed in the following way,
    1) AI_RUNTIME_JCOSERVER connects to the Java stack to execute the registered program AI_RUNTIME_<SID>.
    2) When this connection is fine, then the queue is processed without any issues.
    Now incase of Production system, which most likely to be a cluster system will fail because you'll find that AI_RUNTIME_JCOSERVER connection test fails, when you turn off one node. The reason being in visual administrator the JCo RFC Provider for the server nodes have not been maintained.
    Solution:
    Login to visual administrator, select the service JCo RFC Provider for both the nodes and set the value accordingly.
    Ex:
    SAP Cluster Virtual Name: XICLSTPROD
    Hostname1: XIPROD1
    Hostname2: XIPROD2
    SID: XIP
    CLIENT: 100
    Instance No: 02
    Values for Node1:
    Program Id: AI_RUNTIME_XIP
    Gateway host: XIPROD1
    Gateway service: sapgw02
    Server count: 20
    Application Server host: XICLSTPROD
    System number: 02
    Client: 100
    Language: EN
    User: PI_JCO_RFC
    Password: ***********
    Values for Node2:
    Program Id: AI_RUNTIME_XIP
    Gateway host: XIPROD2
    Gateway service: sapgw02
    Server count: 20
    Application Server host: XICLSTPROD
    System number: 02
    Client: 100
    Language: EN
    User: PI_JCO_RFC
    Password: ***********
    Change in the similar way for the other Programs registered.
    This should resovle the RETRY issue in Inbound queue.
    Hope this piece of information really helps.
    Regards,
    Kamesh

  • In SMQ1 (qRFC Monitor) status

    Hi,
    In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do these statuses mean? Which values in the field 'Status' mean what and which values are correct and which are alarming? Are the statuses BW-specific or generally valid in qRFC?
    Thanks,
    Pradeep

    Hey pradeep,
    Don't post the interview question over here.
    Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read once either in a delta request or in a repetition of the delta request. However, this does not mean that the record has successfully reached the BW yet. The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has been written into the DeltaQueue and will be loaded into the BW with the next delta request or a repetition of a delta. In any case only the statuses READ, READY and RECORDED in both tables are considered to be valid. The status EXECUTED in TRFCQOUT can occur temporarily. It is set before starting a DeltaExtraction for all records with status READ present at that time. The records with status EXECUTED are usually deleted from the queue in packages within a delta request directly after setting the status before extracting a new delta. If you see such records, it means that either a process which is confirming and deleting records which have been loaded into the BW is successfully running at the moment, or, if the records remain in the table for a longer period of time with status EXECUTED, it is likely that there are problems with deleting the records which have already been successfully been loaded into the BW. In this state, no more deltas are loaded into the BW. Every other status is an indicator for an error or an inconsistency. NOSEND in SMQ1 means nothing (see note 378903). The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
    Hopefully this is the correct answer that u were looking for your question
    Thanks,
    Om Ambulker

  • EWM : Error message in the in Inbound Queue

    During the creation of Inbound delivery in EWM through QRFC..the queue is stuck with an error message
    " Error accessing product data administration "Message no. /SCDL/AF032""..Please let me know if you have seen this issue earlier.
    ECC: Inbound delivery is created
    QRFC: Stuck in the queue and error message can be seen through SMQ2 transaction
    EWM: No IBN created because of the errored queue
    Thanks,
    Syed Ismail
    PS: Is there a way to create a new section for EWM queries so that they do not get mixed up with regular WM issues ?

    Thank you for your reply. The views are extended and i did look at the SCU set up and they seem to be good. Actually the scenario is that we had a system where all these processes were working fine in a client. A client copy was made to a new system and i am facing issues simulating in the new client.
    I faced an issue in the new system where the function module to create IDN and ID itself was not getting determined and it was because of logical system issue in EWM>Interfaces>ERP Integration>Goods movement>Map storage locations ERP and EWM..I have corrected and the queue gets processed now but i run into this new error.
    Will investigate a little more and see how it goes...
    I have checked out different settings but i was still not able to fid a solution..Did anybody see this kind of message earlier ?

Maybe you are looking for