Consistency verification
WARNING, this tool returns results which interpretation can be difficult, particularly for certain standard tables. It is therefore advised that, when the log file lines are returned, to contact the support in order to check if the anomalies identified are real and require maintenance, of if these are normal within the context.
The data dictionary of the software describes the links between tables. These links are tested by the update programs, but they are not, for reasons of portability between databases, described in the database itself as referential integrity constraints. In order to be able to check that these constraints are satisfactory, it is possible to use this utility, which is used to exhaustively test the line links to other tables for each line in each table.
Considering the number of tables, the potential number of lines in a table and the number of lines to test, executing this utility in an exhaustive fashion can be extremely long. It is often advised to limit the tests to carry out.
The result of the test is a log file, in which are found the potential anomalies. It is advisable to examine in a detailed fashion the anomalies in order to take the appropriate maintenance measures if required.
Warning, if anomalies exist in the data dictionary description (for example following specific/custom developments), it is possible that "false errors" exist. It is necessary to be very prudent in the interpretation of the results of this test.
Screen management
Entry screen
Triggering this function is carried out on one single window, in which the launch setups of the function are entered.
Block number 1
| Folder (field DOSSIER) |
|
This field is used to define the folder in which the utility is launched. The possible syntaxes are described in the dedicated appendix. |
Block number 2
| First table (field FICDEB) |
|
Used to give a range between two values for the code to be controlled by the utility. |
| Last table (field FICFIN) |
| Module (field LIBMOD) |
|
List of modules in the software. |
| field MODULE |
|
This grid is used to define (by responding Yes for the lines concerned) the tables to be analyzed by filtering by functional module. |
| Yes to all the rest |
|
When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer Yes to all the lines starting from the current line. |
| No to all the rest |
|
When faced with an entry grid with multiple choices and a Yes/No answer on each line, this function makes it possible to answer No to all the lines starting from the current line. |
| Error logs |
|
No error message is displayed on the screen, rather error messages are presented in the following form:
This signifies that in the XXXXXX table, in the key record KEY_RECORD, the INCORRECT_FIELD field points to a non-existent key (LINK_KEY of table, LINKED_TABLE_NAME. For example if in the company table (COMPANY), the company JOHNDOE has for country (CRY field), the country with the UNKNOWN code that does not exist. The log file will display the following message:
|
Refer to documentation