JP7163201B2 - Update data confirmation device and its control program - Google Patents

Description

An embodiment of the present invention relates to an update data confirmation device and a control program for causing a computer to function as the update data confirmation device.

Among relatively large-scale retail stores such as department stores, chain stores, and specialty stores, customers are ranked according to preferential ranks according to store usage status, etc., and unit prices or discount rates are set for each preferential rank. There are places that take the form of sales to do. In general, this type of retail store has a plurality of POS (Point Of Sales) terminals for registering sales data of products purchased by customers, and a POS (Point Of Sales) terminal for aggregating the sales data registered at each POS terminal for each store. A POS system comprising a store server is constructed. The store server is provided with a data file in which the unit price or discount rate is set for each preferential treatment rank in association with the identification code that identifies each product.

The amount of data in the data file is proportional to the number of product items sold at the store. For this reason, in a store that handles a large number of products, the amount of data becomes enormous. Therefore, when correcting the data in the data file due to a change in sales price or the like, the correction work required a great deal of time and effort.

Therefore, update data for updating the data file is created by a system other than the POS system. The store server fetches the update data from the other system and updates the data in the data file based on the update data. By adopting such a method, it is believed that the labor required for correcting the data file can be reduced, and the time can be shortened.

However, in order to make effective use of such a method, it is necessary to construct a mechanism for efficiently confirming the correctness of update data before correcting the data in the data file to be updated.

Japanese Patent Application Laid-Open No. 2001-160183

A problem to be solved by the embodiments of the present invention is to provide an update data confirmation device capable of efficiently confirming the correctness of update data before updating the data to be updated with the update data.

In one embodiment, an update data confirmation device comprises acquisition means, management means, and execution means. The obtaining means obtains a data file storing update data for updating data to be updated. The management means manages a setting table in which the order of execution and the details of processing after error detection are set for each error check item for confirming the validity of the update data. The executing means executes an error check for the item in accordance with the execution order set in the setting table, and when an error is detected, executes a process corresponding to the processing content set in the setting table for the item.

1 is a schematic configuration diagram of a headquarters management system that is an embodiment; FIG. Schematic diagram showing the data structure of a single-item record saved in a single-item master file. Schematic diagram showing the data structure of a classification record saved in a classification master file. 4 is a schematic diagram showing the data structure of a single item update record or classification update record stored in a single item update data file or classification update data file; FIG. FIG. 3 is a block diagram for explaining functions of a store server as an update data confirmation device; 4 is a schematic diagram showing an example of a setting table held by the store server; FIG. FIG. 2 is a block diagram showing the main circuit configuration of the store server; 4 is a flow chart showing main procedures of information processing executed by the processor of the store server according to the control program; 4 is a flow chart showing main procedures of information processing executed by the processor of the store server according to the control program; FIG. 4 is a schematic diagram showing an example of a single-item execution pattern table; FIG. 4 is a schematic diagram showing an example of a classification execution pattern table; FIG. 4 is a schematic diagram showing an example of a pop-up image for error notification; FIG. 4 is a schematic diagram showing an example of an error list image for error notification;

An embodiment of an update data confirmation device capable of efficiently confirming the validity of update data before updating data to be updated with update data will be described below with reference to the drawings.
In this embodiment, a retail store head office management system is exemplified in which customers are ranked according to preferential treatment ranks according to store usage conditions, etc., and the unit price or discount rate of products is set for each preferential treatment rank. . That is, in the present embodiment, the data to be updated is the data of the data file in which the unit price or discount rate is set for each preferential treatment rank in association with the identification code that identifies each product.

FIG. 1 is a schematic configuration diagram of a headquarters management system 100 according to this embodiment. The headquarters management system 100 includes a store server 1 of POS systems 100A and 100B built in each retail store, a headquarters server 2, and a first network NW1. The first network NW1 connects each store server 1 and the head office server 2 so as to allow two-way communication. The first network NW1 is typically the Internet. The first network NW1 may be a closed network dedicated to the headquarters management system 100. FIG. The first network NW1 may include a mobile communication network.

The POS systems 100A and 100B of each retail store have the same basic configuration. That is, POS systems 100A and 100B include store server 1, POS terminal 3, and second network NW2. A second network NW2 connects the store server 1 and the POS terminal 3 so as to allow two-way communication. The second network NW2 is typically a LAN (Local Area Network). The second network NW2 may be a wired LAN or a wireless LAN.

The POS terminal 3 is installed at the sales floor of the retail store. The POS terminal 3 mainly has a function of registering product sales data and a function of processing settlement. The store server 1 is installed in a management office or the like of a retail store. The store server 1 mainly has a function of centrally controlling registration processing at each POS terminal 3, and manages the sales, inventory, etc. of the entire store based on the sales data of each product registered at each POS terminal 3. have the function of

In the POS systems 100A and 100B having such a configuration, the store server 1 has a single-item master file 4 and a classification master file 5. FIG. The single item master file 4 is a storage area for storing a plurality of single item records 4R generated for each single item. A single item represents one item of merchandise. The classification master file 5 is a storage area for storing a plurality of classification records 5R generated for each product classification. Classification represents the type of product. Classifications include, for example, food, clothing, daily necessities, home electric appliances, and the like. Classification is not limited to the above items. Also, for example, food may be subdivided into fresh food, processed food, beverage, confectionery, and the like. The same applies to clothing, daily necessities, home electric appliances, and the like.

FIG. 2 is a schematic diagram showing the data structure of the single item record 4R. As shown in FIG. 2, the single item record 4R includes a single item code, a classification code, a single item name, a normal price, and a preferential price for each of the preferential treatment ranks 1 to p. The item code is a unique identification code set for each item. Many products have a product barcode obtained by converting the single product code of the product into a barcode. The classification code is an identification code representing the classification to which the product identified by the corresponding single item code belongs. A unique classification code is set in advance for each classification. The item name and regular price are the name of the product specified by the corresponding item code and the price at the time of regular sale. The preferential treatment ranks 1 to p are ranks for classifying customers from rank "1" to rank "p" according to the store's usage status and the like. The rank "p" is any integer greater than or equal to 2. Rank "p" is higher than rank "1". The preferential price is the price at which the product identified by the corresponding single-item code is sold to customers with corresponding preferential ranks 1 to p. The preferential price is lower than the normal price. The higher the preferential rank, the lower the preferential price. However, the price may be the same between successive preferential ranks.

FIG. 3 is a schematic diagram showing the data structure of the classification record 5R. As shown in FIG. 3, the classification record 5R includes a classification code, a classification name, and a preferential discount rate for each of the preferential treatment ranks 1 to p. The category name is the item name of the category identified by the corresponding category code. The preferential discount rate is the discount rate for selling products belonging to the corresponding classification code to customers with corresponding preferential treatment ranks 1 to p. The higher the preferential treatment rank, the higher the preferential discount rate. However, the discount rate may be the same between consecutive preferential treatment ranks.

Here, the single-item master file 4 and the classification master file 5 are data files storing data to be updated in which the unit price or discount rate is set for each preferential treatment rank in association with the identification code for identifying each product.

Returning to the description of FIG.
The headquarters server 2 is installed in the headquarters which supervises each retail store. The headquarters server 2 has a function of creating a single item update data file 6 and a category update data file 7 and delivering them to the store server 1 of each retail store. The single item update data file 6 stores update data for updating the single item record 4R stored in the single item master file 4 . In the following description, the update data will be referred to as a single product update record 6R. The classification update data file 7 stores update data for updating the classification records 5R stored in the classification master file 5. FIG. In the following description, this update data will be referred to as a classification update record 7R.

The data structure of the single item update record 6R and the classification update record 7R is common. FIG. 4 is a schematic diagram showing the data structure of the single item update record 6R and the classification update record 7R. As shown in FIG. 4, the single-item update record 6R and the classification update record 7R include record type values, codes, preferential treatment type values, and preferential treatment data for each of the preferential treatment ranks 1 to p.

The record type value is a value for identifying whether the record is the single product update record 6R or the classification update record 7R. In this embodiment, the value indicating the single item update record 6R is set to "1", and the value indicating the classification update record 7R is set to "2".

The code is the single item code when the record is the single item update record 6R, and the classification code when the record is the classification update record 7R.

The preferential treatment type value is a value indicating that the preferential treatment data for each of the preferential treatment ranks 1 to p is the preferential treatment price when the record is the single item update record 6R, and the preferential treatment ranks 1 to p when the record is the classification update record 7R. This is a value indicating that the other preferential treatment data is the preferential discount rate. In this embodiment, the preferential treatment type value indicating the preferential price is "1", and the preferential treatment type value indicating the preferential discount rate is "2".

The preferential treatment data for each of the preferential treatment ranks 1 to p is the preferential price when the record is the single item update record 6R, and the preferential discount rate when the record is the classification update record 7R.

If it becomes necessary to modify the data in the single item master file 4 or the classification master file 5 due to a change in the preferential price or the preferential discount rate, the person in charge at the headquarters will use the headquarters server 2 to update the single item update record. Enter data required to construct 6R or Classification Update Record 7R. By doing so, the headquarters server 2 creates the single item update data file 6 or the classification update data file 7 storing the single item update record 6R or the classification update record 7R. The created single-item update data file 6 or classification update data file 7 is distributed from the head office server 2 to the store server 1 of each retail store via the first network NW1 at an appropriate timing. At that time, the single item update data file 6 or the classification update data file 7 is distributed as a data file in CSV format.

The store server 1 performs an error check to confirm the validity of the single item update data file 6 or the classification update data file 7 delivered from the headquarters server 2 . As a result, if an error is detected, the store server 1 executes processing for notifying the content of the error. Here, the store server 1 has a function as an update data confirmation device.

FIG. 5 is a block diagram for explaining the function of the store server 1 as an update data confirmation device. As shown in FIG. 5, the store server 1 has an update data acquisition function 1A, a setting table management function 1B, an update data check function 1C, a master update function 1D and an error notification function 1E.

The update data acquisition function 1A acquires the single item update data file 6 or the classification update data file 7 distributed from the headquarters server 2, which is an external system, via the first network NW1. Then, the update data acquisition function 1A identifies whether the data file acquired from the headquarters server 2 is the single item update data file 6 or the classification update data file 7, and notifies the result to the setting table management function 1B. Also, the update data acquisition function 1A passes the single item update data file 6 or the classification update data file 7 to the update data check function 1C.

The setting table management function 1B manages the setting table 8. FIG. The setting table 8 is a data table in which the order of execution and the details of processing after error detection are set for each error check item for confirming the validity of update data.

FIG. 6 is a schematic diagram showing an example of the setting table 8. As shown in FIG. As shown in FIG. 6, the setting table 8 has areas for describing item names, execution flags, notification flags, continuation flags, and logic names in association with serial numbers starting from "1". In the item name area, item names representing the contents of the error check are written in ascending order from number "1" according to the order in which the error check is executed.

In the execution flag area, 1-bit data for designating whether or not to execute the error check for the corresponding item name is described. In this embodiment, the implementation flag is "1" when specifying to implement an error check, and "0" when specifying not to implement it.

In the notification flag area, 1-bit data for designating the notification method when an error is detected as a result of executing the error check for the corresponding item name is described. In this embodiment, the notification flag is set to "1" when specifying that a pop-up indicating the content of an error should be output and notified when an error occurs, and a list indicating the content of the error should be output and notified after the error check is completed. It is set to "0" when specifying that

In the area of the continuation flag, 1-bit data for setting whether or not to continue the subsequent error check when an error is detected as a result of executing the error check for the corresponding item name is described. In this embodiment, the continuation flag is "1" when specifying to continue the error check, and "0" when specifying not to continue.

In the logic name area, the name of the program in which the logic for executing the error check for the corresponding item name is programmed is described.

Returning to the description of FIG.
The setting table management function 1B receives the notification from the update data acquisition function 1A and changes the implementation flag, notification flag, and continuation flag of the setting table 8. FIG. That is, when the data file acquired from the headquarters server 2 is the single item update data file 6, the setting table management function 1B sets the implementation flag, the notification flag, and the continuation flag to confirm the validity of the single item update data file 6. change to a state suitable for error checking. When the data file obtained from the headquarters server 2 is the classification update data file 7, the setting table management function 1B sets the implementation flag, the notification flag, and the continuation flag to confirm the validity of the classification update data file 7. Change to a state suitable for error checking.

The update data check function 1C executes an error check for confirming the validity of the single item update data file 6 or the classification update data file 7 based on the data in the setting table 8. FIG. Specifically, the update data check function 1C performs error checks on the item names for which the execution flag is set to "1" in ascending order of the serial number. When an error is detected, the update data check function 1C performs error notification processing according to the value of the notification flag. Also, the update data check function 1C determines whether to continue the error check according to the value of the continuation flag.

The master update function 1D updates the single item master file 4 or the classification master file 5 with the data of the single item update data file 6 or the classification update data file 7 whose validity is recognized by the update data check function 1C.

The error notification function 1E uses the output device 9 to perform processing for notifying that an error has been detected by the update data check function 1C. Output device 9 is typically a display device. The output device 9 may combine a display device and a print device or an audio output device. The output device may be a communication device for notifying information terminals such as smartphones and tablet terminals of data indicating the content of notification.

Here, the contents of the error check specified by the item names shown in FIG. 6 will be described.
The item name "number of records" with the serial number "1" indicates whether the number of single item update records 6R or classification update records 7R saved in the single item update data file 6 or classification update data file 7 is "0". Represents the process of checking whether The single item update data file 6 or the classification update data file 7 with the number of records of "0" is determined to be an error.

The item name "excess number of single items" with the serial number "2" indicates processing for checking whether or not the number of single item update records 6R stored in the single item update data file 6 exceeds the upper limit. A single-item update data file 6 in which the number of single-item update records 6R exceeds the upper limit is determined to be an error. The upper limit value is an arbitrary value determined by the number of records in the single item master file 4 or the like.

The item name "exceeding the number of classifications" with the serial number "3" indicates processing for checking whether or not the number of classification update records 7R stored in the classification update data file 7 exceeds the upper limit. A classification update data file 7 in which the number of classification update records 7R exceeds the upper limit is determined as an error. The upper limit value is an arbitrary value determined by the number of records in the classification master file 5 or the like.

The item name "number of digits" with the serial number of "4" represents the process of checking the number of digits for each item of the single item update record 6R or the classification update record 7R. A single-item update record 6R or a classification update record 7R in which at least one item has more digits is determined to be an error. The number of digits is an arbitrary value determined for each data of record type value, code, preferential treatment type value, and preferential treatment ranks 1 to p.

The item name "record type difference" with the serial number "5" indicates processing for checking the record type value included in the single item update record 6R or the classification update record 7R. In the case of this embodiment, among the single-item update records 6R included in the single-item update data file 6, a record whose record type value is not "1" is determined to be an error. Similarly, among the classification update records 7R included in the classification update data file 7, any record whose record type value is not "2" is determined to be an error.

The item name "no master" with the serial number "6" indicates whether or not the single item or category record specified by the single item update record 6R or the classification update record 7R exists in the single item master file 4 or the classification master file 5. Represents the process of checking the . A single item update record 6R for a single item that does not exist in the single item master file 4 is determined to be an error. Similarly, a classification update record 7R for a classification that does not exist in the classification master file 5 is determined to be an error.

The item name "code duplication" with the serial number "7" indicates that the single item code or classification code is duplicated in the single item update record 6R or the classification update record 7R saved in the single item master file 4 or the classification master file 5. Represents the process of checking whether there are multiple records. A single-item update record 6R whose single-item code overlaps with another single-item update record 6R is determined to be an error. Similarly, a classification update record 7R whose classification code overlaps with another classification update record 7R is determined to be an error.

The item name "non-numerical" with the serial number "8" indicates processing for checking whether or not the data is a numerical value for each item in the single item update record 6R or the classification update record 7R. A single item update record 6R or a category update record 7R in which data of at least one item is not a numerical value is determined as an error.

The item name "format difference" with the serial number "9" represents the process of checking the format of the single item update record 6R or the classification update record 7R. A single product update record 6R or a classification update record 7R having a data structure different from the format shown in FIG. 5 is determined to be an error.

The item name "set 0 yen" with the serial number "10" represents the process of checking whether "0" is set in the data for each of the preferential treatment ranks 1 to p in the single item update record 6R. A single-item update record 6R in which at least one preferential rank data is "0" is determined to be an error.

The item name "price setting error" with the serial number "11" represents the process of checking whether or not the magnitude relationship of the data classified by preferential treatment ranks 1 to p contained in the single item update record 6R is correct. As described above, among the preferential treatment ranks 1 to p, rank "p" is higher than rank "1", and the higher the preferential treatment rank, the lower the price. However, it does not straddle the fact that the price is the same between successive preferential treatment ranks. A single-item update record 6R in which the magnitude relationship of the data for each preferential rank 1 to p does not satisfy such conditions is determined to be an error.
The item name "discount rate setting error" with the serial number "12" represents the process of checking whether or not the magnitude relationship of the data classified by preferential treatment ranks 1 to p contained in the classification update record 7R is correct. As described above, among the preferential treatment ranks 1 to p, the rank "p" is higher than the rank "1", and the higher the preferential treatment rank, the larger the preferential discount rate. However, it does not straddle the fact that the discount rate is the same between consecutive preferential treatment ranks. A classification update record 7R in which the magnitude relationship of the data of the preferential ranks 1 to p does not satisfy such conditions is determined as an error.
The item name "unauthorized discount rate" with the serial number "13" represents the process of checking whether or not the data for each preferential treatment rank 1 to p contained in the classification update record 7R are all the same value. A classification update record 7R in which the data of all the preferential ranks 1 to p have the same value is determined as an error.

FIG. 7 is a block diagram showing the main circuitry of the store server 1. As shown in FIG. The store server 1 comprises a processor 11 , main memory 12 , auxiliary storage device 13 , clock 14 , first communication interface 15 , second communication interface 16 , input device 17 , display device 18 and system transmission line 19 . The system transmission line 19 includes an address bus, a data bus, control signal lines and the like. The store server 1 connects the processor 11 , the main memory 12 , the auxiliary storage device 13 , the clock 14 , the first communication interface 15 , the second communication interface 16 , the input device 17 and the display device 18 to the system transmission line 19 . In the store server 1, a computer is composed of a processor 11, a main memory 12, an auxiliary storage device 13, and a system transmission line 19 connecting them.

The processor 11 corresponds to the central portion of the computer. The processor 11 controls each part to implement various functions of the store server 1 according to an operating system or application program. The processor 11 is, for example, a CPU (Central Processing Unit).

The main memory 12 corresponds to the main memory portion of the computer. Main memory 12 includes a non-volatile memory area and a volatile memory area. The main memory 12 stores an operating system or application programs in a non-volatile memory area. Application programs include programs programmed with logic to perform error checking. The main memory 12 may store data necessary for the processor 11 to execute processing for controlling each part in a non-volatile or volatile memory area. The main memory 12 uses a volatile memory area as a work area in which data is appropriately rewritten by the processor 11 . The non-volatile memory area is, for example, ROM (Read Only Memory). A volatile memory area is, for example, a RAM (Random Access Memory).

The auxiliary storage device 13 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (Electric Erasable Programmable Read-Only Memory), HDD (Hard Disc Drive), SSD (Solid State Drive), or the like can be the auxiliary storage device 13 . The auxiliary storage device 13 stores data used by the processor 11 in performing various types of processing, data created by processing in the processor 11, and the like. The auxiliary storage device 13 may store the above application programs.

The clock 14 measures the date and time as a time information source for the store server 1 . The processor 11 acquires the date and time kept by the clock 14 as the current date and time.

The first communication interface 15 transmits and receives data according to a predetermined communication protocol with the headquarters server 2 connected via the first network NW1. The second communication interface 16 transmits and receives data according to a predetermined communication protocol with each POS terminal 3 connected via the second network NW2.

The input device 17 is a device used for data input. A keyboard, scanner, or the like corresponds to the input device 17 . The display device 18 is a device used for displaying data. A liquid crystal display, an organic EL (electroluminescence) display, or the like corresponds to the display device 18 . A touch panel may be provided in the store server 1 as a device that serves both as the input device 17 and the display device 18 .

In the store server 1 having such a configuration, the display device 18 functions as the output device 9 . A single-item master file 4, a classification master file 5, and a setting table 8 are stored in the auxiliary storage device 13. FIG. The update data acquisition function 1A, the setting table management function 1B, the update data check function 1C, the master update function 1D and the error notification function 1E are executed by the processor 11 according to the control program stored in the main memory 12 or the auxiliary storage device 13. It is realized by executing As memory areas necessary for executing this information processing, the store server 1 includes an error buffer 121 in the main memory 12, a counter memory 122 for counting the number n, and a flag memory for storing a 1-bit first flag F1. 123, forming a flag memory 124 for storing a 1-bit second flag F2 and a flag memory 125 for storing a 1-bit third flag F3. The store server 1 also stores a single-item implementation pattern table 131 and a classification implementation pattern table 132 in the auxiliary storage device 13 . The uses of the error buffer 121, the counter memory 122, the flag memories 123 to 125, the single-item implementation pattern table 131, and the classification implementation pattern table 132 will be clarified in the explanation of operations to be given later.

8 and 9 are flow charts showing main procedures of information processing executed by the processor 11 of the store server 1 according to the control program. The operation of the store server 1 as an update data confirmation device will be described below with reference to the drawings. In addition, the content of the operation|movement demonstrated below is an example. The procedure and contents are not particularly limited as long as similar results can be obtained.

When the time measured by the clock 14 reaches a preset time, the processor 11 confirms whether or not the single item update data file 6 or the classification update data file 7 has been delivered from the headquarters server 1 . After confirming that the single item update data file 6 or the classification update data file 7 has been delivered via the first network NW1, the processor 11 starts the processing of the procedures shown in the flow charts of FIGS.

The processor 11 acquires the data file received via the first communication interface 15 as Act1. Then, the processor 11 identifies whether the data file is the single item update data file 6 or the classification update data file 7 as Act 2 . Here, the processor 11 implements the update data acquisition function 1A in cooperation with the first communication interface 15 through the processing of Act1 and Act2. That is, the processor 11 has acquisition means.

In Act2, the processor 11 determines YES when the single item update data file 6 is acquired, and proceeds to Act3. The processor 11 selects the single item execution pattern table 131 from the auxiliary storage device 13 as Act3. Then, the processor 11 changes the execution flag, the notification flag, and the continuation flag of the setting table 8 with the data of the single item execution pattern table 131 .

In Act2, the processor 11 determines NO when the classification update data file 7 is acquired, and proceeds to Act4. The processor 11 selects the classification execution pattern table 132 from the auxiliary storage device 13 as Act4. Then, the processor 11 changes the execution flag, the notification flag, and the continuation flag of the setting table 8 with the data of the classification execution pattern table 132 .

FIG. 10 shows an example of the single item implementation pattern table 131 for the setting table 8 shown in FIG. 6, and FIG. 11 shows an example of the classification implementation pattern table 132. As shown in FIG. As shown in FIGS. 10 and 11, the single item implementation pattern table 131 and the classification implementation pattern table 132 match the setting table 8 with the logic name item removed. In the single-item implementation pattern table 131, the execution flags associated with the item names "excessive number of classifications", "wrong discount rate setting", and "illegal discount rate", which are unnecessary for error checking of the single-item update data file 6, are set to "0". ”, and the execution flags of the other items are set to “1”. In the single-item execution pattern table 131, of the items whose execution flag is "1", the notification flags of the item names "number of records", "excess number of single items" and "wrong record type" are set to "1", and the remaining items are is set to "0". In the single-item implementation pattern table 131, among the items whose implementation flags are set to "1", the continuation flags of the item names "number of records" and "excess number of single items" are set to "0", and the continuation flags of the remaining items are set to "1". ”.

On the other hand, in the classification execution pattern table 132, the execution flags associated with the item names "excess number of single items", "set at 0 yen" and "erroneous price setting" which are unnecessary for the error check of the classification update data file 7 are set to "0". ”, and the execution flags of the other items are set to “1”. In the classification execution pattern table 132, of the items whose execution flags are set to "1", the notification flags of the item names "number of records", "exceeded number of classifications", and "wrong record type" are set to "1", and the remaining items are is set to "0". Further, the classification execution pattern table 132 sets the continuation flags of the item names "number of records" and "exceeding the number of classifications" among the items whose execution flags are "1" to "0", and sets the continuation flags of the remaining items to "0". 1”.

Here, the processor 11 implements the setting table management function 1B in cooperation with the auxiliary storage device 13 through the processing of Act3 and Act4. That is, the processor 11 has management means and change means.

After completing the processing of Act3 or Act4, the processor 11 clears the error buffer 121 as Act5. The processor 11 also resets the number n of the counter memory 122 to "0" as Act6.

Next, the processor 11 counts up the number n of the counter memory 122 by "1" as Act7. Then, the processor 11 confirms whether or not the number n is equal to or less than the maximum value N as Act8. The maximum value N is the maximum value of serial numbers set in the setting table 8 . That is, in this embodiment, the maximum value N is "13".

If the number n is equal to or less than the maximum value N, the processor 11 determines YES in Act8 and proceeds to Act9. The processor 11 sets the value of the execution flag associated with the number n of the setting table 8 as the value of the first flag F1 of the flag memory 123 in Act9. Similarly, the processor 11 sets the value of the notification flag associated with the number n of the setting table 8 as the value of the second flag F2 of the flag memory 124 in Act10. The processor 11 also sets the value of the continuation flag associated with the number n of the setting table 8 in Act 11 as the value of the third flag F3 of the flag memory 125 .

The processor 11 checks the value of the first flag F1 as Act12. When the value of the first flag F1 is "1", the execution flag associated with the number n of the setting table 8 designates that the error check for the corresponding item name is to be executed. The processor 11 determines YES in Act12 and proceeds to Act13.

The processor 11 selects the logic name associated with the number n of the setting table 8 as Act13. Then, in Act 14, the processor 11 starts error checking of the single item update data file 6 or the classification update data file 7 acquired in Act 1 according to the program of the logic name.

In Act 15, the processor 11 confirms whether or not the error check has ended. If the error check has not been completed, the processor 11 determines NO in Act15 and proceeds to Act16. The processor 11 confirms whether or not an error is detected in Act16. If no error is detected, the processor 11 determines NO in Act16 and returns to Act15. Therefore, the processor 11 waits until the error check is finished or an error is detected by the processing of Act15 and Act16.

In this standby state, when the error check ends, the processor 11 determines YES in Act15 and returns to Act7. That is, the processor 11 further counts up the number n of the counter memory 122 by "1". If the number n is equal to or less than the maximum value N, the processor 11 executes Act9 to Act16 in the same manner as described above.

If an error is detected in the standby states of Act15 and Act16, the processor 11 determines YES in Act16 and proceeds to Act17 in FIG. The processor 11 checks the value of the second flag F2 as Act17. When the value of the second flag F2 is "1", the notification flag associated with the number n in the setting table 8 designates outputting a pop-up indicating the content of the error. The processor 11 determines YES in Act17 and proceeds to Act18. In Act18, the processor 11 causes the display device 18 to display a pop-up image indicating the content of the error.

FIG. 12 is a schematic diagram showing an example of the popup image SC1. As shown in FIG. 12, the pop-up image SC1 displays a message M1 representing error details and an OK button BT1. After confirming the message M1, the operator of the store server 1 inputs the OK button BT1 through the input device 17. FIG.

The processor 11 that causes the display device 18 to display the pop-up image SC1 waits for an input of the OK button BT1 as Act19. When the OK button BT1 is input, the processor 11 determines YES in Act19 and proceeds to Act21.

On the other hand, when the value of the second flag F2 is "0", the notification flag associated with the number n of the setting table 8 designates output of a list indicating error details. The processor 11 determines NO in Act17 and proceeds to Act20. The processor 11 stores the data in which the error was detected in Act 20, ie, the data of the single item update record 6R or the classification update record 7R, in the error buffer 121. FIG. After that, the processor 11 proceeds to Act21.

In this way, the processor 11 advances to Act21 when the OK button BT1 of the popup image SC1 is input in Act19 or the error data is stored in the error buffer 121 in Act20. The processor 11 checks the value of the third flag F3 as Act21. When the value of the third flag F3 is "1", the continuation flag associated with the number n in the setting table 8 designates continuation of the error check. The processor 11 determines YES in Act21, and proceeds to Act15 in FIG. That is, the processor 11 continues the error check and waits for the error check to end or for an error to be detected.

On the other hand, when the value of the third flag F3 is "0", the continuation flag associated with the number n in the setting table 8 specifies not to continue the error check. The processor 11 determines NO in Act21, and proceeds to Act22 in FIG.

In this way, the processor 11 performs an error check on the single item update data file 6 or the classification update data file 7 in ascending order of the serial numbers set in the setting table 8 . Then, when an error is detected, the processor 11 causes the display device 18 to display a pop-up image SC1 indicating the content of the error according to the value of the notification flag. Alternatively, the processor 11 stores in the error buffer 121 the single product update record 6R or the classification update record 7R in which the error was detected.

Here, if the value of the continuation flag set for the error check item in which an error is detected is "0", the error check is not continued. As described above, the processor 11 determines NO in Act21 of FIG. 9, and proceeds to Act22 of FIG.

On the other hand, when the value of the continuation flag is "1", the error check is continued. In this way, the number n exceeds the maximum value N when the error check for all items is completed. That is, the processor 11 determines NO in Act8, and proceeds to Act22.

The processor 11 outputs an error list based on the data of the single item update record 6R or the classification update record 7R stored in the error buffer 121 as Act22. Specifically, the processor 11 creates an error list image listing the codes included in the single item update record 6R or the classification update record 7R, the item name or classification name specified from the code, and the data representing the error content. Display on the display device 18 .

FIG. 13 is a schematic diagram showing an example of the error list image SC2 when the single item update data file 6 is checked for errors. The error list image SC2 displays an error list L1 listing codes, names, and causes of errors, an end button BT2, and an enter button BT3. In addition, information "single item master update" indicating that the data file to be updated by the single item update data file 6 is the single item master file 4 is also displayed. After confirming the error list L1, the operator determines whether or not to update the single item master file 4. FIG. Then, when executing, the operator inputs the decision button BT3 via the input device 17. If not, the operator presses the end button BT2 via the input device 17. FIG.

Incidentally, in the error list image SC2 when the classification update data file 7 is checked for errors, the information "single item master update" becomes "classification master update". Further, when the single item update record 6R or the classification update record 7R is not stored in the error buffer 121, the error list L1 is blank. Alternatively, the error list L1 is omitted.

The processor 11 that has controlled the output of the error list confirms in Act 23 whether or not the decision button BT3 has been input. When the end button BT2 is pressed instead of the confirm button BT3, the processor 11 determines NO in Act 23 and terminates the processing of the procedure shown in the flow charts of FIGS.

When the enter button BT3 is input, the processor 11 determines YES in Act23 and proceeds to Act24. The processor 11 executes a process for updating the update target data with the update data as Act24. That is, when the single item update data file 6 has been received from the head office server 2 as update data, the processor 11 executes processing for updating the data of the single item master file 4 with the data of the valid single item update record 6R. . If the classification update data file 7 has been received from the headquarters server 2 as the update data, the processor 11 executes processing for updating the data of the classification master file 5 with the data of the valid classification update record 7R.
With this, the processor 11 completes the processing of the procedures shown in the flow charts of FIGS.

Here, the processor 11 implements the update data check function 1C through the processing of Act5 to Act16. Further, the processor 11 implements the error notification function 1E by executing the processes of Act17 to Act22. Also, the processor 11 realizes the master update function 1D by executing the processes of Act23 and Act24. That is, the processor 11 comprises execution means.

In the store server 1 operating in this manner, when the single item update data file 6 is delivered from the headquarters server 2, the single item implementation pattern table 131 shown in FIG. value is changed. First, since the value of the execution flag of number "1" is "1", an error check for the item name "number of records" is executed. As a result, when an error is detected, a pop-up image indicating the content of the error is displayed on the display device 18 because the value of the notification flag numbered "1" is "1". Also, since the value of the execution flag of number "1" is "0", the error check ends.

If no error is detected in the error check for the item name "number of records", the value of the execution flag of number "2" is "1", so the error check for the item name "number of single items exceeded" is executed. Also in this case, the value of the notification flag is "1" and the value of the execution flag is "0", so when an error is detected, the pop-up image SC1 is displayed and the error check ends.

If no error is detected, the value of the execution flag of number "3" is "0", so the error check for the item name "excessive number of classifications" is not executed.

Subsequently, since the value of the execution flag of number "4" is "1", the error check for the item name "number of digits" is executed. In this case, since the value of the notification flag is "0", error data is stored in the error buffer 121 when an error is detected. Since the value of the execution flag is "1", the error check continues even if an error is detected.

When the error check for the item name "Number of Digits Wrong" is completed, the error check for the item name "Record Type Wrong" is executed because the execution flag value of number "5" is "1". In this case, since the value of the notification flag is "1", when an error is detected, a pop-up image showing the content of the error is displayed on the display device 18. FIG. Since the value of the execution flag is "1", the error check continues even if an error is detected.

After that, the error checks for the item names corresponding to the numbers "6", "7", "8", "9", "10" and "11" are sequentially executed. Since the values of the notification flags corresponding to these numbers are all "0", error data is stored in the error buffer 121 when an error is detected. Since the value of the execution flag is "1", the error check continues even if an error is detected.

On the other hand, the execution flag values corresponding to numbers "12" and "13" are both "0". An error list image SC2 including an error list L1 is displayed based on the error data stored in . Here, when the operator touches the confirmation button BT3, the data in the single item master file 4 is updated with the update data in the single item update data file 6. FIG.

Next, when the classification update data file 7 is delivered from the headquarters server 2, the values of the execution flag, the notification flag, and the continuation flag of the setting table 8 are changed by the classification execution pattern table 132 shown in FIG. First, since the value of the execution flag of number "1" is "1", an error check for the item name "number of records" is executed. As a result, when an error is detected, a pop-up image indicating the content of the error is displayed on the display device 18 because the value of the notification flag numbered "1" is "1". Also, since the value of the execution flag of number "1" is "0", the error check ends.

If no error is detected in the error check for the item name "number of records", the error check for the item name "excess number of single items" is not executed because the execution flag value of number "2" is "0".

Subsequently, since the value of the execution flag of number "3" is "1", an error check for the item name "exceeded number of classifications" is executed. Also in this case, the value of the notification flag is "1" and the value of the execution flag is "0", so when an error is detected, the pop-up image SC1 is displayed and the error check ends.

If no error is detected, the value of the execution flag of number "4" is "1", so the error check for the item name "number of digits" is executed. In this case, since the value of the notification flag is "0", error data is stored in the error buffer 121 when an error is detected. Since the value of the execution flag is "1", the error check continues even if an error is detected.

When the error check for the item name "Number of Digits Wrong" is completed, the error check for the item name "Record Type Wrong" is executed because the execution flag value of number "5" is "1". In this case, since the value of the notification flag is "1", when an error is detected, a pop-up image showing the content of the error is displayed on the display device 18. FIG. Since the value of the execution flag is "1", the error check continues even if an error is detected.

After that, the error checks for the item names corresponding to the numbers "6", "7", "8" and "9" are sequentially executed. Since the values of the notification flags corresponding to these numbers are all "0", error data is stored in the error buffer 121 when an error is detected. Since the value of the execution flag is "1", the error check continues even if an error is detected.

On the other hand, the values of the execution flags corresponding to numbers "10" and "11" are "0". An error check for the name "discount rate setting error" is performed. Subsequently, an error check for the item name "unauthorized discount rate" of number "13" is also executed.

Thus, when the error check for the item name "unauthorized discount rate" is completed, an error list image SC2 including the error list L1 is displayed based on the error data stored in the error buffer 121. FIG. Here, when the operator touches the confirmation button BT3, the data in the classification master file 5 are updated with the update data in the classification update data file 7. FIG.

As described above, according to the present embodiment, the preferential prices for each of the preferential ranks 1 to p of the single-item record 4R set in the single-item master file 4 are changed to the preferential prices of the single-item update record 6R saved in the single-item update data file 6. The validity of the single item update data file 6 can be efficiently confirmed in the order of the error check items set in the setting table 8 before updating with the data for each of 1 to p. Similarly, the preferential discount rates for each of the preferential ranks 1 to p of the classification record 5R set in the classification master file 5 are obtained by using the data for each of the preferential ranks 1 to p of the classification update record 7R saved in the classification update data file 7. Before updating, the correctness of the classification update data file 7 can be efficiently confirmed in the order of the error check items set in the setting table 8. - 特許庁

Then, if an error is detected as a result of the error check, for each error check item, interrupt the error check and notify that an error has been detected, or do not notify until the error check is completed, and end The value of the notification flag in the setting table 8 can be used to specify whether the list of error data should be displayed and notified when the error data is detected. Therefore, there is an advantage that a notification method can be easily designed in consideration of the content of error check.

In addition, when an error is detected, whether to end or continue the error check at that point can be specified by the value of the continuation flag in the setting table 8. FIG. Therefore, there is also the advantage that it is possible to easily specify whether or not to continue the error check in consideration of the contents of the error check.

Also, regarding the error check execution items set in the setting table 8, when the single item update data file 6, which is the update data of the single item master file 4, is obtained, and when the classification update data file, which is the update data of the classification master file 5, is acquired, 7 can be changed depending on the value of the execution flag in the setting table 8 . Therefore, since unnecessary error checks are not executed, the validity of the single item update data file 6 or the classification update data file 7 can be confirmed more efficiently.

Although the embodiment of the update data confirmation device capable of efficiently confirming the validity of the update data before updating the data to be updated with the update data has been described above, the embodiment is not limited to this. .

In the above-described embodiment, the acquisition means acquires the single item update data file 6 or the classification update data file 7 distributed from the headquarters server 2 via the first communication interface 15 . Regarding this point, for example, the single item update data file 6 or the classification update data file 7 created by the head office server 2 is recorded in a computer-readable portable recording medium, and the recording medium connected to the store server 1 is recorded. The single item update data file 6 or the classification update data file 7 may be acquired by reading the data on the recording medium with a reading device.

In the above embodiment, the case where the store server 1 has the single-item master file 4 and the classification master file 5 is exemplified. As another embodiment, any one POS terminal 3 may have the single-item master file 4 and the classification master file 5 . In this case, the POS terminal 3 functions as an update data confirmation device.

In the above embodiment, the data to be updated is the preferential price or preferential discount rate for each preferential rank 1 to p, which is stored for each item code or each classification code in the single item master file 4 and the classification master file 5 . Data to be updated is not limited to this. For example, when adopting a sales form in which the price or discount rate is changed according to the number of days that have passed since the date of manufacture, the discount price or discount rate for each number of days that have passed will be the data to be updated. Also, in the case of a sales form in which the price or discount rate is changed according to the customer segment, such as a student discount or senior discount, the discount price or discount rate for each customer segment is the data to be updated.

In the above embodiment, the store server 1 preliminarily stores the control program in the main memory 12 or the auxiliary storage device 13 . Regarding this point, for example, the control program may be installed in the store server 1 before executing the error check. In this case, the control program can be installed in the store server 1 by recording it on a removable recording medium or by communicating via a network. The recording medium may be of any form, such as a CD-ROM, memory card, etc., as long as it can store the program and is readable by the store server 1 .

Additionally, while several embodiments of the invention have been described, these embodiments have been presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and modifications can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope of the invention, and are included in the scope of the invention described in the claims and equivalents thereof.

REFERENCE SIGNS LIST 1 store server 1A update data acquisition function 1B setting table management function 1C update data check function 1D master update function 1E error notification function 2 headquarters server 3 POS terminal 4 Single item master file 5 Classification master file 6 Single item update data file 7 Classification update data file 8 Setting table 9 Output device 11 Processor 12 Main memory 13 Auxiliary storage device 14 Clock 15 First communication interface 16 Second communication interface 17 Input device 18 Display device 121 Error buffer 131 Single item implementation pattern table 132 Classification implementation pattern table.

Claims (6)

an acquisition means for acquiring a data file storing update data for updating data to be updated;
a management means for managing a setting table in which an execution order and details of processing after error detection are set for each error check item for confirming the validity of the update data;
execution means for executing an error check for the item according to the execution order set in the setting table, and executing a process corresponding to the processing content set in the setting table for the item when an error is detected; ,
An update data confirmation device comprising: The processing content includes processing for notifying when an error is detected,
The execution means detects the error in the process of executing the error check of the item, and notifies the processing contents set in the setting table for the item at the time when the error is detected. 2. The update data confirmation device according to claim 1, wherein if it is processing, it interrupts said error check and notifies that an error has been detected. the processing content includes processing for displaying a list of the update data in which an error is detected;
The execution means detects the error in the process of executing the error check of the item, and the processing content set in the setting table for the item is changed to the update data in which the error is detected. 2. The process of displaying a list, according to claim 1, wherein the update data in which an error is detected is stored in a buffer, and the update data stored in the buffer is displayed in a list when the error check is finished. update data confirmation device. The processing content includes a type for setting whether to end or continue the error check when the error is detected,
The execution means confirms the type when the error is detected, terminates the error check at that time if the setting is to end the error check, or terminates the error check if the setting is to continue. 4. The update data confirmation device according to claim 2 or 3, continuing. The setting table includes information specifying whether to execute an error check for each item,
changing means for changing the information based on the data file acquired by the acquiring means;
The update data verification device according to claim 1, further comprising: A computer of an update data confirmation device for confirming the validity of update data for updating data to be updated,
acquisition means for acquiring a data file storing update data for updating the data to be updated;
a management means for managing a setting table in which an order of execution and details of processing after error detection are set for each error check item for confirming the validity of the update data;
Execution means for executing an error check for the item according to the execution order set in the setting table, and executing a process corresponding to the processing content set in the setting table for the item when an error is detected;
A control program for functioning as

Images