JPS63278194A - Trade processor - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

[Detailed Description of the Invention] [Industrial Application Field] This invention relates to a transaction processing device, and in particular, by storing a file storing predetermined unit price data for each predetermined rank of a product, and specifying the rank, The present invention relates to a transaction processing device that can read and register rank data from the file.

[Prior Art] When products are sold in bulk at a store, they may be sold at a different unit price than when sold individually. Additionally, products may be sold at different unit prices for member customers and non-member customers. As described above, transaction processing devices that can sell the same product at different unit prices have been known for some time. In such a transaction processing device, a file is provided that stores unit price data predetermined by rank for each product, and by inputting a product code and specifying a rank, a specific γ-value can be read from the file. I am trying to register it.

1 Problem that Komei tries to solve 1 However, as mentioned above, when registering a large number of products that have unit price data by rank, it is necessary to specify the rank for each σ record, so the registration process is difficult. There are problems with low efficiency and a high possibility of input errors.

Therefore, the main purpose of this invention is to specify a rank once during transaction processing such as registration; It is an object of the present invention to provide a transaction processing device that reads data on a transaction basis.

[Means for Solving the Problems] The transaction processing device of the present invention includes a storage means that stores predetermined unit price data for each predetermined rank for each product identification code, and an operator who specifies any rank in the storage means. an input means for inputting a product identification code; and an input means for inputting a product identification code; Each time a product identification code is entered,
The unit price data corresponding to the product identification code is read out from the storage area corresponding to the rank of the storage means.
ll control means.

[Operation] The transaction device according to the present invention stores the unit price data corresponding to the product identification code in the storage means for each rank designated by the product identification code from the input means. The data is read from the storage area corresponding to the data.

Embodiment 1 FIG. 2 is a schematic block diagram showing the electrical configuration of an electronic cash register (ECR) as a transaction processing device according to an embodiment of the present invention, and FIG.
FIG. 4 is an illustration showing a 4-1 device of the keyboard not shown in FIG. 2; FIG. 5 is an illustration showing the storage area of the memory shown in FIG. 2; It is a diagram.

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

In FIG. 2, a CPU 2 is installed in FCRl. CPU2 has PLU file 3. Keyboard 4. A memory 59, a display 6 and a printer 7 are connected. Third
As shown in the figure, P1. ,, U file 30 has
A PLU code storage area 31, a Pl-4U type flag storage area 32, and a rank 1 storage area] are provided. Data is stored in each of the above areas for each product.

P l-U code storage - [The rear 31 is an area for storing the product code (PLU code) of the product. The PtU type flag storage area 32 is an area for storing a PtU type flag indicating whether a product has rank-based unit price data or a product with single unit price data. For example, if the PLU type flag is 1, it indicates that the product has rank-based unit price data, and if it is 0, it indicates that the product has single unit price data. For products that have unit price data for each rank, those unit price data are stored in the rank 1 storage area 33. It is stored in the rank 2 storage area 34 and the rank 3 storage area 35.

In the ptu file shown in FIG. 3, the rank 1 storage area 33 stores unit price data when sold individually, the rank 2 storage area 34 stores price data lower than rank 1, The rank 3 storage area 35 stores price data that is even lower than that of rank 2. The price data stored in the rank 2 storage area 34 is used, for example, when selling to customers who are members of the store, and the price data stored in the rank 3 storage area 35 is used, for example, when selling a large number of products. Applies to the stage where Madome buys. Price data for rank 2 or rank 3 may be calculated by applying the same discount rate to the price data of each product in rank 1, but it may be calculated by applying an arbitrary discount rate to each product. But that's fine. For products that have single unit price data, that unit price data is stored in the rank 1 storage area 33, and the rank 2 storage area 34 and rank 3 storage area 35 are stored in the rank 1 storage area 33, respectively.
is memorized.

The keyboard 4 has a numeric keypad 7' as shown in FIG.
11, rank key 42, payment key 43, PIU key 4
4 is established. The numeric keypad 41 is used to input a PLU code and the like when processing a transaction. The rank key 42 is not shown in FIG. 3 and is used by the operator to specify one of the ranks corresponding to the rank 1 storage area 33 to the rank 3 storage area 35. M2 key 46 for specifying rank 2 and M for specifying rank 3
3 keys 47. The payment key 43 is used to instruct payment processing. The PLU key 44 is used to indicate that one piece of data input from the numeric keypad 41 is an LU code, and is operated following the keystrokes of the numeric keypad 41 manually.

The memory 5 includes a storage area as shown in FIG. 5 in addition to an area storing an operating program for the CPU 2 based on a flowchart shown in FIG. 1 which will be explained later. Fifth
In the figure, the storage area 50 includes a number data buffer 51, a PLU type flag L rear 52, a rank 1 unit price buffer 53, a rank 2 unit price buffer 54, a rank 3 unit price buffer 55, a unit price rank area 5G for the entire transaction, and a unit price for a single item. A rank area 57, a unit price rank buffer 58, a unit price buffer 59, a registration flag area 6°, a sales data cumulative area 61, etc. are provided.

The numeric data buffer 51 is an area for storing data input from the numeric keypad 41.

The PLU type flag area 52 contains the PLU file 3.
The PLU type flags successively retrieved from the PLU type flag storage area 32 of 0 are stored.

The rank 1 unit price buffer 53 stores the unit price data read from the rank 1 storage area 33 of the PLU file 30, and the rank 2 unit price buffer 54 stores the unit price data read from the rank 2 storage area 34 of the PLU file 3o. The data is stored in the rank 3 unit price buffer 55.
The unit price data read from the rank 3 storage area 35 of the LU file 30 is stored.

The entire transaction unit price rank area 56 stores a code indicating the rank that is used from the start to the end of one transaction. In the unit price rank area 57 for single item,
A code indicating the number of items specified for each item is memorized. The unit price rank buffer 58 stores a current issue indicating the rank of the product currently being registered by the CPU 2.

In the five unit price buffers, rank 1 unit price Batsuno 53. Rank 2 unit price buffer 54 or Rank 3
Any unit price data read from the unit price buffer 55 is stored. The registration presence/absence flag area 60 stores a registration presence/absence flag indicating whether or not registration processing has been performed. This registration flag is used, for example, in transaction processing.
It is set to 1 when one product is registered or when any of the rank keys 42 is operated, and is reset to 0 when payment processing is performed. The cumulative sales data area 61 stores the cumulative amount of the amount data stored in the five unit price buffers for each registration.

FIGS. 6A and 6B are diagrams showing key operations in an embodiment of the present invention. In particular, FIG. 6Δ shows a case where all products have multiple unit price data, that is, a case where unit price data for each item is displayed. Figure 6B shows the key operation for pressing down when a product with single unit price data is included.Next, referring to Figure 6Δ and Figure 6B, A specific example of the operation will be explained.

Figure 6A (a) shows the case where all the products to be registered are registered at the unit price of rank 2. The user operates the M2 key 46, then operates the numeric keypad 711 to input the PLU code, and then operates the PLU key 44. And PL for all products
After inputting the U code, the user operates the payment key 43 to perform payment processing.

In this case, the PLU code is 101''', 20
1” and “301” are registered with rank 2 unit price data.

Figure 6A (1) shows a case where the products to be registered include products to be registered with a rank other than the rank specified at the beginning of the transaction.
To specify rank 1, the M1 key 45 corresponding to rack 1 is operated. On the platform where only the next product is registered using rank 2 unit price data, the M2 key 46 corresponding to rank 2 is operated to specify rank 2. Next, operate the numeric keypad 41 to enter the PLU code, for example "
101°' and then operate the P l-U key 44. The product with the PLU code "101" is registered with rank 2 unit price data. PLU code "' 10
1”, rank 2 will be canceled and automatically return to the initially set rank 1. Therefore,
The next input PLU code, for example "201°'
Regarding the product, the unit price data of rank 1 is read and registered. Subsequently, if only the next product is to be registered using the unit price data of rank 3, the user operates the M3 key 47 corresponding to rank 3 in order to specify rank 3.

Next, enter the PIU code, for example '301', and
Press l-U key/1.4. P l-U code'
For the item 301°', unit price data of rank 3 is read and registered. In the same manner as above, P1. ,
, U]-In response to the completion of registration of the code '301', rank 3 is canceled and automatically returns to the initially set rank 1. Therefore, for the product with the next input PLU code, for example '401', unit price data for rank 1 is read out and registered.Payment processing is performed in response to the operation of the payout key 43.In this way, even during the registration process, each time a rank is specified, Since it is possible to register only specific products with a rank other than the initially set rank, flexible operation can be performed.

In FIG. 6B, products with PLU codes "501" and "601" have single unit price data, and other products have rank-based unit price data. FIG. 6B(a) shows key operations when initializing ranks and performing registration processing for products having unit price data for each rank, and then performing registration processing for products having single unit price data. In FIG. 6B, <11) shows a key operation for first registering a product having single unit price data, and then specifying a rank and performing a registration process for a product with unit price data for each rank. ? ! -That is,
Fig. 6B (in a>, to specify rank 3, operate the M3 key 47 corresponding to rank 3, then operate the numeric keypad 41 for each product to enter the PIU code). Operate the PLU key 44.

P1. - If the U code is e.g. '101'' and ``''
A product whose PLU code is "201" is registered as 0 with unit price data of rank 3. A product whose PLU code is, for example, "501" is registered with that single unit price data.

As shown in Figure 6B (a), when registering a product with single unit price data during registration, it is the same as when registering a product with rank-based unit price data. , it is easy to operate because there is no need to distinguish between the two ministries.

In addition, in FIG. 6B(b), after inputting the PLU-]-code of a product having single unit price data, for example, '501' and operating the PLtJ key 44, the rank is determined only for the next product to be registered. In order to specify rank 2, the M2 key 46 corresponding to rank 2 is operated.

Then, enter the product code and PI for that product.
U key 7! Perform operation I4. This allows PLUG
]-For example, the product numbered "101" is registered using rank 2 unit price data. After the registration process, the designation of rank 2 is canceled. Shitak-C1PLU For example, a product with the U code "601" is registered with single unit price data regardless of the designated rank.

FIG. 1 is a flow diagram for explaining the operation of an embodiment of the present invention. Next, an embodiment of the present invention will be described with reference to FIGS. 1 to 6B.

The CPU 2 goes to step 81 (abbreviated as Sl in the figure) J5 to perform initial settings and clear the registration presence/absence flag F in the memory 5, the unit price rank G1 for the entire transaction, and the unit price rank G2 for the single item. In step S2, if there is human power to press the keys, in step S3, the numeric keypad 4
It is determined whether or not 1 has been input, and if the numeric keypad 41 has not been input, in step S6, the PLU key 4 is pressed.
4-14= It is determined whether or not the PLU key 44 has been operated, and if the PLU key 44 has not been operated, in step 823, it is determined whether or not any of the rank keys 42 has been operated, and any rank key is not operated, step S
At 28, it is determined whether the payment key 43 has been operated.

For example, Figure 6A (a>, (b) and Figure 68 (a)
> As shown in FIG. Since it is determined, step 824~
Proceeding to the operation of S27, for example, as shown in FIG. 6B (b), the numeric keypad 41 is operated at the beginning of the transaction and the
If the LU code has been input, it is determined in step S3 that the numeric keypad 41 has been operated, and the process proceeds to steps 84 to S5.

For example, when any of the rank keys 42 is operated for the first time, it is determined in step S24 whether the registration flag F is 0 or not. Since F is initially O, the process proceeds to step 825 and assigns the codes 1 to 3 corresponding to the M1 key 45 to M3 key 47 to the unit price rank for the entire transaction (
G1) Set in area 56. For example, in Figure 6A (
As shown in b), when the M1 key 45 is operated, 1 is set as G1. Next, step S2
7, the set G1 code is displayed on the display 6. Subsequently, in step 822, the registration flag F is set to 1. As shown in Fig. 6(b), if any of the rank keys 42 is operated during registration, instead of setting the unit price rank G1 for the entire transaction, the unit price rank for the single item is set. This is for setting G2.

Therefore, as shown in FIG. 6A(b), the M1 key 4
If the M2 key 46 is operated following the operation in step 5, the CPU 22 determines that F is not O in step S?I, so the process proceeds to step S26, and the M2 key 46 is pressed. The corresponding code 2 is the unit price rank for a single item.
Set it in area 57 of G2).

Next, as shown in FIG. 6A(b), following the operation of the M2 key 46, for example, the PLU code "101"
” is input, continue, P L LJ −1= −44
If has been operated, it is determined in step s3 that the numeric keypad 41 has been operated, and in step S4, the input numeric data, for example "'101", is stored in the buffer 51 of the numeric data <△). Then, in step s5, the numerical data is displayed on the display 6. Subsequently, when the PLU key 44 is operated,
In step s6, it is determined that the PLU key 44 has been operated, and in step S7, the PL code stored in the same number data buffer is converted into PL code.
Search for U file 30. Then, in step S8, it is determined whether or not the same PLU code exists, and if the same PLU code does not exist, step 89
Error processing is performed in step S10, but if the same PLU code exists, the process advances to step S10.

In step S10, the unit price data of the PLU type flag rank 1, rank 2, and rank 3 corresponding to the desired PLU code are read out, and the read PLU type flag is stored in the PLU type flag of the memory 5. (B), the unit price data of rank 1 is stored in the buffer 53 of rank 1 unit price (C1), and the unit price data of rank 2 is stored in the buffer 53 of rank 2 unit price (C2).
4 and store the unit price data of rank 3 as rank 3 unit price (C
3) is stored in the buffer 55.

Subsequently, in step S11, it is determined whether the PLU type flag (B) is 1 or not. If the PLU type flag (B) is 1, unit price data for each rank exists, and the process proceeds to step 813 or step S16. However, if the PLU type flag (B) is O, the unit price data is for each rank. Since there is only one item in unit price rank (D), the process proceeds to step 812 and stores one item in the buffer 58 of unit price rank (D).
Set.

In the case of FIG. 6A (b), the unit price rank (G2) for a single item is not O at the stage when the PLU code par 101'' is input, so the process proceeds from step 813 to step S14, and the unit price rank (G2) for a single item is The sign of unit price rank (D)
Then, in step S15, the single item unit price rank (G2) is reset to 0.

As a result, the unit price rank for a single item is canceled, so when the PLLI code is input next time, the code of the unit price rank for the entire transaction (G1) is stored in the unit price rank (D) buffer 58. Therefore, as shown in FIG. 6A(b), the PLU
If the code '201' is input, the process goes through steps 86 to S11 to step 13 and step S16, and in step 818, in the buffer 58 of unit price rank (D>, corresponding to the M1 key 45,
The code 1 is stored. Note that in step S16,
If it is determined that G1 is 0, step S1
7, error processing is performed.

In step 819, the unit price buffers 53 to 5 for each rank corresponding to the codes 1 to 3 of the unit price rank (D), respectively.
Read the unit price data from the area corresponding to 5 and enter the unit price (E
) is stored in the buffer 59 of For example, if the unit price rank (G2) for a single item is 2'c', and the pt-u code '101'' is input, the unit price of 90 yen corresponding to rank 2, which is not shown in Figure 3, will be displayed. Data is set in five unit price buffers.For example, if the unit price rank (G1) for the entire transaction is 1, and the PLU71-
When the code "201" is input, unit price data of 200 yen corresponding to rank 1 is set in the unit price buffer 59. In step S20, the cumulative sell-to-trade data 31
In area d3, unit price data is cumulatively calculated, and in step S21, the calculation results are displayed and printed.

If all transaction data has been input and the payment key 43 has been operated, payment processing is performed in step 829, and the process proceeds to step 830, where the unit price rank for the entire transaction (G1) and the unit price rank for single item (G2) are processed. ) to 0
Then, in step 331, the registration flag (F) is reset to O to return to the initial state.

[Effects of the Invention] As described above, according to the present invention, each time a product identification code is input from the input means after any rank is specified, unit price data corresponding to the product identification code is input. Since reading is performed from the storage area stored in the corresponding rank of the storage means, there is no need to specify the rank each time a product identification code is input, unlike in conventional transaction processing devices, which simplifies operation and improves processing efficiency. improves performance and reduces input errors.

[Brief explanation of the drawing]

FIG. 1 is a flow diagram for explaining the operation of an embodiment of the present invention. FIG. 2 is a schematic block diagram showing the electrical configuration of an ECR as a transaction processing device according to an embodiment of the present invention. FIG. 3 is an illustrative diagram showing the structure of the PLLJ file shown in FIG. 2. FIG. 4 is a diagram showing the key arrangement of the keyboard shown in FIG. 2. FIG. 5 is an illustrative diagram showing a storage area of the memory shown in FIG. 2. 6A and 6B are diagrams illustrating the operation of one embodiment of the present invention. As shown in the figure, 1 is ECR, 2 is cPU, 3 is PLU
file, 4 is the keyboard, 5 is the message, 6 is the display,
7 is the printer, 3o is the PLU file storage area, 3
1 is the PLU code storage area, 32 is the PLU type flag storage area, 33 is the rank 1 storage area, 34 is the rank 2 storage area, 35 is the rank 3 storage area, 41
is the numeric keypad, 42 is the rank key, 43 is the payment key, 7
1.4 is the PLU key, 45 is the M1 key, 46 is the M2 key, 47 is the LtM3 key, 51 is the numeric data buffer, 52
is P L IJ type flag area, 53 is rank 1 unit price buffer, 54 is rank 2 unit price buffer, 55 is rank 3 unit price buffer, 56 is unit price rank area for entire transaction, 57 is unit price rank area for single item, 58 is unit price rank Buffer, 5 is unit price buffer, 60 is registration flag.”
-Rear, 61 indicates the sales data cumulative area.

Claims (1)

[Scope of Claims] Storage means storing predetermined unit price data for each predetermined rank for each product identification code, instruction means for an operator to specify any rank in the storage means, inputting the product identification code. and a unit price corresponding to the product identification code each time a product identification code is input from the input means in response to any rank in the storage means being specified by the input means and the instruction means. A transaction processing device comprising a control means for controlling data to be read from a storage area corresponding to the rank of the storage means.