JPH01175073A - Transaction processor - Google Patents

Abstract

PURPOSE:To prevent a merchandise from being missupplied by storing merchandise generation data and delivery data respectively in order data files. CONSTITUTION:When data relating to an ordered merchandise are inputted, the inputted data are stored in a storage area at every merchandise in an order file 2. When data relating to the delivery of the merchandise are inputted, the inputted data are stored in the storage area at every merchandise in the order file 2. When report formation is instructed, data relating to each ordered merchandise and data relation to delivered merchandise are read out to form a report.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a transaction processing device, and particularly to a transaction processing device capable of managing ordered products and delivered products.

[Prior Art and Problems to be Solved by the Invention] As a conventional product ordering system, one that utilizes an electronic cash register (hereinafter referred to as ECR) provided in each store is known. When ordering a product using such a system, the operator operates the ECR and inputs the name, code, unit price, quantity, etc. of the product to be ordered.

The input data is transmitted to the host computer, and the host computer orders products from each predetermined vendor.

By the way, in the above product ordering system, the store's ECR
When the host computer receives the order data, the order data is cleared according to a command from the host computer, which causes the following problems. In other words, it is not possible to determine whether the ordered product has actually been delivered or not based on the ECR that processed the order.

Therefore, the main object of the present invention is to provide a transaction processing device that can easily determine whether or not an ordered product has been delivered.

[Means for Solving the Problems] The transaction processing device according to the present invention includes a storage means capable of storing data related to ordered products and delivered products for each product, and a storage device capable of storing data related to ordered products and delivered products. An input means for inputting data, and in response to input of data regarding the ordered product from the input means, writes the input data regarding the ordered product into a storage area for each product of the storage means, and delivers the data from the input means. A storage control means for writing input data regarding delivered products into a storage area for each product of the storage means in response to input of data regarding the product, a report creation means for creating a report, and a report creation means for creating a report. Report creation instructing means for giving instructions from an operator; and report creation for reading data regarding ordered products and delivered products for each product from a storage means and creating a report by the report creating means in accordance with instructions from the report creation instructing means. and a control means.

[Operation] The transaction processing device according to the present invention writes the input data into the storage area for each product of the storage means when data regarding ordered products is input, and when data regarding delivered products is input, The input data is written in a storage area for each product of a storage means, and when report creation is instructed, data regarding ordered products and data regarding delivered products for each product are read from the storage means to create a report.

[Embodiment of the Invention] FIG. 2 is a schematic block diagram showing the electrical configuration of an ECR according to an embodiment of the invention, FIG. T43 is a key arrangement diagram of the keyboard shown in FIG. 2, and FIG. R shown in Figure 2,
FIG. 5 is a configuration diagram of an order data file stored in AM, and FIG. 5 is a configuration diagram of PI and U files stored in RAM shown in FIG. 2.

Next, the configuration of an embodiment of the present invention will be described with reference to FIGS. 2 to 5.

In FIG. 2, the ECRI is provided with a CPU10. A keyboard 11, a display 12, a printer 13, a ROM 14, and a RAM 15 are connected to the CPU10. Further, although not shown, the CPU 10 is connected to the host computer via a dedicated line or the like.

The keyboard 11 has an order key 11 as shown in FIG.
1. Delivery key 112. @Key 113. ST key 114.
X/z key 115. Includes data entry keys 116 and function keys 117.

The ordering key 111 is operated when ordering a product. The delivery key 112 is operated when the product is delivered. @
Key 113. The ST key 114 and the X/Z key 115 are operated when inputting data regarding ordered products and delivered products. The data input key 116 is used to input product name data, order and delivery quantity data, unit price data, and the like. The function key 117 is operated when inputting character data of a product name from the data person key 116, for example. In other words, each numeric key on the numeric keypad 116 can also be used as a key for entering characters other than numbers. Clear key 118 is operated to clear input data. Note that a scanner for reading barcodes may be connected to the CPU 10 in order to input the product code.

The display 12 displays data input from the keyboard 11. The printer 13 prints transaction data and data regarding ordered products and delivered products. The ROM 14 stores an operating program of CPUI O based on the flowcharts shown in FIGS. 7 and 8, which will be explained later.

The RAM 15 stores an order data file shown in FIG. 4 and a PLO file shown in FIG. 5.

The order data file 2 stores data regarding the ordered product for each ordered product, and also stores data regarding the delivered product for each delivered product. Here, the data regarding the ordered product includes a product code, product name data, unit price data, ordered quantity data, and order date data.

Furthermore, the data regarding delivered products includes delivery unit price data, delivery quantity data, and delivery date data. The PLU file 3 stores product name data and unit price data for each product.

6A and 6B are diagrams for explaining key operations on the keyboard shown in FIG. 3; in particular, FIG. 6A shows the case of ordering, and FIG. 6B shows the case of delivery.

When ordering a product, first the order key 111 is operated, then the product code is input from the data input key 116, and then the @ key 113 is operated. Next, product name data is input from the data input key 116,
Subsequently, the ST key 114 is operated. Next, unit price data is input from data person Kaki-116, and then S
T key 114 is operated. Next, Data Person Kaki-1
Order quantity data is input from 16, and then @ key 1 is input.
13 is operated. When data entry has been completed for all products to be ordered, the X/Z key 115 is operated. Please note that data such as the product code of the ordered product is
If it exists in the LU file 3, input of product name data and unit price data is skipped. CPU i-
If a scanner is connected to 0, the product code is input using this scanner. In this way, the ordering process can be performed more easily.

When a product is delivered, first the delivery key 112 is operated, then the product code is input from the data input key 116, and then the @ key 113 is operated. As in the above case, the product code may be input using a scanner.

Subsequently, delivery quantity data is input from the data input key 116, and then the @ key 113 is operated. continue,
Delivery unit price data is input from data person Kaki-116,
Subsequently, the ST key 114 is operated. If the delivered quantity matches the ordered quantity, input of the delivered quantity may be skipped. Furthermore, if the delivery unit price data matches the unit price data at the time of ordering, input of the delivery unit price data may be skipped. When data entry has been completed for all delivered products, the X/Z key 115 is operated.

FIG. 1 is a diagram for explaining the data flow in one embodiment of the present invention, FIG. 7 is a flow diagram for explaining the order processing operation, and FIG. 8 is a flow diagram for explaining the delivery processing operation. This is a diagram. Next, order processing operations and delivery processing operations will be explained with reference to FIGS. 1 to 8.

The store operator performs order processing according to the key operations shown in FIG. 6A. That is, first, data input key 11
6 or input the product code of the ordered product using a scanner (not shown). When a product code is input, CPU10 determines whether the product code exists in the PLU file 3 or not.

If the same product code as the input product code exists in the PLU file 3, the CPU 10 reads the product name data and unit price data corresponding to the product code from the PLU file 3, and stores them in the temporary storage area included in the RAM 15. Remember it. On the other hand, if the same product code as the input product code does not exist in PLU file 3, C
PU10 displays this on the display 12. The operator operates the data person key 116 to input product name data and unit price data in accordance with this operational guidance.

CPU10 stores the input data in the above-mentioned temporary storage area. Next, the operator is the data person Kaki-1
When order quantity data is input from 16, CPU10 stores the input order quantity data in the above-mentioned temporary storage area. Subsequently, the CPU 10 stores data indicating the order date in the order data file 2 along with the product code, product name data, unit price data, and order quantity data stored in the temporary storage area, and transmits the data to the host computer 4.

Based on the transmitted data, the host computer 4
An order is placed for the product from vendor 5. The vendor 5 delivers the product 6 to the store that placed the order.

When the products are delivered, the store operator performs the delivery process according to the key operations shown in FIG. 6B.

That is, first, the product code of the delivered product is input using the data entry key 116 or a scanner (not shown), and then, if necessary, the delivered quantity data and the delivered unit price data are entered. The CPU 10 determines whether the same product code as the input product code exists in the order data file 2 or not. If the same product code does not exist, C
PUl0 displays the error on the display 12. The store manager stops the delivery when this error message is displayed. Therefore, incorrect delivery is prevented.

On the other hand, if the same product code exists in the order data file 2, the CPU 10 subsequently determines whether delivery quantity data has been input. Here, if the delivery quantity data has been input, the CPU 10 stores the delivery quantity data in the area corresponding to the product code of the order data file 2, but if it has not been input, the CPU 10 will place the order with the ordered quantity as the delivery quantity. Store in data file 2.

Subsequently, CPU10 determines whether delivery unit price data has been input. Here, if delivery unit price data is input, CPU10 stores the delivery unit price data in the area corresponding to the product code of the order data file 2.
If not input, the order unit price data is stored as is in the order data file 2 as delivery unit price data. Subsequently, the CPU 10 stores the date data of the delivery date in the order data file 2. Subsequently, when the X/Z key 115 is operated, the CPU10 ends its operation, but when the X/Z key 1
If 15 is not operated, it returns to the initial state and repeats the data input operation described above.

The store manager can print out the contents of the order data file 2 at any time by operating the keyboard 11. That is, when a predetermined key operation is performed, C
PU10 collects the product code, product name data, unit price data, order quantity data,
Order date data.

The delivery unit price data 2, the delivery quantity data, and the delivery date data are read out and printed by the printer 13. By comparing the ordered quantity printed on the report 7 with the delivered quantity, the store manager can grasp whether the products have been completely delivered or not. Also, by looking at this report 7, you can see the delivery date based on the number of units from the order date to the delivery date, making it easier to plan your next order. It should be noted that the store has the advantage of being able to manage ordering and delivery without the use of slips, making the store's office processes paperless.

[Effects of the Invention] As described above, according to the present invention, when data regarding ordered products is input, the input data is written in the storage area for each product of the storage means, and data regarding delivered products is input. When requested, the input data is written to the storage area for each product of the storage means, and when report creation is instructed, data regarding ordered products and data regarding delivered products for each product are read from the storage means to create a report. As a result, it is possible to check whether the ordered product has been delivered or not, and it is also possible to prevent erroneous delivery. Furthermore, since ordering and delivery data can be taken out at any time, there is no need for slips at the time of ordering and delivery, simplifying office work.

[Brief explanation of the drawing]

FIG. 1 is a diagram for explaining the data flow in one embodiment of the present invention. FIG. 2 is a schematic block diagram showing the electrical configuration of an ECR according to an embodiment of the present invention. Third
This figure is a key layout diagram of the keyboard shown in FIG. 2. Fourth
The figure is a configuration diagram of an order data file stored in the RAM shown in FIG. 2. FIG. 5 is a diagram of the PLU file stored in the RAM shown in FIG. 2. FIGS. 6A and 6B are diagrams for explaining key operations on the keyboard shown in FIG. 3. Fig. 7 is a flow diagram for explaining the order processing operation. Fig. 8 is a flow diagram for explaining the delivery processing operation. In the figure, 1 is an ECR, 2 is an order data file, and 3 is a flow diagram for explaining the order processing operation.
is a PLU file, 4 is a host computer, 5 is a vendor, 6 is a product, 7 is a report, 10 is a CPU, 11 is a keyboard, 12 is a display, 13 is a printer, 14 is a ROM
, 15 is a RAM, 111 is an ordering key, and 112 is a delivery key.沁1■ 爲40 Order 1゛-ri7''Ipa9kan-7,-Ichikan7■ Hatsuho principle and

Claims (1)

[Scope of Claims] Storage means capable of storing data regarding ordered products and delivered products for each product; input means for inputting data regarding ordered products as well as data regarding delivered products; and the input means. In response to data regarding the ordered product being input from the input means, the input data regarding the ordered product is written to a storage area for each product of the storage means, and in response to data regarding the delivered product being input from the input means. , a storage control means for writing input data related to delivered products into a storage area for each product of the storage means, a report creation means for creating a report, and a report creation instruction means for giving an instruction to an operator to create a report. and report creation control means for reading data regarding ordered products and delivered products for each product from the storage means and causing the report creation means to create a report in response to instructions from the report creation instruction means. Device.