Report: /SAPAPO/RCIFQUEUECHECK

From APO Release 2.0A on, the report qRFC Alert can be used to monitor the queues in APO and R/3 outbound that are relevant for APO-R/3 integration. Application errors that occur during data transfer are not reported directly to the user because data transfer between APO and R/3 is asynchronous. Instead, the qRFC entries block the outbound queue. Any subsequent data transfers cannot pass the outbound queue. Queue blocks are detected by means of qRFC Alert monitoring. The following are notified:

• The initiator of the block, via SAPOffice Inbox Mail (the initiator of every queue block receives a message informing it that it has caused a block)
• The administrator, via SAPOffice Inbox (one person is chosen to receive all messages)
• The administrator, via their Internet e-mail address (one person is chosen to receive all messages)

Current qRFC entries can also be displayed, activated, debugged, or deleted using transaction SMQ1 (qRFC monitor).

qRFC Alert will be available from APO 3.0A on. The function can be post-installed in APO 1.1 and APO 2.0A using a support package or a note (no. 0300884).

In order for messages to be sent to an e-mail address, the necessary settings must be available in SAPConnect.

The report monitors all APO outbound queues, and the queues of the logical R/3 systems connected to APO.

Local qRFC-API modules in the APO system, or qRFC-API modules in the connected R/3 systems, or both, are called up synchronously and the status of the relevant outbound queues is queried. This is carried out independently of the settings in the selection screen. You can find out the names of the relevant logical systems from the selection screen entries, and from the entries in the table /SAPAPO/SYSDIR (to maintain use /SAPAPO/C2).

If the system recognizes queue errors or blocks, a message is generated from the status information. The message is sent via the SAPOffice API to the relevant receiver(s) or administrators(s), provided the settings are set accordingly. Also, the list of all the incorrect outbound queues is output in list form.

Start qRFC Alert using the SAP Easy Access Menu, as follows: Tools ® APO Administration ® Integration ® Monitor ® qRFC Alert, or using transaction /SAPAPO/CW.

• 2-character prefix ‘CF’
• 2-character object abbreviation (for example, ‘IP’ for ‘in-house production’)
• 4-character numerical value

3. In the case of queue errors: define whether only true application errors (SYSFAIL) (flag set) should be found, or whether temporary errors such as communication errors (CPICERR) or errors caused by temporary application locks (flag not set) should also be found.
4. Define the recipient of the message:

• No notification (the message is not sent, but is simply displayed on your screen)
• To initiating object (the message is sent to the initiator of the block)
• To administrator (all messages are sent to one person)

You can change the entry in the address field (the user who is currently logged on is the default value).

5. Choose a recipient type. The recipient type determines the message format. At the moment, you can choose either B (SAP user) or U (Internet address). When choosing recipient type U, make sure that you have maintained the corresponding entries under SAP Connect.

6. Execute the report (F8). The message is either sent or displayed on-screen.

The settings for monitoring the outbound queues of connected R/3 systems are defined in the group ‘Remote Output Queue’.

1. Under Remote systems, enter the name of the RFC destinations whose outbound queues you want monitored. You can use wild cards (for example, SX*). If you do not make any entries, no outbound queues in any connected system will be monitored.
2. Under Destinations in remote systems, enter the name of the required destination systems in the remote system (usually the APO system itself). You can use wild cards (for example, SX*).
3. Under Remote queue names, enter the name of the R/3 outbound queue that you want to examine in the remote system to be monitored.

4. All subsequent entries are made in the same way as the entries for the local outbound queue.