Transaction Code: /SAPAPO/CQ - SCM Queue Manager

Menu Path: SAP Menu Tools APO Administration

Integration Monitor /SAPAPO/CQ- SCM Queue Manager

This transaction in SAP APO enables you to check the local

system as well as all connected systems. The output queues
are sorted per publishing type (for example, in-house
production, planned independent requirement, planning file
entry, and so on).

With the SCM Queue Manager you can check outbound

queues in your own or in a connected system and analyze and
correct errors if necessary. The advantage compared to the
qRFC Monitor is that the SCM Manager is more user friendly
(see RFC Inbound&outbound queues chapter for more detail)
 Input all inbound and outbound systems in 1), and then click 2)

1
 You then enter this screen:

On the left menu, you can see the error messages concerning
SAP APO or SAP R/3 system, with the type of error specified.
Example:
APOCLIENT1 relates to APO inbound flows: data coming in APO
system having some errors
APOCLIENT1 relates to APO outbound flows: data
coming out of APO to R/3 having some errors
 Double click on the error message type 1) in order to load the
detailed error messages 2) in the right side of the screen:
2

On the left, below each system name, we see the errors of data flows
coming in or out of this system.
In this case for instance, there is an error on the stock for a product.
This error is blocking directly two stock elements in red, and
indirectly another one which is in status waiting: once the error
blocking the red objects is corrected, and these are pushed through,
the waiting record will also flow through
 Once we are in the Queue Manager transaction, the
first step you can then do is to Activate the Queue:
To do so, select the message you want to activate and click on .
If the queue activation has been done without error, the selected
message will disappear from the right side of the screen.
It is possible that the object was blocked at the moment it went
through the interface, and that the element blocking it has now
disappeared. In that case, activating the queue will make it flow
well. An example could be an order which had been changed in
R/3, but was being edited in APO at the same time: the R/3
modification could not flow properly to APO at that moment. But if
the order is not edited anymore in APO, activating the queue will
be enough to make the update flow again, this time successfully.
 Error message Message description

Pegging area for material A

There is a missing transportation line for this product
location LOC1 not available

This error can come from the fact that the component has no
active integration model:
Check in transaction CFM5 if there is an active model for
Component B in location
this product*location. If not, then check in transaction
LOC1 not planned
CFM2 the last time the model of such
components*location should have been activated, and
look why it was not done for this component