JP2012058767A - Commodity information collating device, commodity information collating system, and commodity information collating program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To surely detect contents of inconsistency without any trouble when commodity data is inconsistent between a store server and a head office server.SOLUTION: When receiving a collation source file storing commodity codes and selling prices of all commodities that are registered in a head office commodity master file 11, a store server 22 collates whether the commodity codes of all the commodities stored in the collation source file are stored in a store commodity master file 21 or not and, when they are stored therein, collates whether the selling prices correspond with the commodity codes. The store server 22 identifiably outputs commodity codes that are stored in the store commodity master file 21 but not stored in the collation source file, commodity codes that are stored in the collation source file but not stored in the store commodity master file 21, and commodity codes that are stored in both of the files but whose corresponding selling prices do not correspond with the commodity codes.

Description

  Embodiments of the present invention relate to a technique for collating product information stored in a headquarters database and a store database, for example, in a chain store system including a headquarters and a plurality of stores controlled by the headquarters.

  The chain store system includes a plurality of member stores and a headquarters that controls each member store. Each member store includes a server computer for managing a database of products sold at the store, a so-called store server. The headquarters is provided with a server computer for centrally managing a database of products sold at each member store, a so-called headquarter server. The headquarter server connects the store servers of each member store via a wide-area communication network so as to allow two-way communication.

  The database managed by the headquarters server and each store server stores and stores product information such as the name and selling price of the product corresponding to the product code unique to each product.

  Generally, the headquarters decides whether to purchase and sell new products. In addition, the sales price of products is changed by the headquarters. When selling a new product, the headquarters server additionally registers the data of the new product in the database and distributes it to each store server. When changing the selling price, the headquarters server corrects the selling price of the corresponding product stored in the database to the changed selling price, and transmits data notifying the selling price change to each store server. When the store server receives new product data, the store server additionally registers the received data in the database. When data notifying the selling price change is received, the selling price of the corresponding product stored in the database is corrected to the changed selling price.

  Stores may purchase and sell their own products. In this case, the store server additionally registers the data of the new product in the database and transmits it to the headquarter server. When the headquarter server receives the data of the new product, it additionally registers the received data in the database.

  Therefore, if no error occurs in data communication between servers or database update processing, the data of each product stored in the database of the store server matches the data of the same product stored in the database of the head office server. To do. In other words, when the above-described error occurs, the product data is inconsistent between the store server and the headquarter server.

Japanese Patent Laid-Open No. 10-289379

  There is a demand for a technology that can detect the contents of the inconsistency reliably and without trouble when product data is inconsistent between the store server and the headquarters server.

  According to one embodiment, the product information collating apparatus includes a receiving unit, a product code collating unit, a selling price collating unit, and a collation result output unit. The receiving means receives a verification source file storing the product codes and selling prices of all the products registered in the verification requesting side device. The merchandise code collating means stores the merchandise codes of all the merchandise stored in the received collation source file in the merchandise information file storing at least the merchandise codes and selling prices of all merchandise registered in the collation processing side device. Check if it is. When the same product code is stored in the product information file and the verification source file, the sales price verification unit verifies whether the sales price corresponding to the product code matches. The verification result output means includes a product code stored in the product information file but not stored in the verification source file, a product code stored in the verification source file but not stored in the product information file, and product information The product code that is stored in the file and the matching source file but does not match the corresponding selling price is output in an identifiable manner.

The schematic diagram for demonstrating the outline of the chain store system which is one Embodiment. The schematic diagram which shows the data structure of 1 record memorize | stored in the headquarters merchandise master file in the same embodiment. The schematic diagram which shows the data structure of 1 record memorize | stored in a store goods master file in the same embodiment. The block diagram which shows the principal part structure of the headquarters server in the same embodiment. FIG. 3 is a schematic diagram showing an area structure of an error information table included in the headquarter server in the embodiment. The block diagram which shows the principal part structure of a store server in the embodiment. The schematic diagram which shows the area structure of the collation result table which the store server has in the same embodiment. The flowchart which shows the procedure of the merchandise information collation request | requirement process which CPU of a headquarter server performs in the same embodiment. The flowchart which shows the specific procedure of the collation result reception process shown as step ST7 in FIG. The flowchart which shows the procedure of the merchandise information collation process which CPU220 of a store server performs in the same embodiment. The schematic diagram which shows an example of the collation result output screen displayed on the display connected to the headquarters server in the same embodiment. The schematic diagram which shows an example of the shop collation result detailed screen displayed on the display connected to the headquarters server in the same embodiment.

  An embodiment in which a headquarter server of a chain store system is a verification requesting side device and a store server of the system is a verification processing side device will be described with reference to the drawings.

FIG. 1 is a schematic diagram for explaining an outline of a chain store system. The chain store system includes a headquarter system 10 and a member store system 20. The headquarters system 10 includes a headquarters product master file 11 that is a headquarters product database, and a headquarter server 12 that manages the file 11. The member store system 20 includes a store product master file 21 that is a product database on the member store side, and a store server 22 that manages the file 21. The store server 22 connects a plurality of POS (Point Of Sales) terminals 24 via a communication network 23 such as a LAN (Local Area Network). The headquarter server 12 connects the store server 22 via a communication network 30 such as an intranet.
In FIG. 1, only one member store system 20 is shown, but actually, a plurality of member store systems 20 are connected to the headquarter system 10.

  FIG. 2 is a schematic diagram showing the data structure of one record 110 stored in the headquarters product master file 11. This record 110 corresponds to one product. This record 110 includes a product-specific product code 111 set for each product, product-specific information 112 such as a product name (product name), a classification code, and a selling price specified by the product code 111, a manufacturer code, It includes manufacturer information 113 such as a manufacturer name and order management information 114 such as an ordering party code and an ordering unit.

  FIG. 3 is a schematic diagram showing the data structure of one record 210 stored in the store product master file 21. This record 210 corresponds to one product. This record 210 includes a product-specific product code 211 set for each product, a product name (product name) specified by the product code 211, a product-specific information 212 such as a classification code, a selling price, a sales floor code, Store-specific local information 213 such as a shelf label number and a checked flag 214 are included.

  The headquarters server 12 creates maintenance data for the store merchandise master file 21 each time a record of the headquarters merchandise master file 11 is added, deleted or changed, and updates the store server 22 of each store via the communication network 30. Deliver to.

  When the store server 22 receives the maintenance data, the store server 22 performs maintenance on the store product master file 21 based on the received data. For example, when additional information on a new record is received, a new store product master record 210 is created based on the information and added to the store product master file 21. When the deletion information of the existing record is received, the existing store product master record 210 specified by the information is deleted from the store product master file 21. For example, when selling price change information of an existing record is received, the selling price included in the product specific information 212 of the existing record specified by the information is changed to the changed selling price.

  FIG. 4 is a block diagram showing a main configuration of the headquarter server 12. The headquarter server 12 includes a CPU (Central Processing Unit) 120 as a control unit main body. The CPU 120 is connected to a ROM (Read Only Memory) 121 and a RAM (Random Access Memory) 122 constituting a main storage unit via a bus line such as an address bus and a data bus, and a clock unit for measuring the current date and time. 123, a hard disk drive (HDD) 124 constituting an auxiliary storage unit, and various input / output interfaces such as a communication interface 125, a keyboard interface 126, a mouse interface 127, a display interface 128, and a printer interface 129 are connected. The communication interface 125 manages data communication performed with the store server 22 via the communication network 30.

  FIG. 5 is a schematic diagram showing an area structure of the error information table 40 provided in the head office server 12. The error information table 40 includes an area for storing an error presence flag 42, error 1 information 43, error 2 information 44, and error 3 information 45 for each store name 41. The store name 41 is a unique name of each store formed by connecting the store server 22 of the member store system 20 to the communication network 30. The error presence / absence flag 42, error 1 information 43, error 2 information 44, and error 3 information 45 will be described later. The headquarter server 12 forms the error information table 40 in the RAM 122.

  FIG. 6 is a block diagram showing a main configuration of the store server 22. The store server 22 includes a CPU 220 as a control unit main body. The CPU 220 is connected to the ROM 221 and the RAM 222 constituting the main storage unit, the clock unit 223 for measuring the current date and time, and the HDD 224 constituting the auxiliary storage unit via bus lines such as an address bus and a data bus. The first communication interface 225a and the second communication interface 225b are connected to various input / output interfaces such as a keyboard interface 226, a mouse interface 227, a display interface 228, and a printer interface 229. The first communication interface 225 a manages data communication performed with the headquarters server 12 via the communication network 30. The second communication interface 225 b manages data communication with each POS terminal 24 via the communication network 23.

  FIG. 7 is a schematic diagram showing an area structure of the matching result table 50 provided in the store server 22. The matching result table 50 includes an area for storing a product code 52, a selling price 53, and other product information 54 for each series of table numbers 51. The store server 22 forms a matching result table 54 in the RAM 222. The collation result table 54 functions as a collation result storage unit.

  In such a configuration, the CPU 120 of the headquarter server 12 periodically executes the merchandise information matching request process of the procedure shown in the flowchart of FIG. This process follows a product information collation request program resident in the ROM 121.

  That is, the CPU 120 first waits for the current time measured by the clock unit 123 to reach a predetermined collation time (ST1). The collation time is set in advance at an arbitrary time every morning, for example. When the current time reaches the collation time (YES in ST1), the CPU 120 acquires the product code and the selling price from all the records 110 registered in the headquarters product master file 11 (ST2). Then, a verification source file is created from the product codes and selling prices of all the acquired records (ST3: creation means). The collation source file is a file in which the product code acquired from the same record and the selling price are stored in association with each other.

  CPU 120 compresses the data of the generated verification source file (ST4). The data compression technique is not particularly limited. For example, run length coding, Huffman coding, n / 2n coding, or the like may be applied. The CPU 120 distributes the collation source file obtained by compressing the data to the store server 22 of each member store system 20 via the communication network 30 (ST5: transmission means).

  The CPU 220 of the store server 22 executes the merchandise information matching process according to the procedure shown in the flowchart of FIG. This process follows a product information collation program resident in the ROM 221.

  That is, the CPU 220 waits for reception of the collation source file (ST31: receiving means). When the verification source file distributed from the headquarter server 12 is received via the communication network 30 (YES in ST31), the CPU 220 expands the received verification source file data in the RAM 222 (ST32).

  The CPU 220 resets the checked flags 214 of all the store product master records 210 registered in the store product master file 21 to “0” (ST33). Further, the number of data in a pair of the product code obtained by expanding from the collation source file and the selling price associated therewith is set in the register N provided in the RAM 222 (ST34).

  The CPU 220 once resets the counter n provided in the RAM 222 to “0” (ST35). Next, the CPU 220 increments the counter n by “1” (ST36). Then, CPU 220 determines whether counter n has exceeded the value of register N (ST37).

  When the counter n does not exceed the value of the register N (NO in ST37), the CPU 220 detects the paired data of the nth product code and selling price from the data obtained by expanding the collation source file (ST38). The CPU 220 searches the store product master file 21 with the detected product code of the paired data (ST39), and determines whether or not there is a store product master record 210 including the same product code (ST40: product). Code verification means).

  When the store product master record 210 including the same product code does not exist (NO in ST40), the CPU 220 stores the verification source data, that is, the detected product code of a pair of data in the product code area 52 of the verification result table 50. Let At this time, information “0” indicating that there is no data is stored in the selling price area 53 and the other product information area 54 of the matching result table 50 (ST41: matching result output means). Thereafter, the CPU 220 returns to the process of step ST36 and further increments the counter n by “1”. And the process after step ST37 is performed again.

  When the store product master file 21 including the same product code exists as a result of searching the store product master file 21 in the process of step ST39 (YES in ST40), the CPU 220 has checked the store product master record 210. The flag 214 is set to “1” (ST42). Next, the CPU 220 determines whether or not the selling price set in the store merchandise master record 210 matches the selling price of the detected paired data (ST43: selling price matching means).

  If the selling prices match (YES in ST43), the CPU 220 returns to the process in step ST36 and further increments the counter n by “1”. And the process after step ST37 is performed again.

  On the other hand, if the selling prices do not match (NO in ST43), the CPU 220 converts the product code and selling price of the store product master record 210 into the product code area 52 and selling price area 53 of the matching result table 50. Remember. At this time, information “0” indicating that there is no data is stored in the other product information area 54 of the verification result table 50 (ST44: verification result output means). Thereafter, the CPU 220 returns to the process of step ST36 and further increments the counter n by “1”. And the process after step ST37 is performed again.

  Until the counter n exceeds the value of the register N, the CPU 220 performs the processing of steps ST38, ST39, ST40, ST41, the processing of steps ST38, ST39, ST40, ST42, ST43, or the steps ST38, ST39, ST40, ST42, The processing of ST43 and ST44 is executed.

  If the counter n exceeds the value of the register N in step ST37 (YES in ST37), the CPU 220 searches the store product master file 21 and stores the store product whose checked flag is still reset to “0”. All master records 210 are extracted. Then, the product code and the selling price of the extracted record 210 and the product unique information such as the product name and the classification code are stored in the product code area 52, the selling price area 53, and the product information area 54 of the matching result table 50, respectively (ST45). : Collation result output means).

  Thereafter, the CPU 220 transmits the data of the collation result table 50 to the headquarter server 12 through the communication network 30 together with the store name data set in advance (ST46: result transmission means). This is the end of the current program processing.

  Returning to FIG. As described above, the CPU 220 of each store server 22 that has received the verification source file returns the data of the verification result table to the headquarter server 12. Therefore, after distributing the verification source file, the CPU 120 of the headquarter server 12 executes a verification result reception process specifically shown in FIG. 9 (ST6).

  That is, the CPU 120 waits to receive data of the collation result table sent from the store server 22 (ST11: result receiving means). And if the data of a collation result table are received, CPU120 will acquire a shop name from the data (ST12).

  Next, CPU 120 analyzes the data of the received collation result table, and determines whether there is error information, that is, whether a product code is stored (ST13). If the product code is not stored in the verification result table, there is no error information. In this case (NO in ST13), the CPU 120 sets the error presence / absence flag 42 corresponding to the store name 41 in the error information table 40 to information indicating no error, for example, “0” (ST14).

  If the product code is stored in the matching result table, there is error information. In this case (YES in ST13), the CPU 120 sets the error presence / absence flag 42 corresponding to the store name 41 in the error information table 40 to information indicating that there is an error, for example, “1” (ST15).

  Next, CPU 120 sets the number of product codes stored in the collation result table, that is, the number of error information, in register N provided in RAM 122 (ST16). The CPU 120 once resets the counter n provided in the RAM 122 to “0” (ST17). Next, the CPU 120 counts up the counter n by “1” (ST18). Then, CPU 120 determines whether counter n has exceeded the value of register N (ST19).

  If counter n does not exceed the value of register N (NO in ST19), CPU 120 detects the nth error data from the collation result table (ST20). Then, the CPU 120 determines whether or not the detected error data includes product information (product name, classification code, etc.) other than the selling price (ST21: identification unit). If included (YES in ST21), the CPU 120 stores the error data (product code, selling price, other product information) in the error 3 information area 45 corresponding to the store name 41 in the error information table 40. (ST22: Identification result output means).

  In the process of step ST21, when other product information is not included in the detected error data (NO in ST21), the CPU 120 determines whether or not the selling price is included in the error data (ST23: Identification means). If it is included (YES in ST23), the CPU 120 stores the error data (product code, selling price) in the error 1 information area 43 corresponding to the store name 41 in the error information table 40 (ST24: identification result). Output means).

  In the process of step ST23, when the detected error data does not include the selling price and other product information (NO in ST23), the CPU 120 stores the error data (product code) in the error information table 40. It is stored in the error 2 information area 44 corresponding to the store name 41 (ST25: identification result output means).

  When the process of step ST22, ST24 or ST25 is completed, the CPU 120 returns to the process of step ST18 and further increments the counter n by “1”. And the process after step ST19 is performed again.

  CPU 120 executes the processing of steps ST20, ST21, ST22, the processing of steps ST20, ST21, ST23, ST24, or the processing of steps ST20, ST21, ST23, ST25 until counter n exceeds the value of register N. .

  If the counter n exceeds the value of the register N in step ST19, the CPU 120 proceeds to the process of step ST7 in FIG.

  In step ST <b> 7, the CPU 120 determines whether or not the verification result table data has been received from the store server 22 of each store. When reception has not been completed (NO in ST7), CPU 120 executes the collation result reception process in step ST6 again.

  If the data of the collation result table is received from the store servers 22 of all stores (YES in ST7), the CPU 120 outputs the collation results of all stores based on the data of the error information table 40 (ST8).

  For example, the CPU 120 displays and outputs the matching results of all stores on a display connected to the display interface 128. FIG. 11 is an example of the collation result output screen 60. In this example, the numbers of error 1 information, error 2 information, and error 3 information collected for each store in the error information table 40 are displayed in a list format.

  Here, the error 1 information is information in which error data recorded in the collation result table includes a product code and a selling price. The error data including the product code and the selling price is generated when the selling price is different in the data of the same product in the headquarters product master file 11 and the store product master file 21. Therefore, in the collation result output screen 60 of FIG. 11, the number of error 1 information is displayed as the number of sales price mismatches.

  In the error 2 information, the error data recorded in the collation result table is composed only of the product code. The error data consisting only of the product code is generated when the product data registered in the headquarters product master file 11 is not registered in the store product master file 21. Therefore, on the collation result output screen 60, the number of error 2 information is displayed as the number of products without stores.

  In the error 3 information, the error data recorded in the verification result table includes a product code, a selling price, and other product information. The error data consisting of the product code, selling price and other product information is uniquely registered when the product data registered in the store product master file 21 is not registered in the headquarters product master file 11, that is, on the store side. Generated when Therefore, on the collation result output screen 60 of FIG. 11, the number of error 3 information is displayed as the number of store registered products.

  In the present embodiment, a detail button 61 and an end button 62 for each store are displayed on the collation result output screen 60. When the user operates the mouse connected to the mouse interface 127 or operates the keyboard connected to the keyboard interface 126 and selectively inputs the detail button 61 of any store, as shown in FIG. In addition, the screen of the display is switched to a detailed screen 70 showing the product master matching result of the store.

  In the store matching result detail screen 70, regarding the selling price mismatch data of the error 1 information 1, the product code and product name of the product, the selling price set in the headquarters product master file 11, and the store product master file 21 are displayed. The selling price set for and the number of cases are displayed. Regarding the data of the product without store in the error 2 information, the product code and the product name set in the headquarters product master file 11 of the product are displayed together with the number of items. Regarding the data of the store registration product of the error 3 information, the product code, product name, classification code, selling price, etc. set in the store product master file 21 of the product are displayed together with the number of cases.

  In addition, a return button 71 and a print button 72 are displayed on the store matching result detail screen 70. When the user operates the mouse or keyboard to input the return button 71, the display screen returns to the verification result output screen 60. When the print button 72 is input, the content displayed on the store matching result detail screen 70 is printed out from a printer connected via the printer interface 129.

  As described above, in the chain store system of the present embodiment, the headquarter server 12 acquires the product codes and selling prices of all the records registered in the headquarters product master file 11 at a predetermined time on each business day, Create a verification source file. Then, this verification source file is distributed to the store servers 22 of all member store systems 20 connected via the communication network 30.

  In the store server 22 that has received this verification source file, the product codes and selling prices of all the records stored in the verification source file are verified against the store product master record stored in the store product master file 21. As a result, regarding the products with different selling prices, the product codes of the products and the selling prices set in the store product master record 210 are recorded in the matching result table 50. Further, for a product that exists in the verification source file but does not exist in the store product master file 21, the product code set in the verification source file of the product is recorded in the verification result table 50. On the other hand, for a product that exists in the store product master file 21 but does not exist in the collation source file, the product code and selling price set in the store product master file 21 of the product, the product name, the classification code, etc. Other product information is recorded in the matching result table 50. When the store server 22 finishes the collation, the store server 22 transmits the data of the collation result table 50 to the headquarter server 12 via the communication network 30.

  The headquarter server 12 that has received the data of the verification result table 50 analyzes the data of the verification result table 50. As for the data composed of the product code and the selling price, the selling price registered in the headquarters product master file 11 and the selling price registered in the store product master file 21 are the same for the product identified by the product code. Recognize that it is not. For data consisting only of the product code, it is recognized that the product identified by the product code is registered in the headquarters product master file 11 but not registered in the store product master file 21. Regarding the data consisting of the product code, selling price and other product information, the product identified by the product code is registered in the store product master file 21 but not registered in the headquarters product master file 11. recognize. Then, the screens 60 and 70 showing the recognition result are displayed or printed out.

  As described above, according to the present embodiment, the store product master record registered in the store product master file 21 is checked in all cases of the headquarter product master record registered in the headquarters product master file 11, so the store server When the product data is inconsistent between the headquarters 22 and the headquarters server 12, the content of the inconsistency can be detected reliably and without trouble.

  In addition, according to the present embodiment, the data including the product code and the selling price is recorded in the matching result table 50 for the selling price mismatch data, and the data of only the product code is stored in the matching result table 50 for the data of the store-free product. With respect to the data of the store registration product, data including a product code, a selling price, and other consumption information is recorded in the verification result table 50. Therefore, there is no need to separately record a flag or the like for identifying the type of data in the collation result table 50, so that the storage capacity of the collation result table 50 can be reduced.

  In this embodiment, the function for carrying out the invention is recorded in advance in the apparatus. However, the present invention is not limited to this, and the same function may be downloaded from the network to the apparatus. What is stored in the recording medium may be installed in the apparatus. The recording medium may be any form as long as the recording medium can store the program and can be read by the apparatus, such as a CD-ROM. In addition, the function obtained by installing or downloading in advance may be realized in cooperation with an OS (operating system) inside the apparatus.

  Moreover, the said embodiment is shown as an example and is not intending limiting the range of invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 10 ... Head office system, 11 ... Head office product master file, 12 ... Head office server, 20 ... Nest member store system, 21 ... Store product master file, 22 ... Store server, 30 ... Communication network, 40 ... Error information table, 50 ... Verification Result table, 60 ... verification result output screen, 70 ... store verification result detail screen.

Claims (6)

Receiving means for receiving a verification source file storing the product codes and selling prices of all the products registered in the verification requesting device;
Product for checking whether the product code of all products stored in the received verification source file is stored in the product information file storing at least the product codes and selling prices of all products registered in the verification processing side device Code verification means;
When the same product code is stored in the product information file and the verification source file, the sales price verification means for verifying whether the sales price corresponding to the product code matches,
A product code stored in the product information file but not stored in the verification source file, a product code stored in the verification source file but not stored in the product information file, and the product information file And a matching result output means for outputting the product codes stored in the matching source file but having the corresponding selling price not matching each other,
A product information collating apparatus characterized by comprising:   For the product code that is stored in the product information file but not stored in the verification source file, the verification result output means uses the product information stored in the product information file corresponding to the product code. For the product code that is output to the verification result storage unit and stored in the verification source file but not stored in the product information file, the product code is output to the verification result storage unit, and the product information file and the product code For a product code that is stored in the verification source file but does not match the corresponding sales price, the product code and the sales price information stored in correspondence with the product code in the product information file are stored in the verification result storage unit. The product information collating apparatus according to claim 1, wherein the product information collating apparatus outputs the information to the product information collating apparatus.   3. The product information collating apparatus according to claim 2, further comprising a result transmitting means for transmitting data stored in the collation result storage unit to the collation requesting side apparatus. A system comprising a verification requesting device and a verification processing side device, wherein the verification requesting side device and the verification processing side device are connected by a communication network,
The verification processing side device
Receiving means for receiving a collation source file storing product codes and selling prices of all commodities registered in the collation request side device;
The product information file that stores at least the product codes and selling prices of all products registered in the verification processing side device is checked to see if the product codes of all products stored in the received verification source file are stored. Product code matching means;
When the same product code is stored in the product information file and the verification source file, the sales price verification means for verifying whether the sales price corresponding to the product code matches,
A product code stored in the product information file but not stored in the verification source file, a product code stored in the verification source file but not stored in the product information file, and the product information file And a matching result output means for outputting a product code stored in the matching source file but having a corresponding selling price that does not match, to the matching result storage unit in an identifiable manner,
A result transmitting means for transmitting the data stored in the verification result storage unit to the verification request side device via the communication network, and
The verification requesting device is:
Creating means for creating a collation source file storing product codes and selling prices of all products registered in the collation request side device;
Transmitting means for transmitting the verification source file to the verification processing side device via the communication network;
A result receiving means for receiving the verification result storage unit sent from the verification processing side device via the communication network;
From the data stored in the verification result storage unit, the product code stored in the product information file but not stored in the verification source file, and stored in the verification source file but stored in the product information file Identification means for identifying a product code that is not stored, and a product code that is stored in the product information file and the verification source file but does not match the corresponding selling price;
A product information collating system comprising: an identification result output unit that outputs a product code identification result by the identification unit. For the product code that is stored in the product information file but not stored in the verification source file, the verification result output means uses the product information stored in the product information file corresponding to the product code. For the product code that is output to the verification result storage unit and stored in the verification source file but not stored in the product information file, the product code is output to the verification result storage unit, and the product information file For a product code stored in the verification source file but whose corresponding selling price does not match, the product code and the selling price information stored corresponding to the product code in the product information file are stored in the verification result storage. Output to
The identification means identifies a product code stored together with product information in the verification result storage unit from a product code stored in the product information file but not stored in the verification source file, and stores only the product code. Product codes that are stored in the verification source file but are not stored in the product information file, and the product codes that are stored together with selling price information are the product information file and the verification source 5. The product information matching system according to claim 4, wherein the product code is identified as a product code that is stored in a file but does not match a corresponding selling price. A program for a collation processing side device formed by connecting a collation request side device via a communication network,
The verification processing side device,
When a verification source file storing the product codes and selling prices of all products registered in the verification requesting device is received via the communication network, all the products registered in the verification processing side device Product code verification means for verifying whether or not the product codes of all the products stored in the received verification source file are stored in the product information file storing at least the product code and the selling price;
When the same product code is stored in the product information file and the verification source file, the sales price verification means for verifying whether the sales price corresponding to the product code matches,
A product code stored in the product information file but not stored in the verification source file, a product code stored in the verification source file but not stored in the product information file, and the product information file And a product information collation program for functioning as a collation result output means for outputting a product code that is stored in the collation source file but does not match the corresponding selling price in an identifiable manner.

Images