JP2576113B2 - Data processing device - Google Patents

Description

Description: TECHNICAL FIELD The present invention relates to a data processing device, such as an electronic register.
This is used in a data processing device that performs cumulative processing of data relating to related items of classification data.

[Prior Art] In a conventional electronic register, generally, a PLU (Minimum Unit of Product Classification for Unit Price Reference) code is
U Unit price and character are preset in advance, and corresponding to these, the total is calculated based on the above unit price.
A PLU file that stores the total sales amount and the like for each PLU is provided. The PLU file is additionally corrected in terms of unit price, PLU code, and the like for a new product by the following method. That is, the correction data is temporarily stored in a separate file once, and the PL
When the U code is entered as sales data, registration processing such as storing the total sales amount for each PLU based on another file is performed.For example, after the business closes, the contents of another file are added to the PUL file and corrected. I am trying to do it.

[Problem to be Solved by the Invention] By the way, the conventional additional correction process is performed according to a procedure as shown in a flowchart of FIG. First, the electronic register is additionally corrected based on the PLU file based on another file (the batch maintenance process in step S101), and then all the data of the another file is printed out (step S101).
S102). The operator then looks at the print contents and
It is determined whether or not there is any content that is duplicated (error) with the content stored in the file (step S103). If there is a duplicate content, it means that there is a change to the content (unit price, etc.) stored in the PLU file.
The operator clears the contents stored in the PLU file by performing a predetermined operation to make new data in another file valid (step S104). If there is an erroneous setting (step S103), the error data of another file is corrected (step S104). After the operator makes all the corrections for changes and corrections for erroneous settings, the data in another file is cleared (step S1).
05).

As described above, conventionally, only the process of additional correction for the PLU file can be automatically performed. Therefore, deleting or changing the data of the PLU file requires a troublesome operation with the intervention of an operator. Did not. In addition, the operator sees all the print contents of another file and
It was necessary to determine whether there was an overlap (error) with the contents stored in the U file.

An object of the present invention is to correct a plurality of pre-stored classification data with a plurality of newly input classification data, and to correct control data stored corresponding to the newly input classification data. The purpose is to enable immediate correction in accordance with the correction mode, and to allow the input classification-specific data determined to be uncorrectable to be visibly output.

[Means for Solving the Problems] The means of the present invention are as follows.

 The first storage unit stores a plurality of classification-specific data.

The second storage means stores a plurality of classification data newly inputted and stores control data indicating a correction mode such as deletion or change in association with each of the classification data.

The determining means corrects the plurality of classification data stored in the first storage means based on the individual classification data stored in the second storage means,
It is determined whether or not the correction can be performed for each classification-specific data stored in the storage means.

The correction unit is configured to correct the classification data in the second storage unit determined to be correctable by the determination unit according to a correction mode of the control data stored corresponding to the classification data. And correcting the corresponding classified data in the first storage means.

The visible output means, for the classification data in the second storage means determined to be uncorrectable by the determination means, corrects the classification data without performing correction to the first storage means. Output to be visible.

[Operation] The operation of the means of the present invention is as follows.

A plurality of classification-specific data is stored in the first storage means,
The second storage unit stores a plurality of newly input classification data and control data indicating a correction mode such as deletion or change in association with each of the classification data. . Then, based on the individual classification data stored in the second storage means, the first
In correcting a plurality of classification data stored in the storage means, the determination means determines, for each classification data stored in the second storage means, whether or not the correction is possible. According to the classification data in the second storage means determined to be correctable by the determination, the first data is stored in accordance with the correction mode of the control data stored corresponding to the classification data. The corresponding classification data in the storage means is corrected by the correction means, and the classification data in the second storage means determined to be uncorrectable by the determination means is the first classification data. Is not output to the storage means, and the classified data is output by the visible output means so as to be visible.

Therefore, when correcting a plurality of pre-stored classification data with a plurality of newly input classification data, the input classification data determined to be correctable corresponds to the classification data. Can be immediately corrected according to the correction mode of the control data stored as
With respect to the input classification data determined to be impossible to correct, the classification data can be output in a visible manner.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

Configuration FIG. 2 is a configuration diagram of a data processing device according to one embodiment of the present invention, and this embodiment is an example applied to an electronic register.

This electronic register is for registering sales data with the CPU 1 as the core, and the CPU 1 has an input unit 2, a RAM 3,
The display unit 4 and the printing unit 5 are connected. And
The CPU 1 processes the sales data input from the input unit 2 in various modes, controls operations such as storing the processing result in the RAM 3, displaying the processing result on the display unit 4, and printing the data on the printing unit 5.

The input unit 2 includes a setting (P), a registration I (REG I), a registration II
(REG II), power off, mode (X), checkout (Z) mode changeover switch 2a for switching and setting each mode, department key 2b for inputting departments such as food department, clothing department, unit price, PLU Numeric keys 2c for inputting code numbers and the like, character keys 2d for inputting product characters, etc., # 1, # 2, #
3, # 4 key and the like.

In the RAM 3, a PLU file m1 and a batch maintenance file m2 are formed. The PLU file m1 has a plurality of records formed for each PLU, and each record is composed of the following data items. That is, PL
It consists of a U code No. item, a unit price item, a character item, a bolt unit price item, a mix match item, a section item, a total sales quantity item, a total sales amount item, and a stock item. The PLU code No. item contains the PLU code No.
Are preset and used as key items. A unit price is preset in the unit price item. In the character item, character data indicating a product name is preset. In the bolt unit price item, the unit price of the bolt itself storing the product is preset. In the mix match item, for example, when five or more products are purchased together, mix match data such as a discount of 100 yen is preset. In the section item, a section number is preset. When the PLU code No. and the sales quantity are input by the input unit 2 in the registration I mode in the sales total quantity item, the sales total quantity item in the record corresponding to the input PLU code No. The total value of the content and the number of sales pertaining to the current input is stored. In the total sales amount item, when the PLU code No., the sales quantity, and the like are input by the input unit 2 under the registration I mode, the total sales amount item in the record corresponding to the input PLU code No. , A unit price item, a mix match item, and the like, and a total sales amount calculated based on the contents thereof. The stock item stores the stock quantity of the product, and the stock quantity is subtracted according to the input sales quantity. The arrangement order of these items is unified between records, and the contents of each item are expressed in a predetermined data format. For example, the PLU code No. is represented by a 2-byte binary number (represented by hexadecimal numbers), the unit price is represented by a 3-byte binary number, and the characters are represented by one-byte, one-byte JIS-C6220 code katakana code.
Expressed as 10 characters (10 bytes).

Batch maintenance file m2 collectively stores correction data to add or delete records, or to change the contents of items in records, for example, unit price, etc., from PLU file m1. And based on it PL
It is for maintaining and managing the U file m1. When setting the correction data in the batch maintenance file m2, the validity of the data format is not determined. Under the registration II mode, the contents of the PLU file m1 are corrected based on the contents of the batch maintenance file m2. At this time, the data format of the batch maintenance file m2 and the order of the items (in a broad sense) A record whose data format differs from that of the PLU file m1 cannot be corrected. Then, the record contents provided for correction in the batch maintenance file m2 are deleted, but the record contents which cannot be corrected and are not provided for correction are not deleted from the batch maintenance file m2 and are printed out. . Then, based on this printout, the contents of the record are changed to the same item arrangement and data format as the PLU file m1 by the operator, so that the PL is updated based on all the records in the batch maintenance file m2.
When the contents of U file m1 are corrected, batch maintenance
All records in the file m2 will be deleted. The batch maintenance file m2 has, in addition to the same items as the PLU file m1, a correction mode flag item indicating whether the correction mode for the PLU file m1 is addition, change, or deletion. The addition is “00” and the change is “0”
1 ", deletion is indicated by" 10 ".

When correcting the PLU file m1 by the batch maintenance file m2, the register group R, the record pointer P, and the like in the CPU 1 are used.

Operation Next, the operation of this embodiment will be described.

FIG. 3 is a flowchart showing the operation of the present embodiment. When the registration II mode is set by the mode changeover switch of the input unit 2, the CPU 1 firstly operates according to a program stored in a ROM (not shown) in advance. Then, it waits for data input, and determines whether or not the input data is the manager number (step S1). If it is a manager number, it is determined whether or not the next input data is a person in charge number and a batch maintenance designation code (step S2). As a result, if it is the person in charge number and the batch maintenance designation code, it is further determined whether or not the next input data is a setting designation code (step S3). as a result,
If it is not the setting designation code, it is determined whether or not the mode is the batch maintenance execution designation mode (step S4). If the mode is the batch maintenance execution designation mode, the process proceeds to step S5 to execute the batch maintenance process.

Next, the batch maintenance process will be described in detail with reference to FIG. FIG. 4 is a subroutine showing a batch maintenance process in step S5. First, data for one record is read from the batch maintenance file m2,
The data is stored in the register group R in U1 (step S51). Next, the correction mode is determined based on the correction mode flag item in the record stored in the register group R (step S5).
2) If it is "00", the process of adding the record to the PLU file m1 is started (step S53). This additional processing is performed as follows. In other words, batch maintenance
If the data length of each item in the record read from the file m2 and the corresponding item in the PLU file m1 match, the data in the record is recognized as normal data, and additional processing is executed. However, if the same PLU code No. depends on the PLU file m1 even if the data lengths match, the fact that the PLU code No. is originally set in the batch maintenance file m2 to add , PLU file m
Since the PLU code number and correction mode may not be stored in the batch maintenance file m2, no additional processing is performed.

As a result of the determination in step S52, the correction mode flag is "01"
If so, the change process is started (step S54). Also in this change processing, the normality is determined by determining the data length of each item in the record read from the batch maintenance file m2. In addition, the change is based on the unit price for the PLU-specific product already stored in the PLU file m1,
Since the processing is performed for the bottle unit price and the content of the mix match, the normality of the record read from the batch maintenance file m2 is also determined based on whether or not the same PLU code No. exists in the PLU file m1. If it is determined that the PLU file m1 is normal, the contents of the PLU file m1 are rewritten with the unit price pertaining to the change, and the total sales quantity and the total sales amount are added.

As a result of the determination in step S52, the correction mode flag is "10".
If so, the deletion process is started (step S55). This deletion means the deletion of one entire record corresponding to one PLU-specific product. Since only the PLU code number is set in the record read from the batch maintenance file m2, the same record is deleted.
Normality is recognized only by determining whether the PLU code No. exists in the batch maintenance file m2. Then, when it is recognized that it is normal, the entire record corresponding to the 1PLU-specific product is deleted from the PLU file m1. Note that, instead of deleting the entire record, a part of the record such as the bottle unit price and the content of the mix match is deleted by a change process.

After starting any one of steps S53 to S55, the process proceeds to step S56, in which it is determined whether the contents of the record read from the batch maintenance file m2 are normal and the correction processing has been executed normally. . As a result, when the processing has been executed normally, the contents of the record subjected to the correction processing are deleted from the batch maintenance file m2 (step S5).
7). Then, the record pointer P is incremented by "1" (step S58). If the result of determination in step S56 is that correction processing has not been executed, the process immediately proceeds to step S58 without deleting the target record from the batch maintenance file m2. Next, it is determined whether or not an end-of-file (EOF) code is stored at the position of the batch maintenance file m2 indicated by the record pointer P (step S59). Since this means that the record is not a record, the process returns to step S51 to perform a correction process based on the record. If the EOF code has been stored, the processing of this subroutine ends, and the process returns to the main program of FIG.

As described above, since only the normal records are deleted, when the processing of this subroutine is completed and the process returns to the main program, only the records related to the setting are left in the batch maintenance file m2. It will be.

In this way, when the batch maintenance processing is completed, the main program of FIG. 3 stores the contents of the batch maintenance file m2 at that time, that is, the contents of the records in the batch maintenance file m2 related to the erroneous setting. All are read out and printed by the printing unit 5 (step S6), and the process ends. Then, by judging the content of the print, the record of the erroneous setting is correctly corrected, and if the batch maintenance process is performed based on the corrected record, all the contents of the batch maintenance file m2 are deleted. The batch maintenance file m2 can be used effectively. Then, to correct incorrect settings, as in the prior art,
It is not necessary to judge the correctness of all the records of the batch maintenance file m2 one by one.It is only necessary to judge the correctness only for the records that are automatically determined to be incorrect and printed, Re-execution can be performed quickly.

The re-execution of the batch maintenance process is performed as follows. That is, when correcting the record relating to the erroneous setting printed in step S6 of FIG. 3, when the manager No. person in charge, the batch maintenance designation code, and the setting designation code are input, the process goes through steps S1 to S3. Proceeding to step S7, a setting correction process is executed.

Next, the setting correction process will be described with reference to FIG. FIG. 5 is a subroutine showing a setting correction process in step S7 in FIG.
When a U code No. is entered, a record with the PLU code No. as a key item is stored in the batch maintenance file m2.
Is read out to the register group R (steps S7-1, S2). Then, it is determined whether or not the input next to the PLU code No. is in the correction mode, and if so, the correction mode on the register group R is corrected to the input mode (step S7-3,
4). Hereinafter, similarly, correction according to the next input of the PLU code No. is performed. That is, when the mode is not the correction mode, the process proceeds to step S7-5 to determine whether or not the PLU code No.
If it is not the PLU code No., the process further proceeds to step S7-7 to determine whether or not the price is a unit price, to specify the input content, and make a correction according to the specified content. For example,
When the PLU code No. is input, the PLU code No. of the record read into the register group R with the PLU code No. input in step S1 as a key item is corrected to the PLU code No. input this time. (Steps S7-5 and S6). When the unit price is entered, the unit price is corrected to the unit price entered this time (steps S7-7, S8). At the time of the unit price correction, the total sales amount is also corrected at the same time based on the contents of the corresponding sales total number item and the corrected unit price. When a character is input, the character is corrected to the character input this time (steps S7-9 and S10). When the content of the mix match is input, the content itself is corrected and the total sales based on the correction are performed. Correct the amount (Step S7-
11 and 12) Similarly, when the unit price of the bottle, the department, and the stock are input, they are corrected (steps S7-13-1).
8). Then, it is determined whether a # 3 code corresponding to the # 3 key has been input (step S7-19).
If there is no input of the three codes, the process returns to step S7-3 to sequentially correct other items to be corrected in the record read out to the register group R. When the # 3 code is input, it is recognized that the modification of the read record has been completed, and the target record of the batch maintenance file m2 is rewritten to the contents of the register group R (step S7).
-20). Then, it is determined whether or not the # 4 code corresponding to the # 4 key has been input (step S7-21). If the # 4 code has not been input, the erroneous setting in the batch maintenance file m2 is still not detected. It recognizes that a record exists, and returns to step 7-1. When the # 4 code is input, it is recognized that all the records related to the erroneous setting in the batch maintenance file m2 have been corrected, and the processing of this subroutine ends, and the process returns to the main program of FIG.

When it is determined in step S2 of FIG. 3 that the received code is not the batch maintenance specification code, it is determined whether or not the mode is another processing specification mode (step S8). A process corresponding to the mode is executed (step S9), and the process ends. The setting of the batch maintenance execution designation mode, etc., and the specification of the input of the PLU code No., which have been described so far, are performed by the numeral keys 2c, # 1 to # 1.
This is performed using the # 4 key.

It should be noted that the present invention is not limited to the above-described embodiment,
For example, the present invention can be applied not only to an electronic register but also to another data processing device such as an electronic computer.

[Effects of the Invention] In correcting a plurality of classification-based data stored in advance by newly inputting a plurality of classification-specific data, the input classification-specific data determined to be capable of being corrected is reduced accordingly. According to the correction mode of the control data stored corresponding to the classification data, the corresponding classification data stored in advance can be corrected immediately.

In addition, for input classification data determined to be impossible to correct, without performing correction based on the classification data, the classification data is output so as to be visible,
The classification data that has not been corrected can be immediately confirmed, so that the classification data can be immediately corrected by the operator.

[Brief description of the drawings]

FIG. 1 is a functional block diagram of the present invention, FIG. 2 is a block diagram of a data processing apparatus according to an embodiment of the present invention, FIGS. 3 to 5 are flowcharts showing the operation of FIG. 2, and FIG. FIG. 9 is a diagram for explaining a problem of the conventional technology. 1 ... CPU, 3 ... RAM, 5 ... Printing part, m1 ... PLU file, m2 ... Batch maintenance file, R ... Register group, P ... Record pointer.

Claims (1)

(57) [Claims] 1. A first storage means for storing a plurality of classification data, a plurality of classification data newly inputted, and correction such as deletion or change in association with each of the classification data. A second storage unit for storing control data indicating an aspect; and correcting a plurality of classification data stored in the first storage unit based on individual classification data stored in the second storage unit. In doing so, for each individual classification data stored in the second storage means, a determination means for determining whether the correction is possible, and a determination is made by the determination means that the correction is possible. The second
Correction means for correcting the corresponding classification data in the first storage means in accordance with the correction mode of the control data stored corresponding to the classification data; For the classified data in the second storage means determined to be impossible to correct by the determining means, the classified data is output so as to be visible without correcting the first storage means. And a visible output unit.