3 Replies Latest reply: Apr 9, 2008 8:29 AM by N R Pradeep Reddy RSS

Settings for SMQS

Kushal Prajapati
Currently Being Moderated

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?






  • Re: Settings for SMQS
    Raj Kandula
    Currently Being Moderated

    Hi Kushal,


    Procedure For Registering a Destination


    Call transaction SMQS. On the initial screen, you see a list of previously registered destinations. To register a destination and add it to the list, choose Registration.


    When you choose Registration, a dialog box opens in which you can enter the required destination


    You can enter the following information:

    Destination – Enter the name of your destination.

    MAXCONN – Maximum number of connections

    MAXTIME – Maximum scheduler processing time for a destination in seconds (default is 60 seconds)

    You can use this setting to allocate more processing time to individual queues and restrict the processing time of others.

    NO_TRFC – This prevents tRFC LUWs from being processed by the Outbound Scheduler. This means that the tRFCs for this destination are then executed when the Commit Work is executed.


    You also have the following options, in addition to Registration:

    Register Without Activation: The queue is not triggered immediately by the Outbound Scheduler.

    Deregisters the destination. This means that the destination is not processed automatically by the scheduler, and must be started manually.

  • Re: Settings for SMQS
    N R Pradeep Reddy
    Currently Being Moderated

    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...



    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.





    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