You can neither define the sequence in which the function module calls are executed nor the time of execution. If an error occurs during the transfer, a batch job is scheduled which sends the function module call again after 15 minutes. Scenario 2: qRFC with outbound queue In this scenario, the sender system uses an outbound queue to serialize the data that is being sent.
This means that function module calls which depend on each other such as update and then change are put into the outbound queue of the sender system, and are guaranteed to be sent to the target system one after each other and one time only. The called system server has no knowledge of the outbound queue in the sender system client , meaning that in this scenario every SAP system can also communicate with a non-SAP system. The programming code of the server system does not have to be changed.
However, it must be tRFC-capable. Scenario 3: qRFC with inbound queue and outbound queue In this scenario, an outbound queue in the sender system client is used in parallel to an inbound queue in the target system server. If a qRFC with inbound queue exists, this always means that an outbound queue exists in the sender system. This guarantees the sequence and efficiently controls the resources in the client system and server system. The inbound queue only processes as many function module calls as the system resources in the target system server at that time allow.
The following functions are available:. This way you can be notified if the number of queue entries is higher than expected, the age of the oldest entry of the queue is too high, as well as the combinations. Monitoring Template: qRFC This template contains metrics for the real-time monitoring of exception and performance of qRFC inbound and outbound queues. This metric measures the number of individual queues within the specified queue group.
This means that the number of queues with the same name prefix that have at least one entry at the time of the data collection is measured. This metric measures the total number of all entries in all queues that belong to the monitored queue group at the time of the data collection.
This metric measures the average number of entries in all queues that belong to the monitored queue group at the time of the data collection. In order to determine the measured value for this metric, the "Total number entries in all queues" is divided by the "Number of individual qRFC queues". The average number as shown in the alert text has two decimals.
However, for the measured value it is rounded to an integer number. This integer number is basis for the alert determination. This metric measures the number of entries in the largest queue of the monitored queue group.
This metric measures the age in minutes of the oldest entry within any of the queues of the monitored queue group. Total number of entries in all queues with specific prefix in queue name. Age in minutes of oldest entry in all queues with specific prefix in queue name. Number of queues with critical state with specific prefix in queue name. Age in minutes of oldest critical state queue with specific prefix in queue name. Number of queues with interim state with specific prefix in queue name.
Age in minutes of oldest interim state queue with specific prefix in queue name. Newsletters may contain advertising. You can unsubscribe at any time. You should find information for the specified error code in the subsequent message in the application log.
Customer requirement N xxxxxxxxx not processed successfully. Check the Ship-to-party location in APO wether it exists there or not. Coz it might be a return delivery.
No Account? This serialization of incoming calls also limits the maximum load on the target server caused by RFC. Monitoring with the Alert Monitor. The corresponding special monitors with which you can quickly eliminate the cause of the error are set as analysis methods.
You have performed the setting up of the monitoring of qRFC calls. The monitor contains the following monitoring tree elements MTEs :. Monitoring object with information about the LUWs and tRFC calls that are waiting to be executed on their target system or on an external component. Number of tRFC calls that were not executed due to problems creating the connection or the communication with the target system or an external component; depending on the settings transaction SM59 , the attempt may be repeated a number of times.
Number of tRFC calls that could not be executed due to a problem with the execution in the target system or an external component. Subtrees that contain the log messages of the outbound qRFC calls to external systems; these messages are sorted by the different queue groups: there is a monitoring object for each group with the name Outbound Queues.
Subtrees that contain the log messages of the inbound qRFC calls from external systems; these messages are sorted by the different queue groups: there is a monitoring object for each group with the name Inbound Queues.
Log messages for the queues of an application, sorted by the different clients; the log messages contain the error messages that are returned during the qRFC call. For information about the possible statuses, see the Appendix. Log messages for the queues of an application; the queues have not been processed for longer than the time defined in the associated threshold value by default, seven days.
Log messages with error messages for the QIN schedulers of all clients; an alert here indicates that the system could not process an incoming RFC call due to a communication or execution error. Log messages with error messages for the QIN schedulers of all clients; an alert here indicates that the scheduler found an RFC call with a non-registered queue. As soon as the network connection is available again, a periodic repetition of the data transfer should solve communication problems.
Application problems cannot be solved by the system itself and must be dealt with by a system administrator. The qRFC monitor is used to monitor application errors in inbound and outbound queues. All transfer channels queues are displayed for all target systems. CFSLS — the name of the change transfer for the sales order number Transfer errors in the initial data supply are recognized automatically and a dialog box appears that you can use to access the qRFC monitor.
0コメント