Ansicht
Dokumentation

R3CIF_SCHEDIN - Set Up QIN Scheduler

CPI1466 during Backup   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

The data transfer via Core Interface (CIF) is carried out via queued Remote Function Call (qRFC). If you are working with inbound queues, incoming qRFCs are processed by the QIN scheduler.

You complete the following steps in the relevant client in the production system.

The QIN scheduler is called using transaction SMQR. In contrast to the QOUT scheduler, only queue names are registered in the QIN scheduler, not destinations. The registration is not made automatically; you have to do this yourself. If a queue is not registered, it is not processed (that is, there is no transfer).

qRFC communication has to be configured. For more information, see Configure qRFC Communication.

• Call transaction SMQR and choose Registration.

• Enter the queue name CF* and make the required settings.

• EXEMODE: Execution mode (D - Dialog work process; B - Batch work process)

• MAXTIME: Maximum runtime that the QIN scheduler uses for activating a destination; default value: 60 seconds

• USERDEST: RFC destination with LOGON data. Specification of a logical destination with its own language on the local system. This means that the burden of integration can be distributed to a server group.

• NRETRY: Number of repetitions for failed calls, default value: 30

• RDELAY: Wait time between individual calls, default value: 300

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 1786 Date: 20240523 Time: 202140     sap01-206 ( 35 ms )