Informacion General SAP EWM
Informacion General SAP EWM
Informacion General SAP EWM
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
This is custom documentation. For more information, please visit the SAP Help Portal 1
4/3/2024
Go to start of metadata
Legal Disclaimer
Note that the How-To Guides featured on this page are not part of SAP product documentation. These How-To Guides are
provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of
merchantability, tness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in
this document, except if such damages were caused by SAP intentionally or grossly negligent.
Purpose
The EWM Check Monitor (CHM) is a tool to help identi cation and correction of data inconsistencies in customer systems.
Checks are organized in a hierarchy of check categories - groups - checks. The hierarchy is built upon de ned
major EWM application areas. Currently a set of standard checks and corrective functions have been implemented by SAP.
This is custom documentation. For more information, please visit the SAP Help Portal 2
4/3/2024
Features:
You can execute ad-hoc checks (consistency or any other) or save check pro les for repetitive execution.
For reuse you can create and save so called check pro les. Pro les contain selection of checks to be executed and
parameters for selection of objects to be checked.
The results of the checks are collected and displayed in so called check logs. Check logs are extended business
application logs (BAL Log) containing standard messages and - optionally - additional data attached to these messages.
Check logs can be saved for later analysis.
Check log content can be analyzed using different check log views. These views can be de ned in order to group the
messages based on some common attributes (e.g. all different messages belonging to a single delivery item, warehouse
task or HU).
How-to
This is custom documentation. For more information, please visit the SAP Help Portal 3
4/3/2024
1. How to create a check pro le?
Check pro le (a.k.a. Check Monitor Pro le) is some kind of "variant" of the Check Monitor. Check pro le de nes what
checks are performed and selection criteria to identify the objects to be checked. The check pro le is a persistent object,
you can save it in order to execute the same checks multiple times.
Step-by-step
3. In the hierarchy of checks select the categories, groups and checks you want to execute:
The selection parameters set on category or group level apply for all contained check: if the selection screen is assigned
to a category or group, then the selection adapter runs on this level and the selected objects (e.g. inbound delivery
items) are passed to the selected checks of the category/group. The lower level selection parameters only re ne the
ltering performed on the higher level (e.g. settings for check "Missing Document Flow Links" will only be applied during
this particular check to deal with only speci c link types), but do not affect the execution of other checks (above e.g.
Handling Unit Reference).
This is custom documentation. For more information, please visit the SAP Help Portal 4
4/3/2024
1. Open the selection screen for the category/group/check where you want to make settings. For this you have to
click the "Show Selection" icon in the column "Sel." of the tree. If no icon is present, then no selection parameters
can be speci ed.
2. Enter the necessary selection parameters to ensure your check runs on the required objects. The selection
screens vary for each different category, group or check.
3. For all selection screens, where you have made settings the icon will indicate this fact.
5. When you've nished with all required settings save the pro le (CTRL+S).
Important: Changes to a check pro le are only effective, when they're saved, otherwise the earlier version of the pro le
is executed!
6. Saved check pro les can be managed in the left-hand browser via menu "Edit" or context menu of the entries. Available
functions are:
2. Change: Enables changing of the pro le settings in the right side panel.
1. Checking of pro le parameter consistency (e.g. obligatory selection parameters are lled)
2. Authorization checks
3. List of selected objects can be queried based on the selection parameters: this enables you to check, if the
selection criteria will really identify the required objects.
7. Execute: Checks selected in the pro le will be executed and the results will be summarized in a check log.
8. Display Logs: saved logs for the selected check pro le can be listed and analyzed (this option navigates to
transaction Check Log Viewer /SCWM/CHM_LOG).
Before execution of checks in the Check Monitor you can set different parameters in order to optimize runtime, lter log
messages and set check log expiration. The execution parameters can be set for ad-hoc check execution and execution of
check pro les, as well.
The setting dialog can be opened from the pro le maintenance transaction or the ad-hoc check screen using the
pushbutton "Set Execution Parameters":
Parameter options
This is custom documentation. For more information, please visit the SAP Help Portal 5
4/3/2024
1. Minimum priority: the minimum message priority of messages displayed in the log can be set. This enables to
reduce size of logs of checks. For example a check provides error, warning and status messages as well. You want
to avoid the log to contain messages that does not indicate error situations, then you simply set the minimum
priority to "Warning" or "Error". this is especially useful when you schedule pro le execution as a regular job and
want only have a log, if any errors are identi ed.
2. Display Check Monitor Messages: enables to display non-check-speci c messages raised by the Check Monitor
itself (e.g. wrong customizing or performance relevant messages).
2. Check Log Validity: As in standard BAL logs, you can set the validity period for the logs created. The log deletion report
will check validity before deletion of expired logs.
3. Parallel Processing: As in other applications, reports, you can enable parallelization of check executions and de ne the
server group and percentage of maximum work process usage.
EWM Check Monitor (CHM) provides a report in order to enable scheduling of check execution as background job. This
report is /SCWM/R_CHM_PRF_RUN (package /SCWM/UTILITIES).
YOu want to
the runtime execution parameters (similar parameters to the online check execution).
You simply schedule this report with the de ned variant in transaction SM36 (Schedule Background Job). After execution
the report will save the resulting Check Log to database and you can handle them in the CHM Check Log Viewer
transaction (/SCWM/CHM_LOG)
This is custom documentation. For more information, please visit the SAP Help Portal 6
4/3/2024
4. How to start follow-up functions for the check messages?
Follow-up actions may enable further analysis of the problematic objects or even correct the inconsistent entries.
The concept of an application-independent check monitor also means, that the follow-up actions for the different check
messages are de ned and implemented by the check adapter that returned the given check message. Technically it
means, that for different check messages different options can appear, if you right-click them.
After executing checks the results are collected into a Check Log. If you open a check log you can view the check messages
and the detailed data records attached to them.
1. Select one or more messages and right-click them to display the context menu.
2. On the bottom of the menu item list you may nd some message speci c entries (the rst 3 menu items are
default ALV context menu items). Of course it depends on the logic of the responsible check adapter, which or even if any
follow-up actions are available from the given message (see some examples on the screenshots below).
3. Choose the one you want to use. Based on the implementation various things may happen: navigation to another
transaction to display details of the object, a new screen providing further information or the possibility to execute
corrections on the selected objects.
4. You have also the option to choose only one or more records from the "Details" list of a message and trigger a follow-up
function for these speci c entries.
This is custom documentation. For more information, please visit the SAP Help Portal 7
4/3/2024
For details about the available speci c follow-up actions see the pages about details of the standard checks and
corrections.
With some of the checks it is possible to correct the detected inconsistencies. Some corrections which does not need any
end user interaction and decision can be simply executed with a few clicks in TX. /SCWM/CHM_LOG after selecting the
corresponding check logs. For example the inconsistencies detected by the status management checks for
inbound/outbound deliveries can be executed manually by anyone.
With report /SCWM/R_CHM_LOG_ACT it is possible to execute correction actions which do not need end user input. The
report can be scheduled in a background job to select the recently generated check messages, this way there is no need to
open TX. /SCWM/CHM_LOG to select and inspect the recently saved check logs manually. If the selected check logs refer
to inconsistencies which can be corrected automatically then these will be executed (e.g. status correction for deliveries).
If this approach is combined with the scheduled /SCWM/R_CHM_PRF_RUN report then the detection and correction of
many inconsistencies can be automatized by reducing the manual effort.
Important
The report selects only such check logs which were saved in Customer mode. Checks which require support mode offer
correction actions where end user input or validation is required on a special UI (e.g. adding document ow), such steps in
background mode are not possible.
2883401 Check Monitor Framework: New report for mass execution of follow-on correction actions
2915573 Check Monitor Framework: New report for mass execution of follow-on correction actions (UDO report
Related Content
Related Documents
This is custom documentation. For more information, please visit the SAP Help Portal 8
4/3/2024
This is custom documentation. For more information, please visit the SAP Help Portal 9