The forecast log application (PLANLOG) initially informs you of all of the planning steps performed for a scenario in the planning monitor (PM) by providing you with information on users, point in time, running time, and information on errors and warnings. Furthermore, the processing logs that were shown during execution of the process can be called up again with this application. If desired, the application also logs the user’s directly executed actions between loading and storage of a scenario, in the planning application IDL Forecast (PLAN), but only the action itself and not the details.
The application is called up either directly or as a follow-up application via the respective context menu entry "Forecast Logs" in the planning monitor (PM) or from the scenario in the planning application IDL Forecast (Plan).
The forecast logs for the previously set or selected scenario will then be displayed in a new registry. If you want to show the logs for another scenario, you can select the desired scenario from the listbox on the left side. If the logging is only to be viewed for certain companies, the display can also be grouped by companies. The possibility of “grouping by companies" can also be selected or deselected by placing a checkmark on the left side.
The newest logs will appear at the beginning of the list. The logged actions can be opened by either double clicking on the entry or by marking the entry, pressing the right mouse button and “show log.“ A new window with the logged actions will then open. Besides a printing and filtering function for the actions listed, additional information on individual actions can also be called up by double clicking on the entry. These will be marked with an 'I' in the 'result' column.
Forecast logs can be deleted again by marking the entries that are to be deleted and pressing the right mouse button “delete logs.“ Before the logs are to be deleted permanently, the delete process needs to be confirmed again by pressing “yes.” The deletion process will be stopped if you answer “no.” When deleting a scenario, the respective logs will also be deleted. If logging of user actions is deactivated in the scenario, all of the logs will be retained, not deleted.
Note: Logging takes place in the language that has been set by the respective user. Therefore no multilingual logging is possible!
Whether user actions are to be logged between loading and storing a scenario is to be specified for the first time when the scenario is set up under extended scenario settings. Here, logging must be preset as activated by placing a checkmark. Logging can also be activated or deactivated later on via the properties of the scenario.
Note: This possibility of de-/activation pertains only to logging of user actions in the scenario and not to logging of actions via the planning monitor.
Logs in a scenario on user actions that have been carried out will be marked 'Manual processing in IDL.FORECAST.'
The following actionsthat were carried out while a scenario was open are logged in this entry (partially including further information - see clip):
The changing of values is only to be logged in the following cases:
Logging of actions carried out via the planning monitor (PM) is always active and cannot be de-activated.
Logs of actions that can be carried out via the planning monitor can either be individual planning steps in the context menu or multiple planning steps from a planning process. Planning steps that were started from the context menu begin with 'Kontextmenü -> ...' as the log name. In addition, planning processes will be entered with their 'name' being the same as the log.
The following actions are to be entered as a log:
Besides the context actions listed above, there are also actions that are not currently to be logged:
Logs for planning processes carried out equate to the window shown during the execution of the planning process in the planning monitor (this equates to the process log). Insofar, the content of a process log on various planning processes can be subsequently recalled again. If a context menu entry has been made, the log will contain not only the action itself, but also the subsequent actions 'Open and store a scenario.