JPH0635764A - Record deletion device - Google Patents

Abstract

PURPOSE:To automatically delete unrequired records without increasing record length even when a record deletion period is set in the record. CONSTITUTION:At the time of adjusting a PLU file 17-1, when the contents of a sales amount field inside the merchandise record are not updated for a prescribed period, a CPU 11 sets the record deletion period at the sales amount field. Also, the CPU 11 discriminates whether or not the record deletion period elapsed when the record deletion period is set at the sales amount field. As a result, when the record deletion period elapsed, the corresponding record to which the record deletion period is set is explained from the PLU file 17-1.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a record deletion device for deleting unnecessary records from each record provided for each classification in an electronic cash register or the like.

[0002]

2. Description of the Related Art Conventionally, electronic cash registers (EC
R) is provided with a PLU (price lookup) file, and each product record forming this PLU file has various fields for storing a PLU code, a character, a unit price, the number of sales, a sales amount, etc. , E
The CR performs a registration process for each product based on the sales data input every time the product registration operation is performed, and updates the contents of the number-of-items field and the amount field of the corresponding record. By the way, in large stores, there are many products to handle and the PLU files are huge. Therefore, if there is a product that has not been sold for a certain period (for example, one month or more), delete the product record from the PLU file. I have to. In this case, a field for setting a record deletion period is added to each product record. This record deletion period is set to delete the product record from the PLU file when the corresponding product has not been sold for a predetermined period. If the corresponding product sells before this period elapses, at that time Although the period is updated, if the product does not sell even after the set period has elapsed, the record is deleted from the PLU file at the time of payment.

[0003]

However, in the case of deleting unnecessary records from the PLU file as described above, since a field for setting a record deletion period is required in each record, the number of products handled is particularly large. In a large-scale PLU file for a large store, if a special field is provided in all records, the record length is increased and the file becomes large. An object of the present invention is to make it possible to automatically delete an unnecessary record without increasing the record length even if a record deletion period is set in the record.

[0004]

The means of the present invention are as follows. The data storage unit 1 (see the functional block diagram of FIG. 1, the same applies hereinafter) is a PLU file or the like that stores at least update data in each record provided for each type,
The update field includes a number field, a sales amount field, and the like. The setting means 2 sets a record deletion period in the update field when the content of the update field has not been updated for a predetermined period. Here, for example, the date obtained by adding the date for one month to the current date is set as the record deletion period. The discriminating means 3 discriminates whether or not the record deletion period has elapsed when the record deletion period is set in the update field. The record deleting means 4 deletes the corresponding record for which the record deleting period is set from the data storing means 1 when the judging means 3 judges that the record deleting period has elapsed.

[0005]

The operation of the means of the present invention is as follows. Now, a case where the data storage means 1 is a PLU file in the ECR will be described. Here, when the contents of the data storage means 1 which is a PLU file is settled, the contents of the update fields (sales amount field, etc.) in each product record are set for a predetermined period (for example, from the previous Seimura to the current settlement) prior to that. (For a period of time) and the value is not updated and remains zero, the setting unit 2 sets the record deletion period in this update field. When the record deletion period is set in the update field, the determination means 3 determines whether or not the record deletion period has elapsed, and as a result, if the record deletion period has elapsed, the corresponding product record. Is deleted from the data storage means 1. Therefore, even if a record deletion period is set in a record, unnecessary records can be automatically deleted without increasing the record length.

[0006]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment will be described below with reference to FIGS. FIG. 2 is a block diagram showing the structure of the ECR.
The CPU 11 has a calculation unit 11-1 and a control unit 11-2, and according to various programs in the ROM 12, this E
A key input unit 13, a display unit 14, a printing unit 15, and a drawer 16 are connected to the CPU 11 as a peripheral device for controlling the overall operation of the CR, and control the input / output operations of these.

The key input section 13 has a numeric key AK, a PLU key BK, a department key CK, and other function keys DK on its keyboard, and a mode switch MS.
Is provided. This mode switch MS has “setting”, “registration”, “power OFF”, depending on its switching position.
This is for switching each mode of "inspection" and "payment". The sales data input from the key input unit 13 in the registration mode in which the mode switch MS is set to the "registration" position is displayed and output from the display unit 14. Or printing section 1
It is printed out from 5, and further registered in various totalizers in the RAM 17.

The RAM 17 has a structure including various totalizers such as a PLU file 17-1 and a department file 17-2.
The LU file 17-1 is constructed as shown in FIG. That is, the PLU file 17-1 is provided with a record corresponding to each product in a ratio of 1: 1. Each product record has a PLU code field, a number of fields, a sales amount field, a unit price field, and the sales amount field is It also serves as a field in which the record deleteable date is set instead of the sales amount. The record erasable date is date information set for deleting the corresponding product record from the PLU file when the corresponding product is not sold for a predetermined period.

Next, the operation of this embodiment will be described with reference to the flow charts shown in FIGS. FIG. 4 is a flow chart showing the operation when performing the PLU-specific registration processing in the registration mode in which the mode switch MS is set to the “registration” position. First, when the PLU-by-PLU registration operation is performed, the PLU file 17-1 is referenced to search for a corresponding product record (step A1). Then, it is checked whether or not a record deleteable date is set in the sales amount field in this product record (step A).
2). Here, the first two digits of the data in the sales amount field are defined as an identifier for identifying the data type, and the data type is determined according to the identifier. That is, if the identifier is "00", it is determined that it is a record deleteable date, and if it is "FF", it is determined that it is a sales amount.

If the data in the sales amount field is the normal sales amount, the normal registration by PLU for updating the contents of the sales amount field and the number of fields in the corresponding product record based on the input sales data. Processing is performed (step A3). On the other hand, if the data in the sales amount field is a record deleteable date, the record deletion possible date in the sales amount field is cleared (step A4), and the sales amount according to the sales data entered in the sales amount field is also cleared. Write (Step A
5). In other words, if there is even one sales, even if the record deleteable date is set in the record corresponding to the product, the normal sales amount is written in that field instead. As a result of such an operation being performed each time the PLU-by-PLU registration operation is performed, the record deletable date remains set in the sales amount field for the product without sales.

However, at the end of business day, etc.,
When the settlement process is started in the settlement mode in which the mode switch MS is switched to the settlement position, the operation according to the flowchart shown in FIG. 5 is executed. First, the top record of the PLU file 17-1 is designated (step B
1). Then, it is checked whether or not the data in the sales amount field and the number of fields in the designated record are both "0" (step B2). If the contents of the sales amount field and the number of items field are both “0”, the previous P
After adjusting the contents of LU file 17-1, P this time again
Until the contents of the LU file 17-1 are settled, it is the case that none of the products are sold, so the record deleteable date is set in the sales amount field in the designated record (step B3). In this case, the date obtained by adding the date for one month to the current date is set as the record deleteable date in the sales amount field of the designated record. In addition to the sales amount field, whether or not the content of the number of fields is "0" is checked, for example, a service for providing a certain product to a customer with a large number of points of purchase is provided free of charge. In this case, the sales amount of the product provided free of charge is "0", but the number of cases is "0".
Since it will not be, the number of cases is also checked. next,
This record erasable date is printed out on the settlement report (step B4). Next, PLU file 17-1
It is checked whether or not the last record has been designated (step B5). Since the first record is now designated, the process proceeds to step B6, the next record is designated, and then the process returns to step B2.

Now, in the second record of the PLU file 17-1, if neither the number of cases field nor the sales amount field is "0", step B
In step 8, the data is read from the sales amount field in the designated record, and it is checked whether the data is the record deleteable date or the sales amount. Here, if the data in the sales amount field is the sales amount, the process proceeds to step B12,
Normal settlement processing is performed, the contents of the sales amount field and the count field in the designated record are printed out on the settlement report, and then the contents of the sales amount field and the count field are cleared. Then, on condition that the final record of the PLU file 17-1 has not been specified (step B5), the next record is specified (step B7).

As a result, the third record is designated. If a record erasable date is set in the sales amount field of this record, this is detected in steps B2 and B8, and step B9 is detected. Proceed to and compare today's date with the set record deleteable date to check whether today's date has reached the deleteable date. If today's date has not reached the deletable date, this deletable date is printed out on the settlement report (step B11), but if today's date reaches the deletable date, this deletable date is set. The corresponding record is P
Delete from LU file 17-1 (step B1)
0). Then, the process proceeds to step B5, and the above operation is repeated until the final record of the PLU file 17-1 is designated. When the final record is reached, a settlement report is issued (step B6).

As described above, in this embodiment, the sales amount field in the product record constituting the PLU file 17-1 can be used also as the field for setting the record erasable date, so that the record length is increased. Instead, only unnecessary records can be automatically deleted from the PLU file 17-1.

In the above embodiment, the record erasable date is set in the sales amount field of the merchandise record, but it may be set in the number of cases field. Further, in the above-described embodiment, when searching for a product that has not been sold for a predetermined period, it is checked whether or not the sales amount is “0” in addition to the number of sales, but whether or not one of them is “0”. You may check whether or not. Further, although the above embodiment is applied to the PLU file, unnecessary records may be deleted from other data files.
Further, in the above embodiment, the record erasable date is set, but a day unit or a week unit period may be set.

[0016]

According to the present invention, even if a record deletion period is set in a record, unnecessary records can be automatically deleted without increasing the record length. Can be effectively utilized.

[Brief description of drawings]

FIG. 1 is a functional block diagram of the present invention.

FIG. 2 is a block diagram showing the configuration of an ECR according to the embodiment.

FIG. 3 is a diagram showing the configuration of a PLU file.

FIG. 4 is a flowchart showing the operation of PLU registration processing.

FIG. 5 is a flowchart showing the operation of a settlement process.

[Explanation of symbols]

 11 CPU 12 ROM 17 RAM 17-1 PLU file

Claims (1)

[Claims] 1. A data storage unit for storing at least update data in each record provided for each type, and a setting for setting a record deletion period in the update field when the content of the update field has not been updated for a predetermined period. Means for determining whether or not the record deletion period has elapsed when a record deletion period is set in the update field, and this record when the record deletion period has elapsed for this determination unit A record deleting device comprising: a record deleting unit that deletes a corresponding record having a deletion period from the data storage unit.