JPH0823908B2 - Transaction processor - Google Patents

Description

TECHNICAL FIELD The present invention relates to a transaction processing apparatus, and more particularly to a transaction processing apparatus capable of managing products without using a PLU file.

[Prior Art] Conventionally, an electronic cash register (hereinafter referred to as an ECR) that manages each product requires a PLU file that stores information on all the products handled. The PLU file is
Unit price data is stored in advance for each product code, and
A storage area is provided for storing the sales quantity data of the product. When the operator inputs the product code (PLU code) from the keyboard, the unit price data corresponding to the product code in the PLU file is read, the unit price data is registered, and the sales quantity data is stored in the PLU.
Register in a file. By reading the stored contents of this PLU file and creating a report, it is possible to manage each product.

[Problems to be Solved by the Invention] By the way, the above-mentioned PLU file has a problem that it must have a very large storage capacity because it is necessary to store data for all the products handled. . In addition, even if you have PLU files for all products, in stores where there are few types of products that can be sold every day, such as clothing items that sell well depending on the season,
Since most of the PLU files are data that is rarely used, there is a problem that the advantage of having the PLU file is small.

Therefore, a main object of the present invention is to provide a transaction processing device that enables new merchandise item registration and can perform subdivided registration processing.

[Means for Solving Problems] The transaction processing apparatus according to the present invention comprises an input unit for inputting a product code and unit price data for each product, a storage unit for storing the product code and unit price data, and an input unit. And a determination unit that determines whether the input product code and unit price data match the product code and unit price data stored in the storage unit. The transaction processing device further stores the product code and unit price data input from the input unit in the storage unit when the product code and unit price data input from the input unit is different from the product code and unit price data stored in the storage unit. Control to remember. The transaction processing apparatus further includes a report creating means for creating a report based on the data stored in the storage means, an instruction means for the operator to instruct the report creation by the report creating means, and an instruction from the instruction means. And means for controlling the reporting means to produce the report by the reporting means.

[Operation] In the transaction processing apparatus according to the present invention, the product code and unit price data are input for each product, and the data are stored in the storage means. It is determined whether or not the product code and unit price data input from the input means match the product code and unit price data stored in the storage means, and the product code and unit price data input as a result of the determination are stored in the storage means. If the product code and unit price data are different from the stored product code and unit price data, the input product code and unit price data are newly stored in the storage means. Then, in response to the operator's instruction to create a report, the report is created based on the data stored in the storage means.

[Embodiment] FIG. 2 shows a transaction processing apparatus according to an embodiment of the present invention.
It is a schematic block diagram which shows the electric constitution of ECR. FIG. 3 is a diagram showing a key arrangement of the keyboard shown in FIG.
Next, the configuration of an embodiment of the present invention will be described with reference to FIGS. 2 and 3. As shown in Figure 2, EC
CPU2 is provided in R1. A keyboard 3, a display 4, a printer 5, a ROM 6, a RAM 7, and a modem 8 are connected to the CPU 2. The keyboard 3 includes a numeric keypad 31 and a registration type key 32, as shown in FIG. The ten-key pad 31 is for inputting a product code for identifying a product and unit price data of the product. The registration type key 32 is for instructing the type of registration, and includes a normal registration key 321 and a return product registration key 322. The normal registration key 321 is operated when registering the product purchased by the customer, and the return product registration key 322 is operated when the customer returns the product. Although not shown, the keyboard 3 is provided with a mode selector switch for switching between the report creation mode and the registration mode.

The display 4 is the data input from the keyboard 3 and the CPU 2
The calculation result and the like are displayed. In the registration mode, the printer 5 prints and issues a receipt, and
In the report creation mode, a report as shown in FIG. 4 described later is printed and issued. ROM6
Stores the operation program of the CPU 2 based on the flowchart shown in FIG. 1 described later. The ROM 7 is provided with a storage area for storing data input from the keyboard 3, data transmitted from the host computer via the modem 6, and a registration file 70. The registration file 70 is provided with a plurality of records including a product code, a registration type code, unit price data, and a counter. In this embodiment, the record is composed of the above-mentioned items in order to count the product quantity in each transaction in which the product code, the unit price data and the registration type code are all the same. Various forms are selected according to need. The registration file 70 may have a small memory capacity as long as it can register data on products that sell well at the store. Modem 8 is CP
It is for exchanging data between U2 and the host computer. The registration file 70 contains the conventional PL
Since a large amount of data is not recorded like a U file, the file can be transferred to the host computer in a short time.

FIG. 4 is a diagram showing a report issued by the printer shown in FIG. The issuance of the report shown in FIG. 4 is performed by switching the mode changeover switch (not shown) to the report preparation mode and operating a predetermined key of the keyboard 3. The report shown in FIG. 4 is printed with the product code, registration type code, unit price data, and count value read from the registration file shown in FIG. In the row shown in Fig. 4, the unit price of the product with the product code "00001" is 100.
It indicates that 111 pieces were sold in yen, and in the row, 222 pieces of the product code “00001” were sold at a unit price of 200 yen, and in the row, it was the product code “00001” It shows that 333 items that were sold at a unit price of 100 yen were returned, and in the line of, the unit price of the product with the product code "00002" is 30
It shows that 444 pieces were sold for 0 yen. In this embodiment, when the same product is sold at different unit prices, it is possible to know the number of products sold for each selling price, and to know the product quantity of the registration type (normal registration, return product registration). . Further, by subtracting the sales quantity from the purchase quantity and printing it, it can be used as an inventory management file.

Although the report includes an inspection report and a settlement report, when the inspection report is issued, only the data is read in the registration file 70, whereas when the settlement report is issued. After the data is read, the registration file 70 is cleared.

FIG. 1 is a flow chart for explaining the operation of one embodiment of the present invention. Next, the operation of the embodiment of the present invention will be described with reference to FIGS.

When the customer purchases a product, the operator normally operates the registration key 321, and when the customer returns the product,
Operate the return item registration key 322. Then, the operator operates the ten-key pad 31 to input the product code, unit price data, and quantity data of the product. In response, CPU 2 searches registration file 70 to determine whether or not a record having the same product code as the input product code exists in registration file 70. Here, if there is a record with the same product code, it is subsequently determined based on the registration type code of the record whether the registration type of the record and the type of registration operated this time match. . For example, if the registration type in the record is return goods registration and the operation this time is normal registration, it is regarded as different. Here, if the registration types match, it is determined whether or not the unit price data of the record and the unit price data input this time match. When the unit price data match, the counter of the record is updated by the input quantity.

On the other hand, if any of the product code, the registration type code, or the unit price data is different, a record is created based on the input data and stored in the registration file 70.

[Effects of the Invention] As described above, according to the present invention, when data relating to a product is input from the input means, the input product code and unit price data are stored in the storage means and the product code and unit price data. It is determined whether or not they match.
When the input product code and unit price data are different from the product code and unit price data stored in the storage unit, the product code and unit price data input from the input unit are stored in the storage unit. Therefore, since the input product code and unit price data are registered even for unregistered products not stored in the storage means, it is possible to carry out registration processing of products having the same product code and the same unit price thereafter. Product registration becomes possible.

[Brief description of drawings]

FIG. 1 is a flow chart for explaining the operation of one embodiment of the present invention. FIG. 2 is a schematic block diagram showing the electrical configuration of the ECR according to the embodiment of the present invention. FIG. 3 is a diagram showing a key arrangement of the keyboard shown in FIG. FIG. 4 is a diagram showing a report issued by the printer shown in FIG. In the figure, 1 is an ECR, 2 is a CPU, 3 is a keyboard, 5 is a printer, 6 is a ROM, 7 is a RAM, 31 is a numeric keypad, 32 is a registration type key, and 70 is a registration file.

Claims (1)

[Claims] 1. An input unit for inputting a product code and unit price data for each product, a storage unit for storing the product code and unit price data, and the product code and unit price data input from the input unit. A transaction processing device comprising: a discriminating means for discriminating whether or not the commodity code and the unit price data stored in the storage means match, wherein the discriminating means stores the inputted commodity code and unit price data. When it is determined that the product code and unit price data stored in the storage unit are different from the product code and unit price data stored in the storage unit, a unit for controlling the storage unit to store the product code and unit price data input from the input unit; Creating means for creating a report based on the data obtained, and creating the report by the report creating means And instruction means for operator instructs, characterized in that it comprises a report generation control means for controlling so as to create a report by the reporting means in accordance with an instruction of the instruction means, the transaction processing system.