When you execute planning functions in Supply Network Planning (SNP) in the background (mass processing), the system automatically generates an application log. This log contains planning results, such as data for the planned orders and stock transfers created, as well as error, warning, and information messages.
You can access this log using the central Application Logs function. You can also display the log directly in the respective planning function.
Application logs are generated by the following SNP planning functions:
Extended safety stock planning
SNP heuristic
Capacity leveling
Deployment heuristic
Transport Load Builder (TLB)
SNP aggregation
SNP disaggregation
Resource disaggregation
Single-level supply and demand mapping
Low-level code determination
The separate Optimizer Log Data function is available for accessing logs for optimization-based planning functions in Supply Network Planning, such as the SNP optimizer and deployment optimizer. You can, of course, access these logs using the Application Logs function. However, in the Optimizer Log Data function, you get extensive information, such as the costs of the solution determined by the system. For more information, see Application Logs for Optimizers.
The central Application Logs function provides an overview of the generated logs. For example, you can display the following data for each log:
Input data for the planning run
Customizing settings and Business Add-Ins (BAdIs) that are relevant for the planning run
Messages that appeared during the planning run
Planning results, such as the planned orders and stock transfers created
The messages are displayed according to the message type specification (termination message, error message, warning message, and information message). You can sort the messages by message type or in ascending or descending order. You can also set different filters; to display by message type or message text, for example.
The planning results differ depending on the planning function. The following data is displayed, for example:
Extended safety stock planning
Planned safety stock per location product and period, as well as important location product master data, such as safety stock methods, service level, and target days' supply
SNP heuristic
Detailed information about the SNP planned orders, SNP stock transfers, and product substitution orders
Capacity leveling
Quantities per period and resource utilization before and after capacity leveling, as well as output product surplus and shortage situations
Deployment heuristic
Detailed information about the deployment stock transfers created, such as source location, target location, and means of transport
Transport Load Builder
Detailed information about the deployment stock transfers not processed and the TLB shipments created
SNP aggregation
Detailed information about the location products and orders to be processed
SNP disaggregation
Detailed information about the planned orders and stock transfers to be disaggregated
Resource disaggregation
Detailed information about the resources to be processed and orders created
Single-level supply and demand mapping
Detailed information about the location products to be processed and the fixed SNP stock transfers created
Low-level code determination
Information on the percentage of master data objects for which low-level code determination was successful. You can navigate from the application log to the inconsistent master data objects after the system has finished low-level code determination.
If you want to improve performance and reduce the amount of memory space used, or if you do not want detailed information to be displayed in the application log, you can deactivate the Detailed Result check box on the initial screen of the planning function. The log then only contains the number of generated orders, for example, and not detailed data for the individual orders.
On the initial screen of the planning function, you can also specify how long you want the log to be stored for. The default value for storage is 30 days. You can overwrite this value with anything between 1 and 999 days.
Once this specified period has come to an end, the log is flagged for deletion. You can then either delete it manually using transaction SLG2 or automatically using the delete program. You can also delete the log before the end of this period.
On the SAP Easy Access screen, choose
, or choose Display Logs on the initial screen of the planning function.The SNP/CTM: Display Application Logs screen appears. In the Application field, select the planning function for which you want to display the logs. You can also make additional settings, such as user name. However, you can also leave these fields blank.
If you set the Only Background Runs check box, the system only selects application logs generated using background processing (that is, if you scheduled the planning run as a background job).
Choose Execute.
The SNP Heuristic: Application Log screen appears.
The individual logs are displayed on the left-hand side of the screen. To display log data, the following options are available:
If you select a log and choose Technical Info, you see additional detailed information about the log, such as its expiration date and the specification as to whether it can be deleted before this expiration date.
If you double-click a log, the messages are displayed on the right-hand side of the screen. You can then use the toolbar pushbuttons to sort and filter these messages.
If you choose Available Detail on the right-hand side of the screen in the Detail column, the detailed information is displayed in the lower part of the screen.