JP3661313B2 - Correction processing device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a correction processing apparatus that corrects input data.
[0002]
[Prior art]
In general, in an electronic cash register, input sales data is accumulated and classified by category, and when the registered sales data is arbitrarily specified and this correction is specified, Correction processing for subtracting the sales data from the cumulative value of the classification (total sales amount or number) is performed.
In this case, conventionally, every time sales data registration operation or correction operation is performed, the operation content is printed and output as an operation history in the journal. By checking the journal report, the number of corrections, etc. Can know.
[0003]
[Problems to be solved by the invention]
By the way, when the registered sales data is corrected, whether the correction is due to the reason of the store side such as an input error or the reason of the customer side such as cancellation is aimed at efficient operation. Although it is a very important factor above, it could not be confirmed from the journal report.
An object of the present invention is to make it possible to easily confirm later why the input data has been corrected.
[0004]
[Means for Solving the Problems]
Means of the present invention are as follows.
The present invention provides a first storage means for storing various correction reasons indicating why the input data is corrected, and the first storage means when the correction of the input data is designated. Display means for reading the correction reason from the storage means and displaying it, selection means for selecting one of the correction reasons displayed and output by the display means, and the correction reason selected by the selection means And a second storage means for storing the correction history in association with the data, and an output means for outputting the correction history stored in the second storage means in association with the reason for correction.
The second storage means stores the number of corrections for each correction reason as a correction history, and each time the correction reason is selected by the selection means, the correction in the second storage means corresponding to the correction reason is stored. Update means for updating the number of times may be provided.
In addition, after registering the input sales data by classification, when the correction of the registered sales data is specified, the sales data processing device that corrects the sales data of the specified classification is used. When the correction is designated, the display means may display and output a correction reason indicating whether the registered sales data is corrected for the reason on the customer side or the reason on the store side.
Further, it is determined whether to execute a correction process for correcting the inventory data in the inventory data storage unit based on the correction reason selected by the selection unit and the inventory data storage unit for storing the inventory data by classification. Processing control means may be provided.
The first storage means stores a correction reason specific to each operator, and when the correction of the input data is designated, the display means performs a correction corresponding to the operator according to the operator who designated the correction. The reason may be read from the first storage means and displayed.
Further, the first storage means stores a correction reason specific to each product, and when the correction of data input for each product is designated, the display means displays the correction reason corresponding to the product. You may make it read out from a memory | storage means and to display-output.
According to the present invention, when the correction of the input data is designated, the reason for correction is read from the first storage means and displayed and output. One of the reasons for correction is selected by the selecting means for indicating. Then, the correction history is stored in the second storage means corresponding to the selected correction reason. The correction history is output in association with the correction reason.
Therefore, it can be easily confirmed later why the input data has been corrected.
[0005]
DETAILED DESCRIPTION OF THE INVENTION
(First embodiment)
Hereinafter, a first embodiment of the present invention will be described with reference to FIGS.
FIG. 1A is a block diagram showing the main configuration of an electronic cash register. This electronic cash register is designed for restaurants and other restaurants. The CPU 1 is a central processing unit that controls the overall operation of the electronic cash register according to various programs stored in the program memory in the RAM 2. is there. The storage medium 3 is composed of a magnetic disk or optical storage medium such as a floppy disk, an optical disk, or a RAM card that can be detachably mounted, and a semiconductor memory, and stores programs and data. In the state where the storage medium 3 is mounted, the program and data in the storage medium 3 are taken into the CPU 1 and stored in the storage device 4. The storage device 4 includes a ROM, a hard disk, an optical disk, and the like, and stores an operating system, various application programs, data files, character font data, and the like. The CPU 1 receives programs and data from other devices through a communication line or the like. Is received and stored in the storage device 4. Further, an input device 5, a display device 6, a printing device 7, and a drawer 8 are connected to the CPU 1 as its input / output peripheral devices, and the CPU 1 controls their input / output operations.
[0006]
The input device 5 includes a keyboard and a pointing device, and various keys that are normally provided are arranged on the keyboard. That is, although not shown on the keyboard, in addition to a numeric keypad for inputting monetary amount data, number, etc., a cursor key, a department key, a PLU (price look-up) key, a cash / deposit key, a VOID (specification correction) key, A mode switch for switching to a registration mode, an inspection mode, a checkout mode, and the like is provided. Sales data (in other words, order data) input from the input device 5 is captured by the CPU 1 and displayed on the display device 6 or printed on a receipt / journal set in the two-pack printer 7. Furthermore, it is registered in the sales totalizer in the RAM 2. The display device 6 is composed of a liquid crystal display device, a CRT display device, or the like that can display data for a plurality of lines, and displays and outputs a registration result or the like in Chinese characters, numbers, other characters, or symbols.
[0007]
FIG. 1B shows the main part of the RAM 2. The RAM 2 includes a program memory 2-1, a memory for one transaction 2-2, a sales totalizer 2-3 for each product, a correction history management file 2-4, A correction processing table 2-5 and the like are provided. Various programs loaded from the storage device 4 or the like are stored in the program memory 2-1. The one-transaction memory 2-2 stores and holds the registration result for one transaction that has been registered from the start of the registration of one transaction until the closing key (cash / deposit key) etc. is operated. Therefore, the CPU 1 reads out data for one screen from the memory 2-2 for one transaction, and displays and outputs it on the registration screen. The contents of the one-transaction memory 2-2 are cleared when a closing key such as a cash / deposit key is operated. The sales totalizer 2-3 for each product stores the total sales for each product and has a configuration as shown in FIG. That is, sales data (total sales quantity and total price) is stored for each product (product code, product name), and inventory data and the number of losses are stored. Here, the inventory data indicates the current inventory quantity, and the value is subtracted by the registered quantity during the registration process by product, but if the registered product is later canceled, it is still cooked. If the product can be returned as stock, the stock data is added by the number of corrections during the correction process. The number of lost items indicates the number of products that could not be returned as stock, and if a registered product was later canceled, the product cannot be returned to stock as if it was cooked. If there is, the number of losses is added by the number of corrections during correction processing.
[0008]
As shown in FIG. 3, the correction history management file 2-4 stores a reason for correction (a kanji mixed sentence) indicating why the registered sales data is corrected. In this case, “registration error” due to operator input error, etc., “order change” request from customer side, “cooking delay” due to inconvenience at store side, request from customer side, etc. “Cancel” …… is stored. The reason for correction excluding “cooking delay” is divided into cooked and uncooked. In association with each correction reason, the correction history management file 2-4 has an area for storing “inventory calculation flag”, “number of cases”, “number”, and “amount”. Here, the “inventory calculation flag” indicates whether or not it can be returned as inventory for each correction reason, “1” indicates that it is not returned as inventory, and “0” indicates that it is returned as inventory. Yes. “Number of cases”, “Number”, and “Amount” indicate the total number, number, and amount of money corrected for each correction reason. The area for storing “reason for correction” and “inventory calculation flag” in the correction history management file 2-4 is a setting area, whereas the area for storing “number of cases”, “number”, and “amount” This is the total area.
[0009]
As shown in FIG. 4A, the correction processing table 2-5 is configured to store various “correction reasons”, “processing flags”, and “key operation guidance” corresponding thereto. Here, the “processing flag” indicates what correction processing should be executed according to the correction reason. When the processing flag is “1”, the number of correction targets is corrected, and when the processing flag is “2”, all are cleared. “3” indicates that product correction should be executed. “Key operation guidance” is guidance data for guiding a key operation procedure for performing a correction operation when the processing flag is “1” or “3”. FIG. 4B specifically illustrates a key operation procedure when a correction operation is performed according to the key operation guidance in this case.
[0010]
Next, the operation of the electronic cash register will be described with reference to the flowcharts shown in FIGS. A program for realizing each function described in this flowchart is stored in the storage medium 3 or the storage device 4 in the form of a program code that can be read by the CPU 1, and the contents of the program are stored in the program memory in the RAM 2. 2-1.
FIG. 5 is a flowchart showing an operation that is started when the mode switch described above is set to the registration mode.
First, in a key input waiting state (step A1), if any key input is performed and it is not a cursor key (NO in step A2), a registration operation is performed according to a predetermined key input procedure. It is checked whether it has been performed (step A3). If an operation for receiving an order from a customer and registering it is performed, the process proceeds to step A4, and normal registration processing is performed. In other words, based on the input sales data for each product, the sales data corresponding to the corresponding product in the total sales counter for each product 2-3 is accumulated, and the process for subtracting the inventory data is performed, or the receipt / journal printing, etc. Is done. The registration result is set in the memory 2-2 for one transaction (step A5). Thereafter, returning to step A1, the above-described operation is repeated each time a registration operation is performed. In this case, the registration results sequentially set in the one-transaction memory 2-2 are read out for one screen and displayed on the registration screen.
[0011]
Here, when the cursor key is operated (step A2), the cursor display (reverse display) in the registration screen is moved or the contents of the registration screen are scrolled (step A6). Now, when the contents of the registration screen are confirmed and the VOID key is operated in a state where the cursor display is aligned with the correction target product position (step A7), the reason for correction is read from the correction processing table 2-5. It is displayed as a pull-down menu on the registration screen (step A8). FIG. 7 shows a display example in this case, and a correction reason pull-down menu is displayed at a substantially central portion in the registration screen. In addition, the case where “tempura set meal set” is designated as the product to be corrected is indicated by the cursor, and the item content specified as the correction target is highlighted as shown in the figure. When the cursor key is operated (Step A9) in order to select the reason for correction from this pull-down menu, the cursor is moved and the screen is scrolled (Step A10). Now, when an arbitrary correction reason is designated by the cursor, the designated correction reason is highlighted as shown in FIG. This is a case where “quantity change” is selected as the reason for correction.
[0012]
After selecting the correction reason in this way, when the confirmation key is operated (step A11), the CPU 1 reads the processing flag in the correction processing table 2-5 corresponding to the correction reason (step A12), and the processing flag. Is determined (step A13). If the processing flag is “1” or “3”, the CPU 1 reads out the key operation guidance corresponding to the correction reason from the correction processing table 2-5, and displays and outputs it in the guidance display area in the registration screen (step). A14). And it waits until correction operation is performed by the key input procedure according to this key operation guidance (step A15), and when correction input operation is performed, it will progress to step A16 and the correction process with respect to memory 2-2 for one transaction will be carried out. Done. In this case, if the quantity is changed according to the procedure shown in FIG. 4B, the number of “tempura set meal sets” to be corrected in the memory 2-2 for one transaction is corrected from 2 to 1, for example. Is done. When the order is changed, “tempura set meal set” is corrected to “eel set meal set”. On the other hand, if it is detected in step A13 that the processing flag is “1”, the process proceeds to step A16, and all the data to be corrected in the memory 2-2 for one transaction is cleared.
[0013]
Then, printing / display processing for designated correction is performed in the same manner as usual (step A17), and processing for correcting the sales data in the sales totalizer 2-3 for each product is performed (step A18). Next, the process proceeds to an inventory correction process, which is executed according to the flowchart of FIG.
First, although the product corrected as described above has been cooked, it is confirmed whether or not it remains uncooked and designated as a key input (step B1). Then, the CPU 1 reads from the correction history management file 2-4 the inventory calculation flag corresponding to the correction reason selected in advance and cooked / uncooked (step B2), and whether the inventory calculation flag is “1”. It is checked whether it is “0” (step B3). Here, if the flag is “0”, processing for restoring the inventory data in the sales totalizer by product 2-3 corresponding to the correction target product is performed (step B4), but if the flag is “1”. Then, a process of updating the number of losses in the sales totalizer 2-3 for each product corresponding to the correction target product is performed (step B5). For example, if the reason for correction is “registration error” or “cancel” and cooking has been completed, “1” is set as the inventory calculation flag, so the number of losses is updated, but the reason for correction is “registration error”. If it is uncooked or the reason for correction is “cooking delay”, “0” is set as the inventory calculation flag, so the inventory data is restored.
Then, the process proceeds to step A20, and a calculation process for the correction history management file 2-4 is performed. That is, the number of items, the number, and the amount in the correction history management file 2-4 corresponding to the correction reason selected this time are updated. Then, the process returns to step A1, and again waits for key input.
[0014]
FIG. 8 is a flowchart showing the operation in the inspection / settlement mode (XZ mode).
First, when the cash / deposit key is operated while waiting for input of the VOID key (step C1) or the cash / deposit key (step C2), the contents of the sales totalizer 2-3 for each product are printed out. Normal processing for issuing an inspection / settlement report is performed (step C3). On the other hand, when the VOID key is operated, processing for printing out the contents of the correction history management file 2-4 and issuing a correction history report for each correction reason is performed (steps C4 to C11). FIG. 9 shows a print example of this correction history report.
First, the header portion of the report is printed, and message data is printed out together with the stamp (step C4). In this case, “Z report” and “specified correction” are printed out as message data as shown in FIG. Next, the first record in the correction history management file 2-4 is addressed (step C5), the data for that one record is read (step C6), and the reason for correction, the number of items, the number, and the amount are printed. Output (step C7). Until the last record in the correction history management file 2-4 is printed (step C8), data for the next one record is designated (step C9), and the number, number and amount of money are associated with the reason for correction. Repeat the operation to print out. As a result, when printing of all records is completed, the current date and time are printed out (step C10), and a report is set (step C11).
[0015]
As described above, in this electronic cash register, before the closing key for ending registration for one transaction is operated, when the registered content is arbitrarily designated and the correction is instructed, The correction reason indicating the reason for correction is read from the correction processing table 2-5 and displayed as a pull-down menu, and the operator selects a correction reason corresponding to the current correction from the list. The number, number, and amount of money in the correction history management file 2-4 corresponding to the reason for correction can be updated according to the correction operation. As a result, it is possible to manage how many designated corrections are made for what reason, and how much the total number and amount of the products are for each correction reason. The contents of the correction history management file 2-4 are printed and output as a correction history report in the specified correction at the time of inspection / settlement. Therefore, the number, number, and amount of money can be confirmed for each correction reason. Therefore, managers etc. analyze the contents of the report, and as a future countermeasure based on the analysis results, for example, if there are many cooking delays, review the equipment and personnel, and if there are many registration mistakes, If there is a lot of necessity, cancellation or order change, you can review the product.
In addition, since an inventory calculation flag indicating whether or not to return as stock for each reason for correction is set, stock management in accordance with the actual situation such as not returning stock that has already been cooked (product) as stock. It becomes possible. In addition, in the case of cooking, it is possible to grasp the number of items lost for each correction reason.
[0016]
(Second Embodiment)
Hereinafter, a second embodiment of the present invention will be described with reference to FIGS. In the above-described first embodiment, the correction reason of the same content is uniformly listed regardless of what kind of product is to be corrected and who is performing the correction operation when performing the specified correction. In this second embodiment, specific correction reasons are stored for each product and for each operator, and a list of correction reasons corresponding to the target product and the operator is displayed at the time of specified correction. It is what I did.
FIG. 10 is a diagram for explaining the sales totalizer in the second embodiment. FIG. 10A shows the configuration of the sales totalizer 2-10 by person in charge, and FIG. 10B shows the sales totalizer 2-11 by product. The structure of is shown. FIG. 11 is a diagram showing the configuration of the correction history management file 2-12 in the second embodiment. In addition, since it is the same as that of 1st Embodiment about others, illustration is abbreviate | omitted.
[0017]
The sales totalizer 2-10 for each person in charge stores and manages sales data for each person in charge who performed the product registration operation. For each “person name (character)” such as manager A, clerk B,. It is configured to store a “password”, “sales data (total sales amount / number)”, and “person in charge designated correction group number”. Here, the “person-in-charge specified correction group No” indicates to which group (level) it belongs in order to make the correction range that can be specified and corrected different depending on the person-in-charge level (manager, part-time job). In order to allow many corrections for manager class personnel, but only limited corrections for part-time and general personnel classes, groups are grouped in advance at each personnel level. Is specified. For example, a group number “1” indicates a group belonging to the manager level, and “0” indicates a group belonging to another person-in-charge level.
[0018]
The sales totalizer 2-11 for each product stores and manages sales data for each product, and stores “sales data (amount / number)” and “product designation correction group number” for each “product name (character)”. It has a configuration. Here, the “product designation correction group No” indicates to which group a product belongs when products are grouped according to whether or not cooking is required. For example, it is possible to forget to take out things that do not need cooking (bread, wine, etc.), but there is no possibility of delay in cooking, and there is a possibility of changing the way of grilling steaks or entering errors, but there is no possibility of canceling the way of cooking. As described above, because the reason for correction differs for each specific product or product group, the product designation correction group No indicates the group to which the product belongs. For example, group No. “1” indicates cooking, and “0” indicates that cooking is not performed.
[0019]
The correction history management file 2-12 corresponds to the classification codes “0-0-3”, “0-1-2”, “1-1-6”, “0-1-5”, etc. as shown in FIG. In the configuration with multiple management files, the first digit of the classification code is the person in charge correction group number, the second digit is the product designation correction group number, the third digit is the number of correction reasons (number of items) ing. Each management file is configured to store an inventory calculation flag, the number of cases, the number, and the amount of money for each correction reason, as in the first embodiment. Here, the first digit of the classification code is “0”, that is, in the management file corresponding to the person in charge of the general person in charge class, the number of reasons for correction is limited to a few items in the illustrated case. The manager class management file stores more correction reasons. Moreover, even if it is a person in charge of the same level, the content and number of reasons for correction differ according to goods (for example, depending on whether it cooks).
[0020]
Also in the second embodiment configured as described above, in the registration mode, the operation is performed almost simultaneously according to the flowchart of FIG. 5 described above, and therefore the flowchart is omitted. Hereinafter, only the characteristic part of the second embodiment will be described. explain.
First, when switching to the registration mode, the personal identification number of the person in charge is input. Each time the registration operation for each product is performed, the sales data in the sales totalizer 2-10 for each person in charge corresponding to the person in charge is accumulated and the sales total for each product 2-11 corresponding to that product is stored. It is the same as usual that the sales data is accumulated. Here, when the VOID key is operated to perform the specified correction, the CPU 1 accesses the corresponding classification code in the correction history management file 2-12 based on the person in charge and the product to be corrected, and corresponds to this classification code. The reason for correction is read from the management file to be displayed and displayed as a pull-down menu. In this case, the first digit of the classification code is the person-in-charge specified correction group number, the second digit is the product-specific correction group number, and the designated correction group number corresponding to the current person in charge is assigned to the sales total by person in charge 2-10. The specified correction group number corresponding to the product specified as the correction target is read from the sales totalizer 2-11 for each product and the correction history management file 2-12 is accessed. As a result, a list of reasons for correction for each person in charge and product is displayed. When the reason for correction is selected from this list display to indicate the reason for correction this time, the number, number, and amount of money corresponding to the reason for correction are accumulated, as in the case described above.
[0021]
This second embodiment also has the same effect as the first embodiment described above, and since the individual correction reason is displayed according to the person in charge and the product, it becomes more realistic and more detailed. Correction history can be managed. Further, the contents of the correction history management file 2-12 are printed in the same manner as in the first embodiment at the time of inspection / settlement, but in this case, a report for each person in charge and for each product can be issued. . In this case, since the manager and the owner can grasp from the report contents the actual state in which each person in charge has made the specified correction, it can be used for preventing fraud of the operator.
[0022]
In each embodiment described above, the contents of the correction history management file are printed as a report at the time of inspection / settlement. However, the contents may be displayed as a list on the display screen. In addition, the correction history management file stores the number, the number, and the amount of money for each correction reason, and the contents are updated every time the specified correction is performed. The correction reasons may be written in association with each other. Further, the correction reason may be written together with the correction data in the journal memory when the designated correction is performed.
Further, although the description has been given by taking the designated correction as an example, the correction history for each correction reason may be managed in the same manner when the last correction or the reverse correction is performed.
Furthermore, the number of corrections may be stored for each reason for correction indicating an input error or a conversion error at the time of Kanji conversion in a word processor, personal computer, or the like, not limited to a sales data processing device such as an electronic cash register. . Another reason for correction may be a format or a setting error at the time of format setting.
Although the reasons for correction are displayed as a list of character string data, the reasons for correction may be expressed by graphics, pictures, photographs, or the like.
[0023]
【The invention's effect】
According to the present invention, when the correction of the input data is instructed, the reason for correction is displayed and output, the correction history is stored in association with the correction reason selected from among the reasons, and if necessary, Since the correction history is output in association with the reason for correction, it can be easily confirmed later why the input data has been corrected. It can help to take measures.
[Brief description of the drawings]
FIG. 1A is a block diagram showing a main configuration of an electronic cash register, and FIG. 1B shows the contents of a RAM 2;
FIG. 2 is a diagram for explaining a configuration of a product-based sales totalizer 2-3.
FIG. 3 is a diagram for explaining a configuration of a correction history management file 2-4.
FIG. 4 is a view for explaining the configuration of a correction processing table 2-5.
FIG. 5 is a flowchart showing an operation when switching to a registration mode.
6 is a flowchart for explaining step A19 (inventory correction processing) in FIG. 5;
FIG. 7 is a view showing a state in which a reason for correction is displayed as a pull-down menu on a registration screen.
FIG. 8 is a flowchart showing an operation when the mode is switched to an inspection / payment mode.
FIG. 9 is a diagram exemplifying report contents in which a correction history is printed for each correction reason.
10A and 10B show a sales totalizer in the second embodiment, in which FIG. 10A shows the configuration of a sales totalizer 2-10 by person in charge, and FIG. 10B shows the configuration of a sales totalizer 2-11 by product.
FIG. 11 is a diagram showing a configuration of a correction history management file 2-12 in the second embodiment.
[Explanation of symbols]
1 CPU
2 RAM
2-1 Program memory
2-2 Memory for one transaction
2-3, 2-11 Sales total by product
2-4, 2-12 Correction history management file
2-5 Correction processing table
2-10 Total Sales Unit by Person in Charge
3 storage media
4 storage devices
5 input devices
6 Display device

Claims (6)

First storage means for storing various correction reasons indicating why the input data is corrected;
Display means for reading out and displaying the reason for correction from the first storage means when correction of input data is designated;
A selection means for selecting one of the correction reasons displayed and output by the display means;
Second storage means for storing the correction history in association with the correction reason selected by the selection means;
A correction processing apparatus comprising: output means for outputting the correction history stored in the second storage means in association with the reason for correction. The second storage means stores the number of corrections for each correction reason as a correction history,
2. The correction processing apparatus according to claim 1, further comprising an updating unit that updates the number of corrections in the second storage unit corresponding to the correction reason each time a correction reason is selected by the selection unit. . In the sales data processing device that corrects the sales data of the specified classification when the entered sales data is registered by classification and the correction of the registered sales data is specified,
When the registered sales data is specified to be corrected, the display means displays and outputs a correction reason indicating whether the registered sales data is corrected for the reason on the customer side or the reason on the store side. The correction processing apparatus according to claim 1. Inventory data storage means for storing inventory data by classification;
2. The process control means for determining whether or not to execute a correction process for correcting the inventory data in the inventory data storage means based on the reason for correction selected by the selection means. Correction processing equipment. The first storage means stores a correction reason specific to each operator,
When the correction of the input data is designated, the display means reads out the reason for correction corresponding to the operator from the first storage means and outputs the display reason according to the operator who designated the correction. The correction processing apparatus according to claim 1, wherein: The first storage means stores a correction reason specific to each product,
The display means reads out a correction reason corresponding to the product from the first storage means and displays it when a correction of data inputted for each product is designated. The correction processing apparatus described.

Images