JPH03276392A - Method and device for deleting goods master - Google Patents

Abstract

PURPOSE:To properly and surely execute deleting by retrieving a goods master to possess a delete-scheduled flag and of which sales date before more than a fixed period at delete-processing and deleting the extracted goods master list of goods from a goods master memory. CONSTITUTION:A delete-scheduled flag is written in advance to delete-scheduled goods master among the goods masters of a goods master memory 2 in which sales and a sales date based on the sales goods master are recorded renewedly from registers 5, 5... at registering the sales. Then, the retrieving of the goods master to be deleted to the respective goods masters in the memory 2 is executed at the integrating processing to sales registration. That is, the goods master in which the delete-scheduled flag is written from the goods master and of which sales date stored renewedly is before more than a period fixed in advance is extracted by retrieving and the extracted goods master is deleted from a goods list automatically. When an indication is outputted from an operating part 3, the extracted goods master is deleted from the memory 2. Besides, the goods master to be deleted can be displayed on a display part 31 and can be outputted to a printer 4.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention includes a store controller having a product master memory that collectively manages product master and sales data from (cash) registers installed in supermarkets, etc. The present invention relates to a PoS system, and more particularly to a method and apparatus for deleting a product master scheduled for deletion from a product master memory.

[Conventional technology]

In recent years, stores such as supermarkets have introduced PO3 (point of five) methods to effectively manage products.
e) The system is being introduced.

For example, when a new small-scale supermarket opens, the number of product items (hereinafter referred to as product master) is approximately 3,000.
There are ~4,000 items, and after that, the number of items gradually increases until it reaches approximately 10,000 items if left unused for a year, and this will reach the limit of the storage capacity of the product master. Furthermore, product masters that are not actually available in stores and are not sold due to discontinuation of production or the like are also stored as they are, which is not suitable for product management. For this reason, conventional POS systems are provided with a product master deletion function so that dead products and products whose production has been discontinued can be deleted from the product list. This product master deletion function is designed to delete a product master that has no sales record for one month, for example. However,
It is not favorable for competition to delete products that are currently on sale at other stores (Also, even if there are no sales, there are cases where they remain in stores and in stock, especially in the latter case, they may be purchased by changing the layout etc.) In reality, this function, which only takes into account sales results, was rarely used because of the possibility that

Therefore, in reality, a store manager deletes discontinued products one by one from the product master memo υ while checking the list of discontinued products submitted each time by wholesalers and, for example, one month's sales results. It was being processed.

[Problem to be solved by the invention]

However, depending on the case, there are many products that need to be deleted, and if there are products that have sales within one month, the deletion process will be postponed until the next time (one month later). There are many cases in which the postponed product is forgotten to be deleted during the deletion process, and as a result, the product master memory cannot be properly updated and the POS system cannot be used effectively.

The present invention has been made in view of the above, and an object of the present invention is to provide a product master deletion method and device that reliably deletes a product master to be deleted from a product master memory at an appropriate time.

[Means to solve the problem]

The present invention provides a method for deleting a product master scheduled to be deleted from a product master memory in which sales and sales dates based on a sales product master are updated from a register at the time of sales registration. A deletion schedule flag is written in advance corresponding to the master, and when processing the checkout, the product master with the deletion schedule flag is searched from the product master memory, and the updated sales date is more than a predetermined period of time ago. The product master is searched for, and the product master extracted by the search is deleted from the product master memory.

Further, the present invention provides a product master memory in which at least a sales date is updatedly recorded based on a sales product master from a register at the time of sales registration, and a deletion schedule flag written in the product master memory in association with the product master. a schedule flag writing means, a deletion instruction means for giving an instruction to delete the product master, and a deletion schedule flag is written from the product master memory in response to a deletion instruction from the deletion instruction means, and the deletion schedule flag is updatedly stored. The present invention includes a search means for searching for a product master whose sales date is a predetermined period or more ago, and a deletion means for deleting the product master extracted by the search from the product master memory.

Further, an output means such as a printer or a display device may be provided to output the product master extracted by the above search.

[Effect]

According to the method according to the present invention, a deletion scheduled flag is set in advance for a scheduled deletion product master among the product masters of the product master memory in which sales and sales dates based on the sales product master are updated from the register at the time of sales registration. written. Then, at the time of settlement processing for sales registration, a search is performed for each product master in the product master memory to find a product master to be deleted under the following conditions. In other words, a product master in which the deletion schedule flag is written in the product master and in which the updately stored sales date is more than a predetermined period of time is extracted by searching, and this extracted product master is used as the product for the above-mentioned product. automatically removed from the list.

According to the configuration of claim 2, at least the sales date is updated based on the sales product master from the register at the time of sales registration, for the product master scheduled to be deleted among the product masters in the product master memory. When the deletion schedule flag is written in advance and a deletion instruction is received from the deletion instruction means,
A search is sequentially performed by determining whether a deletion schedule flag has been written for each product master in the product master memory, and whether or not the updated sales date is more than a predetermined period of time ago. The product master that satisfies the above conditions is extracted. Then, the extracted product master is deleted from the product master memory.

According to the configuration described in claim 3, the product master to be deleted from the product master memory is deleted.

〔Example〕

FIG. 1 is a block diagram showing an example of a product master deletion device according to the present invention.

In the figure, 1 is a store controller (hereinafter referred to as
2 is a product master memory in which various information related to each product master is stored as shown in Figure 2; 3 is a product master memory that can execute various processes such as sales registration/settlement selection, deletion flag writing, deletion instructions, etc. The operating section is equipped with operation keys, a numeric keypad, etc., and a display section 31 is provided at a certain position.

4 is a printer that prints daily accounting reports for product master records with sales and deletion reports for deleted products; 5;
, 5... are registers installed at appropriate locations within the store.

5TCI is equipped with a clock 11 that is operated by a built-in power supply and outputs date and time signals internally (or externally), and has a register 5.
, 5, . . . data on sales, sales date, etc. at the time of sales registration are captured, and the captured data is stored in a predetermined position of the product master memory 2 in correspondence with the product master. Then, it creates a settlement report based on each input data, searches for and extracts the deleted product master upon receiving a deletion instruction as described later, deletes the deleted product master from the product master memory 2, and performs necessary operations. The deleted product is programmed to be printed or displayed on the display unit 31 in accordance with the deletion. In addition, the 5TCI is internally comprised of a RAM, etc., and includes a memory 12 for a settlement report for settlement processing, which has items according to their purposes, and a memory 12 for a deletion report that (temporarily) stores the product master to be deleted. It is equipped with a memory 13.

The above input data from registers 5, 5... is as follows:
For example, the sales quantity, sales amount (sales), sales date, etc., and at least the sales date are stored in an updated manner. Further, the sales quantity is updated and the cumulative quantity is also stored for comparison with the delivered quantity, ie, for checking the remaining quantity.

As shown in the memory map of FIG. 2, the product master memory 2 includes items such as product master, deletion schedule flag, sales date, delivery quantity, sales quantity, and sales. others,
Although not shown, items such as product number and list price are also provided as necessary. The above deletion schedule flag can be set, for example, by a store manager or the like operating a deletion flag write key (not shown) on the operation unit 3 while looking at a list of discontinued products submitted each time by a wholesaler, etc., for the corresponding product master. This is done by writing "1" in the flag field. for example,
In Figure 2, product masters A and C are not scheduled to be deleted, so the deletion schedule flag field is left at "0", while product master B is marked as a product scheduled to be deleted, and the deletion schedule flag field is set to "1". ” has been written.

Registers 5, 5... input the customer's purchase details, issue the input data as a receipt at the time of sales registration, and
As mentioned above, this is input to 5TCI.

Next, the process of deleting the product master to be deleted will be explained using the flowchart shown in FIG.

Please note that the settlement process is done on a daily basis, and for products scheduled to be deleted, a flag 1'' is set in the deletion scheduled flag field as shown in Figure 2.
It is assumed that the information has been written in advance by the store manager or the like.

When the 5TCI is turned on (start), the selected state of the sales registration/settlement selection key (not shown) is first determined (step S1). If we are currently in a state where sales registration is permitted, the contents of the corresponding product master, such as sales and sales date obtained from clock 11, will be updated every time input data regarding sales is sent from register 5 and sales are registered. is carried out (step S2, Sa). Subsequently, data necessary for creating a daily account settlement report, such as addition of sales, is updated in the daily account settlement report memory 12 (step S4). Similar processing is performed every time there is an interruption of sales registration (loop from step 81 to step S4).

Now, when the day's business ends and the sales registration/settlement selection key is switched to allow settlement (step S1
Wait for an instruction to create a daily account settlement report from the operation unit 3, and if there is an instruction (YES at step S5), create a daily account settlement report (step Ss). That is, the printer 4 is operated to print out the daily account settlement report stored in the daily account settlement report memory 12 either as it is or in a predetermined format.

Subsequently, a search process is sequentially executed in the product master memory 2 from the first row of product masters, for example, product master A in FIG. 2, to the last row.

First, in step S7, it is determined whether or not the deletion schedule flag is "1" for the deletion schedule flag item. For example, since the deletion schedule flag for product master A is "0" (no in step S7), the process moves to step 11, and it is determined whether it is the product master in the last row. If it is not the product master in the last row (No in step S11), the process moves to step S12, where the product master in the next row, for example, product master B, is selected, and the same search as described above is performed. In other words, since the deletion flag for the product master B is "1" (present in step S7), the process moves to step S8, and next, for the item of sales date, whether or not the sales date is within January is checked. A determination is made. Here, if the sales date updatedly stored for each sales registration is within January (step S8
), it is assumed that the item is not to be deleted, and the process moves to step S1□, where it is determined whether or not it is the product master in the last line, as described above. If it is not the product master in the last line (No in step S), the process moves to step S12, the product master in the next line is selected, and the product master is searched. On the other hand, if the sales date is one month or more ago (no in step S8),
As this is the product master to be deleted, product master memory 2
is transferred to the deletion report memory 13 (step 89).
). Furthermore, after this transcription process, the product master is deleted from the product master memory 2 (step 5Szo). After this,
It is determined whether the last line is the product master. If it is not the product master in the last line (NO in step S□□), the process moves to step 812, where the product master in the next line, for example, product master C, is selected and searched.

Since the deletion schedule flag for product master C is 0'' (no in step S7), the process moves to step S11, and if it is not the product master in the last row, the product master in the next row is selected (step 512), and the search is performed. will be held.

Thereafter, product masters are selected one after another until reaching the product master in the last line, and a search is repeated for product masters that have a scheduled deletion flag and whose sales date is one month or more ago (step 87 to step S1°).

When the search for the product master in the last line is completed (YES in step S11), the process moves to step S13 and a deletion report is created. That is, the contents transferred to the deletion report memory 13 are printed out from the printer 4 as is or in a predetermined format. This deletion report may be created by simply displaying it on the display section 31,
It may also be displayed together with the printout.

In addition, in this embodiment, the deletion report is created during the payment process to simplify the instruction operation.
This may be performed separately from the payment processing.

Furthermore, the criterion for determining the sales date is not limited to January, and any suitable period such as one week can be set. Furthermore, monthly review settlement processing and annual settlement settlement processing are also possible.

Further, it is also possible to perform a more suitable deletion determination of a product master by using elements such as sales, sales quantity, and remaining amount in addition to the deletion schedule flag and sales date as determination factors.

〔Effect of the invention〕

As explained above, according to the present invention, a deletion schedule flag is written in advance in correspondence with the product master to be deleted, and when deletion processing is performed, products that have a deletion schedule flag and whose sales date is more than a predetermined period of time ago. Since the product master is searched and the product master extracted by the search is deleted from the product master memory, the product master can be deleted properly and reliably from the product master memory, and the product master 1
There is no need to manually perform troublesome deletion processing for each item. Moreover, by performing the deletion process at the same time as the payment process, there is no need to forget the deletion process.

In addition, since the product master to be deleted is printed out or displayed, it can be confirmed, and it becomes easy to discover erroneous deletion of the product master.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing an example of a product master deletion device according to the present invention, FIG. 2 is a memory map showing an example of storage items in a product master memory, and FIG. 3 is a flowchart showing an example of deletion processing. 1...Store controller (STC), 2...Product master memory, 3...Operation unit, 4...Printer, 5
--Register, 11...Clock, 12...Memory for daily account settlement report, 13...Memory for deletion report, 31
...Display section.

Claims (1)

[Claims] 1. In a method for deleting a product master scheduled to be deleted from a product master memory in which sales and sales dates based on a sales product master are updated from a register at the time of sales registration, A deletion schedule flag is written in advance in correspondence with the product master to be deleted, and at the time of settlement processing, the product master with the deletion schedule flag is searched from the product master memory, and the updated sales date is predetermined. A method for deleting product masters, comprising: searching for product masters older than a period of time, and deleting the product masters extracted by the search from the product master memory. 2. At the time of sales registration, at least the sales date is updated in the product master memory based on the sales product master from the register, and the deletion plan flag is written in the product master memory in association with the product master. means, a deletion instruction means for giving an instruction to delete the product master, and a deletion schedule flag is written from the product master memory in response to the deletion instruction from the deletion instruction means, and the updated sales date is stored. A product master deletion device comprising: a search means for searching for a product master older than a predetermined period; and a deletion means for deleting the product master extracted by the search from the product master memory. 3. The product master deletion device according to claim 2, further comprising an output means for outputting the extracted product master.