JPH03263194A - Pos system - Google Patents

Abstract

PURPOSE:To eliminate a memory problem by totalizing the sales of articles by using a memory and utilizing the memory area effectively at a place where the memory area is limited. CONSTITUTION:The sales of an article A is registered on a POS register 1-1. In the POS register 1-1, price collation is performed by a PLU memory 1-2 to generate a transaction log, which is outputted in a transaction log file 1-3 after the transaction is carried out and deposit processing is done. A totalization program 1-6 reads the transaction log out of the transaction log file 1-3 and performs totalization on a single article totalization memory 1-5 or article master file 1-4. The totalization on the article master file 1-4 is performed only when there is no unused area in the totalization area on the single-article totalization memory 1-5, and thus the memory area is utilized effectively. Consequently, the number of article items that the system has never becomes a memory problem.

Description

DETAILED DESCRIPTION OF THE INVENTION [Industrial Application Field] The present invention relates to a POS system for retail stores, supermarkets, and specialty stores, and particularly relates to aggregation of individual products.

[Conventional technology]

Conventionally, this type of memory aggregation method prepares one aggregation area in memory for one product in advance, makes a one-to-one correspondence between the product code and the aggregation area, and performs aggregation for each product. Ta.

[Problem to be solved by the invention]

The conventional memory aggregation method described above always has one aggregation area in memory for product code V, so as the number of product codes increases, the memory area must also be increased, and the number of product items that can be held in the system increases. There was a problem that caused a memory bottleneck.

[Means to solve the problem]

In order to solve the above problems, the present invention secures a certain amount of memory area as a total area, manages the used area and unused area separately, and creates index keys in the used area sequentially based on sales. , expanding the area of use. At this time, the pointer is replaced from the unused area to the used area, and the used area is logically expanded. When the unused area is no longer available, the total is directly recorded on the disk file. Therefore, it has a function to determine whether to aggregate products in a memory file or a disk file, and a function to manage the memory aggregation area.

〔Example〕

Next, the present invention will be explained with reference to the drawings.

FIG. 1 is a block diagram of one embodiment of the present invention.

Sales of product A are registered at the POS register 1-1 (process 1). Make a price inquiry in the PLU memory 1-2 in the POS register 1-1 (processing 2) and create a transaction log (processing 3)
. After the transaction is completed and the custody process is performed, the transaction log is output to the transaction log file 1-3 (processing 4). The aggregation program 1-6 reads transaction logs from the transaction log file 1-3 (processing 5) and aggregates them in the single item aggregation memory 1-5 or product master file 1-4 (processing 6).

Aggregation is performed in the product master file 1-4 when there is no unused area of the aggregation area in the single item aggregation memory 1-5.

FIG. 2 shows the sales registration work (processes 1 to 4) at the POS register 1-1 shown in FIG. 1 in a two-chart format.

When the transaction is started (step 2-1) and the product 2-11 is registered (step 2-2), the FLU memory 1-2 is referred to and the price is checked (step 2-3). PLU memory 1
The layout of -2 is as shown in FIG. 5, and has a product code as a key, a price, a tally pointer, etc. P
If the product 2-11 exists in the LU memory 1-2 (step 2-4), the price is displayed and a receipt is printed (step 2-5). Create a transaction log (step 2-6) and temporarily store it in the transaction log area 2-13 of the internal memory of the cash register. The record image of the transaction log 2-13 at this time is as shown in FIG. 6, and is created by quoting the product code, selling price, and total pointer from the FLU memory 1-2. Register products one after another, and after registering the final product (Step 2
-7), perform payment processing (step 2-8),
Output transaction log 2-13 to transaction log file 1-3.

FIG. 3 is a flowchart of the counting program 1-6 shown in FIG. One cycle of transaction log aggregation starts with reading the second transaction log 2-13 (step 3-1). Read the transaction log file 1-3 and check the total pointer for each item item (step 3-3). As shown in Figure 4, the rules for the tally pointer are that when the tally pointer is zero, no sales have been made yet, and when it is ALL9, there is no unused area in the single item tally memory l-5 and the product master file 1-4. In the case of other values, the totalization is performed at the address indicated by the value in the single item totalization memory 1-5.

In step 3-3, the total pointer is checked, and if it is not ZEP and ALL9, the single item total memory 1-
5 (step 3-4).

If not, that is, zero or ALL9, check whether there is an unused area in the single item tally memory 1-5 (step 3-5), and if there is an unused area, secure the tally area in step 3-6. ), the total is performed in the single item total memory as in step 3-4 (step 3-7). If there is no unused area, product master file 1-4
Aggregation is performed (step 3-8). Once all details of the transaction log have been processed (step 3-9), reading the next transaction log is repeated (step 3-10). FIG. 7 is a layout image of the product master file 1-4, which includes product information as well as a part for totalizing sales using product codes as keys.

FIG. 8 is a record layout image of the single item tally memory l-5. The tally pointer consists of a unique number that includes 0 and does not include ALL, and serves as a search key. The total pointer of the management record 8-1 is zero, and manages the address of the first record of the used area and unused area, that is, the total pointer. Used record 8-2 Unused record 8
The total pointer -3 is other than zero and ALL9 and has a next record pointer in addition to the total pointer. The role of the next record pointer is to manage the next area and to change an area from an unused area to a used area. It also uses logical combinations to do the opposite. The usage record 8-2 has a product code and a tally section, and the single item tally is performed using this usage area.

FIG. 9 shows the structure of the single item tally memory 1-5. The address A indicated by the used area head pointer of the management record 8-1 is the number code of the used area 9-2. The used area 9-2 is connected like a chain by the next record pointer, and the last used area record has the next record pointer set to zero to indicate this. Similarly, the unused area 9-3 also forms a chain using the unused area head pointer and the next record pointer. Since the used area 9-2 and unused area 9-3 are chained like this, it is possible to change from unused area 9-3 to used area 9-2, or vice versa, by changing the pointer. It can be done easily.

〔Effect of the invention〕

As described above, the present invention is effective in that it is possible to use a memory to tally sales of products, and to utilize the memory area effectively in a case where the memory area is limited.

[Brief explanation of drawings]

FIG. 1 is a block diagram of one embodiment of the present invention, and FIG. 2 is a block diagram of an embodiment of the present invention.
Figure 3 is a flowchart of the sales registration process 1 shown in Figure 1, Figure 3 is a flowchart of the single item counting program in the embodiment shown in Figure 1, Figure 4 shows the number of counts pointers in relation to each file in the embodiment shown in Figure 1. Diagram showing the combination of each file by,
FIG. 5 is a schematic diagram of the record image of the PLU memory 1-2 shown in FIG. 1, FIG. 6 is a schematic diagram of the transaction log and product details of the embodiment shown in FIG. The schematic diagram of the record image of the product master file 1-4 shown in Figure 1, and Figures 8 and 9 are the single item tally memo shown in Figure 1, respectively! 71-5 is a schematic diagram of a record image and a schematic diagram showing its structure. FIG. 1-1...POS cash register, 1-2...F
LU memory file, l-3... Transaction log file, 1-4... Product master file, 1-5
...Single item tally memory file, 1-6...
...Aggregation program.

Claims (1)

[Claims] In a POS system that has an input means for registering product sales, a disk file and a memory file as storage means for aggregating sales, index keys are dynamically created within a limited memory area for aggregating individual product sales. A POS system characterized by making effective use of memory area.