Transaction processing device and information processing program

Abstract

To make it possible to continue a processing transaction having been processed in accordance with an operation using an information terminal appliance even when a fault occurs in the information terminal appliance.SOLUTION: A transaction processing device of an embodiment comprises terminal management means and processing means. The terminal management means can variably manage an association between an identifier of a register serial number and an information terminal appliance for receiving operations by an operator. The processing means processes a transaction determined in response to an operation on the information terminal appliance as a transaction relating to the identifier of the register serial number that is associated by the terminal management means to the information terminal appliance on which that operation was performed.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] Embodiments of the present invention relate to a transaction processing apparatus and an information processing program.

Background Art

[0002] In a POS system, a transaction being processed is managed by an information terminal device such as a POS terminal for receiving an operation by an operator. Therefore, when a failure occurs in the information terminal device, there is a risk that the processing managed by the information terminal device cannot be continued. Under such circumstances, it has been desired that even when a failure occurs in the information terminal device, the processing of the transaction that has been processed in response to the operation using the information terminal device can be continued.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] The problem to be solved by the present invention is to provide a transaction processing apparatus and an information processing program capable of continuing the processing of a transaction that has been processed in response to an operation using an information terminal device even when a failure occurs in the information terminal device.

Means for Solving the Problems

[0005] The transaction processing apparatus according to the embodiment is [[ID=……]] The system comprises a first storage means, a second storage means, a first update means, and a second update means. The first storage means stores terminal device codes and registration number codes in association. The second storage means stores transaction data that represents the content of a transaction and includes a registration number code. The first update means updates the transaction data stored in the second storage means, which includes a registration number code and is stored in the first storage means in association with the terminal device code of the information terminal device that made the change request, in response to a change request from an information terminal device, in order to change the content of the transaction data represented by that transaction data. The second update means updates the terminal device code stored in the first storage means in association with the notified registration number code in response to a notification of a registration number code from an information terminal device, to the terminal device code of the information terminal device that made the notification. The second update means further updates the data in response to a notification of a registration number code included in the transaction data stored by the second storage means. [[ID=……]] [[ID=……]]

Brief Description of the Drawings

[0006] [Figure 1] A block diagram showing a schematic configuration of a transaction processing system according to an embodiment. [Figure 2] A block diagram showing the main circuit configuration of the transaction processing device in Figure 1. [Figure 3] This diagram schematically represents the structure of a single data record included in the register number master in Figure 2. [Figure 4] A schematic diagram illustrating the structure of a single data record included in the functional restriction table in Figure 2. [Figure 5] A schematic diagram illustrating the structure of a single data record included in the management table in Figure 2. [Figure 6] A schematic diagram showing the structure of transaction data in Figure 2. [Figure 7] A sequence diagram illustrating an example of the procedure by which a transaction processing device processes a transaction using a single information terminal device as a user interface. [Figure 8] A sequence diagram illustrating an example of a procedure in which a transaction processing device processes a transaction while exchanging information terminal devices used as the user interface along the way. [Figure 9] Flowchart for editing the registration number. [Figure 10] A diagram showing an example of a registration number list screen. [Figure 11] A diagram showing an example of the configuration editing screen. [Figure 12] Flowchart for the function setting editing process. [Figure 13] A diagram showing an example of the function settings list screen. [Figure 14] A diagram showing an example of a function settings screen. [Modes for carrying out the invention]

[0007] An example of an embodiment will be described below with reference to the drawings. Figure 1 is a block diagram showing the schematic configuration of the transaction processing system according to this embodiment. The transaction processing system configuration shown in Figure 1 is one specific example of a system configured to suit the operating policies of a particular store.

[0008] The transaction processing system shown in Figure 1 includes a transaction processing unit 1, an information terminal device 2, an input / output device 3, peripheral devices 4, a simple drawer 5, a settlement terminal 6, a management terminal 7, and a communication network 8. The transaction processing unit 1, information terminal device 2, input / output device 3, simple drawer 5, settlement terminal 6, and management terminal 7 are able to communicate with each other via the communication network 8. The connection of the transaction processing unit 1, information terminal device 2, input / output device 3, simple drawer 5, settlement terminal 6, and management terminal 7 to the communication network 8 can be either wired or wireless. For example, it is assumed that the transaction processing unit 1, input / output device 3, and simple drawer 5 are connected via wired connections, while the information terminal device 2, settlement terminal 6, and management terminal 7 are connected via wireless connections.

[0009] The transaction processing device 1 performs information processing for transaction processing, appropriately utilizing peripheral devices 4, a simple drawer 5, and a payment terminal 6 in response to operations by an operator on the information terminal device 2. The transaction processing device 1 includes application programs for executing processes that were previously performed in conventional POS terminals, such as product registration processing for registering products to be purchased, accounting processing for registered products, and other business processes. The transaction processing device 1 executes various transaction-related processes in response to operations by an operator on the information terminal device 2. Information terminal device 2 is a user interface device that receives operations from an operator. The hardware of information terminal device 2 is expected to be, for example, a tablet computer. Information terminal device 2 includes an application program that provides a user interface for communicating with or controlling the transaction processing device 1, input / output device 3, and peripheral device 4 in response to operations from the operator.

[0010] Each input / output device 3 is appropriately connected to one or more peripheral devices 4. The input / output device 3 performs interface processing for the connected peripheral devices 4 to communicate via the communication network 8. The input / output device 3 functions as a peripheral device control device that controls the connection of the transaction processing device 1 and the information terminal device 2 to the peripheral devices 4. Alternatively, the input / output device 3 can be described as a device that mediates the connection of the transaction processing device 1 and the information terminal device 2 to the peripheral devices 4. In this embodiment, the input / output device 3 may be referred to as "IO BOX".

[0011] Figure 1 shows an example of a transaction processing system where a system tailored to specific locations within a store, such as a permanent checkout counter, service counter, temporary checkout counter, and sales floor, is built. In other words, the transaction processing system is built to suit the accounting scenario, such as a permanent checkout counter, service counter, temporary checkout counter, and sales floor. The transaction processing system in Figure 1 is an example of a system configured to conform to the store's operating policy. Here, a permanent checkout counter refers to a location that is permanently installed in the store and used during normal checkouts. A system is built at the permanent checkout counter for use during checkouts. A service counter refers to a location in the store that is separate from the permanent checkout counter and can provide various services outside of normal checkouts. For example, a system is built for use when providing services such as membership registration and delivery requests. The service counter system can also be used for accounting and return processing. A temporary checkout counter refers to a location in the store that is not normally used but is temporarily opened during busy periods or events for use during checkouts. A system is built at the temporary checkout counter for use during checkouts. A sales area refers to a location where goods are displayed permanently or temporarily, allowing customers to browse and view them. Permanent checkout counters are equipped with systems that are simpler to use for checkout than those at service counters or temporary checkout counters. The systems in the sales area may, for example, be designed as portable systems for store employees.

[0012] The peripheral device 4 is a device that performs various processes related to transaction processing. As the peripheral device 4, various types of devices such as an automatic change dispenser, a drawer, a payment terminal, a printer, a scanner, or a display can be appropriately used. Note that many of the peripheral devices 4 are various devices equipped in an existing POS terminal or externally attached to an existing POS terminal.

[0013] In the transaction processing system shown in FIG. 1, regarding the permanent accounting corner provided in the store, one input / output device 3 is installed corresponding to each checkout lane, and the peripheral device 4 used when processing a transaction in the same checkout lane is connected to the input / output device 3. Thus, FIG. 1 shows a case where two checkout lanes are set in the permanent accounting corner. Also, in the transaction processing system shown in FIG. 1, one input / output device 3 is installed at the service counter provided in the store, and the peripheral device 4 used when processing a transaction at the service counter is connected to the input / output device 3.

[0014] The simple drawer 5 is a drawer with a simple structure so that it can be easily moved. In the transaction processing system shown in FIG. 1, the simple drawer 5 is used in a special accounting corner temporarily provided in the store. The payment terminal 6 is a terminal device that performs processing for payment by various payment methods. The payment terminal 6 may correspond to only one payment method or may correspond to a plurality of payment methods. Also, each of the plurality of payment terminals 6 may have various corresponding payment methods. The payment methods that the payment terminal 6 corresponds to are, for example, credit card payment, electronic money payment, code payment, prepaid payment, debit payment, coupon payment, and the like. In the transaction processing system shown in FIG. 1, the payment terminal 6 is used in the special accounting corner and the sales floor.

[0015] The management terminal 7 is an information processing device that functions as a user interface for receiving operations from the administrator of the transaction processing system shown in Figure 1. The hardware of the management terminal 7 is expected to include a general-purpose information processing device such as a tablet computer, desktop computer, or laptop computer.

[0016] The communication network 8 can use the internet, VPN (virtual private network), LAN (local area network), public communication network, mobile communication network, etc., individually or in appropriate combinations. As an example, a LAN is used as the communication network 8. However, the communication network 8 can be modified as appropriate, for example, by using a combination of LAN and the internet, and having communication between the transaction processing device 1 and other devices conducted via the internet. Thus, the communication network 8 may include network equipment such as routers and transmission cables.

[0017] Figure 2 is a block diagram showing the main circuit configuration of the transaction processing device 1. The transaction processing device 1 includes a processor 11, a main storage unit 12, an auxiliary storage unit 13, a communication unit 14, and a transmission line 15, etc. The processor 11 and the main storage unit 12, the auxiliary storage unit 13, and the communication unit 14 are able to communicate with each other via the transmission line 15.

[0018] By connecting the processor 11, the main storage unit 12, and the auxiliary storage unit 13 via a transmission line 15, a computer is configured to perform information processing for controlling the transaction processing device 1. The processor 11 corresponds to the central part of the computer described above. The processor 11 performs information processing to control each part in order to realize various functions as a transaction processing device 1, in accordance with information processing programs such as the operating system and application programs.

[0019] The main memory unit 12 corresponds to the main memory portion of the computer described above. The main memory unit 12 includes a read-only memory area and a rewritable memory area. The main memory unit 12 stores a portion of the information processing program described above in the read-only memory area. The main memory unit 12 may also store data necessary for the processor 11 to perform processing to control each part in the read-only memory area or the rewritable memory area. The main memory unit 12 uses the rewritable memory area as a work area for the processor 11.

[0020] The auxiliary storage unit 13 corresponds to the auxiliary storage portion of the computer described above. The auxiliary storage unit 13 can utilize, for example, an EEPROM (electric erasable programmable read-only memory), an HDD (hard disk drive), an SSD (solid state drive), or various other well-known storage devices. The auxiliary storage unit 13 stores data used by the processor 11 in performing various processes and data generated by the processing performed by the processor 11. The auxiliary storage unit 13 may also store the information processing program described above. In this embodiment, the auxiliary storage unit 13 stores the transaction processing program PRA, which is one of the information processing programs. The transaction processing program PRA is an application program that describes the information processing procedures described later that should be executed in relation to the processing of transactions related to the buying and selling of goods at a store. A portion of the storage area of ​​the auxiliary storage unit 13 is used as an area for storing the register master DBA, the function restriction table TAA, the management table TAB, and the transaction data DAA.

[0021] The register master DBA is a database that represents the configuration of each register. Here, a register is a set of devices used by the transaction processing unit when processing a single transaction. For example, in the transaction processing system shown in Figure 1, for permanent checkout corners and service counters, one register is composed of one information terminal device 2, one input / output device 3, and peripheral devices 4 connected to this input / output device 3. For example, in the transaction processing system shown in Figure 1, for temporary checkout corners, one register is composed of one information terminal device 2, one simple drawer 5, and one payment terminal 6. For example, in the transaction processing system shown in Figure 1, for sales floors, one register is composed of one information terminal device 2 and one payment terminal 6. Although Figure 1 shows information terminal device 2 not belonging to any of the permanent checkout area, service counter, temporary checkout area, or sales floor, in actual operation it will be brought to and used in one of these locations.

[0022] The Function Restriction Table TAA is a data table that shows which of the multiple functions that can be executed during transaction processing are permitted to be executed for each scenario in which the cash register is used (hereinafter referred to as the accounting scenario). Management table TAB is a data table used to manage which register number information terminal device 2 is being used with. Transaction data (DAA) is data that represents the details of a single transaction.

[0023] The communication unit 14 performs communication processing for data communication via the communication network 8. For example, an existing communication device for a LAN can be used as the communication unit 14. The transmission line 15 includes an address bus, a data bus, and control signal lines, and transmits data and control signals exchanged between the connected parts.

[0024] The information processing performed by the transaction processing device 1 is, as described later, processing for transactions in response to operations on the information terminal device 2. Therefore, the transaction processing device 1 operates as a server device with the information terminal device 2 as its client. If only a LAN is used as the communication network 8, the transaction processing device 1 operates as a local server. If, for example, a combination of a LAN and the internet is used as the communication network 8, and communication between the transaction processing device 1 and other devices is performed via the internet, the transaction processing device 1 operates as a web server or a cloud server.

[0025] Figure 3 schematically represents the structure of a single data record REA included in the register master DBA. The register master DBA is a collection of multiple data records REA associated with each register included in the transaction processing system. Each data record REA contains multiple fields FAA, FAB, ... Field FAA contains the register code as an identifier for the associated register. Field FAB contains the name of the associated register. Field FAC contains the scene code as an identifier for the usage scenario of the associated register. Field FAC may contain the scene code and the name of that accounting scene. Each field from FAD onward contains information about various devices other than the information terminal device 2 belonging to the associated register. The feeling The notification is set.

[0026] The register number master DBA is generated, for example, by the worker during the process of building the transaction processing system, adapting it to the configuration of the transaction processing system. The register number master DBA may be updated during maintenance work, such as when the configuration of the transaction processing system is changed, but it is not updated during the transaction processing described later.

[0027] As an example, suppose one of the cash registers installed in a permanent checkout area is configured with input / output device 3 connected to peripheral devices 4, including an automatic change dispenser, payment terminal, printer, scanner, and display. The cash register code and name are set to "0001" and "Permanent Counter Semi-Self-Service_1," respectively, and the scene code of the assigned checkout scene is "A." In this case, the fields FAA, FAB, and FAC of the data record REA associated with the cash register are set to "0001," "Permanent Counter Semi-Self-Service_1," and "A," respectively, while the fields FAD, FAE, FAF, FAI, FAJ, and FAK are set to information about the above-mentioned input / output device 3, automatic change dispenser, payment terminal, printer, scanner, and display, respectively. For fields like FAG and FAH in this example, where there is no corresponding device, they may be left blank or set to a predetermined null value.

[0028] As another example, suppose one of the cash registers installed in a special accounting corner is composed of a simple drawer 5 and a payment terminal 6, and its cash register code and name are set to "0005" and "Temporary Cash Register_2", respectively, and the scene code of the accounting scene to which it is assigned is "B". In this case, the fields FAA, FAB, and FAC of the data record REA associated with the cash register are set to "0005", "Temporary Cash Register_2", and "B", respectively, and the fields FAE and FAF are set to the information about the simple drawer 5 and payment terminal 6 mentioned above, respectively.

[0029] As another example, suppose one of the cash registers used in the sales area is composed of three payment terminals, and its cash register code and name are set to "0007" and "Sales Area_2", respectively, and the scene code of the assigned accounting scene is "C". In this case, the fields FAA, FAB, and FAC of the data record REA associated with the cash register are set to "0007", "Sales Area_2", and "C", respectively, and the fields FAF, FAG, and FAH are set to information about the three payment terminals 6 mentioned above, respectively.

[0030] Figure 4 schematically represents the structure of a single data record REB included in the functional restriction table TAA. The Function Restriction Table TAA is a collection of multiple data records REB associated with each of several predetermined accounting scenes. These accounting scenes are determined as appropriate by the transaction processing system administrator, depending on the store's operational policy regarding how the cash register will be used. Each data record REB includes fields FBA, FBB, etc. Field FBA contains the scene code of the associated accounting scene. Field FBB contains the name of the associated accounting scene. Each field from FBC onwards contains a flag indicating whether or not the execution of various functions realized by transaction processing is permitted. In other words, each field from FBC onwards generates or edits setting information for enabling or disabling various functions for each accounting scene distinguished by the scene code.

[0031] For example, if each of the functions named "Terminal Camera Scan," "Cash Payment," "Imprinter," "Bank Transfer," "Self-Service," "Buyback," "Return," "Drawer Opening," "Currency Exchange," "Collection," and "Ticket Issuance" is predetermined to be subject to restrictions, and for each of these functions, the accounting scene with the scene code "A" and the name "Self-Service" is set to "Invalid," "Valid," "Invalid," "Valid," "Valid," "Invalid," "Valid," "Valid," "Valid," "Valid," "Valid," then "A" will be set in field FBA, and the respective flags set in fields FBB to FBL will be set to represent "Invalid," "Valid," "Invalid," "Valid," "Valid," "Valid," "Invalid," "Valid," "Valid," "Valid," "Valid," respectively. The function restriction table TAA is generated, for example, when building a transaction processing system, by the worker involved in that work, adapting to the operational policies of the transaction processing system. The function restriction table TAA may be updated as described below in response to instructions from the transaction processing system administrator, but it is not updated during the transaction processing described later.

[0032] "Terminal Camera Scan" is a function that uses the camera 26 installed in the information terminal device 2 to acquire product barcodes, etc. "Cash Payment" is a function for registering cash payments. When using this function, for example, the store clerk selects the "Cash" button from the payment method selection field on the accounting screen, enters the amount received using the numeric keypad, and performs the cash settlement. "Imprinter" is a function that prints the card company and payment category on the receipt. "Bank Transfer" is a function that enables bank transfers. "Self-Service" is a function that displays instructions on the customer's screen and enables semi-self-service operation where registration is performed according to the store clerk's operation and payment is performed according to the customer's operation. "Buyback" is a function that performs processing related to the buyback of used goods, etc. "Return" is a function that performs processing for receiving returned goods. "Drawer Open" is a function that opens and closes the drawer belonging to the same register number. "Change" is a function that performs processing for change exchange. "Collection" is a function that enables the collection of coins of different denominations stored in the automatic change machine. "Ticket issuance" is a function that prints tickets using a ticket printer included in the register unit, for example, when selling tickets such as ski lift tickets.

[0033] Figure 5 schematically represents the structure of a single data record REC contained in the management table TAB. The management table TAB is a collection of multiple data records REC associated with each register number included in the transaction processing system. Each data record REC includes fields FCA, FCB, and FCC. Field FCA contains the register number code of the associated register number. Field FCB contains data representing the status of the associated register number. This data selectively indicates, for example, whether the associated register number is in use or unused. Field FCC contains the terminal device code, which serves as the identifier for the information terminal device 2 used by the associated register number. The management table TAB is updated as described below during the transaction processing described later.

[0034] Figure 6 is a schematic diagram illustrating the structure of the transaction data DAA. Transaction data DAA is generated for each transaction being processed by the transaction processing unit 1 and stored in the auxiliary storage unit 13. Thus, there may be cases where no transaction data DAA is stored in the auxiliary storage unit 13, or where multiple transaction data DAAs are stored simultaneously in the auxiliary storage unit 13 for each of multiple transactions being processed.

[0035] The transaction data DAA includes fields FDA and FDB. The transaction data DAA may include any number of fields starting from field FDC. Field FDA is set with the transaction code as the identifier for the transaction in question. Field FDB is set with the register code for the register used for the transaction in question. If there are registered goods that are the subject of the transaction (hereinafter referred to as transaction goods), fields FDC, FDD, ... associated with each of those transaction goods are added to the transaction data DAA. Fields FDC, FDD, ... each contain product data for a separate transaction product. The product data includes the product code and quantity as identifiers for the transaction product in question. The product data may also include various other information, such as product name, unit price, and discount information. Transaction data DAA is generated and updated as needed through the transaction processing described later.

[0036] Now, as the hardware for the transaction processing device 1, for example, a general-purpose server device can be used. Generally, the transfer of the transaction processing device 1 is performed with the transaction processing program PRA stored in the auxiliary storage unit 13. However, the hardware and the transaction processing program PRA may be transferred separately, either without the transaction processing program PRA stored in the auxiliary storage unit 13, or with a different version of the same type of application program stored in the auxiliary storage unit 13. The transaction processing device 1 may then be configured by writing the transaction processing program PRA to the auxiliary storage unit 13 in response to an operation by any operator. The transfer of the transaction processing program PRA can be performed by recording it on a removable recording medium such as a magnetic disk, magneto-optical disk, optical disk, or semiconductor memory, or by communication over a network.

[0037] Next, we will explain the operation of the transaction processing system configured as described above, focusing on the operation of the transaction processing device 1. Note that the processing described below is an example, and it is possible to change the order of some processes, omit some processes, or add other processes as appropriate. Furthermore, other processes that yield similar results may be applied to the specific processes described below.

[0038] (Processing of transactions) Figure 7 is a sequence diagram illustrating an example of the procedure in which the transaction processing device 1 processes a transaction using one information terminal device 2 as a user interface. When a store employee initiates the use of a cash register that is currently unused, they activate one unused information terminal device 2. Then, they instruct it to access the transaction processing device 1 through a predetermined procedure. Upon receiving this access instruction, information terminal device 2 proceeds to ACT201. Note that all operations of information terminal device 2 described below are realized through information processing by processor 21.

[0039] As ACT201, information terminal device 2 accesses transaction processing device 1 via communication network 8. When the processor 11 in the transaction processing device 1 receives the above access from the information terminal device 2, it starts information processing based on the transaction processing program PRA (hereinafter referred to as transaction processing). All operations of the transaction processing device 1 described below are realized by said transaction processing.

[0040] As ACT101, the transaction processing device 1 instructs the information terminal device 2 to display the login screen. As ACT202, information terminal device 2 displays a login screen, for example, on the touch panel 25, in accordance with the above instructions. The login screen is a screen for the operator to enter information for operator authentication. The store clerk performs a predetermined login operation to enter predetermined authentication information for operator authentication into information terminal device 2. Upon receiving this login operation, information terminal device 2 proceeds to ACT203.

[0041] As ACT203, information terminal device 2 requests login from transaction processing device 1, along with notification of the entered authentication information. Upon receiving this request, transaction processing device 1 proceeds to ACT102. As ACT102, the transaction processing device 1 authenticates, based on the notified authentication information, that the operator of the information terminal device 2 is a store employee authorized to use the information terminal device 2. If the authentication is successful, the transaction processing device 1 proceeds to ACT103.

[0042] As ACT103, the transaction processing device 1 instructs the information terminal device 2 to display the selection screen. Upon receiving this instruction, the information terminal device 2 proceeds to ACT204. As ACT204, the information terminal device 2 displays a selection screen, for example, on the touch panel 25, in accordance with the above instructions. The selection screen is a screen that allows the store clerk to select the cash register to which the information terminal device 2 is to be applied. The transaction processing device 1 displays, for example, a list of cash registers associated with data records included in the cash register master DBA on the selection screen, and the screen is used to receive a selection for one of those cash registers.

[0043] The store clerk determines the cash register to which information terminal device 2 will be applied and performs a predetermined operation on information terminal device 2 to specify that cash register. In response to this operation, information terminal device 2 proceeds to ACT205. As ACT205, information terminal device 2 notifies transaction processing device 1 of the registration number of the registration number specified above. Upon receiving this notification, transaction processing device 1 proceeds to ACT104.

[0044] As ACT104, the transaction processing device 1 updates the management table TAB to associate the information terminal device 2 with the specified register number as described above. At this time, the processor 11 in the transaction processing device 1 searches for data record REC in the management table TAB, for example, in which the notified register number code is set in field FCA. Then, the processor 11 rewrites the data set in field FCB of the corresponding data record REC, for example, if it represents "unused", to data representing "in use", and sets the terminal device code of information terminal device 2 in field FCC.

[0045] Thus, the transaction processing device 1 manages the association between information terminal devices and register codes using a management table TAB. In other words, by having the processor 11 execute information processing based on the transaction processing program PRA, the computer with the processor 11 as its central component functions as a terminal management means.

[0046] As ACT105, the transaction processing device 1 transmits peripheral device data and function restriction data related to various devices belonging to the specified register number to the information terminal device 2. Peripheral device data includes at least connection information for communicating with each device. Peripheral device data includes various data necessary for using the device in transaction processing, such as the type of device, device name, or data indicating what functions it has. Transaction processing device 1, for example, finds data record REA in the register master DBA where the notified register code is set in field FAA. Then, transaction processing device 1, for example, extracts predetermined information from the information set in each field from field FAD onward in the corresponding data record REA, and generates connection information as information containing that information. Transaction processing device 1 transmits the peripheral device data containing the generated connection information to information terminal device 2.

[0047] The function restriction data represents the settings for the function restrictions related to the accounting scene of the specified cash register. The transaction processing unit 1, for example, refers to the cash register master DBA to determine the scene code of the accounting scene of the specified cash register as described above. The transaction processing unit 1 then finds, for example, the data record REB in the function restriction table TAA in which the corresponding scene code is set in the field FBA. Furthermore, the transaction processing unit 1 generates the function restriction data, for example, by including the corresponding data record REB as data. The transaction processing unit 1 transmits the generated function restriction data to the information terminal device 2. Upon receiving this peripheral device data and function restriction data, the information terminal device 2 proceeds to ACT206.

[0048] As ACT206, information terminal device 2 performs connection processing to enable communication with various devices using peripheral device data. As ACT207, information terminal device 2 displays a registration screen, for example, on the touch panel 25. The registration screen is a screen that allows store staff to confirm the registration status of the transaction items. In other words, the registration screen displays, for example, a list of transaction items. The registration screen is also a screen where transaction items can be registered. However, since no transaction items have been registered yet, the registration screen does not display any transaction item information in the list.

[0049] If a customer requests that the store clerk register the items being purchased, the clerk performs a predetermined operation on information terminal device 2 to instruct it to register one of the items the customer intends to purchase as the item being purchased. The operation performed by the clerk here is, for example, to scan the barcode displayed on the product using a scanner provided as peripheral device 4 or a camera provided on information terminal device 2. However, if the terminal camera scanning function is disabled based on the function restriction data received as described above, information terminal device 2 will not perform barcode scanning using the camera provided on information terminal device 2. The operation performed by the clerk here may be, for example, to directly input the product code or to select a preset key for a product that is set in advance. The operation performed by the clerk here may be, for example, any other operation performed in an existing POS system. In response to this operation, information terminal device 2 obtains a product code to identify the product and proceeds to ACT208.

[0050] As ACT208, information terminal device 2 requests product registration from transaction processing device 1, along with notification of the product code of the specified product. Upon receiving this request, transaction processing device 1 proceeds to ACT106. As ACT106, the transaction processing device 1 generates new transaction data DAA. Specifically, the processor 11 in the transaction processing device 1 determines a new transaction code that is different from the transaction code used to identify other transactions, according to predetermined rules, sets this transaction code in field FDA, sets the register number code associated with the information terminal device 2 in field FDB, and sets the notified product code in field FDC to generate transaction data DAA, which is then stored in the auxiliary storage unit 13.

[0051] As ACT107, the transaction processing device 1 instructs the information terminal device 2 to update the registration screen. In other words, the transaction processing device 1 instructs the information terminal device 2 to update the registration screen so that the registered transaction products are displayed in a list as described above. Specifically, the transaction processing device 1 sends instruction data to the information terminal device 2 to instruct this update. The transaction processing device 1 includes the transaction data DAA generated as described above in the instruction data. Upon receiving this instruction, the information terminal device 2 proceeds to ACT209.

[0052] As ACT209, information terminal device 2 updates the registration screen in accordance with the above instructions. Specifically, information terminal device 2 updates the registration screen to display information such as the product name included in each product data set from field FDC onwards in the transaction data DAA included in the above instruction data in the list of transaction products.

[0053] The transaction processing device 1 may include only the individual product data from the information contained in the transaction data DAA as the instruction data. Alternatively, the transaction processing device 1 may include information such as a URL (uniform resource locator) for viewing the transaction data DAA from the information terminal device 2, instead of including the transaction data DAA or product data in the instruction data. In this case, the information terminal device 2 will view the transaction data DAA based on this information and update the registration screen.

[0054] Furthermore, the transaction processing device 1 generates screen data representing a registration screen showing a list of trading products based on the updated transaction data DAA, and may include this screen data in the instruction data, or it may include information such as a URL for viewing this screen data in the instruction data. In this case, the information terminal device 2 displays the registration screen represented by the screen data included in the instruction data on the touch panel 25, or displays a registration screen that can be viewed by the transaction processing device 1 for transactions based on information such as a URL included in the instruction data on the touch panel 25.

[0055] After this, the store clerk performs predetermined operations on information terminal 2 to instruct the customer to change the items to be traded, so that all the items the customer intends to purchase become the traded items. Changes to traded items include adding items, i.e., registering new items, deleting items, and changing the quantity. The operations performed by the store clerk here may be the same as those performed in an existing POS system. Upon receiving this change instruction, information terminal 2 proceeds to ACT210.

[0056] As ACT210, information terminal device 2 requests a change in the trading product from trading processing device 1 in accordance with the above operation. Upon receiving this request, trading processing device 1 proceeds to ACT108. As ACT108, the transaction processing device 1 responds to the above change request, ACT106 Update the transaction data DAA generated by [the program / tool].

[0057] As ACT109, the transaction processing device 1 instructs the information terminal device 2 to update the registration screen. In other words, the transaction processing device 1 instructs the information terminal device 2 to update the registration screen so that the registered transaction products are displayed in a list in the updated transaction data DAA, as described above, similar to ACT107. Upon receiving this instruction, the information terminal device 2 proceeds to ACT211. As ACT211, information terminal device 2 updates the registration screen in accordance with the above instructions, similar to ACT207. From this point forward, if the store clerk repeats the operation to instruct a change, the transaction processing device 1 and the information terminal device 2 will repeat the same processing as ACT210, ACT108, ACT109, and ACT211.

[0058] Once the clerk has finished registering all the items the customer intends to purchase as transaction items, they perform a predetermined operation on the information terminal device 2 to instruct the payment process. For example, the clerk operates the subtotal key or the payment method selection key on the information terminal device 2. The payment method selection key may be selected after the subtotal key has been selected, or the operation of the subtotal key may be unnecessary. The subtotal key or payment method selection key is an operation key to complete the registration of transaction items. The payment method selection key is an operation key to declare that the payment processing will be carried out using the selected payment method. The payment method indicated by the payment method selection key may include cash as well as payment methods supported by the payment terminal 6. In response to this instruction, the information terminal device 2 proceeds to ACT212. As ACT212, information terminal device 2 requests accounting processing from transaction processing device 1. Upon receiving this request, transaction processing device 1 proceeds to ACT110.

[0059] Transaction processing device 1 (ACT110) and information terminal device 2 (ACT213) cooperate with each other to calculate the price of the traded goods and perform accounting processing to settle the price. The accounting processing is performed by applying the payment method specified by information terminal device 2. The accounting processing includes cash settlement, for example, by using an automatic change dispenser to settle the price. The accounting processing also includes processing for settling the price, for example, by using a payment terminal. The details of the accounting processing may be the same as those performed in existing POS terminals, for example.

[0060] Once the accounting process is complete, information terminal device 2 proceeds to ACT214. As ACT214, the information terminal device 2 displays a new registration screen, for example on the touch panel 25, which does not contain information about the trading product. Alternatively, the information terminal device 2 may display the registration screen in response to instructions from the transaction processing device 1. After this, if a store clerk operation related to a new transaction is performed on the information terminal device 2, the transaction processing device 1 and the information terminal device 2 will repeat the processes from ACT106 and ACT208 onward as described above to process the new transaction.

[0061] As described above, in the transaction processing device 1, the processor 11 processes the transaction to be processed as a transaction relating to the registration code associated with the information terminal device 2. In other words, by having the processor 11 execute information processing based on the transaction processing program PRA, the computer with the processor 11 as its central component functions as a processing means.

[0062] If the transaction processing device 1 generates historical data relating to transactions processed by the transaction processing device 1, it is preferable that the historical data includes a register code so as to identify the register number used in each transaction. Furthermore, if the historical data is generated by an information processing device other than the transaction processing device 1, it is preferable that the transaction processing device 1 includes the register code in the data used to notify the above-mentioned information processing device of the transaction result, so as to enable the inclusion of the register code in that historical data.

[0063] If, for any reason, the store clerk needs to discontinue using information terminal device 2 with the current cash register, they will perform a predetermined operation on information terminal device 2 to issue a command to unlink it. In response to this command, information terminal device 2 will proceed to ACT215. As ACT215, information terminal device 2 requests transaction processing device 1 to disassociate the device. Upon receiving this request, transaction processing device 1 proceeds to ACT111.

[0064] As ACT111, the transaction processing device 1 updates the management table TAB to remove the association with information terminal device 2. At this time, the processor 11 in the transaction processing device 1 searches for data record REC in the management table TAB, for example, in which the terminal device code of information terminal device 2 that requested to be removed is set in field FCC. Then, the processor 11 rewrites the data set in field FCB of the corresponding data record REC to data representing "unused" and deletes the terminal device code set in field FCC.

[0065] As ACT112, the transaction processing device 1 notifies the information terminal device 2 that the association has been removed. After this, by accessing the transaction processing device 1 again using the information terminal device 2 and specifying a different register code, the information terminal device 2 will operate as a user interface device for a different register code.

[0066] (Replacement of information terminal device 2) Now, suppose that information terminal device 2, whose terminal device code is "01", is associated with the register code "0001". Then, suppose that while transaction processing device 1 and information terminal device 2, whose terminal device code is "01", are repeating the same process as, for example, ACT210, ACT108, ACT109, and ACT211, a failure occurs in information terminal device 2, and it becomes unable to continue the above operation. The procedure for replacing information terminal device 2 in this case is described below.

[0067] Figure 8 is a sequence diagram illustrating an example of the procedure in which the transaction processing device 1 processes a transaction while exchanging the information terminal device 2 used as the user interface along the way. Here, we assume that the process proceeds as shown in Figure 7 between the transaction processing device 1 and the information terminal device 2, whose terminal device code is "01," up to ACT109 and ACT211. Then, we assume that the information terminal device 2, whose terminal device code is "01," becomes unable to continue processing while waiting for a change instruction or accounting instruction.

[0068] In this case, the store clerk instructs another information terminal device 2, whose terminal device code is "02", to access the transaction processing device 1. Upon receiving this access instruction, information terminal device 2, whose terminal device code is "02", proceeds with the transaction processing device 1 as follows. Transaction processing device 1 and information terminal device 2, designated as ACT121, ACT122, ACT123 and ACT221, ACT222, ACT223, and ACT224, perform the same processing as ACT101, ACT102, ACT103 and ACT201, ACT202, ACT203, and ACT204 in Figure 7.

[0069] The store clerk selects the register code "0001" on the selection screen. In response, information terminal 2 proceeds to ACT225. As ACT225, information terminal device 2 notifies transaction processing device 1 of the registration code "0001" of the registration number specified above. Upon receiving this notification, transaction processing device 1 proceeds to ACT124.

[0070] As ACT124, transaction processing device 1 updates the management table TAB to associate the information terminal device 2 with the specified register number, similar to ACT104 in Figure 7. In this case, transaction processing device 1 changes the field FCC of data record REC, which already has "01" set in field FCA in the management table TAB, to "02". Transaction processing device 1 also leaves the field FCB of the corresponding data record REC as is, as it already has data indicating "in use".

[0071] As ACT125, transaction processing device 1 transmits peripheral device data and function restriction data related to various devices belonging to the specified register number to information terminal device 2, similar to ACT105. As ACT126, the transaction processing device 1 instructs the information terminal device 2 to display a registration screen showing a list of transaction products based on the transaction data DAA in which the register code "0001" is set in the field FDB, in the same manner as ACT107. As ACT226, information terminal device 2 performs connection processing to enable communication with various devices using peripheral device data. As ACT227, the information terminal device 2 displays the registration screen, for example, on the touch panel 25, in response to the above display instructions.

[0072] If the store clerk then performs the aforementioned operation to instruct a change in the transaction item on information terminal 2, whose terminal code is "02", then information terminal 2 proceeds to ACT228. As ACT228, information terminal device 2 requests a change in the trading product from trading processing device 1 in accordance with the above operation. Upon receiving this request, trading processing device 1 proceeds to ACT127. As ACT127, the transaction processing device 1 updates the transaction data DAA generated in ACT107, that is, the transaction data DAA generated in response to a request from the information terminal device 2 whose terminal device code is "01", in response to the above change request.

[0073] As ACT128, the transaction processing device 1 instructs the information terminal device 2, whose terminal device code is "02", to update the registration screen. Upon receiving this instruction, the information terminal device 2 proceeds to ACT229. As ACT229, information terminal device 2 updates the registration screen in accordance with the above instructions. Subsequently, if the store clerk repeatedly performs the operation to instruct a change using information terminal device 2, whose terminal device code is "02", the transaction processing device 1 and information terminal device 2 will repeat the same processing as ACT228, ACT127, ACT128, and ACT229. As a result, the transaction processing that was interrupted due to an operation on information terminal device 2 with terminal device code "01" will continue to be executed in response to an operation on information terminal device 2 with terminal device code "02". In other words, the interrupted transaction processing can be resumed without waiting for information terminal device 2 with terminal device code "01" to recover.

[0074] (Editing the registration number master DBA) Incidentally, although not mentioned in the explanation of the transaction processing described above, during the above processing, peripheral devices 4, the simple drawer 5, and the payment terminal 6 are controlled, for example, by operating the printer to print a receipt. This control is performed from the transaction processing device 1 via the communication network 8, or from the information terminal device 2 via the communication network 8. For this control, the transaction processing device 1 manages the configuration of each register using the register master DBA and sends peripheral device data regarding available peripheral devices to the information terminal device 2. In other words, by having the processor 11 execute information processing based on the transaction processing program PRA, the computer with the processor 11 as its central component functions as a device management means that manages devices used as peripheral devices of the information terminal device 2 using the register master DBA. Therefore, when changing the configuration of a registration number, it is necessary to update the registration number master DBA.

[0075] In the transaction processing device 1, when the processor 11 receives access from the management terminal 7 and requests editing of the register master DBA, it executes information processing for editing the register master DBA (hereinafter referred to as register editing processing) based on the transaction processing program PRA. Note that the transaction processing and the register editing processing may be executed based on separate information processing programs. Although not shown in the diagram, it is preferable that the processor 11 performs authentication processing to confirm that the operator of the management terminal 7 is an administrator authorized to edit the register master DBA, and only starts the register editing processing if the authentication is successful. Access from the management terminal 7 to the transaction processing unit 1 is expected to be performed, for example, using a general-purpose web browser. However, a dedicated application for accessing the transaction processing unit 1 may also be used.

[0076] Figure 9 is a flowchart of the registration number editing process. As ACT301, processor 11 responds to management terminal 7 with an instruction to display the register number list screen. In response to this instruction, management terminal 7 displays the register number list screen. The register number list screen is a screen that shows a list of register numbers to which each data record REA included in the register number master DBA is associated. The register number list screen is also a screen for instructing the start of editing the register number master DBA.

[0077] Figure 10 shows an example of a registration number list screen. The register number list screen shown in Figure 10 is an example where the register number master DBA contains seven data records REA, meaning that seven register numbers are configured. The register number list screen displays the register number code and name, and the scene code and name of the accounting scene for each register number, as strings, on the same row. The register number list screen also displays a button BUA on each row. The button BUA is a soft key that instructs the user to start editing the register number displayed on the same row.

[0078] The administrator selects the register number to be edited from the register numbers displayed on the register number list screen. The administrator then specifies the register number to be edited by performing a predetermined operation, such as tapping the button BUA corresponding to that register number. Once such a specification has been made, the management terminal 7 notifies the transaction processing device 1 of the register number code of the specified register number.

[0079] Once processor 11 has finished issuing the display instruction for ACT301 in Figure 9, it proceeds to ACT302. As ACT302, processor 11 waits for one of the registration numbers to be specified. Then, if the registration number code is notified from the management terminal 7 as described above, processor 11 determines YES in ACT302 and proceeds to ACT303.

[0080] As ACT303, processor 11 generates editing data to temporarily record the edited content. For example, processor 11 copies the data record REA associated with the register number to be edited from the data record REA contained in the register number master DBA to use as editing data. As ACT304, processor 11 responds to management terminal 7 with an instruction to display the configuration editing screen. In response to this instruction, management terminal 7 displays the configuration editing screen. The configuration editing screen is a screen that receives operations for editing the settings related to the configuration of the specified register number. The configuration editing screen is a screen for editing the information of fields FAB, FAC, ... which are associated with the register number code in the data record REA included in the register number master DBA.

[0081] Figure 11 shows an example of a configuration editing screen. The configuration editing screen displays the settings for the selected register in the display area ARA. The configuration editing screen also has buttons BUB, BUC, and BUD. Button BUB is a soft key used to delete the settings for the selected register. Button BUC is a soft key used to cancel editing and return to the register list screen. Button BUD is a soft key used to save the settings displayed in the display area ARA.

[0082] Once processor 11 has finished issuing the display instruction as ACT304 in Figure 9, it proceeds to ACT305. As ACT305, processor 11 checks whether it has been notified that an editing operation has been performed. If processor 11 cannot confirm the event, it determines NO and proceeds to ACT306. As ACT306, processor 11 checks whether a return has been requested. If processor 11 cannot confirm the relevant event, it determines NO and proceeds to ACT307. As ACT307, processor 11 checks whether saving the edited content has been requested. If processor 11 cannot confirm the event, it determines NO and proceeds to ACT308. As ACT308, processor 11 checks whether or not the deletion of the registration number to be edited has been requested. If processor 11 cannot confirm the relevant event, it determines NO and returns to ACT305. Thus, the processor 11 waits for one of the following to be made as ACT305~ACT308: an edit operation, a return request, a save request, or a delete request.

[0083] The administrator then uses the management terminal 7 to perform predetermined operations to change various settings related to the configuration of the registered machine being edited, such as tapping a radio button displayed in the display area ARA of the configuration editing screen, or performing predetermined operations to edit a string of text displayed in the display area ARA.

[0084] For example, the register unit name can be set by directly entering text. The accounting scene can be set by selecting from pre-prepared accounting scenes. Note that on the configuration editing screen, the scene code and scene name set in the FBA and FBB fields of the data record REC associated with each accounting scene in the function restriction table TAA are listed and represented as "A: Stationary Counter Semi-Cashier". The IOBOX connection and IOBOX address are set to "yes" or "no" for the connection of input / output device 3, and the connection setting information if "yes". The change dispenser connection and model are set to "yes" or "no" for the change dispenser connection, and the model if "yes". The payment terminal connection and payment terminal address are set to "yes" or "no" for the payment terminal connection, and the connection setting information if "yes". If multiple payment terminals are connected, multiple payment terminal connections and payment terminal addresses are set. The printer connection and printer name, and the scanner connection and scanner name, are similarly configured with an "Yes" or "No" setting, and if "Yes," the device name or connection setting information is also set.

[0085] The management terminal 7 notifies the transaction processing unit 1 of the details of the operation and requests that the settings be changed. Upon receiving this request, the processor 11 determines YES in ACT305 and proceeds to ACT309. As ACT309, processor 11 updates the edited data in accordance with the above operation.

[0086] As ACT310, processor 11 instructs management terminal 7 to update the configuration editing screen to reflect the settings represented by the updated editing data. After this, processor 11 returns to the waiting state for ACT305~ACT308. Management terminal 7 updates the displayed configuration editing screen in accordance with the above instruction.

[0087] If the administrator wishes to cancel the changes to the configuration settings of the registered machine being edited, they can return by performing a predetermined operation, such as tapping the BUC button displayed on the configuration editing screen. In response to this instruction, the management terminal 7 requests the transaction processing unit 1 to return. Upon receiving this request, the processor 11 determines YES in ACT306 and returns to ACT301, repeating the process from there as described above.

[0088] If the administrator wishes to save the edited results, they will initiate saving by performing a predetermined operation, such as tapping the BUD button displayed on the configuration editing screen. In response to this instruction, the management terminal 7 requests saving from the transaction processing unit 1. Upon receiving this request, the processor 11 determines YES in ACT307 and proceeds to ACT311.

[0089] As ACT311, processor 11 updates the register master DBA to reflect the edited content. For example, processor 11 overwrites the data record REA associated with the register being edited with the edited data. After this, processor 11 returns to ACT301 and repeats the subsequent processing as described above.

[0090] If the administrator wishes to delete the registration number to be edited, they will instruct the deletion by performing a predetermined operation, such as tapping the BUB button displayed on the configuration editing screen. In response to this instruction, the management terminal 7 requests the transaction processing unit 1 to delete the registration number. Upon receiving this request, the processor 11 determines YES in ACT308 and proceeds to ACT312.

[0091] As ACT312, processor 11 deletes the data record REA associated with the registration number to be edited from the registration number master DBA. Then, processor 11 returns to ACT301 and repeats the subsequent processing as described above. Before executing ACT312, processor 11 may display a screen on the management terminal 7 prompting confirmation whether it is OK to perform the deletion, and proceed to ACT312 only if it is confirmed that the operation to instruct the deletion to be performed has been made on the management terminal 7.

[0092] The processor 11 may, upon receiving an operation from the management terminal 7 to instruct the addition of settings for a new register number, generate edit data representing predetermined default settings and then execute the processes from ACT305 onward. However, in this case, the processor 11 adds the edit data as a new data record REA to the register number master DBA in ACT311.

[0093] (Editing the feature restriction table) In the above description of transaction processing, the execution of various other functions not performed may be required in response to execution instructions from a store clerk on information terminal device 2, or when predetermined execution conditions are met during other processing. In this case, the transaction processing device 1 or information terminal device 2 will refer to the function restriction table TAA or notified function restriction data and will not execute functions that are disabled for the accounting scene of information terminal device 2. In other words, by having the processor 11 execute information processing based on the transaction processing program PRA, the computer with the processor 11 as its central component functions as a function management means that manages whether to allow the execution of various functions using the function restriction table TAA. The processor 11 determines that the accounting scene for the information terminal device 2 is the one identified by the scene code associated in the register master DBA with the register code associated with the register code in the management table TAB. In other words, by having the processor 11 execute information processing based on the transaction processing program PRA, the computer with the processor 11 as its central component functions as a scene management means that manages the association between the register code and the accounting scene using the register master DBA. As mentioned above, the function restriction table TAA is determined according to the operating policy of each store, and it may be necessary to update it when the operating policy changes.

[0094] In the transaction processing device 1, when the processor 11 receives access from the management terminal 7 and a request is made to edit the function restriction table TAA, it executes information processing for editing the function restriction table TAA (hereinafter referred to as function setting editing processing) based on the transaction processing program PRA. Note that the transaction processing and the function setting editing processing may be executed based on separate information processing programs. Although not shown in the diagram, it is preferable that the processor 11 performs authentication processing to confirm that the operator of the management terminal 7 is authorized to edit the function restriction table TAA, and only starts the function setting editing processing if the authentication is successful.

[0095] Figure 12 is a flowchart of the function setting editing process. As ACT401, processor 11 instructs management terminal 7 to display the function settings list screen. In response to this instruction, management terminal 7 displays the function settings list screen. The function settings list screen is a screen that shows a list of the setting status of function restrictions for each accounting scene.

[0096] Figure 13 shows an example of the function settings list screen. The function settings list screen shown in Figure 13 is an example where the function restriction table TAA contains five data records REB, meaning five accounting scenes are configured. The function settings list screen displays the accounting scene code and name, along with the enabled / disabled status of various functions for that accounting scene, as strings on the same row, and the button BUE. The button BUE is a soft key that instructs the user to begin editing the function restriction settings.

[0097] The administrator selects the accounting scene to be edited from the accounting scenes displayed on the function settings list screen. The administrator then specifies the accounting scene to be edited by performing a predetermined operation, such as tapping the button BUE corresponding to that accounting scene. Once such a specification has been made, the management terminal 7 notifies the transaction processing device 1 of the scene code of the specified accounting scene.

[0098] Once processor 11 has finished issuing the display instruction for ACT401 in Figure 12, it proceeds to ACT402. As ACT402, processor 11 waits for one of the accounting scenes to be specified. Then, if the scene code is notified from the management terminal 7 as described above, processor 11 determines YES in ACT402 and proceeds to ACT403.

[0099] As ACT403, processor 11 generates editing data to temporarily record the edited content. For example, processor 11 copies the data record REB associated with the accounting scene to be edited from the data record REB contained in the function restriction table TAA to use as editing data.

[0100] As ACT404, processor 11 instructs management terminal 7 to display the function settings screen. In response to this instruction, management terminal 7 displays the function settings screen. The function settings screen is a screen that allows operations to edit the settings related to the function restrictions for the specified accounting scene.

[0101] Figure 14 shows an example of a function settings screen for different scenes. The function settings screen displays the settings for function restrictions related to the accounting scene being edited in the display area ARB. The function settings screen also has buttons BUF, BUG, ​​and BUH. Button BUF is a soft key used to delete the accounting scene being edited. Button BUG is a soft key used to cancel editing and return to the function settings list screen. Button BUH is a soft key used to save the settings displayed in the display area ARB.

[0102] Once processor 11 has finished issuing the display instruction for ACT404 in Figure 12, it proceeds to ACT405. As ACT405, processor 11 checks whether it has been notified that an editing operation has been performed. If processor 11 cannot confirm the event, it determines NO and proceeds to ACT406. As ACT406, processor 11 checks whether a return has been requested. If processor 11 cannot confirm the relevant event, it determines NO and proceeds to ACT407. As ACT407, processor 11 checks whether saving the edited content has been requested. If processor 11 cannot confirm the event, it determines NO and proceeds to ACT408. As ACT408, processor 11 checks whether or not the deletion of the registration number to be edited has been requested. If processor 11 cannot confirm the relevant event, it determines NO and returns to ACT405. Thus, the processor 11 waits for one of the following to be made as ACT405~ACT408: edit operation, return request, save request, or delete request.

[0103] The administrator then performs predetermined operations on the management terminal 7 to change various settings related to the functional restrictions of the accounting scene to be edited, such as tapping a radio button displayed in the ARB display area of ​​the function settings screen. The management terminal 7 notifies the transaction processing unit 1 of the details of these operations and requests the settings to be changed. Upon receiving this request, the processor 11 determines YES in ACT405 and proceeds to ACT409. As ACT409, processor 11 updates the edited data in accordance with the above operation.

[0104] As ACT410, processor 11 instructs management terminal 7 to update the function settings screen to reflect the settings status represented by the updated edited data. After this, processor 11 returns to the standby state of ACT405~ACT408. Management terminal 7 updates the function settings screen it is displaying in accordance with the above instruction.

[0105] If the administrator wishes to cancel changes to the settings related to the functional restrictions of the accounting scene being edited, they can return by performing a predetermined operation, such as tapping the BUG button displayed on the functional settings screen. In response to this instruction, the management terminal 7 requests the transaction processing unit 1 to return. Upon receiving this request, the processor 11 determines YES in ACT406 and returns to ACT401, repeating the processing from there as described above.

[0106] If the administrator wishes to save the edited results, they will instruct the administrator to save by performing a predetermined operation, such as tapping the BUH button displayed on the function settings screen. In response to this instruction, the management terminal 7 requests the transaction processing unit 1 to save. Upon receiving this request, the processor 11 determines YES in ACT407 and proceeds to ACT411.

[0107] As ACT411, processor 11 updates the function restriction table TAA to reflect the edited content. For example, processor 11 overwrites the data record REB associated with the accounting scene being edited with the edited data. After this, processor 11 returns to ACT401 and repeats the subsequent processing as described above.

[0108] If the administrator wants to delete the accounting scene to be edited, they will instruct the deletion by performing a predetermined operation, such as tapping the BUF button displayed on the function settings screen. In response to this instruction, the management terminal 7 requests the transaction processing unit 1 to delete the scene. Upon receiving this request, the processor 11 determines YES in ACT408 and proceeds to ACT412.

[0109] As ACT412, processor 11 deletes the data record REB associated with the accounting scene to be edited from the function restriction table TAA. After this, processor 11 returns to ACT401 and repeats the subsequent processing as described above. Before executing ACT412, processor 11 may display a screen on the management terminal 7 prompting confirmation whether it is OK to perform the deletion, and proceed to ACT412 only if it is confirmed that the operation to instruct the deletion to be performed has been made on the management terminal 7.

[0110] The processor 11 may, in response to an operation on the management terminal 7 instructing the addition of a new accounting scene, generate edit data representing predetermined default settings and then execute the processes from ACT405 onward. However, in this case, the processor 11 adds the edit data as a new data record REB to the function restriction table TAA in ACT411.

[0111] As described above, the transaction processing device 1 manages the association between information terminal devices 2 and registration code numbers, and processes transactions determined by operations on information terminal devices 2 as transactions related to the registration code number associated with that information terminal device 2. Thus, by changing the information terminal device 2 associated with a registration code, it is possible to change the information terminal device 2 used to receive operations related to a single transaction, and even if an information terminal device fails, the processing of transactions that were being processed in response to operations using that information terminal device can continue.

[0112] Furthermore, the transaction processing unit 1 manages the devices used in each register by associating them with the register code using the register master DBA, and updates the register master DBA as needed according to instructions from the administrator. This makes it possible to easily change the configuration of the registers.

[0113] Furthermore, the transaction processing unit 1 manages which of multiple functions are permitted to be executed for each accounting scene using a function restriction table TAA, and updates the function restriction table TAA as needed according to instructions from the administrator. This makes it easy to change the restrictions on which functions are permitted to be executed for each accounting scene.

[0114] This embodiment can be modified in various ways as follows: At least one of the register number master DBA, function restriction table TAA, management table TAB, and transaction data DAA may be stored in a storage device located outside the transaction processing device 1.

[0115] The decision of whether or not to execute a function whose use may be restricted by the settings in the function restriction table TAA may be made by the processor 11 in the transaction processing device 1. For example, even if the use of the terminal camera scanning function is restricted, barcode scanning using the camera installed in information terminal device 2 may be permitted. Furthermore, if a registration request is received in response to this barcode scan, the transaction processing device 1 may be configured to reject the registration request.

[0116] The transaction processing device 1 may be equipped with a user interface device, such as a touch panel, and this user interface device may be used to perform editing user interface operations.

[0117] Peripheral devices 4, simple drawers 5, and payment terminals 6 may be directly connected to the transaction processing device 1 or information terminal device 2 via wired or wireless connections without going through the communication network 8. However, in this case, the transaction processing device 1 controls the devices connected to the transaction processing device 1, and the information terminal device 2 controls the devices connected to the information terminal device 2.

[0118] The transaction processing system shown in Figure 1 is an example where, in a permanent accounting corner and service counter, peripheral devices 4 are connected to the communication network 8 via input / output devices 3, and the simple drawer 5 and payment terminal 6 are directly connected to the communication network 8. However, how each device is connected to the communication network 8 can be changed as needed.

[0119] Transaction processing device 1 may process an error if the register identified by the register code notified, for example, in ACT205 in Figure 7, is "in use". In other words, if the data set in field FCB of the data record REC, which has the notified register code set in field FCA, indicates that it is "in use", transaction processing device 1 will return an error notification or a notification that it is in use to information terminal device 2. In this case, information terminal device 2 will display a screen on the touch panel 25 indicating that the specified register is in use.

[0120] Transaction processing device 1 or information terminal device 2 may prevent the selection of a register that is currently in use on the selection screen. Specifically, for example, transaction processing device 1 or information terminal device 2 may extract data records REC from the management table TAB where the data set in field FCB indicates "unused," and generate a selection screen that displays only the registers associated with the corresponding data records REC as options. Alternatively, for example, transaction processing device 1 or information terminal device 2 may generate a selection screen that displays a list of registers associated with each data record REC in the management table TAB, but grays out or otherwise prevents the selection of registers associated with data records REC where the data set in field FCB indicates "in use."

[0121] Transaction processing unit 1 may monitor the status of information terminal equipment 2, or monitor communication logs from information terminal equipment 2 to transaction processing unit 1, to confirm whether each register is operating normally, and may prevent the selection of registers that are operating normally and are marked as "in use" on the selection screen. In this case, transaction processing unit 1 may also display a message on an information terminal equipment 2 other than the one used by the register that is not operating normally and is marked as "in use," indicating that an abnormality has occurred.

[0122] If the cash register number specified by the information terminal device 2 is "in use", the transaction processing device 1 may forcibly associate the information terminal device 2 that was previously associated with the specified cash register number (hereinafter referred to as the first information terminal device in this paragraph) with the information terminal device 2 that was specified for that cash register number (hereinafter referred to as the second information terminal device in this paragraph). In this case, the transaction processing device 1 may query the first information terminal device and switch to the second information terminal device if the query is not denied. Specifically, when the transaction processing device 1 queries, it may display a query screen such as a pop-up requesting permission on the "in use" first information terminal device, and if the store clerk operates the query screen and a permission response is detected from the first information terminal device, it may switch from the first information terminal device to the second information terminal device. Furthermore, if the request is not denied, this includes cases where, for example, when a register number is specified from the second information terminal device, the transaction processing device 1 queries the first information terminal device, but no response is received from the first information terminal device even after a certain period of time has elapsed, due to a malfunction or other issue at the first information terminal device making it unable to respond, or because the operator is absent. Note that, as described above, if the system is configured to allow confirmation of whether the information terminal device 2 is functioning correctly, for register numbers that are known to be "in use" but are not functioning correctly, the system may switch to the second information terminal device without querying the first information terminal device.

[0123] You may add fields to the data record REB in the function restriction table TAA to set data that represents the scope of application, such as "per store," "store group," or "common to all stores." You may also make it possible to set function settings for the same accounting scene for multiple scopes. "Per store" means that, for example, function settings can be set individually in association with each of multiple stores, and only the associated stores are within the scope of application. "Store group" means that function settings can be set individually in association with each of the multiple store groups defined by dividing multiple stores into several groups, and only the stores belonging to the associated store group are within the scope of application. "Common to all stores" means that the scope of application for a single function setting is all stores. If multiple scopes of application are defined for the same accounting scene, the scope of application shall be selected according to a predetermined priority order. For example, the priority order may be "per store" > "per store group" > "common to all stores." Furthermore, if there are two stores, Store A and Store B, belonging to the same group, and functional settings have been made for the group, and functional settings have been made for Store A at the store level, but not for Store B, then Store A will be subject to the store-level functional settings for Store A, and Store B will be subject to the functional settings for the store group to which Store B belongs.

[0124] The transactions subject to processing are not limited to the buying and selling of goods; they can include a variety of other transactions.

[0125] Each function realized by the processor 11 through information processing can also be partially or entirely realized by hardware that performs non-program-based information processing, such as logic circuits. Furthermore, each of the above functions can also be realized by combining the above-mentioned hardware, such as logic circuits, with software control.

[0126] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These novel embodiments can be carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims of the invention and its equivalents. The invention described in the original claims of this application is listed below. [Note 1] A terminal management means that manages the association between an information terminal device for receiving operations by an operator and the identifier of a registration number in a changeable manner, A processing means that processes a transaction determined in response to an operation on an information terminal device as a transaction relating to the identifier of a registration number associated with the information terminal device on which the above operation was performed by the terminal management means, A transaction processing device equipped with the following. [Note 2] The terminal management means rewrites a storage device that stores the identification code of an information terminal device and the identifier of a registration number in association with each other, so that it stores the identifier of a registration number specified by an information terminal device and the identification code of the information terminal device that specified the identifier of said registration number in association with each other. The transaction processing device described in Appendix 1. [Note 3] The system further comprises a device management means for managing devices used by a given registration number in association with the registration number identifier, The processing means uses the device associated with the identifier of the registration number, which is associated with the information terminal device operated on by the terminal management means, for processing the transaction determined in accordance with the above operation. The transaction processing device described in Appendix 1. [Note 4] The device management means changes the association between the identifier of the registration number and the device in accordance with instructions from the administrator. The transaction processing device described in Appendix 3. [Note 5] The processing means is capable of executing processes that realize multiple functions with respect to transaction processing, A function management means that manages which of the multiple functions that the processing means can implement is permitted to be executed, in association with each of the multiple scenarios in which the information terminal device may be used, A scene management means that associates and manages a registration number identifier with one of several scenes, Furthermore, The processing means executes processing to realize a function managed by the function management means, which is permitted with respect to a scene associated with the register identifier associated with the information terminal device that has been operated by the terminal management means, with respect to the scene associated with the scene management means. The transaction processing device described in Appendix 1. [Note 6] The function management means changes which of the multiple functions that the processing means is capable of executing, according to instructions from the administrator. Transaction processing device as described in Appendix 5. [Note 7] Computers, A terminal management means that manages the association between an information terminal device for receiving operations by an operator and the identifier of a registration number in a changeable manner, A processing means that processes a transaction determined in response to an operation on an information terminal device as a transaction relating to the identifier of a registration number associated with the information terminal device on which the above operation was performed by the terminal management means, An information processing program that enables a function to work. [Explanation of Symbols]

[0127] 1...Transaction processing device, 2...Information terminal device, 3...Input / output device, 4...Peripheral device, 5...Simple drawer, 6...Payment terminal, 7...Management terminal, 8...Communication network, 11...Processor, 12...Main memory unit, 13...Auxiliary memory unit, 14...Communication unit, 15...Transmission path.

Claims

1. A first storage means for storing a terminal device code and a registration number code in association with each other, A second storage means that stores transaction data that represents the details of the transaction and includes the register number code, A first update means updates transaction data, which includes a registration number code stored in the second storage means and associated with the terminal device code of the information terminal device that made the change request, in response to a change request from an information terminal device, in order to change the content of the transaction data represented by the transaction data. A second update means updates the terminal device code stored in the first storage means in association with the notified registration code in response to the notification of the registration code from the information terminal device, It is equipped with, The second update means performs an update in response to a notification of a registration number code included in the transaction data stored by the second storage means. Transaction processing device.

2. A third storage means that stores the registration number code and information about a device other than the aforementioned information terminal device in association with each other, A processing means that performs processing related to the transaction content represented by the transaction data stored in the second storage means using a device related to information stored in the third storage means in association with the registration number code included in the transaction data, The transaction processing apparatus according to claim 1, further comprising:

3. A first modification means for modifying information stored in the third storage means in association with a registration number code in accordance with instructions from an administrator. The transaction processing apparatus according to claim 2, further comprising:

4. The processing means is capable of executing processes that implement multiple functions related to transaction processing, A fourth storage means that stores a data table associated with a scene code, which of a plurality of functions that the processing means can execute is permitted to execute in the scene identified by the scene code, A fifth storage means that stores the registration number code and the scene code in association, Furthermore, The processing means executes processing to realize the functions shown in the data table, by allowing processing of transactions represented by the transaction data stored in the second storage means with respect to scenes identified by scene codes stored in the fifth storage means in association with the registration code included in the transaction data. The transaction processing apparatus according to claim 2.

5. A second modification means for modifying the data table stored by the fourth storage means in accordance with instructions from an administrator. The transaction processing apparatus according to claim 4, further comprising:

6. A first storage means for storing a terminal device code and a registration number code in association with each other, A second storage means that stores transaction data that represents the details of the transaction and includes the register number code, Computers and, The computer in the transaction processing device equipped with the following A first update means updates transaction data, which includes a registration number code stored in the second storage means and associated with the terminal device code of the information terminal device that made the change request, in response to a change request from an information terminal device, in order to change the content of the transaction data represented by the transaction data. A second update means updates the terminal device code stored in the first storage means in association with the notified registration code in response to the notification of the registration code from the information terminal device, and make it work Furthermore, the second update means is configured to perform an update in response to a notification of a registration number code included in the transaction data stored by the second storage means. An information processing program for that purpose.

Images