Work support device, work support method and work support program

Abstract

To maintain and improve business transactions with business partners by managing business transaction status with the business partners.SOLUTION: An elapsed days detection unit detects, based on business transaction data, business transaction elapsed days from a date of the business transaction with a customer till the current date. A business transaction interval elapsed days detection unit detects business transaction interval elapsed days as days of difference between business transaction interval days as an interval of business transactions with the customer recorded in advance in a memory unit and detected business transaction elapsed days. A data generation unit generates business transaction performance data for each transaction, at a minimum, including the customer, the business transaction elapsed days, the business transaction interval days, and the date of the business transaction with the customer. An output control unit outputs the generated business transaction data via an external device. As a result, business transaction intervals with the customer can be easily managed, and the business transactions with business partners can be maintained and improved.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a business support device, a business support method, and a business support program. [Background technology]

[0002] Patent Document 1 (JP Patent Publication No. 2009-288886) discloses an awareness server that can quickly and accurately contact a person in charge about work using a fixed method that eliminates personal dependencies, without the administrator having to contact the person in charge directly, and can make the person in charge aware of delays in delivery dates, etc.

[0003] This awareness server uses the business data and the management master to determine whether or not the awareness generation conditions are met based on the awareness execution timing. If it determines that the awareness generation conditions are met, it creates awareness data including condition comments, etc., and distributes or displays the awareness data based on the awareness notification destination and awareness notification method. This makes it possible to make the person in charge aware of delivery delays, etc. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2009-288886 A Summary of the Invention [Problem to be solved by the invention]

[0005] In the business of delivering ordered products, it is common to repeatedly receive orders for products for which unit prices have been estimated. However, as the number of business partners and products increases, it becomes difficult to manage the business transaction status with each business partner individually. If management of the business transaction status with each business partner is neglected, it will result in the inconvenience of losing business opportunities with business partners.

[0006] The present invention has been made in consideration of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that make it possible to manage the status of commercial transactions with trading partners and maintain and improve commercial transactions with trading partners. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the object, the business support device of the present invention has an elapsed days detection unit that detects the number of days since a commercial transaction was conducted with a customer to the current date based on commercial transaction data, a commercial transaction interval elapsed days detection unit that detects the number of days since a commercial transaction interval, which is the number of days between commercial transactions with a customer pre-stored in a memory unit, and the detected number of days since a commercial transaction was conducted, a data generation unit that generates commercial transaction performance data including at least, for each commercial transaction target, the customer, the number of days since a commercial transaction was conducted, the number of days since a commercial transaction was conducted, the number of days since a commercial transaction was conducted, and the date on which a commercial transaction was conducted with the customer, and an output control unit that outputs the commercial transaction performance data via an external device.

[0008] In addition, in order to solve the above-mentioned problems and achieve the object, the business support method of the present invention includes an elapsed days detection step in which an elapsed days detection unit detects the number of days elapsed since a commercial transaction was conducted with a customer to the current date based on commercial transaction data; a commercial transaction interval elapsed days detection step in which an elapsed days interval detection unit detects the number of days elapsed since a commercial transaction was conducted, which is the number of days between a commercial transaction interval, which is the interval between commercial transactions with a customer stored in advance in a memory unit, and the detected number of days elapsed since a commercial transaction was conducted; a data generation step in which a data generation unit generates commercial transaction performance data including at least, for each commercial transaction target, the customer, the number of days elapsed since a commercial transaction, the number of days between commercial transactions, the number of days elapsed since a commercial transaction was conducted, and the date when the commercial transaction was conducted with the customer; and an output control step in which an output control unit outputs the commercial transaction performance data via an external device.

[0009] In addition, in order to solve the above-mentioned problems and achieve the object, the business support program of the present invention causes a computer to function as: an elapsed days detection unit that detects the number of days since a commercial transaction was conducted with a customer to the current date based on commercial transaction data; a commercial transaction interval elapsed days detection unit that detects the number of days since a commercial transaction interval, which is the number of days between commercial transactions with a customer pre-stored in a memory unit, and the detected number of days since a commercial transaction was conducted; a data generation unit that generates commercial transaction performance data including at least, for each commercial transaction target, the customer, the number of days since a commercial transaction was conducted, the number of days since a commercial transaction was conducted, the number of days since a commercial transaction was conducted, and the date of the commercial transaction with the customer; and an output control unit that outputs the commercial transaction performance data via an external device. Effect of the Invention

[0010] The present invention can manage the status of commercial transactions with business partners, and can maintain and improve commercial transactions with business partners. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram showing a hardware configuration of a unit price estimate management device according to an embodiment. [Diagram 2] FIG. 2 is a diagram showing an update matrix which is a pattern of the master update process. [Diagram 3] FIG. 3 is a flowchart for explaining an outline of the overall processing flow of the control unit of the unit price estimate management device. [Figure 4] FIG. 4 is a diagram showing an example of sample data for explaining a specific example of processing by the control unit of the unit price estimate management device. [Diagram 5] FIG. 5 is a diagram showing an example of sample data for explaining a specific example of processing by the control unit of the unit price estimate management device. [Figure 6] FIG. 6 is a diagram showing an example of sample data for explaining a specific example of the processing of the control unit of the unit price estimate management device. [Figure 7] FIG. 7 is a diagram showing an example of sample data for explaining a specific example of the processing of the control unit of the unit price estimate management device. [Figure 8] FIG. 8 is a diagram showing an example of sample data for explaining a specific example of the processing of the control unit of the unit price estimate management device. [Figure 9] FIG. 9 is a diagram showing an example of sample data for explaining a specific example of the processing of the control unit of the unit price estimate management device. [Figure 10] FIG. 10 is a diagram showing an example of sample data for explaining a specific example of the processing of the control unit of the unit price estimate management device. [Figure 11] FIG. 11 is a diagram showing an example of sample data for explaining a specific example of the processing of the control unit of the unit price estimate management device. [Figure 12] FIG. 12 is a diagram showing an example of the order input screen. [Figure 13] FIG. 13 is a diagram showing an example of sample data for explaining a specific example of the processing of the control unit of the unit price estimate management apparatus. [Figure 14] FIG. 14 is a diagram showing an example of the estimate input screen (main screen). [Figure 15] FIG. 15 is a diagram showing an example of a quotation input screen (details input screen). [Figure 16] FIG. 16 is a diagram illustrating an example of the quotation data. [Figure 17] FIG. 17 is a diagram illustrating an example of the route master. [Figure 18] FIG. 18 is a diagram showing an example of a sales order performance table by commercial product. [Figure 19] FIG. 19 is a diagram showing partial data of the order performance table by commercial product, which is generated based on the route master. [Figure 20] FIG. 20 is a diagram illustrating an example of the customer master. [Figure 21] FIG. 21 is a diagram illustrating an example of the order data. [Figure 22] FIG. 22 is a diagram showing a display designation screen for the order performance table by commercial product. [Diagram 23]Figure 23 shows an example of an order performance table by commercial product that is generated using the commercial transaction performance data of the commercial product performance work updated on the specified reference date when "Update" is specified in the data update category on the display designation screen for the order performance table by commercial product. [Figure 24] FIG. 24 is a diagram showing an example of a commercial product-by-product performance cause input screen in which the results of the supervisor's analysis of the causes are input. [Diagram 25] Figure 25 shows an example of an order performance table by commercial product in which the results of the cause analysis by a supervisor have been entered, along with specific information (order opportunity loss warning) identifying other staff members who handle the same commercial transaction object as the commercial transaction object for which the cause analysis was conducted, and factor data have been added. [Figure 26] FIG. 26 is a diagram showing an example of a commercial product-by-product performance cause input screen in which products (other products) similar to the product that is the subject of the cause analysis are input along with the results of the cause analysis by the supervisor. [Figure 27] Figure 27 shows an example of an order performance table by product in the trade flow, to which is added the results of the supervisor's cause analysis, specific information (warning of lost order opportunities) identifying other staff members who handle the same commercial transaction object as the commercial transaction object for which the cause analysis was conducted, cause data, and products (other products) similar to the product that was the subject of the cause analysis. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] An embodiment in which the present invention is applied to a unit price estimate management device that estimates unit prices will be described in detail below with reference to the drawings as an example. Note that the present invention is not limited to the following embodiment.

[0013] [overview] Nowadays, salespeople estimate the unit price of commercial transactions such as goods or services using various communication tools used by clients, such as spreadsheet software, e-mail, telephone, etc. This makes it difficult for managers to grasp the status of unit price estimates, leading to commercial transactions being conducted at unintended unit prices, resulting in inconveniences such as loss of profits.

[0014] In addition, because the results of the contract were circulated in writing and the information system staff registered various master data separately, there were mistakes in the master data and time lags until the data was registered. This caused inconveniences such as the master data not being created when the clerks wanted to register it, and also led to frequent mistakes due to inputting data each time.

[0015] For this reason, in the embodiment of the unit price estimate management device, a sales representative registers unit price estimates for customers etc. by inputting estimates, and when a superior approves them, each unit price master (product unit price master by customer, product unit price master by customer supplier, product unit price master by customer supplier) and route master are created based on the contents of the registered estimate.

[0016] This allows contract details to be registered as quotation information, enabling centralized management and sharing of quotation information. In addition, after a superior approves the contract details, the unit price master is automatically created, making the work of unit price quotation more efficient. In addition, based on the registration information of one quotation, the unit price master to be updated is automatically allocated and registered, so not only is the registration of the unit price master more efficient, but the approved quotation information is reflected, strengthening control and making the overall work, including the input by office staff, more efficient.

[0017] For example, chemical trading companies often receive repeated orders for products for which they have made unit price estimates. When the number of business partners and products increases, it becomes difficult to manage the business transaction status with each business partner individually. For this reason, if a business partner places an order with another company for a product that the company had been ordering from the company until recently, the business partner's orders to the company are interrupted, but the company is slow to notice this, which causes the inconvenience of losing business opportunities with the business partner.

[0018] For this reason, the unit price estimate management device of the embodiment makes it possible to easily grasp the order frequency for each commercial product by registering the number of days between orders in the route master at the time of unit price estimate.

[0019] Furthermore, the unit price estimate management device according to the embodiment analyzes the order status to prevent loss of business opportunities.

[0020] [Configuration of unit price estimate management device] 1 is a block diagram showing a hardware configuration of a unit price estimate management device 100 according to an embodiment of the present invention. The unit price estimate management device 100 is a workstation or a commercially available desktop personal computer.

[0021] The unit price estimate management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units comprised in the unit price estimate management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0022] The communication interface unit 104 communicatively connects the unit price estimate management 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 unit price estimate management device 100, the server device 200, the sales representative terminal device 410, and the sales manager terminal device 420 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). As a result, the communication interface unit 104 is configured to be able to communicate data with the server device 200 via the network 300.

[0023] The salesperson terminal device 410 is a terminal device used by a salesperson in the sales department, and is configured to be able to access the unit price estimate management device 100 .

[0024] The sales manager terminal device 420 is a terminal device used by a sales department manager, and is configured to be able to access the unit price estimate management device 100 .

[0025] An input device 112 and an output device 114 are connected to the input / output interface unit 108. In addition to a monitor (including a home television), a speaker and a printer can be used as the output device 114. In addition to a keyboard, a mouse and a microphone, the input device 112 can also be a monitor that cooperates with the mouse to realize a pointing device function.

[0026] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs for cooperating with an OS (Operating System) to give instructions to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, optical disks, etc. can be used as the storage unit 106.

[0027] The storage unit 106 includes a temporary master 106a, a customer-specific product unit price master 106b, a customer-delivery-specific product unit price master 106c, a customer-supplier-specific product unit price master 106d, a customer-delivery-specific product unit price master 106e, a route master 106f, and an estimate data file 106g, each of which is a storage area. The customer-specific product unit price master 106b, the customer-delivery-specific product unit price master 106c, the customer-supplier-specific product unit price master 106d, and the customer-delivery-specific product unit price master 106e are collectively referred to as the "unit price master."

[0028] The temporary master 106a is a master for updating the unit price master, and can be composed of, for example, a table in which quotation number, line number, quotation category (inventory quotation, direct delivery quotation), customer, delivery destination, supplier, application start date, application end date, immediate reflection flag in master after approval, product, quantity, and unit price are associated and registered.

[0029] The customer-specific product unit price master 106b can be configured as a table or the like in which the customer, application start date, application end date, product, quantity, and unit price are registered in association with each other.

[0030] The customer delivery destination-specific product unit price master 106c can be configured as a table or the like in which the customer, delivery destination, application start date, application end date, product, quantity, and unit price are registered in association with each other.

[0031] The customer / supplier-specific product unit price master 106d can be configured as a table or the like in which customer, supplier, application start date, application end date, product, quantity, and unit price are registered in association with each other.

[0032] The customer / delivery / supplier-specific product unit price master 106e can be configured with a table (storage area) or the like in which customer, delivery destination, supplier, application start date, application end date, product, quantity, and unit price are registered in association with each other.

[0033] The route master 106f is a master for managing the flow of trade, and can be configured with a table or the like in which customers, delivery destinations, suppliers, and products are registered in association with each other.

[0034] The quotation data file 106g is a table (storage area) for storing quotation data. The quotation data may include a quotation number, a line number, a quotation category (stock quotation, direct delivery quotation), a business establishment, a quotation date, a planned order date, a planned sales date, a person in charge, a customer, a delivery destination, a supplier, a unit price update category that specifies whether or not to update the temporary master 106a (unit price master) (0: do not update, 1: update), an application start date, an application end date, an approval post-master immediate reflection flag, a product, a quantity, a unit price, an amount, and a description.

[0035] The timing of updating the unit price master can be selected with the Immediately Reflected After Approval flag, either immediately after approval or at any time. If the Immediately Reflected After Approval flag is set to "Immediately reflected", the unit price master is updated immediately after approval, and if it is set to "Do not immediately reflect", the unit price master is updated at any time.

[0036] The storage unit 2 also includes a customer master 106h and a commercial product-specific performance workbook 106W. The customer master 106h stores each customer and the person in charge of each customer in association with each other (see FIG. 20). The commercial product-specific performance workbook 106W stores work data for a commercial product-specific order performance table that displays a list of order performance by commercial product and product. This will be described in detail later.

[0037] The control unit 102 is a CPU or the like that comprehensively controls the unit price estimate management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, and the like, and executes various types of information processing based on these stored programs.

[0038] The control unit 102 is configured to be able to access the temporary master 106a, the customer-specific product unit price master 106b, the customer-delivery-specific product unit price master 106c, the customer-supplier-specific product unit price master 106d, the customer-delivery-specific product unit price master 106e, the route master 106f, the quotation data file 106g, and the like, which are stored in the storage unit 106. Note that these masters and files may be provided in other locations (for example, the server device 200) as long as they are accessible by the control unit 102.

[0039] The control unit 102 operates based on a unit price estimate management program (including a business support program) stored in the memory unit 2, and functions as a unit price estimate input unit 102a, a workflow processing unit 102b, an approval processing unit 102c, a master update unit 102d, and a screen display control unit 102e.

[0040] The control unit 102 also operates based on the unit price estimate management program, thereby functioning as an elapsed day detection unit 102f, a transaction interval elapsed day detection unit 102g, a data generation unit 102h, an output control unit 102k, and a communication control unit 102m.

[0041] In this example, the unit price estimate input unit 102a to the data generation unit 102h, the output control unit 102k, and the communication control unit 102m of the control unit 102 are described as being realized by software using a unit price estimate management program, but some or all of the unit price estimate input unit 102a to the data generation unit 102h, the output control unit 102k, and the communication control unit 102m of the control unit 102 may be realized by hardware. In either case, the same effects as those described below can be obtained.

[0042] The unit price estimate input unit 102a provides an estimate input screen in response to access from the salesperson terminal device 410, and inputs estimate data including estimate number, estimate date, expected order date, expected sales date, customer, delivery destination, supplier, application start date, product, quantity, unit price, and amount in response to the salesperson's operation on the estimate input screen of the salesperson terminal device 410, and registers the data in the estimate data file 106g. After registering the estimate data, the salesperson uses a workflow to apply for approval of the estimate data.

[0043] The workflow processing unit 102b provides a workflow environment. For example, the workflow processing unit 102b provides a workflow application screen in response to an access from the salesperson terminal device 410, and when the salesperson specifies quotation data and an approval route (e.g., a sales manager) on the workflow application screen, the workflow processing unit 102b executes circulation on the specified approval route and notifies the approval route, and the approval route (e.g., by the sales manager on the sales manager terminal device 420) decides whether to approve or reject the quotation data.

[0044] When the quotation data is approved, the approval processing unit 102c performs the following process based on the quotation data: The temporary master 106a is updated.

[0045] The master updating unit 102d updates the unit price master based on the updated temporary master 106a, and also updates the route master 106f based on the updated temporary master 106a.

[0046] The quotation data (provisional master 106a) includes a post-approval master immediate reflection flag that specifies whether or not the unit price master is to be immediately reflected after approval. If the post-approval master immediate reflection flag is "immediately reflected", the master update unit 102d immediately updates the unit price master after updating the provisional master 106a, and if the post-approval master immediate reflection flag is "not immediately reflected", the master update unit 102d updates the unit price master at any timing after updating the provisional master 106a.

[0047] Fig. 2 is a diagram showing an update matrix, which is a pattern of master update processing. The update patterns of the unit price master will be explained with reference to Fig. 2. The master update unit 102d selects the unit price master to be updated (customer-specific product unit price master 106b, customer-specific product unit price master 106c, customer-specific product unit price master 106d, customer-specific product unit price master 106e) based on the quotation type (inventory quotation, direct delivery quotation) of the quotation data (provisional master 106a) and the presence or absence of a customer, a delivery destination, and a supplier. In any pattern, the route master 106f is always updated.

[0048] If the quotation category is "inventory quotation", the customer is "○: data available", the delivery destination is "-: data unavailable", and the supplier is "-: data unavailable", the customer-specific product unit price master 106b is updated.

[0049] If the quotation category is "inventory quotation", the customer is "○: data available", the delivery destination is "○: data available", and the supplier is "-: no data", the customer delivery destination-specific product unit price master 106c is updated.

[0050] If the quotation category is "direct delivery quotation", the customer is "○: data available", the delivery destination is "-: data not available", and the supplier is "○: data available", the customer / supplier-specific product unit price master 106d is updated.

[0051] If the quotation category is "direct delivery quotation", the customer is "○: data available", the delivery destination is "○: data available", and the supplier is "○: data available", the customer-delivery-supplier-specific product unit price master 106e is updated.

[0052] The screen display control unit 102e controls the display of various screens (eg, a unit price estimate input screen, an order input screen, etc.) displayed on the output device 114 and the input therefor.

[0053] That is, to explain again, the unit price estimate input unit 102a inputs estimate data including the following items: estimate number, estimate date, expected order date, expected sales date, customer, delivery destination, supplier, application start date, product, quantity, unit price, and amount.

[0054] When the input quotation data is approved, the approval processing unit 102c updates the provisional master based on the approved quotation data. The master updating unit 102d updates the various unit price masters 106b to 106e based on the updated provisional master.

[0055] Furthermore, the master updating unit 102d updates the root master 106f based on the updated temporary master 106a.

[0056] In addition, the quotation data includes a post-approval master immediate reflection flag that specifies whether or not the data is to be immediately reflected in the various unit price masters 106b to 106e after approval, and if the post-approval master immediate reflection flag is set to "immediately reflected," the master update unit 102d immediately updates the various unit price masters 106b to 106e after updating the provisional master.

[0057] The quotation data includes a quotation category that specifies an inventory quotation when inventory is sent or a direct delivery quotation when the product is directly shipped from the supplier. As various unit price masters, there are provided a customer-specific product unit price master 106b for storing data on the items of customer, application start date, product, quantity which is the unit of unit price, and unit price in association with each other, and a customer-specific product unit price master 106c for storing data on the items of customer, delivery destination, application start date, product, quantity which is the unit of unit price, and unit price in association with each other. There are also provided a customer-specific product unit price master 106d for storing data on the items of customer, delivery destination, product, quantity which is the unit of unit price, and unit price in association with each other, and a customer-specific product unit price master 106e for storing data on the items of customer, delivery destination, product, application start date, product, quantity which is the unit of unit price, and unit price in association with each other.

[0058] The master update unit 102d selects and updates one of the customer-specific product unit price master 106b, the customer-specific product unit price master 106c, the customer-specific product unit price master 106d, and the customer-specific product unit price master 106e, based on the quotation category of the quotation data and the presence or absence of a customer, a delivery destination, and a supplier.

[0059] Furthermore, the master update unit 102d updates the customer-specific product price master 106b when the quotation data has the quotation category "inventory quotation", the customer "data available", the delivery destination "no data", and the supplier "no data".

[0060] Furthermore, when the quotation category is "inventory quotation", the customer has "data available", the delivery destination has "data available" and the supplier has "no data", the master update unit 102d updates the customer-delivery destination-specific product unit price master 106c.

[0061] Furthermore, the master update unit 102d updates the customer / supplier-specific product unit price master 106d when the quotation category is "direct delivery quotation", the customer has "data available", the delivery destination has "no data", and the supplier has "data available" for the quotation data.

[0062] In addition, the master update unit 102d updates the customer / delivery / supplier-specific product unit price master 106e when the quotation category is "direct delivery quotation", the customer "data available", the delivery destination "data available", and the supplier "data available" for the quotation data.

[0063] The elapsed days detection unit 102f detects the number of days since the date of a transaction with a customer to the current date based on the transaction data. The transaction interval elapsed days detection unit 102g detects the number of days since the transaction interval, which is the difference between the detected number of days since the transaction was performed with the customer and the transaction interval days, which is the interval between transactions with the customer stored in advance in a storage unit (route master 106f: see FIG. 17).

[0064] The data generating unit 102h generates commercial transaction history data (see FIG. 18(a) to FIG. 18(c)) including at least the customer, the number of days since the commercial transaction, the number of days between commercial transactions, the number of days since the commercial transaction, and the date of the commercial transaction with the customer for each commercial transaction target. The output control unit 102k outputs the commercial transaction history data via an external device (output device 114).

[0065] Furthermore, when the transaction interval elapsed days detection unit 102g detects a transaction interval elapsed days indicating that the transaction elapsed days have exceeded the transaction interval days, the data generation unit 102h generates notification data indicating that the transaction elapsed days have exceeded the transaction interval days. The communication control unit 102m controls the communication unit (the communication interface unit 104, for example) to transmit the generated notification data to the terminal device of the person in charge (the sales manager terminal device 420).

[0066] Furthermore, the person in charge (sales manager, etc.) analyzes the reason why the number of days since the commercial transaction exceeded the number of days between commercial transactions based on the notification data. The communication control unit 102m acquires the results of this analysis of the cause via the communication unit (communication interface unit 104). The person in charge inputs the reason why the number of days since the commercial transaction exceeded the number of days between commercial transactions, which is indicated in the acquired analysis results, via the commercial product performance cause input screen. The data generation unit 102h generates commercial transaction performance data to which the input cause ("C-2 (no purchase required due to order for other product)" in the cause input field in FIG. 25(c)) etc. are added.

[0067] In addition, the data generation unit 102h generates transaction performance data to which is added specific information (the circle mark in the record indicated by the arrow (D) in Figure 27(c) and the circle mark in the record indicated by the arrow (F)) that identifies other staff members who handle the same transaction object as the transaction object for which the cause analysis was performed.

[0068] The data generating unit 102h generates commercial transaction performance data to which, together with such specific information, factor data indicating the commercial transaction performance data that was the subject of the cause analysis has been added. As will be described later with reference to Fig. 24, the person in charge inputs the results of the cause analysis via the commercial product performance cause input screen. At that time, the person in charge inputs the "serial number" on the route master 106f of the product whose cause has been analyzed, into the "serial number" input field of the commercial product performance cause input screen in Fig. 24. In the example of Fig. 24, the number input into the serial number input field is "4".

[0069] The column of the "Factor Route Master" shown in Fig. 27(c) is a column that displays the cause data. The data generating unit 102h generates commercial transaction performance data by inputting, as the cause data, the row number of the commercial transaction performance data that was the subject of the cause analysis (in this example, "4") in the column of the "Factor Route Master".

[0070] In addition, when another trade object (e.g., another product: SH01 in FIG. 26) that is similar to the trade object for which the cause analysis was performed is specified, the data generation unit 102h generates trade performance data to which order opportunity suggestion data indicating the specified other trade object (a circle mark next to "order opportunity available" in FIG. 27(c)) is added.

[0071] [Unit Price Estimate Management Operation] Next, the unit price estimate management operation of the unit price estimate management device 100 according to the embodiment will be described.

[0072] (Overall processing) 3 is a flowchart for explaining an outline of the overall processing flow of the control unit 102 of the unit price estimate management device 100. The outline of the overall processing flow of the control unit 102 of the unit price estimate management device 100 will be described with reference to FIG.

[0073] In Fig. 3, the unit price estimate input unit 102a executes estimate input processing (step S1). Specifically, in the estimate input processing, the unit price estimate input unit 102a provides an estimate input screen in response to access from the salesperson terminal device 410, and inputs estimate data including estimate number, estimate category, estimate date, expected order date, expected sales date, customer, delivery destination, supplier, unit price update category, application start date, application end date, immediate reflection flag after approval in master, product, quantity, unit price, and amount in response to the operation of the salesperson on the estimate input screen, and registers the data in the estimate data file 106g. After registering the estimate data, the salesperson applies for approval of the estimate data using a workflow (WF). The sales manager approves the estimate data if it is OK, and rejects it if it is NG.

[0074] The approval processing unit 102c executes the approval process (step S2). Specifically, in the approval process, when the quotation data is approved, the approval processing unit 102c updates the provisional master 106a based on the quotation data. When the superior approves, the provisional master 106a for updating the unit price master is updated.

[0075] The master update unit 102d executes a master update process (step S3). Specifically, the master update unit 102d updates the unit price master and the route master 106f based on the updated temporary master 106a.

[0076] When the master immediate reflection flag after approval is set to "immediately reflect", the master update unit 102d immediately updates the unit price master after updating the provisional master 106a, and when the master immediate reflection flag after approval is set to "not immediately reflect", the master update unit 102d updates the unit price master at any timing after updating the provisional master 106a.

[0077] The master update unit 102d selects the masters to be updated (customer-specific product unit price master 106b, customer-specific product unit price master 106c, customer-specific product unit price master 106d, customer-specific product unit price master 106e) based on the quotation type (inventory quotation, direct delivery quotation) of the quotation data (provisional master 106a) and the presence or absence of a customer, a delivery destination, and a supplier. In this way, the unit price masters to be updated are allocated according to the conditions at the time of quotation.

[0078] Specifically, if the quotation category is "inventory quotation", and the customer is "○: data available", the delivery destination is "-: no data", and the supplier is "-: no data", the customer-delivery destination product price master 106b is updated. If the quotation category is "inventory quotation", and the customer is "○: data available", the delivery destination is "○: data available", and the supplier is "-: no data", the customer-delivery destination product price master 106c is updated. If the quotation category is "direct delivery quotation", and the customer is "○: data available", the delivery destination is "-: no data", and the supplier is "○: data available", the customer-delivery destination product price master 106d is updated. If the quotation category is "direct delivery quotation", and the customer is "○: data available", the delivery destination is "○: data available", and the supplier is "○: data available", the customer-delivery destination product price master 106e is updated.

[0079] (Sample data) A specific example of the processing by the control unit 102 of the unit price estimate management device 100 will be described with reference to Fig. 4 to Fig. 13. Fig. 4 to Fig. 13 are diagrams showing sample data for explaining a specific example of the processing by the control unit 102 of the unit price estimate management device 100.

[0080] (S1: Estimate input processing) A specific example of the quotation input process will be described with reference to Figs. 4 to 6. The unit price quotation input unit 102a provides a quotation input screen in response to access from the salesperson terminal device 410, and inputs quotation data including quotation number, quotation category, quotation date, expected order date, expected sales date, customer, delivery destination, supplier, unit price update category, application start date, application end date, immediate reflection flag after approval in master, product, quantity, unit price, and amount in response to the operation of the salesperson on the quotation input screen, and registers the data in the quotation data file 106g. After registering the quotation data, the salesperson uses a workflow (WF) to apply for approval of the quotation data. The sales manager approves the quotation data if it is OK, and rejects it if it is NG.

[0081] FIG. 4 is a diagram showing a display example of the main screen of the quotation input screen, and FIG. 5 is a diagram showing a display example of the details screen of the quotation input screen. As shown in FIG. 4, the main screen of the quotation input screen is a header area for specifying (inputting) the business establishment, quotation date, expected order date, expected sales date, customer, person in charge, delivery destination, unit price update category, application start date, and application end date, an area for specifying the details of the unit price quotation, and is provided with a details area for specifying the line number, quotation category, post-approval master immediate reflection flag (box checked: immediate reflection, box unchecked: no immediate reflection), product, supplier, quantity, unit price, amount, and details summary, and a registration button (not shown). When the registration button (not shown) is pressed, quotation data according to the input contents on the screen is created and registered in the quotation data file 106g. When data as shown in the examples of FIG. 4 and FIG. 5 is input, quotation data as shown in FIG. 6 is registered.

[0082] When you select a row in the details area (e.g. by double-clicking), a details screen like the one shown in Figure 5 will be displayed. When you enter data on the details screen and press the Reflect button (not shown), the data will be reflected in the selected row in the details area.

[0083] In the header area, "Unit price update category" is specified as "0: Do not update" or "1: Update". If "1: Update" is specified, the quotation data is reflected in the temporary master 106a. "Applicable start date" is the date when the estimated unit price starts to apply. "Applicable end date" is the date when the estimated unit price ends to apply, and is an optional item.

[0084] In the details area, specify "10: Inventory estimate" or "20: Direct delivery estimate" for "Estimate category" and the unit price master will be updated according to the selected estimate category. "Quantity" sets the unit price for each quantity according to the quantity entered. "Supplier" is valid when the estimate category is "20: Direct delivery estimate" and is invalid when it is "10: Inventory estimate" (this is because an inventory estimate is an estimate for when warehouse stock is delivered to a customer / delivery destination, and the supplier is not relevant). "Immediate reflection flag after approval" - if checked ("reflect immediately"), the price master will be reflected immediately upon final approval.

[0085] Figure 6 shows an example of quotation data. Figure 6 shows an example of quotation data corresponding to the input contents on the quotation input screen of Figure 4 and Figure 5. The quotation data has the following fields: quotation number, line number, quotation category, business establishment, quotation date, expected order date, expected sales date, person in charge, customer, delivery destination, supplier, unit price update category, application start date, application end date, immediate reflection in master after approval, product, quantity, unit price, amount, and summary of details.

[0086] In the example shown in the figure, the first line has the quotation number "MT001," line number "1," quotation category "inventory quotation," business location "T100," quotation date "4 / 1 / 2022," expected order date "5 / 10 / 2022," expected sales date "6 / 30 / 2022," person in charge "TAN001," customer "TK001," delivery destination "NOU001," supplier "-," unit price update category "Update," application start date "5 / 1 / 2022," application end date "12 / 31 / 2022," immediate reflection in master after approval "Yes," product "Product A," quantity "1 case," unit price "¥1,000," amount "¥1,000," and detail description "Quotation for new transaction: base quantity."

[0087] (S2: Approval process) The approval process will be described with reference to Fig. 7. When the quotation data is approved, the approval processing unit 102c updates the temporary master 106a based on the quotation data.

[0088] 7 is a diagram showing an example of data in the temporary master 106a. The temporary master 106a includes fields such as quotation number, line number, quotation category, customer, delivery destination, supplier, application start date, application end date, immediate reflection flag in master after approval, product, quantity, and unit price.

[0089] In the example shown in the figure, the first line has the quotation number "MT001," line number "1," quotation category "inventory quotation," customer "TK001," delivery destination "NOU001," supplier "-," application start date "2022 / 5 / 1," application end date "2022 / 12 / 31," immediate reflection flag after approval "immediate reflection," product "product A," quantity "1 case," and unit price "￥1,000." For line numbers "1" and "4," the immediate reflection flag after approval is set to "immediate reflection," so the unit price master is updated immediately.

[0090] (S3: Master update process) A specific example of the master update process will be described with reference to Fig. 8 and Fig. 9. The master update unit 102d updates the unit price master and the route master 106f based on the updated temporary master 106a. If the master immediate reflection flag after approval is "immediately reflected", the master update unit 102d updates the unit price master immediately after updating the temporary master 106a, and if the master immediate reflection flag after approval is "not immediately reflected", the master update unit 102d updates the unit price master at any timing after updating the temporary master 106a. In addition, the master update unit 102d selects the master to be updated (customer-specific product unit price master 106b, customer-specific product unit price master 106c, customer-specific product unit price master 106d, customer-specific product unit price master 106e) based on the quotation category (inventory quotation, direct delivery quotation) of the quotation data (temporary master 106a) and the presence or absence of a customer, a delivery destination, and a supplier.

[0091] For row numbers "1" and "4" in the temporary master 106a in Fig. 7, where the immediate master reflection flag after approval is set to "immediately reflected", the unit price master is updated immediately as shown in Figs. 8(A) and (B). For row numbers "1" to "3", the quotation category is "inventory quotation", the customer is "TK001", the delivery destination is "NOU001", and the supplier is "no data", so the customer-delivery destination-specific product unit price master 106c is updated. For row number "4", the quotation category is "direct delivery quotation", the customer is "TK001", the delivery destination is "NOU001", and the supplier is "SR001", so the customer-delivery destination-specific product unit price master 106e is updated.

[0092] 8(A) is a diagram showing an example of updating the customer delivery destination-specific product unit price master 106c. The customer delivery destination-specific product unit price master 106c has the following fields: customer, delivery destination, application start date, application end date, product, quantity, and unit price. In the example shown in the figure, the fields are customer "TK001", delivery destination "NOU001", application start date "2022 / 5 / 1", application end date "2022 / 12 / 31", product "product A", quantity "1 case", and unit price "￥1,000".

[0093] 8B is a diagram showing an example of updating the customer delivery destination supplier-specific product unit price master 106e. The customer delivery destination supplier-specific product unit price master 106e has the following fields: customer, delivery destination, supplier, application start date, application end date, product, quantity, and unit price. In the example shown in the figure, the fields are customer "TK001", delivery destination "NOU001", supplier "SR001", application start date "2022 / 5 / 1", application end date "2022 / 12 / 31", product "product B", quantity "1 piece", and unit price "￥200".

[0094] 8C shows an example of updating the route master 106f. The route master 106f has items for customer, delivery destination, supplier, and product. In the example shown in the figure, the first line shows customer "TK001", delivery destination "NOU001", supplier "-", and product "product A", while the second line shows customer "TK001", delivery destination "NOU001", supplier "SR001", and product "product B".

[0095] For row numbers “2” and “3” in the temporary master 106a in FIG. 7, in which the information on immediate reflection after approval is “not reflected immediately”, the temporary master 106a is updated, and the customer delivery destination-specific product unit price master 106c is updated at any timing as shown in FIG. 9(A).

[0096] Fig. 9A is a diagram showing an example of updating the customer delivery destination-specific product unit price master 106c. Fig. 9B is a diagram showing an example of updating the route master 106f. As the same record already exists in the route master 106f, it is overwritten and updated.

[0097] Next, a case where the estimate is revised at a later date and the revised estimate data is registered will be described with reference to Figs.

[0098] FIG. 10 is a diagram showing an example of revised quotation data. In FIG. 10, the data in line number "1" of the quotation data in FIG. 6 has been revised. In FIG. 10, the quotation number has been revised to "MT002", quotation date to "2022 / 6 / 1", expected order date to "2022 / 6 / 10", application start date to "2022 / 6 / 1", unit price to "¥1,100", amount to "¥1,100", and line item description to "Quotation revision for existing transaction".

[0099] FIG. 11A shows an example of an updated temporary master 106a that has been updated based on the revised quotation data of FIG.

[0100] Fig. 11B shows an example of an update of the customer delivery destination-specific product unit price master 106c, which is updated based on the temporary master 106a in Fig. 11A. The second line shows a record created based on the revised estimate.

[0101] 11C is a diagram showing an example of updating the route master 106f. Since the same record already exists in the route master 106f, it is overwritten and updated.

[0102] (Using the Route Master and Unit Price Master) An image of how the route master and unit price master are used on the order entry screen will be described with reference to Figs. 12 and 13. Fig. 12 is a diagram showing an example of the display of the order entry screen. Fig. 13(A) is a diagram showing an example of the display of the route search screen, and Fig. 13(B) is a diagram showing an example of data in the customer delivery destination-specific product unit price master 106c. The screen display control unit 102e controls the display of the order entry screen, for example, as follows.

[0103] As shown in FIG. 12, the order input screen has a header area for specifying the business establishment, order date, shipping date, expected sales date, customer, person in charge, and delivery destination, a route search button for displaying a route search screen for selecting a route from the route master 106f, and a details area for specifying details such as the line number, order category, quantity, description, product, unit price, amount, and supplier.

[0104] When the route search button is pressed, a route search screen such as that shown in FIG. 13(A) is displayed. On the route search screen, a list of data from the route master 106f is displayed, and the person in charge selects a route. The selected route (customer, delivery destination, supplier, product) is displayed on the order input screen. When the person in charge enters the "quantity" in the details area, the "unit price" and "amount (unit price x quantity)" for the applicable start date based on the "order date" from the unit price master corresponding to the selected route are displayed in the details area.

[0105] In the example shown in the figure, the route of the first line of customer "TK001", delivery destination "NOU001", supplier "-", and product "Product A" is selected on the route search screen, and customer "TK001", delivery destination "NOU001", and product "Product A" are displayed on the order entry screen. When the quantity "1 case" is entered in the details area, the unit price "¥1,000" of the record with the applicable start date "2022 / 5 / 1" corresponding to the order date "2022 / 5 / 1" is obtained from the customer delivery destination product unit price master 106c (because customer "TK001", delivery destination "NOU001", and supplier "-") corresponding to the selected route, and the unit price "¥1,000" and the amount "¥1,000 (=¥1,000 x 1)" are displayed in the details area.

[0106] In this way, by searching the route, the person in charge of data entry can save the trouble of inputting each client, and by selecting the route, information including the product is set on the screen. After that, by inputting the quantity, the unit price of the target product is set, so data entry can be made more efficient.

[0107] [Function to prevent loss of order opportunities by product] Next, the unit price estimate management device 100 of the embodiment manages the number of days that have passed since the last order date for each business partner and each product, making it possible to prevent the loss of business opportunities and to maintain and improve business transactions (function to prevent the loss of order opportunities by product in the trade).

[0108] Specifically, the person in charge inputs a quotation for a customer via a quotation input screen displayed by the screen display control unit 102e as shown in Fig. 14. Fig. 15 shows the details input screen of this quotation input screen. As can be seen from Fig. 15, the details input screen has input fields for the line number, transaction type, product code, quantity, etc., as well as an input field for "order interval days." The person in charge inputs the number of days between orders for the product quoted in the "order interval days" input field.

[0109] The number of days between orders is the number of days between receiving an order for a product from a customer and the next order for the same product. In the example of Figure 15, "60 days" is entered as the number of days between orders.

[0110] When the quotation is input in this manner, the data generation unit 102h generates quotation data shown in Fig. 16 based on the input contents on the quotation input screens shown in Fig. 14 and Fig. 15, and stores it in the storage unit 2. As can be seen from Fig. 16, the quotation data includes the quotation number, line number, transaction type, office code, quotation date, person in charge code, customer code, delivery destination code, supplier code, product code, quantity, unit price, amount, as well as the "order interval days" input on the quotation detail input screen shown in Fig. 15. The quotation data in the first line record in Fig. 15 is quotation data in which the order interval days of "60 days" has been input.

[0111] Furthermore, the master update unit 102d adds the "order interval days" input on the quotation detail input screen to the above-mentioned route master 106f indicating the trade flow. In this case, the route master 106f is configured to include the order interval days as well as the serial number, transaction category, customer code, delivery destination code, supplier code, and product code. The first line in Fig. 17 is a record of the route master 106f in which the order interval days of "60 days" has been input.

[0112] Next, the data generation unit 102h generates commercial transaction performance data for displaying the order performance table by commercial product shown in FIG. 18 based on the route master 106f in which the "number of days between orders" shown in FIG. 19 is registered, and the customer master 106h shown in FIG. 20, and stores this in the commercial product performance work 106W.

[0113] The commercial transaction performance data includes partial data corresponding to the route master 106f in which the "order interval days" shown in FIG. 18(a) is registered, partial data shown in FIG. 18(b) including the latest order date detected from the order data shown in FIG. 21, the number of days since the latest order date, which is the number of days since the latest order date until the current date, and the number of days since the order interval, which is the date obtained by subtracting the number of days since the order interval from the number of days since the order interval.

[0114] The commercial transaction performance data also includes partial data shown in FIG. 18(c), which includes the results of an analysis of the cause of the number of days since order exceeded the number of days between orders, specific information (order opportunity loss warning) identifying other staff members who handle the same product as the product for which the cause analysis was performed, factor data indicating the commercial transaction performance data that was the subject of the cause analysis, and order opportunity suggestion data (order opportunity available) indicating other products similar to the product for which the cause analysis was performed.

[0115] (Details of the operation of generating the order performance table by commercial product) The operation of generating an order performance table by commercial product based on such commercial transaction performance data will be described in detail. First, the person in charge specifies the display of the display specification screen for the order performance table by commercial product. When this specification is made, the screen display control unit 102e displays the display specification screen for the order performance table by commercial product shown in Fig. 22 via the output device 114. The person in charge inputs, into this display specification screen, a base date that is the date used as the basis for calculating the number of days since order and the number of days since order, and a data update category that indicates whether or not to update the commercial product performance worksheet 106W with the commercial transaction performance data for the base date.

[0116] FIG. 22 shows an example in which "June 2, 2022" is entered as the base date and "1: Update" is entered as the data update category. After entering the base date and data update category, the person in charge operates the "Output" button shown in FIG.

[0117] When the "Output" button is operated, the number of days elapsed detection unit 102f detects the number of days since the last date of a transaction with a customer to the current date, based on the order data shown in Fig. 21. For example, in the case of a product with product code "SH01" in Fig. 21, orders were placed on "May 16, 2023" and "May 5, 2023" as shown by the arrows, so "May 16, 2023" is detected as the most recent date.

[0118] The transaction interval number of days detection unit 102g detects the number of days elapsed between orders, which is the difference between the number of days elapsed between orders stored in the route master 106f and the detected number of days elapsed between orders.

[0119] The data generation unit 102h generates commercial transaction performance data for displaying the order performance table by commercial product shown in Figures 23(a) to 23(c), which includes the route master 106f shown in Figure 19, the customer master 106h shown in Figure 20, the number of days between orders, the latest order date, the number of days since order, and the number of days since order, and stores the data in the commercial transaction performance work 106W.

[0120] Here, when "0: Do not update" is specified as the data update category on the display designation screen of the order performance table by commercial flow product shown in Fig. 22, the output control unit 102k outputs the commercial transaction performance data via the output device 114 without updating the commercial flow product-specific performance work 106W with the commercial transaction performance data shown in Fig. 23(a) to Fig. 23(c). As a result, the order performance table by commercial flow product corresponding to the commercial transaction performance data shown in Fig. 23(a) to Fig. 23(c) is displayed (or may be printed out).

[0121] The person in charge sends the transaction performance data corresponding to the outputted order performance table by commercial product to the sales manager's terminal device 420 to notify the superior of the transaction status, or passes the printed out order performance table by commercial product to the superior to notify the superior of the transaction status.

[0122] In contrast, when "1: Update" is specified as the data update category on the display designation screen of the order performance table by commercial product shown in Fig. 22, the output control unit 102k updates the commercial product performance work 106W with the commercial transaction performance data shown in Fig. 23(a) to Fig. 23(c). Note that at this stage, the output control unit 102k updates the cause to factor route master shown in Fig. 23(c) (= the data showing the analysis results of the cause) by leaving it blank (no data), for example, as null data (Null).

[0123] In the case of the commercial transaction performance data shown in Fig. 23, the commercial transaction performance data of the record in the second row of Fig. 23(b) is detected by the commercial transaction interval elapsed days detection unit 102g as the number of days since order exceeds the number of days since order by about 10 days (number of days since order interval = +10 days). In this way, when the commercial transaction interval elapsed days detection unit 102g detects that the number of days since order exceeds the number of days since order, the communication control unit 102m generates notification data (e.g., email, etc.) indicating that the number of days since order exceeds the number of days since order, and transmits it to the sales manager terminal device 420, etc. via the communication interface unit 104 and the network 300.

[0124] When the supervisor receives the notification data via the sales supervisor terminal device 420, the supervisor analyzes the cause of the order elapsed days exceeding the order interval days based on the business transaction performance data shown in Figure 23, which is pointed out as a problem in the notification data. As an example, the cause is coded as follows:

[0125] A) Unrecorded B) Insufficient confirmation of orders from customers by staff C) A decline in customer demand for products. C-1) Orders from competitors C-2) No need to purchase other products due to orders C-3) No need to purchase products for business purposes C-4) Shipment not possible due to supplier

[0126] The superior returns the analysis result to the unit price estimate management device 100 via the sales superior terminal device 420. As an example, it is assumed that the superior returns the analysis result "C-2) No purchase required due to receipt of order for other product." The communication control unit 102m of the unit price estimate management device 100 acquires this analysis result via the communication interface unit 104.

[0127] In this way, when the person in charge obtains the analysis result from the superior, he / she inputs the obtained analysis result "C-2) Purchase unnecessary due to order of other product" into the "Cause" input field of the screen for inputting the cause of the results by commercial product, as shown in Figure 24. At the same time, the person in charge inputs the row number and base date of the commercial transaction results data for which the cause analysis was performed into each input field of the screen for inputting the cause of the results by commercial product.

[0128] The commercial transaction performance data for which the cause was analyzed is the record in the second row of FIG. 23(a), and is commercial transaction performance data with a base date of "June 20, 2023", a customer code of "T001", a delivery destination code of "N001", a supplier code of "S001", a product code of "SH02", and an order interval of "20 days". The number of this commercial transaction performance data on the route master 106f is "4" as shown in FIG. 19. Therefore, the person in charge enters "4" in the "serial number" input field on the commercial flow product-specific performance cause input screen. This makes it possible to identify the commercial transaction performance data for which the analysis of the cause of the order elapsed days exceeding the order interval days was performed.

[0129] Next, the data generating unit 102h inputs the analysis result "C-2) No purchase required due to order of other product" input in the "Cause" input field on the commercial product-specific performance cause input screen into the "Cause" input field of the record of commercial transaction performance data that was the subject of the analysis, as shown in FIG. 25(c). That is, the record of commercial transaction performance data that was the subject of the analysis is the record indicated by the arrow (B) in FIG. 25(a) to FIG. 25(c). The data generating unit 102h generates commercial transaction performance data by inputting the analysis result of "C-2" replied by the superior as the "Cause" of the record indicated by the arrow (B).

[0130] The product code of the product that was the subject of the analysis is "SH02". As shown by the arrows (D) and (F) in Fig. 25(a) and Fig. 25(b), the product with the product code "SH02" is also handled by the staff of "TA002" and the staff of "TA003". For this reason, it is preferable to notify the staff of "TA002" and the staff of "TA003" that the business transaction situation has become such that the number of days since the order of the product "SH02" handled by the staff of "TA001" has exceeded the number of days between orders, and to call their attention so that the same inconvenience does not occur.

[0131] For this reason, the data generating unit 102h generates commercial transaction performance data in which a "○" mark (an example of specific information) is added to the input field for the order opportunity loss warning of the person in charge who handles the same product as the product whose order elapsed days have exceeded the order interval days, as shown by the arrows (D) and (F) in Fig. 25(c). This enables the person in charge of "TA002" and the person in charge of "TA003" to take measures such as making sales to the customer, and prevents the inconvenience of losing order opportunities.

[0132] Furthermore, when the data generating unit 102h marks the input field for the order opportunity loss warning with a circle, it generates commercial transaction performance data by marking the number "4" (an example of factor data) in the input field of the factor route master as shown by the arrows (D) and (F) in FIG. 25(c). This data with the number "4" is the commercial transaction performance data that was the factor in the analysis as described above. In this way, by inputting the "serial number" of the commercial transaction performance data that was the factor in the analysis in the input field of the factor route master, it is possible to easily identify the commercial transaction performance data that was the factor in the analysis.

[0133] The output control unit 102k displays the commercial transaction performance data thus generated via the output device 114. This makes it possible to easily grasp the number of days that have passed since the previous order date, thereby preventing the loss of commercial transaction opportunities and maintaining and improving commercial transactions.

[0134] In addition, the results of the analysis of the order status are displayed in a table of order performance by product in the trade flow, which alerts each person in charge to the risk of losing business opportunities, thereby making it possible to significantly prevent the loss of business opportunities.

[0135] Next, as shown in Figure 26, the same sequential number (4), reference date (June 2, 2023), and cause (C-2) as above are specified, along with another product (SH01) that is similar to the product (SH02) for which the cause was analyzed.

[0136] In this case, the other product (SH01) similar to the product (SH02) for which the cause was analyzed is a product handled by the staff with the staff codes "TA001", "TA002" and "TA003", as shown by the arrows (A), (C) and (E) in Figures 27(a) and 27(b). The fact that it is a product similar to the product (SH02) for which the cause was analyzed means that there is a possibility that it will be in the same unforeseen business transaction situation as the product (SH02) for which the cause was analyzed. For this reason, it is preferable to encourage each staff member who handles similar products to consider a response policy for the customer.

[0137] For this reason, the data generation unit 102h generates commercial transaction performance data in which a “○” mark (an example of order opportunity suggestion data) is added to the “order opportunity available” input field of the record of another product (SH01) that is similar to the product (SH02) for which cause analysis was conducted, as shown by the arrows (A), (C), and (E) in Figures 27(a) and 27(b).

[0138] This will encourage each person in charge of handling a product (SH01) similar to the product (SH02) for which the cause was analyzed to consider how to respond to the customer in question, thereby improving the chances of receiving orders.

[0139] [Effects of the embodiment] As is clear from the above explanation, the unit price estimate management device 100 of the embodiment is equipped with at least a unit price master for storing data on the items of customer, application start date, product, quantity which is the unit of unit price, and unit price in association with each other, a temporary master 106a for storing data for updating the unit price master, a unit price estimate input section 102a for inputting quotation data including the items of quotation number, quotation date, scheduled order date, scheduled sales date, customer, delivery destination, supplier, application start date, product, quantity, unit price, and amount, an approval processing section 102c for updating the temporary master 106a based on the approved quotation data when the input quotation data is approved, and a master updating section 102d for updating the unit price master based on the updated temporary master 106a, thereby making it possible to improve the efficiency of unit price estimate work.

[0140] In addition, since the route master 106f stores the number of days between orders, the number of days that have passed since the previous order date can be easily ascertained, which makes it possible to prevent the loss of business opportunities and to maintain and improve business transactions.

[0141] In addition, by analyzing the order status and displaying the results of this analysis in a table of order performance by product in the trade flow, it is possible to alert each person in charge to the risk of losing business opportunities, thereby making it possible to significantly prevent the loss of business opportunities.

[0142] [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.

[0143] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby making it possible to contribute to Goals 12, 13, and 15 of the SDGs.

[0144] Furthermore, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

[0145] [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.

[0146] 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 known methods.

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

[0148] Moreover, with regard to unit price estimate management device 100, each of the components shown in the figure is merely a functional concept, and does not necessarily have to be physically configured as shown in the figure.

[0149] For example, the processing functions of the unit price estimate management device 100, particularly the control unit 102 and each processing function performed by the control unit 102, may be realized in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded in a non-transient computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the unit price estimate management 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. This computer program is executed by being loaded into a RAM, and constitutes the control unit 102 in cooperation with the CPU.

[0150] In addition, the unit price estimate management program of this unit price estimate management device 100 may be stored in another server device connected to the unit price estimate management device 100 via any network, and it is also possible to download all or part of it as needed.

[0151] The unit price estimate management program for executing the process described in the present embodiment may be stored in a non-transient computer-readable recording medium, or may be configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical Disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) Disc.

[0152] Moreover, a "program" is a data processing method written in any language or description method, and may be in any form, 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 cooperation with a separate program, such as an OS, to achieve its function. Note that well-known configurations and procedures can be used for the specific configuration and reading procedure for reading a recording medium in the unit price estimate management device 100 shown in the embodiment, as well as the installation procedure after reading.

[0153] The memory unit 2 is a storage means such as a memory device such as RAM or ROM, a fixed disk device such as a hard disk, a flexible disk, or an optical disk, and stores various programs, tables, databases, and web page files used for various processes and providing websites.

[0154] The unit price estimate management device 100 may be configured as an information processing device such as a known personal computer device or a workstation, or may be configured as an information processing device to which any peripheral device is connected. The information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

[0155] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be functionally or physically distributed and integrated in any unit according to 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. [Industrial Applicability]

[0156] The present invention is suitable for application to order management for business partners, and is particularly suitable for application to order management for companies that handle many business partners and products, such as chemical trading companies. [Explanation of symbols]

[0157] 100 Unit price estimate management device 102 Control section 102a Unit price estimate input section 102b Workflow processing section 102c Approval Processing Unit 102d Master Update Section 102e Screen display control unit 102f Elapsed days detection unit 102g Transaction interval detection unit 102h Data generation section 102k Output control section 102m Communication control section 104 Communication interface section 106 Storage section 106a Temporary Master 106b Customer-specific product price master 106c Customer delivery destination product price master 106d Customer / Supplier Product Price Master 106e Customer delivery destination supplier product unit price master 106f Route Master 106g Quote Data File 106h Customer master 106W Product-specific sales results work 108 Input / Output Interface Section 112 Input Devices 114 Output Device 200 Server device 300 Network 410 Salesperson terminal equipment 420 Sales Manager Terminal Device

Claims

1. a number-of-days detection unit for detecting the number of days that have passed since a transaction was made with a customer to a current date based on the transaction data; a transaction interval number of days detection unit that detects a transaction interval number of days that is the difference between a transaction interval number of days that is the interval between transactions with the customer that is stored in advance in a storage unit and the detected number of days that have passed since the transaction; a data generating unit that generates, for each transaction target, transaction performance data including at least a customer, the number of days since the transaction, the number of days between the transactions, the number of days since the transaction, and the date on which the transaction was conducted with the customer; an output control unit that outputs the commercial transaction performance data via an external device; A business support device having the above configuration.

2. the data generating unit generates notification data indicating that the number of days elapsed between commercial transactions has exceeded the number of days elapsed between commercial transactions when the number of days elapsed between commercial transactions detecting unit detects that the number of days elapsed between commercial transactions has exceeded the number of days elapsed between commercial transactions; Further comprising a communication control unit that controls the communication unit so as to transmit the generated notification data to a terminal device of a person in charge; 2. The business support device according to claim 1,

3. the communication control unit acquires, via the communication unit, an analysis result of the reason why the number of days elapsed since the commercial transaction has exceeded the number of days between commercial transactions, the analysis result being returned via the terminal device by the person in charge performing an analysis based on the notification data; the data generation unit generates the commercial transaction performance data to which the acquired analysis result of the cause is added; 3. The business support device according to claim 2,

4. the data generation unit generates the commercial transaction performance data to which is added specific information that identifies other personnel who handle the same commercial transaction object as the commercial transaction object for which the cause analysis was performed; 4. The business support device according to claim 3,

5. the data generating unit generates the commercial transaction performance data to which, together with the specific information, factor data indicating the commercial transaction performance data that was the subject of the cause analysis is added; 5. The business support device according to claim 4,

6. the data generation unit generates the commercial transaction performance data to which order opportunity suggestion data indicating the specified other commercial transaction object is added when another commercial transaction object similar to the commercial transaction object for which the cause analysis was performed is specified; 6. The business support device according to claim 5,

7. an elapsed days detection step in which an elapsed days detection unit detects the number of days that have elapsed since a transaction was made with a customer to a current date based on the transaction data; a transaction interval elapsed days detection step in which a transaction interval elapsed days detection unit detects a transaction interval elapsed days, which is the difference between a transaction interval elapsed days, which is the interval between transactions with the customer and which is stored in advance in a storage unit, and the detected transaction elapsed days; a data generating step in which a data generating unit generates, for each commercial transaction target, commercial transaction performance data including at least a customer, the number of days since the commercial transaction, the number of days between the commercial transactions, the number of days since the commercial transaction, and the date on which the commercial transaction was conducted with the customer; an output control step in which an output control unit outputs the commercial transaction performance data via an external device; A business support method having the above-mentioned features.

8. Computer, a number-of-days detection unit for detecting the number of days that have passed since a transaction was made with a customer to a current date based on the transaction data; a transaction interval number of days detection unit that detects a transaction interval number of days that is the difference between a transaction interval number of days that is the interval between transactions with the customer that is stored in advance in a storage unit and the detected number of days that have passed since the transaction; a data generating unit that generates, for each transaction target, transaction performance data including at least a customer, the number of days since the transaction, the number of days between the transactions, the number of days since the transaction, and the date on which the transaction was conducted with the customer; An output control unit that outputs the commercial transaction performance data via an external device. A business support program that functions as a

Images