JP2009009174A - Method for updating master data in pos system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent the master data table of a store server from being updated with unauthorized data in updating master data in a POS system. <P>SOLUTION: In updating merchandise data about each piece of merchandise stored in a maser data table constructed in a store server configuring a POS system for each merchandise based on received update data configured of a plurality of item data about each merchandise, whether or not each of a plurality of item data is present within the range of predetermined update conditions is determined for each of the update data of each merchandise, and when all the item data are present within the update conditions, it is determined that the received update data are authorized data about the merchandise, and when at least one item data are beyond the range of the update conditions, it is determined that the received update data are unauthorized data. As for the unauthorized data, a log file is generated. Only as for merchandise whose update are determined to be authorized data, the master data table is updated. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a method for updating master data in a POS system, and in particular, a plurality of items for each product that has received product data for each product stored in a master data table constructed in a store server constituting the POS system. The present invention relates to a master data updating method in a POS system that updates each product based on update data composed of data.

  At convenience stores, products change frequently. While new products are introduced one after another, there are many products that will be discontinued. In addition, because popular products change every day, there are a wide variety of products delivered every day.

  A POS system at a convenience store includes a master data table of a store server, and stores product data of products handled at the store as master data.

  The delivered products are each inspected by reading the barcode attached to the products with a barcode reader, collating with the master data table.

  For this reason, before delivery of goods, it is necessary to update the master data of the said store server corresponding to the delivered goods.

  The master data is updated by update data distributed from the host vendor to the store. This update data includes PLU (Price Lookup) data, a flight code, a company code, and a common company code for each product for all products delivered to the store.

  Patent Document 1 describes a technique for updating a PLU file in a POS system. In Patent Document 1, a plurality of individual store PLU master files corresponding to each store are constructed in the center device, and the center device further includes a common product master file in response to a PLU correction request from each store. The personal store PLU master file is corrected while referring to the product master file, and the corrected portion is transmitted to the corresponding POS device of the store. The in-store POS device captures the received corrected portion and stores the PLU file in itself. That corrects or updates is described.

JP 2000-76550 A

  By the way, in the case where the update data from the host vendor mentioned above is so-called illegal data, if this illegal data is updated as master data of the store server, problems such as malfunction of the POS system or business stoppage in business. Will occur. In other words, because of illegal data for some products, the operation of the entire POS system may be affected.

  Therefore, an object of the present invention is to provide a master data updating method in a POS system that can prevent a master data table of a store server from being updated with unauthorized data.

  Means for solving the above-mentioned problems in the present invention comprises a plurality of item data for each product that has received product data for each product stored in a master data table constructed in a store server constituting the POS system. In the master data update method in the POS system for updating for each product based on the update data, it is determined whether or not a plurality of item data is within a predetermined update condition range for the received update data for each product. When the item data is within the update condition, it is determined that the received update data is the correct data for the product, and when at least one item data is outside the range of the update condition, the received update data Only for the process of determining that the data is illegal and for products that are determined to be correct A step of updating the master data table based on the new data, a method of updating the master data in the POS system, characterized in that it and a process for generating a log file for the incorrect data.

  According to the master data update method in the POS system according to the present invention, it is determined that all the item data constituting the update data does not satisfy the predetermined update condition, and the update is based on the incorrect data in the update process. Will not affect other product data that is updated with genuine data, and the status of this update will be recorded in the log file created during the log generation process. Has the effect that can be performed quickly.

  Embodiments of the master data updating method in the POS system according to the present invention will be described below.

  FIG. 1 is a block diagram showing a POS system in which a master data updating method according to an embodiment is executed. In this example, the POS system 100 is formed by connecting a store 10 and a host vendor 20 via a line 30. A store server 200 is disposed in the store 10, and a plurality of POS terminals 300 are connected to the store server 200 via a line 310. The host vendor 20 is also provided with a host server 400 that sends update data to the store server 200 via the line 30.

  In such a POS system 100, the store server 200 in the store 10 has the following configuration. FIG. 2 is a block diagram showing the configuration of the store server. The store server 200 has a process control unit 210 that performs an update process of the store server 200, a master data table 220 that stores product data in the store, and conditions for determining whether the update data from the host server 400 is correct or incorrect. An update condition storage unit 230 for storing, a log file storage unit 240 for storing an update history, and a first work table 251 and a second work table 252 for determining whether a classification item is correct or incorrect among update data. Are generated, and a registry area 260 that stores data about which item data of update data is to be updated.

  The processing control unit 210 includes a determination unit 211 that determines whether the update data is correct / incorrect, a work table creation unit 212 that creates the first work table 251 and the second work table 252 in the work table area 250, and maintenance. A data update unit 213 and a log generation unit 214 are provided. Each of these units is realized by executing a program with a computer including a CPU, a ROM, a RAM, and the like.

  The master data table 220 stores product data for products placed in the store 10, and the product data includes item data such as PLU (price look-up) data, flight codes, company codes, and common items. Stores data such as company code, major classification, medium classification, and minor classification product classification data, maintenance date, headquarter selling price, tax classification, and the like.

The update data from the host server 400 includes the following item data for each product.
(1) Application date range 8-digit data indicating the application date (2) Order start date 8-digit data indicating the order start date (3) Order stop start date 8-digit data indicating the order stop start date (4) Ordering Stop end date 8 digit data indicating order stop end date (5) Order closing date for event order 8 digit data indicating order closing date for event order (6) Discount start date 8 digit data indicating discount start date (7) Discount end date 8-digit data indicating the discount end date (8) Number of lots / items entered Data indicating the number of lots indicating the ordering unit of products and the number of items received in case products (9) Store arrival / departure number No. Data indicating how many flights (eg 1-3)
(10) Flight No. No. of stool Data indicating how many flights (eg 1-3)
(11) PLU data 14-digit data indicating the PLU data of the product (12) Own code Unique code for managing the product at the store 14-digit data (13) Common in-house code Multiple in-house codes such as flight products are bundled 14-digit code (14) classification code 3-digit major classification code, 3-digit middle classification, product classification code consisting of 3-digit minor classification The update condition storage unit 230 stores update conditions at the time of update Has been. As the date data for judging update data including date, “xxx × xxx × xxx” indicating xxxxxx year xx month xx day (for example, future date and time that cannot be updated) is stored. Has been. In addition, the update conditions for the lot / entry number data are “0” indicating a quantity of 0, a flight number. As for, the number of flights of goods brought into the store for one day “1 to 3” is stored. The determination unit 211 of the process control unit 210 determines whether the item data of the update data meets this update condition.

  In the POS system 100 according to this example, the master data table 220 is updated in the following procedure. FIG. 3 is a flowchart showing a procedure for updating the master data table.

  At a predetermined timing, store server 200 first receives update data from host server 400 (step ST1). When data about all the products is received and stored (step ST2), the determination unit 211 determines whether the product data is correct or incorrect (step ST3).

  At this time, for normal product data, the determination unit 211 refers to the update condition storage unit 230 or compares item data in the product data to determine whether the product is correct or incorrect. The unit 211 uses the work table creation unit 212 to create the first work table 251 and the second work table 252 in the work table area 250, and makes a determination using the first work table 251 and the second work table 252. I do.

If the determination unit 211 detects unauthorized data, the log generation unit 214 stores the unauthorized data in the log file storage unit 240 (step ST4). Then, the maintenance data updating unit 213 excludes illegal data from the update data (step ST5), and updates the master data table 220 with the remaining main data (step ST6). Thereafter, necessary processing such as correction is performed with reference to the illegal data stored in the log file storage unit 240 (step ST7).
Hereinafter, the determination process of the determination unit 211 will be described in detail. In this example, processing is performed according to the record classification = 1 or 2 classification of master maintenance single item addition / change data. The process control unit 210 first determines whether to obtain a system option and make a determination. Since there may be a user who cannot register sales at all when the determination is made, the user can select not to perform the determination process.
This selection follows the setting made in the field name VASC single item maintenance consistency check of TC_SYS_CTL_TBL (system management table).

  Next, each registry in the registry area 260 is acquired to determine whether it is necessary to determine each item data. For example, the registry key in the registry area is set as follows.

¥ VHONLCTR ¥ MATCHK1 When there is the same flight with the same product code ¥ VHONLCTR ¥ MATCHK2 When the number of lots and entering is “0” ¥ VHONLCTR ¥ MATCHK3 Is a number other than 1 to 3 ¥ VHONLCTR ¥ MATCHK4 Flight No. Is a number other than 1 to 3 ¥ VHONLCTR ¥ MATCHK5 And flight No. \ VHONLCTR \ MATCHK6 When there are multiple records with the same company code and different common product codes. \ VHONLCTR \ MATCHK7 Different classification codes are linked to the products linked with the common product code. In the case where the minimum order quantity> the maximum order quantity, the determination unit 211 performs the following determination based on the setting of the registry area 260. The reason for the error is as follows, for example.
(1) Application date range error (2) Order start date range error (3) Order stop start date range error (4) Order stop end date range error (5) Special order order closing date range error (6) Discount start date range Error (7) Discount end date range error (8) Lot / entry number 0 error (9) Store arrival number Range error (10) Flight No. Range error (11) Store arrival No. Flight No. Mismatch error (12) Minimum order quantity> Maximum order quantity error (13) Same common product same flight error (14) Same company code multiple error (15) Classification code mismatch error (16) Date range error (actually (1) (This error is not output because it is caught in the judgment of ~ (7))
When the system option [Single Item Maintenance Consistency Determination] is a determination target, the above error determination is performed as follows.
(1) Application date range error When the application date is 8 digits> ××××××××, “Applicable date range error” is output to the error log. (2) Order start date range error Order start date 8 digits> ×× When “××××××”, “Order start date range error” is output to the error log. (3) Order stop start date range error Order stop start date 8 digits> ×××××××× "Stop start date range error" is output to the error log (XXX represents the preset date)
(4) Order stop end date range error When the order stop end date is 8 digits> xxx xxx xxx, "Order stop ending date range error" is output to the error log. When the order closing date for event ordering is 8 digits> ××××××××, “Order order closing date range error for event ordering” is output to the error log. (6) Discount start date range error Discount start date 8 digits> ××× When xxxx is output, the “discount start date range error” is output to the error log. (7) Discount end date range error When the discount end date is 8 digits> xxx xxxx xxxx "Error" is output to the error log. (8) Lot / entry number 0 error (Registry \ VHONLCTR \ MATCHK2 = 1 or not exists)
When the number of lots = 0 or the number of incoming items = 0, "Lot / Entering number 0 error" is output to the error log. Range error (Registry \ VHONLCTR \ MATCHK3 = 1 or if it does not exist)
Store arrival flight No. <1 or store arrival No. When “> 3”, “Store arrival No. range error” is output to the error log. Range error (determines if \ VHONLCTR \ MATCHK4 = 1 or does not exist)
Flight No. <1 or Flight No. When “> 3”, “Flight No. range error” is output to the error log. Flight No. Mismatch error (Registry \ VHONLCTR \ MATCHK5 = 1 or determines if it does not exist)
Store arrival flight No. ! = Flight No. In this case, “store arrival flight No. flight No. mismatch error” is output to the error log. (12) Minimum order quantity> maximum order quantity error (Registry \ VHONLCTR \ MATCHK8 = 1 or determined not to exist)
When minimum order quantity> maximum order quantity, "Minimum order quantity> Maximum order quantity error" is output to the error log (13) Same common product same flight error (Registry \ VHONLCTR \ MATCHK1 = 1 or not exists)
Read CB_JAN_KEY_TBL using the common company code as a key (repeat while reading)
Extraction condition: Common in-house code = Common in-house code for single item addition / change data Extraction item: In-house code, flight code (in-house code! = In-house code for single item addition / change data) and (flight code = flight code for single item addition / change data) "Same product same flight error" is output to the error log (14) Same in-house code multiple errors (Registry \ VHONLCTR \ MATCHK6 = 1 or not exists)
Read CB_JAN_KEY_TBL using your company code as a key (repeat while reading)
Extraction condition: Company code = Company code extraction item of single item addition change data: Common company code (Common company code! = When the company code of individual product addition change data, "Same company code multiple errors" is output to the error log (15) Classification code mismatch error (Registry \ VHONLCTR \ MATCHK7 = 1 or if it does not exist)
As described above, for the “(1) application date range error” to “(14) same company code multiple errors”, the determination unit 211 performs determination based on the value stored in the update condition storage unit 230. An error judgment is made. On the other hand, for the “(15) classification code mismatch error”, the work table creation unit 212 creates the first work table 251 and the second work table 252 in the work table area 250, and the classification data is stored in this work table. Is stored and compared.

  Next, classification data determination will be described. FIG. 4 is a flowchart showing the classification data determination procedure, and FIGS. 5 to 9 are schematic diagrams showing the states of the first and second work tables during classification data determination.

  When determining the classification data, first, the work table creation unit 212 creates the first work table 251 and the second work table 252 in the work table area 250 according to an instruction from the determination unit 211 (step ST11).

  As shown in FIG. 5, the first work table 251 includes items of serial number, common company code, company code, major classification, middle classification, minor classification, and check result. The second work table 252 includes items of common company code, company code, major classification, middle classification, and minor classification.

  Next, as shown in FIG. 6, the work table creation unit 212 writes the change data of the common company code, company code, and classification (large, medium, and small) to the first work table 251 (step ST12).

  Next, the work table creation unit 212 classifies the second work table 252 based on the CB_JAN_OWN_BAS data of the master data table 220 based on the common company code of the first work table, as shown in FIG. Is updated (step ST13).

  Then, the work table creation unit 212 updates the second work table 252 in the order of the serial number of the first work table 251. When the common company code and the company code do not exist in the second work table 252, a new one is added. When the common company code and company code exist in the second work table 252, the contents of the item are updated (FIG. 8 (2)) (step ST 14).

  The determination unit 211 checks whether the classification (large, medium, small) matches the acquired update data based on the second work table 252, and if the classification data is not the same, the classification data is assumed to be invalid. As shown in FIG. 9, “1” (NG) is stored in the determination result of the first work table 251 (step ST15). As a result, the classification data is determined. When the determination result is “1”, a “classification code mismatch error” occurs.

The error determination made in the determination process described above is output as an error log by the log generation unit 214 to the log file storage unit 240. The error log is created as follows.
The data stored in the error log is as follows.
(1) Maintenance date and time (YYYYMMDDDHHMSS) Set the date and time when starting single item addition / change master maintenance.
(2) PLU (fixed 14 digits, right justified, padded with heads “0”)
(3) In-house code (fixed 14 digits, right justified, padded with "0")
(4) Common company code (fixed 14 digits, right justified, padded with "0")
(5) Classification Large classification (fixed 3 digits, right justified, padded with "0" heads)
Middle classification (fixed 3 digits, right justified, padded with heads “0”)
Small classification (fixed 3 digits, right justified, padded with heads “0”)
(6) Department (fixed 3 digits, right justified, padded with heads “0”)
(7) Head office sales price (fixed 6 digits, right justified, head space)
(8) Taxation category (fixed to 1 digit)
(9) Error reason (40 digits (20 full-width characters) fixed, left justified, extra space)
The output destination of the error log is, for example, c: \ cvs \ data \ mnerr \, and the file name is, for example, “mntlog.MDn”. Here, “MDn” below “.” Is an extension attached in the following format.
M: (Monday) 1-9, A (October), B (November), C (December)
D: (Sunday) 1-9, A (10th) to V (31st)
n: Count 1-9 (1-9 within the same month and day)
The creation date and creation number are displayed by this extension.

For example, if an error log is created twice on November 30,
The first error log is “mnterlog.BU1”, and the second error log is “mnterlog.BU2”.

  In this example, an error log is generated with the above contents, so the error log creation date and order can be easily recognized just by checking the extension of the error log, making it easy to check the error log. Can be. The error log may be deleted after a certain period, for example, three months.

  As described above, according to the master data update method in the POS system according to the present invention, other product data updated with the genuine data is not affected, and the update state is the log generation process. Since it is recorded in the created log file, there is an effect that the illegal data can be confirmed and corrected quickly.

It is a block diagram which shows the POS system with which the update method of the master data which concerns on the example of an embodiment is performed. It is a block diagram which shows the structure of a shop server. It is a flowchart which shows the procedure of the update of a master data table. It is a flowchart which shows the determination procedure of classification data. It is a schematic diagram which shows the state of the 1st and 2nd work table in determination of classification data. It is a schematic diagram which shows the state of the 1st work table in determination of classification data. It is a schematic diagram which shows the state of the 2nd work table in determination of classification data. It is a schematic diagram which shows the state of the 2nd work table in determination of classification data. It is a schematic diagram which shows the state of the 1st work table in determination of classification data.

Explanation of symbols

10 stores, 20 host vendors, 30 lines, 100 POS systems, 200 store servers, 400 host servers

Claims (5)

In a POS system that updates product by product based on update data composed of a plurality of item data for each product that has received product data for each product stored in a master data table constructed in a store server constituting the POS system In the master data update method,
It is determined whether or not a plurality of item data is within a predetermined update condition range for the received update data for each product, and when all item data is within the update condition, the received update data is the product A step of determining that the received update data is invalid data when at least one item data is outside the range of the update condition,
A process of updating the master data table based on update data only for products determined to be positive data;
Generating a log file for the unauthorized data;
A method for updating master data in a POS system.   2. The method for updating master data in a POS system according to claim 1, further comprising a step of preliminarily designating item data to be judged, and performing judgment on the designated item data.   3. The method for updating master data in a POS system according to claim 1, further comprising a step of selecting whether or not to execute the determination process. Update data includes PLU (Price Lookup) data, flight code, company code, common company code for each product,
The update data is determined for each item data, and even if one item data is outside the update condition range, it is determined that the update data for the product is illegal data. A method for updating master data in the POS system. The updated master data includes product classification data,
When detecting illegal data of classification data in the determination process,
A first work table for storing classification data acquired from the update data;
Creating a second work table that stores classification data about the product to be updated acquired from the master data table;
3. The classification data acquired when the classification data stored in the first work table does not match the classification data stored in the second work table is determined to be invalid. A method of updating master data in the described POS system.

Images