/SAPAPO/ATPLOG_DISPLAY - ATP: Display application log

General Data in Customer Master   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Title

Purpose

The ATP application log is a message log which can be created during an availability check in APO. Itcontains information about Customizing settings, the technical and time facets of the check as well as possible warnings and errors that occurred.

With the application log the technically oriented users or consultants have a tool with which they canbetter understand the availability check process and are thereby in a position to solve problems like,for example, incorrect Customizing settings, independently. The ATP developer gets detailed informationfrom the log about the control flow (up to function module level) within an availability check and abouterrors and problems which have occurred. This can be helpful (for example, with customer problems) forquickly localizing an error without having to debug immediately or to quickly find the best place tostart debugging. The application log supports both of these usage scenarios via a technical view with detailed information for the control flow and via an application oriented view without this information.

This report loads selected ATP application logs from the APO database and displays them.

Integration

Prerequisites

ATP application logs which correspond to the selection criteria must be available in the APO database.

The user must belong to the ATP expert role or higher.

Features

Selection

It is possible to display all available logs of a particular user or to display the logs of all users by leaving the user field blank.

Furthermore you can choose between two display profiles:

• 'A' for the application oriented log

• 'T' for the technical log

Standard Variants

Output

All ATP application logs found are listed in the upper section of the display screen. If you doubleclick on a log or a log-section the associated messages are listed in the lower screen area. A log issub-divided into different areas (application classes) of the availability check (by pressing the legend button @5E@ a description appears in the system):

• BAP:,,BAPI APO interface

• BOP:,,backorder processing

• EAS:,,explanation and simulation components

• EVR:,,rule evaluation

• FCK:,,check method: check against planning

• PAC:,,check method: product availability check

• PAL:,,check method: product allocation

• PAT: persistent ATP tree structure

• PRD:,,production

• SCH: scheduling

• TQA:,,temporary quantity assignments

• TRC:,,ATP controller

Every applications class is subdivided again into problem classes which document the importance of amessage. In the technical view of an application log the problem classes are available as very important, important, medium, other and . In the application oriented view there are only the problem classesvery important, important and medium.Further numerous filter possibilities exist alongside the subdivided display of messages in applicationsclasses and problem classes. For example, certain error classes (cancel, error, warning, information)can be hidden. Furthermore, an application log can be exported in different formats. This is useful,for example, if there is no service connection to a customer computer. The customer can then create a log, export it as a file and then send it by e-mail to SAP.

It is also possible to delete individual logs from the database by selecting the log to be deleted andthen pressing the delete button. The delete button is however only visible to APO users with the ATP controller role or higher.

In order to load changes made in the meantime to the logs or to new logs in the database, which were created during the display, select the refresh button.

If a log exists in the main memory (for example, if it was selected as the log display) you can save this log in the database. Select the log and save.

Activities

Example

PERFORM Short Reference   CPI1466 during Backup  
This documentation is copyright by SAP AG.


Length: 4482 Date: 20120523 Time: 171416     triton ( 196 ms )