Manage System Diagnostics

Background

The M3 Business Engine is a very large product. To set up parameter combinations, to monitor certain key values, to avoid running out of a number series, for example, could be very difficult. To help the system administrator, M3 BE has monitoring capabilities. This solution contains two parts:

  1. The system diagnostics checks are a number of batch runs that check the basic data and setups in the system. The idea is that these checks should proactively find potential errors before they occur, and act like help for troubleshooting already existing problems.
  2. The application monitoring console consists of several small, fast, interactive checks of the application. They are performed at the initialization of the list view (or API call) and thus always contain fresh data. The application monitoring console also offers the possibility to set user-defined threshold values to define which result is acceptable, and which is not.

Follow these steps for system diagnostics

The program 'System Diagnostics. Open' (CRS998) contains a number of batch runs that check the status of the basic data in the system. The result of the check is displayed with a status that indicates if the check contains errors, or if the check was performed OK.

Currently, the system diagnostics contain seven check programs that perform 16 tests of the system.

Program name Description
CRCHK002

Checks that each calendar entry has a valid period type. Checks that all divisions have a calendar at least as long as the calendar for blank division.

CRCHK003 Checks all number series and warns if usage is > 90%.

This is valid for all number series (CRS165), including invoice number (MFS165), journal number (CRS400) and voucher number (CRS410).

Journal number is also checked so that a record exists for the next year.

CRCHK004 Checks planning values in Item/Warehouse (MMS002)

Currently checking that low-level code is < 50 and that the planning horizon is not further out in the future than the calendar entries.

CRCHK005 Checks that all fields in Item Master (MMS001), Item/Warehouse (MMS002) and Item/Facility (MMS003) have a valid value.
CRCHK006 Checks that all CRS7* programs have a corresponding CSYPAR value.
CRCHK007 Checks that all sorting options have an existing user defined table. Also checks that all inquiry types have an activated sorting option.
CRCHK008 Checks that all activated datasets have an existing dataset table.

If dataset status = 10 (not activated) but file ID exists = error message.

If dataset status = 20 (activated) but no file ID = error message.

If dataset status = 20 (activated) but file does not exist = error message.

System diagnostics outcome

The result of the checks generates detailed messages in the program 'Application Message. Open' (CRS420/CRS421) using option ‘Detailed message log’ (21). The result could also be viewed in the server view according to previous chapter.

From 'Detail Message. Open' (CRS421) you can jump to the different programs to fix the logged problems.

System diagnostics setup

There is only one parameter on (CRS998/E) that can be set, and that controls if the result of the check should generate a text file. This text file could be used if the result of the checks should be monitored using a third-party system.

Activate message ‘964’ in 'Settings – Application Messages. Open' (CRS424).

The program (CRS998) contains a ‘Standard’ key (F14) that should be used the first time the program is used, or whenever a new MCP (M3 BE Correction Pack) has been installed. The action ‘Standard’ (F14) will generate the standard tests delivered, and if any new tests have been added in an MCP, these new tests will show up when pressing this key.

The checks can be started either using the action ‘Run’ (F9), which will run through all the checks, or option ‘Run’ (9) on a specific check.

The result of the checks is displayed as a status where status 00 indicates that the system check has found some errors, status 20 indicates that there are no errors found.

Follow these steps for application monitoring

The program 'Application Monitoring. Open' (CRS995) contains a number of small and fast interactive checks that monitors the status of application. The result of the check is displayed with a status that indicates if the check contains errors, or if the check was considered OK.

Currently the application monitoring contains nine interactive check templates from where you can build your own checks.

Template Description
Analyze And Repair Status Returns the status from a specified Analyze and Repair run in 'Item per Warehouse. Analyze and Repair'(MWS980)
Analyze And Repair GL Balance Returns the status from a specified Analyze and Repair run in 'GL Balance File. Analyze' (GLS940)
Erroneous Financial Jobs Returns the number of erroneous financial jobs in table FCR040
Invoice Number Series Percentage Returns the used percentage of a specified invoice number series in 'Internal Invoice Series. Open' (MFS165)
Journal Number Series Percentage Returns the used percentage of a specified journal number series in 'Journal Number Series. Open' (CRS400)
Number Series Percentage Returns the used percentage of a specified number series in 'Number Series. Open' (CRS165)
System Diagnostic Status Returns the status from a specified System Diagnostics run in (CRS998)
Table Size Control Returns the number of records in a specified table
Voucher Number Series Percentage Returns the used percentage of a specified voucher number series in 'Voucher Number Series. Open' (CRS410)
Multi Invoice Number Series Returns the used percentage of a specified multi-invoice number series in ‘Multiple Invoice Number Series. Open’ (MFS168)
Terminated PO receipts Returns any PO receipt that has been abnormally terminated

Application monitoring outcome

The results of the application monitoring checks are displayed in (CRS995). There is also an API, CRS995MI, from where these checks can be run and viewed from outside M3 BE.

Application monitoring setup

The program (CRS995) contains a ‘Standard’ key (F14) that should be used the first time the program is used, or whenever a new MCP has been installed. The action ‘Standard’ (F14) will generate the standard tests delivered, and if any new tests have been added in an MCP, these new tests will show up when pressing this key.

The execution of the checks is performed at initialization of the list view, when starting the program or when pressing ‘Refresh’ (F5), or when running the API transactions in CRS995MI. The result of the checks is displayed as a status where status 00 indicates that the system check has found some errors, status 10 indicates a warning, and status 20 indicates that the check is performed OK.

Here, you can also define the thresholds for when a result should be considered OK or not OK. Define the compare value (threshold), an operator, and the resulting status where status 00 = ‘Not OK, status 10 = ‘Warning’ and status 20 = ‘OK’.

Note: You define what is OK and what is not OK, everything that falls outside the threshold values will be set to status 10='Warning'.

Limitations

Only a limited number of application monitoring templates or system diagnostics tests are provided.

Note: When jumping to the different programs for correcting the problems, you will most often be positioned correctly in the called program. However, if division is in the key of the program, the positioning will not be correct. The division affects the LDA values, you must be logged on to the correct division to fix a problem. For example, if you find that a dataset in division AAA needs to be deactivated, you must be logged into division AAA to see the dataset and to perform the deactivation