Show TOC

Registering/Deregistering a DestinationLocate this document in the navigation structure


Registering Destinations

To register a logical destination manually, proceed as follows:

  1. Call transaction SMQS.

  2. Select the Registration pushbutton and maintain the values for the specified fields:

    • Destination: Enter the name of your destination.

    • Max. Conn: Maximum number of connections.

    • Max. Time: 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.

    • Without tRFC: This prevents tRFC LUWs from being processed by the QOUT Scheduler. This means that the tRFCs for this destination are then executed when the Commit Work is executed.

    • Scheduler Monitoring: Timeout value (in seconds) for queue monitoring by the scheduler The runtime of LUWs is restricted to 1800 seconds to prevent the scheduler from being blocked by too many terminated asynchronous RFCs (aRFCs) with responses. by changing this value (> 1800 seconds), you can increase the runtime if necessary to prevent a runtime error ( CALL_FUNCTION_SEND_ERROR).


      As soon as a LUW with a registered destination has been created, the QOUT Scheduler in this client is activated automatically by the qRFC Manager, if it was not already active. You can also activate the QOUT Scheduler manually for the current client.

      When you register a destination but do not want to activate it at the same time, choose Registration Without Activation instead of Registration.

After registration the queue status changes from INACTIVE to ACTIVE, if the queues contain LUWs that can be processed for this destination.

If no free connection is available then either the status WAITING or WAITCONN is shown. As soon as a connection becomes available, the status changes to ACTIVE and the queue is processed.

Deregistering Destinations

You can prevent immediate transfer of the tRFC/qRFC LUWs by deregistering a destination in SMQS.


It is not enough to delete the registration here because the destination is registered again automatically after the next tRFC/qRFC call if the client, user, password, and language have been maintained in transaction SM59.

You can register the destination again on the QOUT Scheduler using transaction SMQS at a later time.

Follow the procedure below:

  1. Call transaction SMQS.

  2. Select the destination that you want to deregister and choose Deregister.

  3. Confirm the deregistration in the subsequent pop-up window using Enter.