JP7572259B2 - Business support device, business support method, and business support program - Google Patents

Description

The present invention relates to a business support device, a business support method, and a business support program.

Systems for managing product inventory are known. For example, systems that also manage the locations where products are stored are known (see, for example, Patent Document 1).

JP 2005-35760 A

In this case, there may be a need to manage the product's sales destination as well. However, with conventional technology, sales destinations are registered or updated once actual results have been confirmed, making it difficult to grasp the planned inventory for a sales destination before the results are confirmed. For this reason, with conventional technology, it is not possible to grasp the planned inventory for a sales destination before the actual results are confirmed, such as at the product ordering or order receiving stage, which can reduce the efficiency of business operations.

The present invention has been made in consideration of the above problems, and aims to provide a business support device, a business support method, and a business support program that can improve the efficiency of business execution.

In order to solve the above-mentioned problems and achieve the object, the business support device according to the present invention is a business support device equipped with a memory unit and a control unit, the memory unit stores an inventory table in which product information, customer information, and inventory quantity are registered in association with each other, and the control unit is equipped with a receiving means for receiving input of pre-performance information, which is at least one of order information for a product to be ordered, order information for a product to be received, and customer change information for a product to be changed in order to the customer, and the customer information, and a registration means for registering the received pre-performance information and the customer information in an appointment management table in association with each other.

The registration means of the business support device according to the present invention is characterized in that, when receiving input of the order information and the customer information, it associates the order information, which is the pre-performance information, with the customer information and registers them in the order table, which is the schedule management table.

The registration means of the business support device according to the present invention is characterized in that, when receiving the input of the order information and the customer information, it associates the order information, which is the pre-performance information, with the customer information and registers them in the order table, which is the schedule management table.

The registration means of the business support device according to the present invention is characterized in that, when input of the sales destination change information and the sales destination information is accepted, the sales destination change information, which is the pre-performance information, and the sales destination information are associated with each other and registered in the change instruction table, which is the schedule management table.

The receiving means of the business support device according to the present invention further receives input of at least one of actual purchase information of the product, actual sales information of the product, and actual change information of the customer, and the customer information, and the registration means registers the received actual information and the customer information in a performance management table in association with each other.

The business support device according to the present invention is also characterized by having an update means for updating the inventory table based on the received performance information and sales destination information.

The registration means of the business support device according to the present invention is characterized in that, when input of the purchase record information and the customer information is accepted, the purchase record information, which is the record information, is associated with the customer information and registered in the purchase table, which is the record management table; when input of the sales record information and the customer information is accepted, the sales record information, which is the record information, is associated with the customer information and registered in the sales table, which is the record management table; and, when input of the change record information and the customer information is accepted, the change record information, which is the record information, is associated with the customer information and registered in the change table, which is the record management table.

The business support method according to the present invention is a business support method to be executed by an information processing device having a control unit and a storage unit, the storage unit stores an inventory table in which product information, customer information, and inventory quantities are registered in association with each other, and the method includes a step executed by the control unit to accept input of pre-performance information, which is at least one of order information for a product to be ordered, order information for a product to be received, and customer change information for a product to be changed in order to the customer, and the customer information, and a step to register the accepted pre-performance information and the customer information in an appointment management table in association with each other.

The business support program according to the present invention is a business support program to be executed by an information processing device having a control unit and a storage unit, the storage unit stores an inventory table in which product information, customer information, and inventory quantities are registered in association with each other, and the control unit is a contract management program to execute the steps of accepting input of pre-performance information, which is at least one of order information for a product to be ordered, order information for a product to be received, and customer change information for a product to be changed in association with the customer information, and registering the accepted pre-performance information and customer information in a schedule management table.

The present invention has the effect of making it possible to improve the efficiency of business operations.

FIG. 1 is a block diagram showing an example of a configuration of a task support device. FIG. 2A is a schematic diagram showing an example of a data configuration of the inventory table. FIG. 2B is a schematic diagram showing an example of the data configuration of the order point master table. FIG. 3A is a schematic diagram showing an example of the data configuration of the order table. FIG. 3B is a schematic diagram showing an example of a data configuration of the change instruction table. FIG. 3C is a schematic diagram showing an example of a data configuration of the order table. FIG. 4A is a schematic diagram showing an example of a data configuration of a purchase table. FIG. 4B is a schematic diagram showing an example of the data configuration of the change table. FIG. 4C is a schematic diagram showing an example of a data configuration of a sales table. FIG. 5 is a flowchart showing an example of the flow of information processing executed by the task support device according to the present embodiment. FIG. 6 is an explanatory diagram of an example of a flow of a task using the task support device according to the present embodiment. FIG. 7A is a schematic diagram of an example of an order table. FIG. 7B is a schematic diagram of an example of a purchase table. FIG. 7C is a schematic diagram of an example of the inventory table before updating. FIG. 7D is a schematic diagram of an example of the inventory table after updating. FIG. 8A is a schematic diagram of an example of a change instruction table. FIG. 8B is a schematic diagram of an example of the change table. FIG. 8C is a schematic diagram of an example of the inventory table before updating. FIG. 8D is a schematic diagram of an example of the inventory table after updating. FIG. 9A is a schematic diagram of an example of an order table. FIG. 9B is a schematic diagram of an example of a sales table. FIG. 9C is a schematic diagram of an example of the inventory table before updating. FIG. 9D is a schematic diagram of an example of an updated inventory table.

Below, an embodiment of a business support device, a business support method, and a business support program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the present embodiment.

[1. Configuration]
An example of the configuration of a task assistance device 100 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing an example of the configuration of the task assistance device 100.

The business support device 100 is a device that combines and manages multiple contracts. The business support device 100 is a commercially available desktop personal computer. Note that the business support device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

The business support device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit included in the business support device 100 is connected to each other so as to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the business support device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the business support device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). Note that the various data stored in the memory unit 106 may be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The storage unit 106 stores various databases, tables, files, and the like. The storage unit 106 records computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, or the like.

The memory unit 106 stores, for example, an inventory table 106a, an order point master table 106b, a schedule management table 106c, and a performance management table 106d. The schedule management table 106c includes an order table 106e, a change instruction table 106f, and an order table 106g. The performance management table 106d includes a purchase table 106h, a change table 106i, and a sales table 106j.

An example of the data structure of these tables will be described below. Note that in this embodiment, the structures of tables such as inventory table 106a, order point master table 106b, schedule management table 106c, performance management table 106d, order table 106e, change instruction table 106f, order table 106g, purchase table 106h, change table 106i, and sales table 106j are described in a simplified manner. The actual table structures are more complex, but parts that are not directly related to the present invention are shown in a simplified manner. Also, the data format of these tables is not limited to tables. For example, the data format of the tables may be a database or a file.

Figure 2A is a schematic diagram showing an example of the data structure of inventory table 106a.

The inventory table 106a is a table for managing the current inventory status of products. In detail, the inventory table 106a is a table in which product information, product sales destination information, and the number of products in stock are registered in association with each other.

Product information is information that describes a product. For example, product information includes the product name, the product lot, the warehouse where the product is managed, and the like. Note that the information included in product information is not limited to these. In this embodiment, the number of products in stock is shown as "quantity." The "quantity" registered in the inventory table 106a is information that represents the actual number of products in stock.

Sales destination information is information that indicates the sales destination of a product. In this embodiment, for products whose sales destination has been determined, the sales destination information of the sales destination is registered in the inventory table 106a. FIG. 2A shows an example in which "Customer A" is registered as the sales destination information of the sales destination. On the other hand, for products whose sales destination has not been determined, "FREE" is registered as the sales destination information in the inventory table 106a, indicating that the sales destination has not been determined. Note that the information indicating that the sales destination has not been determined is not limited to "FREE".

The inventory table 106a is updated by the processing of the control unit 102, which will be described later in detail. In the following, the seller information may be simply referred to as the seller.

Figure 2B is a schematic diagram showing an example of the data configuration of the order point master table 106b.

The reorder point master table 106b is a master table for managing reorder points. In detail, the reorder point master table 106b registers in association with the warehouse where the product is managed, the customer, the product name, the order quantity, and the safety stock quantity. The order quantity represents the lower limit below which an order must be placed. The safety stock quantity represents the lower limit below which there will be no shortage of stock if there is this number of products.

Figures 3A to 3C are schematic diagrams showing an example of the data configuration of schedule management table 106c. Schedule management table 106c is a table for managing product information at the stage before actual results are finalized, i.e., the schedule stage. Stages before actual results are finalized include, for example, the stage of ordering a product, the stage of receiving an order for a product, and the stage of changing the sales destination of a product. Schedule management table 106c is registered in response to user instructions from the input device 112.

In this embodiment, the schedule management table 106c includes an order table 106e, a change instruction table 106f, and an order table 106g.

Figure 3A is a schematic diagram showing an example of the data configuration of order table 106e.

The order table 106e is a table for managing order data. The order table 106e is a table that is registered by a user, such as a purchasing agent, when the user places an order for a product. In this embodiment, the order table 106e is a table that associates the order information of the product to be ordered with the seller information.

Order information is an example of pre-performance information. Order information is information related to ordering goods. For example, order information includes order number, line number, order date, receiving warehouse, person in charge, product, lot, quantity, etc. Note that information included in order information is not limited to these.

Figure 3B is a schematic diagram showing an example of the data configuration of the change instruction table 106f. The change instruction table 106f is a table registered by a user such as a warehouse manager when issuing an instruction to change the sales destination information. In this embodiment, the change instruction table 106f is a table that associates the sales destination change information of the product to be changed with the sales destination information.

Sales destination change information is an example of pre-performance information. Sales destination change information is information related to the change of sales destination of the product for which the sales destination is to be changed. For example, sales destination change information includes the change instruction number, line number, change instruction date, incoming warehouse, outgoing warehouse, product, lot, quantity, etc. Note that the information included in sales destination change information is not limited to these. Sales destination information registered in the change instruction table 106f includes, for example, "sales destination (shipping)", which is the sales destination information before the change, and "sales destination (receiving)", which is the sales destination information after the change.

In this embodiment, the schedule management table 106c will be described as an example of a table that is registered by a user such as a warehouse manager when issuing an instruction to change the sales destination information. However, the schedule management table 106c may also be used as a table that is registered by a user such as a warehouse manager when issuing an instruction to change the warehouse information, which is the management location of the product. In this case, for example, the "shipping warehouse" in the schedule management table 106c indicates the management location before the change, and the "receiving warehouse" indicates the management location after the change.

Figure 3C is a schematic diagram showing an example of the data configuration of the order table 106g. The order table 106g is a table that is registered by a user, such as a sales representative, when registering order information. In this embodiment, the order table 106g is a table that associates order information for the product to be ordered with sales destination information.

Order information is an example of pre-performance information. Order information is information about the product that is the subject of the order. For example, order information includes the order number, line number, order date, shipping warehouse, person in charge, product, lot, quantity, etc. Note that information included in order information is not limited to these.

Figures 4A to 4C are schematic diagrams showing an example of the data configuration of the result management table 106d. The result management table 106d is a table for managing products at the stage after the actual results have been determined, i.e., at the result stage. The result stage is, for example, the stage at which results such as the registration of purchase results, the registration of change results, and the registration of sales results have been determined. The result management table 106d is registered, for example, at the stage at which each of these results is determined, by the user's operation instructions via the input device 112.

In this embodiment, the performance management table 106d includes a purchase table 106h, a change table 106i, and a sales table 106j.

Figure 4A is a schematic diagram showing an example of the data structure of the purchasing table 106h.

The purchase table 106h is a table for managing purchase data. The purchase table 106h is a table that is registered by a user, such as a purchasing agent, when the user registers a product purchase record. In this embodiment, the purchase table 106h is a table that associates purchase record information with sales destination information.

Purchase record information is an example of record information. Purchase record information is information related to the purchase record of a product. For example, purchase record information includes purchase number, line number, purchase date, receiving warehouse, person in charge, product, lot, quantity, etc. Note that the information included in purchase record information is not limited to these.

Figure 4B is a schematic diagram showing an example of the data configuration of change table 106i.

Change table 106i is a table for managing sales destination change history information. Change table 106i is a table that is registered by a user such as a warehouse manager when an actual sales destination is changed and the change is confirmed. In this embodiment, change table 106i is a table that associates sales destination information with change history information for products whose sales destination has been changed.

Change performance information is an example of performance information. Change performance information is information about the confirmed sales destination after the change. For example, change performance information includes the change number, line number, change date, receiving warehouse, shipping warehouse, product, lot, quantity, etc. Note that the information included in the change performance information is not limited to these. Sales destination information registered in the change table 106i includes, for example, "Sales destination (shipping)", which is the sales destination information before the change, and "Sales destination (receiving)", which is the sales destination information after the change.

Figure 4C is a schematic diagram showing an example of the data structure of sales table 106j.

The sales table 106j is a table for managing sales data. The sales table 106j is a table registered by a user, such as a sales representative, when the user registers the sales performance of a product. In this embodiment, the sales table 106j is a table that associates sales performance information of sold products with sales destination information.

Sales performance information is an example of performance information. Sales performance information is information about products that have been sold. For example, sales performance information includes sales number, line number, sales date, shipping warehouse, person in charge, product, lot, quantity, etc. Note that information included in sales performance information is not limited to these.

Returning to FIG. 1, the explanation will continue. The control unit 102 is a CPU or the like that performs overall control of the business support device 100. The control unit 102 has an internal memory for storing control programs such as an OS (operating system), programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs.

In this embodiment, the control unit 102 includes a reception unit 102a, a registration unit 102b, an update unit 102c, and an output control unit 102d.

The reception unit 102a receives various information input by the user through operation instructions of the input device 112.

In this embodiment, the reception unit 102a receives input of pre-performance information, which is at least one of the ordering information of the product to be ordered, the order information of the product to be received, and the sales destination change information of the product to be changed, and the sales destination information of the product.

The registration unit 102b associates the received pre-performance information with the seller information and registers them in the schedule management table 106c. In detail, when the registration unit 102b receives input of order information and seller information, it associates the order information with the seller information and registers them in the order table 106e. When the registration unit 102b receives input of order information and seller information, it associates the order information with the seller information and registers them in the order table 106g. When the registration unit 102b receives input of seller change information and seller information, it associates the seller change information with the seller information and registers them in the change instruction table 106f.

In addition, in this embodiment, the reception unit 102a receives input of performance information and customer information, which is at least one of product purchasing performance information, product sales performance information, and customer change performance information.

The registration unit 102b associates the received performance information with the seller information and registers it in the performance management table 106d. In detail, when the registration unit 102b accepts input of purchase performance information and seller information, it associates the purchase performance information with the seller information and registers it in the purchase table 106h. When the registration unit 102b accepts input of sales performance information and seller information, it associates the sales performance information with the seller information and registers it in the sales table 106j. Furthermore, when the registration unit 102b accepts input of seller change performance information and seller information, it associates the change performance information with the seller information and registers it in the change table 106i.

The update unit 102c updates the inventory table based on the received performance information and sales destination information.

The output control unit 102d outputs information corresponding to the sales destination information based on the inventory table 106a, the order point master table 106b, the schedule management table 106c, and the performance management table 106d.

2. Specific Examples
A specific example of the process of the task assistance device 100 in this embodiment will be described with reference to FIGS. 5 to 9D.

First, we will explain the flow of information processing performed by the business support device 100 of this embodiment.

Figure 5 is a flowchart showing an example of the flow of information processing performed by the business support device 100 in this embodiment.

The reception unit 102a judges whether the input of the order information and the seller information has been received (step S100). If the judgment in step S100 is affirmative (step S100: Yes), the process proceeds to step S102. In step S102, the registration unit 102b associates the order information with the seller information and registers them in the order table 106e (step S102). Then, this routine ends.

If a negative judgment is made in step S100 (step S100: No), the process proceeds to step S104. In step S104, the reception unit 102a judges whether input of purchase history information and purchase destination information has been received (step S104). If a positive judgment is made in step S104 (step S104: Yes), the process proceeds to step S106. In step S106, the registration unit 102b associates the purchase history information with the purchase destination information and registers them in the purchase table 106h (step S106). The update unit 102c updates the inventory table 106a based on the purchase history information and purchase destination information registered in step S106 (step S108). Then, this routine ends.

If the answer is negative in step S104 (step S104: No), the process proceeds to step S110. In step S110, the reception unit 102a judges whether the input of the sales destination change information and the sales destination information has been received (step S110). If the answer is positive in step S110 (step S110: Yes), the process proceeds to step S112. In step S112, the sales destination change information and the sales destination information received in step S110 are associated with each other and registered in the change instruction table 106f (step S112). Then, this routine ends.

If the determination in step S110 is negative (step S110: No), the process proceeds to step S114. In step S114, the reception unit 102a determines whether input of the sales destination change history information and sales destination information has been received (step S114). If the determination in step S114 is positive (step S114: Yes), the process proceeds to step S116. In step S116, the registration unit 102b associates the change history information with the sales destination information and registers them in the change table 106i (step S116). The update unit 102c updates the inventory table 106a based on the change history information and sales destination information registered in step S116 (step S118). Then, this routine ends.

If a negative judgment is made in step S114 (step S114: No), the process proceeds to step S120. In step S120, the reception unit 102a judges whether or not input of the order information and the seller information has been received (step S120). If a positive judgment is made in step S120 (step S120: Yes), the process proceeds to step S122. In step S122, the registration unit 102b associates the order information and the seller information received in step S120 and registers them in the order table 106g (step S122). Then, this routine ends.

If the result of step S120 is negative (step S120: No), the process proceeds to step S124. In step S124, it is determined whether the input of sales performance information and sales destination information has been accepted (step S124). If the result of step S124 is negative (step S124: No), the process ends this routine. If the result of step S124 is positive (step S124: Yes), the process proceeds to step S126. In step S126, the registration unit 102b associates the performance information and sales destination information accepted in step S124 and registers them in the performance management table 106d (step S126). The update unit 102c updates the inventory table 106a based on the performance information and sales destination information registered in step S126 (step S128). Then, the process ends this routine.

As described above, the schedule management tables 106c, such as the order table 106e, the change instruction table 106f, and the order table 106g, are tables for managing products in the stage before the actual results are finalized, i.e., the schedule stage. On the other hand, the results management tables 106d, such as the purchase table 106h, the change table 106i, and the sales table 106j, are tables for managing products in the stage after the actual results are finalized, i.e., the results stage. And the inventory table 106a is a table for managing the actual inventory status of products.

For this reason, the update unit 102c does not update the inventory table 106a when the schedule management table 106c is registered or changed, but updates the inventory table 106a when the performance management table 106d is registered or updated. For this reason, the update unit 102c updates the inventory table 106a so that it becomes a table that reflects the actual inventory status of the product.

The order table 106e, change instruction table 106f, and order table 106g, which are registered in the pre-performance stage, are tables that respectively associate pre-performance information such as order information, order information, and customer change information with customer information. The inventory table 106a is a table that associates product information, customer information, and inventory quantity.

Therefore, the user can search the information registered in the inventory table 106a and the information registered in each of the order table 106e, change instruction table 106f, and order receipt table 106g using the seller information as a search key. In other words, the user can check the information registered in the inventory table 106a and the schedule management table 106c on a seller-by-seller basis before the actual results are specified or registered, such as when considering an order, when registering change instruction information for the seller information, and when registering order information.

Therefore, by referring to and using these tables in the business support device 100 of this embodiment, the user can grasp the planned inventory for a specific sales destination before the actual results are confirmed.

Next, we will explain in detail the flow of work using the work support device 100 in this embodiment and the changes in the contents of the tables.

Figure 6 is an explanatory diagram of an example of a business flow using the business support device 100 in this embodiment. Figure 6 shows an example of a business flow that follows the order, purchase, change, order, and sales of a product.

First, for example, a purchasing clerk considers ordering a product (step S1). At the ordering stage, when considering an order, the purchasing clerk considers whether or not to place an order, taking into account not only the current inventory but also the arrival and shipping schedules for each sales destination. In detail, the purchasing clerk generates an order recommendation list by operating the input device 112 of the business support device 100 while referring to the inventory table 106a and the order point master table 106b. For example, the purchasing clerk compares the inventory status of products shown in the inventory table 106a shown in FIG. 2A with the order point master table 106b shown in FIG. 2B, and outputs a list of products that need to be ordered as an order recommendation list. Products that need to be ordered are, for example, products whose inventory quantity has fallen below the order point.

Here, the inventory table 106a in this embodiment is a table that associates customer information, product information, and inventory quantities. The order point master table 106b is a table that associates warehouses, products, order quantities, and safety stock quantities with customer information.

Therefore, users such as purchasing personnel can use the seller information as a search key to search the inventory table 106a and the order point master table 106b to consider whether or not to order products for each seller.

Next, the purchasing clerk inputs the order information (step S2). The purchasing clerk operates the input device 112 of the business support device 100 to input the order information of the product to be ordered and the buyer information. For example, the output control unit 102d of the business support device 100 displays the registration screen of the order table 106e shown in FIG. 7A on the output device 114. FIG. 7A is a schematic diagram of an example of the order table 106e. The purchasing clerk inputs the order information while referring to the displayed registration screen. Furthermore, if the buyer has been specified, the purchasing clerk inputs the buyer information. If the buyer has not been determined, the purchasing clerk inputs "FREE" as the buyer information. The registration unit 102b of the business support device 100 registers the input information in the order table 106e. Thus, for example, the order table 106e shown in FIG. 7A is registered.

Returning to FIG. 6 for further explanation. When the product is purchased based on the order information, the purchasing clerk operates the input device 112 of the business support device 100 to input the purchasing history information and the buyer information (step S3). For example, the output control unit 102d of the business support device 100 displays the registration screen of the purchasing table 106h shown in FIG. 7B on the output device 114. FIG. 7B is a schematic diagram of an example of the purchasing table 106h. The purchasing clerk inputs the purchasing history information and the buyer information while referring to, for example, the order information and the displayed registration screen. The registration unit 102b of the business support device 100 registers the input information in the purchasing table 106h. As a result, for example, the purchasing table 106h shown in FIG. 7B is registered.

Note that users who enter order information and purchase record information are not limited to purchasing personnel.

The update unit 102c updates the inventory table 106a based on the registered purchase history information and sales destination information.

For example, the inventory table 106a shown in FIG. 7C is updated to the inventory table 106a shown in FIG. 7D based on the purchase record information and sales destination information registered in the purchase table 106h shown in FIG. 7B. FIG. 7C is a schematic diagram of an example of the inventory table 106a before the update. FIG. 7D is a schematic diagram of an example of the inventory table 106a after the update.

Here, at the stage of inputting the order information in step S2 above, the inventory table 106a is in the state before the update shown in FIG. 7C. However, in this embodiment, various information is registered in the inventory table 106a and the order table 106e in association with the seller information. For example, at the stage of inputting the order information in step S2, the user checks the inventory table 106a shown in FIG. 7C and the order table 106e entered in step S2. For example, the planned inventory quantity for a specific seller can be easily calculated by "current inventory quantity + inventory quantity scheduled to arrive - inventory quantity scheduled to be shipped".

This confirmation allows the user to check the inventory status in inventory table 106a shown in FIG. 7D, which is the state after the actual results have been confirmed, using inventory table 106a before the update and order table 106e shown in FIG. 7C. The user can also easily consider ordering.

Specifically, in the example shown in Figures 7A to 7D, when entering order information, the user can check in advance whether an excessive amount has been ordered or reserved, for example, that there are 12 units of inventory reserved for customer A out of the total inventory.

Returning to FIG. 6 for further explanation, the business support device 100 of this embodiment can provide a system that can grasp the planned inventory for the sales destination at the stage of inputting the order information in step S2, which is the stage prior to step S3 where the actual sales amount is finalized.

Next, for example, a warehouse clerk inputs the sales destination change information (step S4). The purchasing clerk inputs the sales destination change information and the sales destination information by operating the input device 112 of the business support device 100. For example, the output control unit 102d of the business support device 100 displays the registration screen of the change instruction table 106f shown in FIG. 8A on the output device 114. FIG. 8A is a schematic diagram of an example of the change instruction table 106f. The warehouse clerk inputs the sales destination change information and the sales destination information while referring to the displayed registration screen. The registration unit 102b of the business support device 100 registers the input information in the change instruction table 106f. Therefore, for example, the change instruction table 106f shown in FIG. 8A is registered.

Returning to FIG. 6, the explanation will be continued. When the sales destination is actually changed based on the change instruction table 106f, the warehouse staff operates the input device 112 of the business support device 100 to input the change record information and the sales destination information (step S5). For example, the output control unit 102d of the business support device 100 displays the registration screen of the change table 106i shown in FIG. 8B on the output device 114. FIG. 8B is a schematic diagram of an example of the change table 106i. The warehouse staff inputs the change record information and the sales destination information while referring to the destination change information and the displayed registration screen. The registration unit 102b of the business support device 100 registers the input information in the change table 106i. As a result, the change table 106i shown in FIG. 8B is registered.

The user who inputs the sales destination change information and change record information is not limited to the warehouse staff. As described above, the user may input instruction information for moving the product to another warehouse as sales destination change information. Similarly, the user may input information indicating that the product has been moved to another warehouse as change record information.

The update unit 102c updates the inventory table 106a based on the registered change history information and sales destination information.

For example, the inventory table 106a shown in FIG. 8C is updated to the inventory table 106a shown in FIG. 8D based on the change record information and sales destination information registered in the change table 106i shown in FIG. 8B. FIG. 8C is a schematic diagram of an example of the inventory table 106a before the update. FIG. 8D is a schematic diagram of an example of the inventory table 106a after the update.

Here, at the stage of inputting the sales destination change information in step S4 above, the inventory table 106a is in the pre-update state shown in FIG. 8C. However, in this embodiment, various information is registered in the change instruction table 106f and the inventory table 106a in association with the sales destination information. For example, at the stage of inputting the order information in step S4, the user checks the inventory table 106a shown in FIG. 8C and the change instruction table 106f entered in step S4. This check enables the user to check the inventory status of the inventory table 106a shown in FIG. 8D, which is the state after the actual results have been confirmed, using the pre-update inventory table 106a and change instruction table 106f shown in FIG. 8C.

Specifically, in the example shown in Figures 8A to 8D, the user can confirm that at the stage of inputting the sales destination change information, the 12 units of inventory reserved for customer A have been ordered and reduced to 1 unit, and that the item has been appropriately dispensed.

Returning to FIG. 6 for further explanation, the business support device 100 of this embodiment can provide a system that can grasp the planned inventory for a customer at the stage of inputting customer change information in step S4, which is the stage prior to step S5 where the change record is finalized.

Next, for example, a sales representative inputs order information (step S6). The sales representative operates the input device 112 of the business support device 100 to input order information and customer information. For example, the output control unit 102d of the business support device 100 displays a registration screen of the order table 106g shown in FIG. 9A on the output device 114. FIG. 9A is a schematic diagram of an example of the order table 106g. The sales representative inputs order information while referring to the displayed registration screen. Also, if the designated customer has been decided, the sales representative inputs customer information. If the customer has not been decided, the sales representative inputs "FREE" as the customer information. The registration unit 102b of the business support device 100 registers the input information in the order table 106g. Therefore, for example, the order table 106g shown in FIG. 9A is registered.

Returning to FIG. 6, the explanation will be continued. When an item is actually sold based on the order table 106g, the sales representative operates the input device 112 of the business support device 100 to input sales performance information and purchase destination information (step S7). For example, the output control unit 102d of the business support device 100 displays the registration screen of the sales table 106j shown in FIG. 9B on the output device 114. FIG. 9B is a schematic diagram of an example of the sales table 106j. The sales representative inputs the sales performance information and purchase destination information while referring to the order information and the displayed registration screen. The registration unit 102b of the business support device 100 registers the input information in the sales table 106j. As a result, the sales table 106j shown in FIG. 9B is in a registered state.

Note that users who enter order information and sales performance information are not limited to sales representatives.

The update unit 102c updates the inventory table 106a based on the registered sales performance information and customer information.

For example, the inventory table 106a shown in FIG. 9C is updated to the inventory table 106a shown in FIG. 9D based on the sales performance information and sales destination information registered in the sales table 106j shown in FIG. 9B. FIG. 9C is a schematic diagram of an example of the inventory table 106a before the update. FIG. 9D is a schematic diagram of an example of the inventory table 106a after the update.

Here, at the stage of inputting the order information in step S6 above, the inventory table 106a is in the pre-update state shown in FIG. 9C. However, in this embodiment, various information is registered in the order table 106g and the inventory table 106a in association with the seller information. For example, at the stage of inputting the order information in step S6, the user checks the inventory table 106a shown in FIG. 9C and the order table 106g entered in step S6. This check enables the user to check the inventory status of the inventory table 106a shown in FIG. 9D, which is the state after the actual results have been confirmed, using the pre-update inventory table 106a and the order table 106g shown in FIG. 9C.

In other words, the business support device 100 of this embodiment can provide a system that can grasp the planned inventory for the customer at the stage of inputting order information in step S6, which is the stage prior to step S7 in which the change record is finalized. Therefore, the sales representative, who is the user, can easily grasp the planned inventory for the customer at the stage of inputting order information.

Specifically, in the example shown in Figures 7A to 9D, the user can quickly grasp the possibility of overstocking because the inventory reserved for customer B has increased from 5 to 7 and there are no planned orders.

As described above, the business support device 100 of this embodiment includes a memory unit 106 and a control unit 102. The memory unit 106 stores an inventory table 106a in which product information, customer information, and inventory quantities are registered in association with each other. The control unit 102 includes a reception unit 102a and a registration unit 102b. The reception unit 102a receives input of pre-performance information, which is at least one of order information for a product to be ordered, order information for a product to be received, and customer change information for a product to be changed in order to the customer, and customer information for the product. The registration unit 102b registers the received pre-performance information and customer information in the schedule management table 106c in association with each other.

Therefore, even before the actual results are finalized, the user can check the inventory status for the buyer in the schedule management table 106c after the results are finalized by referring to the inventory table 106a and schedule management table 106c, which contain the buyer information. In other words, the business support device 100 of this embodiment can provide a system that can grasp the planned inventory for the buyer before the actual results are finalized. In addition, the user can easily check the planned inventory for each buyer in a short time before the results are specified, such as order consideration and inventory confirmation.

Therefore, the business support device 100 of this embodiment can improve the efficiency of business execution.

In addition, the business support device 100 of this embodiment is configured with a table of the above configuration including seller information, making it possible to provide a system that can easily grasp which products are assigned to which seller. In addition, the business support device 100 of this embodiment is configured with a table of the above configuration including seller information, making it possible to provide information using seller information as a search key. This allows the user to easily grasp the inventory status for a specific seller, and to easily check information such as whether or not a specific seller is carrying excess inventory. In addition, the business support device 100 of this embodiment can suppress a deterioration in the inventory turnover rate for a specific seller.

[3. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby making it possible to contribute to goals 8 and 9 of the SDGs.

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

4. Other embodiments
The present invention may be embodied in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

In addition, the processing procedures, control procedures, specific names, registered data for each process, information including parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

In addition, with regard to the business support device 100, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the business support device 100, particularly the processing functions performed by the control unit 102, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the business support device 100 as necessary. That is, a computer program for giving instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the business support device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored on a non-transitory computer-readable recording medium, and may also be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, and a Blu-ray (registered trademark) Disc.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

The various databases stored in the memory unit 106 are storage devices such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and store various programs, tables, databases, and web page files used for various processes and website provision.

The business support device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The business support device 100 may be realized by implementing software (including programs or data, etc.) that causes the device to realize the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or functional loads. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

100 Business support device 102a Reception unit 102b Registration unit 102c Update unit 102d Output control unit 106a Stock table 106c Schedule management table 106d Performance management table 106e Order table 106f Change instruction table 106g Order table 106i Change table 106j Sales table

Claims (10)

A business support device including a storage unit and a control unit,
The storage unit is
storing an inventory table in which product information including storage location information of the product , customer information , and an actual inventory quantity, which is the number of products actually existing in the storage location specified by the storage location information , are registered in association with each other;
The control unit is
A receiving means for receiving input of pre-performance information, which is at least one of order information for a product to be ordered, order information for a product to be received, and sales destination change information for a product to be changed to a sales destination, and the sales destination information;
a registration means for registering the received pre-performance information and the received customer information in a schedule management table in association with each other;
A business support device comprising: The inventory table is capable of registering information indicating that a buyer is undecided as the buyer information.
2. The business support device according to claim 1 , The registration means includes:
when input of the order information and the sales destination information is accepted, the order information, which is the pre-performance information, and the sales destination information are associated with each other and registered in an order table, which is the schedule management table;
3. The business support device according to claim 1 or 2 . The registration means includes:
When the input of the order information and the customer information is accepted, the order information, which is the pre-performance information, and the customer information are associated with each other and registered in the order table, which is the schedule management table.
4. The business support device according to claim 1, wherein the business support device is a computer . The registration means includes:
When the input of the sales destination change information and the sales destination information is accepted, the sales destination change information, which is the pre-performance information, and the sales destination information are associated with each other and registered in a change instruction table, which is the schedule management table.
5. The business support device according to claim 1, wherein the business support device is a computer . The receiving means is
further receiving input of at least one of product purchase record information, product sales record information, and customer change record information, and the customer information;
The registration means includes:
The received performance information and the sales destination information are associated with each other and registered in a performance management table.
6. The business support device according to claim 1, wherein the business support device is a computer . an updating means for updating the inventory table based on the received performance information and sales destination information;
7. The business support device according to claim 6, further comprising: The registration means includes:
When the input of the purchase record information and the sales destination information is accepted, the purchase record information, which is the record information, is associated with the sales destination information, and is registered in a purchase table, which is the record management table;
When the input of the sales performance information and the sales destination information is accepted, the sales performance information, which is the performance information, is associated with the sales destination information, and is registered in a sales table, which is the performance management table;
When the input of the change record information and the sales destination information is accepted, the change record information, which is the record information, is associated with the sales destination information, and is registered in a change table, which is the record management table.
8. The business support device according to claim 6 or 7 . A business support method for causing an information processing device having a control unit and a storage unit to execute the business support method,
The storage unit includes:
An inventory table is stored in which product information including storage location information of the product , sales destination information , and an actual inventory quantity, which is the number of products actually existing in the storage location specified by the storage location information , are registered in association with each other;
Executed by the control unit,
receiving input of pre-performance information, which is at least one of order information for a product to be ordered, order information for a product to be received, and change of purchase destination information for a product to be changed, and the purchase destination information;
a step of registering the received pre-performance information and the sales destination information in a schedule management table in association with each other;
A business support method comprising: A business support program to be executed by an information processing device having a control unit and a storage unit,
The storage unit includes:
An inventory table is stored in which product information including storage location information of the product , sales destination information , and an actual inventory quantity, which is the number of products actually existing in the storage location specified by the storage location information , are registered in association with each other;
In the control unit,
receiving input of pre-performance information, which is at least one of order information of the product to be ordered, order information of the product to be received, and change of the seller information of the product to be changed to a new seller, and the seller information of the product;
a step of registering the received pre-performance information and the sales destination information in a schedule management table in association with each other;
A business support program for carrying out the above.

Images