JP7226117B2 - Order entry device, order entry method and order entry program - Google Patents

Description

The present invention relates to an order entry device, an order entry method and an order entry program.

In a sales management application that manages ordering and shipping of products, when an order for a product is received, processing is performed to allocate inventory for the ordered product. Inventory allocation is to allocate the ordered quantity of products from inventory for each ordered product. When simply managing the inventory quantity, the inventory quantity of the product is reduced by the number of orders for the product, and the product is shipped. In addition, if it is necessary to manage product deadlines, etc., it is also possible to assign attribute information to each inventory product and perform inventory allocation based on the concept of first-in, first-out, so that products with the earliest manufacturing dates are shipped first. It is done.

For example, Patent Literature 1 discloses a method of performing inventory allocation for products that match customer attributes based on customer attribute information, product identification information, and the like.

JP 2008-105795 A

From the viewpoint of traceability and quality control, product lot management is performed, for example, assigning the same lot number to products manufactured in the same factory line on the same day. By recording information such as the manufacturing date and manufacturing factory line in association with the lot number, it is possible to know the product information from the lot number. It can be carried out.

However, even if you want to allocate inventory based on lot numbers, such as allocating products with lot numbers that meet specific conditions when receiving an order from a specific customer, the conventional method performs inventory allocation on a product-by-product basis. For example, you can only allocate inventory based on products, such as allocating products with early lot numbers first, or allocating products with specific lot numbers first, and you cannot allocate inventory based on lots. I have a problem.

In one aspect, an object of the present invention is to provide an order entry device, an order entry method, and an order entry program capable of realizing inventory allocation on a lot basis.

In one aspect, an order entry input device comprises: an order information reception unit that receives input of a customer code, a product code, and an order quantity; a lot extraction unit for extracting a lot number corresponding to an allocation condition set in a customer code whose corresponding manufacturing information is input to the order information reception unit; an inventory allocation receiving unit that receives an input of the allocation quantity to be allocated from the inventory of the lot number extracted by the unit.

Lot-based inventory allocation can be realized.

FIG. 1 is a block diagram showing an example of a functional configuration of a server device 10 according to the first embodiment. FIG. 2 is a diagram showing an example of an order entry screen. FIG. 3 is a diagram showing an example of order information 13A1. FIG. 4 is a diagram showing an example of the received order information 13A2. FIG. 5 is a diagram showing an example of the allocation condition information 13B. FIG. 6 is a diagram showing an example of lot information 13C. FIG. 7 is a diagram showing an example of lot information extraction transition. FIG. 8 is a diagram showing an example of the lot inventory screen. FIG. 9 is a diagram showing an example of allocation information 13D. FIG. 10 is a diagram showing another example of the order entry screen. FIG. 11 is a flowchart illustrating the procedure of order entry processing according to the first embodiment. FIG. 12 is a flowchart illustrating the procedure of lot extraction processing according to the first embodiment. FIG. 13 is a flowchart illustrating the procedure of lot determination processing according to the first embodiment. FIG. 14 is a flowchart illustrating the procedure of inventory allocation determination processing according to the first embodiment. FIG. 15 is a diagram showing a hardware configuration example of a computer.

An order entry device, an order entry method, and an order entry program according to the present application will be described below with reference to the accompanying drawings. Note that this embodiment does not limit the disclosed technology. Further, each embodiment can be appropriately combined within a range that does not contradict the processing contents.

[System configuration]
FIG. 1 is a block diagram showing an example of a functional configuration of a server device 10 according to the first embodiment. The sales management system 1 shown in FIG. 1, as just one aspect, is packaged with various functions related to sales management, such as sales, billing, accounts receivable, receiving orders, ordering, allocation, receiving, shipping, and inventory management. provides sales management services.

As shown in FIG. 1, the sales management system 1 can include a server device 10 and a client terminal 50 . These server device 10 and client terminal 50 are communicably connected via a network NW. Any type of communication network such as the Internet or a LAN (Local Area Network) may be employed as the network NW, regardless of whether it is wired or wireless. Note that FIG. 1 shows an example in which one client terminal 50 is connected to one server device 10 for convenience of explanation, but it is assumed that one server device 10 is connected to a plurality of client terminals 50 . Do not interfere.

The server device 10 is an example of a computer that provides the sales management service described above.

As one embodiment, the server device 10 can be implemented by installing a sales management program that realizes functions corresponding to the sales management service described above as package software or online software in any computer. For example, the server device 10 can be implemented as a server that provides on-premises functions related to the sales management service described above. The server device 10 may be implemented as a SaaS (Software as a Service) type sales management application to provide the above sales management service as a cloud service.

As just one example of such a sales management service, the following description will be given by citing an example in which a plurality of functions listed below are provided in a package. The above sales management services include "Sales", "Invoicing", "Receivables", which are standard in sales management, "Order receipt", "Order", "Allocation", "Receive", "Shipment", or Functions such as "inventory management" are packaged. For example, in the above "order receipt", in addition to functions such as "order entry" for entering various information related to orders when accepting orders for products, such as customer, deadline, and data corresponding to slip items such as products, A function such as "inventory allocation" for allocating products in stock is provided.

The client terminal 50 corresponds to an example of a computer used by a client receiving the sales management service described above. As a mere example of such a client, organizations such as business operators involved in sales management, and related persons who belong to such organizations may be mentioned. For example, a specific user of the client terminal 50 is a wholesaler operator. The client terminal 50 may have any hardware configuration as long as it is a terminal that can use the services provided by the server device 10 . As an example only, the client terminal 50 corresponds to a desktop or laptop personal computer. This is merely an example, and the client terminal 50 may be any computer such as a mobile terminal device or a wearable terminal.

[One aspect of the challenge]
As explained in the background art section above, the prior art including Patent Document 1 above only performs inventory allocation on a coarse granularity basis, such as items and manufacturing dates, so customer satisfaction is reduced. may be unavoidable.

For example, even if the product is the same item, the factory or line where the product is manufactured may be different. At this time, the appropriate inventory differs depending on the customer who purchases the product. As just one aspect, if the customer prioritizes avoiding the risk of recalling all products, even if the product is the same item, they would like to purchase products manufactured in different factories or on different lines in a distributed manner. There is Another aspect is that customers who give priority to uniform product quality want to purchase products that are manufactured in the same factory or on the same line.

In spite of this fact, the above conventional technology can only allocate inventory on a first-in, first-out basis so that products with earlier manufacturing dates are shipped first, so the following problems occur. Sometimes. For example, customers who prioritize risk aversion may be allocated inventory manufactured in the same factory or on the same line, and customers who prioritize uniform quality may be allocated inventory manufactured in a different factory or on a different line. be. In this way, when inventory allocation is carried out in a way that goes against customer needs, even if the quality of each product is sufficient, the inventory allocation may contribute to a decline in customer satisfaction.

[One aspect of problem-solving approach]
Therefore, the order entry function according to the present embodiment adopts an approach of realizing inventory allocation based on units called "lots" used from the aspects of traceability and quality control in product production management. In the following description, the same lot number is given to products manufactured on the same day on the same factory line in the present embodiment.

In other words, the order entry function according to the present embodiment enables the setting of allocation conditions for each lot and each customer in order to realize inventory allocation based on lots. When an order is entered, a lot that can be allocated is automatically extracted according to the allocation conditions, and inventory allocation can be performed for each lot. In addition, the allocation conditions are checked when entering the number of orders received for each lot.

By realizing such a mechanism for order entry and inventory allocation, and setting the above allocation conditions from the viewpoint of traceability management and deadline management, it becomes possible to allocate inventory based on lots in a form that conforms to transaction rules. . For example, it is possible to realize inventory allocation such as allocating inventory of different lots to customers who prioritize risk avoidance, or allocating inventory of the same lot to customers who prioritize uniform quality. As a result, it is also possible to improve customer satisfaction through inventory allocation.

[Configuration of server device]
Next, a functional configuration of the server device 10 equipped with an order entry function according to this embodiment will be described. As shown in FIG. 1 , the server device 10 has a communication interface 11 , a storage section 13 and a control section 15 . Although FIG. 1 shows a solid line representing the relationship of data transfer, for convenience of explanation, only the minimum portion is shown. That is, input/output of data regarding each processing unit is not limited to the illustrated example, and input/output of data other than illustrated, for example, between the processing unit and the processing unit, between the processing unit and data, and between the processing unit and the external Input/output of data between devices may be performed.

The communication interface 11 is an interface that controls communication with another device such as the client terminal 50 .

As an example only, the communication interface 11 can employ a network interface card such as a LAN card. For example, the communication interface 11 receives various inputs related to order slips and various operations related to inventory allocation from the client terminal 50, and also sends various screens related to order slips, inventory allocation, and inventory allocation check results to the client terminal 50. or send.

The storage unit 13 stores data used for various programs such as the OS (Operating System) executed by the control unit 15, the above-mentioned sales management program, or the order entry program in which the above order entry function is modularized. It is a functional part that

As an example only, the storage unit 13 corresponds to an auxiliary storage device in the server device 10 . For example, HDDs (Hard Disk Drives), optical disks, SSDs (Solid State Drives), etc. correspond to auxiliary storage devices. In addition, flash memory such as EPROM (Erasable Programmable Read Only Memory) also corresponds to the auxiliary storage device.

The storage unit 13 stores order information 13A, allocation condition information 13B, lot information 13C, and allocation information 13D as an example of data used in the program executed by the control unit 15 . In addition to these data, the storage unit 13 may store data referred to or generated by the above order entry program, such as the above sales management service account. The order information 13A, the allocation condition information 13B, the lot information 13C, and the allocation information 13D will be explained together with the explanation of the control unit 15 that refers to or generates each data.

In addition, FIG. 1 shows only one example of the data referred to or generated by the order entry program, but other data may be stored in the storage unit 13 . For example, data referenced or generated by a program other than the order entry program described above, such as a sales management program that is package software, may be stored.

The control unit 15 is a functional unit that performs overall control of the server device 10 .

As one embodiment, the control unit 15 can be implemented by a hardware processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). Here, a CPU and an MPU are illustrated as examples of processors, but any processor can be used regardless of whether it is a general-purpose type or a specialized type. Alternatively, the control unit 15 may be realized by hardwired logic such as ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).

By executing the order entry program, the control unit 15 virtualizes the processing unit shown in FIG. come true. Here, an example in which an order entry program corresponding to the order entry function is executed among the functions packaged as the sales management service is given, but the program that runs on the server device 10 is limited to this. not. For example, package software of the sales management program described above may be executed, or arbitrary functions of the sales management services described above may be extracted and executed as a program module, or referenced as a library. I don't mind.

For example, as shown in FIG. 1, the control unit 15 has an order reception information reception unit 15A, a lot extraction unit 15B, an inventory allocation reception unit 15C, and an inventory allocation determination unit 15D.

The order information reception unit 15A is a processing unit that receives order information.

As an example only, the order receipt information receiving unit 15A can receive an order receipt creation request from the client terminal 50 whose account for the sales management service described above has been successfully authenticated. For example, when receiving an operation of pressing an icon such as "order entry" on the menu screen displayed on the client terminal 50, the order entry information reception unit 15A causes the client terminal 50 to display the order entry screen shown in FIG. Through an input operation on this order input screen, the order information receiving unit 15A receives input of order information such as customer information, scheduled date information, and order item information.

[Order entry screen]
FIG. 2 is a diagram showing an example of an order entry screen. As shown in FIG. 2, the order entry screen 200 includes various GUI (Graphical User Interface) components. For example, on the order input screen 200, text boxes 210, 220, 230 and 240A are associated with items such as order slip number, order date, customer (customer), scheduled shipping date, scheduled delivery date, and scheduled acceptance date. ~240C are placed.

Here, the "order receipt number" refers to an example of identification information assigned to the order receipt. numbered automatically. "Order date" refers to the date on which an order for a product is accepted. "Customer (customer)" refers to the name of a customer, which is identified by a customer code registered in a customer master (not shown) or the like on a computer in association with the customer name. "Scheduled shipping date" refers to the date on which the product is scheduled to be shipped to the customer. "Scheduled delivery date" refers to the date on which the product is scheduled to be delivered to the customer. "Scheduled acceptance date" refers to the date on which the acceptance inspection of the product at the customer's site is scheduled.

For example, the date when the order entry screen 200 was generated is automatically entered in the text box 220 corresponding to "order date". Needless to say, the date value entered in the text box 220 can be edited via a numeric keypad or the like.

Also, "customer (customer)" corresponds to an example of customer information. For example, by entering a customer code in the text box 230, the customer name corresponding to the customer code is retrieved from the customer master and automatically entered in the text box 230A. As a matter of course, the customer code corresponding to the customer name may be retrieved from the customer master and input to the text box 230 by inputting the customer name into the text box 230A. Although FIG. 2 shows a text box as a GUI component for inputting customer information, this is merely an example, and other GUI components such as pull-down menus and combo boxes may be used.

Also, the "scheduled shipping date", the "scheduled delivery date", and the "scheduled acceptance date" correspond to an example of scheduled date information. For example, by accepting date text input via the text boxes 240A to 240C, schedule information including "scheduled shipping date", "scheduled delivery date" and "scheduled acceptance date" can be entered. Although FIG. 2 shows a text box as a GUI component for entering schedule information, this is only an example, and other GUI components such as a date input widget with a calendar and a pull-down menu can be used. I don't mind.

In addition to the GUI component for inputting customer information and schedule information, the order input screen 200 may include a table 250 for receiving input of order product information. As shown in FIG. 2, the table 250 accepts input of ordered product information on a line-by-line basis, just as an example. That is, in the row direction of the table 250, from the left, input fields for "product code" and "product name", input fields for "order quantity", input fields for "order unit price", and "lot number" are arranged. are arranged.

For example, when a value is entered in one of the entry fields of "product code" or "product name", the other is automatically entered by searching for the other from a product master (not shown). In addition, since the "order unit price" is also determined by the product, the "order unit price" entry field also contains the order unit price retrieved from the product master or the unit price master (not shown) in which the unit price of the product is registered for each period and customer. Values can be entered automatically. In addition, a numerical value is entered in the input column of "Order Quantity" via a numeric keypad or the like. If values are set in the input fields for "product name" or "product code" and "order quantity", the "order amount" can be calculated from the order unit price and order quantity. Calculation results, that is, multiplication values of order unit price and order quantity can also be automatically entered in the fields. "Lot number" is an input field used for inventory allocation, and will be described later.

In this way, a new entry corresponding to the customer information, the scheduled date information and the ordered product information input to the order entry screen 200 is added to the order information 13A stored in the storage unit 13. FIG. For example, the order reception information receiving unit 15A assigns an order slip number according to a predetermined rule, and associates the order slip number with a new entry corresponding to the customer information, the scheduled date information, and the ordered product information in the order information 13A. to add. At this time, of the customer information, the scheduled date information, and the ordered product information, the received order information receiving unit 15A adds an entry regarding the customer information and the scheduled date information to the received order information 13A1, and adds an entry regarding the ordered product information to the received order information 13A1. to add.

For example, when the customer information, the scheduled date information, and the ordered product information shown in FIG. 2 are input, the received order information receiving unit 15A assigns "JU00001" as an example of the order slip number.

[Order information 13A1]
After that, the order reception information reception unit 15A adds an entry corresponding to the customer information and the scheduled date information inputted on the order entry screen 200 shown in FIG. 2 to the order reception information 13A1. As a result, the received order information 13A1 is updated to the state shown in FIG. FIG. 3 is a diagram showing an example of order information 13A1. That is, the received order information receiving unit 15A sets the input value "2018/10/1" in the text box 220, the input value "C0001" in the text box 230, and the input value "2018/ 10/2", the input value "2018/10/3" of the text box 240B, and the input value "2018/10/3" of the text box 240C are associated with each other in the received order information 13A1. As a result, as shown in FIG. 3, the entry of the order slip number "JU00001", which is the first from the top, is added to the order information 13A1.

[Order information 13A2]
Further, the order information receiving unit 15A adds an entry of order item information corresponding to each line of the table 250 of the order input screen 200 shown in FIG. 2 to the order information 13A2. As a result, the received order information 13A2 is updated to the state shown in FIG. FIG. 4 is a diagram showing an example of the received order information 13A2. For example, in the example of the first row of the table 250, the order reception information receiving unit 15A sets the order slip number "JU00001", the value "30001" in the product code input field, and the value "50" in the order quantity input field. and the value "5,000" in the input field for the order amount are associated with each other in the order information 13A2. As a result, the first entry from the top is added to the order information 13A2 as shown in FIG. Further, in the example of the second row of the table 250, the order receipt information reception unit 15A adds the order slip number "JU00001" to the value "30002" in the product code input field and the value "40" in the order quantity input field. and the value "4,400" in the input field of the order price are generated in the order information 13A2. As a result, the second entry from the top is added to the order information 13A2 as shown in FIG. Further, in the example of the third row of the table 250, the order receipt information receiving unit 15A adds the order slip number "JU00001", the value "30003" in the input field for the product code, and the value "10" in the input field for the number of orders received. and the value "1,200" in the input field of the order price are generated in the order information 13A2. As a result, the third entry from the top is added to the order information 13A2 as shown in FIG.

The lot extraction unit 15B is a processing unit that extracts a lot that meets the allocation conditions from the lots of the ordered product.

By way of example only, the lot extraction unit 15B executes lot extraction that meets the allocation conditions when a selection of a product for inventory allocation is received from among the products included in the table 250 of the order entry screen 200 . For example, when lot button 260A is operated while a row displayed in table 250 of order input screen 200 is selected, lot extraction unit 15B selects the product corresponding to the selected row as the product for which inventory allocation is to be performed. to start extracting lots that meet the allocation conditions.

More specifically, the lot extraction unit 15B acquires the customer code corresponding to the entry registered via the order entry screen 200 from the order information 13A1 stored in the storage unit 13 . Furthermore, the lot extraction unit 15B acquires the allocation conditions corresponding to the previously acquired customer code from among the allocation conditions included in the allocation condition information 13B stored in the storage unit 13 . Further, the lot extraction unit 15B acquires the product code corresponding to the row currently selected in the table 250 of the order entry screen 200 as the product for inventory allocation. After that, the lot extraction unit 15B acquires a group of lot information corresponding to the previously acquired product code from among the lot information 13C stored in the storage unit 13 .

Here, an example of the allocation condition information 13B and the lot information 13C is given.

[Allocation condition information 13B]
FIG. 5 is a diagram showing an example of the allocation condition information 13B. As shown in FIG. 5, the allocation condition information 13B can employ data in which lot conditions, factory line conditions, shipment date conditions, delivery date conditions, and acceptance inspection date conditions are associated with each customer code.

The "lot condition" referred to here refers to a condition for specifying a lot. For example, in the "lot condition", types of conditions such as "none", "same lot", "multiple lots", and "same lot as product shipped in the same month" are set. Of these, "none" refers to an unconditional no designation of lot. If "none" is set for the lot condition, it is allowed to allocate inventory for any lot number. In addition, "same lot" refers to a condition for unifying the lot numbers of the inventory to be allocated to orders with the same lot number. When "same lot" is set, mixing multiple lot numbers is prohibited. In addition, "multiple lots" refers to a condition in which multiple lot numbers are included in the inventory lot numbers to be assigned to the order. If "multiple lots" is set, conditions containing only a single lot number are prohibited. In addition, "the same lot as the product shipped in the same month" refers to the condition for allocating inventory with the same lot number as the product shipped at the time of the previous order if the previous order history is within the same month.

In addition, "factory line conditions" refer to conditions that designate a factory line. For example, in the "factory line condition", types of conditions such as "none", "factory + line" and "same factory" are set. Of these, "none" refers to an unconditional no designation of a factory line. If "none" is set for the factory line condition, then any factory and any line inventory is allowed to be reserved. Also, "factory + line" refers to a condition specifying a factory and a line. By way of example only, if "Factory A's first line" is set as the factory line condition, it is prohibited to allocate inventory for products manufactured on lines other than the first line of Factory A. In addition, "same factory" refers to the condition that the inventory to be allocated for the order is unified to those manufactured in the same factory. When "same factory" is set as the factory line condition, it is prohibited to mix inventory of products manufactured in a plurality of factories.

In addition, "shipment date condition", "delivery date condition" and "acceptance date condition" refer to conditions specifying the date of shipment, the date of delivery, or the date of acceptance inspection. For example, for the "shipping date condition", "delivery date condition", and "acceptance inspection date condition", the format is "from the date of manufacture to N (natural number) days". can be set as Needless to say, it is also possible to set an unconditional "none" that does not specify the shipping date, the delivery date, or the inspection date.

[Lot information 13C]
FIG. 6 is a diagram showing an example of lot information 13C. As shown in FIG. 6, the lot information 13C employs data in which items such as product code, lot number, stock quantity, allocation quantity, manufacturing plant, manufacturing line, manufacturing date and expiration date are associated.

The "lot number" referred to here indicates an example of identification information for identifying a lot. As described above, the same lot number is assigned to products manufactured on the same factory line on the same day, and smaller numbers are assigned to products manufactured earlier, even among the same products. As just one example, the "lot number" is assigned a number in which the identifier of the factory and the line is embedded. For example, the letter "A" in the third last digit indicates the factory name, and the numbers in the second and first digits indicate the line number. If the lot number is "A111A01", it means that the product is manufactured on the first line of the A factory.

In addition, "the number of stocks" indicates the number of stocks. Here, as an example, the number of pieces is described, but the number of packing units such as cardboard boxes and pallets may be used. In addition, the "number of allocations" refers to the number of stocks allocated for the order. "Manufacturing factory" refers to the factory where the goods are manufactured. Also, the “manufacturing line” refers to the line where the product is manufactured. Also, the manufacturing date refers to the date when the product was manufactured. Furthermore, the term "expiration date" refers to the expiration date of the product, and corresponds to, for example, the expiration date or best-before date.

Returning to the explanation of lot extraction, after the lot information group corresponding to the product code is acquired, the lot extraction unit 15B extracts the factory line conditions, shipping date conditions, delivery date conditions, and acceptance inspection date conditions for each of the acquired lot information. Perform a satisfaction check.

For example, the lot extraction unit 15B determines whether or not the lot information satisfies the factory line condition among the allocation conditions corresponding to the customer code. At this time, if the factory line condition is satisfied, the lot extraction unit 15B further determines whether or not the lot information satisfies the shipping date condition among the allocation conditions corresponding to the customer code. Then, when the shipping date condition is satisfied, the lot extraction unit 15B further determines whether or not the lot information satisfies the delivery date condition among the allocation conditions corresponding to the customer code. At this time, if the delivery date condition is satisfied, the lot extraction unit 15B further determines whether or not the lot information satisfies the acceptance inspection date condition among the allocation conditions corresponding to the customer code. If the acceptance inspection date condition is also satisfied, the lot extracting unit 15B determines that the lot meets the allocation condition. On the other hand, if any one of the factory line condition, the shipping date condition, the delivery date condition, or the acceptance inspection date condition is not satisfied, the lot extraction unit 15B determines that the lot does not meet the allocation condition. Hereinafter, a lot that meets the allocation conditions may be referred to as an "applicable lot," while a lot that does not meet the allocation conditions may be referred to as a "non-suitable lot."

Such factory line conditions, shipping date conditions, delivery date conditions, and acceptance date conditions are checked for each lot information. After that, when all the lot information is checked, the lot extraction unit 15B determines whether or not lot conditions are set, that is, whether or not the lot conditions are other than "none". At this time, if lot conditions are set, the lot extraction unit 15B further extracts lot information that satisfies the lot conditions from the lot information of the adaptive lot. After that, the lot extraction unit 15B sorts the extracted lot information in ascending order of expiration date, and causes the client terminal 50 to display a list of the sorted lot information. If the lot conditions are not set, the process of extracting lot information that satisfies the lot conditions is naturally skipped.

[Specific example of lot extraction]
Here, lot extraction will be described with a specific example. As an example only, the scene where the operation of the lot button 260A is accepted while the first row of the table 250 of the order entry screen 200 shown in FIG. 2 is selected will be taken as an example.

In this case, the customer code "C0001" corresponding to the entry registered via the order entry screen 200, ie, the entry on the first line, of the order entry information 13A1 shown in FIG. 3 is obtained. Further, among the allocation conditions included in the allocation condition information 13B shown in FIG. 5, the allocation condition corresponding to the previously acquired customer code "C0001", that is, the first line record is acquired. In other words, lot condition "same lot", factory line condition "A factory 1st line", shipping date condition "up to 7 days from manufacturing date", delivery date condition "up to 10 days from manufacturing date" and acceptance date condition "manufacturing date" to the 13th" is obtained as the allocation condition for the customer code "C0001". Furthermore, the product code “30001” corresponding to the first row currently selected in the table 250 of the order entry screen 200 is acquired.

Then, among the lot information 13C shown in FIG. 6, five pieces of lot information corresponding to the previously acquired product code "30001" are acquired. FIG. 7 is a diagram showing an example of lot information extraction transition. For convenience of explanation, FIG. 7 shows how checks are executed in parallel between lot information for each factory line condition, shipping date condition, delivery date condition, and acceptance inspection date condition. As shown in FIG. 7, among the lot information 13C shown in FIG. 6, five pieces of lot information corresponding to the previously acquired product code "30001" are acquired (step S1). The following description will be given while identifying five pieces of lot information corresponding to the product code "30001" by the lot number of each piece of lot information.

(1) Factory line condition check line is checked. That is, lot information manufactured in the first line of factory A is extracted according to the factory line condition "first line of factory A". Here, the lot information of the lot number "A115B01" out of the five lot information is the product with the product code "30001", but it is a lot manufactured at the B factory, not the A factory, so it is an unsuitable lot. be judged. On the other hand, the four lot information corresponding to the lot numbers "A111A01", "A112A01", "A113A01" and "A114A01" satisfy the factory line condition "A factory first line". A check is made.

(2) Checking the shipping date condition A check is made. Here, the production dates of lot numbers "A111A01", "A112A01", "A113A01" and "A114A01" are "2018/9/21", "2018/9/27", "2018/9/28" and "2018/9/28". On the other hand, the scheduled shipping date specified in the order is "2018/10/2" as shown in the order entry screen 200 shown in FIG. Of these, the manufacturing date “2018/9/21” of lot number “A111A01” is 11 days before the scheduled shipping date “2018/10/2”, and it exceeds the specified condition of 7 days from the manufacturing date, so it is not valid. It is judged as an adaptive lot. On the other hand, the scheduled shipping date is included within seven days of the manufacturing date of the three pieces of lot information corresponding to lot numbers "A112A01", "A113A01" and "A114A01". In this way, the three lot information corresponding to the lot numbers "A112A01", "A113A01" and "A114A01" satisfy the shipping date condition "within 7 days from the manufacturing date", so the next check is performed.

(3) Checking the delivery date condition Next, the delivery date condition "within 10 days from the manufacturing date" is checked for each of the three lot information corresponding to the lot numbers "A112A01", "A113A01" and "A114A01". . Here, the manufacturing dates of lot numbers "A112A01", "A113A01" and "A114A01" are "2018/9/27", "2018/9/28" and "2018/9/28". On the other hand, the scheduled delivery date specified in the order is "2018/10/3" as shown in the order entry screen 200 shown in FIG. Therefore, the scheduled delivery date is included within 10 days from the manufacturing date of the three pieces of lot information corresponding to lot numbers "A112A01", "A113A01" and "A114A01". In this way, the three pieces of lot information corresponding to the lot numbers "A112A01", "A113A01" and "A114A01" satisfy the delivery date condition "within 10 days from the date of manufacture", so the next check is performed.

(4) Checking acceptance date conditions Next, for each of the three lot information corresponding to lot numbers "A112A01", "A113A01" and "A114A01", the acceptance date condition "13 days from date of manufacture" is checked. . Here, the manufacturing dates of lot numbers "A112A01", "A113A01" and "A114A01" are "2018/9/27", "2018/9/28" and "2018/9/28". On the other hand, the scheduled acceptance inspection date specified in the order is "2018/10/3" as shown in the order entry screen 200 shown in FIG. Therefore, the scheduled acceptance date is included within 13 days from the manufacturing date of the three lot information corresponding to lot numbers "A112A01", "A113A01" and "A114A01". Thus, the three pieces of lot information corresponding to the lot numbers "A112A01", "A113A01" and "A114A01" satisfy the acceptance inspection date condition "13 days from date of manufacture".

As a result, as shown in FIG. 7, lot numbers "A112A01", "A113A01" and "A114A01" are extracted as adaptive lots (step S2).

(5) Lot Condition Check Here, the lot condition "same lot" is set as the allocation condition corresponding to the customer code "C0001". In this way, when "same lot" is set as the lot condition, it is prohibited that a plurality of lot numbers are mixed in the lot number of the inventory to be allocated to the order. Therefore, it is checked whether or not the inventory quantity of the lot number is greater than or equal to the order quantity. For example, as shown in the order information 13A2, the number of orders for product code "30001" with order slip number "JU00001" is "50". On the other hand, the inventory quantity of lot number "A112A01" is "40", the inventory quantity of lot number "A113A01" is "60", and the inventory quantity of lot number "A114A01" is "50". Of these, the inventory quantity "40" of lot number "A112A01" is less than the order quantity "50", so it is difficult to allocate lot number "A112A01" alone to the order. On the other hand, the inventory quantity of lot number "A113A01" and lot number "A114A01" is greater than or equal to the order quantity "50". .

From this, two pieces of lot information corresponding to lot number "A113A01" and lot number "A114A01" are extracted (step S3). After that, a list of two lot information corresponding to lot number "A113A01" and lot number "A114A01" is displayed on the client terminal 50 as a lot inventory screen shown in FIG. Here, an example in which a lot satisfying the lot conditions exists is given, but if there is no lot satisfying the lot conditions, an error message such as "No lot available for allocation" can be displayed.

FIG. 8 is a diagram showing an example of the lot inventory screen. As shown in FIG. 8, lot inventory screen 300 displays table 310 for accepting inventory allocation. Table 310 contains two rows for lot number "A113A01" and lot number "A114A01". Furthermore, in the row direction of the table 310, "Lot number", "Expiration date", "Stock quantity" and "Allocation quantity" are displayed in order from the left. columns are placed. In the table 310, it is possible to receive an input of the number of inventory allocations for each row via the "number of allocations" input field in each row.

In this example, "same lot" is set as an example of lot conditions. If only one piece of information is extracted, an error message such as "Not enough lots available for allocation" can be displayed. In addition, if "same lot as product shipped in the same month" is set, refer to the shipping history associated with the product code of the product shipped for each customer code and its lot number, and the history of previous orders will be displayed. If it exists within the same month, extract only the lot information with the same lot number as the lot number of the product shipped at the time of the previous order, and if the extraction of the lot information fails, an error message such as Lot does not exist." can be displayed. In addition, the lot number existing in the shipping history of the customer code for which "the same lot as the product shipped in the same month" is set can be prohibited from allocating inventory to the orders of other customer codes.

Returning to the description of FIG. 1, the inventory allocation reception unit 15C is a processing unit that receives inventory allocation.

As an example only, the inventory allocation receiving unit 15C receives lots and allocation numbers for inventory allocation on the list of lot information extracted by the lot extracting unit 15B. For example, the inventory allocation accepting unit 15C accepts selection of a lot for inventory allocation by accepting selection of a row from the table 310 of the lot inventory screen 300 . Further, the inventory allocation receiving unit 15C receives input of the allocation number via the "allocation number" input field in the row currently selected in the table 310 of the lot inventory screen 300. FIG.

After the number of allocations is entered in this way, by accepting the operation of the registration button 320A, the acceptance of the inventory allocation for the selected product among the products included in the table 250 of the order entry screen 200 is completed. If the cancel button 320B is operated before the registration button 320A is operated, the allocation number is cancelled. Also, if the close button 320C is operated before the registration button 320A is operated, the window of the lot inventory screen 300 is closed.

Here, when the reception of the inventory allocation is completed, the inventory allocation reception unit 15C adds the allocation number of the lot number for which the inventory allocation was performed to the allocation number of the lot information 13C stored in the storage unit 13, and adds the "allocation number" of the table 310 to the lot information 13C stored in the storage unit 13. Add the number of allocations entered through the input field of . For example, when the lot number "A113A01" on the first line of the table 310 of the lot inventory screen 300 is selected and "50" is further input in the input field of the "number of allocations" on the first line, the register button is clicked. 320A is operated, of the lot information 13C shown in FIG. By adding "50", the allocation number of the record corresponding to the lot number "A113A01" in the lot information 13C is updated to "50 (=0+50)".

Further, the inventory allocation receiving unit 15C creates a new entry regarding the inventory allocation in the allocation information 13D stored in the storage unit 13. FIG.

[Allocation information 13D]
FIG. 9 is a diagram showing an example of allocation information 13D. FIG. 9 shows a state in which the lot number "A113A01" on the first line of the table 310 of the lot inventory screen 300 is selected and "50" is further input in the input field of the "number of allocations" on the first line. The entry of the allocation information 13D generated when the registration button 320A is operated in is shown. As shown in FIG. 9, the allocation information 13D employs data in which an order slip number, a lot number, and an allocation quantity are associated with each other. In the example of the record on the first line of the allocation information 13D shown in FIG. 9, it means that 50 pieces of the inventory of lot number "A113A01" have been allocated for the order received with the order slip number "JU00001".

Thereafter, selection of a lot for inventory allocation and input of the number of allocations are repeatedly executed until inventory allocation is performed for all the products included in the table 250 of the order entry screen 200 .

The inventory allocation determination unit 15D is a processing unit that determines whether or not the inventory allocation received by the inventory allocation reception unit 15C satisfies allocation conditions.

As an example only, when the registration button 260B is operated in a state in which inventory allocation has been performed for all the products included in the table 250 of the order input screen 200, the inventory allocation determination unit 15D Check whether the inventory allocation satisfies the allocation conditions for each product. If the cancel button 260C is operated before the registration button 260B of the order entry screen 200 is operated, the input values in the text boxes 210, 220, 230 and 240A to 240C and the input values in the table 250 are canceled. be If the end button 260D is operated before the registration button 260B of the order entry screen 200 is operated, order entry and inventory allocation are terminated.

More specifically, the inventory allocation determination unit 15D acquires the customer code corresponding to the entry registered via the order input screen 200 from the order information 13A1 stored in the storage unit 13. FIG. Further, the inventory allocation determination unit 15D acquires the allocation condition corresponding to the previously acquired customer code from among the allocation conditions included in the allocation condition information 13B stored in the storage unit 13 . Further, the inventory allocation determining unit 15D determines the allocation number of entries for which inventory allocation has been performed in the lot information 13C stored in the storage unit 13, and the number of entries newly allocated in the allocation information 13D stored in the storage unit 13 by the inventory allocation. Acquire the number of allocations of generated entries.

After that, the inventory allocation determining unit 15D determines whether or not the number of allocations has been input for multiple lots. At this time, if the allocation quantity is input for multiple lots, the inventory allocation determination unit 15D further determines whether or not "same lot" is set as the lot condition among the allocation conditions. Then, when "same lot" is set in the lot condition, the inventory allocation determination unit 15D determines that inventory allocation is not possible.

Such checks are performed because human errors such as: For example, the table 310 of the lot inventory screen 300 shown in FIG. 8 includes two lots, lot number "A113A01" and lot number "A114A01." This is not to force the user to enter the number of allocations for two lots, but to show that two lots are available as options for inventory allocation. However, if the customer with the customer code "C0001" does not know or forgets that "same lot" is set in the lot conditions, the two lots are displayed in the table 310, thereby A human error may occur, such as entering the number of allocations in the From the aspect of suppressing such human errors, the above checks are performed again after receiving the inventory allocation.

In addition, if the allocation quantity is not input for multiple lots, or if the lot conditions are not set to "same lot" even if the allocation quantity is input for multiple lots, the inventory allocation determination unit 15D Check whether or not the number of allocations is equal to or less than the number of stocks for each lot. At this time, if the allocation quantity of each lot is not equal to or less than the inventory quantity of each lot, the inventory allocation determination unit 15D determines that inventory allocation is impossible. On the other hand, when the allocation quantity of each lot is equal to or less than the inventory quantity of each lot, the inventory allocation determination unit 15D determines that inventory allocation is possible.

[Example of inventory allocation check]
As an example only, an example of checking inventory allocation will be described by taking as an example a scene in which the registration button 260B is operated in a state in which the following inventory allocation is performed in the table 250 of the order entry screen 200. At this time, the check of the inventory allocation for the product code "30001" in the first row of the table 250 will be extracted and explained. Assume that the registration button 320A is operated while the lot number "A113A01" on the line is selected and "50" is entered in the "number of allocations" input field on the first line.

In this case, the customer code "C0001" corresponding to the entry registered via the order entry screen 200, ie, the entry on the first line, of the order entry information 13A1 shown in FIG. 3 is acquired. Further, among the allocation conditions included in the allocation condition information 13B shown in FIG. 5, the allocation condition corresponding to the previously acquired customer code "C0001", that is, the first line record is acquired. In other words, lot condition "same lot", factory line condition "A factory 1st line", shipping date condition "up to 7 days from manufacturing date", delivery date condition "up to 10 days from manufacturing date" and acceptance date condition "manufacturing date" to the 13th" is obtained as the allocation condition for the customer code "C0001". Furthermore, among the lot information 13C, the number of allocations of the entry of the lot number "A113A01" updated by the inventory allocation is "50", and the allocation number of the entries newly generated by the inventory allocation among the allocation information 13D. "50" is obtained.

After that, it is checked whether or not the number of allocations has been entered for multiple lots. Here, only the entry of lot number "A113A01" exists in the lot information for which inventory allocation has been performed for the order received for the product corresponding to product code "30001" among the orders received for order slip number "JU00001". Therefore, it is determined that the number of allocations has not been input for multiple lots. In this case, it is further checked whether the allocation quantity of each lot is equal to or less than the inventory quantity of each lot. For example, lot number "A113A01" has an inventory quantity of "60" and an allocation quantity of "50". In this way, since the number of allocations is equal to or less than the number of stocks, it is determined that the lot number "A113A01" can be allocated for the order for the product corresponding to the product code "30001" of the order slip number "JU00001". In this example, the number of allocations is less than the number of stocks, but if the number of allocations exceeds the number of stocks, an error message such as "The number of input allocations exceeds the number of stocks" can be displayed. .

[Another example of inventory allocation check]
As another example, the case where the registration button 260B is operated with the inventory allocation shown in the table 250 of the order entry screen 201 shown in FIG. FIG. 10 is a diagram showing another example of the order entry screen. Taking the example of the order entry screen 201 shown in FIG. An example is shown in which inventory allocation is performed to allocate 30 units of inventory numbered "B222A01".

In this case, the customer code "C0002" corresponding to the entry registered via the order entry screen 201, ie, the entry on the second line, of the order entry information 13A1 shown in FIG. 3 is obtained. Further, among the allocation conditions included in the allocation condition information 13B shown in FIG. 5, the allocation condition corresponding to the previously acquired customer code "C0002", that is, the second line record is acquired. In other words, the lot condition "none", the factory line condition "same factory", the shipping date condition "none", the delivery date condition "none", and the acceptance date condition "within 7 days from the manufacturing date" are the allocation conditions for the customer code "C0002". is obtained as Further, among the lot information 13C, the allocation number "10" of the entry of the lot number "B221A01" and the allocation number "30" of the entry of the lot number "B222A01" updated by the inventory allocation are obtained. be.

After that, it is checked whether or not the number of allocations has been entered for multiple lots. Here, the lot information for which inventory allocation was performed for the product corresponding to the product code "30002" among the orders received with the sales order slip number "JU00002" consists of two entries: lot number "B221A01" and lot number "B222A01". exists. Therefore, it is determined that the number of allocations has been input for multiple lots. In this case, it is checked whether or not "same lot" is set in the lot conditions. At this time, "none" is set as the lot condition for customer code "C0002", and "same lot" is not set. For this reason, it is further checked whether or not the allocation quantity of each lot is equal to or less than the inventory quantity of each lot. For example, lot number "B221A01" has an inventory quantity of "50" and an allocation quantity of "10." In addition, the inventory quantity of the lot number "B222A01" is "50" and the allocation quantity is "30". In this way, since the number of allocations is less than the number of stocks in any lot, the lot number "B221A01" and the lot number "B222A01" for the order for the product corresponding to the product code "30002" of the order slip number "JU00002" It is determined that inventory allocation is possible. In this example, "same lot" is not set in the lot conditions, but if "same lot" is set in the lot conditions, an error message such as "Multiple lots have been allocated , etc., can be displayed.

Also here, if "same lot as the same month shipment product" is set, refer to the shipping history associated with the product code of the product shipped for each customer code and its lot number, and If the history exists within the same month, determine whether the lot number for which inventory allocation was made is the same as the lot number of the product shipped at the time of the preceding order, and if the two are different, An error message such as "A lot number that is different from the lot number that has been shipped this month" can be displayed.

[Process flow]
FIG. 11 is a flowchart illustrating the procedure of order entry processing according to the first embodiment. This process is started only as an example when an operation of pressing an icon such as "input order" on the menu screen displayed on the client terminal 50 is received.

As shown in FIG. 11, the order information reception unit 15A receives input of order information such as customer information, scheduled date information, and order product information through an input operation on an order entry screen displayed on the client terminal 50 ( step S101, step S102 and step S103).

Subsequently, when a selection of a product for which inventory allocation is to be made is received from among the products entered as the ordered product information on the order input screen (step S104), the lot extraction unit 15B selects a lot of the ordered product that meets the allocation conditions. A "lot extraction process" for extracting a lot to be processed is executed (step S105).

FIG. 12 is a flowchart illustrating the procedure of lot extraction processing according to the first embodiment. This process corresponds to the process of step S105 shown in FIG. As shown in FIG. 12, the lot extraction unit 15B acquires a customer code corresponding to an entry registered via the order input screen from the order information 13A1 stored in the storage unit 13 (step S301).

Further, the lot extraction unit 15B acquires the allocation condition corresponding to the customer code acquired in step S301 from among the allocation conditions included in the allocation condition information 13B stored in the storage unit 13 (step S302).

Further, the lot extraction unit 15B acquires the product code of the product selected as the product for inventory allocation in step S104 (step S303). After that, the lot extraction unit 15B acquires a group of lot information corresponding to the product code acquired in step S303 from among the lot information 13C stored in the storage unit 13 (step S304).

After that, the lot extraction unit 15B executes a "lot determination process" for determining whether or not the factory line conditions, the shipping date conditions, the delivery date conditions, and the acceptance inspection date conditions are met for each lot information acquired in step S304. (Step S305).

FIG. 13 is a flowchart illustrating the procedure of lot determination processing according to the first embodiment. This process corresponds to the process of step S305 shown in FIG. As shown in FIG. 13, when the factory line conditions are set in the allocation conditions, that is, when the factory line conditions are other than "none" (step S501 Yes), the lot extraction unit 15B determines that the lot information corresponds to the customer code. It is determined whether or not the factory line conditions among the allocation conditions are satisfied (step S502). If the factory line conditions are not set in the allocation conditions (step S501 No), the process of step S502 is skipped and the process proceeds to step S503.

At this time, if the factory line condition is satisfied (step S502 Yes), the lot extraction unit 15B determines whether or not the shipment date condition is set in the allocation condition, that is, whether the shipment date condition is other than "none" ( step S503). Then, if the shipment date condition is set in the allocation conditions (step S503 Yes), the lot extracting unit 15B further determines whether or not the lot information satisfies the shipment date condition (step S504). If the shipping date condition is not set in the allocation conditions (No at step S503), the process at step S504 is skipped and the process proceeds to step S505.

Subsequently, if the shipping date condition is satisfied (step S504 Yes), the lot extraction unit 15B determines whether the delivery date condition is set in the allocation condition, that is, whether the delivery date condition is other than "none" ( step S505). Then, if the delivery date condition is set in the allocation condition (step S505 Yes), the lot extraction unit 15B further determines whether or not the lot information satisfies the delivery date condition (step S506). If the delivery date condition is not set in the allocation condition (No at step S505), the process of step S506 is skipped and the process proceeds to step S507.

Then, if the delivery date condition is satisfied (step S506 Yes), the lot extraction unit 15B determines whether or not the acceptance inspection date condition is set in the allocation conditions, that is, whether the acceptance inspection date condition is other than "none" (step S506 Yes). S507). If the allocation condition includes the acceptance inspection date condition (Yes at step S507), the lot extraction unit 15B further determines whether or not the lot information satisfies the acceptance inspection date condition (step S508). If the acceptance inspection date condition is not set in the allocation conditions (step S507 No), the process of step S508 is skipped and the process proceeds to step S509.

Here, if the inspection date condition is also satisfied (step S508 Yes), the lot extracting unit 15B determines that the lot is an adaptive lot (step S509), and terminates the process. On the other hand, if any one of the factory line condition, shipping date condition, delivery date condition, or acceptance date condition is not satisfied (No in step S502, No in step S504, No in step S506, or No in step S508), the lot extracting unit 15B regards the lot as an unsuitable lot. A decision is made (step S510), and the process ends.

Returning to the description of FIG. 12, the above lot determination process is performed (step S305) until the above lot determination process is performed for all lot information (step S306 No). After that, when the above-described lot determination processing has been executed for all lot information (step S306 Yes), the lot extracting unit 15B determines whether or not the lot conditions are set, that is, whether the lot conditions are other than "none". (step S307).

At this time, if lot conditions are set (step S307 Yes), the lot extraction unit 15B further extracts lot information that satisfies the lot conditions from the lot information of the adaptive lot (step S308). After that, the lot extracting unit 15B sorts the extracted lot information in ascending order of expiration date (step S309), displays a list of the sorted lot information on the client terminal 50 (step S310), and executes the process. finish.

Note that if the lot conditions are not set (step S307 No), the process of step S308 is skipped. In this case, the lot information of the adaptive lot is sorted in ascending order of expiration date (step S309), the list of the sorted lot information is displayed on the client terminal 50 (step S310), and the process ends.

Returning to the description of FIG. 11, the inventory allocation receiving unit 15C receives lots and allocation numbers for inventory allocation on the list of lot information extracted as a result of the lot extraction process in step S105 (steps S106 and S107).

Then, the processes from step S104 to step S107 are repeatedly executed until inventory allocation is performed for all the products included in the order entry screen (step S108 No).

After that, when inventory allocation has been performed for all the products included in the order entry screen (step S108 Yes), the inventory allocation determination unit 15D determines whether the inventory allocation accepted on the list of lot information satisfies the allocation conditions. Execution of the "inventory allocation determination process" to determine whether or not (step S109), and the process ends.

FIG. 14 is a flowchart illustrating the procedure of inventory allocation determination processing according to the first embodiment. This process corresponds to the process of step S109 shown in FIG. As shown in FIG. 14, the inventory allocation determining unit 15D acquires the customer code corresponding to the entry registered via the order entry screen from among the order information 13A1 stored in the storage unit 13 (step S701). .

Further, the inventory allocation determination unit 15D acquires the allocation condition corresponding to the customer code acquired in step S701 from among the allocation conditions included in the allocation condition information 13B stored in the storage unit 13 (step S702).

Further, the inventory allocation determining unit 15D determines the allocation number of entries for which inventory allocation has been performed in the lot information 13C stored in the storage unit 13, and the number of entries newly allocated in the allocation information 13D stored in the storage unit 13 by the inventory allocation. The number of allocations of generated entries is obtained (step S703).

After that, the inventory allocation determining unit 15D determines whether or not the number of allocations has been input for multiple lots (step S704). At this time, if the allocation quantity is input for multiple lots (step S704 Yes), the inventory allocation determination unit 15D further determines whether or not "same lot" is set as the lot condition among the allocation conditions (step S705).

Then, when "same lot" is set in the lot condition (Yes at step S705), the inventory allocation determination unit 15D determines that inventory allocation is not possible (step S706), and ends the process.

Also, if the allocation quantity is not input for multiple lots (step S704 No), or if the lot conditions are not set to "same lot" even if the allocation quantity is input for multiple lots (step S704 Yes and step S705 No) , the inventory allocation determining unit 15D checks whether or not the allocation quantity of each lot is equal to or less than the inventory quantity of each lot (step S707).

Here, if the allocation quantity of each lot is not equal to or less than the inventory quantity of each lot (step S707 No), the inventory allocation determination unit 15D determines that inventory allocation is impossible (step S706), and terminates the process. On the other hand, if the allocation quantity of each lot is equal to or less than the inventory quantity of each lot (Yes at step S707), the inventory allocation determining unit 15D determines that inventory allocation is possible (step S708), and ends the process.

[One aspect of the effect]
As described above, the server device 10 according to the present embodiment enables setting of allocation conditions for each lot and each customer. When an order is entered, a lot that can be allocated is automatically extracted according to the allocation conditions, and inventory allocation can be performed for each lot. In addition, the allocation conditions are checked when entering the number of orders received for each lot. Therefore, according to the server apparatus 10 of this embodiment, it is possible to realize inventory allocation based on lots.

Although embodiments of the disclosed apparatus have been described so far, the present invention may be embodied in various forms other than the embodiments described above. Therefore, other embodiments included in the present invention will be described below.

Distributed and integrated
Also, each component of each illustrated device may not necessarily be physically configured as illustrated. In other words, the specific form of distribution and integration of each device is not limited to the one shown in the figure, and all or part of them can be functionally or physically distributed and integrated in arbitrary units according to various loads and usage conditions. Can be integrated and configured. For example, the order reception information reception unit 15A, the lot extraction unit 15B, the inventory allocation reception unit 15C, or the inventory allocation determination unit 15D may be connected as external devices of the server device 10 via a network. Further, separate devices each have the received order information receiving unit 15A, the lot extracting unit 15B, the inventory allocation receiving unit 15C, or the inventory allocation determining unit 15D, and are connected to a network and cooperate with each other to realize the functions of the server device 10 described above. may be realized.

[Order entry program]
Moreover, various processes described in the above embodiments can be realized by executing a prepared program on a computer such as a personal computer or a work station. Therefore, an example of a computer that executes an order entry program having functions similar to those of the above embodiment will be described below with reference to FIG.

FIG. 15 is a diagram showing a hardware configuration example of a computer. As shown in FIG. 15, the computer 100 has an operation section 110a, a speaker 110b, a camera 110c, a display 120, and a communication section . Furthermore, this computer 100 has a CPU 150 , a ROM 160 , an HDD 170 and a RAM 180 . Each part of these 110 to 180 is connected via a bus 140 .

As shown in FIG. 15, the HDD 170 has an order entry input unit that performs the same functions as the order information reception unit 15A, the lot extraction unit 15B, the inventory allocation reception unit 15C, and the inventory allocation determination unit 15D shown in the first embodiment. A program 170a is stored. This order input program 170a may be integrated or separated like the constituent elements of the order reception information reception unit 15A, lot extraction unit 15B, inventory allocation reception unit 15C, or inventory allocation determination unit 15D shown in FIG. That is, the HDD 170 does not necessarily store all the data shown in the first embodiment, and the HDD 170 only needs to store data used for processing.

Under such an environment, the CPU 150 reads the order entry program 170 a from the HDD 170 and loads it into the RAM 180 . As a result, the order entry program 170a functions as an order entry process 180a as shown in FIG. The order entry process 180a deploys various data read from the HDD 170 in an area assigned to the order entry process 180a among the storage areas of the RAM 180, and executes various processes using the deployed various data. For example, examples of processing executed by the order entry process 180a include the processing shown in FIGS. 11 to 14. FIG. Note that the CPU 150 does not necessarily have to operate all the processing units described in the first embodiment, as long as the processing units corresponding to the processes to be executed are virtually realized.

Note that the order entry input program 170a described above does not necessarily have to be stored in the HDD 170 or the ROM 160 from the beginning. For example, the order input program 170a is stored in a “portable physical medium” such as a flexible disk inserted into the computer 100, so-called FD, CD-ROM, DVD disk, magneto-optical disk, IC card, or the like. The computer 100 may acquire and execute the order entry program 170a from these portable physical media. Alternatively, the order entry program 170a may be stored in another computer or server device connected to the computer 100 via a public line, the Internet, a LAN, a WAN, etc., and the computer 100 may obtain the order entry program 170a therefrom. You can also run

1 sales management system 10 server device 11 communication interface 13 storage unit 13A order information 13B allocation condition information 13C lot information 13D allocation information 15 control unit 15A order information reception unit 15B lot extraction unit 15C inventory allocation reception unit 15D inventory allocation determination unit 50 client terminal

Claims (8)

an order information reception unit that receives input of a customer code, a product code, and the number of orders received;
Of the lot numbers corresponding to the product code input to the order information receiving unit, the lot number for which the manufacturing information corresponding to the lot number corresponds to the allocation conditions set for the customer code input to the order information receiving unit. a lot extraction unit for extracting
an inventory allocation receiving unit that receives an input of an allocation quantity to be allocated from the inventory of the lot number extracted by the lot extracting unit to the order quantity input to the order receiving information receiving unit;
An order entry input device characterized by comprising: The apparatus further comprises an inventory allocation determination unit that determines whether or not the allocation quantity input to the inventory allocation receiving unit and the lot number to which the allocation quantity is input correspond to allocation conditions set in the customer code. 2. The order entry input device according to claim 1. The lot extraction unit extracts a lot number corresponding to a manufacturing plant or manufacturing plant line corresponding to the lot number, which is set as the allocation condition in the customer code. 3. An order entry input device according to item 1 or 2. 1. The lot extractor extracts a lot number whose production date corresponding to the lot number corresponds to a deadline for shipment, delivery, or acceptance inspection set as the allocation condition in the customer code. 4. The order input device according to any one of 3. The lot extraction unit extracts the lot number included in the shipping history corresponding to the customer code when the shipment of the product with the same lot number as the customer code is set as the allocation condition. 5. An order entry input device according to any one of claims 1 to 4. The inventory allocation determining unit determines whether or not the lot number for which the allocation quantity is input to the inventory allocation receiving unit is the same as the lot number included in the shipping history corresponding to the customer code. 3. The order entry input device according to claim 2. Accepts input of customer code, product code and number of orders,
extracting, from among the lot numbers corresponding to the product code for which the input was received, the lot number for which the manufacturing information corresponding to the lot number corresponds to the allocation condition set for the customer code for which the input was received;
Receiving the input of the allocation quantity to be allocated from the inventory of the lot number extracted from the received order quantity for which the input was received;
An order entry method characterized in that processing is executed by a computer. Accepts input of customer code, product code and number of orders,
extracting, from among the lot numbers corresponding to the product code for which the input was received, the lot number for which the manufacturing information corresponding to the lot number corresponds to the allocation condition set for the customer code for which the input was received;
Receiving the input of the allocation quantity to be allocated from the inventory of the lot number extracted from the received order quantity for which the input was received;
An order entry program characterized by causing a computer to execute processing.

Images