JP2005078503A - Client/server system with master data reflecting means, master data reflection method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To obtain coincidence between a master file in a server computer and the copy file content of the master file in a client computer when necessary while keeping the communication volume between a client and a server small. <P>SOLUTION: The server computer is provided with a server master storage part and a transaction data storage part, and the client computer is provided with a client master storage part having information obtained by copying information in the server master storage part. The server computer compares the content of the server master storage part and the content of the client master storage part when receiving transaction data from the client computer and registers the transaction data in the transaction data storage part in the case coincidence is found and extracts and transmits the difference between the content of the server master storage part and the content of the client master storage part to the client computer in the case no coincidence is found. The client computer updates the client master storage part on the basis of the received difference. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

According to the present invention, a server computer is provided with a master file, and all client computers are provided with a copy file as a copy thereof. After the master file on the server computer is updated, the copy file on the client computer is transferred to the master on the server computer. The present invention relates to a client / server system having a function for matching a file, a master data reflection method and a master data reflection program in the client / server system.

In a client / server system having a function of matching copy files on all client computers with the master file of the server computer, when the master file is updated, it is necessary to perform the same update on the copy file. . Conventionally, in such a case, a method of regularly checking whether there is an update based on the master file update history information acquired in the server computer, and updating the copy file if it has been updated (for example, Patent Document 1). ) Was taken. Specifically, it is performed as part of a process called a daily process, which is executed regularly every day. In the method as disclosed in Patent Document 1, the contents of the files do not match between the client / server computers for a certain period after the master file is updated until the periodic update processing is performed. There was a point. Therefore, this method cannot be adopted in a system in which it is essential that both files match at a certain point in a certain process. To avoid this problem, when a copy file needs to be referenced on the client computer, check whether the master file has been updated immediately before the reference, and if there is an update, update the copy file ( For example, Patent Document 2) has been taken.

Japanese Patent Laid-Open No. 3-110463 (page 4-5, FIG. 3)

Japanese Patent Laid-Open No. 6-290098 (page 5, FIG. 7)

However, while the method of Patent Document 2 guarantees that the reference data matches between the client / server computer, the client computer always inquires the server computer about the update status every time the copy file is updated, so the client computer is constantly inquired about the update status. There has been a problem that communication between server computers frequently occurs and the processing efficiency of the system is lowered.
On the other hand, in business systems that create and register certain types of data based on the contents of the file, i) refer to the copy file many times during the data creation process on the client computer. It is sufficient that the match is guaranteed when the data is completed and registered in the server computer. Ii) The file update frequency is low, and the probability that a mismatch between the two files is detected at the time of data registration is low. May have two characteristics. For example, it is a case of a system in which sales data is created by a client computer based on the contents of a product master file and registered in a server computer. In the case of such a system, in the data creation process, it is assumed that the file contents are the same, and the process is performed while referring to the copy file several times. If the matching check is performed, the traffic for checking the matching of both files can be greatly reduced.
The present invention adopts such a concept, and in the system having the characteristics i) and ii), the contents of the master file of the server computer and the copy file of the client computer are maintained while keeping the communication amount between the client / server computer low. The client / server system, the master data reflecting method, and the master data reflecting program in the client / server system that guarantee the matching are provided at the time when matching is required.

A first client / server system according to the present invention is a client / server system including at least one client computer and one server computer, and the server computer stores a server master storage unit and transaction data. Each of the at least one client computer includes a client master storage unit having information obtained by copying information in the server master storage unit, and transaction data input by a user. A client-side transaction data registration unit that transmits to the server computer, and when the server computer receives the transaction data from the client computer, the server master storage unit and the client master storage unit match confirmation The line The server-side transaction data registration unit that registers the transaction data in the transaction data storage unit when they match, and the server master storage unit and the client master when the match confirmation confirms that they do not match A server-side client master update unit that performs difference extraction of contents with the storage unit and transmits the extracted client master update difference to the client computer, wherein the client computer receives the client received from the server computer A client side client master update unit is provided for updating the client master storage unit based on the master update difference.
According to a second client / server system of the present invention, in the first client / server system, at least one of the at least one client computer is updated information on the server master storage unit input by a user. A server-side server master update unit that receives the update information and updates the server master storage unit based on the update information It has.
According to a third client / server system of the present invention, in the first client / server system, the server computer is configured as one update history record as an update history each time information in the server master storage unit is changed. Each of the at least one client computer includes a client master update number storage unit that stores the number of update history records that have been updated in the client master storage unit, The server side / transaction data registration unit is configured to compare the contents of the server master storage unit and the client master storage unit by comparing the number of update history records in the master update history storage unit and the value of the client master update number storage unit. The server side client is checked for a match. The star update unit extracts the update history record from the master update history storage unit based on the difference between the number of the update history records in the master update history storage unit and the value of the client master update number storage unit, thereby An update difference is extracted, and the client side server master update unit updates the client master storage unit based on the client master update difference received from the server computer, and the update history of the master update history storage unit The number of records is stored in the client master update number storage unit.
According to a fourth client / server system of the present invention, in the third client / server system, at least one of the at least one client computer has the server master storage unit input by a user. The client-side server master update unit that transmits update information to the server computer, the server computer receives the update information, updates the server master storage unit based on the update information, and updates the update The server-side server master update unit stores the update history as the update history record in the master update history storage unit.
According to a fifth client / server system of the present invention, in the third or fourth client / server system, the server master storage unit stores a master record including an identifier and data related to the identifier, The master update history storage unit stores the update history record including the identifier of the master record corresponding to the updated master record, and the transaction data includes the identifier of at least one master record, The server side client master update unit, when there is no match between the identifier included in each update history record of the difference for client master update and the identifier included in the transaction data, the transaction data It stores in a transaction data storage part.
The master data reflecting method in the first client / server system of the present invention comprises a server master storage unit, a server computer comprising a transaction data storage unit for storing transaction data, and information in the server master storage unit. In a client / server system including at least one client computer having a client master storage unit having copied information, the client computer transmits transaction data input from a user to the server computer. When the transaction data registration step and the server computer receive the transaction data from the client computer, the contents of the server master storage unit and the client master storage unit are checked for coincidence. The server-side transaction data registration step for registering the transaction data in the transaction data storage unit, and when the server computer confirms that they do not match in the match confirmation, the server master storage unit and the client A server-side client master update step of performing difference extraction of contents with the master storage unit and transmitting the extracted client master update difference to the client computer; and the client master received from the server computer by the client computer A client-side client master update step of updating the client master storage unit based on the update difference.
The master data reflecting method in the second client / server system of the present invention is the master data reflecting method in the first client / server system, wherein at least one of the at least one client computer is input by a user. A client-side server master update step for transmitting update information for the server master storage unit to the server computer; and the server computer receives the update information and stores the server master storage unit based on the update information. And a server side server master update step of updating.
The master data reflection method in the third client / server system according to the present invention is the master data reflection method in the first client / server system, in which the server computer changes the information in the server master storage unit. A master update history storage unit that stores one update history record as an update history, and each of the at least one client computer indicates the number of the update history records that have been updated in the client master storage unit. In the client / server system including a client master update number storage unit for storing, in the server side / transaction data registration step, the server computer updates the number of the update history records in the master update history storage unit and the client master update number. The server master storage unit and the client master storage unit confirm the contents by comparing the values in the number storage unit, and in the server side client master update step, the client computer is configured to store the master update history storage unit in the master update history storage unit. The client side server master is extracted by extracting the update history record from the master update history storage unit based on the difference between the number of update history records and the value of the client master update number storage unit, and the client side server master In the update step, the client computer updates the client master storage unit based on the client master update difference received from the server computer, and sets the number of update history records in the master update history storage unit And to store the compliant master maintenance count storage unit.
The master data reflection method in the fourth client / server system of the present invention is the master data reflection method in the third client / server system, in which at least one of the at least one client computer is input by a user. The client-side server master update step of transmitting the update information to the server master storage unit to the server computer, and the server computer receives the update information and based on the update information, the server master storage And the server side server master update step of storing the update history of the update in the master update history storage unit as the update history record.
The master data reflection method in the fifth client / server system of the present invention is the master data reflection method in the third or fourth client / server system, in which the server master storage unit is associated with an identifier and the identifier. A master record comprising data, and the master update history storage unit stores the update history record including the identifier of the master record corresponding to the updated master record, and the transaction data includes at least one transaction record In the client / server system including the identifier of the master record, in the server-side client master update step, the server computer includes the identifier and the transaction data included in each update history record of the client master update difference. Included in That if there is no match between the identifier is characterized by storing the transaction data in the transaction data storage unit.
A first program of the present invention includes a server master storage unit and a transaction data storage unit for storing transaction data, and includes at least one client master storage unit having information obtained by copying information in the server master storage unit. When the transaction data is received from the client computer to one server computer that can communicate with the client computer, the contents of the server master storage unit and the client master storage unit are checked for coincidence. When the server-side transaction data registration procedure for registering the transaction data in the transaction data storage unit and the match confirmation confirm that they do not match, the contents of the server master storage unit and the client master storage unit Difference extraction is performed and the extracted difference for client master update The executing a server-side client master maintenance procedures to be sent to the client computer.

As described above, according to the present invention, i) the client master storage unit is referred to many times during the data creation process in the client computer. In a system that has two characteristics, that is, it is only required to be guaranteed at the time of registration, and ii) the file update frequency is low, and the probability that a mismatch between the two files is detected at the time of data registration is low. There is an effect that it is possible to guarantee the coincidence when the contents of the master file of the server computer and the contents of the copy file of the client computer need to be matched while keeping the communication volume between the server computers low.

Referring to FIG. 1, the best mode of the present invention is a client / server system in which at least one client computer 200 and one server computer 100 are connected via a communication line.
Referring to FIG. 2, in the embodiment of the client / server system of the present invention, the server computer 100 of FIG. 1 includes each client computer such as a product code and a product name in a storage medium (not shown) such as a hard disk. Server master storage unit 101 storing information (master data) referred to by 200, master update history storage unit 102 storing update history of information in server master storage unit 101, and server for recording the number of updates in server master storage unit 101 A master update number storage unit 103 and a transaction data storage unit 104 for storing transaction data such as order information for products stored in the server master storage unit 101 are provided.
A client computer 200 in FIG. 2 represents one of the client computers 200 in FIG. 1, but in a storage device (not shown) such as a hard disk, a client master storage unit 201 that is a copy of the server master storage unit 101. A client master update number storage unit 202 that records the number of updates in the client master storage unit 201 is provided. The client computer 200 further includes an input / output device such as a display / keyboard / mouse that provides a user with a man-machine interface.
In the server master update number storage unit 103 and the client master update number storage unit 202, zero is set as an initial value.
The server computer 100 includes a server-side server master update unit 111 that updates the server master storage unit 101 based on a request from the client computer 200, and stores transaction data in the transaction data storage unit 104 according to a request from the client computer 200. When the server-side / transaction data registration unit 113 and the server-side / transaction data registration unit 113 that perform registration detect a mismatch between the server master storage unit 101 and the client master storage unit 201 by the method described later, the client master 200 stores the client master A server-side client master update unit 112 that requests an update of the storage unit 201 is provided.
The client computer 200 includes a client-side server master update unit 211 that requests the server computer 100 to update the server master storage unit 101 based on information from the input / output device input by the user, based on a request from the server computer 100 Requests the server computer 100 to register the client side client master update unit 212 for updating the client master storage unit 201 and the transaction data input from the input / output device by the user in the transaction data storage unit 104 The client side / transaction data registration unit 213 includes a client side / transaction data registration unit 213.
Details of the operation of each processing unit will be described later. Each of these processing units is realized by the CPU (not shown) of the server computer 100 or the client computer 200 to which each processor belongs reads out and executes a program stored in a storage device (not shown). The program may be read from a recording medium (not shown) or downloaded via a computer network such as the Internet (not shown).
The client side server master update unit 211 may be provided only in the specific client computer 200 of FIG. 1 and may not exist in the other client computers 200.
FIG. 3 is an example of data stored in the server master storage unit 101. This is an example of a product master file, and stores product information such as a product code, a product name, and a unit price. The information in this figure is also stored in the client master storage unit 201 which is a copy of the server master storage unit 101. The contents of both storage units are the same at the beginning, but if the server master storage unit 101 is updated by the server side server master update unit 111 in response to a notification from the client side server master update unit 211, it temporarily becomes inconsistent. It becomes. Such an update is performed to add a new product or delete a product. This discrepancy is resolved when transaction data is registered in the transaction data storage unit 104, as will be described later.
FIG. 4 is an example of data stored in the master update history storage unit 102 (hereinafter referred to as an update history record). This figure is an example corresponding to the data example of FIG. As shown in the figure, when the server master storage unit 101 is updated as products are added, deleted, price changes, etc., the serial number 401, product code, added / deleted as one record for each updated product An update category indicating different types of update and data after update (there is no data when the update category is deleted) are stored. The serial number 401 is a serial number assigned to each update history record starting from 1.
FIG. 5 is an example of transaction data stored in the transaction data storage unit 104. This figure is an example of order information corresponding to the data example of FIG. Here, order information is illustrated as transaction data. As shown in the figure, the transaction data is composed of a transaction date, a business partner identifier, all received product codes, and the number of items.
In the above configuration, first, an operation when the user updates the server master storage unit 101 from the client computer 200 will be described with reference to FIG. The client computer 200 used here is a client computer 200 including a client side server master update unit 211.
When activated by the user, the client side server master update unit 211 of the client computer 200 displays the server master storage unit update screen illustrated in FIG. 8 on the input / output device (step 601), and then the user enters. The product code, product name, unit price, update classification, etc. (hereinafter referred to as update information), which are data necessary for the update designated by the output device, are read (step 602). Thereafter, the update information is transmitted to the server side server master updating unit 111 of the server computer 100 (step 603).
The server side server master update unit 111 receives the update information from the client side server master update unit 211 (step 604), updates the server master storage unit 101 (step 605), and stores the update information in the master update history storage unit 102. An update history as shown in FIG. 4 is added (step 606). Finally, the value of the serial number 401 of the record in the last master update history storage unit 102 (having the largest serial number) is stored in the server master update number storage unit 103.
Next, an operation when the user registers transaction data in the transaction data storage unit 104 from the client computer 200 will be described with reference to FIG. Note that the client computer 200 used in such a case may be the same as or different from the client computer 200 used for updating the server master storage unit 101 in FIG.
When activated by the user, the client side / transaction data registration unit 213 of the client computer 200 displays the sales transaction data registration screen illustrated in FIG. 9 on the input / output device (step 701). The client-side / transaction data registration unit 213 reads the product code and transaction date entered from the product code field 901 on the screen by the user (step 702), and searches the client master storage unit 201 using the product code as a key. The product name and unit price corresponding to the designated product code are read out and displayed on the sales transaction data registration screen (step 703). When the user who has confirmed the displayed product name and unit price inputs the number of orders for the product in the number field 902 of the screen, the client side / transaction data registration unit 213 reads the value (step 704), and the transaction entered above. The data (product code, the number and transaction date, etc.) and the value in the client master update number storage unit 202 are transmitted to the server side client master update unit 112 of the server computer 100 (step 705). Here, steps 702, 703, and 704 may be repeated a plurality of times depending on the screen displayed in step 701. For example, in the screen example of FIG. 9, each time a user sequentially inputs a product code into a plurality of product code fields 901, the client side / transaction data registration unit 213 repeats the above steps 702 to 704 for use. When the user presses the registration button 903 on the sales transaction data registration screen and detects that the input is completed, the process proceeds to step 705.
The server side / transaction data registration unit 113 receives the transmission information (step 720), compares the received value of the client master update number storage unit 202 with the value of the server master update number storage unit 103 (step 721), If it is the same value, the transaction data is registered in the transaction data storage unit 104 (step 722), and the operation is terminated.
In the above comparison (step 721), if the values are not the same, the server side / client master update unit 112 searches the master update history storage unit 102, and the value of the serial number 401 is received by the server side / transaction data registration unit 113. An update history record having a value larger than the value stored in the client master update count storage unit 202 is extracted as an update history record necessary for updating the client master storage unit 201 (step 730). Next, the product code in the extracted update history record is compared with the product code in the transaction data (step 731), and if there is no matching product code, the transaction data is registered in the transaction data storage unit 104 (step 732). Thereafter, the extracted update history record and the value of the server master update number storage unit 103 are transmitted to the client side client master update unit 212 (step 733).
If there is a match between the product code in the update history record extracted in the comparison in step 731 and the product code in the transaction data, the extracted update history is registered without registering the transaction data in the transaction data storage unit 104. The record and the value of the server master update number storage unit 103 are transmitted to the client side client master update unit 212 of the client computer 200 (step 734). At this time, notification that transaction data registration has failed is also made (step 734). The transaction data is not registered in the transaction data storage unit 104 when there is a match between the product code in the extracted update history record and the product code in the transaction data. This is because the information has been updated and deleted (for example, deletion of a product, price change, etc.) in the server master storage unit 101, and the user needs to review the transaction data.
Upon receiving the transmission information (step 710), the client side client master update unit 212 updates the client master storage unit 201 based on the received update history record (step 711), and the client master update number storage unit 202 Is updated to the value stored in the server master update number storage unit 103 (step 712), and the operation is terminated. However, if the server-side client master update unit 112 has received a notification that transaction data registration has failed (step 713), the client master storage unit 201 is updated for the product information specified in the transaction data. A message to the effect is displayed in the error message display field 904 of the sales transaction data registration screen of the input / output device (step 733). In the error message, a list of product codes that have been updated and the details of the update are notified based on the update history record. In response to this, the client side server master updating unit 211 resumes the product code input from step 702. The data in the client master storage unit 201 read in step 703 after resumption reflects the updated price change or the like.
In the above description, the server master storage unit 101 and the client master storage unit 201 are examples of product master files. However, the application of the present invention is not limited to this, and a supplier master file that stores supplier information. Or any other master file.
Note that the comparison in step 731 may be omitted, and the process may always proceed to step 734 after step 730. In this embodiment, the server master update number storage unit 103 is provided, but it is not always necessary to provide it. In such a case, the number of server master updates is obtained by referring to the maximum serial number in the update history record in the master update history storage unit 102. Further, the master update history storage unit 102 may not be provided. For example, when the server master storage unit 101 and the client master storage unit 201 have a small capacity and the server / client communication capacity is large, the master update history storage unit 102 is not provided. When transmitting to the server computer 100, the contents of the client master storage unit 201 may be transmitted to the server computer 100 at the same time, and in steps 721 and 730, the master storage units may be compared to detect and extract the difference. .
As described above, in this embodiment, even when the client computer 200 refers to the client master storage unit 201 many times when registering one transaction data, the server master storage unit 101 and the client master storage Communication between the client / server computer for confirmation of coincidence of the unit 201 does not occur, and only one communication (one round-trip) occurs for updating only when they do not coincide. Therefore, in a system in which transaction data registration is regularly performed in large quantities and the update frequency of the server master storage unit 101 is not high, the number of communications per transaction data registration is extremely low. As described above, the present invention maintains a low amount of communication between the client / server computers, and at the time when the contents of the server master storage unit 101 of the server computer 100 and the client master storage unit 201 of the client computer 200 need to match, There is an effect that the coincidence can be guaranteed.
Further, the present invention has an effect that even when the server master storage unit 101 is updated, it is not necessary to recreate transaction data unless the record referred to in transaction data creation is updated.
Next, a modification of the embodiment of the present invention will be described.
In this modification, the server computer 100 is provided with a plurality of server master storage units 101. In the first embodiment, the server master storage unit 101 is only a product master file storing product information. However, in this modification, other master storage such as a supplier master storage unit storing other supplier information is also available. Provide a part. The number of server master storage units 101 to be set is not limited to two. In such a configuration, the same number of client master storage units 201 of the client computer 200 are provided in correspondence with the existence of a plurality of server master storage units 101 of the server computer 100. At the same time, the name of the master storage unit to be updated is added to the update history record stored in the master update history storage unit 102. The configuration example is as shown in FIG. 11 instead of FIG. As shown in the figure, when the product master file, which is one of the server master storage units 101, is updated with changes in the addition, deletion, price, etc., one record for each updated product. As a product code, an update category indicating whether addition / deletion / update is performed, a storage name of the product master, and updated data (if the update category is deleted, there is no data) are stored. In addition, when the transaction master storage unit, which is another server master storage unit 101, is updated with the addition or deletion of a business partner or a change in the credit limit, etc., one record for each business partner updated at each update. Are stored as the supplier code, the update classification indicating the addition / deletion / update, the storage name of the supplier master, and the updated data (there is no data when the update classification is deleted). The same applies when other master files are provided. Other configurations are the same as those in the first embodiment.
The operation of updating the server master storage unit 101 in the configuration of the above modification will be described with reference to FIG. In the configuration according to this modification, the client side server master update unit 211 first displays the selection menu of the master storage unit to be updated exemplified in FIG. 10 on the display device in step 601, and the user selects the storage unit. When a product master file is selected by pressing a button or the like, a product master update screen as illustrated in FIG. 8 is displayed. The operation when the product master is selected is as described in the first embodiment. When the supplier master is selected, an update screen (not shown) for the supplier master is displayed, and then the update information (for example, supplier name, address, etc.) specified by the user on the input / output device from the screen. , Credit limit etc.) is read (step 602). The same operation is executed for other server master storage units 101. Thereafter, update information is transmitted to the server-side server master update unit 111 of the server computer 100 (step 603). In this embodiment, the update information to be transmitted includes the update information of the server master storage unit 101 to be updated. The name is also included.
The server side server master update unit 111 receives the update information from the client side server master update unit 211 (step 604), and updates the server master storage unit 101 whose name is included in the update information (step 605). An update history is added to the master update history storage unit 102 (step 606). The update history includes the name of the server master storage unit 101 as shown in FIG. Finally, the value of the serial number 401 of the record in the last master update history storage unit 102 (having the largest serial number) is stored in the server master update number storage unit 103.
The client-side server master update unit 211 allows a user to input update information of a plurality of server master storage units 101 using a single menu, and collectively sends the update information to the server-side server master update unit 111. You may implement | achieve so that it may transmit. In this case, the server-side server master updating unit 111 updates all the server master storage units 101 whose names are included in the update information in step 605.
Next, an operation when the user registers transaction data in the transaction data storage unit 104 from the client computer 200 will be described with reference to FIG. Also in this embodiment, the client computer 200 used in such a case may be the same as or different from the client computer 200 used for updating the server master storage unit 101 in FIG.
When activated by the user, the client side / transaction data registration unit 213 of the client computer 200 displays the sales transaction data registration screen illustrated in FIG. 9 on the input / output device (step 701). The client side / transaction data registration unit 213 reads the supplier code, the product code, the search code of the other server master storage unit 101, the transaction date, and the like input by the user from the product code column 901 on the screen (step 702). The product code, supplier code, and other server master storage unit 101 search codes are used as keys to search the product master, supplier master, and other client master storage units 201, respectively. The customer name, product name, unit price, etc. corresponding to the product code are read and displayed on the sales transaction data registration screen (step 703). When the user who has confirmed the displayed supplier name, product name, and unit price inputs the number of products ordered in the number field 902 of the screen, the client side / transaction data registration unit 213 reads the value (step 704), and The transaction data (customer code, product code, other server master storage unit 101 search code, number of transaction products, transaction date, etc.) and the value stored in the client master update number storage unit 202 are stored in the server side of the server computer 100. The data is transmitted to the client master update unit 112 (step 705). Here, steps 702, 703, and 704 may be repeated a plurality of times depending on the screen displayed in step 701. For example, in the screen example of FIG. 9, each time a user sequentially inputs a product code into a plurality of product code fields 901, the client side / transaction data registration unit 213 repeats the above steps 702 to 704 for use. When the user presses the registration button 903 on the sales transaction data registration screen and detects that the input is completed, the process proceeds to step 705.
The server side / transaction data registration unit 113 receives the transmission information (step 720), compares the received value of the client master update number storage unit 202 with the value of the server master update number storage unit 103 (step 721), If it is the same value, the transaction data is registered in the transaction data storage unit 104 (step 722), and the operation is terminated.
In the above comparison (step 721), if the values are not the same, the server side / client master update unit 112 searches the master update history storage unit 102, and the value of the serial number 1101 is received by the server side / transaction data registration unit 113 An update history record having a value larger than the value stored in the client master update count storage unit 202 is extracted as an update history record necessary for updating the client master storage unit 201 (step 730). The extracted update history record includes update records for a plurality of server master storage units 101. Next, the supplier code, product code or other search code in the server master storage unit 101 in each extracted update history record is compared with the same kind of code in the transaction data (step 731), and the matched supplier code If there is no product code or other server master storage unit 101 search code, the transaction data is registered in the transaction data storage unit 104 (step 732). Thereafter, the extracted update history record and the value of the server master update number storage unit 103 are transmitted to the client side client master update unit 212 (step 733).
If there is a match between the product code in the update history record extracted in the comparison in step 731 and the product code in the transaction data, the extracted update history is registered without registering the transaction data in the transaction data storage unit 104. The record and the value of the server master update number storage unit 103 are transmitted to the client side client master update unit 212 of the client computer 200 (step 734). At this time, notification that transaction data registration has failed is also made (step 734).
When the client-side / client master update unit 212 receives the transmission information described above (step 710), it updates the client master storage unit 201 based on the received update history record (step 711). When the update history record includes a plurality of server master storage unit 101 names, all corresponding client master storage units 201 are updated. Next, the value of the client master update number storage unit 202 is updated to the value of the received server master update number storage unit 103 (step 712), and the operation is terminated. However, if the server-side client master update unit 112 has received a notification that registration of transaction data has failed (step 713), the client master storage unit stores information on the business partner, product, etc. specified in the transaction data. The fact that 201 has been updated is displayed in the error message display field 904 of the sales transaction data registration screen of the input / output device (step 733). Based on the update history record, such an error message is notified of a list of updated supplier codes, product codes, other server master storage unit 101 search codes, and their update contents. In response to this, the client side server master updating unit 211 resumes the product code input from step 702. The data in the client master storage unit 201 read in step 703 after resumption reflects the updated price change or the like.
Note that the comparison in step 731 may be omitted, and the process may always proceed to step 734 after step 730. In this embodiment, the server master update number storage unit 103 is provided, but it is not always necessary to provide it. In such a case, the number of server master updates is obtained by referring to the maximum serial number in the update history record in the master update history storage unit 102. Further, the master update history storage unit 102 may not be provided. For example, when the server master storage unit 101 and the client master storage unit 201 have a small capacity and the server / client communication capacity is large, the master update history storage unit 102 is not provided. When transmitting to the server computer 100, the contents of the client master storage unit 201 may be transmitted to the server computer 100 at the same time, and in steps 721 and 730, the master storage units may be compared to detect and extract the difference. .
As described above, in this modification, even when a plurality of server master storage units 101 and client master storage units 201 are installed, the number of communication times per transaction data registration is the same as in the first embodiment. At a time when the contents of the server master storage unit 101 of the server computer 100 and the client master storage unit 201 of the client computer 200 need to be matched while keeping the communication amount between the client / server computer low. This has the effect of guaranteeing the coincidence.

FIG. 1 is a block diagram showing the configuration of a system to which the present invention is applied. FIG. 2 is a block diagram showing the configuration of the embodiment of the present invention. FIG. 3 is a diagram illustrating the contents of the server master storage unit and the client master storage unit. FIG. 4 is a diagram illustrating the contents of the master update history storage unit. FIG. 5 is a diagram illustrating an example of transaction data. FIG. 6 is a flowchart showing an operation of updating the server master storage unit by the client side server master update unit and the server side server master update unit. FIG. 7 illustrates the registration of transaction data by the client side / transaction data update unit and the server side / transaction data update unit, and the update operation of the client master storage unit by the server side / client master update unit and the client side / client master update unit. It is a flowchart which shows. FIG. 8 is a diagram illustrating an example of the server master storage unit update screen. FIG. 9 is a diagram illustrating an example of a sales transaction data registration screen. FIG. 10 is a diagram illustrating an example of a selection menu of the master storage unit to be updated in the modification of the embodiment. FIG. 11 is a diagram illustrating the contents of the master update history storage unit in a modification of the embodiment.

Explanation of symbols

100 server computer 101 server master storage unit 102 master update history storage unit 103 server master update number storage unit 104 transaction data storage unit 111 server side server master update unit 112 server side client master update unit 113 server side transaction data update unit 200 Client Computer 201 Client Master Storage Unit 202 Client Master Update Number Storage Unit 211 Client Side / Server Master Update Unit 212 Client Side / Client Master Update Unit 213 Client Side / Transaction Data Update Unit

Claims (11)

A client / server system comprising at least one client computer and one server computer,
The server computer
A server master storage unit and a transaction data storage unit for storing transaction data;
Each of the at least one client computer is
A client master storage unit having information obtained by copying information in the server master storage unit;
A client side transaction data registration unit for transmitting transaction data input from a user to the server computer,
The server computer
When the transaction data is received from the client computer, the contents of the server master storage unit and the client master storage unit are checked for coincidence, and if they match, the server registers the transaction data in the transaction data storage unit Side and transaction data registration department,
A server that extracts a difference between the contents of the server master storage unit and the client master storage unit and transmits the extracted client master update difference to the client computer when it is confirmed by the match check that they do not match Side client master update unit,
The client computer is
A client / server system comprising a client-side client master update unit that updates the client master storage unit based on the client master update difference received from the server computer. At least one of the at least one client computer is
A client-side server master update unit that transmits update information for the server master storage unit input by a user to the server computer,
The server computer
The client / server system according to claim 1, further comprising a server-side server master update unit that receives the update information and updates the server master storage unit based on the update information. The server computer
As the update history whenever the information of the server master storage unit is changed, a master update history storage unit that stores one update history record,
Each of the at least one client computer is
A client master update number storage unit that stores the number of the update history records that have been updated in the client master storage unit,
The server side / transaction data registration unit is configured to compare the contents of the server master storage unit and the client master storage unit by comparing the number of update history records in the master update history storage unit and the value of the client master update number storage unit. Check for a match
The server side client master update unit extracts an update history record from the master update history storage unit based on a difference between the number of the update history records in the master update history storage unit and a value of the client master update number storage unit. To extract the difference for updating the client master,
The client side server master update unit updates the client master storage unit based on the client master update difference received from the server computer, and sets the number of update history records in the master update history storage unit to the client master The client / server system according to claim 1, wherein the client / server system is stored in an update number storage unit. At least one of the at least one client computer includes the client-side server master update unit that transmits the update information for the server master storage unit input by a user to the server computer,
The server computer receives the update information, updates the server master storage unit based on the update information, and stores the update history of the update in the master update history storage unit as the update history record 4. The client / server system according to claim 3, further comprising a side server master update unit. The server master storage unit stores a master record composed of an identifier and data related to the identifier,
The master update history storage unit stores the update history record including the identifier of the master record corresponding to the updated master record,
The transaction data includes at least one identifier of the master record;
The server side client master update unit, when there is no match between the identifier included in each update history record of the client master update difference and the identifier included in the transaction data, the transaction data 5. The client / server system according to claim 3, wherein the client / server system is stored in the transaction data storage unit. At least one client comprising a server computer having a server master storage unit and a transaction data storage unit for storing transaction data, and a client master storage unit having information obtained by copying information in the server master storage unit In a client / server system consisting of computers,
A client-side transaction data registration step in which the client computer transmits transaction data input by a user to the server computer;
When the server computer receives the transaction data from the client computer, it confirms the contents of the server master storage unit and the client master storage unit, and if they match, stores the transaction data in the transaction data storage Server-side transaction data registration step to be registered in the department,
When the server computer confirms that there is no match in the match check, it extracts a difference between the contents of the server master storage unit and the client master storage unit, and uses the extracted client master update difference as the client A server-side client master update step to send to the computer;
Reflecting master data in a client / server system, wherein the client computer includes a client side client master update step of updating the client master storage unit based on the client master update difference received from the server computer Method. A client-side server master update step in which at least one of the at least one client computer transmits update information for the server master storage unit input by a user to the server computer;
7. The client / server system according to claim 6, further comprising a server-side server master update step in which the server computer receives the update information and updates the server master storage unit based on the update information. Method for reflecting master data. The server computer includes
As the update history whenever the information of the server master storage unit is changed, a master update history storage unit that stores one update history record,
Each of the at least one client computer is
In the client / server system comprising a client master update number storage unit that stores the number of the update history records that have been updated in the client master storage unit,
In the server-side / transaction data registration step, the server computer compares the number of the update history records in the master update history storage unit with the value of the client master update number storage unit to compare the server master storage unit and the client master. Check the content of the storage unit,
In the server side client master update step, the client computer updates from the master update history storage unit based on a difference between the number of the update history records in the master update history storage unit and the value of the client master update number storage unit. Extracting the client master update difference by extracting a history record,
In the client side server master update step, the client computer updates the client master storage unit based on the client master update difference received from the server computer, and the update history record in the master update history storage unit 7. The method of reflecting master data in a client / server system according to claim 6, wherein the number is stored in said client master update number storage unit. The client-side server master update step in which at least one of the at least one client computer transmits the update information for the server master storage unit input by a user to the server computer;
The server side in which the server computer receives the update information, updates the server master storage unit based on the update information, and stores an update history of the update in the master update history storage unit as the update history record 9. A master data reflection method in a client / server system according to claim 8, further comprising a server master update step. The server master storage unit stores a master record composed of an identifier and data related to the identifier,
The master update history storage unit stores the update history record including the identifier of the master record corresponding to the updated master record,
In the client / server system, the transaction data includes the identifier of at least one of the master records,
In the server side client master update step, when the server computer has no match between the identifier included in each update history record of the client master update difference and the identifier included in the transaction data 10. The master data reflecting method in the client / server system according to claim 8, wherein the transaction data is stored in the transaction data storage unit. One server communicable with at least one client computer comprising a server master storage unit and a transaction data storage unit for storing transaction data, and a client master storage unit having information obtained by copying information in the server master storage unit On the server computer,
When the transaction data is received from the client computer, the contents of the server master storage unit and the client master storage unit are checked for coincidence, and if they match, the server registers the transaction data in the transaction data storage unit Side / transaction data registration procedure,
A server that extracts a difference between the contents of the server master storage unit and the client master storage unit and transmits the extracted client master update difference to the client computer when it is confirmed by the match check that they do not match A program for executing the side client master update procedure.

Images