JP2002099535A - Database information alteration method between organizations - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a database information alteration method between organizations that makes use of an existing system and permits information alteration and data alteration for every individual organization with high performance and reliability. SOLUTION: A system to be a transmission side has a DB update monitoring means and an update data transmitting means. A system to be a reception side has an update data reception means, an update data type determining means for determining whether reception data are intended for master system or transaction system, a means for updating record contents of the master system of a reception side DB if the reception data are intended for the master system, and a means that produces a group of transaction records related to the transaction system data and adds the group to the reception DB if the reception data are intended for the transaction system.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for changing database information between organizations, and more particularly, to a method for improving the performance of an existing system including a database when a plurality of organizations use the existing system as it is. The present invention relates to a database information change method between organizations which can change database information with high reliability and can change data for each individual organization.

[0002]

2. Description of the Related Art For example, consider a case where a notebook computer is shipped from a factory as a finished product. In this case, the factory (assembly company) that ships the finished notebook computer will
In many cases, a large number of various components such as a CPU and a RAM are purchased from a plurality of component manufacturers, and various components are assembled and subjected to a predetermined inspection by an assembling company before being shipped as a finished product.

In such a case, the assembling company and a plurality of component manufacturers operate the individual company information processing system KJ300 shown in FIG. 7 without the inter-company network in order to procure and supply parts. Assume. In the system KJ300, information exchange between each company is human-based (slip,
(Telephone, FAX, etc.) and manually updates the transaction information database unique to each company. This system KJ300
The advantages of this are that the contents of the database can be changed at the convenience of each company, that a company secret that you do not want to be known to other companies can be stored in the database, and that even if another company's machine fails, its system is not affected. is there. However, the disadvantages are a lot of clerical work and a long transaction time.

Therefore, in order to improve these disadvantages, it is conceivable to construct an inter-company information exchange system KJ400 in which a transaction information database is shared by interposing a network shown in FIG. The transaction information database shown in FIG.
An area for storing data of an assembly company and an area for storing data of a component maker are secured. In this centralized database format, data belonging to a company secret is stored separately in a separate database in accordance with a common database schema. However, this centralized database format has the following disadvantages.

That is, the existing system (FIG. 7) has to be recreated, the transaction information database becomes a bottleneck when the processing is concentrated, the turnaround time is required for performing the processing via the network, Cannot be changed by
This is a disadvantage in that trade secrets cannot be stored in the transaction information database, and if a machine in which the transaction information database is placed fails, business operations of all companies cannot be performed.

As a solution to some of these drawbacks, a distributed database type inter-company information exchange system KJ500 shown in FIG. 9 can be considered. This distributed database format is the same as the centralized database format in that data belonging to a company secret is stored in a separate database according to a common database schema. In the distributed database format, a transaction information cache and a network constitute a distributed database, and logically constitute one database. This inter-enterprise information exchange system KJ400 solves the above disadvantages.

[0007]

However, this distributed database format has the following problems. The first problem is that the existing system (FIG. 7) must be recreated (same as the above-mentioned disadvantage). The second problem is that if the write processing is concentrated, the transaction information database becomes a bottleneck, and the performance such as the processing speed cannot be improved beyond a certain limit (the same as the above-mentioned drawback).

[0008] The third problem is that it is difficult to improve the consistency (reliability) of all the distributed transaction information caches (new disadvantage). The fourth problem is that the contents of the transaction information database cannot be changed for the convenience of one company (the same as the above-mentioned disadvantage). The fifth problem is that confidential information for a company cannot be stored in a transaction information database (the same as the above-mentioned disadvantage).

Therefore, an object of the present invention is to solve the problem that a plurality of organizations have established an existing system including a database.
An object of the present invention is to provide a database information change method between organizations which can change database information with high performance and high reliability while utilizing the existing system as it is and which can change data for each individual organization.

[0010]

SUMMARY OF THE INVENTION In order to solve the above-mentioned problems, the present invention provides a computer system in which each organization independently builds a computer system provided with a database and connects the independent systems to each other. In the database information change method between organizations when constructing a new system, a database update monitoring means for monitoring data update of a sender database and the updated data are sent to the independent system serving as a sender. Update data transmitting means, the independent system serving as a receiving side includes update data receiving means for receiving the update data, and update data type determining means for determining whether the received data is a master system or a transaction system. And a means for updating the recorded contents of the master system in the receiving database when the received data is the master system. When the received data is in the case of a transaction system, create a set of transaction records associated with the transaction system data, characterized by comprising a means for adding the reception-side database.

In this way, if the received data is of the master type, the corresponding part of the master type recorded contents of the receiving side database is updated as it is (for example, "update data distribution message" in FIG. 5), and the transaction type is updated. In the case of (1), a new set of transaction records (for example, a related set indicated by reference symbol X in FIG. 6) related to the received message (for example, the “update data distribution message” in FIG. 6) is newly created, and to add. Therefore, database information can be changed with high performance and high reliability simply by adding a transaction record creation means to a part of the existing system, and database information can be changed between organizations where data can be changed for each individual organization. A scheme can be built.

[0012]

DESCRIPTION OF THE PREFERRED EMBODIMENTS (1) Outline of the present invention In the present invention, when information distributed from a certain company is updated in inter-company information exchange (inter-organization information exchange), existing information in each company is updated. An object of the present invention is to provide a configuration capable of minimizing the influence on the system and particularly eliminating the influence on the existing in-house system. In FIG. 1, company A to company B
When the information is sent to the system B-SYS or the system B1-SYS, the information is not sent explicitly from the system A-SYS to the system B-SYS. Detect and update the DB of company B via the interface. In FIG. 1, illustration of terminals and networks is omitted.

In the data receiving company (Company B), if the updated data is a master system (for example, see "Update Data Distribution Message" in FIG. 5), the processing on the system side does not need to be changed at all. Here, the master system refers to data that has only one record at a specific point in time, such as a product code and a unit price, is referred to from other records, and serves as a reference for processing. Generally, data is added. And few changes. If the updated data is transactional, the interface does not update the record in the DB, but adds an appropriate set of records (for example, refer to “Related set” indicated by X in FIG. 6) to update the data. Make corrections. Here, the transaction type refers to data for business process recording in which a plurality of records may exist at a specific point in time, such as ordering information and transaction information. Generally, data is frequently added or changed. . In this way,
Data change in the exchange of information between companies is enabled without modifying the existing system indicated by the dashed line. Also,
When changing data, the number of messages to be sent can be reduced.

(2) Embodiment Hereinafter, the present invention will be described based on the illustrated embodiment. (2-1) System Configuration FIG. 2 is a system configuration diagram of the present embodiment. Referring to FIG. 2, the inter-company information exchange system KJ of the present embodiment
And a second company system BB. In FIG. 2, the illustration of the terminal and the network is omitted.

The system AA of the first company includes an existing system 10 having a database device and the like and an additional interface 20. The existing system 10 includes a business system 11, a DB device 12, a DB updating unit 13, and a DB reading unit 14. The additional interface 20 includes a DB update monitoring unit 21 and an update information transmission unit 22.

These systems and means operate in the following manner. The DB updating means 13 updates the contents of the DB device 12 in response to an instruction from the business system 11. The DB reading unit 14 updates the data in the DB device 12 when the data to be exchanged in the inter-company information exchange is updated.
In response to an instruction from the DB update monitoring unit 21 described below, the update data is read and passed to the update information transmission unit 22. The DB update monitoring unit 21 instructs the DB reading unit 14 to read the updated data when the target data among the data in the DB device 12 is updated in the inter-company information exchange. The update information transmitting unit 22 converts the update information obtained from the DB reading unit 14 into a message format to be passed to another company (second company). Further, information indicating whether the update information is a master system or a transaction system is added according to the nature of the data in the DB device 12, and the update information is transmitted to another company (second company).

The system BB of the second company includes an existing system 50 having a database device and the like and an additional interface 60. The existing system 50 includes a business system 51, a DB device 52, a DB updating unit 53, a DB reading unit 54, and a DB adding unit 55. The additional interface 60 includes an update information receiving unit 61, an update type determining unit 62, and a transaction record creating unit 63.

Update information receiving means 61 in the second company 20
Receives the message related to the update information obtained from the update information transmitting unit 22 of the first company, and passes the update information to the update type determination unit 62. The update type determination means 62 determines whether the update information is a master type or a transaction type based on the additional information. In the case of the transaction system, the update information is passed to the transaction record creation means 63. In the case of the master system, the update information is passed to the DB updating means 53.

Transaction record creation means 63
Receives the update information from the update type determination unit 62, converts the update information into DB record information to be added (for example, see the update data distribution message in FIG. 6), and
The DB record is passed to the adding means 55. DB adding means 55
Adds the DB record information received from the transaction record creation unit 63 to the DB device 52.

The DB updating means 53 includes an update type determining means 6
The master information in the DB device 52 is updated on the basis of the DB record update information received from the second device. The DB reading means 54
Upon receiving a DB read instruction from the business system 51 in the second company 20, the record is read from the DB device 52 and returned.

(2-2) Outline of Operation Next, the entire operation of the present embodiment will be described in detail with reference to the flowcharts of FIGS. 2 and 3A and 3B. FIG. 3A is a flowchart on the update information transmitting side, and FIG. 3B is a flowchart on the update information receiving side. First, the system AA of the first company is connected to another company (second company) in the DB device 12 through the DB updating means 13.
The data for which the update information is to be distributed is updated. (Step 1) Next, the DB update monitoring means 21 acquires data update (control). (Step 2) The DB update monitoring unit 21 causes the DB reading unit 14 to acquire the content of the updated information from the DB device 12. (Step 3) The acquired information is delivered by the update information transmitting means 22 to a company (second company) that should receive the update information.
(Step 4)

The update information receiving means 61 in the second company to which the update information has been sent passes the received update information to the update type determination means 62. (Step 5) The update type determination means 62 determines whether the update information is the update of the transaction record or the master update.
The updating means 53 is called. (Step 6)

In the case of creating a transaction record, the transaction record creating means 63 creates a new transaction record according to the update information (see “Related set” in FIG. 6). (Step 7) The created transaction record is written into the DB device 52 by the DB adding means 55. (Step 8) In the case of the master update, the DB update means 53 updates the information of the master record that matches the update information (see “Update data distribution message” in FIG. 5) and writes it to the DB device 52. (Step 9) By the above procedure, the existing system 50 in the second company is
Transmits the updated information from the DB device 52 to the DB reading unit 5.
4 can be read correctly.

(2-3) Description of Operation of Specific Example Next, a description will be given using a specific example. FIG. 4 is a system configuration diagram of this example. In FIG. 4, the illustration of the terminal and the network is omitted. As shown in FIG. 4, it is assumed that a component manufacturer and an assembly company exchange information between the companies.
Parts information is sent from the parts manufacturer to the assembly company,
The ordering information is sent from the assembly company to the parts manufacturer. At this time, the component information is a master system for referring to the same record in every case, and the order information is a transaction system for information generated at a specific time.

The part maker is an inter-company information exchange system 1
The inter-enterprise information exchange system 100 includes an existing system 110 (corresponding to an existing system of a component manufacturer and an assembly company in FIG. 7) and an additional interface 120. The existing system 110 includes the manufacturing management system 11
1, a DB device 112, a DB reading unit 113, a DB updating unit 114, and a DB adding unit 115. The additional interface 120 includes a DB update monitoring unit 121, an update information transmission unit 122, an update information reception unit 123, an update type determination unit 124, and a transaction record creation unit 12.
5 is provided.

The assembling company is an inter-company information exchange system 200.
The inter-enterprise information exchange system 200 includes an existing system 210 and an additional interface 220. The existing system 210 includes an ordering system 211 and a DB device 2
12, DB reading means 213, DB updating means 214, DB
And an additional unit 215. Additional interface 220
Are DB update monitoring means 221, update information transmission means 22
2, update information receiving means 223, update type determining means 224
Is provided. Note that an assembly company does not have a transaction record creation means because it is unnecessary for a business to add a transaction record by receiving update information from another company (parts manufacturer) unlike a parts manufacturer.

First, the updating of the master system will be described. As shown in FIG. 5, the component manufacturer has a DB (DB device 112) having columns including a component code, a component name, a unit price, an order unit, a minimum order quantity, a raw material code, a production line, a yield, and a cost. Among these, the part code, the part name, the unit price, the order unit, and the minimum order number are information for exchanging information between companies with other companies (assembly companies) that may trade. The parts manufacturer sets the unit price of the part with the part code 000001 to 123,
Decreased from 456 to 123,000. This is because the production management system 111 of the component manufacturer has
14 is instructed to update the corresponding record.

When such a change in data related to the exchange of information between companies occurs in the DB device 112, the DB update monitoring means 121 is notified of the change. The DB update monitoring means retrieves the update content from the DB device 112 by the DB reading means 113 and sends the changed information to another company (assembly company) through the update information transmitting means 122. If the information immediately before the update is held in the component manufacturer, the information before and after the update can be sent to another company as a set. An example of a set of update information is shown in "Update message distribution message" in FIG.
Shown in

On the assembly company side, the update information receiving means 223
Receives update information from another company (parts manufacturer). The received update information is determined by the update type determination unit 224 as to whether DB update is necessary. The unit price revision message from the parts manufacturer shown as an example
Since the data needs to be updated, the corresponding record of the DB device 212 is updated through the DB updating unit 214. As a result, the assembly company ordering system 211 can use the information obtained by the inter-firm information exchange without changing the system (see FIG. 7) at the time when the inter-firm information exchange was not performed.

It should be noted that the DB device 21
2 does not have a function of managing the history, if all information is updated in a batch using the information updated by the ordering system 211, the contents to be calculated based on the information before the update will be incorrect. Calculated based on the updated information. In order to cope with such a situation, a system that updates information in a batch manner on the ordering system 211 side performs not only the master update described here but also a transaction update described later. In any case, the ordering system 21
You don't need to change 1 A means for maintaining consistency for optimizing processing may be added to the ordering system once connected to the inter-enterprise information exchange system thus configured. In this case, it is no longer necessary to update the master in the DB device or add a transaction.

Next, updating of the transaction system will be described. As shown in FIG. 6, the assembly company has a DB having columns including a slip number, scheduled delivery date and time, a part code, a quantity, a subtotal, and remarks. Of these, the slip number, scheduled delivery date and time,
The part code, the quantity, and the subtotal are information for exchanging information between companies with another company (a participant company such as a part maker) that has a possibility of dealing. The assembly company has decided to change the order quantity of the part code 000001 in the slip number 200008010001 from 1100 to 2000. This is the ordering system 2 of the assembly company
11 by instructing the DB updating means 214 to update the corresponding record. At this time, the amount subtotal is also updated after the calculation.

When such a change in data related to the exchange of information between companies occurs in the DB device 212, the change is notified to the DB update monitoring means 221. The DB update monitoring means extracts update contents from the DB device 212 by the DB reading means 213 and sends the changed information to another company (parts manufacturer) through the update information transmitting means 222. If the information immediately before the update is held in the assembling company, the information before and after the update can be sent to another company as a set. One example of a set of update information is shown in “Update data distribution message and“ Related set ”in FIG.

On the part maker side, the update information receiving means 1
23 receives update information from another company (assembly company). The received update information is determined by the update type determination means 124 as to whether DB update is necessary. The quantity change message from the assembly company shown as an example is data that requires a transaction record to be added on the part manufacturer side.
That is, the quantity change information is passed from the update type determination unit 124 to the transaction record creation unit 125.

Transaction record creation means 125
Then, the DB reading unit 113 searches which of the existing transaction records has been changed, and obtains the corresponding order details. By comparing with the order details before the update, it is found that there is a difference between the quantity and the subtotal. Therefore, the transaction record creation unit 125 creates one record indicating that a difference amount has been ordered, and passes the record to the DB addition
Add a record to. As a result, the manufacturing management system 111 of the component manufacturer can use the information obtained by the inter-firm information exchange without changing the system (see FIG. 7) at the time when the inter-firm information exchange was not performed.

It should be noted that if the manufacturing management system 111 is not provided with a function for canceling a negative quantity, the quantity may be reduced by information exchange between companies from another company (assembly company). The point that cannot be raised is raised.
In order to cope with such a situation, it is necessary to regard the transaction record once determined to be the same as that of the master, rewrite the record, and add or update another record which affects the transaction execution. If such measures are taken, the manufacturing management system 11
You don't need to change 1 A means for maintaining consistency after information exchange between companies can be added to the production management system once connected to the information exchange system between companies for optimization of processing. In this case, it is no longer necessary to update the master in the DB device or add a transaction.

[0036]

As described above, according to the present invention, the following effects can be obtained. The first effect is that information can be exchanged between companies without changing the existing system (see FIG. 7). The reason is that, as means for updating the DB of the existing system from the outside, a DB updating means for updating the master, a transaction record creating means for updating the transaction, and a DB adding means are added. It should be noted that DB updating means and DB
As the additional means, an existing system may be used. Second
The effect of this is that information can be exchanged with a plurality of companies by one interface, and even if a new company joins later, the system of another company is not affected. The reason is that by distributing the update information of the DB, it is possible for a plurality of companies to appear as if they have one virtual DB, and the configuration does not change even if a new company participates later. is there.

The third effect is that a performance problem caused by the inter-company cooperation mechanism does not occur in principle. The reason is,
This is because there is no need to centrally manage information across multiple companies. The fourth effect is that the reliability of the system is good. The reason is that information exchange between a plurality of companies uses a simple message exchange, and there is no part that permanently retains logic and information.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating an outline of the present invention.

FIG. 2 is a system configuration diagram of an embodiment of the present invention.

FIG. 3 is a flowchart of the embodiment, in which (A) is a flowchart on the transmission side and (B) is a flowchart on the reception side.

FIG. 4 is a system configuration diagram of a specific example of the embodiment.

FIG. 5 is a diagram illustrating data exchange of a database in the specific example.

FIG. 6 is a diagram illustrating another data exchange of a database in the specific example.

FIG. 7 is a diagram showing an existing processing system of a conventional example.

8 is an example of an inter-company information exchange system in which the processing system of FIG. 7 is improved.

9 is an example in which the inter-company information exchange system of FIG. 8 is improved.

[Explanation of symbols]

 10, 50 Existing system 20, 60 Additional interface 21 DB update monitoring means 22 Update information transmission means 61 Update information reception means 62 Update type reception means 63 Transaction record creation means

Claims (2)

[Claims] 1. A system for changing database information between organizations when each organization independently builds a computer system having a database and connects the independent systems to each other to build a new system. Wherein the independent system serving as a transmitting side includes: a database update monitoring means for monitoring data update of a transmitting side database; and an update data transmitting means for transmitting data after the update, and the independent system serving as a receiving side. The system comprises: an update data receiving unit for receiving the update data; and an update data type determining unit for determining whether the received data is a master system or a transaction system. Means for updating the record contents of the master system, and when the received data is a transaction system, Means for creating a set of transaction records related to the transaction data and adding it to the receiving database. 2. The method according to claim 1, wherein the independent system is an existing computer system provided in each organization.