JPH11259351A - Data base device, shared data base device, shared data base system, data extracting method for shared data base device and storage medium recording data extraction program for shared data base device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To accept update data before the date of appointment by including condition data, with which the conditions of handling are determined, in the update data and executing reflecting processing or extracting processing, based on the condition data. SOLUTION: When the update data including the date of command and the date of appointment are transferred from respective data bases by purposes to a shared data base DB, an intermediate file generating part 130 generates a status managing table. The status managing table stores the date of command, the date of appointment and state code shoving the state of the update data. A state transition managing part 140 manages the state code by comparing the current date, the date of command and the date of appointment. When the state code indicates presence, the contents of an original data base 10 are reflected with the update data. When extraction applications 211-217 generate extraction data for respective data bases by purposes while referring to the state code, mask processing is performed by a mask part 230, a header is added by a post-processing part 240, and a file is transferred to the respective data bases according to the purposes.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention records a database device for autonomously managing the state of update data, a shared database device, a shared database system, a data extraction method for the shared database device, and a data extraction program for the shared database device. It relates to a recording medium.

[0002]

2. Description of the Related Art In an information society in recent years, various information processing apparatuses are used to support corporate activities.
For example, in a large company, business management is often performed by an individual database such as a personnel system, a salary system, or a company housing system.

In such a system, since processing is performed based on mutually related data, when data is updated by one application, the updated data is transferred to another application in the form of a file. Needs may arise. For example, suppose that an employee is transferred from one establishment to another due to promotion, and information on this transfer is first input to the personnel system. In this case, since the salary increases with the promotion, it is necessary to pass this information to the salary system, and since the place of work is changed, it becomes necessary to pass information about the company home to the company home system. Therefore, in the personnel system, a file is created by converting the data format so that the data relating to the employee's transfer can be read by the partner system. And
The other party's system reads the magnetic disk storing the file, or transfers the file via a communication network.

Here, if N systems are operating in relation to each other, the number of conversion applications of the entire system is N (N-1), and the number of systems constituting the entire system increases. Then, the number of required conversion applications increases dramatically. For this reason, there is a problem that the man-hour for developing the conversion application, the man-hour required for the conversion process, or the computer resources for storing the conversion application are consumed. Therefore, a shared database system has been developed in which data handled in common by each system is shared.

[0005] The shared database system is composed of an individual database and a shared database, and each individual database is connected to the shared database. When data is updated in each database, the updated data is standardized and stored in the shared database.
Then, standardized data is transferred from the shared database to another database as needed.

[0006] Since data updated in one database is not required in all other databases, when a shared database reflects the updated data from one database in the stored content, the shared database is updated for each other database. An update data extraction process is performed, and a process of transferring the extraction result to another database is executed.

[0007]

In the business management system described above, data to be updated may be known in advance. For example, information on a change of an employee occurs before the date of issuing the change or the appointment date at which the change is actually made. In this case, if the search date is before the appointment date, the old affiliation should be output as the search result, and if the search date is after the appointment date, the new affiliation should be output as the search result in the database that can search for the affiliation of the employee. It is. Therefore, in the conventional business management system, even if the update data is generated in advance, it is necessary to take the update data into the database after the appointment date.

When a job such as transfer, recruitment, or promotion occurs, data may be updated in one database based on the date of issuance, and may be updated in another database based on the appointment date. Therefore, in the conventional business management system, it is necessary to fetch update data according to the type of data or the type of database, and the work is complicated.

The present invention has been made in view of the above-described circumstances, and provides a database device that manages the state of update data and can automatically reflect the update data to stored contents at a required timing. The purpose is to do.

[0010]

According to the first aspect of the present invention, there is provided an information processing apparatus, comprising: storage means for storing a plurality of data in association with each other; A database device to which data is input, wherein it is determined whether or not a condition is satisfied based on storage means for storing the input update data and condition data relating to the update data read from the storage means. It is characterized by comprising a determining means, and a reflecting means for reflecting the update data in the storage content of the storage means when the result of the determination by the determining means satisfies a condition.

Further, in the invention according to claim 2, the condition data indicates an update time, and the determination means compares the current time with the time indicated by the condition data to determine the condition. Or not.

According to a third aspect of the present invention, there is provided a database device comprising storage means for storing a plurality of data in association with each other, and receiving update data including a plurality of condition data indicating handling conditions. A storage unit that stores the input update data, and a determination unit that determines whether each condition is satisfied based on a plurality of condition data related to the update data read from the storage unit.
A status data generating unit that generates status data indicating a status of the update data based on a determination result of the determination unit; a management table generating unit that generates a management table that associates the status data with the update data; When the data is changed, the content of the change is reflected in the management table, and when the content of the management table is monitored and the status data indicates that the updated data is reflected, the content of the storage is stored in the storage unit. And a state management means for reflecting the update data.

Further, in the invention according to the fourth aspect, a shared database device in which updated data including a plurality of condition data indicating handling conditions is supplied from a plurality of individual database devices handling data related to each other. A storage unit that stores a plurality of data in association with each other, a storage unit that stores update data supplied from each of the individual database devices, and a plurality of condition data related to the update data read from the storage unit. Determining means for determining whether each condition is satisfied, based on the determination result of the determining means, status data generating means for generating status data indicating a status of the update data; and A management table generating means for generating a management table for associating update data; and a management table when the status data is changed. When the status data indicates that the update data is to be reflected by monitoring the content of the management table while reflecting the change content in the management table, the status management that reflects the update data in the storage content of the storage unit is performed. Means for extracting and extracting required data from the storage means and the storage means by referring to the status data stored in the management table in accordance with rules defined for each individual database device Extraction means for generating data, and transfer means for transferring the extracted data to the corresponding individual database devices, respectively, are provided.

Further, in the invention according to claim 5, the shared database device performs business management,
The plurality of condition data indicate an issue date and an appointment date of a task, and the determination means determines each condition by comparing a current date with an issue date and an appointment date indicated by the condition data, and determines the condition data. The generating means, if the current date is before the issuance date, status data indicating an undetermined future, and if the current date is after the issuance date and is before the appointment date, status data indicating a determined future, When the current date is after the appointment date, status data indicating the present is generated, and the status management means monitors the contents of the management table and stores the status data when the status data reaches the current date. The update data is reflected in the storage contents of the means, and the extracting means refers to the state data stored in the management table according to a rule defined for each individual database device. It allows to extract the data even before appointment date is required from the storage unit and generates the extracted data.

In the invention according to a sixth aspect, the apparatus further comprises the shared database device, a plurality of individual database devices, and a communication network connecting the shared database device and the plurality of individual database devices. When the update data updated in the individual database device is transferred to the shared database device via the communication network, the shared database device reflects the update data in the storage content of the storage device, and the storage device Alternatively, the extracted data extracted from the storage unit is transferred to another individual database device via the communication network.

According to the present invention, there is provided a storage means for storing a plurality of data in association with each other, and the update data including a plurality of condition data indicating handling conditions is used to store mutually related data. A method of extracting data of a shared database device supplied from a plurality of individual database devices to be handled, wherein the update data supplied from each of the individual database devices is stored in a storage unit, and the update data read from the storage unit A step of determining whether or not each condition is satisfied, based on a plurality of condition data related to, and a step of generating state data indicating a state of the update data based on the determination result; and Generating a management table for associating update data with the management table; Together to reflect the changes to the Le, when the status data to monitor the contents of the management table indicates that to reflect the update data,
Reflecting the update data in the storage contents of the storage means, and referring to the state data stored in the management table in accordance with a rule determined for each of the individual database devices, whereby the storage means and the The method includes the steps of: extracting required data from storage means to generate extracted data; and transferring the extracted data to each of the corresponding individual database devices. Further, the invention according to claim 8 is characterized in that the recording medium is a recording medium that records a data extraction program of a shared database device that causes a computer device to execute the data extraction method of the shared database device.

[0017]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a shared database system according to an embodiment of the present invention will be described with reference to the drawings.

1. Configuration of Embodiment 1-1. Overall Configuration First, the overall configuration of the shared database system will be described. FIG. 1 is a block diagram showing the overall configuration of the shared database system. Although the shared database system can be applied to various types of information processing, an example applied to business management will be described here.

In the figure, a shared database system D
B includes purpose-specific databases S1 to S7 arranged at different locations, an original database 10 for accumulating standardized data, and purpose-specific databases S1 to S7.
It is composed of a local area network LAN connecting the S7 and the shared database 10, respectively.

Each of the purpose-specific databases S1 to S7 is composed of, for example, a personal computer, in which an individual database is constructed. For example, the personnel system S1 manages personnel changes, attendance, evaluation, family composition, etc. of the employee, the salary system S2 manages the employee's salary, the pension system manages the payment of pensions to retirees, The company housing system manages the occupancy status of the company housing, and the retirement allowance system S5
Manages the retirement allowance of each employee, the distribution system S6 manages the distribution, and the accounting system S7 manages the accounting of the entire company.

Such purpose-specific databases S1 to S
7 are closely related to each other. For example, the employee's attendance data stored in the personnel system S1 is also required in the salary system S2 to reflect the employee's salary on the employee's salary. In addition, when an employee desires a company house, it is necessary to arrange the company house in consideration of the family structure, so family data is required in the company house system S4. Therefore, if there is an update in the data stored in each of the purpose-specific databases S1 to S7, the update data is transferred in a file format, so that the shared database DB once collects the update data, and the shared database DB collects the update data. The files used for updating are transferred to S1 to S7.

Next, the main part of the shared database DB is:
It comprises an original database 10 and a database management mechanism 20. By the way, each purpose-specific database S1 to S
The data type of 7 (for example, the number of characters in one data) depends on those applications. Therefore, the database management mechanism 20 standardizes the transfer files from the purpose-specific databases S1 to S7 to generate standard data, and stores the standard data in the original database 10. When transferring data to the purpose-specific databases S1 to S7, the database management mechanism 20 performs a process of extracting required standard data from the original database 10. For this reason, the data structure of the original database 10 is grouped so that the extraction process can be executed efficiently. Specifically, it is composed of various tables such as employees, educational backgrounds, and affiliations, and can be searched by specifying the table name.

1-2: Functional Configuration Next, the functional configuration of the main part of the shared database DB will be described. FIG. 2 is a functional block diagram showing a functional configuration of the shared database DB. As shown in the figure, the shared database DB includes an original database 10 and a database management mechanism 20.

The data stored in the original database 10 is roughly classified into received data, current data, and past data. The current data indicates the current data and is stored in the current database, and the past data indicates the immediately preceding data and is stored in the immediately preceding database. Each database is composed of a plurality of tables, for example, an affiliation table in which employee codes are stored in association with department names to which they belong, an educational history table in which employee codes are stored in association with educational backgrounds, or an employee code. And various types of tables such as a family table storing the family information in association with each other. On the other hand, the received data is data generated in accordance with the occurrence of some business, and is used as data for managing the status of the current data or data before the appointment date,
It consists of a status management table, an acceptance data configuration table, and an event table. Note that these tables will be described later.

The database management mechanism 20 reflects the update files transferred from the purpose-specific databases S1 to S7 on the original database 10
0 and an extraction processing mechanism 200 that extracts updated data from the original database 10 and generates files to be transferred to the purpose-specific databases S1 to S7.

First, the reflection processing mechanism 100 includes the pre-processing unit 1
10, standardization processing unit 120, intermediate file generation unit 130
And a state transition management unit 140. The pre-processing unit 110 detects and corrects an error occurring in the communication path and deletes the header / trailer for the update file transferred from each of the purpose-specific databases S1 to S7. The standardization processing unit 120 standardizes the data type and the grouping. In the standardization of the data format, for example, as described above, the number of characters of one data is made uniform and standard data is generated. In standardization of grouping, data is grouped so as to conform to the data structure of the original database 10, and a standardized file is generated.

Next, the intermediate file generating section 130 generates an intermediate file while referring to various tables stored in the original database 10 and table column information designating the contents of the columns. This intermediate file includes a status management table, a received data configuration table, and an event table. These tables are generated when any event relating to the update of the original database 10 occurs.

In the human resource management system,
Time management is important. For example, in a personnel change, there are an issue date that informs the person of the personnel change and an appointment date with the actual change, but the meanings of the announcement date and the appointment date are different. Even so, the date for updating the data differs depending on the purpose-specific databases S1 to S7. In view of this, the status management table stores data indicating the status of the data relating to the update, and the reflection extraction process is performed by referring to the data.

Next, the state transition management unit 140 manages the state by comparing the current date with the date of issue and the date of appointment stored in the status management table.

Next, the extraction processing mechanism 200 includes extraction applications 211 to 217 provided for each purpose-specific database S1 to S7, a schedule unit 220 for controlling the activation of these applications, and ones created by the extraction applications 211 to 217. A mask unit 230 for masking items that are not appropriate for security reasons from items of the next extraction file, and a post-processing unit 240 for adding a header / trailer
It is composed of

The schedule section 220 has a calendar function, and can set a start date and time so that predetermined extraction applications 211 to 217 are started on a preset date. If the closing date of salary is 15th every month and the payment date is 25th, the setting is made so that the extraction applications 211 to 217 corresponding to the salary system S2 are activated on the 17th of every month, for example, on the 25th. do it.

The extraction applications 211 to 217
A data to be transferred to each purpose-specific database S1 to S7 is extracted to generate a primary extraction file, and a target data specifying unit M1 for specifying a target key to be extracted, and a target key using the target key And a connection data generation unit M2 for generating a primary extraction file for each of the purpose-specific databases S1 to S7 by combining the extracted tables.

Here, each extraction application 211-
217 is basically independent to extract data conforming to the specifications of the purpose-specific databases S1 to S7. Therefore, the extraction applications 211 and 2
17 may be configured as separate and independent components.

However, when the extraction applications 211 to 217 are configured in this manner, the amount of programs becomes enormous, and when the specifications of the purpose-specific applications S1 to S7 are changed, the extraction applications 211 to 211 are adjusted to the changed specifications. 217 need to be recreated from the beginning. Further, when a new purpose-specific database is added, it is necessary to create a new extraction application from the beginning. Therefore, extraction application 2
If the components 11 to 217 are separately and independently configured, the amount of programs is enormous, the number of development steps is large, and when the purpose-specific databases S1 to S7 in operation are changed or when a new purpose-specific database is added. There is a problem that it takes man-hours and time.

Therefore, in the present embodiment, a plurality of functions used in the extraction process are modularized, and the functional modules are shared. Specifically, the target data specifying unit M1 of each of the extraction applications 211 to 217
And the function of the connection data generation unit M2 are modularized, and necessary ones are read out from a plurality of functional modules and parameters are given to them. By sharing these function modules, the amount of programs can be reduced, and by combining function modules,
It is possible to flexibly cope with a change in the specifications of the purpose-specific databases S1 to S7 and the expansion thereof.

Next, each extraction application 211-2
The seventeen target data specifying units M1 specify target keys to be extracted from the following viewpoints. The target key is
This is a key item when searching for data to be extracted, for example, a name code. Extraction period range First, the data extraction period range indicates the range in which changed data is extracted.
1) On a daily basis, 2) From the previous extraction date to the present, 3) Specific date or specific time, 4) There is a certain period. The processing on a daily basis corresponds to, for example, totaling of sales amounts used in the accounting system S7. Further, the processing from the previous extraction date to the present is the most general processing, for example,
It is used for updating according to an address change required in the company housing system S4. Also, as the processing for a certain period, for example,
Aggregation of time data used in the personnel system corresponds to this. Each of the above processes 1) to 4) is modularized as a period designation module, and each extraction application 2
11 to 217 can specify a period by executing a required period specifying module.

Determination of Extractable Table Next, the following processing is performed as a module for determining an extractable table. 1) Extraction is executed immediately after reception / reflection, 2) Extraction is executed after the current value data is changed, 3) Extraction is executed when a condition occurs. Extraction is executed immediately after reception / reflection. This corresponds to a case where data accompanying the promotion of an employee is transferred to the salary system S2 in order to perform the salary calculation efficiently. Also,
The function module that performs extraction when a condition occurs is provided, for example, by updating the update file at the appropriate timing for a purpose-specific database that updates based on the date of issue or a database that updates based on the appointment date. In order to transfer.

Extraction of Related Tables Next, as processing for extracting related tables, the following are modularized. There are 1) extraction of a specific key range irrespective of a change, 2) extraction related to a specific business occurrence, and 3) extraction related to a change in specific data. As an extraction of a specific key range that is not related to changes, for example,
Limited by area such as Kanto or Tohoku. The extraction related to the occurrence of a specific event corresponds to, for example, a case where the workplace of a specific person is changed due to a personnel change. Further, the change of the specific data corresponds to, for example, a change in the occupation status such as absence from work or employment. As described above, the target data specifying unit M1 determines the extraction period range, the table that can be extracted, and the extraction of the related table from the viewpoints
A target key is generated by reading a modularized function module and giving parameters to it.

Next, the connection data generation unit M2 reads the corresponding tables from the original database 10 based on the target key and combines them to generate a primary extraction file. There are the following modes of joining tables. This is to extract various tables stored in the original database 10 in units of tables. Combining related current value tables This is to extract and combine tables of the current database stored in the original database 10, which is the most common form of joining.

Combination of Related Current Value Table and Previous Table This is to extract and combine tables having the same table name of the current database and the previous database stored in the original database 10. Combining a plurality of occurrences in the same table For example, a case where a plurality of families having the same name code are extracted and combined, or a case where a plurality of qualifications are extracted and combined with their qualification data.

Combining Key Search Results with Foreign Keys In this method, after a table is searched using extracted key information such as a name code, a search is further performed using the extracted table items as keys to obtain predetermined item values. In this case, this is embedded in the output table. For example, when there is a first table for storing a name code and a belonging organization code and a second table for storing the belonging organization code in association with the belonging organization name, the first code is used as the first key as extraction key information. When a table is searched and an organization code is acquired therefrom, the second table is searched using this organization code as a key to obtain an organization name, and this is embedded in place of the organization code in the first table. Is applicable.

Joining related tables including past and future This is to extract and join related tables including past and future. For example, information such as past affiliation and previous job is extracted and joined. This is the case. The joining process of these tables is also modularized, and a transfer file satisfying the specifications of the purpose-specific databases S1 to S7 can be generated by appropriately selecting and combining the functional modules. In each functional module, a table to be combined is given as an extraction parameter. Thus, the extraction program 2
11 to 217 are configured by the target data specifying unit M1 and the connection data generating unit M2. 1) The specification of target data (generation of extraction key information) is mainly performed by state management described later. The generation of connection data is a common use of data extraction processing (table access processing), and has different characteristics. 2) Even if a file interface is provided between two blocks, the overhead is very small.

Next, the mask section 230 stores a mask parameter which defines what item is to be masked for each purpose-specific database S1 to S7, and masks unnecessary items using this mask parameter. Is performed. The post-processing unit 240 converts the character code into a character code suitable for transmission, adds a header / trailer, and generates a transfer file for each purpose-specific database S1 to S7.

2. Operation of Embodiment Next, the operation of the embodiment will be described. 2-1: File transfer processing from the purpose-specific database to the shared database When data is updated in the purpose-specific databases S1 to S7, the purpose-specific databases S1 to S7 store tables relating to the updated data in the shared database DB. Forward. Here, a table transferred by the personnel system S1 will be described as an example. In this example, the personnel system S
1 has the same data structure (how to hold tables) as the data structure of the original database 10, and the data constituting the file transferred from the personnel system S1 has a standard data format. It shall be.

In the personnel system S1, if a personnel change occurs in a certain employee, the personnel system S1 generates an update table including a set of the name code of the employee, the date on which the personnel change was issued and the appointment date, and update information. . in this case,
Since the affiliation and workplace of the employee are changed with the occurrence of a transfer (event), various tables such as a transfer table, a affiliation table, and a workplace table stored in the original database 10 are updated. Need arises. For this reason, the update tables are generated only for the types of tables that need to be changed among the various tables stored in the original database 10. For example, if it is necessary to update n tables, in the personnel system S1, as shown in FIG.
Ln is generated, and the event management tables TBLa1 to TBLan shown in FIG. 3B are generated.

Each of the event management tables TBLa1 to TBLan includes a name code, a data type code, and a related table name. Here, the data type code is
It indicates what kind of business has caused the data to be updated. For example, a code is assigned so that the business can be distinguished, such as "01" for transfer and "02" for retirement. I have. The table name column stores the table name of the original database 10 that is changed by the job. In this example, the tables related to updating are TBL1 to TBLn, and these are stored as table names.

When the above-mentioned tables TBL1 to TBLn and the event management tables TBLa1 to TBLan are transferred to the shared database DB via the LAN, the database management mechanism 2
0, the intermediate file generation unit 130 stores
The date when these are accepted is added to Ln as the date of business occurrence, and event tables TBL1 'to TBLn' are respectively generated as shown in FIG. 3A, and received data configuration tables TBLb1 to TBLbn shown in FIG. Generate The received data configuration tables TBLb1 to TBLbn are the event management tables TBLa1 to TBLa
It is the date of work addition to BLan. Therefore,
By referring to the received data configuration tables TBLb1 to TBLbn, it is possible to know which table has been updated.

Further, the intermediate file generation unit 130 generates a status management table TBLc in which the date of occurrence of a task is added to the event management tables TBLa1 to TBLan and information on the status of the task (current status, status transition execution date and time) is added. I do. The writing of the information on the status of the business will be described in detail in the status transition process. The event tables TBL1 'to TBLn', the received data configuration tables TBLb1 to TBLbn, and the status management table TBLc thus generated are stored in predetermined storage areas of the original database 10.

The purpose-specific databases S1 to S
The updating of the data in 7 is performed in principle after the appointment date. Therefore, the purpose-specific databases S1 to S7
Is usually transferred to the shared database DB. However, in the present embodiment, the event management tables TBLa1 to TBL
Since an is included in the update data and transferred to the shared database DB, the update data can be transferred to the shared database DB before the appointment date, and the original database is referred to by referring to the issuance date and the appointment date in the shared database DB. The update data can be reflected on the server 10, or the extraction process can be executed at an appropriate time.

2-2: State Transition Processing The shared database system 1 determines the state of data from (1) undetermined future, (2) determined from the relation between the operation date (current date), the issue date, and the appointment date. Future, (3) present,
(4) It is managed in four stages such as the past,
The state transition management unit 140 reflects these states in the status management table TBLc. Specifically, (1)-
The status code (2 bits) indicating the status of (4) is stored in the status management table TBLc.

Here, the undetermined future state refers to a state in which the operation date is before the issuance date and the operation date is before the appointment date. Also,
The state of the determined future is a state in which the operation date is after the issuance date and the operation date is before the appointment date. The current state means that the operation date is after the issuance date and the appointment date and is the latest one. The past means that the operation date is after the issuance date and the appointment date and is in the past.

By the way, since the status management table TBLc stores the table name that needs to be changed in accordance with the occurrence of a certain task as described above, if the status management table TBLc is referred to, the status of the related table is obtained. Can be centrally managed.

FIG. 5 is a diagram showing state management using the status management table TBLc. In the figure, when the status management table TBLc is sent to the status transition management unit 140, the status transition management unit 140 compares the operation date with the issuing date and the appointment date stored in the status management table TBLc, as follows. A status code is generated (X0).

First, if the operation date is before the issuance date and the operation date is before the appointment date, the process proceeds to the undetermined future state X1 via the path P1, and the status code 00 indicating the undetermined future is stored in the status management table TBLc. Store. For example, this corresponds to a case where a job scheduled to be raised occurs.

Next, when the operation date is after the issuance date and the operation date is before the appointment date, the process proceeds to the determined future state X2 via the path P2, and the status code 01 indicating the determined future is stored in the status management table. Store in TBLc. For example, this corresponds to a case where a job of relocation occurs.

Next, if the operation date is after the issuance date and the operation date is after the appointment date, the process proceeds to the current state X3 via the path P3, and the status code 10 indicating the present is stored in the status management table TBLc. To be stored. For example, this corresponds to a case where various correction operations occur. If the issuance date and the appointment date are the same day and the operation date is after the issuance date, the process proceeds to the current status X3 via the path P4 and stores the status code 10 indicating the current status in the status management table TBLc. I do.

As described above, the status code is stored in the column of the current status of the status management table TBLc, and the status transition execution date and time indicating the date and time of transition to the current status are stored in the status management table TBLc.

Thereafter, the state transition management section 140 reads out the status management table TBLc every day, compares the issued date and the appointment date stored therein with the operation date, and executes the state transition processing. In this case, the state transition management unit 140
Reads the status code, date of issue, and date of appointment stored in the status management table TBLc. Then, the status of the job is detected from the read status code. Next, the operation date is compared with the issuance date and the appointment date to grasp the state of the operation day. If there is a change in the business status, the status management table TBLc is updated. On the other hand, if there is no change in the business status, the status management table TBLc is not updated.

For example, if the read status code is 00 and the operation date and the issuing date match, the business changes from the undetermined future state X1 to the confirmed future state X2 via the path P5. In this case, the status code 01 is stored in the column of the current status of the status management table TBLc, and the date and time when the status transition was executed is stored in the column of the status transition execution date and time.
Update the status management table TBLc. The status management table TBLc is similarly updated when the state changes from the undetermined future state X1 to the current state X3 via the path P6 and from the confirmed future state X2 to the current state X3 via the path P7.

By the way, when a personnel change occurs in a certain employee and the appointment date has passed, the state of the business concerned is the current state X3, but it is assumed that the next personnel change has occurred in this employee. In this case, when the operation day reaches the appointment date of the next personnel change, there will be two status management tables TBLc for the personnel change of the employee, but the accurate data of the employee will be stored in the new status management table TBLc. Therefore, the old status management table TBLc needs to be distinguished from the new one. For this reason, when the latest status management table TBLc is generated for the status management table TBLc in the current state X3, the old work is handled as the past state X4.

More specifically, the paths P3, P4, P6, P7
Status management table TB that has reached the current state X3 via
When Lc occurs, another status management table TBLc currently in the state X3 is searched using the name code and the data type stored therein as key information. If applicable items are extracted, their status management tables
The status management table TBLc is updated by storing the status code 11 in the column of the current status of the TBLc and the date and time when the status transition was executed in the column of the status transition execution date and time. The status management table TBLc in the past state X3 is deleted when the deletion application is activated (P9, X5). In this case, the event tables TBL1 'to TBLn' related to the status management table TBLc and the received data configuration tables TBLb1 to TBL
bn is also deleted at the same time. The deletion application may be set to be started periodically, such as once a month.

As described above, the status management table TBLc
Since the status of the business on the operation day is stored as a status code, by referring to the business occurrence date, name code and data type code of the status management table TBLc, the event tables TBL1 ′ to TBLn ′, the received data configuration Tables TBLb1 to TBLbn can be managed,
Reflection processing and extraction processing can be performed according to the status of business.

2-3: Reflection Processing Next, the reflection processing of the current data stored in the original database 10 will be described. FIG. 6 shows the current data reflection processing operation. First, the reflection processing mechanism 100
State transition management unit 140, the status management table TB
With reference to Lc, from the current state X3, the one whose state transition date and time matches the operation day is extracted. In this case, in the extracted status management table TBLc, the operation date and the appointment date match. Since the current data represents information such as the affiliation of each employee at a certain point in time,
The data received on the appointment date needs to be reflected in the current data. For this reason, the state transition management unit 140 refers to the work occurrence date, the name code, and the data type code of the extracted status management table TBLc, and stores the related event tables (TBL1 ′ to TBLn ′ in FIG. 3A). Read and update the current database DB1. This updating process is performed every day, and the current database one day ago is stored as the immediately preceding database DB2.

The above is the principle reflection processing. However, due to various circumstances such as a case where data input is forgotten, a failure of the communication line, a failure of the purpose-specific databases S1 to S7, etc. Acceptance data may be generated. In such a case, the content is reflected on the current database DB1 and, if necessary, the content is reflected on the immediately preceding database DB2.

As described above, since the state transition management unit 140 performs the update data reflection processing by referring to the state code of the status management table TBLc, the purpose-specific databases S1 to S7 can be stored even before the appointment date. Update data can be transferred to the shared database DB. As a result, it is possible to transfer update data from the purpose-specific databases S1 to S7 at an arbitrary timing.

2-4: Extraction Processing Next, the extraction processing performed by each of the extraction applications 211 to 217 will be described separately for the key information file generation processing and the connection data generation processing.

2-4-1: Key Information File Generation Processing The key information file generation processing is executed in the target data specifying unit M1 of each of the extraction applications 211 to 217. The target data specifying unit M1 first detects the timing at which the extraction process is performed by the functional module that specifies the extraction timing, and starts the extraction process at a predetermined timing. For example, the payroll system S2 executes a huge amount of calculation processing, so it is necessary to know information about promotion as soon as possible. Therefore, in the corresponding extraction application 212, it is necessary to execute the extraction process even if the operation date is before the appointment date, so that the status code of the status management table TBLc is 01 (determined future status X2).
Starts the extraction process. That is, based on conditions for handling update data, such as an appointment date and an operation date, the state of the update data is held as a status code, and the extraction process is performed by referring to the status code. Or the extraction process can be performed on the date of the announcement.

Next, the target data specifying unit M1 specifies an extraction period range. In the case of extracting a status change on a daily basis, the status change date and time in the status management table TBLc are referred to, and those whose date matches the operation date are extracted. Also, when extracting data that has changed since the previous extraction date, the previous extraction date is compared with the status transition date and time of the status management table TBLc, and those whose status transition date and time are later than the previous extraction date are extracted. . On a specific date (for example,
When extracting data on the 25th of each month), the data is extracted with reference to the key value currently assigned to the data.
Also, when extracting data that has changed over a certain period of time,
With reference to the work occurrence date in the acceptance data configuration table, for example, the data accepted by the shared database DB from one day to the end of the month is extracted.

Further, the target data specifying unit M1 performs an extraction process on the data limited by specifying the extraction period range from the following viewpoints. First, when extraction is performed irrespective of a change in data, key information serving as an extraction key is designated, the database DB1 is currently searched, and a name code stored in a corresponding table is extracted. In this case, the key information is given as an extraction parameter. Particularly important extraction processes are a data extraction process relating to the occurrence of a specific task (event) and a data extraction process relating to the occurrence of a change in specific data. The former is convenient when updating the purpose-specific databases S1 to S7 in association with a job such as recruitment or transfer, while the latter is used to store relevant data when specific data changes regardless of the occurrence of the job. Useful for updating.

When executing data extraction processing relating to the occurrence of a specific job, a data type code in the status management table TBLc is searched for a code that matches a code given as an extraction parameter, and a corresponding name code is retrieved. Is extracted. When executing a data extraction process related to a change in specific data, a table name is given as an extraction parameter. For example, if data relating to address change is to be extracted, the table name of the address table is used as an extraction parameter. In this case, referring to the received data configuration table TBLb, the name code is extracted from the received data configuration table TBLb storing the table name that matches the extraction parameter. The extracted name code is used as extraction key information when extracting a table in the connection data generation process, and is stored in an extraction key information file.

Incidentally, the purpose-specific databases S1 to S7
Is constructed for each purpose so as to be able to cope with various tasks, and there is a close relationship between the type of event and the data update for each purpose-specific database S1 to S7. Therefore, as described above, extracting the extraction key information related to a specific event by referring to the data type code of the status management table TBLc enables efficient generation of the extraction key information. On the other hand, data stored in a specific table may be updated regardless of an event. Therefore, by appropriately combining the extraction by the data type code and the extraction by the table name, it is possible to efficiently generate the extraction key information corresponding to the request.

2-4-2: Connection Data Generation Processing Next, connection data generation processing using the extracted key information file will be specifically described. In this example, the name code aaa of employee A and the name code bbb of employee B are stored in the extraction key information file, and a primary extraction file to be transferred to the company home system S4 is generated. Further, it is assumed that the company housing system S4 requires employee data, family data, and affiliation data.

In this case, the connection data generation unit M2
A function module (hereinafter, referred to as a first function module F1) for combining the extracted parameter and the related current value table described above, and a function module for combining a plurality of occurrences of the same table (hereinafter, referred to as a second function module F2) The connection data is generated using a function module (hereinafter, referred to as a third function module F3) that combines the key search results with the external key.

In this processing, processing is performed in the order of employee A and employee B. First, when the name of an employee table for storing employee data and the name of a family table for storing family data are given to the first function module F1 as extraction parameters, an employee table and a family that match the extraction code with the name code aaa are given. Tables are extracted and joined.
If the family of employee A is his wife, eldest son, and eldest daughter, for example, FIG.
As shown in (a), employee table TBLsa of employee A and his wife,
The family tables TBLka1 to TBLka3 of the eldest son and the eldest daughter are extracted and combined. In this case, family tables TBLka1 to TBLk
a3 belongs to the same table in the sense of the family table of the employee code aaa. Therefore, FIG.
When the extracted combination result of (a) is input to the second function module F2, the combination result shown in FIG. 7B is obtained.

Next, the third function module F3 executes a combining process using an external key. The external key in this case is the affiliation code 101. Therefore, the third functional module F3 searches the affiliation table TBLx (see FIG. 7C) that defines the correspondence between the affiliation code and the affiliation name, and acquires the affiliation name corresponding to “101”. This is embedded in place of the belonging code 101. As a result, FIG.
The connection table shown in (d) is obtained. The join table thus obtained is treated as one record, and employee B
And the same process is performed to obtain a record. And
By storing each record in one file,
A primary extraction file is created. In this case, a file name that can distinguish the destination-specific databases S1 to S7 of the transfer destination is given to the primary extraction file.

2-4-3: Mask Processing and Post-Processing Next, the mask processing performed by the mask section 230 will be described. In each extraction application 211-217,
As described above, a primary extraction file is created by extracting and connecting the tables stored in the original database 10, and the primary extraction file includes:
In some cases, items that should not be transferred are included in the purpose-specific databases S1 to S7 of the transfer destination. For example, in the company house system S4, no educational background information is necessary, and such information should not be transferred to the company house system S4 for security. Therefore, upon receiving the primary extraction file from each of the extraction applications 211 to 217, the mask unit 230 detects the transfer destination from the file name. Then, by using the mask parameter corresponding to the detection result, among the items of the primary extraction file, items that are not appropriate to be transferred are masked to create a masked extraction file. Thereafter, the post-processing unit 240 converts the character code of the masked extraction file into a standard character code used for communication, and adds a header / trailer to this to create a standard distribution file.

The standard distribution file created in this way is L
When the data is transferred to the purpose-specific databases S1 to S7 via the AN, the data is converted into an existing record format in a form used there by a conversion application provided in the purpose-specific databases S1 to S7, and then updated. Is stored. In this case, since the data structure of the original database 10 (how to hold the table) is configured in consideration of the data structure of the purpose-specific databases S1 to S7 as described above, the conversion application uses a method such as sorting items. Only simple processing is required. For this reason,
The conversion application needs only a very small conversion application, and has the advantage that the number of development steps and the storage area are small.

3. Conclusion As described above, according to the present embodiment, the extraction applications 211 to 217 are divided into the target data specifying unit M1 and the connection data generating unit M2, and the processing performed by each unit is converted into a functional module. Since the combination and the extraction parameter are given, the extraction application 2 for each purpose-specific database S1 to S7
Functional modules 11 to 217 can be shared. As a result, the amount of programs can be reduced as compared with the case where the programs are individually created, and the specifications can be changed in each purpose-specific database S1 to S7, and even when a new purpose-specific database is added, it can be completed in a short time. An environment in which a new extraction application can be developed can be provided.

Further, according to the above-described embodiment, in each of the purpose-specific databases S1 to S7, the event (business)
When a plurality of related data are updated with the occurrence of the event, an event management table TBLa including a data type code indicating the type of the event is generated, and this is transferred to the shared database DB. When extracting data related to an event, an extraction key information file is generated by referring to a data type code stored in the received data configuration table TBLb. When an event such as recruitment or transfer occurs, an update process occurs in a plurality of purpose-specific databases corresponding to a certain event. As described above, key information is extracted by a data type code, and a related table is efficiently extracted. It becomes possible.

Further, according to the above-described embodiment, when data is updated in each of the purpose-specific databases S1 to S7, the event management table TBLa including the table name in which the data is to be stored is generated, and this is stored in the shared database. Transferred to DB. Then, when extracting data relating to specific data, the reception data configuration table TB
An extraction key information file is generated by referring to the table name stored in Lb. Therefore, when extracting updated data for a certain table, the extraction process can be performed efficiently.

According to the above-described embodiment, the status of the business is managed using the status management table TBLc, so that the current data is reflected at an appropriate timing while grasping the status of the update data. It is possible,
Further, the extraction process can be performed at a timing required by the purpose-specific databases S1 to S7. In this case, the status of the business can be represented by a 2-bit status code, and if the status management table TBLc is searched using the status code, the status of the event table related to the business can be grasped centrally. , And efficient search becomes possible. In particular, since it is possible to indicate the issuance date before the appointment date when the business concerned is officially confirmed or the state of the undecided future before the issuance date, it is necessary to use a system that requires a large amount of calculation and needs to pass update data before the appointment date. However, it is possible to transfer necessary files by performing extraction processing at appropriate timing.

Also, since the items that should not be disclosed are masked by the masking unit 230, only the items required in the purpose-specific databases S1 to S7 can be included in the transfer file, and high security is provided. It can be easily secured.

4. 2. Modifications Although the embodiment according to the invention has been described above, the invention is not limited to the embodiment described above, and various modifications described below are possible. In the embodiment described above, the status management table
Although TBLc manages the state of work under a plurality of time conditions such as the date of issue and the date of appointment, the present invention is not limited to this.For example, the state of work is managed under time conditions such as an order receipt date and a delivery date. You may make it. That is, when the state of the data changes depending on the time-related condition, the state can be managed by a code representing the state.

The data such as the date of issue and the date of appointment transferred from the purpose-specific databases S1 to S7 are used when executing the reflection processing on the original database 10 or the extraction processing from the original database 10 based on the data. Therefore, it can be grasped as condition data indicating conditions for handling update data. Therefore, the shared database DB determines whether or not the condition is satisfied based on the condition data indicating the condition to be handled.
And reflect the result of the determination as a status code in the status management table TBLc.
By referring to the TBLc, it can be said that the reflection process and the extraction process are performed.

The reflection processing and the extraction processing using the condition data indicating the handling conditions may be applied not only to the shared database DB but also to an ordinary database device. In this database device, update data including condition data indicating an update condition is stored in a partial storage area (storage unit) of the storage unit corresponding to the original database 10, and the update data read from the storage unit is stored in the storage unit. Based on the relevant condition data, the database management mechanism 20 determines whether or not the condition is satisfied. If the determination result satisfies the condition, the updated data is reflected in the storage contents of another storage area of the storage unit. do it.

Further, update data including a plurality of condition data indicating handling conditions typified by reflection processing and extraction processing are stored in a partial storage area (storage means) of the storage means, and read out from the storage means. The database management mechanism 20 determines whether the condition is satisfied based on the condition data relating to the update data, generates state data indicating the state of the update data based on the determination result, and associates the state data with the update data. A status management table is generated (corresponding to the intermediate file generation unit 130). When status data is changed, the content of the change is reflected in the management table, and the content of the management table is monitored to update the status data with the update data. Is reflected, the update data is reflected in the storage contents of the storage means (to the state pipe transition management unit 140, ) It may be.

In the above-described embodiment, each of the extraction applications 211 to 217 is divided into the target data specifying unit M1 and the connection data generating unit M2. However, it is needless to say that these may be handled integrally. In addition, the target data specifying unit M1 and the connection data generating unit M2 combine a plurality of functional modules and perform extraction processing by giving extraction parameters to the functional modules.
Function modules are programmed in the SQL language, and dynamic SQL
The extraction parameter may be described in an L sentence so that the extraction processing can be executed.

In the above-described embodiment, the database management mechanism 20 is realized by software used in a computer system. However, it is needless to say that the present invention can be understood as a storage medium storing these programs. In this case, examples of the recording medium include a magnetic recording medium such as a floppy disk, an MO disk, and a hard disk, an optical recording medium such as a CD-ROM and a DVD-ROM, and a semiconductor recording medium such as a RAM and a ROM. In short, any recording medium capable of recording and reproducing a program may be used.

[0089]

As described above, according to the invention-specifying matter of the present invention, the update data is made to include the condition data defining the handling conditions, and the reflection process and the extraction process are executed based on the condition data. As a result, you can enter updated data before the actual reflection process is executed,
It is possible to allow time for inputting update data.
In a database device or a shared database device, as long as update data is input, the state of the update data is autonomously managed based on the condition data contained therein, and the reflection extraction process is automatically performed. Can be done.

[Brief description of the drawings]

FIG. 1 is a block diagram showing an overall configuration of a shared database system according to an embodiment of the present invention.

FIG. 2 is a functional block diagram illustrating a functional configuration of a shared database according to the embodiment;

FIG. 3 is a diagram showing an example of a table generated by the personnel system according to the embodiment;

FIG. 4A shows an example of a received data configuration table according to the embodiment, and FIG. 4B shows an example of a status management table according to the embodiment.

FIG. 5 is a diagram showing state management using the status management table according to the embodiment;

FIG. 6 is a diagram showing a current data reflection processing operation according to the embodiment;

FIG. 7 is a diagram showing an example of a connection data generation operation according to the embodiment.

[Explanation of symbols]

S1 to S7: Purpose-specific database (individual database device) DB: Shared database (shared database device, database device) 10: Original database (storage means, storage means) 100: Reflection processing mechanism (determination means, reflection means, state data generation) Means, management table generation means, state management means) 200 extraction processing mechanism (extraction means, transfer means) 211 to 217 extraction application 230 mask part 240 post-processing part (transfer means) M1 target data identification part (extraction Means) M2: Connection data generation unit (extraction means) LAN: Local area network (communication network)

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Takeshi Kido 1-9-1, Konan, Minato-ku, Tokyo NTT Communications Wear Co., Ltd. (72) Inventor Keisuke Yamamoto Kon-ichi, Minato-ku, Tokyo (No. 9-1, NTT Communicationware Co., Ltd.) (72) Inventor Ryuyuki Samukawa, 9-1-1 Konan, Minato-ku, Tokyo, Japan (NTT Communicationware Co., Ltd.)

Claims (8)

[Claims] 1. A database device comprising storage means for storing a plurality of data in association with each other and receiving update data including condition data indicating an update condition, wherein the storage means stores the input update data. And determining means for determining whether or not a condition is satisfied based on condition data relating to the update data read from the storage means. If the determination result of the determining means satisfies the condition, the update data is A database device comprising: a reflection unit that reflects the content stored in the storage unit. 2. The method according to claim 1, wherein the condition data indicates an update time, and the determination unit determines whether the condition is satisfied by comparing a current time with a time indicated by the condition data. The database device according to claim 1, wherein 3. A database device comprising storage means for storing a plurality of data in association with each other and receiving update data including a plurality of condition data indicating handling conditions, wherein the input update data is stored. A storage unit, a determination unit that determines whether each condition is satisfied based on a plurality of condition data related to the update data read from the storage unit, and the update data based on a determination result of the determination unit. Status data generating means for generating status data indicating the status of the status data; management table generating means for generating a management table for associating the status data with the update data; and when the status data is changed, the contents of the change are stored in the management table. At the same time, the contents of the management table are monitored to indicate that the status data reflects the update data. Case, the database device characterized in that it comprises a state-management part to reflect the updated data in the storage contents of the storage means. 4. A shared database device, wherein update data including a plurality of condition data indicating handling conditions is supplied from a plurality of individual database devices that handle mutually related data, and stores a plurality of data in association with each other. Storage means for storing update data supplied from each of the individual database devices; and determining whether each condition is satisfied based on a plurality of condition data relating to the update data read from the storage means. Determining means for determining; state data generating means for generating state data indicating a state of the update data based on a determination result of the determination means; and a management table for generating a management table for associating the state data with the update data Generating means, when the status data is changed, reflects the change in the management table. In particular, when the content of the management table is monitored and the status data indicates that the update data is reflected, the status management unit that reflects the update data in the storage content of the storage unit, and the individual database Extraction means for extracting necessary data from the storage means and the storage means to generate extracted data by referring to the status data stored in the management table in accordance with rules determined for each device. And a transfer unit for transferring the extracted data to each of the corresponding individual database devices. 5. The shared database device is for performing business management, wherein the plurality of condition data indicate a business issue date and an appointment date, and the determination means includes a current date and an issue date indicated by the condition data. And the appointment date to determine each condition, wherein the status data generating means includes status data indicating an undetermined future if the current date is before the issuance date, and the current date is the issuance date. Thereafter, when the date is before the appointment date, status data indicating a confirmed future is generated, and when the current date is after the appointment date, status data indicating the present is generated, and the status management means includes: And when the status data reaches the current date, reflects the update data in the storage content of the storage means. The extraction means is determined for each individual database device. By referring to the status data stored in the management table in accordance with the rules, required data is extracted from the storage unit even before the appointment date, and the extracted data is generated. The shared database device according to claim 4. 6. The individual database comprising: the shared database device according to claim 4 or 5; a plurality of individual database devices; and a communication network connecting the shared database device and the plurality of individual database devices. When update data updated in the device is transferred to the shared database device via the communication network, the shared database device reflects the update data in the storage content of the storage unit, and the storage unit or the storage unit A shared database system for transferring the extracted data extracted from the database to another individual database device via the communication network. 7. A shared system comprising storage means for storing a plurality of data in association with each other, wherein update data including a plurality of condition data indicating handling conditions is supplied from a plurality of individual database devices handling mutually related data. A method of extracting data from a database device, the method comprising: storing update data supplied from each of the individual database devices in a storage unit; and storing a plurality of condition data related to the update data read from the storage unit. A step of determining whether or not a condition is satisfied; a step of generating state data indicating a state of the update data based on the determination result; a step of generating a management table that associates the state data with the update data When the status data is changed, the change is reflected in the management table. Monitoring the contents of the management table, if the status data indicates that the update data is reflected, reflecting the update data in the storage content of the storage unit; Extracting the required data from the storage means and the storage means to generate the extracted data by referring to the state data stored in the management table in accordance with the specified rule; and Transferring the data to each of the corresponding individual database devices. 8. A recording medium for recording a data extraction program for a shared database device for causing a computer device to execute the data extraction method for a shared database device according to claim 7.