Error Handling/Monitoring There are various functions for error handling and monitoring available in the
Transportation Planning/Vehicle Scheduling (TP/VS)
component. Most of these functions are valid across the whole of SAP APO.
Using transaction /n/SAPAPO/VSCC, you can check the settings you have made in Customizing (including a check of SAP R/3 Customizing) and the master data and movement data. You get a list of error messages. For some of these messages you can display detailed information by clicking the relevant object. In some cases you can go directly to the affected transaction and rectify the error. You can also schedule the consistency check as a background job and write the results to the application log. We recommend executing the check according to the supply chain model and after the IMG activities have been completed.
Using the application log, you can track what has been transferred (data objects and integration model), when (time), and by whom (user). The application log also issues a detailed error message is there is an application error. You can call the application log for
Transportation Planning/Vehicle Scheduling
using the application toolbar in interactive planning. You define the log level, that is, the level of detail in the log in SAP APO Customizing under
.
This function uses preset time selection parameters. If you want to enter your own time selection parameters or want to take additional SAP APO components into consideration in the application log, use transaction /n/SAPAPO/C3.
The SCM queue manager (transaction /n/SAPAPO/CQ) allows you to centrally monitor queues and how they are being processed in both the sending system and the receiving system. It is possible to navigate to the qRFC monitor and to the application log in both systems.
The qRFC and the qRFC alert offer further monitoring possibilities. The qRFC monitor (transaction SMQ1 for outbound queues and SMQ2 for inbound queues) lets you display, activate, debug, or delete queues. The qRFC alert (transaction /n/SAPAPO/CW for outbound queues and /n/SAPAPO/CQINW for inbound queues) enables a message to be issued automatically if a transmission error occurs.
Saving the Log Files from the Optimization Runs
In transaction /n/SAPAPO/OPT10, you can set the debug level and dump level of the Optimizer. In transaction /n/SAPAPO/OPT11 (under menu option
Extras
), you can save the Optimizer trace file, and the input and output data (if you have given the dump level the value 1).
Using the CIF comparison/reconciliation of transaction data, you can identify and correct data inconsistencies between SAP APO and SAP R/3.
Using transaction /n/SAPAPO/OM17, you can identify inconsistencies between the liveCache and various databases in SAP APO.