JP2015179475A - Selling registration device and control program therefor - Google Patents

Abstract

PROBLEM TO BE SOLVED: To easily confirm selling registrations which were respectively handled by plural employees.SOLUTION: A selling registration device of the embodiment comprises: registration means; update means; extraction means; and creation means. The registration means performs selling registration according to operation by a handling person. The update means updates a history database so that the history database includes information about selling registration which is performed by the registration means and history information capable of identifying the handling person. The setting means sets plural employees as object employees according to an instruction of an operator. The extraction means extracts from the history database the history information related to the selling registration, which is performed by the object employee as the handling person, about each of the plural object employees set by the setting means. The creation means creates an image indicating the history information extracted by the extraction means.

Description

  Embodiments described herein relate generally to a sales registration apparatus and a control program thereof.

  A sales registration apparatus such as a POS (point-of-sale) terminal apparatus may hold a history database. The history database is configured by accumulating history information regarding individual sales registrations executed. There are various types of information included in the history information. For example, the date and time when the sales registration was executed, the product code of the sold product, the product name and price, the settlement method, or the employee's employee An employee code is assumed.

  Then, the sales registration apparatus extracts history information about one designated employee from the history database, and prints the extracted history information on a receipt sheet, for example.

  By confirming the information output in this way, it is possible to perform various managements such as confirming the results of sales registration performed in the past.

  However, since the output of history information is for each employee as described above, if you want to manage sales registration handled by multiple employees, you must check the history information for each employee individually. did not become.

  Under such circumstances, it has been desired to easily confirm the sales registration handled by each of the plurality of employees.

JP 2007-128295 A

  The problem to be solved by the present invention is to provide a sales registration apparatus and its control program that can easily confirm sales registration handled by a plurality of employees.

  The sales registration apparatus according to the embodiment includes a registration unit, an update unit, an extraction unit, and a generation unit. The registration means performs sales registration according to the operation by the operator. The update means updates the history database to include history information that includes information related to the sales registration performed by the registration means and that enables the operator to be identified. The setting means sets a plurality of employees as target employees in accordance with an instruction from the operator. For each of the plurality of target employees set by the setting unit, the extraction unit extracts, from the history database, history information related to sales registration performed by the target employee serving as a handler. The generation unit generates an image representing the history information extracted by the extraction unit.

The block diagram of the POS terminal which concerns on one Embodiment. The flowchart of CPU in FIG. 1 in the control processing at the time of setting registration mode. The flowchart of CPU in FIG. 1 in the control processing at the time of setting of inspection mode. The flowchart of CPU in FIG. 1 in the control processing at the time of setting of inspection mode. The flowchart of CPU in FIG. 1 in the control processing at the time of setting of inspection mode. The figure which shows a main screen. The figure which shows a range designation | designated screen. The figure which shows an inspection screen. The figure which shows the receipt paper on which the log | history image was printed.

  Hereinafter, an example of the embodiment will be described with reference to the drawings. In the present embodiment, a point-of-sale (POS) terminal will be described as an example of the sales registration device.

  FIG. 1 is a block diagram of a POS terminal 1 according to the present embodiment.

  The POS terminal 1 is included in the order processing system 100. The order processing system 100 can be used in various facilities that provide various services such as a restaurant service and a product sales service in accordance with customer orders such as restaurants and dealers. However, in the following, the order processing system 100 configured to be adapted for use in restaurants will be described.

  The order processing system 100 is configured by connecting a POS terminal 1, a plurality of handy terminals 2, and a plurality of slip printers 3 to a local area network (LAN) 4, respectively. However, the handy terminal 2 is connected to the LAN 4 via the wireless access point 5. Although two handy terminals 2 and slip printers 3 are illustrated in FIG. 1, the number thereof is arbitrary.

  The POS terminal 1 is installed on a customer service floor or a checkout counter, for example. The POS terminal 1 performs processing related to various operations such as guidance to customers, order reception, serving (delivery), accounting, or inspection. Order receiving is a business for registering sales of products ordered by customers. The inspection is an operation for confirming the record of sales registration.

  The handy terminal 2 is a terminal device for inputting a store clerk's operation for order entry. The handy terminal 2 generates order information according to the input operation, and wirelessly transmits the order information. The order information wirelessly transmitted from the handy terminal 2 is transmitted to the POS terminal 1 via the wireless access point 5 and the LAN 4. Upon receiving the order information, the POS terminal 1 performs sales registration processing according to the order information. Also, the POS terminal 1 generates image data representing an order slip for notifying order information to employees in charge of flooring or cooking, and transmits the image data to the slip printer 3.

  The slip printer 3 is installed on, for example, a customer service floor or a kitchen. Upon receiving the image data, the slip printer 3 prints an image represented by the image data on a slip sheet and discharges it. Thus, the slip printer 3 issues an order slip.

  The POS terminal 1 includes a CPU (central processing unit) 11, a ROM (read-only memory) 12, a RAM (random-access memory) 13, an auxiliary storage device 14, a clock unit 15, an operator touch panel 16, and a customer display 17. A receipt printer 18, a journal printer 19, a card reader 20, a communication device 21, and a transmission system 22.

  The CPU 11 corresponds to the central part of the computer. The CPU 11 controls each unit to implement various operations as the POS terminal 1 based on the operating system, middleware, and application program stored in the ROM 12 and the auxiliary storage device 14.

  The ROM 12 corresponds to a main storage part of the computer. The ROM 12 stores the above operating system. The ROM 12 may store the above middleware and application programs. The ROM 12 may store data that is referred to when the CPU 11 performs various processes.

  The RAM 13 corresponds to the main storage portion of the computer. The RAM 13 stores data to be referred to when the CPU 11 performs various processes. Further, the RAM 13 is used as a so-called work area for storing data temporarily used when the CPU 11 performs various processes. A part of the storage area of the RAM 13 is used as a product list area.

  The auxiliary storage device 14 corresponds to an auxiliary storage portion of the computer. The auxiliary storage device 14 is, for example, a hard disk drive (HDD) or a solid state drive (SSD), and stores data used when the CPU 11 performs various processes and data generated by the processes in the CPU 11. . The auxiliary storage device 14 may store the above operating system, middleware, or application program. As shown in FIG. 1, the auxiliary storage device 14 stores a history database (history DB) 14a.

  The history database 14 a is a set of history information including various information related to sales registration performed at the POS terminal 1. What information is included in the history information is arbitrary, but includes at least an employee code for identifying an employee who has been a sales registration handler. The history information may include the date and time when the sales registration was executed, the product code of the product, the product name and sales price, and the settlement method.

  The application program stored in the ROM 12 or the auxiliary storage device 14 includes a control program described regarding control processing described later. The transfer of the POS terminal 1 is generally performed in a state where the control program is stored in the ROM 12 or the auxiliary storage device 14. However, the POS terminal 1 is transferred in a state where the control program is not stored in the ROM 12 or the auxiliary storage device 14, and is recorded on a removable recording medium such as a magnetic disk, a magneto-optical disk, an optical disk, or a semiconductor memory, Alternatively, the control program may be transferred via a network, and the control program may be written in the ROM 12 or the auxiliary storage device 14 of the POS terminal 1 that is separately transferred.

  The clock unit 15 performs a timekeeping operation on a regular basis, and generates date / time information representing the date and time. For the clock unit 15, for example, a TOD (time of day) clock can be used.

  The operator touch panel 16 can display an arbitrary image under the control of the CPU 11. The image displayed on the operator touch panel 16 is mainly an image representing information to be notified to the operator. The operator touch panel 16 inputs a touch operation on the display image by the operator.

  The customer display 17 can display an arbitrary image under the control of the CPU 11. The image displayed on the customer display 17 is mainly an image representing information to be notified to the customer.

  The receipt printer 18 is, for example, a thermal printer or a dot impact printer, and issues receipts to be handed to customers by printing various character strings and images on receipt paper.

  The journal printer 19 is, for example, a thermal printer or a dot impact printer, and creates a storage journal by printing various character strings and images on journal paper.

  The card reader 20 reads information recorded on the employee card. The information recorded on the employee ID includes an employee code. The card reader 20 includes a barcode reader that reads a barcode visually displayed on the employee ID, a magnetic card reader that reads information magnetically recorded on the employee ID, and information that is transmitted wirelessly by the IC chip in the employee ID. Various known types such as a contactless card reader for receiving are arbitrarily used.

  The communication device 21 communicates with the handy terminal 2 and the slip printer 3 via the LAN 4. As the communication device 21, for example, an existing LAN communication device is used.

  The transmission system 22 includes data between the CPU 11, ROM 12, RAM 13, auxiliary storage device 14, clock unit 15, operator touch panel 16, customer display 17, receipt printer 18, journal printer 19, card reader 20 and communication device 21. Is transmitted. The transmission system 22 may be a well-known system including various buses such as a system bus, and various interface circuits that connect these buses and each unit.

  Now, the employee in charge of customer service has one handy terminal 2 each. Then, the employee who has received the order from the customer inputs the contents into the handy terminal 2. The handy terminal 2 generates order information having contents corresponding to the above input, and wirelessly transmits the order information. In addition to the identification information of the ordered product (hereinafter referred to as product information), the order information includes employee identification information (hereinafter referred to as employee information) and customer identification information (hereinafter referred to as customer information). Including). The employee information is an employee code assigned to each employee or a device code unique to the handy terminal 2. When the employee code is used as the employee information, for example, when the employee starts using the handy terminal 2, the employee code is input to the handy terminal 2. The handy terminal 2 stores this employee code as employee information and includes it in the order information. When a device code is used as employee information, a code held by the handy terminal 2 such as a MAC address may be used. The customer information temporarily identifies the customer during the period from when the customer comes to the store until the accounting is completed. For example, a customer seat code assigned to a customer seat at the store is used.

  Next, the operation of the POS terminal 1 will be described. Note that the content of the processing by the CPU 11 described below is an example, and the order of the processing can be changed as appropriate, or various processing that can obtain a similar result can be used.

  The POS terminal 1 has several operation modes including a registration mode and an inspection mode. When any of the selection buttons for each mode provided on the operation screen displayed on the operator touch panel 16 is touched, the CPU 11 sets the mode associated with the selection button as the operation mode.

  FIG. 2 is a flowchart of the CPU 11 in the control process when setting the registration mode.

  The CPU 11 executes the control process shown in FIG. 2 by executing the control program stored in the ROM 12 or the auxiliary storage device 14.

  In Act 1, the CPU 11 confirms whether or not the order information transmitted from the handy terminal 2 has been received by the communication device 21 as described above. If the CPU 11 determines NO because the order information has not been received, the CPU 11 proceeds to Act2.

  In Act 2, the CPU 11 confirms whether or not the start of the accounting process is instructed. If the CPU 11 determines NO because the operation for instructing the start of the accounting process is not performed, the CPU 11 returns to Act1.

  Thus, the CPU 11 waits for Act 1 and Act 2 to receive the order information or to instruct the start of accounting. If the order information is received, the CPU 11 determines YES in Act 1 and proceeds to Act 3. When the order information arrives via the LAN 4, the communication device 21 receives this order information. The communication device 21 stores the received order information in the RAM 13 or the auxiliary storage device 14 and notifies the CPU 11 that the order information has been received.

  In Act 3, the CPU 11 confirms whether or not the registration data including the customer information included in the received order information is already stored in the auxiliary storage device 14. If the CPU 11 determines NO because there is no corresponding registration data, the CPU 11 proceeds to Act4.

  In Act 4, the CPU 11 creates registration data as information in which the customer information included in the order information is associated with a data record including product information included in the order information, employee information, order date and time, and the like. Is stored in the auxiliary storage device 14. The CPU 11 includes the current date and time output from the clock unit 15 in the registration data as the order date and time. Thereafter, the CPU 11 returns to the standby state for Act1 and Act2.

  When order information based on the additional order by the customer is received by the communication device 21, the registration data including the customer information included in the order information is already stored in the auxiliary storage device 14 by the processing of Act4. . For this reason, when the CPU 11 proceeds from Act1 to Act3 in response to the reception of such order information, it determines YES in Act3. In this case, the CPU 11 proceeds to Act5.

  In Act 5, the CPU 11 updates the registration data including the customer information included in the received order information. That is, the CPU 11 adds to the corresponding registration data a data record configured to include employee information and product information included in the order information received this time, the current date and time output by the clock unit 15, and the like. Thereafter, the CPU 11 returns to the standby state for Act1 and Act2.

  As described above, sales registration relating to the ordered product is performed. When the CPU 11 executes the above-described control processing based on the control program, the computer having the CPU 11 as a central part functions as a registration unit. Although not shown, the CPU 11 generates image data representing an order slip for notifying the received order information to the floor staff or the employee in charge of cooking, and transmits the image data to the slip printer 3. .

  On the other hand, when an account is requested by a customer, the employee performs an operation for instructing the start of accounting on the operator touch panel 16. In response to this, the CPU 11 determines YES in Act 2 and proceeds to Act 6.

  In Act 6, the CPU 11 performs an accounting process. Specifically, in response to designation of customer information by the employee, the total amount related to the products registered in the registration data including the customer information is calculated, and processing for settlement of the total amount is performed. A more specific process of the accounting process may be the same as that of an existing similar device.

  In Act 7, the CPU 11 adds the history information consisting of a set of each data record included in the registration data subject to the current accounting to the history database 14a stored in the auxiliary storage device 14, thereby making the history database 14a. Update. Thus, when the CPU 11 executes the above-described control processing based on the control program, the computer having the CPU 11 as a central part functions as an updating unit.

  In Act 8, the CPU 11 deletes the registration data that is the subject of the current transaction from the auxiliary storage device 14. Thereafter, the CPU 11 returns to the standby state for Act1 and Act2.

  FIG. 3 is a flowchart of the CPU 11 in the control process when the inspection mode is set.

  By executing the control program stored in the ROM 12 or the auxiliary storage device 14, the CPU 11 executes the control processing shown in FIGS. 3, 4 and 5.

  First, in Act 11 shown in FIG. 3, the CPU 11 controls the operator touch panel 16 to display the top screen. The top screen represents a GUI (graphical user interface) for selecting various types of work related to the check work, and includes a button for designating work for checking the record of sales registration by operator.

  In Act 12, the CPU 11 confirms whether or not the top screen has been touched by the operator. Specifically, it is confirmed whether or not detection information related to a touch within the range of the top screen is output from the operator touch panel 16. If the corresponding detection information is not output, the CPU 11 determines NO and repeats Act12. Thus, in Act 12, the CPU 11 waits for the top screen to be touched. If the top screen is touched, the CPU 11 determines YES in Act 12, and proceeds to Act 13.

  In Act 13, the CPU 11 confirms whether or not the touch is a touch on a button for designating a task for confirming a record of sales registration by operator (hereinafter referred to as an operator-specific inspection task). . Then, the CPU 11 determines NO if a button other than the corresponding button is touched, and proceeds to processing according to the touched position. Since the processing at this time is not a feature of the present embodiment, description thereof is omitted. On the other hand, if the corresponding button has been touched, the CPU 11 determines YES in Act 13 and proceeds to Act 14.

  In Act 14, the CPU 11 controls the operator touch panel 16 to display a main screen for the operator-specific inspection work.

  FIG. 6 is a diagram showing the main screen 30.

  In the main screen 30, a correction button 31, an end button 32, an all designation button 33, a range designation button 34, and a display button 35 are arranged.

  In Act 15, the CPU 11 confirms whether or not the main screen 30 has been touched by the operator. If the detection information related to the touch within the range of the main screen 30 is not output from the operator touch panel 16, the CPU 11 determines NO and repeats Act15. Thus, the CPU 11 waits for the main screen 30 to be touched in Act 15. If the main screen 30 is touched, the CPU 11 determines YES in Act 15 and proceeds to Act 16.

  In Act 16, the CPU 11 confirms whether or not the touch is a touch on the end button 32. If the detection information related to the touch within the range of the end button 32 is output from the operator touch panel 16, the CPU 11 determines YES and returns to Act 11. However, if the detection information regarding the touch within the range of the end button 32 is not output, the CPU 11 determines NO in Act 16 and proceeds to Act 17.

  In Act 17, the CPU 11 confirms whether or not the above touch is a touch on the all designation button 33. Then, the CPU 11 determines YES if the detection information related to the touch within the range of all the designation buttons 33 is output from the operator touch panel 16, and proceeds to Act 18.

  In Act 18, the CPU 11 sets the smallest one of the employee codes as the start code of the employee code range that is the object of history confirmation.

  In Act 19, the CPU 11 sets the largest one of the employee codes as the end code of the employee code range that is the object of history confirmation. Thereafter, the CPU 11 returns to Act 14 and performs the subsequent processing in the same manner as described above.

  If the detection information related to the touch within the range of all the designation buttons 33 is not output from the operator touch panel 16, the CPU 11 determines NO in Act 17 and proceeds to Act 20.

  In Act 20, the CPU 11 confirms whether or not the above touch is a touch on the range designation button 34. If the detection information related to the touch within the range of the range designation button 34 is output from the operator touch panel 16, the CPU 11 determines YES and proceeds to Act 21 shown in FIG.

  In Act 21, the CPU 11 controls the operator touch panel 16 to display a range designation screen.

  FIG. 7 is a diagram showing a range designation screen 40.

  In the range designation screen 40, a correction button 41, a confirmation button 42, a start code button 43, an end code button 44, a start code area 45, an end code area 46, and a list area 47 are arranged. The start code area 45 displays the employee code set as the start code. The end code area 46 displays the employee code set as the end code. The list area 47 displays a list of employee codes.

  In Act 22, the CPU 11 sets the setting target as a start code.

  In Act 23, the CPU 11 confirms whether or not the employee card has been read by the card reader 20. If the card reader 20 has not read the employee card, the CPU 11 determines NO and proceeds to Act 24.

  In Act 24, the CPU 11 confirms whether or not the range designation screen 40 has been touched by the operator. Then, the CPU 11 determines NO if the detection information related to the touch within the range of the range designation screen 40 is not output from the operator touch panel 16, and returns to Act 23.

  Thus, in Acts 23 and 24, the CPU 11 waits for either reading of the employee ID card or touching of the range designation screen 40. If the operator uses the employee code recorded on the employee ID as a history check target, the operator causes the card reader 20 to read the employee ID when the CPU 11 is in this standby state. When the card reader 20 reads the information recorded on the employee ID card, the card reader 20 writes this information in the RAM 13 and notifies the CPU 11 accordingly. Upon receiving this notification, the CPU 11 determines YES in Act 23, and proceeds to Act 25.

  In Act 25, the CPU 11 sets the employee code included in the information read by the card reader 20 as the start code.

  In Act 26, the CPU 11 sets the employee code included in the information read by the card reader 20 as the end code. Thereafter, the CPU 11 returns to the standby state of Acts 23 and 24.

  That is, when the employee card is read by the card reader 20, only the employee code recorded on the employee card is defined as the employee code range.

  On the other hand, if the range designation screen 40 is touched, the CPU 11 determines YES in Act 24 and proceeds to Act 27.

  In Act 27, the CPU 11 confirms whether or not the touch is a touch on the start code button 43. If the detection information related to the touch outside the range of the start code button 43 is output from the operator touch panel 16, the CPU 11 determines NO and proceeds to Act 28.

  In Act 28, the CPU 11 confirms whether or not the touch is a touch on the end code button 44. If the detection information related to the touch outside the range of the end code button 44 is output from the operator touch panel 16, the CPU 11 determines NO, and proceeds to Act 29.

  In Act 29, the CPU 11 confirms whether or not the touch is a touch on the correction button 41. If the detection information related to the touch outside the range of the correction button 41 is output from the operator touch panel 16, the CPU 11 determines NO and proceeds to Act 30.

  In Act 30, the CPU 11 confirms whether or not the touch is a touch on the list area 47. If the detection information related to the touch outside the range of the list area 47 is output from the operator touch panel 16, the CPU 11 determines NO and proceeds to Act31.

  In Act 31, the CPU 11 confirms whether or not the touch is a touch on the confirmation button 42. If the detection information related to the touch outside the range of the confirmation button 42 is output from the operator touch panel 16, the CPU 11 determines NO and returns to the standby state of Acts 23 and 24.

  Thus, in Acts 27 to 31, the CPU 11 touches the range designation screen 40 made by the operator by touching any one of the start code button 43, the end code button 44, the correction button 41, the list area 47 and the confirmation button 42. Check if it exists. If the CPU 11 confirms that the touch is not touching any of the start code button 43, the end code button 44, the correction button 41, the list area 47, and the confirmation button 42, the CPU 11 does not start any processing for the current touch. Return to the standby state of Acts 23 and 24.

  If the detection information related to the touch within the range of the start code button 43 is output from the operator touch panel 16, the CPU 11 determines YES in Act 27, and returns to Act 22. That is, if the start code button 43 is touched, the CPU 11 sets the setting target as the start code.

  If the detection information related to the touch within the range of the end code button 44 is output from the operator touch panel 16, the CPU 11 determines YES in Act 28, and proceeds to Act 32.

  In Act 32, the CPU 11 sets the setting target as an end code. Thereafter, the CPU 11 returns to the standby state of Acts 23 and 24. That is, if the end code button 44 is touched, the CPU 11 sets the setting target code as the end code.

  If the detection information regarding the touch within the range of the correction button 41 is output from the operator touch panel 16, the CPU 11 determines YES in Act 29 and returns to Act 14 shown in FIG. Then, the CPU 11 performs the processing after Act 14 in the same manner as described above. That is, if the correction button 41 is touched, the CPU 11 returns to a standby state where it waits for a touch operation on the main screen 30.

  If the detection information related to the touch within the range of the list area 47 is output from the operator touch panel 16, the CPU 11 determines YES in Act 30, and proceeds to Act 33.

  In Act 33, the CPU 11 confirms whether the setting target is a start code. If the CPU 11 determines YES because the setting target is a start code, the CPU 11 proceeds to Act 34.

  In Act 34, the CPU 11 sets an employee code (hereinafter referred to as a touch code) displayed at the touched position in the list area 47 as a start code.

  In Act 35, the CPU 11 checks whether any of the employee codes has been set as the end code. If none of the employee codes has been set as the end code, the CPU 11 determines NO and proceeds to Act 36. If the CPU 11 determines NO in Act 33 because the setting target is the end code, the CPU 11 passes Acts 34 and 35 and proceeds to Act 36.

  In Act 36, the CPU 11 sets the touch code as the end code. Thereafter, the CPU 11 proceeds to Act 37. If any of the employee codes has been set as the end code, the CPU 11 determines YES in Act 35, passes Act 36, and proceeds to Act 37.

  In Act 37, the CPU 11 updates the range designation screen 40 so that the start code and the end code set at this time are displayed in the start code area 45 and the end code area 46, respectively. Thereafter, the CPU 11 returns to the standby state of Acts 23 and 24.

  If the detection information related to the touch within the range of the confirmation button 42 is output from the operator touch panel 16, the CPU 11 determines YES in Act 31, and returns to Act 14 shown in FIG. Then, the CPU 11 performs the processing after Act 14 in the same manner as described above. That is, when the confirmation button 42 is touched, the CPU 11 returns to a standby state in which it waits for a touch operation on the main screen 30.

  If the main screen 30 is touched and the detection information related to the touch within the range of the range designation button 34 is output from the operator touch panel 16, the CPU 11 determines YES in Act 20, and proceeds to Act 38.

  In Act 38, the CPU 11 confirms whether or not the touch is a touch on the display button 35. If the detection information related to the touch within the range of the display button 35 is output from the operator touch panel 16, the CPU 11 determines YES in Act 38, and proceeds to Act 39 shown in FIG. The CPU 11 determines NO if the detection information related to the touch outside the range of the display button 35 is output from the operator touch panel 16, and shifts to another process corresponding to the touch position. In other processes, the CPU 11 may set various conditions other than the employee code range such as the period, day of the week, time zone, sales type, and total / average according to the operation of the operator.

  In Act 39, the CPU 11 extracts, from the history database 14a, history information that includes an employee code within the employee code range and that meets other set conditions. Thus, when the CPU 11 executes the above-described control processing based on the control program, the computer having the CPU 11 as a central part functions as an extraction unit. Further, the employee identified by the employee code within the employee code range is the target employee, and the computer having the CPU 11 as the central part functions as a setting means.

  In Act 40, the CPU 11 generates a history image representing the extracted history information. Thus, when the CPU 11 executes the above-described control processing based on the control program, the computer having the CPU 11 as a central part functions as a generating unit.

  In Act 41, the CPU 11 controls the operator touch panel 16 to display an inspection screen.

  FIG. 8 is a diagram showing an inspection screen 50.

  The inspection screen 50 includes a history image 51 and a condition display area 52 that represents conditions applied to the creation of the history image 51. The inspection screen 50 includes a print button 53, a correction button 54, and an end button 55.

  In Act 42, the CPU 11 confirms whether or not the inspection screen 50 is touched by the operator. Then, the CPU 11 determines NO if the detection information regarding the touch within the range of the inspection screen 50 is not output from the operator touch panel 16, and repeats Act42. Thus, in Act 42, the CPU 11 waits for the inspection screen 50 to be touched. If the detection information related to the touch within the range of the inspection screen 50 is output from the operator touch panel 16, the CPU 11 determines YES in Act 43 and proceeds to Act 43.

  In Act 43, the CPU 11 confirms whether or not the touch is a touch on the end button 55. If the detection information related to the touch outside the range of the end button 55 is output from the operator touch panel 16, the CPU 11 determines NO and proceeds to Act 44.

  In Act 44, the CPU 11 checks whether or not the touch is a touch on the correction button 54. If the detection information related to the touch outside the range of the correction button 54 is output from the operator touch panel 16, the CPU 11 determines NO, and proceeds to Act 45.

  In Act 45, the CPU 11 checks whether or not the touch is a touch on the print button 53. If the detection information related to the touch outside the range of the print button 53 is output from the operator touch panel 16, the CPU 11 determines NO and returns to the Act 42 standby state.

  Thus, in Acts 43 to 45, the CPU 11 confirms whether or not the touch on the inspection screen 50 made by the operator is a touch on any of the end button 55, the correction button 54, and the print button 53. If the CPU 11 confirms that it is not a touch on any of the end button 55, the correction button 54, and the print button 53, the CPU 11 returns to the standby state of Act 42 without starting any processing for the current touch.

  If the detection information related to the touch within the range of the print button 53 is output from the operator touch panel 16, the CPU 11 determines YES in Act 45, and proceeds to Act 46.

  In Act 46, the CPU 11 controls the receipt printer 18 and the journal printer 19 to print the history image on the receipt paper and the journal paper. Thereafter, the CPU 11 returns to the standby state of Act43. Thus, when the CPU 11 executes the above-described control processing based on the control program, the computer having the CPU 11 as a central part functions as a control means.

  If the detection information related to the touch within the range of the end button 55 is output from the operator touch panel 16, the CPU 11 determines YES in Act 43, and returns to Act 11 shown in FIG. Then, the CPU 11 performs the processing after Act 11 in the same manner as described above. That is, when the end button 55 is touched, the CPU 11 returns to a state of waiting for a touch operation on the top screen.

  If the detection information related to the touch within the range of the correction button 54 is output from the operator touch panel 16, the CPU 11 determines YES in Act 44 and returns to Act 14 shown in FIG. Then, the CPU 11 performs the processing after Act 14 in the same manner as described above. That is, if the correction button 41 is touched, the CPU 11 returns to a state of waiting for a touch operation on the main screen 30.

  FIG. 9 is a view showing a receipt sheet on which a history image is printed.

  As described above, according to the POS terminal 1, when a plurality of employee codes are included in the employee code range set in accordance with the operator's instruction, the history information including the plurality of employee codes is respectively displayed. A history image extracted from the history database 14a and representing them is generated. The history image is displayed on the operator touch panel 16 and further printed on a receipt sheet in accordance with an instruction from the operator.

  Thus, the operator can easily confirm the sales registration handled by a plurality of employees from the history image displayed on the operator touch panel 16 or the history image printed on the receipt paper.

  Further, when printing the history image on the receipt paper, the POS terminal 1 prints the same history image on the journal paper. Therefore, it is possible to verify afterwards what kind of information has been browsed by confirming the print contents on the journal paper.

  This embodiment can be variously modified as follows.

  The history image may be sent from the POS terminal 1 to the management terminal (not shown), the handy terminal 2 or the like via the LAN 4. The history image may be displayed or printed under the control of the management terminal or the handy terminal 2.

  Although several embodiments of the present invention have been described, these embodiments are presented by way of example and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 1 ... POS terminal, 2 ... Handy terminal, 3 ... slip printer, 4 ... LAN, 5 ... wireless access point, 11 ... CPU, 12 ... ROM, 13 ... RAM, 14 ... auxiliary storage device, 14a ... history database, 15 ... Clock unit, 16 ... touch panel for operator, 17 ... customer display, 18 ... receipt printer, 19 ... journal printer, 20 ... card reader, 21 ... communication device, 22 ... transmission system.

Claims (6)

A registration means for performing sales registration in response to an operation by the operator;
Update means for updating the history database to include history information that includes information related to the sales registration made by the registration means and that enables the operator to be identified;
A setting means for setting a plurality of employees as target employees in response to an instruction from the operator,
For each of a plurality of target employees set by the setting means, an extraction means for extracting history information related to sales registration performed by the target employee as a handler, from the history database;
A sales registration apparatus comprising: a generation unit that generates an image representing the history information extracted by the extraction unit. A receipt printer that prints an image representing the contents of the sales registration performed by the registration means on a receipt sheet and discharges it;
2. The sales registration apparatus according to claim 1, further comprising control means for controlling the receipt printer so as to print the image generated by the generating means on the receipt paper. A journal printer that prints an image representing the contents of the sales registration performed by the registration means on journal paper;
3. The sales registration apparatus according to claim 2, wherein the control unit further controls the journal printer to print the image generated by the generation unit on the journal sheet.   The setting means specifies two identification numbers for identifying each of the employees in accordance with an instruction from the operator, and is identified by all the identification numbers included in a range between the two identification numbers. The sales registration device according to any one of claims 1 to 3, wherein all of the employees are set as the target employees. Under the operation of the operator, further comprising reading means for reading the identification number,
5. The sales registration apparatus according to claim 4, wherein the setting unit sets an identification number selected under the operation of the operator from the list of identification numbers as one of the two identification numbers. A computer for controlling the sales registration device,
A registration means for performing sales registration in response to an operation by the operator;
Updating means for updating the history database so as to include the history information related to the sales registration and made the operator identifiable in response to the sales registration being performed by the registration means;
A setting means for setting a plurality of employees as target employees in response to an instruction from the operator,
For each of a plurality of target employees set by the setting means, an extraction means for extracting history information related to sales registration performed by the target employee as a handler, from the history database;
A control program that functions as a generation unit that generates an image representing history information extracted by the extraction unit.