There is a call sequence for using logon data:
1. If logon data is maintained in the destination (transaction SM59), then this is used now.
2. If no logon data is entered, the user data (including the language, client, and username) of the calling user is used.
3. If logon data is not maintained completely in the destination, the data that is available is used as logon data for processing. The current data of the calling user (language, client, user) is used for all logon data that is missing.
When processing qRFC/tRFC calls using the QIN or QOUT Scheduler, in specific situations it can, however, occur that the qRFC/tRFC is processed under logon data that was not specified using the destination or calling user.
If the destination scheduler is running under another user at the point when a LUW (n+1) is called and if no logon data is maintained in the destination, subsequent LUWs are executed in the QOUT Scheduler using the logon data of a previous user. In this case, the destination scheduler runs under the user that started the scheduler. It also runs under this user's language and user name. In this case, the destination scheduler and the processing of the subsequent LUW are therefore executed with the wrong logon data.
To ensure that all started LUWs in a queue are processes under a specifically-defined user in the QIN Scheduler, you can create a logical destination that is referenced in the QIN Scheduler (transaction SMQR)
If no logical destination is defined for a queue, it is possible that a subsequent LUW in a queue is executed under other logon data, for example, if different users use the same queue.
To define a logical destination, proceed as follows:
4. Select Transaction SM59.
5. Create a logical destination (destination type L).
The complete logon data must be entered in the logical destination.
6. When registering the queue in transaction SMQR, enter the logical destination.
In this way all LUWs in this queue are processed with the specified logon data.