SMQS (QOUT Scheduler)

Hi All,
Using SMQS transaction I Scheduled a new Outbound scheduler in which TRFC queues were getting created. For QRFC queues  we can use SMQ1 to trace the volume of queues. Similar way how do we trace the volume and status of TRFC queues. Please advise.
Thanks,
Savitha.

HI,
You can use Transaction SM58 for the tRFC ..
Also look this for more-http://help.sap.com/saphelp_nw2004s/helpdata/en/f0/02a63b9bb3e035e10000000a114084/content.htm
Rgds,
Moorthy

Similar Messages

  • QOUT Scheduler stays inactive

    We are trying to activate the Standard tRFC Scheduling in BI 7.0. We attempted to use SMQS to activate the Scheduler. The Scheduler Status would change to STARTING and then change back to INACTIVE after we refreshed in a few seconds. We checked that the BW destination was a valid destination.
    For unknow reason the QOUT Scheduler won't activate. Any idea?

    Inactive does not mean that queue is inactive.It only means that at present Q(in/out) sceduler is not doing any thing now.(activating or deactivating)
    qRFC Monitor(QIN Scheduler)

  • Interaction between Qout scheduler and Integration engine

    Hello,
    I would like to understand more about the XI 3 architecture regarding the place of qRFC. If I understood right, depending on the QOS, the qOUT scheduler is used to send XML documents comming from the Integration Engine. The qOUT scheduler is able to process and queue rfc calls using traditional RFC ports (for example in case of CIF for APO). I imagine that in the case of XML message shipping, the qOUT scheduler is  called by the Integration Engine messaging logic layer. But then, I don't understand how outgoing SOAP calls occure. Are the queued RFC calls in destination of the local SOAP framework which uses the ICM to talk SOAP with the partner?
    Thanks for your lights,
    Christian.

    Thanks Holger for youor quick and precise answer,
    You mean, that the connection between the adapter framework and the integration engine is pure rfc based and not Soap-based XI protocol ?
    Is XI protocol used between the two engines each time no qRFC is envolved and in this case, the Abap-based Soap framework and the ICM are used by the integration logic layer of the central integration engine to communicate with the adapter engine ?
    Thanks,
    Christian.

  • SMQ1 purpose

    Hi,
    What is the purpose of cleaning the SMQ1,SMQ2,SMQS?
    While upgrading why it has to be deleted?
    Please let me know the reason. and if there we dont do, what will happen?
    Thanks in advance
    Savitha

    Hi,
    SMQ1:Out bound queue which is phisical storage of OUT bound delta(RSA7:delta queue),delta data will be saved in unstructured format
    SMQ2:Inbound queue,Where you can see data which is coming from other systems to your R3 system
    SMQS:QOUT scheduler where u can see the queue names which are connected to your R3 system like BI  snd someother systems which are geeting data from your R3 system
    SMQR:QIN sheduler where you can see the queues which are connected to your R3 system and from which you are pulling data to you R3 system like CRM for example your R3 system is getting updates from CRM system then CRM queue u can see in SMQR scheduler
    While upgrading your source system all systems will be cleared because Upgrade will be fast and u can avoid  data corruptions.
    somtimes data source structure will be changed because of upgrade ,so if u keep delta data it will  be corrupted and u will face delta load will failed and u will get dumps in RSA7 and to currect this error u have to delete delta data nd reintilize.
    to avoid above errors ,we have to clear delta data before upgrade.if u do this u will not miss any delta data and upgrade also will be fast.

  • CRM Monitoring T-codes

    Hi All,
    Can any of them help me in monitoring steps and T-code used while monitoring a CRM Server.
    Regards,
    Sandeep Singh

    Hi ,
    If you are looking for CRM Middleware monitoring T-Codes . Here are few :
    1) SMW01 -- Display Bdoc
    2) SMW02 - Display Bdoc summary
    3) To view the Unprocessed Bdoc Type in the sytem use : SMW03
    4) SMW20 - for Bdoc Procsing
    5) SMWMFLOW - Monitoring Message Flow
    For qrfc related monitroing check
    SMQR -- QIN Scheduler ( Inbound Queue checking )
    SMQS -- Qout Scheduler ( OutBound Queue checking )
    If you have to monitoe R&R queues use transaction : SMOHQUEUE
    Hope this helps
    Vinayak

  • Settings for SMQS

    Hi Everybody,
    What are the defaut settings for SMQS in R3 as well as BW. In our server the status is Inactive for all processes. And how to change or register?
    Thanks,
    Kush

    Hi Kushal,
    SMQS sttings in BW:
    In releases up to and including BW Service API 3.0C, data packages are transferred independently of any enhancements to outbound scheduling (QOUT scheduler) that have since been made available. Settings in the corresponding control transaction SMQS were not relevant. However, in some cases, it was necessary to explicitly deregister the BW destination (see SAP Note 673940).
    With BI Service API in Release SAP NetWeaver 7.0 (Plug-In-Basis 2005.1), you can (optionally) switch control of the transfer to the standardized outbound scheduling of the queued RFC. The approaches differ as follows:
    &#9679;      Connected BI system has Release <= 3.5
    Default remains unchanged. You perform the switch manually using the RSA1_TRFC_OPTION_SET program. (Prerequisite in Basis Release 4.6C is qRFC version 9 supplement 45.)
    Alternatively, the BW destination can be deregistered automatically.
    &#9679;      Connected BI system has Release >= SAP NetWeaver 7.0
    The default setting is changed; however, you can revert to the original setting using the program mentioned above.
    If you are using standardized outbound scheduling, the number of processes used to transfer data packages to the BI system has to be maintained for the BI destination in transaction SMQS.
    In this case, the global data transfer settings (see SAP Customizing Implementation Guide (transaction SPRO)--->Integration with Other SAP Components ---> Data Transfer to the SAP Business Information Warehouse ---> General Settings ---> Maintain Control Parameters for Data Transfer) only effect the number of processes that are used to transfer the data packages from the extraction process to the tRFC for the transfer.
    For regestering Go through...
    [http://help.sap.com/saphelp_nw70/helpdata/EN/af/d4fa40ee14f26fe10000000a1550b0/frameset.htm]
    When Your destination is registered and the queue status changes from INACTIVE to ACTIVE, if the queues contain LUWs that can be processed for this destination. WAITING and WAITCONN appear if the maximum number of connections has been reached or if the scheduler is waiting for a connection to become available again. As soon as a connection becomes available, the status changes to ACTIVE and the queue is processed.
    Regards,
    NR
    Edited by: N R Pradeep Reddy on Apr 9, 2008 7:27 AM
    Edited by: N R Pradeep Reddy on Apr 9, 2008 7:28 AM

  • What are the main transaction codes in XI?

    What are the main transaction codes in XI?

    SAP XI TRANSACTION CODES
    ALRTCATDEF- Alerts Configuration.
    ALRTDISP - Display of Alerts Created
    SXMB_IFR -> Start Integration Builder
    SXMB_MONI -> Integration Engine - Monitoring
    SXI_MONITOR -> XI: Message Monitoring
    SXI_CACHE -> To Access IS runtime cache
    SXI_SUPPORT -> Test all the Repository and Directory Objects
    SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter
    IDX2 -> idoc metadata
    IDX5 -> monitor idoc adapter
    SM21 -> log di sistema
    ST22 -> dump abap (analisi di eccezioni)
    SMQ1 -> messages inbound e outbound queue
    SMQ2 -> messages inbound e outbound queue
    SMICM -> J2EE administration
    ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.
    ST03 -> workload.
    SCC4 -> visualizza mandanti del sistema
    WE20 -> partner profiles
    sale - ale settings
    RZ10 - edit system profile
    SM59 ->mantain rfc destinations
    BD64 -> mantain distribution model (trasformazioni)
    SU01 -> users
    AL08 -> list all logged users(user login logon)
    SE10 -> Change Request
    SE09 -> Change Request
    WE05 -> All idocs
    WE19 -> IDoc Test Tool
    WE21 -> port definition
    SE11 -> Data dictionary
    SM21 -> log sistema xi
    se37 -> mantain funcion modules
    SICF -> http server configuration
    SMGW -> trace, alzare livello di trace.
    BD13 ->
    BD64 -> modelli di distribuzione
    PFCG -> Roles
    tabella TSTC -> sap transactions codes
    tabella TSTCT -> transaction descriptions
    STMS -> transports management
    SPAM -> apply ABAP support packages
    SPAU -> manage objects after apply support packages
    SE01 -> manage change requests
    SLDCHECK -> Test SLD Connection
    SLDAPICUST-> SLD API Customizing
    SXMB_ADM -> Integration Engine - Administration
    SXMB_MONI_BPE -> Process Engine - Monitoring
    SE38 -> ABAP Editor
    SE11 -> ABAP Dictionary
    ST22 -> ABAP dump analysis
    SPROXY-> ABAP Proxy Generation
    SE80 -> Object Navigator
    ABAPDOCU -> ABAP Documentation and Examples
    SE24-> Class Builder
    SM21-> Online System Log Analysis
    SMQ1-> qRFC Monitor (Outbound Queue)
    SMQ2-> qRFC Monitor (Inbound Queue)
    RZ70-> SLD Administration
    SM58-> Asynchronous RFC Error Log
    SM59-> RFC Destinations (Display/Maintain)
    SMICM-> ICM Monitor
    WE60-> Documentation for IDoc types
    BD87-> Status Monitor for ALE Messages
    IDX1-> Port Maintenance in IDoc Adapter
    IDX2-> Meta Data Overview in IDoc Adapter
    WE05-> IDoc Lists
    WE02-> Display IDoc
    WE19-> Test tool
    WE09-> Search for IDocs by Content
    WE20-> Partner Profiles
    WE21-> Port definition in XI
    SE16-> Data Browser
    SE93-> Maintain Transaction Codes
    SM30-> Call View Maintenance
    SU01-> User Maintenance
    SM02-> System Messages
    BD54 -Logical System Creation.
    SWXF_PBUILDER -> for Detail BPM Process
    SMQS - > to register the destination in QOUT scheduler
    WEOUTQUEUE - > to start the queue processing
    SMQR - > to register the queue
    IDXPW - > to activate the IDOC message package
    IDXP - > to monitor the message packages.
    SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes.
    http://www.erpgenie.com/abaptips/content/view/452/62/

  • Idocs not coming to XI

    Hi,
    In our landscape developers are trying to send Idoc from R/3 to XI system.
    We have created RFC_XI as RFC connection, which they are using to trigger IDoc from R/3 to XI. Now IDocs are getting triggered from R/3 without any error, but they are not coming to XI.
    Now when I checked Inbound queues in XI and found that all queues start with XBTI* are stuck with SYSFAIL error.
    Through SXMB_ADM I have tried to register and activate queue for XBTI* but it gives error as below:
    Error while activating queue XBTI*
    Message no. XMS_ADM610
    Can anyone help me regarding this so that IDocs can be processes between these systems.
    How can we see wats the issue while activating Queues?
    Is there anything else needs to be configured between these two systems?
    Thanks & Regards,
    Manish

    Hi,
    First of all thanks for so quick reply.
    I have checked at XI Side:
    In IDX2 in loaded meta data, two types of Idocs are showing
    ORDERS02 and CREMAS01
    In IDX1, Partner port and RFC have been configured.
    at R/3 side:
    RFC is checked its working fine.
    Using WE20 and WE21, Partner profile and port been configured already.
    In SMQS below is the status:
    <R/3 Client> RFC_XI                            R                 10          60      INACTIVE    0     <R/3 HOST NAME>
    Register the destination in QOUT scheduler (SMQS) and make it as active
    Destination is there (as per above) I hope entries are correct but its showing INACTIVE. How to activate it?
    Select the queue from WEOUTQUEUE transaction and start the queue processing; now you can see that your XI starts receiving the Idocs
    In WEOUTQUEUE when trying to see IDocs using Reciever Port as RFC_XI its showing nothing.
    While I checked sent IDoc status using WE05, previously it was taking port as RFC_XI for sent IDoc but now its taking port SAPID6 after I defined port in XI for R/3 using IDX1.
    For SYSFAIL Status, further message is as below:
    XI restart in qRFC not allowed
    Any more ideas or help? Will appreciate if anything step wise can be refer to check and rectify this error.
    Thanks & Regards
    Manish

  • XI and SAP --- & transactions

    HELLO EVERYONE,
    i have very stupid question with me but then also wanted to clear it.
    when i login in XI i have tcodes to do specific tasks and same is with any r/3 system.
    My doubt is with the IDOC list which we see in the XI side, e.g when i give we02 then it will give me IDOC list and same is with the SAP R/3 system also.
    Why XI has all these transactions ? when do we need to use we02 in XI??
    thanks,
    gaurav
    Message was edited by:
            gaurav sharma

    HI
    Below are the complete T-CODES which we use in SAP XI.
                 COMPLETE SAP XI TRANSACTION CODES
    ALRTCATDEF- Alerts Configuration.
    ALRTDISP - Display of Alerts Created
    SXMB_IFR -> Start Integration Builder
    SXMB_MONI -> Integration Engine - Monitoring
    SXI_MONITOR -> XI: Message Monitoring
    SXI_CACHE ->   To Access IS runtime cache
    SXI_SUPPORT -> Test all the Repository and Directory Objects
    SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter
    IDX2 -> idoc metadata
    IDX5 -> monitocr idoc adapter
    SM21 -> log di sistema
    ST22 -> dump abap (analisi di eccezioni)
    SMQ1 -> messages inbound e outbound queue
    SMQ2 -> messages inbound e outbound queue
    SMICM -> J2EE administration
    ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.
    ST03 -> workload.
    SCC4 -> visualizza mandanti del sistema
    WE20 -> partner profiles
    sale - ale settings
    RZ10 - edit system profile
    SM59 ->mantain rfc destinations
    BD64 -> mantain distribution model (trasformazioni)
    SU01 -> users
    AL08 -> list all logged users(user login logon)
    SE10 -> Change Request
    SE09 -> Change Request
    WE05 -> All idocs
    WE19 -> IDoc Test Tool
    WE21 -> port definition
    SE11 -> Data dictionary
    SM21 -> log sistema xi
    se37 -> mantain funcion modules
    SICF -> http server configuration
    SMGW -> trace, alzare livello di trace.
    BD13 ->
    BD64 -> modelli di distribuzione
    PFCG -> Roles
    tabella TSTC -> sap transactions codes
    tabella TSTCT -> transaction descriptions
    STMS -> transports management
    SPAM -> apply ABAP support packages
    SPAU -> manage objects after apply support packages
    SE01 -> manage change requests
    SLDCHECK -> Test SLD Connection
    SLDAPICUST-> SLD API Customizing
    SXMB_ADM -> Integration Engine - Administration
    SXMB_MONI_BPE -> Process Engine - Monitoring
    SE38 -> ABAP Editor
    SE11 -> ABAP Dictionary
    ST22 -> ABAP dump analysis
    SPROXY-> ABAP Proxy Generation
    SE80 -> Object Navigator
    ABAPDOCU -> ABAP Documentation and Examples
    SE24-> Class Builder
    SM21-> Online System Log Analysis
    SMQ1-> qRFC Monitor (Outbound Queue)
    SMQ2-> qRFC Monitor (Inbound Queue)
    RZ70-> SLD Administration
    SM58-> Asynchronous RFC Error Log
    SM59-> RFC Destinations (Display/Maintain)
    SMICM-> ICM Monitor
    WE60-> Documentation for IDoc types
    BD87-> Status Monitor for ALE Messages
    IDX1-> Port Maintenance in IDoc Adapter
    IDX2-> Meta Data Overview in IDoc Adapter
    WE05-> IDoc Lists
    WE02-> Display IDoc
    WE19-> Test tool
    WE09-> Search for IDocs by Content
    WE20-> Partner Profiles
    WE21-> Port definition in XI
    SE16-> Data Browser
    SE93-> Maintain Transaction Codes
    SM30-> Call View Maintenance
    SU01-> User Maintenance
    SM02-> System Messages
    BD54 -Logical System Creation.
    SWXF_PBUILDER -> for Detail BPM Process
    SMQS - > to register the destination in QOUT scheduler
    WEOUTQUEUE - > to start the queue processing
    SMQR - > to register the queue
    IDXPW - > to activate the IDOC message package
    IDXP - > to monitor the message packages.
    SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes
    Reward with points if found useful
    cheers

  • T.Codes for SAP XI 3.0

    Hi All,
    Can one give me all the SAP XI related transaction codes so that it will easy for me to learn SAP XI or any URL which will give me the same.
    Regards,
    Krushna Biswal

    Hi Krushna
    Following Tcode may Help you
    ALRTCATDEF- Alerts Configuration.
    ALRTDISP - Display of Alerts Created
    SXMB_IFR -> Start Integration Builder
    SXMB_MONI -> Integration Engine - Monitoring
    SXI_MONITOR -> XI: Message Monitoring
    SXI_CACHE -> To Access IS runtime cache
    SXI_SUPPORT -> Test all the Repository and Directory Objects
    SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter
    IDX2 -> idoc metadata
    IDX5 -> monitocr idoc adapter
    SM21 -> log di sistema
    ST22 -> dump abap (analisi di eccezioni)
    SMQ1 -> messages inbound e outbound queue
    SMQ2 -> messages inbound e outbound queue
    SMICM -> J2EE administration
    ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.
    ST03 -> workload.
    SCC4 -> visualizza mandanti del sistema
    WE20 -> partner profiles
    sale - ale settings
    RZ10 - edit system profile
    SM59 ->mantain rfc destinations
    BD64 -> mantain distribution model (trasformazioni)
    SU01 -> users
    AL08 -> list all logged users(user login logon)
    SE10 -> Change Request
    SE09 -> Change Request
    WE05 -> All idocs
    WE19 -> IDoc Test Tool
    WE21 -> port definition
    SE11 -> Data dictionary
    SM21 -> log sistema xi
    se37 -> mantain funcion modules
    SICF -> http server configuration
    SMGW -> trace, alzare livello di trace.
    BD13 ->
    BD64 -> modelli di distribuzione
    PFCG -> Roles
    tabella TSTC -> sap transactions codes
    tabella TSTCT -> transaction descriptions
    STMS -> transports management
    SPAM -> apply ABAP support packages
    SPAU -> manage objects after apply support packages
    SE01 -> manage change requests
    SLDCHECK -> Test SLD Connection
    SLDAPICUST-> SLD API Customizing
    SXMB_ADM -> Integration Engine - Administration
    SXMB_MONI_BPE -> Process Engine - Monitoring
    SE38 -> ABAP Editor
    SE11 -> ABAP Dictionary
    ST22 -> ABAP dump analysis
    SPROXY-> ABAP Proxy Generation
    SE80 -> Object Navigator
    ABAPDOCU -> ABAP Documentation and Examples
    SE24-> Class Builder
    SM21-> Online System Log Analysis
    SMQ1-> qRFC Monitor (Outbound Queue)
    SMQ2-> qRFC Monitor (Inbound Queue)
    RZ70-> SLD Administration
    SM58-> Asynchronous RFC Error Log
    SM59-> RFC Destinations (Display/Maintain)
    SMICM-> ICM Monitor
    WE60-> Documentation for IDoc types
    BD87-> Status Monitor for ALE Messages
    IDX1-> Port Maintenance in IDoc Adapter
    IDX2-> Meta Data Overview in IDoc Adapter
    WE05-> IDoc Lists
    WE02-> Display IDoc
    WE19-> Test tool
    WE09-> Search for IDocs by Content
    WE20-> Partner Profiles
    WE21-> Port definition in XI
    SE16-> Data Browser
    SE93-> Maintain Transaction Codes
    SM30-> Call View Maintenance
    SU01-> User Maintenance
    SM02-> System Messages
    BD54 -Logical System Creation.
    SWXF_PBUILDER -> for Detail BPM Process
    SMQS - > to register the destination in QOUT scheduler
    WEOUTQUEUE - > to start the queue processing
    SMQR - > to register the queue
    IDXPW - > to activate the IDOC message package
    IDXP - > to monitor the message packages.
    SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes.
    Thanks

  • Inbound queue in APO side

    hi,
    All R/3 changes are not transfered to APO. It got stuck in SMQ2 in APO side. every time i am manually activating  those queues in ready status.
    1) Is there  any simple way to activate all the queues having status "ready" in single execution.
    2) what will be the reason for inbound queue and how to avoid? i able to see only "ready" and "waiting" status queues there is no error

    Hi,
    Please check the status of the QIN and QOUT scheduler in transaction SMQR/SMQS and see if the destination is registered or not. I am pasting the content of the SAP Help for you quick reference.
    Set Up QOUT Scheduler
    Use
    Queued Remote Function Calls (qRFCs) are used to transfer data between SAP APO and SAP R/3. The QOUT scheduler processes outbound qRFCs (outbound queue).
    You complete the following steps in the relevant client in the production system.
    You call the QOUT scheduler using transaction SMQS. The destinations to which the outbound qRFCs are to be sent are registered in the QOUT scheduler. As of version 6.20.45 this is done automatically.
    The following options exist for a registered destination:
    Type
    R: The destination is registered, that is, it is started using the QOUT scheduler.
    U: The destination is not registered, that is, it is not processed.
    N: The destination is not processed using the QOUT scheduler, but is sent at the time of the COMMIT WORK.
    Max. Connections: Number of connections that are used to send the qRFCs. The default value is 10 for R/3 connections and 1 for TCP/IP connections.
    Max. Runtime: Time that a destination is processed by the QOUT scheduler. The default value is 60 seconds.
    The destination NONE means that the qRFCs are processed in the local system and should not be registered up to version 6.20.45, supplement 8 inclusive. As of supplement 9, NONE can be registered and the without tRFC option set.
    Requirements
    The qRFC configuration must be configured. For more information, see
    Set Up QOUT Scheduler
    Use
    Queued Remote Function Calls (qRFCs) are used to transfer data between SAP APO and SAP R/3. The QOUT scheduler processes outbound qRFCs (outbound queue).
    You complete the following steps in the relevant client in the production system.
    You call the QOUT scheduler using transaction SMQS. The destinations to which the outbound qRFCs are to be sent are registered in the QOUT scheduler. As of version 6.20.45 this is done automatically.
    The following options exist for a registered destination:
    Type
    R: The destination is registered, that is, it is started using the QOUT scheduler.
    U: The destination is not registered, that is, it is not processed.
    N: The destination is not processed using the QOUT scheduler, but is sent at the time of the COMMIT WORK.
    Max. Connections: Number of connections that are used to send the qRFCs. The default value is 10 for R/3 connections and 1 for TCP/IP connections.
    Max. Runtime: Time that a destination is processed by the QOUT scheduler. The default value is 60 seconds.
    The destination NONE means that the qRFCs are processed in the local system and should not be registered up to version 6.20.45, supplement 8 inclusive. As of supplement 9, NONE can be registered and the without tRFC option set.
    Requirements
    The qRFC configuration must be configured. For more information, see
    Regards,
    Senthilrajan
    Edited by: Senthil_APO on Oct 12, 2009 10:54 AM
    Edited by: Senthil_APO on Oct 12, 2009 10:55 AM

  • CIF Ques Stuck in READY State on R3 Inbound for no Reason

    Hi,
    Question pertains to CIF Processing and Ques waiting in READY State from R3 to SCM-APO for no Apparent Reason.
    Our Orders (PRs, STOs) generated via APO are being sent to R3 correctly, getting generated in R/3 but not coming back with the PR/STO Number back to APO.  Stuck in R3 inbound.
    I've read a couple of articles on SDN on this.
    Apart from the Standard CIF Configuration, and Settings in SMQR and SMQS (Qin & Qout Scheduler) for retrying Stuck Ques to be processed, is there anything else that can be looked at ?  Any Consulting Notes on this Topic ?
    SCM-APO version 4.0 on latest Support Pack.
    R3 4.6c and Plugin compatible. Not on most latest SP.
    Thanks,
    Ambrish Mathur

    Hai,
    Yes our Problem is resolved now.  The Solution was Technical in Nature and not functional  (as you can logically expect).
    Assuming your Basis Team has properly setup the QIN and QOUT Scheduler on BOTH sides (APO and R3) ...
    Also in QIN and QOUT the Time to RETRY a Que is set to something low as every 5 minutes and retry 10 times. 
    (However this was not the main issue for us).
    We found in our Case since the R3's Support Pack and Plug-In were not upgraded due to many depandancies to other Projects ... we found that the QRFC Versions on the R3 side were a few sub versions behind the APO QRFC Version since APO was on Latest Support Pack on SCM 4.
    The BASIS Group downloaded and Installed the Latest QRFC version and the Problem was subsequently resolved. 
    QRFC Version can be found in Transaction SMQ1 / SMQ2 -> Menu Path Information -> Version.
    We are now at QRFC ver. 6.30.060, Supplement # 11.
    Hope you find this usefull and it resolves your issue.  Do revert back if it does.
    Regards,
    Ambrish Mathur

  • Transacation codes

    Hello,
          I am new to SAP XI. So could you please tell me the transaction codes which we use in SAP XI. I know so many transaction codes were there, but at least which were important to note. And what are the main objects to learn.
    Thank you

    SAP XI TRANSACTION CODES
    ALRTCATDEF- Alerts Configuration.
    ALRTDISP - Display of Alerts Created
    SXMB_IFR -> Start Integration Builder
    SXMB_MONI -> Integration Engine - Monitoring
    SXI_MONITOR -> XI: Message Monitoring
    SXI_CACHE -> To Access IS runtime cache
    SXI_SUPPORT -> Test all the Repository and Directory Objects
    SXI_CACHE -> XI data directory cacheidx1 -> idoc adapter
    IDX2 -> idoc metadata
    IDX5 -> monitor idoc adapter
    SM21 -> log di sistema
    ST22 -> dump abap (analisi di eccezioni)
    SMQ1 -> messages inbound e outbound queue
    SMQ2 -> messages inbound e outbound queue
    SMICM -> J2EE administration
    ST06 -> stato della macchina cpu memory filesystem machine status - cpu, memory and file system.
    ST03 -> workload.
    SCC4 -> visualizza mandanti del sistema
    WE20 -> partner profiles
    sale - ale settings
    RZ10 - edit system profile
    SM59 ->mantain rfc destinations
    BD64 -> mantain distribution model (trasformazioni)
    SU01 -> users
    AL08 -> list all logged users(user login logon)
    SE10 -> Change Request
    SE09 -> Change Request
    WE05 -> All idocs
    WE19 -> IDoc Test Tool
    WE21 -> port definition
    SE11 -> Data dictionary
    SM21 -> log sistema xi
    se37 -> mantain funcion modules
    SICF -> http server configuration
    SMGW -> trace, alzare livello di trace.
    BD13 ->
    BD64 -> modelli di distribuzione
    PFCG -> Roles
    tabella TSTC -> sap transactions codes
    tabella TSTCT -> transaction descriptions
    STMS -> transports management
    SPAM -> apply ABAP support packages
    SPAU -> manage objects after apply support packages
    SE01 -> manage change requests
    SLDCHECK -> Test SLD Connection
    SLDAPICUST-> SLD API Customizing
    SXMB_ADM -> Integration Engine - Administration
    SXMB_MONI_BPE -> Process Engine - Monitoring
    SE38 -> ABAP Editor
    SE11 -> ABAP Dictionary
    ST22 -> ABAP dump analysis
    SPROXY-> ABAP Proxy Generation
    SE80 -> Object Navigator
    ABAPDOCU -> ABAP Documentation and Examples
    SE24-> Class Builder
    SM21-> Online System Log Analysis
    SMQ1-> qRFC Monitor (Outbound Queue)
    SMQ2-> qRFC Monitor (Inbound Queue)
    RZ70-> SLD Administration
    SM58-> Asynchronous RFC Error Log
    SM59-> RFC Destinations (Display/Maintain)
    SMICM-> ICM Monitor
    WE60-> Documentation for IDoc types
    BD87-> Status Monitor for ALE Messages
    IDX1-> Port Maintenance in IDoc Adapter
    IDX2-> Meta Data Overview in IDoc Adapter
    WE05-> IDoc Lists
    WE02-> Display IDoc
    WE19-> Test tool
    WE09-> Search for IDocs by Content
    WE20-> Partner Profiles
    WE21-> Port definition in XI
    SE16-> Data Browser
    SE93-> Maintain Transaction Codes
    SM30-> Call View Maintenance
    SU01-> User Maintenance
    SM02-> System Messages
    BD54 -Logical System Creation.
    SWXF_PBUILDER -> for Detail BPM Process
    SMQS - > to register the destination in QOUT scheduler
    WEOUTQUEUE - > to start the queue processing
    SMQR - > to register the queue
    IDXPW - > to activate the IDOC message package
    IDXP - > to monitor the message packages.
    SWF_XI_CUSTOMIZING -> transaction to check prerequisites for integration processes
    Catagory Listing:
    /people/morten.wittrock/blog/2006/03/23/getting-started-with-xi-part-1-xi-30-cheat-sheet
    regards,
    nikhil

  • Hostid in smqr ?

    Hi,
    What does host-id means in SMQR and SMQS  ??? Is it where the qin/qout scheduler is running ???
    Thank you.

    Hi,
    please have a look at SMQ1:
    http://help.sap.com/saphelp_nw04/helpdata/en/76/e12041c877f623e10000000a155106/content.htm
    It seems that there is a 'mapping' between the client and the destination possible.
    Perhaps some additional informations are helpful:
    http://help.sap.com/saphelp_nw04/helpdata/en/59/d9fa40ee14f26fe10000000a1550b0/content.htm
    best regards
    Jörg

  • Unable to generate Bdocs

    Hi
    When i create a BP from R/3 side,  no Bdoc is generated when i check it in CRM transaction SMW01.
    Is there any possiblity to check created BDOC in R/3 side itself?
    If not what would be the problem for non creation of BDOCs, this prevails only in sandbox and development but this works fine in quality.

    Hi Kranthi,
    Please check the filter settings maintained in t-code: R3AC1 for object CUSTOMER_MAIN.
    Check whether R/3 is activated as consumer in CRMCONSUM table in CRM.
    Check whether CRM is maintained in table CRMRFCPAR table in R/3.
    Check the QOUT scheduler on the R/3 side and confirm CRM is registered (SMQS).
    Check the Qin scheduler on the CRM side and confirm R3A* Queues are registered (SMQR).
    Check whether any Queues are failing on the R/3 outbound side (SMQ1)
    Check whether any Queues are failing on the CRM inbound side (SMQ2)
    Hope this helps you.
    Regards,
    DT

Maybe you are looking for