JP3725734B2 - Product information management device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a product information management apparatus that stores and manages various types of information related to each product handled in a retail store and supports store operations such as sales and ordering of products.
[0002]
[Prior art]
In a business format where the headquarters controls multiple retail stores, for example, convenience stores, a POS system consisting of a POS (Point Of Sales) terminal and a store controller is built in each retail store, and a computer system is built in the headquarters. In addition, the POS system of each retail store and the computer system of the headquarters are connected via a network so that product sales at each retail store, product orders from each retail store, and the like are centrally managed at the headquarters.
[0003]
Specifically, products such as product name, classification code, selling price, cost, manufacturer code, order unit, etc. corresponding to the product code of each product handled at the store from the computer system of the headquarters to the store controller of each retail store. A product file for storing and managing information is distributed, and at each retail store, a store controller supports store operations such as sales and ordering of products performed at the POS terminal based on the product information in the product file. Collected product sales data and order data acquired by the store controller of each retail store are collected by the computer system of the headquarters via the network, thereby realizing unified management at the headquarters.
Here, the store controller functions as a product information management device that stores and manages various information related to each product handled in the retail store and supports store operations such as sales and ordering of products.
[0004]
By the way, in general, when carrying out store operations such as sales and ordering, each retail store treats a new product that has been newly sold and a normal product that has been continuously sold for more than one month, for example. I have to. Therefore, conventionally, when the store controller accesses the product file, a flag for identifying whether it is a new product or a normal product is set in each product information of the product file distributed from the computer system of the head office to the store controller of each retail store. On the basis of the flag, it is determined whether the product is a new product or a normal product, and supports store operations performed at each POS terminal.
[0005]
[Problems to be solved by the invention]
In this way, since the headquarters conventionally distinguished new products from normal products and set the result as a flag in the product file, if there is a flag setting error at the headquarters, each retail store has a new product. In some cases, a product that should be handled is treated as a normal product, and conversely, a normal product is handled as a new product.
[0006]
Moreover, since the store controller determines whether or not the product subject to information management is a new product from the flag of the latest product file distributed from the headquarters, for example, in ordering business, an order placed on a date earlier than the current day If a product that is no longer a new product on the day is a new product at this time, it has been treated as a new product.
[0007]
In addition, product files distributed from the headquarters are created in a nationwide version, so product information for products that are sold in advance in a specific region is also distributed to retail stores in other regions that are sold late. It was. The headquarters handled this kind of product as a new product for a certain period of time after sales began in the preceding region. For this reason, if a certain period of time has passed before the sales are started in another area, the product cannot be treated as a new product in that area.
[0008]
Accordingly, the present invention provides a merchandise information management device that can manage whether a new product or a normal product other than that on the retail store side without being conscious of the headquarters side, and can also manage the handling period in the case of a new product. It is what.
It is another object of the present invention to provide a product information management apparatus that can arbitrarily set a period for handling as a new product.
[0009]
[Means for Solving the Problems]
The invention described in claim 1 of the present application includes a product file for storing and managing product information such as a product name, a classification code, and an amount corresponding to a product code of each product, and product information to be added to the product file or a product to be changed When a maintenance file storing information is input from the outside, the maintenance is performed each time the maintenance file is input in the product information management apparatus that updates the product information stored and managed in the product file based on the product information stored in the maintenance file. Product information matching means for matching the product information stored in the file with the product information stored in the product file before update, and a product with a product code that exists in the maintenance file by this product information matching means and does not exist in the product file When information is detected, this product information is handled as information on new products. It is provided with a a new product management means for a predetermined period stored and managed from Hajimeji.
With this configuration, product information that exists in the maintenance file but does not exist in the product file is automatically stored and managed as new product information for a certain period from the start of handling the product.
[0010]
According to the second aspect of the present invention, information on a new start change date, which is a start date for managing the product information as information on a new product, is selectively set in the product information stored in the maintenance file. When the new product management means of the invention of claim 1 detects the product information of the product code that exists in the maintenance file and does not exist in the product file by the product information collating means, the product information in the maintenance file is newly started and changed. Judge whether or not day information is set. If not set, store and manage this product information as new product information for a certain period from the start of handling. If set, start the new information. The information is stored and managed as information on new products for a certain period from the date of change.
With this configuration, as in the first aspect of the invention, product information that exists in the maintenance file but does not exist in the product file is automatically stored and managed as new product information for a certain period of time. However, the start date of this period is the new start change date set in the product information of the maintenance file.
[0011]
In the invention described in claim 3 of the present application, when the product information of the product code existing in both the maintenance file and the product file is detected by the product information matching means in the invention described in claim 2, the product information on the maintenance file side is displayed. It is determined whether or not new start change date information is set, and if set, a new change product management means for storing and managing the product information as new product information for a certain period from the new start change date. It is provided.
By having such a configuration, among the product information of the product code existing in both the maintenance file and the product file, the product information in which the new start change date information is set in the product information on the maintenance file side is new. The product information is stored and managed for a certain period from the new start change date.
[0012]
The invention according to claim 4 of the present application selectively sets a new non-target flag in the product information stored in the maintenance file. When the new product management means according to the first aspect of the invention detects product information of a product code that exists in the maintenance file and does not exist in the product file by the product information matching means, the product information in the maintenance file is not newly included in the product information. It is determined whether or not a flag is set, and only when the flag is not set, this product information is stored and managed as information on new products for a certain period from the start of handling.
By having such a configuration, among product information that exists in the maintenance file but does not exist in the product file, product information in which the new exclusion flag is not set in the product information on the maintenance file side is automatically new. It is stored and managed as product information for a certain period.
[0013]
The invention according to claim 5 of the present application is provided with a table memory in which a handling period as a new product is preset for each classification code for classifying each product, and in the invention according to each of claims 1 to 4, the new product management The period for storing and managing as new product information by the means is the handling period set in the table memory corresponding to the classification code to which the product belongs.
By having such a configuration, the period for storing and managing as new product information is variably set according to the classification code to which the product belongs.
[0014]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a conceptual diagram of a POS system constructed in each retail store controlled by the headquarters. The store controller 1 functions as a product information management apparatus of the present invention, and a plurality of units that perform product sales and ordering operations. POS terminal 2 is connected to communication line 3 such as a LAN (Local Area Network).
The store controller 1 is equipped with a product file 5 that stores a large number of product information records in the record format shown in FIG. The product information record is configured for each product, and using the product code of the product as a key, product management information such as a product name, a department code as a classification code, a selling price, a manufacturer code, an order unit, and the product information record It is a record that stores handling period information (handling start date and handling end date) and new period information (new start date and new end date) that is a handling period as a new product.
[0015]
The store controller 1 is connected to a computer system (not shown) of the headquarters via a dedicated communication network 4 such as ISDN (Integrated Services Digital Network). A maintenance file 6 storing a maintenance record in the record format shown in FIG. 3 is distributed from the computer system of the headquarters via the dedicated communication network 4 in a timely manner.
[0016]
The maintenance record is configured for each product information record to be added or changed to the product file 5 and corresponds to the product code that is the key of the product information record to be added or changed. This record stores product management information such as a department code, selling price, manufacturer code, order unit, handling period information (handling start date and handling end date), a new non-target flag, and new start change date information.
Here, the new non-target flag is a flag that is set to “1” when the product information record added or changed by the maintenance record is not a new target. The new start change date information is a start date for managing a product information record added or changed by the maintenance record as a record of a new product. These new target flag and new start change date information are arbitrarily set on the computer system of the headquarters.
[0017]
FIG. 4 is a block diagram showing a configuration of a main part of the store controller 1, and a CPU (Central Processing Unit) 11 is mounted as a control unit body. The CPU 11 receives a read only memory (ROM) 12 in which fixed data such as a program is stored in advance via a bus line BL such as an address bus and a data bus, and a maintenance file 6 distributed from the computer system of the headquarters. A RAM (Random Access Memory) 13 in which various memory areas such as a reception buffer for temporary storage are formed, a clock unit 14 for measuring the current date and time, and each POS terminal 2 connected via the communication line 3 POS interface 15 for controlling data communication, HDD (Hard Disc Drive) device 16 for storing data files such as the product file 5, FDD (Floppy Disk Drive) device 17 for writing and reading data to and from a floppy disk, keyboard, Various input / output devices such as displays and printers are connected I / O port 18 is connects the host interface 19 for controlling the data communication with the private network 4 connected headquarters computer system via.
[0018]
As shown in FIG. 5 in particular, the RAM 13 is formed with a departmental period setting table 7 in which day data is preset for each department code for classifying each product. Then, in each retail store, a period (number of days) in which a product belonging to the department is treated as a new product is determined for each department, and the number of days data is set in the department-specific period setting table 7 in the store controller 1 of the own store. I am doing so. It is also possible to determine a new product handling period for each department at the headquarters and create the department-specific period setting table 7 and load this table 7 into the RAM 13 via the dedicated communication network 4 or via a floppy disk.
[0019]
When the store controller 1 configured as described above receives the maintenance file 6 distributed from the computer system of the headquarters via the dedicated communication network 4 and temporarily stores it in the reception buffer, the CPU 11 performs the merchandise file update process shown in the flowchart of FIG. The program of the ROM 12 is configured to execute.
[0020]
First, the CPU 11 resets the counter n built in the CPU to “0” as ST (step) 1. Next, when the counter n is incremented by “1” as ST2, the CPU 11 reads out the maintenance record of the record number n corresponding to the count value of the counter n from the maintenance file 6 stored in the reception buffer as ST3.
[0021]
Here, if a record with the record number n exists in the maintenance file 6 and is read as ST4, the product file 5 is searched using the product code of the maintenance record with the record number n as a search key as ST5 (product information matching means) ).
If a product information record having a product code that matches the product code as the search key is detected in ST6, the maintenance record is a record for changing the product information of the product information record. Execute the change process. On the other hand, if a product information record having a product code that matches the product code as the search key cannot be detected in ST6, the maintenance record is a record of product information to be added to the product file 5, and will be described later as ST8. Execute product information record addition processing.
[0022]
When the merchandise information record change process in ST7 or the merchandise information record addition process in ST8 is completed, the CPU 11 returns to the process in ST2, further increments the counter n by “1”, and maintains the maintenance of record number n from the maintenance file 6. Read the record. Then, the product file 5 is searched using the product code of the maintenance record with the record number n as a search key, and if a product information record with a matching product code is detected, the product information record change process is executed and cannot be detected. If so, the product information record addition process is executed.
[0023]
Thus, every time one record is read from the maintenance file 6, the merchandise information record changing process or the merchandise information record adding process is executed, and when the record of the record number n does not exist in the maintenance file 6 in ST4, it becomes difficult to read. In ST9, the maintenance file 6 is deleted from the reception buffer, and the product file update process is terminated.
[0024]
FIG. 7 is a flowchart embodying the contents of the merchandise information record changing process. That is, when the CPU 11 detects a product information record that matches the product code of the maintenance record with the record number n from the product file 5, the CPU 11 starts this product information record change process.
[0025]
First, in ST11, the handling period information and the merchandise management information of the corresponding merchandise information record are rewritten to the handling period information and the merchandise management information of the maintenance record of record number n. Next, in ST12, it is determined whether or not a new non-target flag is set in the maintenance record with the record number n. Here, when it is confirmed that the new non-target flag is set to “1”, that is, it is set to be non-new target (YES in ST13), the new period of the corresponding product information record as ST14 The information is cleared, that is, the management period as a new product is forcibly terminated, and the product information record change process is terminated.
[0026]
On the other hand, if the new non-target flag of the maintenance record with the record number n is not set to “1”, that is, is not set to be out of new target (NO in ST13), this record number is set as ST15. The new start change date information of the n maintenance records is checked. If it is confirmed that the new start change date information is not set (YES in ST16), the product information record change process is terminated.
[0027]
On the other hand, if it is confirmed that the new start change date information is set (NO in ST16), the date data of the new product handling period corresponding to the department code of the maintenance record with the record number n is obtained by department as ST17. Read from the period setting table 7. In ST18, a date D is calculated by adding the day data from the date of the new start change date information. Therefore, the date of the new start change date information is set as the new start date of the new period information in the product information record of the product file 5 rewritten based on the product information of the maintenance record with the record number n in ST19, and the new end date If the product information record is set to be managed as new product information for a certain period of time by setting the date D calculated in ST18 (newly changed product management means), the product information record change process is terminated.
[0028]
FIG. 8 is a flowchart embodying the contents of the product information record addition process. That is, the CPU 11 cannot detect the product information record that matches the product code of the maintenance record with the record number n from the product file 5, that is, if the product information of the product code that exists in the maintenance file 6 and does not exist in the product file 5 is detected. The product information record addition process is started.
[0029]
First, a new record is secured in the product file 5 as ST21, and the product code, product management information, and handling period information of the maintenance record with the record number n are set in this record. Next, in ST22, it is determined whether or not the new non-target flag of the maintenance record with the record number n is set to “1”. Here, when it is confirmed that it is set to “1”, that is, it is set to be excluded from the new target (YES in ST23), the new period information of the product information record added to the product file 5 is set. This product information record addition process is terminated without setting.
[0030]
On the other hand, if the new non-target flag of the maintenance record with the record number n is not set to “1”, that is, it is not set to be out of the new target (NO in ST23), this record number is set as ST24. The new start change date information of the n maintenance records is checked. If it is confirmed that the new start change date information is not set (YES in ST25), the date data of the new product handling period corresponding to the department code of the maintenance record of record number n is obtained as ST26. Read from another period setting table 7. Then, in ST27, a date D is calculated by adding the day data from the handling start date of the maintenance record with the record number n. Thus, in ST28, the handling start date is set as the new start date of the new period information in the product information record added to the product file 5 based on the product information of the maintenance record of record number n, and the new end date is set in ST27. If the product date record is set to be managed as a new product information for a certain period of time by setting the calculated date D (new product management means), the product information record addition process is terminated.
[0031]
On the other hand, if it is confirmed that the new start change date information is set (NO in ST25), the number of days data of the new product handling period corresponding to the department code of the maintenance record with the record number n is obtained in ST29. Read from the period setting table 7. Then, as ST30, a date D is calculated by adding the day data from the date of the new start change date information. Accordingly, the date of the new start change date information is set as the new start date of the new period information in the product information record added to the product file 5 based on the product information of the maintenance record with the record number n as ST31. When the date D calculated in ST30 is set as the end date so that the product information record is set to be managed for a certain period of time as new product information (new product management means), the product information record addition process is terminated. .
[0032]
In this embodiment configured as described above, a maintenance record of product information to be added to a product file 5 mounted on a store controller 1 installed in each retail store and a maintenance record of product information to be changed are stored. A maintenance file 6 is created by the computer system of the headquarters and distributed to the store controller 1 of each retail store via the dedicated communication network 4.
[0033]
Then, the store controller 1 of each retail store that has received the maintenance file 6 executes the above-described product file update process. Thereby, the product information record corresponding to the product file 5 is added based on the maintenance record of the product information to be added to the product file 5. Further, the corresponding product information record of the product file 5 is changed based on the maintenance record of the product information to be changed.
[0034]
In this case, the product information record added to the product file 5 is a record of a product code that exists in the maintenance file 6 but does not exist in the product file 5, and is automatically managed as a record of a new product. Specifically, when a new start change date is set in the corresponding maintenance record, it is managed as a new product for a certain period from the new start change date, and when a new start change date is not set , The product is managed as a new product for a certain period from the start date of handling of the product. Here, the fixed period managed as a new product is the number of days set in advance on the departmental period setting table 7 for the department to which the product belongs.
If the new non-target flag is set (set to “1”) in the corresponding maintenance record, the product information record is not managed as a record of a new product.
[0035]
On the other hand, the product information record changed based on the maintenance record in the maintenance file 6 also has a new start change date when the new non-target flag of the maintenance record is not set and a new start change date is set. Are managed as new product records for a certain period of time. The period in this case is also the number of days set in advance in the section setting table 7 for the section to which the product belongs.
In addition, when the new non-target flag of the maintenance record is set (set to “1”) and the new period information is set in the changed product information record, the new period information is compulsory. Cleared. That is, it is no longer managed as a record of a new product.
[0036]
As described above, in this embodiment, the product information stored in the maintenance file 6 received from the computer system of the headquarters, and the product information stored in the product file 5 before being updated by the maintenance record of the maintenance file 6 When product information of a product code that exists in the maintenance file 6 but does not exist in the product file 5 is detected, this product information is automatically stored and managed as new product information for a certain period from the start of handling. Yes. Therefore, it is not necessary for the headquarters creating the maintenance file 6 to set or reset a flag added to the product information in consideration of whether the product information stored in the file 6 is information on a new product. As a result, a product that should be a new product at each retail store is not handled as a normal product other than a new product, or a normal product is not handled as a new product due to a setting error at the headquarters. In addition, since the period from the new start date to the new end date is set and managed, for example, for products that are not new products on the order date before the current date in the ordering business, even if the current product is a new product It is handled as a normal product and can perform store operations without hindrance.
[0037]
Further, in the present embodiment, new start / change date information is selectively set in the product information stored in the maintenance file 6. When product information of a product code that exists in the maintenance file 6 but does not exist in the product file 5 is detected, it is determined whether or not new start / change date information is set in the product information of the maintenance file 6. If not set, this product information is stored and managed as new product information for a certain period from the start of handling, and if set, it is stored and managed as new product information for a certain period from the new start change date. ing. Therefore, the start date of the period managed as a record of a new product can be arbitrarily changed by the setting of the headquarters.
[0038]
Also, when product information of a product code existing in both the maintenance file 6 and the product file 5 is detected, it is determined whether or not new start date information is set in the product information on the maintenance file 6 side. If set, the product information is stored and managed as new product information for a certain period from the new start change date. Therefore, the merchandise information that has been managed as a normal merchandise record in each retail store can be managed as a new merchandise record for a certain period of time by setting the headquarters.
[0039]
Furthermore, in this embodiment, a new non-target flag is selectively set in the product information stored in the maintenance file 6. When product information of a product code that exists in the maintenance file 6 but does not exist in the product file 5 is detected, it is determined whether or not a new exclusion flag is set in the product information of the maintenance file 6. Only when there is not, this product information is stored and managed as information on new products for a certain period from the start of handling. Therefore, even if it is a merchandise information record added to the merchandise file 5, it can be made not to manage as a record of a new merchandise by the head office setting.
[0040]
Further, when product information of a product code that exists in both the maintenance file 6 and the product file 5 is detected, it is determined whether or not a new exclusion flag is set in the product information of the maintenance file 6. If it is set, the new period information of the corresponding product information in the product information file 5 is forcibly cleared. Accordingly, it is possible to forcibly change the merchandise information record managed as a new merchandise record in each retail store to a normal merchandise record by setting the headquarters.
[0041]
In the present embodiment, a section-specific period setting table 7 in which a handling period as a new product is set in advance for each department code for classifying each product is provided, and the period to which the product belongs is stored and managed as information on the new product. The handling period is set in the department-specific period setting table 7 corresponding to the department code. Therefore, the period managed as a new product can be variably set for each retail store depending on the department to which the product belongs.
[0042]
In the above-described embodiment, the maintenance file 6 is input to the store controller 1 by online delivery. However, the maintenance file 6 may be recorded on a floppy disk and read by the FDD 17 and input to the store controller 1. . Needless to say, a memory card, CD-ROM, or the like may be used instead of the floppy disk.
[0043]
【The invention's effect】
As described above in detail, according to the invention described in claim 1 of the present application, it is possible to manage a new product or other normal product on the retail store side without being conscious on the headquarter side, and in the case of a new product, A product information management apparatus capable of managing the handling period can be provided.
Further, according to the invention described in claim 2 of the present application, in addition to the effect of the invention described in claim 1, it is possible to achieve an effect that the start date of the period managed as a new product can be arbitrarily set.
Further, according to the invention described in claim 3 of the present application, in addition to the effect of the invention described in claim 2, it is possible to produce an effect that a product that has been managed as a normal product so far can be managed as a new product for a certain period of time. .
Further, according to the invention described in claim 4 of the present application, in addition to the effect of the invention described in claim 1, an effect that can be forcibly set not to be managed as a new product can be achieved.
Furthermore, according to the invention described in claim 5 of the present application, in addition to the effects described in the above claims, there can be achieved an effect that the period managed as a new product can be arbitrarily variably set according to the classification to which the product belongs.
[Brief description of the drawings]
FIG. 1 is a conceptual diagram of a POS system according to an embodiment of the present invention.
FIG. 2 is a view showing a format of a product information record stored in a product file in the embodiment.
FIG. 3 is a diagram showing a format of a maintenance record stored in a maintenance file in the embodiment
FIG. 4 is a block diagram showing a main configuration of a store controller according to the embodiment.
FIG. 5 is a configuration diagram of a departmental period setting table formed in the RAM of the store controller.
FIG. 6 is a flowchart showing a main part of a product file update process executed by the CPU of the store controller.
7 is a flowchart that embodies the merchandise information record change process in FIG. 6;
FIG. 8 is a flowchart that embodies the product information record addition process in FIG. 6;
[Explanation of symbols]
1 ... Store controller
2 ... POS terminal
4 ... Dedicated communication network
5. Product file
6. Maintenance file
7… Department period setting table

Claims (5)

A product file that stores and manages product information such as product name, classification code, price, etc. corresponding to the product code of each product is provided, and a maintenance file that stores product information to be added or changed to this product file from the outside When the product information management apparatus updates product information stored and managed in the product file based on the product information stored in the maintenance file,
Each time the maintenance file is input, product information matching means for matching the product information stored in the maintenance file with the product information stored in the product file before update, and the product information matching means New product management means for storing and managing the product information as new product information for a certain period from the start of handling the product when product information of a product code that exists and does not exist in the product file is detected. Product information management device. The product information stored in the maintenance file is selectively set with information on a new start change date, which is a start date for managing the product information as information on a new product, and the new product management means is configured as the product information collating means. When the product information of the product code that exists in the maintenance file and does not exist in the product file is detected, it is determined whether or not the new start / change date information is set in the product information of the maintenance file. This product information is stored and managed as new product information for a certain period from the start of handling, and if set, means for storing and managing as new product information for a certain period from the new start change date The merchandise information management device according to claim 1. When the product information of the product code existing in both the maintenance file and the product file is detected by the product information matching unit, it is determined whether or not new start change date information is set in the product information on the maintenance file side. 3. A merchandise information management unit according to claim 2, further comprising a newly changed merchandise management means for storing and managing merchandise information as new merchandise information for a predetermined period from the new start change date if set. apparatus. A new non-target flag is selectively set in the product information stored in the maintenance file, and the new product management means is a product with a product code that exists in the maintenance file by the product information matching means and does not exist in the product file. When information is detected, it is determined whether or not a new exclusion flag is set in the product information of the maintenance file. Only when the flag is not set, the product information is stored and managed as new product information for a certain period from the start of handling. The merchandise information management apparatus according to claim 1, wherein the merchandise information management apparatus is a means. A table memory in which a handling period as a new product is set in advance for each classification code for classifying each product is provided, and the period for storing and managing the information as new product information by the new product management means corresponds to the classification code to which the product belongs. The merchandise information management device according to any one of claims 1 to 4, wherein the handling period is set in the table memory.

Images