JPH0554894B2 - - Google Patents

Description

[Detailed Description of the Invention] Industrial Application Field The present invention relates to a weighing in-line system that is capable of managing scheduled production quantities, etc. at distribution centers and the like that wholesale fresh foods, etc., to supermarkets and the like with weighed prices. .

2. Description of the Related Art Generally, this type of distribution center handles a wide variety of fresh foods and the like for a large number of stores. The label printer for weighing and pricing calls up the product name, unit price, etc. of the corresponding PLU (Price Luk Up) by key-inputting the individual store code and item number of the supermarket, etc. There is a device that prints a label along with the weight, etc., and issues the label.

There is also an inline system in which a PLU file is previously set inline in each of a plurality of label printers, and each label printer is operated according to this information to issue labels.

Problems to be Solved by the Invention However, there are a wide variety of products handled at distribution centers, and the number of products to be produced differs from store to store. In other words, each store determines the planned production quantity according to the situation such as sales, inventory adjustments, etc., and the distribution center learns the planned production quantity of each shop from the order form or the like. Then, according to these production schedules, workers at the distribution center perform weighing and pricing work. In other words, with this conventional method, it is not possible to collectively manage the amount of discrepancy during weighing and pricing work, and it is time consuming and inconvenient to issue labels according to the planned production volume of each store. be. Furthermore, when considering weighing and pricing work, it is more convenient to perform the work continuously on the same product or for each product for each store, but this is not the case in the past. These tasks are difficult to perform and are performed randomly.

Means to solve the problem Equipped with a file controller that collectively manages the PLU memory that stores product numbers, product names, etc., and the store code memory that stores store codes, unit prices, tares, planned production quantities, etc., and each scale. Multiple label printers that print and issue labels with weight, unit price, price, product name, etc. are connected inline in real time, and inquiries from any label printer to the file controller are sent to the product number for the PLU memory or to the store. This is done by inputting one key of the store code for the code memory, and information such as each store code, unit price, tare, planned production quantity, etc. of different store codes for the same product number as the inquired product number is sent to the file controller, or information on the same store as the inquired store code. Responses regarding information such as each product number, product name, store code, unit price, tare, planned production quantity, etc. for different product codes regarding the code are sequentially received from the PLU memory and store code memory, and labels for the planned production quantity are issued. do.

Function Basically, one file controller equipped with PLU memory and store code memory is connected inline with multiple label printers in real time, and when each label printer assigns a weight value, the file controller is Label issuing information is collectively managed by PLU memory and store code memory. Since the planned production quantity is also stored in the store code memory, various information including the planned production quantity can be obtained by entering either the product number or the store code when making a PLU inquiry for label issuance. The planned production quantity is instructed to the label printer, the number of labels issued is controlled, and the pricing work is collectively managed. Here, in response to such inquiries to the file controller, the file controller side will receive PLU data for different store codes for the same product number if you query by product number, and PLU data for different product numbers for the same store code if you query by store code. Since responses are made sequentially, the label printer side simply issues labels in accordance with the responses from the file controller, and weighs and prices the scheduled production quantity at once for the same product or store.

Embodiment An embodiment of the present invention will be described based on the drawings.
First, Figure 3 shows the system configuration installed in a distribution center, etc. One file controller (FC) 1 has multiple label printers 2 (RP) in real time (loop system). Connected inline. Here, each of the label printers 2 is a backroom printer equipped with an electronic scale and has a function of issuing labels with weighted values. Also, to explain the inline connection, the inline cable 3 of this embodiment is
HDLC (High Level Data Link Control)
or SDLC (synchronized data link control) or a similar procedure. In other words, as an inline system, there is also a multi-drop method in which label printers each having a PLU memory are connected to a personal computer etc. in a batch manner, but in this type of inline system, while communicating with a specific label printer, other label printers It is impossible to interrupt and takes a long time to process. In this regard, according to the real-time inline system of this embodiment, even if there is communication between a specific label printer 2 and the file controller 1, other label printers 2 can intervene. A personal computer (PC) 4 is connected to the file controller 1 through a connection line 5 using a BSC procedure or a procedure similar thereto. This personal computer 4 performs tasks such as setting and changing the PLU file of the PLU memory group provided in the file controller 1 and the store code file (described later) of the store code memory group.

Next, the file controller 1 has
The contents of the PLU memory 6 are shown in FIG. 4, and the contents of the store code memory 7 are shown in FIG. First, the PLU memory 6 stores product numbers for various products (for example, "0001", "0002", etc.), product names corresponding to the product numbers (for example, "beef shoulder loin", "sliced beef thigh", etc.), and other product information. It is something. Further, the store code memory 7 stores unit price, planned production quantity, production results, and other information (for example, tare, etc.) for each store code (for example, "01", "02", etc.) corresponding to each product number. be. Storage information in both the PLU memory 6 and the store code memory 7 is set by input from the personal computer 4. That is, the fourth
The contents of the PLU memory 6 and store code memory 7 in the file controller 1 as shown in FIG. ing. or,
The contents of the PLU memory 6 and code memory 7 are also changed by instructions from the personal computer 4. In other words, the personal computer 4 performs setting/changing operations for the PLU memory 6 and store code memory 7 in the file controller 1. Therefore, in this embodiment, the information on the planned production quantity stored in the store code memory 7 is also set by the personal computer 4. The PLU memory 6 and the store code memory 7 are used to store in advance a plurality of PLUs used in the label printer 2 and collectively manage them. The production performance data in the store code memory 7 is transmitted from the label printer 2 in accordance with the label issuing operation described later.

In such a configuration, a file controller 1 and each label printer 2 are used for weighing and pricing work.
The data processing in between will be explained with reference to the flowchart on the label printer side shown in FIG. 1 and the flowchart on the file controller side shown in FIG.
First, after the power is turned on, each memory, I/O port, etc. are initialized, and the process moves to the main routine. In this main routine, mode determination is made for various modes, and work is performed according to the mode. If we are currently in label issuing mode, we will proceed to each task in this label issuing mode. First, in the PLU inquiry mode, an inquiry request to the file controller 1 is made by key input. In this embodiment, the inquiry method is performed by keying in either the product number or store code, and the store code sequential inquiry mode responds with different store codes for the same product number as the inquired product number, and the store code sequential inquiry mode, in which different store codes are responded sequentially for the same product number as the inquired product number. A sequential product number inquiry mode in which different product numbers are responded to in sequence for the store code is set and can be selected by key input or switch operation.

Therefore, when an inquiry request is made, it is first determined whether the inquiry mode is in the order of product numbers or in the order of store codes. If the store code is entered in the product number sequential inquiry mode, the store code and other information (for example, address) for determining the same store code are set in the transmission buffer for the file controller 1. On the other hand, if it is in the store code sequential inquiry mode in which the product number is keyed in, the product number and other information for determining the same product number are set in the transmission buffer. As a result, an inquiry message for the file controller 1 is created and sent to the file controller 1.

In response to such an inquiry message, the file controller 1 responds according to the flowchart shown in FIG. First, the file controller 1 side is initialized after power is turned on, and then stands by in a state where it can receive data from the label printer 2. When an inquiry message as described above is received, if it is a PLU inquiry, it is determined whether the inquiry is in the product number sequential inquiry mode or the store code sequential inquiry mode. This is determined based on whether the inquiry message contains the store code or the product number. That is, in the product number sequential inquiry mode, since the store code is fixed, this store code is included in the inquiry message, and in the case of the store code sequential inquiry mode, the opposite is true.

If we are currently in the store code sequential inquiry mode, the file controller 1 will store each store code, unit price, planned production quantity, production results, and other stores for different store codes with the same product number as the inquiry product number included in the inquiry message. A state is reached in which the information stored in the code memory 7 can be responded to sequentially for each store code. More specifically, in this embodiment, responses are not necessarily made for all store codes, but for those whose production results have reached the production planned quantity in the corresponding product number (inquiry product number) in the store code memory 7, and the production schedule. (i.e., the planned production quantity is zero)
are excluded, so only unfinished products that have not reached the planned production quantity are searched. For example, in the store code memory 7 in Fig. 5, the inquiry product number is "0002".
If so, basically the store code is "01"
In this example, the store code "02" will be searched sequentially. Since the actual production has reached the planned production quantity for the store code "01", the store code "02" whose actual production has not reached the planned production quantity will be searched sequentially. ” will be searched.

On the other hand, in the product number sequential call mode, each product number, product name, store code, unit price, planned production quantity,
A state is reached in which production results and other information can be sequentially responded to for each product number from the PLU memory 6 and store code memory 7. More specifically, in this case as well, responses are not necessarily given to all product numbers sequentially, but only those whose production results have reached the planned production quantity in the corresponding store code (inquiry store code) in the store code memory 7 Since items without plans are excluded, only unfinished products that have not reached the planned production quantity are searched. For example, in the store code memory 7 shown in FIG. 5, if the inquiring store code is "01", basically all product numbers are sequentially searched such as "0001", "0002", "0003", etc. However, in this example, from the store code "01", product numbers "0001" and "0002" that have reached the production schedule, and product number "0004" that is not scheduled to be produced are excluded, and the product number "0003" is used.
"0005" will be searched sequentially.

In either mode, when the store code memory 7 is searched for unfinished products, the PLU in the file controller 1 is
Search the memory 6 for the corresponding product number. Then, the product number, the corresponding product name, and other information (for example, address) are set in the transmission buffer to the label printer 2. Furthermore, the data of the memory part of the corresponding product number based on the store code memory 7 search results (i.e. store code, unit price, planned production quantity, etc.)
is set in the transmission buffer to the label printer 2. As a result, a response message for the label printer 2 is created and sent to the label printer 2 that made the inquiry. On the other hand, in response to the above-mentioned inquiry, if production of all products has already been completed and there is no corresponding product, a completion message is created and sent to the label printer 2.

After transmitting the inquiry message to the file controller 1, the label printer 2 waits to receive a response message from the file controller 1. When this response message is received, the response information in the message is stored in the label printer's own memory. Here, as a response message from the file controller 1, as mentioned above, whether all products with the same product number or the same store code have already been discontinued (end of production message), or if there are unproduced items and the product number is There are two options: one that includes PLU information.
And this content, i.e. product number, product name, store code,
The unit price, scheduled number of issues, etc. are displayed on the display section.

This ends the PLU inquiry mode and shifts to the actual label issuing operation in the label issuing mode. In other words, when a label issue instruction is given, the scheduled number of issues received in response to the above-mentioned inquiry is compared with the actual production number of the product, that is, the production record, and if the production result does not reach the planned production number, the label is issued. For this purpose, a printing buffer for weight, price, etc. is created along with the unit price, product name, etc., and a label is printed and issued. When the label is issued in this way, the number of production (production results) is increased by +1. Furthermore, production performance data (+1) is stored in file controller 1.
This production performance data is sent to the file controller 1. On the file controller 1 side that receives this production record data, it is added and stored in the memory of the production record in the corresponding product number and store code part in the store code memory 7. Then, the process returns to the first main routine, so label issuance is repeated until the actual production reaches the planned production quantity.

According to this embodiment, since the production results for each label issue are transferred and accumulated in the store code memory 7 in the file controller 1, the same information is sent from the label printer 2 side to the file controller 1 again. Even if there is a PLU inquiry using the same store code for the product number, it is possible to immediately respond by checking whether the planned production quantity has been reached (production has ended) without having to search for the product number, etc. in response to the inquiry. Furthermore, it is not always the case that one label printer 2 performs the weighing and pricing/label issuing work for the same product, but there are cases where labels are issued using other label printers 2. The label issuance results until the planned production quantity is reached, that is, the value of the production results, should be grasped by all of these label printers 2, and even if labels are issued by other label printers 2, the production results will be recorded in the store. Since it is stored in the code memory 7, it is possible to check the contents including the results of other label printers 2. In other words, if the file controller 1 side does not have production performance data,
When the same product is handled by multiple label printers 2, there is no relationship between their label issuance records, and each label printer 2 is able to issue labels up to the planned production quantity. However, according to this embodiment, the system The total production can be controlled to the planned quantity. In this way, the file controller 1 always knows the production results, and even if it is necessary to process performance data, data is exchanged between the personal computer 4 and the file controller 1, and the label printer The second party can concentrate on the original weighing and pricing work without being affected by interruptions or the like.

Incidentally, when the actual production reaches the planned production quantity, labels cannot be issued for the product, but this is insufficient to deal with additional requests from stores. However, in this embodiment, even if the actual production reaches the planned production quantity, additional labels can be issued by setting additional production by operating a key on the label printer. Therefore, after comparing the planned production quantity with the actual production quantity, even if the actual production quantity reaches the planned production quantity, the system does not immediately return to the main routine, but instead checks whether additional production has been set, and when setting additional production, After inputting the additional production quantity using a key, this additional production quantity is added to the previous production planned quantity to create a new production planned quantity, and the process moves to the label issuing operation side. Thereby, labels can be issued according to the situation at the time.

As described above, according to this embodiment, when weighing and pricing a certain product at a distribution center, if the PLU inquiry to the file controller 1 is set to the store code sequential inquiry mode, the label for the product handled at the desired store can be displayed. By obtaining the information necessary for issuance, you can weigh and price all the products for that store. On the other hand, if the PLU inquiry is set to the product number sequential inquiry mode, it is possible to process all the stores' products at once for the products to be weighed and priced. In this way, no matter which inquiry mode is used, just by keying in either the product number or store code, sequential information including the other store code or product number information is obtained, so it is possible to collect information in a unified manner. It is possible to reliably carry out weighing and pricing work for the required number of production schedules, thereby increasing efficiency. In response to such a PLU inquiry, labels that no longer need to be issued are excluded, which is more efficient.
Further, since the store code sequential inquiry mode and the product number sequential inquiry mode can be selected by key input or the like, processing can be performed in any desired mode.

By the way, if the store code memory 7 mentioned above is divided into a plurality of blocks and each block is specified by a block number, it will be convenient to handle a wider variety of store codes. For example, what is shown in FIG. 5 shows the state of a block with a certain block number in the store code memory 7, and the blocks with other block numbers are constructed in the same manner. In other words, it can be considered that blocks having the same block configuration as shown in FIG. 5 are divided into blocks by adding block numbers to each block. In this case, when making a PLU inquiry, the product number and store code must be entered from the label printer 2, and the inquiry mode must be selected and set, as described above. In order to identify which block the store code in the store code memory 7 belongs to, the user is required to key in the block number in addition to the product number and store code.
Then, processing is performed according to the inquiry mode, but no matter which inquiry mode is used, the processing is performed within the range of the key-input block number. That is,
In the store code sequential inquiry mode, store codes with the same product number within the designated block number in the store code memory 7 are searched and responded to sequentially.
If it is in the product number sequential inquiry mode, the designated block number in the store code memory 7 and the product number in the store code will be searched and responded to sequentially.

There are a large number of stores handled by the distribution center, and delivery truck services to these stores are also determined by region. There are also cases where it is desired to price each pallet. Regarding these points, by dividing the store code memory 7 into a plurality of blocks in this way, it can be used for convenience such as weighing and pricing for each truck delivery.

Effects of the Invention As described above, the present invention connects a file controller that collectively manages the PLU memory and store code memory and a plurality of label printers inline in a real-time manner, and prints each label using information in the PLU memory and store code memory. Although it centrally manages the label issuing work for printers, the planned production quantity is also stored in the store code memory, and by keying in either the product number or store code at the time of PLU inquiry, the other responds in sequence. Since information on the planned production quantity is also received, it is possible to collectively control and manage the planned production quantity when the label printer is used to issue labels.This inquiry is particularly useful for store code sequential inquiries that are regulated by product number. The mode is the product number sequential inquiry mode, which is regulated by the store code, so that store codes or product numbers can be responded to sequentially, so products with the same product number or products handled by the same store can be weighed together and according to the planned production quantity. It is possible to increase the efficiency of weighing and pricing work for various stores at distribution centers, etc. Also, since items that no longer need to be produced are excluded in any inquiry mode, search is possible. The response processing is fast, and furthermore, such inquiry modes can be selected arbitrarily and work can be done in a mode according to the product situation, etc. Furthermore, the store code memory in the file controller can be divided into multiple blocks. Since the weights are divided, it is possible to weigh and price each truck or pallet at a distribution center, for example.

[Brief explanation of drawings]

The drawings show one embodiment of the present invention; FIG. 1 is a flowchart of operation control in a label printer, FIG. 2 is a flowchart of operation control in a file controller, FIG. 3 is a wiring diagram of the entire system, and FIG. Figure 4 is an explanatory diagram of PLU memory, Figure 5
The figure is an explanatory diagram of a store code memory. 1... File controller, 2... Label printer, 6... PLU memory, 7... Store code memory.

Claims (1)

[Scope of Claims] 1. A file controller that collectively manages a PLU memory that stores product numbers, product names, etc., and a store code memory that stores store codes, unit prices, tares, planned production quantities, etc.; Multiple label printers that print and issue labels with unit price, price, product name, etc. are connected inline in real time, and inquiries from any label printer to the file controller are sent to the product number for the PLU memory or the store code memory. This is done by inputting one key of the store code for the file controller, and information such as each store code, unit price, tare, planned production quantity, etc. of different store codes for the same product number as the inquired product number, or information about the same store code as the inquired store code. Each product number, product name, store code, unit price, tare weight,
The response regarding information such as the planned production quantity is sent to the PLU.
A weighing inline system is characterized in that it sequentially receives labels from a memory and store code memory and issues labels for the number of scheduled productions. 2. The inline measurement system according to claim 1, wherein the file controller responds to an inquiry from a label printer by excluding PLUs whose planned production quantity is zero and PLUs whose production quantity has reached the planned production quantity. system. 3 Responses to the file controller regarding information such as each store code, unit price, tare, planned production quantity, etc. for different store codes for the same product number as the inquired store code, and each product number and product name for different product numbers for the same store code as the inquired store code. Claim 1, characterized in that responses regarding information such as store code, unit price, tare, and planned production quantity can be freely selected.
Weighing in-line system as described in section. 4 A file controller that centrally manages the PLU memory that stores product numbers, product names, etc., store code memory that stores store codes, unit prices, tares, planned production quantities, etc., and each of them is equipped with a scale to store weights, unit prices, prices, product names, etc. A plurality of label printers that print and issue labels are connected inline in real-time, and the store code memory in the file controller is divided into multiple blocks and identified by block numbers, and any label printer can print the store code to the file controller. Inquiry to the product number for the PLU memory or the store code for the store code memory and key input of one of the blocks, and in the inquiry block number to the file controller, enter a different store code for the same product number as the inquired product number. Please respond with information such as each store code, unit price, tare weight, planned production quantity, etc., or information such as each product number, product name, store code, unit price, tare weight, planned production quantity, etc. of different product numbers for the same store code as the inquiring store code.
Receive sequentially from PLU memory and store code memory,
This is a weighing in-line system that is characterized by issuing labels for the scheduled production quantity.