JP5821528B2 - Data check program, data check method, and data check device - Google Patents

Description

  The present invention relates to a data check program, a data check method, and a data check apparatus.

  2. Description of the Related Art Conventionally, business systems used in local governments or the like are provided with various functions for the purpose of system user input support and the like. For example, some business systems have a function that performs input value checks on input values entered on the screen and issues a warning if there is an error, allowing the system user to recognize the error. Some systems have Such input value checks include, for example, a check that causes an error when the input completion button is pressed even though no name is entered in the field where the name must be entered, An error check is included when a numerical value (such as 2010/2/30) that cannot be entered in the date field is entered. When an input value results in an error, the system generally does not accept the input value at all. In some cases, an error is not generated by selecting a value such as an era from a list box or inputting a date from a calendar. That is, the input value accepted by the system is handled as a valid input value in the subsequent processing.

  In local governments, etc., when the system used for business becomes obsolete or a new high-performance system is developed, the system used (current (old) system) is changed to a new system (new system). There may be a migration. In this case, it is necessary to migrate the data used in the old system to the new system using the data migration program. Conventionally, after the data is transferred to the new system, a test operation is performed to test whether the program of the new system operates normally using the data after the transfer. If an error occurs during test operation, the system developer analyzes the cause, and corrects a bug in the new system program or a data migration program. After that, actual operation of the new system will be started.

  Patent Document 1 discloses a method for transferring data from an old system to a new system of a care insurance office work support system. In this patent document 1, a migration data extraction program extracts data used in a new system from an old system, and converts and edits the data for the new system to create migration data. Then, the migration program creates post-migration data from the migration data and performs data check.

JP 2004-240524 A

  However, in the conventional test operation, as described above, attention has been focused on repairing bugs in the new system program itself. Further, the migration program of Patent Document 1 merely checks whether the migration data created by the migration data extraction program has been correctly converted / edited (in Patent Document 1, the migration program is substantially used as a migration interface). (It can only check if the data format matches) For this reason, even if the data managed by the old system is data whose validity and consistency are not guaranteed, the data may be transferred from the old system to the new system as it is.

  When data that is not guaranteed correctness or consistency is transferred to the new system, the new system treats the data as correct data and performs subsequent processing. As a result, processing errors may occur frequently in the new system, or an erroneous calculation result may be output as correct although it does not cause an error. For this reason, it is preferable that data causing a processing error or the like in the new system is corrected before data migration.

  Therefore, this case has been made in view of the above problems, and a data check program, a data check method, and data that can output information for appropriately estimating the number of persons and the period necessary for correction of management data. An object is to provide a check device.

  The present inventor has examined problems of a business system currently used, problems in transition to a new system, and the like in developing a business system used in a local government or the like. As a result, the present inventor has found that (1) business systems that have been used for a long time in local governments, etc., are often host-based systems that have been subjected to repeated modifications by users. There are cases where the structure is complicated, input value check at the time of data input may not be performed, and (2) even if input value check is performed in the old system and a valid input value is input, Since the data may be corrected by the user after that, attention was paid to the fact that the correctness and consistency of the data are not necessarily guaranteed.

  Then, the present inventor has come to the conclusion that it is very important to check the correctness and consistency of the data itself stored in the system used in the local government or the like in the transition to the new system. In this specification, based on such new knowledge, the following data check program, data check method, and data check device are disclosed.

A data check program described in this specification is a data check program that causes a computer to execute a process of checking management data including at least one of input data and data generated based on the input data. wherein acquires check data generated from management data wherein the first system, the based on the conditions caused by the function difference between the different second system from the first system, a plurality of the check data included in the To determine whether or not there is consistency , and to output the type of the condition and the amount of check data obtained as a result of the determination based on the condition that is not consistent , to cause the computer to execute the process This is a data check program.

The data check method described in this specification is a data check method in which a computer executes a process of checking management data including at least one of input data and data generated based on the input data. an acquisition step of acquiring the check data generated from the management data having the a first system, and the first system based on the conditions caused by the function difference between the different second system, a plurality of the a determination step of determining whether or not matching is taken between the check data, output step of outputting the number of check data type and resulting alignment of the determination based on the condition is not taken of the condition Is a data check method executed by the computer.

The data check device described in this specification is a data check device that checks management data including at least one of input data and data generated based on the input data. Matching between a plurality of the check data based on a condition resulting from a functional difference between the acquisition unit that acquires the generated check data, the first system, and a second system different from the first system A data check comprising: a determination unit that determines whether or not a check is taken; and an output unit that outputs the type of the condition and the quantity of check data obtained as a result of the determination based on the condition that are not matched Device.

  The data check program, the data check method, and the data check device described in the present specification have an effect of being able to output information for appropriately estimating the number of persons, the period, and the like necessary for correcting management data.

It is a conceptual diagram which shows the structure and process of one Embodiment. It is a figure which shows the hardware constitutions of the check tool terminal of FIG. It is a figure which shows typically the flow of the data processing in the present system and a check tool terminal. FIG. 4A is a table showing an example of an error check, and FIG. 4B is a diagram showing an example of a condition table. It is a flowchart which shows the process of a data consistency check. FIG. 6A is a diagram illustrating an example of the household insured table, and FIG. 6B is a diagram illustrating an example of the householder table. It is a figure which shows the example of a condition table. It is a flowchart which shows the process of an annual tax amount check. FIG. 9A is a diagram illustrating an example of an imposition file (recalculation), and FIG. 9B is a diagram illustrating an example of a period-specific imposition file (current). It is a figure which shows an example of an error data total table (qualification). It is a figure which shows an example of an error data total table (imposition).

  Hereinafter, an embodiment will be described in detail with reference to FIGS. FIG. 1 is performed before data migration and data migration in the case where the system for resident information management used in local governments is migrated from the current system 100 as the first system to the new system 200 as the second system. It is a conceptual diagram which shows a data check.

  For example, the current system 100 is a system called legacy, and the new system 200 is an open system. The current system 100 and the new system 200 differ in various points such as an OS (Operating System), a DB (Database), and a program language used. Therefore, in this embodiment, the management data (hereinafter simply referred to as “data”) from the current system 100 to the new system 200 shown in FIG. 1 is migrated without being affected by the difference between the systems. A data migration program is used.

  In the present embodiment, before data migration between systems, the data held by the current system 100 is checked by the check tool terminal 10 as a data check device, and the check result is output (printout or the like). Is done. The person in charge of check or the person in charge of data migration (hereinafter simply referred to as “worker”) refers to the check result output from the check tool terminal 10 and is the person required to correct the data held by the current system 100. Determine the number, time, etc., and correct the data.

  FIG. 2 shows a hardware configuration diagram of the check tool terminal 10. As shown in FIG. 2, the check tool terminal 10 includes a CPU 90, a ROM 92, a RAM 94, a storage unit (HDD (Hard Disk Drive)) 96, an input unit 93, an output unit 95, a portable storage medium drive 99, and the like. It has. Each component of the check tool terminal 10 is connected to the bus 98. The input unit 93 includes an interface (such as a USB interface) to which an external device (such as a USB memory or an external HDD) can be connected, in addition to an input device such as a keyboard and a mouse. The output unit 95 includes a display, a printer, and the like.

  In the check tool terminal 10, the CPU 90 executes a program (data check program) stored in the ROM 92 or the HDD 96 or a program (data check program) read from the portable storage medium 91 by the portable storage medium drive 99. Thus, each unit (acquisition unit 12, data check unit 14 as a determination unit, and output control unit 16) illustrated in FIG. 3 is realized. The processing executed by the acquisition unit 12, the data check unit 14, and the output control unit 16 will be described later. In FIG. 3, for convenience of illustration, the condition table 22 and the error DB 20 stored in the HDD 96 and the like are also illustrated in the CPU 90.

  FIG. 3 is a diagram schematically illustrating a data processing flow and a functional configuration in the current system 100 and the check tool terminal 10. Hereinafter, data processing in the current system 100 and the check tool terminal 10 will be described with reference to FIG.

  As shown in FIG. 3, in the current system 100, data (extraction data 104) used in the new system 200 is extracted from the data stored in the database 102 by the processing of the data migration program. Next, in the current system 100, the extracted data 104 is converted and processed by the data migration program to generate check data 106. Here, the conversion processing includes processing such as character code conversion and personal information masking.

  The check data 106 generated as described above is transferred from the current system 100 to the check tool terminal 10. For transferring the check data 106 from the current system 100 to the check tool terminal 10, an information storage medium such as a USB memory may be used, or a network such as a LAN (Local Area Network) may be used. .

  On the other hand, in the check tool terminal 10, the acquisition unit 12 acquires the check data 106 transferred from the current system 100. Next, the data check unit 14 takes in the check data 106 acquired by the acquisition unit 12 and performs a data check based on the condition table 22. This data check is a check regarding conformity / nonconformity of the check data 106 with respect to the new system 200. Details of the data check performed by the data check unit 14 will be described later. The check result (the number of errors for each error type) in the data check unit 14 is stored in the error DB 20. The check result stored in the error DB 20 is read by the output control unit 16. Then, the output control unit 16 creates an error data tabulation table that lists the number of errors for each type of error, and outputs the error data tabulation table created by controlling the output unit 95. When the output unit 95 is a display, an error data summary table is displayed on the screen. When the output unit 95 is a printer, the error data tabulation table is printed on paper. In the present embodiment, the output control unit 16 and the output unit 95 realize the process of outputting the error data summary table.

  Next, specific processing of the data check unit 14 will be described in detail. The data check unit 14 determines (checks) whether the check data 106 is compatible with the new system 200 from various viewpoints. This check includes an error check as shown in FIG. For example, “Non-input check” checks whether a value is set for an essential input item, and “Illegal date check” checks whether an impossible date is set. In addition, “Consistency Check” checks the consistency between items in multiple tables, such as comparing the total amount of insurance premiums for medical care, nursing care, and support money with the amount of insurance premiums. Check the relationship between items such as whether or not the householder periods with individual numbers overlap.

  Hereinafter, the inter-table consistency check and the annual tax amount check as an example of the consistency check performed by the data check unit 14 will be described in detail.

<Check consistency between tables>
In the inter-table consistency check, the data check unit 14 executes processing according to the flowchart of FIG. As a premise of the processing in FIG. 5, it is assumed that the data check unit 14 reads one check item and check contents in the condition table 22 before performing the inter-table consistency check. Here, the condition table 22 is a condition that does not pose a problem even if the current system 100 is not satisfied, but a condition that becomes a problem if the new system 200 is not satisfied, that is, the current system 100 and the new system 200. It is assumed that the conditions resulting from the functional differences of are included. In this case, the data check unit 14 is set to No. It is assumed that 34 conditions have been read. This No. The condition No. 34 is a condition for checking consistency between tables, and is a condition caused by a functional difference between the current system 100 and the new system 200.

  In step S10 of FIG. 5, the data check unit 14 reads the household insured table based on the check item and check content fields of the condition table 22 (No. 34) of FIG. Here, the household insured table is one of the check data 106 shown in FIG. 3, and has a data structure as shown in FIG. More specifically, the household insured table has fields of “symbol number”, “household insured serial number”, and “qualification classification”. A serial number assigned to each household is input to the “symbol number” field, and a serial number assigned to the insured person included in the household is input to the “household insured serial number” field. In the “qualification classification” field, “1” is entered for a householder, and “0” is entered for other than a householder.

  Returning to FIG. 5, in the next step S <b> 12, the data check unit 14 reads the householder table based on the check item and check content columns of the condition table 22 (No. 34) of FIG. . Here, the householder table is one of the check data 106 and has a data structure as shown in FIG. More specifically, the householder table has fields of “symbol number” and “household insured serial number”. In the householder table, the householder's symbol number and household insured serial number of each household are entered. That is, in the household insured table in FIG. 6A, persons whose qualification category is “1” are collected in the householder table in FIG. 6B.

  Returning to FIG. 5, in the next step S <b> 14, the data check unit 14 selects one unselected householder record from the household insured table. Here, the householder record means a record in which the value of “qualification category” in the household insured table in FIG. 6A is “1”. Here, it is assumed that the data check unit 14 selects a record having a symbol number “0000000121” and a household insured number “1”.

  Next, in step S16, the data check unit 14 determines whether there is a record in the householder table corresponding to the householder record in the household insured table, based on the check contents column of the condition table 22 (No. 34). Determine whether. In this case, since the record with the symbol number “0000000121” and the household insured number “1” selected in step S14 exists in the householder table of FIG. 6B, the determination is affirmed and the process proceeds to step S20. To do. If the determination in step S16 is affirmed, it can be said that the selected record is a record that is compatible with the new system 200.

  If transfering it to step S20, the data check part 14 will judge whether selection of the record of all the household insured tables was completed. If the determination in step S20 is negative, the process returns to step S14. In step S14, the next householder record in the household insured table is selected. Here, it is assumed that the data check unit 14 selects a record having a symbol number “0000000122” and a household insured number “1”. Next, in step S16, the data check unit 14 determines whether there is a record in the householder table corresponding to the householder record in the household insured table, but since the determination here is affirmed, The process proceeds to S20. And when judgment of Step S20 is denied, it returns to Step S14 again.

  Returning to step S14, the data check unit 14 selects the next householder record (symbol number “0000000123”, household insured number “1”). In the next step S16, the data checking unit 14 determines whether or not the selected householder record exists in the householder table (FIG. 6B). Here, since the selected householder record does not exist in FIG. 6B, the determination in step S16 is denied, and the process proceeds to step S18. In this case, it can be said that the selected record is a record that is not compatible with the new system 200.

  When the process proceeds to step S18, the data check unit 14 selects No. based on the remarks column of the condition table 22. The error 279 (qualification) is stored in the error DB 20. The error DB 20 includes an error No. This database stores the number of errors for each. Thereafter, the process proceeds to step S20.

  As described above, the process is repeated, and all the processes in FIG. 5 are completed when the selection of the householder records in all the household insured tables is completed. As a result of the above process, the condition table 22 No. 34 completes the error check. When an error occurs in the process of FIG. 5, it is difficult for the data migration program of the current system 100 to automatically determine which of the householder record and the householder table of the household insured table is correct. This is because the data in the household insured table and the head of household table are registered based on the application of residents (unspecified large number of people), so confirm which data is correct with the residents who are the parties. This is because if you do n’t take it, you wo n’t know.

<Annual tax check>
Next, the annual tax amount check will be described. In the annual tax amount check, the data check unit 14 executes processing according to the flowchart of FIG. As a premise of the processing in FIG. 8, it is assumed that the data check unit 14 reads one condition (No. 52 in FIG. 7) in the condition table 22 before performing the annual tax amount check. This No. The condition of No. 52 is the above-mentioned No. Similar to the condition 34, the condition is caused by a functional difference between the current system 100 and the new system 200.

  In step S30 of FIG. 8, the data check unit 14 reads the imposed file (recalculation) based on the check item and check content fields of the condition table 22 (No. 52) of FIG. Here, the levy file (recalculation) is one of the check data 106 generated by the data migration program, and is newly imposed based on the qualification information and tax information of the national health insurance to be migrated. This file stores the results of calculations. More specifically, the levy file (recalculation) includes the fields “Tax year”, “Tax identification number”, “Taxpayer serial number”, and “Basic tax amount” as shown in FIG. have. The actual taxed year is entered in the “Taxation Year” field, and the taxation identification number indicating the taxation type is entered in the “Taxation Identification Number” field. In addition, the serial number assigned to the taxpayer is entered in the “Taxpayer serial number” field, and the basic tax payment amount after recalculation by the data migration program is entered in the “Basic taxpayment amount” field. The

  Returning to FIG. 8, in the next step S <b> 32, the data check unit 14 reads the period-specific imposed file (current) based on the check item and check content fields of the condition table 22 (No. 52) in FIG. 7. Do. Here, the period-specific charge file (current) is one of the check data 106 generated by the data migration program, and is a file that stores the charge calculation result originally held by the current system 100. As shown in Fig. 9 (b), this period-specific levy file (current) is similar to the levy file (recalculation), "Tax year", "Tax identification number", "Taxpayer serial number", "Basic Each field of “Tax Payment”.

  Next, in step S34, the data check unit 14 selects one unselected record of the imposed file (recalculation).

  Next, in step S36, the data check unit 14 determines whether or not there is a record of the periodic charge file (current) corresponding to the selected record based on the condition table 22 (No. 52, upper row). . If the determination here is negative, that is, if the selected record is a record that does not conform to the new system 200, the data check unit 14 determines based on the remarks column of the condition table 22 in step S38. , No. 106 (imposition) error is stored in the error DB 20 (the error number of the corresponding error No. is counted up). Thereafter, the process proceeds to step S44.

  On the other hand, if the determination in step S36 is affirmative, in step S40, the data check unit 14 selects the record and period of the selected imposed file (recalculation) based on the condition table 22 (lower part of No. 52). It is determined whether the basic payment amount in the separate charge file (current) is the same amount. If the determination here is negative, that is, if the selected record is not compatible with the new system 200, the process proceeds to step S 42, and the data check unit 14 selects No. 1 based on the remarks column of the condition table 22. 112 (imposition) error is stored in the error DB 20 (the error number of the corresponding error No. is counted up). Thereafter, the process proceeds to step S44. On the other hand, if the determination in step S40 is affirmative, the process proceeds to step S44 without passing through step S42.

  In step S44, the data check unit 14 determines whether selection of all records has been completed. If the determination is negative, the process returns to step S34, and the processes after step S34 are executed. On the other hand, if the determination in step S44 is affirmative, the entire process of FIG. As a result of the above process, the condition table 22 No. The error check regarding 52 is completed. If an error occurs in the processing of FIG. 8, it is difficult for the data migration program of the current system 100 to automatically determine which of the charge file (recalculation) and the period-specific charge file (current) is correct. . This is because the levy file (recalculation) and the levy levy file (current) contain information derived from data requested by residents (unspecified large number of people). This is because there are many cases where it is not known without confirmation from the residents.

  In the check tool terminal 10 of this embodiment, a large number of various data checks such as the inter-table consistency check and the annual tax amount check described above are executed. That is, various conditions are defined in the condition table 22. For example, if the condition read by the data check unit 14 from the condition table 22 is an illegal date check, all date data stored in the database 102 of the current system 100 and the year / month / day pattern are stored. The calendar table (stored in the data check unit 14) is compared. The data check unit 14 determines that an error has occurred when the same date as the date data does not exist in the calendar table.

  For example, when the condition read by the data check unit 14 from the condition table 22 is a range check (see FIG. 4A), it is checked whether a certain value is included in a predetermined range. . Here, it is assumed that there is processing for obtaining a difference (A−B) between the value A and the value B in the new system 200. Further, it is assumed that the value B should be a positive (+) value, but has been changed to a negative (−) value in the current system 100. In this case, if the negative value B is not regarded as an error, the calculated value of the difference between the values A and B (A−B) is erroneous (increased). In this case, in the new system 200, an error cannot be determined based on the magnitude of the calculated value (it is difficult to determine), but in this embodiment, the range of values managed by the current system 100 can be checked. It is possible to suppress the occurrence of an error in the calculated value in the new system 200.

  If an error occurs as a result of the various checks described above, the error is stored in the error DB 20 for each error type (the number of errors corresponding to the corresponding error No. is counted up). .

  Next, the error data summary table output from the output unit 95 will be described. FIG. 10 shows an example of an error data tabulation table (qualification), and FIG. 11 shows an example of an error data tabulation table (imposition). These error data summary tables include “No.”, “Record name”, “Check item”, “Check content”, “Error content”, “Number of cases”, “Number of previous cases”, and “Severity”. Is provided. It is assumed that the contents of “No.”, “Record name”, “Check item”, “Check content”, “Error content”, and “Severity” are input in advance. Here, “A: Severe”, “B: Mild”, “C: No action required”, “D: No confirmation required”, etc. are input to “Severity”. The classification of severity A to D is, in order, an error that cannot be corrected without confirmation to the residents of the local government, an error that can be corrected if the worker confirms it, an error that is automatically corrected on the system, and needs to be corrected There can be no error etc.

  The output control unit 16 reads the error DB 20 at a timing such as when all the error checks have been completed. Aggregate the number of errors for each. Then, the output control unit 16 inputs the total number of errors in the “number” column of the corresponding error data total table. The “number of cases” when the previous error check was performed is entered in the “last number of cases” column.

  In the error data tabulation table (qualification) of FIG. It can be seen that there are 0 279 errors (the previous number is also 0). Further, in the error data summary table (imposition) of FIG. The number of errors of 106 is 8 (the previous number is 20) and the severity is “A: Severe”. It can be seen that the number of errors 112 is 70 (the previous number is 73). In this embodiment, by outputting such an error data summary table, the worker needs to know how many people are required to correct the error, how much time should be taken, and until the new system 200 is operated. It can be estimated how much man-hours are required Note that errors of low severity (C or D) are automatically corrected in the current system 100.

  As described above in detail, according to the present embodiment, the check tool terminal 10 is applied to data applied from an unspecified number of residents (for example, household data) and data generated based on the applied data. An apparatus that checks data including at least one of (for example, imposition data), an acquisition unit 12 that acquires check data 106 generated from data included in the current system 100, the current system 100, and the new system 200 The data check unit 14 for checking the error (conformity / nonconformity with the new system 200) of the check data 106 based on the condition (condition table 22) caused by the functional difference between the data and the condition type (error No. and error content) Etc.) and the quantity of check data that does not conform to the new system 200 And an output control section 16 for outputting Te. Thereby, in this embodiment, since it is possible to output information for appropriately estimating the manpower and period necessary for data correction, the man-hours until the new system 200 is operated, the worker who confirmed the output result is In addition, it is possible to appropriately estimate the number of personnel and the period necessary for correcting the error, the man-hours until the new system 200 is operated, and the like.

  In this embodiment, since the number of a plurality of errors is displayed in a list on the error data tabulation table, the number of persons and the period necessary for correcting the error are determined (estimated) by comprehensively including the plurality of errors. It is possible.

  In this embodiment, since the “severity” column is provided in the error data tabulation table, the operator can estimate the number of persons and the period necessary for correcting the error in consideration of the severity of the error. Can do. In this case, it is possible to make an appropriate guess by setting the severity in consideration of whether the residents need to be confirmed.

  In the above embodiment, the case where the number of errors is displayed in the error data tabulation table has been described. However, the present invention is not limited to this. A quantity other than the number of errors, for example, the appearance frequency (ratio) of errors may be displayed in the error data tabulation table.

  In the above-described embodiment, a case has been described in which data is checked before data is migrated from the current system 100 to the new system 200 (before migration), but is not limited thereto. For example, the data check similar to that in the above embodiment may be performed regardless of the data transfer between systems (without assuming the transfer between systems).

  In the above embodiment, the case where the data check program, the data check method, and the data check device described in this specification are applied to the data check at the time of system transition in the local government business system has been described. However, the present invention is not limited to this. For example, the data check program described in this specification for system migration and data check in a system that handles data applied by an unspecified number of people and data generated based on the applied data in countries and companies The data check method and the data check device may be applied.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the functions that the processing apparatus should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium.

  When the program is distributed, for example, it is sold in the form of a portable recording medium such as a DVD (Digital Versatile Disc) or a CD-ROM (Compact Disc Read Only Memory) on which the program is recorded. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. Further, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

  The above-described embodiment is an example of a preferred embodiment of the present invention. However, the present invention is not limited to this, and various modifications can be made without departing from the scope of the present invention.

In addition, the following additional notes are disclosed regarding the above description.
(Appendix 1) A data check program for causing a computer to execute a process of checking management data including data applied from an unspecified number of people and data generated based on the applied data,
Obtaining check data generated from the management data of the first system;
Determining whether the data for checking is compatible with the second system based on a condition caused by a functional difference between the first system and a second system different from the first system;
A data check program for causing the computer to execute a process of outputting the type of the condition and the quantity of check data that does not conform to the second system obtained as a result of the determination based on the condition.
(Additional remark 2) The data check program of Additional remark 1 characterized by performing the said determination process before the management data transfer from the said 1st system to the said 2nd system.
(Supplementary Note 3) The data check program according to Supplementary Note 1 or 2, wherein the determination process determines whether or not a plurality of check data is consistent based on the condition.
(Supplementary Note 4) When there are a plurality of the conditions, the determination process determines based on each of the plurality of conditions,
The data check program according to any one of appendices 1 to 3, wherein, in the output process, a list of the types of the plurality of conditions and the quantity of check data that does not conform to the second system is output in a list. .
(Additional remark 5) In the said process to output, when outputting the classification of the said condition, and the quantity of the data for a check which do not suit the said 2nd system obtained as a result of the determination based on the said condition, the conditions used for the said determination The data check program according to any one of appendices 1 to 4, wherein the severity is output.
(Appendix 6) A data check method in which a computer executes a process of checking management data including at least one of data applied from an unspecified number of people and data generated based on the applied data,
An acquisition step of acquiring check data generated from the management data of the first system;
A determination step of determining whether or not the check data is compatible with the second system based on a condition caused by a functional difference between the first system and a second system different from the first system;
A data check method, wherein the computer executes an output step of outputting a type of the condition and a quantity of check data that does not conform to the second system obtained as a result of the determination based on the condition.
(Supplementary note 7) The data check method according to supplementary note 6, wherein the determination step is performed before the management data is transferred from the first system to the second system.
(Supplementary note 8) The data check method according to supplementary note 6 or 7, wherein, in the determination step, it is determined whether or not the plurality of check data is consistent based on the condition.
(Supplementary Note 9) In the determination step, when there are a plurality of the conditions, the determination is performed based on each of the plurality of conditions.
9. The data check method according to any one of appendices 6 to 8, wherein in the output step, a list of the types of the plurality of conditions and the quantity of check data that does not conform to the second system is output in a list.
(Additional remark 10) In the said output process, when outputting the classification of the said condition and the quantity of the data for a check which do not suit the said 2nd system obtained as a result of the determination based on the said condition, the condition used for determination is serious The data check method according to any one of appendices 6 to 9, wherein the degree is output.
(Appendix 11) A data check device for checking management data including at least one of data applied from an unspecified number of people and data generated based on the applied data,
An acquisition unit that acquires check data generated from the management data of the first system;
A determination unit that determines whether or not the check data is compatible with the second system based on a condition caused by a functional difference between the first system and a second system different from the first system;
A data check device comprising: an output unit that outputs the type of the condition and the quantity of check data that does not conform to the second system obtained as a result of the determination based on the condition.
(Additional remark 12) The said determination part performs the said determination before the management data transfer from the said 1st system to the said 2nd system, The data check apparatus of Additional remark 11 characterized by the above-mentioned.
(Supplementary note 13) The data check device according to supplementary note 11 or 12, wherein the determination unit determines whether or not a plurality of check data are consistent based on the condition.
(Supplementary Note 14) When there are a plurality of the conditions, the determination unit performs the determination based on each of a plurality of conditions,
The data check apparatus according to any one of appendices 11 to 13, wherein the output unit outputs a list of types of the plurality of conditions and a quantity of check data that does not conform to the second system.
(Supplementary Note 15) When the output unit outputs the type of the condition and the quantity of check data that does not conform to the second system obtained as a result of the determination based on the condition, the output unit 15. The data check device according to any one of appendices 11 to 14, wherein the severity is output.

10 Check tool terminal (data check device)
12 Acquisition unit 14 Data check unit (determination unit)
16 Output control part (part of output part)
22 Condition table (conditions)
95 Output section (part of output section)
100 Current system (first system)
200 New system (second system)

Claims (6)

A data check program for causing a computer to execute processing for checking management data including at least one of input data and data generated based on the input data ,
Obtaining check data generated from the management data of the first system;
Determining whether or not the plurality of check data are consistent based on a condition caused by a functional difference between the first system and a second system different from the first system;
A data check program for causing the computer to execute a process of outputting the type of the condition and the quantity of check data obtained as a result of the determination based on the condition that is not matched .   The data check program according to claim 1, wherein the determination process is performed before management data is transferred from the first system to the second system. The determination process is performed based on each of the plurality of conditions when there are a plurality of the conditions,
3. The data check program according to claim 1, wherein, in the output process, the plurality of condition types and the quantity of check data that does not conform to the second system are output in a list. In the output process, when outputting the type of the condition and the quantity of check data that does not conform to the second system obtained as a result of the determination based on the condition, the severity of the condition used for the determination is output. The data check program according to any one of claims 1 to 3 , wherein: A data check method in which a computer executes a process of checking management data including at least one of input data and data generated based on the input data ,
An acquisition step of acquiring check data generated from the management data of the first system;
A determination step of determining whether or not the plurality of check data are consistent based on a condition caused by a functional difference between the first system and a second system different from the first system;
A data check method, wherein the computer executes an output step of outputting the type of the condition and the quantity of check data obtained as a result of the determination based on the condition that is not matched . A data check device for checking management data including at least one of input data and data generated based on the input data ,
An acquisition unit that acquires check data generated from the management data of the first system;
A determination unit that determines whether or not a plurality of the check data are consistent based on a condition caused by a functional difference between the first system and a second system different from the first system;
A data check apparatus comprising: an output unit that outputs the type of the condition and the quantity of check data obtained as a result of the determination based on the condition, which is not matched .

Images