Ahout the F:TRFC_SET_QIN_PROPERTIES and TRFC_SET_QUEUE_NAMEu3000

Question

hi forks,
  when we do qRFC  sometimes we use the FF:TRFC_SET_QIN_PROPERTIES
and sometimes we use the F: TRFC_SET_QUEUE_NAME　
so can anybody tell the difference between them
as detail as wish
thanks in advance
bestregards

Answer 1

qRFC API for the Inbound Queue
API for Queue Management
1)   TRFC_SET_QIN_PROPERTIES:
You use this function module to transfer an outbound queue name, an inbound queue name, and optionally a queue counter, to the qRFC Manager.  These parameters are only valid for the next “Call Function in Background Task”. The outbound queue and the inbound queue can have the same queue name.
See also the program RSTRFCT5.
2)   TRFC_GET_QIN_INFO and TRFC_GET_QIN_INFO_DETAILS
You use these function modules to read the current content of one or all of the inbound queues.
See also the program RSTRFCIR.
3)   TRFC_QIN_GET_CURRENT_PARAM
You use this function module to obtain information about the inbound queues, such as queue name, queue counter, and queue counter assignment for the current LUW. You need this information if you use the “re-use” function in qRFC with inbound queue.
4)   TRFC_QIN_STOP
·        You use this function if you specify a queue name to stop processing of one or more queues (single or generic, for example BASIS_TEST_*)
·        If the importing parameter FORCE is changed to SPACE, the qRFC Manager only processes LUWs that exist in the queue at STOP time. Otherwise, the qRFC Manager stops the processing immediately.
·        A STOP counter counts the number of STOP calls.
·        You can also stop an empty (non-existent) queue. In this situation, all the LUWs assigned to this queue are saved in the qRFC tables.
See also the program RSTRFCI1.
5)   TRFC_QIN_ACTIVATE
·        You use this function module if you want to specify a queue name (single or generic, for example BASIS_TEST_*) to stop the processing of one or more queues. You should only use this function if the queue is blocked due to a communication error, or if a system or application exception has occurred and the problem has been solved.  You can also use it if the LUWs have been saved in the inbound queue and need to be reactivated.
·        A queue that has been blocked by calling the function TRFC_QIN_STOP cannot be processed using this function.
·        If you set the import parameter MAXLUW to a value not equal to 0, the qRFC Manager activates all LUWs in the inbound queue.
·        If you set the import parameter MAXTIME to a value not equal to 0 (0= unrestricted; the call is returned once the queue is empty), the qRFC Manager only activates the queue within the specified time. If the time runs out while the last LUW is being processed, this call is returned after the last LUW.
·        If you change the import parameter MODE to 'B', the qRFC Manager activates the queue (executes the qRFC LUWs) in a BATCH task. The import parameters for starting this batch job are optional (default setting: immediate start).
·        If you change the import parameter MODE to ‘L’, the qRFC Manager processes all qRFC LUWs in a queue in the context of the caller. If an exception occurs in a function module in this queue, this results in a short dump because the qRFC Manager cannot detect the exception in this session.
·        If you set the import parameter USERDEST to a "local" RFC destination (for example, a logical destination with NONE or SPACE as a reference destination) in SM59, the qRFC Manager processes all qRFC LUWs in a queue under the user who is currently logged on. If no destination is entered, or the user has not been defined, the current user is used.
See also the program RSTRFCI0.
6)   TRFC_QIN_RESTART
·        You use this function module if you want to specify a queue name (single or generic, for example BASIS_TEST_*) to continue processing one or more queues, regardless of whether or not these queues have previously been stopped.
·        If you change the import parameter FORCE to SPACE, the qRFC Manager reduces the STOP counter and, if the counter is on 0, activates the queue. Otherwise, the qRFC Manager will always activate the queue, whatever the status of the STOP counter.
·        If you set the import parameter MAXLUW to a value not equal to 0, the qRFC Manager activates all LUWs in the inbound queue.
·        If a queue has been stopped, use this call and not TRFC_QIN_ACTIVATE.
·        If you change the importing parameter NO_ACTIVATE to ‘X’, the qRFC Manager “unlocks” the queue, but does not activate it.
·        If you set the import parameter MAXTIME to a value not equal to 0 (0= unrestricted; the call is returned once the queue is empty), the qRFC Manager only activates the queue within the specified time. If the time runs out while the last LUW is being processed, this call is returned after the last LUW is processed.
·        If you set the import parameter MODE to 'B', the qRFC Manager activates the queue (processes the qRFC LUWs) in a BATCH task. The import parameters for starting this batch job are optional. The default setting is immediate start.
·        If you change the import parameter MODE to ‘L’, the qRFC Manager processes all qRFC LUWs in a queue in the context of the caller. If a function module in this queue resolves an exception, this results in a short dump because the qRFC Manager cannot detect the exception in this session.
·        If you set the import parameter USERDEST to a "local" RFC destination (for example, a logical destination with NONE or SPACE as a reference destination) in SM59, the qRFC Manager processes all qRFC LUWs in a queue under the user who is currently logged on. If no destination has been entered, or the user has not been defined, the current user is used.
See also RSTRFCI3.
7)   TRFC_QIN_RESTART_COND
·        You use this function module if you specify a queue name, or a “high priority” queue name (single or generic, for example BASIS_TEST_*) for restarting one or more queues.
·        If you change the import parameter TILL_STOP to SPACE, the qRFC Manager restarts the queue once the "high priority" queue is empty. Otherwise the queue is restarted when the “high priority” queue has been stopped or is empty.
·        If no other STOP call has been scheduled, calling this function using TILL_STOP = SPACE automatically ends the queue at the time of the call.
See also RSTRFCI4.
8)   TRFC_QIN_STATE
·        You use this function module when you enter the queue name, destination, and optionally the SAP client, to display the status of the queue.
·        A queue has the following possible statuses: READY, CPICERR, SYSFAIL, STOP, WAITSTOP, and WAITING.
·        The status SYSFAIL results from a serious system error, and is caused by a system exception or application exception while the current LUW is being processed in the target system. In this situation, the queue is blocked, and automatic restart is not possible. You can use the program RSTRFCI0 to reactivate the LUW, or use the program RSTRFCID to delete the qRFC LUW.
·        In status CPICERR, there is also no automatic retry. This error can only occur if the SAP Gateway on the local application server is out of order. Use RSTRFCI0 to restart the queue after the Gateway problem has been resolved.
·        If the queue has the status WAITSTOP or WAITING, the exporting parameter WQNAME displays which queue the current queue is waiting for before it is processed.
See also RSTRFCI2.
9)   TRFC_QIN_OVERVIEW
You use this function module for an overview of all the inbound queues that currently exist. These can have various optional import parameters, for example, queue name or SAP client.
10)  TRFC_QIN_DELETE_LUW
You use this function module to delete the LUW from an inbound queue that is defined by the import parameter TID.
11)  TRFC_QIN_DELETE_QUEUE
You use this function module to delete all the inbound queues defined by the import parameter QNAME.
12)  TRFC_QIN_SAVE_CURRENT_LUW
You use this function module during the execution of a function module from a LUW, to inform the qRFC Manager to save the current LUW after successful processing (for re-use).
13)  TRFC_QINS_RESTORE
You use this function module if you want the qRFC Manager to restore one or all of the saved LUWs defined by the import parameters QNAME and FROM_COUNT.
14)  TRFC_QINS_ERASE
You use this function module if you want the qRFC Manager to delete one or all of the saved LUWs defined by the import parameters QNAME and FROM_COUNT.
15)  TRFC_QINS_OVERVIEW
You use this function module for an overview of all the saved inbound queues that currently exist (for various optional import parameters, such as queue name, SAP client).
16)  TRFC_QINS_DELETE_LUW
You use this function module to delete the LUW defined by the parameter TID from a saved inbound queue.
17)  TRFC_QINS_DELETE_QUEUE
You use this function module to delete all the inbound queues defined by the import parameter QNAME.
18)  TRFC_RECEIVER_INFO
You use this function module to obtain information from the sender of a tRFC or qRFC LUW (for example TID, client, user, host name of the application server, program name, or transaction code). You can also use this function module to determine whether a function module has been sent by tRFC or qRFC with inbound queue.
19)  TRFC_QIN_GET_HANGING_QUEUES
·        This function displays all blocked queues, including the queues that the application has intentionally written in the queue for later processing and have the status WAITING.
·        This function also displays all queues that have the status WAITING. To display only the queues with errors, use the function module TRFC_QIN_GET_ERROR_QUEUES described in 22).
20)  TRFC_QIN_GET_FIRST_LUW
This function displays information (such as the TID) for the first LUW in a queue.
21)  TRFC_QIN_GET_CURRENT_QUEUES
This function displays all the queues that currently exist.
22)  TRFC_QIN_GET_ERROR_QUEUES
·        This function module displays all queues that are blocked due to one of the following errors: SYSFAIL, CPICERR, RETRY, ARETRY, ANORETRY.
·        Queues that have the status WAITING are not displayed.