JPS63258739A - Pricing data acquisition device - 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) The present invention relates to a pricing data aggregation device that can aggregate specific items of pricing performance data output from a pricing machine.

(Prior art) Pricing machines that issue and affix labels with the product name, date, price, etc. printed on packed products such as fresh foods are used in backyards and stores. .

When such a pricing machine is used, data is aggregated every day to determine the number of shipments, etc., and is used as material for planning production plans, etc.

(Problems to be solved by the invention) Conventionally, data obtained by pricing machines was compiled by storing it in the memory of a computer, but since data is accumulated one after another every day, Because of the problem of not being able to distinguish which day's data is stored, Japanese Patent Publication No. 8473/1984 proposes a device that stores the aggregated data of this type of pricing machine by dividing it into days. There is.

However, in the conventional example, although it is possible to aggregate data divided by day as performance data for using price machines, it is sometimes desirable to aggregate data for each flight within the day, such as shipping in the morning, shipping in the afternoon, etc. The problem was that they could not respond to requests.

Therefore, the present invention provides a pricing data aggregation device aimed at solving the problems of the prior art.

(Means for Solving the Problem) In order to solve the above-mentioned conventional problems, the present invention provides a pricing data aggregation device that aggregates product information such as the price attached to a product for each item. , a pricing machine that issues a label with product information written on each product, and a storage means that cumulatively stores pricing performance data output from the pricing machine using the shipping date and shipping number of the product as keywords. A pricing data aggregation device having the following is provided.

(Operation) Pricing performance data for each product output from the pricing machine is input to the computer. At this time, the computer has
Data on what day and what flight the product was shipped on is entered manually using an input means such as a keyboard.

In the computer, using the manually entered shipping date data and the number of shipments as keywords, the pricing performance data is compiled for each shipping date and number of shipments, and is accumulated and stored in a tally memory.

In addition, if the shipping date and number of shipments are included in the pricing performance data output from the pricing machine, a computer judges and sorts these shipping date data and number of shipments, and then calculates the shipping date and number of shipments. Using both data as keywords, the pricing performance data is accumulated and stored in the storage means.

(Example) Hereinafter, one embodiment of the present invention will be described with reference to the drawings.

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

In the figure, 1 is a CPU and 2 is a CRT.

3 is an input means such as a keyboard, 4 is a tally memory, 5 is a communication memory, and 6 is an input/output board.These elements 1 to 6 constitute a computer, which is connected to a pricing machine 8 by a pass line 7. . The total memory 4 is provided with an area for totaling the pricing performance data for flights 1 and 2 on the current day, flights 1 and 2 on the next day, and flights 1 and 2 on the day after the next day. The pricing performance data includes, for example, product name, price, weight, quantity, etc., as well as information such as product expiration date.

These pricing performance data are printed on a label by the pricing machine 8 and affixed to the product, and are also sent to the memory 4 via the CPU 1.

As shown in FIG. 2, the pricing performance data for each area is compiled using the input means 3, such as the numeric keys, when transferring the pricing performance data from the pricing machine 8 to the memory 4. This is done by specifying the date category and number of flights.

For example, if one flight on the day is specified, the corresponding pricing performance data is stored in the area of the total memory 4 for one flight on the day by inputting 1-1 manually.

That is, the pricing performance data is accumulated and stored in the memory area using the date category and the number of flights as keywords. Furthermore, within each memory area, data is aggregated for each item included in the pricing performance data attached to each product.

FIG. 3 is a flowchart showing the processing procedure of the present invention. Next, this flowchart will be explained.

(1) Start the pricing performance data aggregation program and check whether the date category specified by the pricing machine 8 is 1 (Step PI). If the determination is NO, proceed to the processing from Step 27 onwards. Move and search for the corresponding number in the date category. If the date category is 1, then the number of flights is checked, and if 1 flight is specified (step P2), the total is stored in the area of 1 flight on the day of the total memory 4 (step P2).
), if there are 2 flights (step P4), the total is stored in the area for 2 flights on the day (step ps).

If the corresponding number of flights is not specified, error processing is executed (step pa).

(2) If the date category specified by the price tag 8 is 2 (step P7), 8 lines are used to check the number of flights, and if 1 flight is specified (step pa), the memory area for 1 flight the next day. are stored in total (step P9). Further, if two flights are specified (step Pro), the total is stored in the memory area for two flights the next day (step Pz), and if the number of flights is not specified, error processing is executed (step P12).

(3) If the date category specified by the pricing machine is 3 (step P13), then the number of flights is checked, but if the determination is NO, error processing for date category specification is executed (step P13). P14). When checking the number of flights, if 1 flight is specified (step P+s), the total is stored in the memory area for 1 flight the day after the next day (step P+a), and if 2 flights are specified (step PI7), the memory area for 2 flights the day after the next day is stored. are stored in total (step P18). If the designation of the number of flights does not correspond to 1 flight or 2 flights, error processing is executed (steps P and 9).

In the above example, the date and number of flights are specified by the pricing machine 8, and the total is stored in the corresponding area of the total memory 4.
In the pricing machine 8, an identification number is attached to the production category of the pricing performance data and transmitted to the computer, and the computer reads out the identification number and determines the date and number of deliveries of the corresponding data.
It is also possible to store the total in the corresponding area of the total memory 4.

FIG. 5 is an explanatory diagram showing an example of specifying an identification number in the second embodiment. As shown in the figure, arbitrary identification numbers are used to specify the date classification and number of flights. For example, one flight on date 1 has an identification number of 4, and two flights on date 2 have an identification number of 3.
It is said that

FIG. 4 is a block diagram showing a schematic configuration of the second embodiment. Similarly to the first embodiment, the host computer is
It consists of an input means 3 such as a CPU, CRT 2, and keyboard, a tally memory 4, a communication memory 5, and a turnout capotro, and is connected to a pricing machine 8 by a pass line 7. In addition, the host computer stores data corresponding to identification numbers, dates, and flight numbers in a table, and when the pricing machine 8 transfers the pricing performance data with the identification number attached to the aggregated data to the host computer. The host computer reads out the date and number of flights corresponding to the identification number and stores them in the corresponding memory area.

FIG. 6 is an explanatory diagram showing an example of a tally memory in the second embodiment. In this tally memory, the identification number is stored in areas a, the date in b, the movement in C1, the day of the week in d, and the identification numbers 1, 2, . ... are associated with the date, flight number, and day of the week.

FIG. 7 is a flowchart of a procedure for creating an identification number-total area correspondence table as shown in FIG. 6. This process is performed as follows.

(1) Identification number 1, 2. (Step P)
51)・(2) Enter the date corresponding to the identification number (Step P
52).

(3) Enter the flight number corresponding to the identification number manually (step P53).

(4) Enter the day of the week corresponding to the identification number (Step P
54).

(5) All identification numbers and corresponding dates and flight numbers
, check whether the day of the week was manually set or not.Step P5
5) If the determination is No, the loop processing from steps P51 to pis is repeated, and if the determination is YES, the loop processing is exited and the series of processing is completed.

FIG. 8 is a flowchart showing the processing procedure for aggregating pricing performance data in the second embodiment.

Next, this flowchart will be explained.

When the host computer receives the performance data from the pricing machine 8 (step P6 □), it checks whether the received data is finished data or not (step P62). The date etc. are read out (step P63). Next, check whether the identification number in the correspondence table and the received identification number are equal (step P64), and if the determination is No, step P63)
Repeat the correspondence table reading process, and if the judgment is YES,
The performance data is added to the total area of the designated date and designated side number (step Pea), and then the performance data is added to the total area of the designated day of the week (step P66).

FIG. 9 is an explanatory diagram showing an example of the total area in the second embodiment. Figure (a) shows the designated date and designated side number.
(b) shows the totaling area for the specified day of the week. Here, Fig. 9(a)
, (b) shows the aggregation area where the performance data corresponding to the identification number has occurred with a solid line in relation to the correspondence table in FIG. 6,
Aggregation areas where actual data does not occur are indicated by broken lines.

Although the gist of the present invention has been described above with reference to specific embodiments thereof, it is clear that various modifications and variations of the present invention based on what has been described above are possible.

(Effects of the Invention) As described above, according to the present invention, when aggregating data obtained by a pricing machine, the number of shipments can be sorted, aggregated, and stored together with the date, allowing for more detailed data aggregation. can be done.

[Brief explanation of the drawing]

FIG. 1 is a block diagram of a first embodiment of the present invention, FIG. 2 is an explanatory diagram, FIG. 3 is a flowchart, FIG. 4 is a block diagram of a second embodiment of the present invention, FIGS. Figure 6 is an explanatory diagram, Figures 7 and 8 are flowcharts, and Figures 9 (a) and (b).
is an explanatory diagram. 1...CPU, 2...CRT, 3...Keyboard, 4...Tally memory, 5...Communication memory, 6...
Input/output boat, 7...Pass line, 8...Valuation machine. Patent applicant: Ishida Kouki Seisakusho Co., Ltd. Agent: Minoru Tsuji, patent attorney: Figure 2, 1 rin? Infarction Fig. 5 1 Infarction 2 Hardness Fig. 9 Fig. 7

Claims (2)

[Claims] (1) In a pricing data aggregation device that aggregates product information such as the price attached to a product for each item, there is a pricing machine that issues a label with product information written for each product, and an output from the pricing machine. 1. A pricing data aggregation device comprising: storage means for cumulatively storing pricing performance data using product shipping date and shipping number as keywords. (2) A pricing data aggregation device according to claim (1), characterized in that the shipping date and shipping number of a product serving as a keyword are included in pricing performance data output from a pricing machine.