JP3358103B2 - Data integration method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data integration technique for creating a new record from records contained in databases of a plurality of provider business systems, and more particularly, to receiving database data from a plurality of provider business systems. The present invention relates to a data integration method suitable for improving the efficiency of construction of a business system and construction of a data warehouse (a database for decision support constructed by extracting database data from a plurality of provider business systems). Things.

[0002]

2. Description of the Related Art Data integration (hereinafter referred to as integration)
This is a process of creating a new record (integrated record) by putting together records that satisfy a specified condition, that is, integration conditions, among records included in databases of a plurality of business systems. Note that the maximum number of times that the record before integration satisfies the integration condition is called an integration radix.

An example of integrating a facility design record and a facility current state record will be described with reference to FIG. Where integration conditions,
The following assumptions are made regarding the integrated radix. Integration conditions: equipment design. Equipment code = Equipment status. Equipment code AND Equipment design. Construction completion date = Equipment status. Completion date of latest construction Integrated radix: Equipment design: 1 (one equipment status record 242 corresponding to equipment design record 241) Equipment status: 1 (one latest equipment design record 241 corresponding to equipment status record 242) In this case, three combinations of the equipment design record 241 and the equipment status record 242 associated with the arrows in the figure are integrated.

Next, an example of integrating transmission line records and leased line records will be described with reference to FIGS. As shown in FIG. 25, it is assumed that the transmission line 251 accommodates at most two dedicated lines 252, and the dedicated line 252 is always accommodated in one transmission line 251. That is, it is assumed that the integrated radix is as follows. Integrated radix: Transmission path: 2 (the transmission line accommodates two dedicated lines) Dedicated line: 1 (the transmission line accommodates one dedicated line) The following assumptions are made regarding the integration conditions. Integration conditions: transmission path. Transmission line code = dedicated line. Accommodating transmission line code In this case, as indicated by the arrow in FIG. 26, one transmission line record 261 and two dedicated lines 262
Are combined.

Conventionally, such integration has been realized by creating individual application programs. Hereinafter, two typical techniques related to the conventional integration processing will be described. First, an integration technique using all record files will be described with reference to FIG. The user system 277 performing the integration process is provided by the provider system X271.
Then, all the record files X273 and all the record files Y276 are received from the provider system Y274 and the record in the received all record files X273 and the record in the all record files Y276 are integrated. The problem with this technique is that the provider database X272 or the provider database Y40
5 is large, the transmission of all record files requires a lot of time, and the providing system X27
1 or the performance of the providing system Y274 is greatly squeezed.

Next, an integration technique using a difference file and ad hoc access to a provider database will be described with reference to FIG. The user side system 287 performing the integration process receives the difference files (the difference file X283 and the difference file Y28) from the provider system X281 and the provider system Y284 after the previous reception.
After receiving 6), integration is performed in the following procedure. First,
Integration is performed between the difference file X283 and the difference file Y286. Then, among the records of the difference file X283, for the records in which the number of times satisfying the integration condition has not reached the integration radix, the ad hoc access 289 is performed to the database Y285 of the provider system Y284, and the record of the integration partner is searched for. Try. Similarly, among the records of the difference file Y286, for records whose number of times satisfying the integration condition has not reached the integration radix, the ad hoc access 288 is performed to the database X282 of the provider system X281 to search for the record of the integration partner. Try.

[0007] If this integration technique is used, all new records that can be integrated are integrated at the time of integration processing. However, the problem of this technology is that when ad-hoc access 288 to the provider database X282 or ad-hoc access 289 to the provider database Y285 occurs, the performance of the provider system X281 or the provider system Y284 is reduced. It is pressure.

[0008] Further, the above two integrated technologies have a common problem that it is difficult to find a record omission in a provider database. As a simple solution to this problem, an error notification is given to the operator of the integrated processing system for all records whose number of times satisfying the integration condition is less than the integration radix, and the operator checks whether there is any omission of the integration partner of each record. It is conceivable to check However, in general, the operation of each provider system (data input and
There is no guarantee that the transmission of the difference file to the integrated processing system is synchronized, and the reception timing of a part of a record that should satisfy the integration condition may be shifted from the reception timing of another record. As a result, in the above-described solution technology, a large number of records whose reception time is simply shifted,
There is a risk that the operator will be notified of an error, and the above solution is impractical.

[0009]

The problem to be solved is that, in the prior art, transmission of all records from the providing system or ad-hoc access to the providing system is necessary, and The point is that the performance is squeezed, and the omission of record input to the provider database cannot be detected with high reliability and efficiency. An object of the present invention is to solve these problems of the prior art,
Eliminates the need to send all records from the provider system that sent the difference file or ad-hoc access to the provider system, thereby reducing the performance pressure on the provider system and saving records to the provider database. An object of the present invention is to provide a data integration method that enables easy detection of input omission.

[0010]

To achieve the above object, the data integration method of the present invention comprises the steps of (1) receiving each file transmitted from a plurality of databases, and storing each record in the received file. In the data integration method of evaluating whether or not a predetermined integration condition is satisfied and combining records satisfying the integration condition and creating a new record, the number of times that the integration condition of each record is satisfied is evaluated at the time of evaluation. It is counted for each record, and it is determined whether or not this number has reached the integration radix indicating the maximum number of times that the integration condition is satisfied. Is temporarily stored in association with the number of times satisfying the above, a difference file from the previous file newly transmitted from each database is received, and the records in the difference file are evaluated. At this time, evaluation and counting are performed including the temporarily accumulated records, and among the temporarily accumulated records, the records that satisfy the integration condition and reach the integration radix are discarded from the temporary accumulation, and the records in each difference file and the temporary Among the accumulated records, records whose number of times that the integration condition was satisfied did not reach the integration radix are temporarily stored in association with the number of times that the integration condition was satisfied for re-evaluation at the time of receiving the next difference file. And Also,
(2) Receiving each file transmitted from a plurality of databases, evaluating whether each record in each received file satisfies an integration condition specified in advance, and comparing records satisfying the integration condition with each other In summary, in the data integration method that creates a new record, the number of times that the integration condition of each record is satisfied is counted for each record during evaluation, and this number reaches the integration radix that indicates the maximum number of times that the integration condition is satisfied. The number of times that the integration condition was satisfied did not reach the integration radix, and the number of times that the integration condition was satisfied and the date and time of first reception are temporarily stored, and newly transmitted from each database. Received the difference file from the previous file, and evaluates and counts the records in the difference file, including the temporarily accumulated records, Of the records accumulated when the number of times that the integration condition was satisfied reached the integration radix, the records that had reached the integration radix were discarded from the temporary accumulation, and the number of records in each difference file and the temporarily accumulated records that satisfied the integration condition were the integration radix. Records that have not reached the number of records that are temporarily stored for re-evaluation at the time of receiving the next difference file, by associating the number of times that the integration conditions were satisfied with the date and time of first reception, and temporarily storing the data for this re-evaluation. Among them, a record that exceeds a preset storage time limit from the reception date and time is extracted and an error notification is performed. Further, (3) receiving each file transmitted from the plurality of databases, evaluating whether each record in each received file satisfies a pre-designated integration condition, and determining a record satisfying the integration condition. In a data integration method for creating a new record by putting together, at the time of evaluation, the number of times each record that satisfies the integration condition is counted for each record, and this number represents the maximum number of radix that satisfies the integration condition. The number of times that the integration condition was satisfied did not reach the integration radix, and the number of times that the integration condition was satisfied and the total number of evaluations (integrated processing times) were associated with each other. Accumulate and receive the difference file from the previous file newly transmitted from each database, and when evaluating the records in this difference file, include the temporarily accumulated records The number of records that satisfy the integration condition among the temporarily accumulated records is discarded from the temporary accumulation, and the integration condition of the records in each difference file and the temporarily accumulated record is discarded. Records for which the number of satisfies does not reach the integration radix are temporarily stored in association with the number of times that the integration condition is satisfied and the number of processes to be integrated for re-evaluation at the time of receiving the next difference file, and Out of the records temporarily stored in the storage device, the records in which the number of times of integration processing exceeds a preset number of times are extracted, and an error is notified. (4) In the data integration method according to any one of (1) to (3), the number of times that the integration condition is satisfied is registered in each record as the number of times that the integration condition is satisfied. This is characterized by adding a field to be performed.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS In the present invention, a record in which the number of times that the integration condition is satisfied is less than the integration radix is defined as a record that has a possibility of satisfying the integration condition, and the number of times that the integration condition is satisfied is associated with the record. , Temporary storage unit 2 shown in FIG.
To temporarily accumulate. Then, at the time of evaluation of the integration condition, data integration processing is performed for each record stored in the temporary storage unit 2 as an evaluation target in addition to each record in the received file. At this time, the number of times that the integration condition is satisfied is added to the newly integrated record. Records in which the addition result has reached the integrated radix are deleted from the temporary storage unit 2, and only those records that do not satisfy the integrated radix are stored in the temporary storage unit 2 in association with the addition results.

As described above, whether or not each record may satisfy the integration condition is determined based on whether or not the number of times that the integration condition is satisfied has reached the integration radix. As a result, when the file received from the providing system is not the entire record file but the differential file after the previous reception, the ad hoc access conventionally required can be replaced by the access to the temporary storage unit 2 and becomes unnecessary. Become. In other words, among records that may newly satisfy the integration condition, the total number of records in the difference file newly received and the records in the previously received file that satisfy the integration condition reach the integration radix. The record in the file received earlier is stored in the temporary storage unit 2 in the previous integration processing. Therefore, records that can newly satisfy the integration condition are all present in the received difference file or in the temporary storage unit 2, and according to the present invention, records that can be newly integrated are integrated without omission. .

In the present invention, the temporary storage expiration date and time is set and managed in advance as a temporary storage expiration threshold value of the temporarily stored record. That is, when a record is stored in the temporary storage unit 2, the first reception date and time of the record are associated with the number of times that the integration condition is satisfied. Then, for the record temporarily stored in the temporary storage unit 2, the elapsed date and time from the first reception date and time to the integration processing time is calculated, and it is determined whether or not the elapsed date and time exceeds the temporary storage expiration date and time. As a result, for example, an error can be efficiently detected when there is a record omission in the provider database.

In other words, if a record is omitted from the database on the provider side, the number of times that the record to be integrated with the record satisfies the integration condition does not reach the integration radix. At a predetermined time, an error is notified to the operator. The operator can confirm whether there is any omission of record input based on the error notification. Here, the error is notified to the operator only for the records temporarily stored beyond the period indicated by the temporary storage time limit. As a result, even if there is a difference in the reception timing of multiple records that should originally satisfy the integration condition, if the difference is within the temporary storage period, the received record will be notified to the operator in advance with an error. There is no. Therefore, there is little danger that a large number of records will be notified to the operator by error, and the present invention is a practical solution for finding omission of records into the provider database.

In the present invention, the number of times of integration processing (the number of times of integration processing = the number of times of temporary storage) is set and managed in advance as a threshold of the temporary storage time limit of the temporarily stored records. That is, when records are stored in the temporary storage unit 2, the number of times that the integration condition is satisfied and the number of times of temporary storage (the number of times of integration processing) are associated with each other. Then, for the record temporarily stored in the temporary storage unit 2,
The number of times of accumulation is added, and it is determined whether or not the addition result exceeds the number of times of integration processing. As a result, similarly to the case where the temporary storage expiration date and time is used as the threshold of the temporary storage expiration as described above, it is possible to efficiently detect errors in the omission of record input to the database on the provider side, and to detect omission of record input. Is a realistic solution.

[0016]

Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a flowchart showing a first embodiment of a process according to the present invention of the data integration method of the present invention,
FIG. 2 is a block diagram illustrating a configuration example of a system that performs the processing. The system for performing the data integration process of the present invention in FIG. 2 includes an integrated control information management unit 1 for managing integrated control information, a temporary storage unit 2 for temporarily storing records, and a pre-integration for adding a field to a record. Processing unit 3 and integrated record creation unit 4 for creating an integrated record
And a post-integration processing unit 5 that discards records or stores them in the temporary storage unit 2.

The operation of the data integration processing system having such a configuration according to the present invention will be described with reference to FIG.
First, the integrated control information management unit 1 sets and manages an integrated radix in advance for each combination of an integration condition and a record type (step 101). When a file is received from the provider system (step 102), the pre-integration processing unit 3
In FIG. 3, as shown in FIG. 3, the integration condition satisfaction count field 32 is added to the record 31 in the received file (step 103).

Next, the integrated record creation unit 4 evaluates integration conditions for the records in the received file and the records stored in the temporary storage unit, and creates an integrated record from a combination of records that satisfy the integration conditions (step 104). ). Then, in the post-integration processing unit 5, of the records in the received file and the records stored in the temporary storage unit 2, as shown in detail in FIG.
Some records are discarded, and the rest are stored in the temporary storage unit 2 (step 105).

FIG. 4 is a flowchart showing a detailed operation example of the post-integration processing in FIG. 1 according to the present invention. The subsequent operation is performed for each record in the received file and each record stored in the temporary storage unit (step 40).
1). First, one unprocessed record is taken out of each record in the received file and each record stored in the temporary storage unit (step 402), and a new integration condition Are added (step 403). Next, the value of the integration condition satisfaction count field 32 is compared with the integration radix managed by the integration control information management unit 1 (step 404), and records whose integration condition satisfaction count field 32 reaches the integration radix are discarded. Then, the record that does not reach is stored in the temporary storage unit 2 (step 406).

A specific example of such processing will be described with reference to FIGS. 5 to 7 by using an example of integration of a facility design record and a facility status record. Here, the integration conditions are as follows. Equipment design, equipment code = equipment status, equipment code AND
Equipment design, construction completion date = equipment status, latest construction completion date The integrated radix is as follows. Facility design: 1 (one facility status record corresponding to the facility design record) Facility status: 1 (one latest facility design record corresponding to the facility status record) Also, the initial state of both the provider system and the integrated processing system・ The contents of each provider database at the time of the first file reception shall be equal to the contents of the corresponding reception file. -It is assumed that there is no record stored in the temporary storage unit 2 of the integrated processing system.

First, as shown in FIG. 5, four records (equipment codes 1001 to 1004) are used as the first reception file 51 of the equipment design record, and two records (equipment code) are used as the first reception file 52 of the equipment status record. 1001, 1002). The integration conditions are evaluated for the records in each of the received files, and two integrated records (equipment code 100) are created as shown in the integrated record 61 created in the first integration process in FIG.
1,1002) Create. However, two of the equipment design records (equipment codes 1003 and 1004) whose integration condition satisfaction times are less than the integration radix (= 0) are the equipment design records stored in the temporary storage unit at the end of the first integration processing in FIG. The data is stored in the temporary storage unit 2 of FIG.

Next, as shown in FIG. 7, two records (equipment codes 1005 and 1006) are used as the equipment design record second reception file 71, and four records (equipment information) are used as the equipment status record second reception file 72. Codes 1003 to 1006) are received. By evaluating the integration conditions for the records in the reception files 71 and 72 and the record 62 of FIG. 6 stored in the temporary storage unit 2 of FIG. 2, the integration record 73 is created by the second integration processing. As shown, four integrated records (equipment code 1
003 to 1006) Create.

As described above, in each integration process, in addition to the record in the received file, the temporary storage unit 2 shown in FIG.
The records that have been stored in the database are also subjected to the integration condition evaluation, so that records that can be newly integrated can be integrated without omission. Further, the access to the temporary storage unit 2 in FIG. 2 replaces the ad hoc access to the provider database, which is required in the conventional technique, and becomes unnecessary.

Next, a second embodiment of the present invention will be described with reference to FIGS. FIG. 8 is a flowchart showing a second embodiment of the processing according to the present invention of the data integration method of the present invention. The processing of this example is the same as that of the first embodiment.
This is performed by the system having the configuration shown in FIG. First, the integrated control information management unit 1 sets and manages an integrated radix in advance for each combination of an integration condition and a record type (step 801). When a file is received from the providing system (step 802), the pre-integration processing unit 3 records the record 91 in the received file as shown in FIG.
, An integration condition satisfaction count field 92 and a reception date / time field 93 are added, and “0” is set as an initial value of the integration condition satisfaction count field 92.
The reception date and time are set as the initial value of (Step 80)
3).

Next, the integrated record creation unit 4 evaluates the integration conditions for the records in the received file and each record stored in the temporary storage unit 2, and creates an integrated record from a combination of records satisfying the integration conditions (step). 804). Then, the post-integration processing unit 5 discards some of the records in the received file and the records stored in the temporary storage unit 2 as shown in FIG. 2, and an error notification is given to the records temporarily stored in the temporary storage unit 2 that exceed the temporary storage time limit (step 805).

FIG. 10 is a flowchart showing a detailed operation example of the post-integration processing in FIG. 8 according to the present invention. The subsequent operation is performed for each record in the received file and each record stored in the temporary storage unit 2 (step 1).
11). First, one unprocessed record is extracted from each record in the received file and each record stored in the temporary storage unit 2 (step 112), and newly integrated into the integration condition satisfaction count field 92 in FIG. The number of times satisfying the condition is added (step 113).

Next, the integration condition satisfaction count field 9
The value of 2 is compared with the integrated radix managed by the integrated control information management unit 1 (step 114), and records in which the value of the integration condition satisfaction count field 92 has reached the integrated radix are discarded (step 115), and records not reached Is stored in the temporary storage unit 2 (step 116). Further, with respect to the records stored in the temporary storage unit 2, the elapsed date and time from the value of the reception date and time field 93 in FIG. 9 to the time of integration processing is compared with the temporary storage time limit managed by the integrated control information management unit 1 ( (Step 117), an error is notified to the operator of the record whose elapsed date and time has passed the temporary storage time limit managed by the integrated control information management unit 1 (Step 118).

A specific example of such processing will be described with reference to FIGS. 11 to 16 using an example of integration of the equipment design record and the equipment status record. Here, the integration conditions are as follows. Equipment design, equipment code = equipment status, equipment code AND
Equipment design, construction completion date = equipment status, latest construction completion date The integrated radix is as follows. Facility design: 1 (one facility status record corresponding to facility design record) Facility status: 1 (one latest facility design record corresponding to facility status record)

The temporary storage term is one day. Also,
Initialize both the provider system and the integrated processing system. • The contents of each provider database at the time of the first file reception shall be equal to the contents of the corresponding received file. -It is assumed that there is no record stored in the temporary storage unit 2 of the integrated processing system. The file is received from each provider system once a day.

First, as shown in FIG. 11, one record (equipment code 1002) is used as the equipment design record first reception file 111a, and one record (equipment code) is used as the equipment status record first reception file 112a. 1001) is received. The integration condition is evaluated for the records in each of the received files (111a, 112a). Here, since no record satisfies the integration condition, no integrated record is created. Then, records whose integration condition satisfaction times are less than the integration radix (= 0) (that is, all records in the reception files 111a and 112a) are stored in the temporary storage unit and the facility design record 113a, respectively. It is stored in the temporary storage unit 2 of FIG.

Next, as shown in FIG. 12, two records (equipment codes 1003 and 1004) are used as the equipment design record second reception file 121, and two records (equipment information) are used as the equipment status record second reception file 122. Codes 1002 and 1003) are received. Records in these received files (121, 122)
Record 11 of FIG. 11 stored in the temporary storage unit 2 of FIG.
By evaluating the integration conditions for 3a and 114a, as shown by the integration record 131 in FIG.
Two integrated records (equipment code 1002, 1003)
create. However, since the integration conditions are not satisfied for the equipment codes 1001 and 1004, the number of times that the integration conditions are satisfied is set to less than the integration radix (= 0), and the equipment design record 132 and the temporary storage section stored in the temporary storage section shown in FIG. Are stored in the temporary storage unit 2 of FIG.

Further, as shown in FIG. 14, two records (equipment codes 1005 and 1006) are used as the equipment design record third reception file 141, and two records (equipment code) are used as the equipment status record third reception file 142. 1004, 1005). Then, the integration conditions are evaluated for the records in these received files (141, 142) and the records 132, 133 of FIG. 13 stored in the temporary storage unit 2 of FIG. 151, two integrated records (equipment codes 1004, 100
5) Create.

However, since the integration conditions are not satisfied for the equipment codes 1001 and 1006, the number of times that the integration conditions are satisfied is set to less than the integration radix (= 0), and the equipment design record 152, which is stored in the temporary storage unit shown in FIG. The information is stored in the temporary storage unit 2 of FIG. 2 as the equipment status record 153 stored in the temporary storage unit. Here, of the records (152, 153) to be stored in the temporary storage unit 2, those whose elapsed date and time from the value of the reception date and time field to the integration processing time have passed the temporary storage time limit (= 1 day), that is, the equipment Code 1
The facility status record of 001 is notified of the error to the integrated processing system operator.

The operator checks the record for which the error has been notified in this manner, and, for example, checks the equipment design record 1
001 is detected as a missing input. in this way,
In this embodiment, when there is a record omission,
Eventually, the record of the integration partner is notified to the operator as an error. Further, an error notification is not given to a record whose received date shift is within one day (= temporary storage time limit) due to only the received date shift. Therefore, only a small number of records (“1” in the present embodiment) are notified to the operator as an error.

Next, a third embodiment of the present invention will be described with reference to FIGS.
This will be described with reference to FIG. FIG. 16 is a flowchart showing a third embodiment of the process according to the present invention of the data integration method of the present invention. The processing of this example is performed by the system having the configuration shown in FIG. 2 as in the first and second embodiments. First, the integrated radix is preset and managed by the integrated control information management unit 1 for each combination of the integration condition and the record type (step 161). When a file is received from the providing system (step 162), the pre-integration processing unit 3, as shown in FIG. 17, stores the integration condition satisfaction count field 172 and the integrated processing count field 173 in the record 171 in the received file. In addition, “0” is set as an initial value of the integration condition satisfaction count field 172 and the integration target count field 173, respectively (step 163).

Next, the integrated record creation unit 4 evaluates the integration conditions for the records in the received file and each record stored in the temporary storage unit 2, and creates an integrated record from a combination of records satisfying the integration conditions (step). 164). Then, the post-integration processing unit 5 discards some of the records in the received file and the records stored in the temporary storage unit 2 as shown in FIG. 2, and among the records stored in the temporary storage unit 2, an error is reported for a record temporarily stored beyond the temporary storage time limit (step 165).

FIG. 18 is a flowchart showing a detailed operation example of the post-integration processing in FIG. 16 according to the present invention. The subsequent operation is performed for each record in the received file and each record stored in the temporary storage unit (step 1).
81). First, one unprocessed record is extracted from each record in the received file and each record stored in the temporary storage unit 2 (step 182), and newly integrated into the integration condition satisfaction count field 172 in FIG. The number of times that the condition is satisfied is added (step 183).
"1" is added to the number of times of integration process field 173 of No. 7 (step 184).

Next, the value of the integration condition satisfaction frequency field 172 of FIG. 17 is compared with the integration radix managed by the integration control information management unit 1 (step 185). The record that has reached (step 186) is discarded, and the record that has not reached is stored in the temporary storage unit 2 (step 187). Further, regarding the record stored in the temporary storage unit 2, the value of the integrated processing count field 173 in FIG.
(Step 18)
8) An error is notified to the operator of a record in which the value of the integrated processing count field 173 has passed the temporary storage time limit managed by the integrated control information management unit 1 (step 18).
9).

A specific example of such processing will be described with reference to FIGS. 19 to 23, using an example of integration of a facility design record and a facility status record. The integration conditions are as follows. Equipment design, equipment code = equipment status, equipment code AND
Equipment design, construction completion date = current equipment status, latest construction completion date. Facility design: 1 (one facility status record corresponding to facility design record) Facility status: 1 (one latest facility design record corresponding to facility status record)

The temporary storage term is twice. Also,
Initialize both the provider system and the integrated processing system. • The contents of each provider database at the time of the first file reception shall be equal to the contents of the corresponding received file. -It is assumed that there is no record stored in the temporary storage unit 2 of the integrated processing system.

First, as shown in FIG. 19, one record (equipment code 1002) is used as the first reception file 191 of the equipment design record, and one record (equipment code 100) is used as the first reception file 192 of the equipment status record. 1001) is received. The integration conditions are evaluated for the records in each of the received files (191, 192). Here, since no record satisfies the integration condition, no integrated record is created. Then, records whose integration condition satisfaction times are less than the integration radix (= 0) (that is, all records in the reception files 191 and 192) are stored in the facility design record 193 and the temporary storage unit respectively stored in the temporary storage unit. As shown as the completed equipment status record 194, the temporary storage unit 2 stores the information. At this time, each record (facility code 100
1,1002) is added to “1”.

Next, as shown in FIG. 20, two records (equipment codes 1003 and 1004) are used as the equipment design record second reception file 201, and two records (equipment information) are used as the equipment status record second reception file 202. Codes 1002 and 1003) are received. The records in these received files 201 and 202 and FIG.
Records 193 and 193 in FIG.
By evaluating the integration conditions with respect to 194, FIG.
, Two integrated records (equipment codes 1002 and 1003) are created.
However, since the integration conditions are not satisfied for the equipment codes 1001 and 1004, the number of times that the integration conditions are satisfied is set to less than the integration radix (= 0), and the equipment design record 212 and the temporary As shown as the facility status record 213 stored in the storage unit, the information is stored in the temporary storage unit 2 of FIG. Here, the number of times of integration processing of the record of the facility code 1001 is “2”.

Further, as shown in FIG. 22, two records (equipment codes 1005 and 1006) are used as the third reception file 221 of the equipment design record, and two records (equipment information) are used as the third reception file 222 of the equipment status record. Codes 1004, 1005) are received. Then, the integration conditions are evaluated for the records in the received files 221 and 222 and the records 212 and 213 in FIG. 21 stored in the temporary storage unit 2 in FIG. Two integrated records (equipment codes 1004 and 1005) are created.

However, since the integration conditions are not satisfied for the equipment codes 1001 and 1006, the number of times that the integration conditions are satisfied is set to less than the integration radix (= 0), and the equipment design record 232 stored in the temporary storage unit in FIG. The information is stored in the temporary storage unit 2 of FIG. 2 as the equipment status record 233 stored in the storage unit. Here, of the records (232, 233) to be stored in the temporary storage unit 2, the number of integrated processings that have passed the temporary storage time limit (= 2), that is, the equipment status record of the equipment code 1001 is the integrated processing system An error is notified to the operator.

The operator checks the record for which the error notification has been made in this way, and detects, for example, that the equipment record 1001 in the equipment design database is missing. As described above, in the present embodiment, when there is a record omission, the error of the record of the integration partner is eventually notified to the operator. In addition, the reception shift is 2
No error notification is given to records within the number of times (= temporary storage time limit) due to only a difference in the number of receptions. Therefore, only a small number of records (“1” in the present embodiment) are notified to the operator as an error.

As described above with reference to FIGS. 1 to 23, in the data integration method of this embodiment, in addition to the records in the received file, the records stored in the temporary storage unit are also subjected to the integration processing. I do. This allows the receiving file from the provider system to be
It can be a difference file. Further, by accessing the temporary storage unit 2, ad hoc access to the providing system can be substituted. Therefore, compared to the conventional technology,
The pressure on the performance of the provider system can be reduced. Further, records whose total number of times satisfying the integration condition has reached the integration radix are discarded without being stored in the temporary storage unit 2, so that the number of records stored in the temporary storage unit 2 is continuously expanded without bound. There is no.

Furthermore, if there is a record omission, the number of times that the integration conditions of the integration partner record satisfy the integration condition does not reach the integration radix. The operator can confirm whether there is a record omission based on the error notification. In this case, in the present embodiment, an error is notified to the operator only for the records temporarily stored beyond the period indicated by the temporary storage time limit. As a result, even if a difference occurs in the reception timing of a plurality of records that should originally satisfy the integration condition, if the difference is within the temporary storage time limit, the error of the previously received record is not notified to the operator. Absent. Therefore, there is little risk that an operator is notified of an error in a large number of records, and the present embodiment is a practical solution for finding omission of record input.

The present invention is not limited to the embodiment described with reference to FIGS. 1 to 23, and can be variously modified without departing from the gist thereof. For example, by deleting from the temporary storage unit 2 the record for which the error notification has been made by the operator, it is possible to limit the number of records stored in the temporary storage unit.

[0049]

According to the present invention, the transmission of all records from the provider system or the ad hoc access to the provider system becomes unnecessary, and the pressure on the performance of the provider system can be reduced, and the provider database can be saved. , It is possible to detect the omission of the input record with high reliability and efficiency.

[Brief description of the drawings]

FIG. 1 is a flowchart showing a first embodiment of a process according to the present invention of the data integration method of the present invention.

FIG. 2 is a block diagram illustrating a configuration example of a system that performs the processing in FIG. 1;

FIG. 3 is an explanatory diagram showing a configuration example of a record to be processed in FIG. 1;

FIG. 4 is a flowchart showing a detailed operation example of the post-integration process in FIG. 1 according to the present invention.

FIG. 5 is a 1/3 part of an explanatory diagram showing a specific example of the processing in FIG. 1;

FIG. 6 is a 2/3 part of the explanatory diagram showing a specific example of the processing in FIG. 1;

FIG. 7 is a 3/3 portion of the explanatory diagram showing a specific example of the processing in FIG. 1;

FIG. 8 is a flowchart showing a second embodiment of the process according to the present invention of the data integration method of the present invention.

FIG. 9 is an explanatory diagram showing a configuration example of a record to be processed in FIG. 8;

FIG. 10 is a flowchart showing a detailed operation example of the post-integration process in FIG. 8 according to the present invention.

11 is a １ ／ part of an explanatory diagram showing a specific example of the processing in FIG. 8;

FIG. 12 is a 2/5 portion of the explanatory diagram showing a specific example of the processing in FIG. 8;

FIG. 13 is a 3/5 part of the explanatory diagram showing a specific example of the processing in FIG. 8;

FIG. 14 is a 4/5 portion of the explanatory diagram showing a specific example of the processing in FIG. 8;

FIG. 15 is a 5/5 portion of the explanatory diagram showing a specific example of the processing in FIG. 8;

FIG. 16 is a flowchart showing a third embodiment of the processing according to the present invention of the data integration method of the present invention.

FIG. 17 is an explanatory diagram showing a configuration example of a record to be processed in FIG. 16;

18 is a flowchart showing a detailed operation example of the post-integration processing in FIG. 16 according to the present invention.

FIG. 19 is a ５ part of an explanatory diagram showing a specific example of the processing in FIG. 16;

FIG. 20 is a 2/5 portion of the explanatory diagram showing a specific example of the processing in FIG. 16;

FIG. 21 is a 3/5 portion of the explanatory diagram showing a specific example of the processing in FIG. 16;

FIG. 22 is a 4/5 portion of the explanatory diagram showing a specific example of the processing in FIG. 16;

FIG. 23 is a 5/5 portion of the explanatory diagram showing a specific example of the processing in FIG. 16;

FIG. 24 is an explanatory diagram showing an example of integration of a conventional facility design record and a facility status record.

FIG. 25 is an explanatory diagram showing a conventional relationship between a transmission line to be integrated and a dedicated line.

FIG. 26 is an explanatory diagram showing a conventional example of integrating a transmission line record and a leased line record.

FIG. 27 is an explanatory diagram showing an example of a conventional integration process using all record files.

FIG. 28 is an explanatory diagram showing an example of a conventional integration process using a difference file.

[Explanation of symbols]

1: integrated control information management unit, 2: temporary storage unit, 3: pre-integration processing unit, 4: integrated record creation unit, 5: post-integration processing unit,
31: record in the received file, 32: integration condition satisfaction count field, 51: equipment design record first reception file, 52: equipment status record first reception file, 61: integrated record created in the first integration processing,
62: equipment design record stored in the temporary storage unit at the end of the first integration processing, 71: equipment design record second reception file, 72: equipment current status record second reception file, 73: created by the second integration processing Integrated records,
91: record in received file, 92: integration condition satisfaction count field, 93: reception date and time field, 11
1a: first received file of facility design record, 112
a: Equipment status record first received file, 113a:
Equipment design record 114a stored in the temporary storage unit:
Equipment status record stored in the temporary storage unit, 121: Equipment design record second reception file, 122: Equipment status record second reception file, 131: Integrated record created by the second integration process, 132: Temporary storage unit Accumulated facility design record, 133: Facility status record accumulated in the temporary storage unit, 141: Facility design record third reception file, 142: Facility status record third reception file, 151: Created by third integration processing Integrated record, 152: equipment design record stored in the temporary storage unit, 153: equipment status record stored in the temporary storage unit, 171: record in received file, 172:
Integration condition satisfaction count field, 173: integrated processing count field, 191: equipment design record first reception file, 192: equipment status record first reception file,
193: Equipment design record stored in temporary storage unit, 1
94: Equipment status record stored in the temporary storage unit, 20
1: Equipment design record second reception file, 202: Equipment status record second reception file, 211: Integrated record created by the second integration processing, 212: Equipment design record stored in the temporary storage unit, 213: Temporary storage Equipment status record, 221: equipment design record third reception file, 222: equipment status record third reception file, 231: integrated record created in the third integration process, 232: temporarily stored in the temporary storage unit 233: Facility status record stored in the temporary storage unit, 241: Facility design record, 242: Facility status record, 251: Transmission line, 252: Dedicated line, 26
1: transmission line record, 262: dedicated line record, 27
1: provider system X, 272: database X, 27
3: All record files X, 274: Provider system Y, 275: Database Y, 276: All record files Y, 277: User system, 281: Provider system X, 282 database X, 283: All difference files X, 284: providing system Y, 285: database Y, 286: difference file Y, 287: using system, 288, 289: ad hoc access.

──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Masakazu Okumura 3-19-2 Nishi Shinjuku, Shinjuku-ku, Tokyo Japan Telegraph and Telephone Corporation (56) References JP-A-4-199237 (JP, A) JP-A-4-360248 (JP, A) JP-A-6-214843 (JP, A) JP-A-5-225250 (JP, A) JP-A-5-81337 (JP, A) (58) Fields investigated ( Int.Cl. ⁷ , DB name) G06F 12/00 512 G06F 12/00 510 G06F 12/00 545

Claims (4)

(57) [Claims] 1. Receiving each file transmitted from a plurality of databases, evaluating whether each record in each received file satisfies a pre-designated integration condition, and determining a record satisfying the integration condition. In the data integration method of creating a new record by grouping together, at the time of the evaluation, the number of times of satisfying the integration condition of each record is counted for each record, and the number is the maximum number of times satisfying the integration condition. It is determined whether the integration radix has reached the integration radix, and records in which the number of times satisfying the integration condition has not reached the integration radix are temporarily stored in association with the number of times satisfying the integration condition, and newly stored. When a difference file from the previous file transmitted from each database is received, and when the records in the difference file are evaluated, the evaluation and the above-mentioned records including the temporarily accumulated records are performed. Of the temporarily accumulated records, the records in which the number of times satisfying the integration condition has reached the integration radix are discarded from the temporary accumulation, and the records in the respective difference files and the temporarily accumulated records are discarded. Records for which the number of times satisfying the integration condition has not reached the integration radix are temporarily stored in association with the number of times satisfying the integration condition for the evaluation at the time of receiving the next difference file. Data integration method. 2. Receiving each file transmitted from a plurality of databases, evaluating whether each record in the received file satisfies a pre-designated integration condition, and determining a record satisfying the integration condition. In the data integration method of creating a new record by grouping together, at the time of the evaluation, the number of times of satisfying the integration condition of each record is counted for each record, and the number is the maximum number of times satisfying the integration condition. It is determined whether the integration radix has reached the integration radix or not, and records in which the number of times satisfying the integration condition has not reached the integration radix are temporarily associated with the number of times satisfying the integration condition and the date and time of first reception. Receives a difference file from the previous file that has been accumulated and newly transmitted from each database, and evaluates the records in the difference file. The above-mentioned evaluation and counting are performed, and among the temporarily stored records, records in which the number of times satisfying the integration condition has reached the integrated radix are discarded from the temporary storage, and the records in the respective difference files and the temporary Of the accumulated records, records whose number of times that the above-mentioned integration condition was satisfied did not reach the above-mentioned integration radix are re-evaluated at the time of receiving the next difference file. Data integration characterized in that, among records temporarily stored in association with each other and temporarily stored for the re-evaluation, a record exceeding a preset storage time limit from the reception date and time is extracted, and an error notification is made. Method. 3. Receiving each file transmitted from a plurality of databases, evaluating whether each record in each of the received files satisfies an integration condition specified in advance, and records which satisfy the integration condition In the data integration method of creating a new record by grouping together, at the time of the evaluation, the number of times of satisfying the integration condition of each record is counted for each record, and the number is the maximum number of times satisfying the integration condition. It is determined whether or not the number of times that the integration condition has been satisfied does not reach the integration radix. The number of times that the integration condition has been satisfied does not reach the integration radix. (The number of processing times), temporarily store the data, and receive a difference file from the previous file newly transmitted from each of the above databases. The above evaluation and counting are performed including the temporarily accumulated records, and among the temporarily accumulated records, records in which the number of times satisfying the integration condition has reached the integrated radix are discarded from the temporary accumulation, and each of the difference files is discarded. Out of the records and the temporarily accumulated records, the records in which the number of times satisfying the integration condition did not reach the integration radix are re-evaluated at the time of receiving the next difference file. Extracting the records in which the number of times of the integrated processing exceeds a preset number of times from among the records temporarily stored in association with the number of times of the integrated processing and temporarily storing for the re-evaluation, and reporting an error. A data integration method characterized by the following. 4. The data integration method according to claim 1, wherein the number of times the record satisfies the integration condition is associated with the record by the number of times the record satisfies the integration condition. A data integration method characterized by adding a field for registering the data.