Kontakt

Ansicht
Dokumentation

APO_ATP_ATPLOG - Maintain Parameters for ATP Application Log

APO_ATP_ATPLOG - Maintain Parameters for ATP Application Log

CL_GUI_FRONTEND_SERVICES - Frontend Services   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you maintain the parameters for the ATP application log. You also switch on the ATP application log here.

Make sure that you use the OLTP user name to switch on the log when calling APO from a linked OLTP system.

  • Log on
Switches on the writing of the log.
Note
Switching on the log has a negative impact on the performance of the availability check.
  • Display direct
If the Direct display indicator is set, a log is displayed in a dialog box for messages from particular application classes that are reached in the program code. The application classes, for whose messages a log display should be created immediately, can be selected at the start of the log in a dialog box.
In the dialog box for the log display, the program continues to run until the next message, if you confirmed with Enter in order to display the log again.
If you choose Switch on debugging, debugging is switched on (assuming you have the apporpriate authority); that is, after exiting the display log, the program sequence is continued in the debugger.
If you want to switch off the message display, choose the Switch off message display pushbutton. When you have selected the pushbutton and confirmed using Enter, the check runs without any further message display.
  • Action at log end
The indicator determines which action should be carried out automatically after the log has been created and exited. The following options exist:
  • Log remains in the main memory without any particular action

After the end of the log, nothing happens. When the calling transaction has ended and the main memory has been released, the log disappears.
  • Display log

The log is displayed at the end. The log is displayed only in the dialog transactions, not in batches or asynchronous RFCs. The log disappears after the main memory has been released.
  • Save log to database

The log is written to the database at the end and can later be displayed and deleted again.
  • Display log and save to DB

The log first can be displayed and then saved to the database. If the log cannot be displayed because the user is not in the dialog transaction, the log is still saved to the database.
  • Initialize log in main memory

The log is initialized in the main memory, that is, all messages in the log are deleted. However, the log header continues to exist. Initializing is helpful when several LUWs are executed one after the other within a transaction (for example, T-Code VA01), without the main memory being released (for example, when several orders are created within the VA01).
  • Display log and then initialize in the main memory

First the log is displayed (only dialog transaktion) and then initialized.
  • Save log to DB and then initialize in the main memory

First the log is saved to the database and then initialized.
  • Display log, save to DB and then initialize in the main memory

First the log is displayed (only dialog transaktion), then saved, and finally initialized.
  • C-trace availability check
If you set this indicator, a log file for the product availability check in liveCache (in C++ code) is also created. A corresponding message about the creation of this file is written to the application log. The C-trace file is displayed immediately by selecting the detailed information about this particular message.

If too many messages are displayed, the system performance can rapidly get worse.

  1. Enter your user name.
  2. Set the corresponding parameters.
  3. Save your entries.






Addresses (Business Address Services)   General Material Data  
This documentation is copyright by SAP AG.

Length: 5636 Date: 20240524 Time: 010138     sap01-206 ( 86 ms )