Business support device, business support method, and business 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 Art

[0002] Patent Document 1 (Japanese Patent Application Laid-Open No. 2009-288886) discloses a notice server that can quickly and accurately send a business notice to a person in charge in a certain manner that eliminates personal attributes without directly contacting the person in charge from the administrator, and can make the person in charge aware of a delay in delivery date or the like.

[0003] This notice server determines whether or not it meets the notice generation conditions using business data and a management master based on the notice execution timing. When it is determined that the notice generation conditions are met, notice data including a condition comment or the like is created, and the notice data is distributed or displayed based on the notice destination and the notice method. As a result, it is possible to make the person in charge aware of a delay in delivery date or the like.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Here, in the business of delivering ordered products, it is often the case that products for which a unit price estimate has been made are repeatedly ordered. However, as the number of business partners and the number of handled products increases, it becomes difficult to individually manage the business transaction status with each business partner. If the management of the business transaction status with each business partner is neglected, there will be an inconvenience that the opportunity for business transactions with the business partner is lost.

[0006] This invention has been made in view of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that enable the management of business transaction status with business partners and the maintenance and improvement of business transactions with business partners. [Means for solving the problem]

[0007] To solve the above-mentioned problems and achieve the objective, the business support device according to the present invention includes: an elapsed days detection unit that detects the number of days elapsed from the date a business transaction was conducted with a customer to the current date based on business transaction data; a business transaction interval elapsed days detection unit that detects the number of days that is the difference between the business transaction interval, which is the interval between business transactions with a customer stored in a storage unit in advance, and the detected number of days elapsed in business transactions; a data generation unit that generates business transaction performance data for at least one business transaction target, including the customer, the number of days elapsed in business transactions, the number of days elapsed in business transactions, the number of days elapsed in business transaction intervals, and the date a business transaction was conducted with the customer; and an output control unit that outputs the business transaction performance data via an external device.

[0008] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support method according to the present invention comprises: an elapsed days detection step in which a day elapsed detection unit detects the number of days elapsed from the date a business transaction was conducted with a customer to the current date based on business transaction data; a business transaction interval elapsed days detection step in which a business transaction interval elapsed days detection unit detects the number of days elapsed from a business transaction interval, which is the number of days that is the difference between the number of days elapsed from a business transaction with a customer, which is the interval between business transactions with a customer, and the number of days elapsed from a business transaction interval, which is the number of days that was detected; a data generation step in which a data generation unit generates business transaction performance data including, for at least one business transaction target, the customer, the number of days elapsed from a business transaction, the number of days elapsed from a business transaction interval, and the date a business transaction was conducted with the customer; and an output control step in which an output control unit outputs the business transaction performance data via an external device.

[0009] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support program according to the present invention enables the computer to function as: an elapsed days detection unit that detects the number of days elapsed from the date a business transaction was conducted with a customer to the current date based on business transaction data; a business transaction interval elapsed days detection unit that detects the number of days that is the difference between the business transaction interval, which is the interval between business transactions with a customer stored in advance in a storage unit, and the detected number of days elapsed from business transactions; a data generation unit that generates business transaction performance data for at least one business transaction target, including the customer, the number of days elapsed from business transactions, the number of days elapsed from business transactions, the number of days elapsed from business transaction intervals, and the date a business transaction was conducted with the customer; and an output control unit that outputs the business transaction performance data via an external device. [Effects of the Invention]

[0010] This invention allows for the management of business transaction status with business partners and enables the maintenance and improvement of business transactions with business partners. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a block diagram showing the hardware configuration of the unit price estimation management device according to the embodiment. [Figure 2] Figure 2 shows the update matrix, which is a pattern for the master update process. [Figure 3] Figure 3 is a flowchart illustrating the overall processing flow of the control unit of the unit price estimation management device. [Figure 4] Figure 4 shows an example of sample data to illustrate a specific example of the processing performed by the control unit of the unit price estimation management device. [Figure 5] Figure 5 shows an example of sample data to illustrate a specific example of the processing performed by the control unit of the unit price estimation management device. [Figure 6] Figure 6 shows an example of sample data to illustrate a specific example of the processing performed by the control unit of the unit price estimation management device. [Figure 7] Figure 7 shows an example of sample data to illustrate a specific example of the processing performed by the control unit of the unit price estimation 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 device. [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 the estimate input screen (detail input screen). [Figure 16] FIG. 16 is a diagram showing an example of estimate data. [Figure 17] FIG. 17 is a diagram showing an example of the route master. [Figure 18] FIG. 18 is a diagram showing an example of the order receipt performance table by business flow for each product. [Figure 19] FIG. 19 is a diagram showing partial data generated based on the route master in the order receipt performance table by business flow for each product. [Figure 20] FIG. 20 is a diagram showing an example of the customer master. [Figure 21] FIG. 21 is a diagram showing an example of the order receipt data. [Figure 22] FIG. 22 is a diagram showing the display specification screen of the order receipt performance table by business flow for each product. [Figure 23]Figure 23 shows an example of a commercial product-specific order performance table generated using commercial transaction performance data of the commercial product-specific performance work updated on the specified reference date, when "Update" is selected in the data update category on the display specification screen for the commercial product-specific order performance table. [Figure 24] Figure 24 shows an example of a commercial product-specific performance cause input screen where the results of the supervisor's cause analysis are entered. [Figure 25] Figure 25 shows an example of a sales performance table by product in the commercial flow, where the results of the supervisor's cause analysis have been entered, along with identifying information (order opportunity loss warning) that identifies other personnel handling the same commercial transaction as the one analyzed, and factor data has been added. [Figure 26] Figure 26 shows an example of a commercial product-specific performance cause input screen, which includes the results of the supervisor's cause analysis, along with input for products similar to the product that was the subject of the cause analysis (other products). [Figure 27] Figure 27 shows an example of a sales performance table by product in the commercial flow, with the results of the supervisor's cause analysis, identifying information (warning of lost sales opportunity) that identifies other personnel handling the same commercial transaction subject as the one analyzed, factor data, and similar products (other products) to the product that was the subject of the cause analysis added. [Modes for carrying out the invention]

[0012] Below, an embodiment in which the present invention is applied to a unit price estimation management device for estimating unit prices will be described in detail with reference to the drawings, as an example. However, the present invention is not limited to the following embodiment.

[0013] [overview] Today, unit price estimates for goods or services are made by sales representatives using various communication tools such as spreadsheet software, email, and telephone, which are used by the client. As a result, it has become difficult for managers to grasp the status of unit price estimates, leading to transactions being conducted at unintended unit prices and resulting in lost profits.

[0014] Furthermore, because the results agreed upon in the contract were circulated in writing, and the information systems staff separately registered various master data, errors in registering the master data and time lags occurred. This resulted in inconveniences such as the master data not being created when administrative staff wanted to register something, and frequent errors due to manual input.

[0015] Therefore, in this embodiment, the unit price estimate management device allows sales representatives to register unit price estimates for customers, etc., by inputting estimates, and when approved by their superiors, it creates various unit price masters (customer-specific product unit price master, customer-delivery destination-specific product unit price master, customer-supplier-specific product unit price master, customer-delivery destination-specific product unit price master) and route masters based on the registered estimates.

[0016] This allows contract details to be registered as quotation information, enabling centralized management and sharing of quotation information. Furthermore, since a unit price master is automatically created after a supervisor approves the contract details, the unit price quotation process can be streamlined. Additionally, because the system automatically allocates and registers the updated unit price master based on the registration information of each quotation, it not only streamlines unit price master registration but also strengthens control and improves overall efficiency, including data entry by administrative staff, as approved quotation information is reflected.

[0017] In a chemical trading company, for example, it is common to repeatedly receive orders for products for which unit price estimates have been provided. As the number of clients and products handled increases, it becomes difficult to individually manage the business relationship with each client. Therefore, if a client that previously ordered products from our company then orders them from another company, the company may not notice this situation until it is too late, resulting in the loss of business opportunities with that client.

[0018] Therefore, the unit price estimation management device of this embodiment makes it easy to grasp the order frequency for each product in the commercial flow by registering the order interval in days at the time of unit price estimation in the route master.

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

[0020] [Configuration of the Unit Price Estimation Management System] Figure 1 is a block diagram showing the hardware configuration of the unit price estimation management device 100 according to the embodiment. The unit price estimation management device 100 is a workstation or a commercially available desktop personal computer, etc.

[0021] The unit price estimation management device 100 comprises a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. Each part of the unit price estimation management device 100 is connected to communicate via any communication path.

[0022] The communication interface unit 104 connects the unit price estimation management device 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines. The communication interface unit 104 has the function of communicating data with other devices via communication lines. Here, the network 300 has the function of connecting the unit price estimation 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 communicate data with the server device 200 via the network 300.

[0023] The sales representative terminal device 410 is a terminal device used by sales department personnel and is configured to provide access to the unit price estimate management device 100.

[0024] The sales manager terminal device 420 is a terminal device used by sales managers and is configured to provide access to the unit price estimation management device 100.

[0025] The input / output interface unit 108 is connected to an input device 112 and an output device 114. The output device 114 can be a monitor (including a home television), as well as a speaker or a printer. The input device 112 can be a keyboard, mouse, microphone, or a monitor that works in conjunction with the mouse to provide pointing device functionality.

[0026] The memory unit 106 stores various databases, tables, and files. The memory unit 106 also stores computer programs that work in cooperation with the OS (Operating System) to give instructions to the CPU (Central Processing Unit) to perform various processes. As the memory 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, and optical disks can be used.

[0027] Furthermore, this memory unit 106 includes, respectively, a temporary master 106a, a customer-specific product unit price master 106b, a customer-delivery destination-specific product unit price master 106c, a customer-supplier-specific product unit price master 106d, a customer-delivery destination-supplier-specific product unit price master 106e, a root master 106f, and an estimate data file 106g. The customer-specific product unit price master 106b, the customer-delivery destination-specific product unit price master 106c, the customer-supplier-specific product unit price master 106d, and the customer-delivery destination-supplier-specific product unit price master 106e are collectively referred to as the "unit price master".

[0028] Temporary master 106a is a master for updating the unit price master, and can consist of tables such as a table that associates and registers the following: quotation number, row number, quotation type (inventory quotation, direct shipment quotation), customer, delivery destination, supplier, start date of application, end date of application, flag for immediate master reflection after approval, product, quantity, and unit price.

[0029] The customer-specific product unit price master 106b can be composed of tables that associate customer, start date, end date, product, quantity, and unit price.

[0030] The customer-delivery-location product unit price master 106c can be composed of tables that associate customer, delivery location, start date, end date, product, quantity, and unit price.

[0031] The customer / supplier-specific product unit price master table 106d can be composed of tables that associate customer, supplier, start date, end date, product, quantity, and unit price.

[0032] The Customer, Delivery Destination, and Supplier-Specific Product Unit Price Master 106e can be composed of tables (storage areas) that register customer, delivery destination, supplier, start date, end date, product, quantity, and unit price in association with each other.

[0033] Route Master 106f is a master database for managing commercial flows and can consist of tables that associate and register customers, delivery destinations, suppliers, and products.

[0034] The estimate data file 106g is a table (storage area) for storing estimate data. The estimate data may include estimate number, line number, estimate type (inventory estimate, direct shipment estimate), business location, estimate date, planned order date, planned sales date, person in charge, customer, delivery destination, supplier, unit price update type (0: do not update, 1: update) which specifies whether or not to update the temporary master 106a (unit price master), start date of application, end date of application, flag for immediate master reflection after approval, product, quantity, unit price, amount, and detail description.

[0035] The "Immediate Master Update After Approval" flag allows you to choose whether to update the unit price master immediately after approval or at a time of your choosing. If the "Immediate Master Update After Approval" flag is set to "Update Immediately," the unit price master will be updated immediately after approval. If it is set to "Do not update immediately," the unit price master will be updated at a time of your choosing.

[0036] Furthermore, the memory unit 2 is equipped with a customer master 106h and a sales flow / product-specific performance work 106W. The customer master 106h stores each customer and the person in charge of each customer, each associated with the customer (see Figure 20). The sales flow / product-specific performance work 106W stores work data for a sales flow / product-specific order performance table that displays a list of order performance by sales flow and product. More details will be described later.

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

[0038] The control unit 102 is configured to access the following files stored in the storage unit 106: temporary master 106a, customer-specific product unit price master 106b, customer-delivery destination-specific product unit price master 106c, customer-supplier-specific product unit price master 106d, customer-delivery destination-supplier-specific product unit price master 106e, route master 106f, quotation data file 106g, etc. Note that these masters and files may be located in other locations (for example, on the server device 200), as long as the control unit 102 can access them.

[0039] The control unit 102 operates based on the unit price estimate management program (including the business support program) stored in the storage 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] Furthermore, the control unit 102 operates based on the unit price estimation management program and functions as an elapsed days detection unit 102f, a commercial transaction interval elapsed days 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 estimation input section 102a to data generation section 102h, output control section 102k, and communication control section 102m of the control unit 102 are described as being implemented in software by the unit price estimation management program. However, some or all of the unit price estimation input section 102a to data generation section 102h, output control section 102k, and communication control section 102m of the control unit 102 may be implemented in hardware. In either case, the same effects as described later can be obtained.

[0042] The unit price estimate input unit 102a provides an estimate input screen in response to access from the sales representative terminal device 410, and registers estimate data including estimate number, estimate date, expected order date, expected sales date, customer, delivery destination, supplier, effective start date, product, quantity, unit price, and amount into the estimate data file 106g in response to the sales representative's operations on the estimate input screen of the sales representative terminal device 410. Once the sales representative has registered the estimate data, they apply for approval of the estimate data using the workflow.

[0043] The workflow processing unit 102b provides a workflow environment. For example, in response to access from the sales representative terminal device 410, the workflow processing unit 102b provides a workflow application screen. When the sales representative specifies the quotation data and approval route (e.g., sales manager) on the workflow application screen, the workflow processing unit 102b circulates the data through the specified approval route and notifies the approval route, where a decision is made to approve or reject the quotation data (e.g., by the sales manager on the sales manager terminal device 420).

[0044] The approval processing unit 102c, upon approval of the estimate data, performs the following actions based on the said estimate data: Update temporary master 106a.

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

[0046] The estimate data (temporary master 106a) includes an approval-post-master immediate reflection flag that specifies whether or not to immediately reflect the data in the unit price master after approval. The master update unit 102d updates the unit price master immediately after updating the temporary master 106a if the approval-post-master immediate reflection flag is set to "reflect immediately," and updates the unit price master at any time after updating the temporary master 106a if it is set to "do not reflect immediately."

[0047] Figure 2 shows an update matrix, which is a pattern for master update processing. Referring to Figure 2, the update patterns for the unit price master will be explained. The master update unit 102d selects the unit price master to be updated (customer-specific product unit price master 106b, customer / delivery destination-specific product unit price master 106c, customer / supplier-specific product unit price master 106d, customer / delivery destination-specific product unit price master 106e) based on the quotation category (inventory quotation, direct shipment quotation) of the quotation data (temporary master 106a) and the presence or absence of customers, delivery destinations, and suppliers. In any pattern, the root master 106f is always updated.

[0048] If the quotation category is "Inventory Quotation," and the customer is "○: Data Available," the delivery destination is "-: Data Not Available," and the supplier is "-: Data Not Available," update the customer-specific product unit price master 106b.

[0049] If the quotation category is "Inventory Quotation," and the customer is "○: Data Available," the delivery destination is "○: Data Available," and the supplier is "-: Data Not Available," then update the customer / delivery destination-specific product unit price master 106c.

[0050] If the quotation category is "Direct Quotation," and the customer is "○: Data Available," the delivery destination is "-: Data Not Available," and the supplier is "○: Data Available," then update the customer / supplier-specific product unit price master 106d.

[0051] If the quotation category is "Direct Quotation," and the customer, delivery destination, and supplier are all listed as "○: Data Available," then update the customer, delivery destination, and supplier-specific product unit price master 106e.

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

[0053] In other words, to explain again, the unit price estimate input unit 102a inputs estimate data that includes the following items: estimate number, estimate date, planned order date, planned sales date, customer, delivery destination, supplier, effective start date, product, quantity, unit price, and amount.

[0054] The approval processing unit 102c updates the temporary master based on the approved estimate data when the entered estimate data is approved. The master update unit 102d updates the various unit price masters 106b to 106e based on the updated temporary master.

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

[0056] Furthermore, the estimate data includes a post-approval master immediate reflection flag that specifies whether or not to immediately reflect the data in the various unit price masters 106b to 106e after approval. If the post-approval master immediate reflection flag is set to "reflect immediately", the master update unit 102d immediately updates the various unit price masters 106b to 106e after updating the temporary master.

[0057] Furthermore, the quotation data includes quotation categories that specify inventory quotations when inventory is sent or direct shipment quotations when goods are shipped directly from the supplier. In addition, various unit price masters are provided, including a customer-specific product unit price master 106b for storing data related to customer, effective start date, product, quantity (unit of unit price), and unit price; a customer-delivery destination-specific product unit price master 106c for storing data related to customer, delivery destination, effective start date, product, quantity (unit of unit price), and unit price; a customer-supplier-specific product unit price master 106d for storing data related to customer, supplier, effective start date, product, quantity (unit of unit price), and unit price; and a customer-delivery destination-supplier-specific product unit price master 106e for storing data related to customer, delivery destination, supplier, effective start date, product, quantity (unit of unit price), and unit price.

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

[0059] Furthermore, the master update unit 102d updates the customer-specific product unit price master 106b if the quotation category is "Inventory Quotation", the customer is "Data Available", the delivery destination is "Data Not Available", and the supplier is "Data Not Available".

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

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

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

[0063] Furthermore, the elapsed days detection unit 102f detects the number of days elapsed since the date of the business transaction with the customer, based on the business transaction data. The elapsed days between business transactions detection unit 102g detects the number of days elapsed since the business transaction interval, which is the number of days between business transactions with the customer that is stored in advance in the storage unit (root master 106f: see Figure 17), and the detected number of days elapsed since the business transaction interval.

[0064] The data generation unit 102h generates transaction performance data (see Figures 18(a) to 18(c)) for each transaction, including the customer, the number of days elapsed since the transaction, the number of days between transactions, and the date on which the transaction took place with the customer. The output control unit 102k outputs the transaction performance data via an external device (output device 114).

[0065] Furthermore, if the elapsed days between commercial transactions, which indicates that the number of days elapsed in a commercial transaction has exceeded the number of days between commercial transactions, is detected by the elapsed days between commercial transactions detection unit 102g, the data generation unit 102h generates notification data indicating that the number of days elapsed in a commercial transaction has exceeded the number of days between commercial transactions. The communication control unit 102m controls the communication unit (for example, the communication interface unit 104) to transmit the generated notification data to the terminal device of the person in charge (sales manager terminal device 420).

[0066] Furthermore, the person in charge (sales manager, etc.) analyzes the reason why the number of days elapsed for a 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 via the communication unit (communication interface unit 104). The person in charge inputs the reason why the number of days elapsed for a commercial transaction exceeded the number of days between commercial transactions, as indicated in the acquired analysis results, via the commercial transaction product-specific performance cause input screen. The data generation unit 102h generates commercial transaction performance data with the input reason (e.g., "C-2 (No procurement required due to orders for other products)" in the cause input field of Figure 25(c)) added.

[0067] Furthermore, the data generation unit 102h generates transaction performance data with added identification information (the circles in the records indicated by the arrows in (D) and (F) in Figure 27(c)) that identify other personnel handling the same transaction subject as the one whose cause was analyzed.

[0068] Furthermore, the data generation unit 102h generates commercial transaction performance data that includes this specific information along with factor data indicating the commercial transaction performance data that was the subject of the cause analysis. As will be described later using Figure 24, the person in charge inputs the results of the cause analysis via the commercial transaction product-specific performance cause input screen. At that time, the person in charge enters the "sequence number" on the route master 106f for the product whose cause was analyzed into the "sequence number" input field on the commercial transaction product-specific performance cause input screen in Figure 24. In the example in Figure 24, the number entered in the sequence number input field is "4".

[0069] The "Factor Root Master" column shown in Figure 27(c) is a column that displays factor data. The data generation unit 102h generates commercial transaction data in this "Factor Root Master" column, with the row number of the commercial transaction data that was the subject of the cause analysis (in this example, row "4") entered as the factor data.

[0070] Furthermore, if another commercial transaction target similar to the commercial transaction target for which the cause analysis was performed (for example, another product: SH01 in Figure 26) is specified, the data generation unit 102h generates commercial transaction performance data with added data indicating the opportunity to receive orders (the circle mark "Opportunity to receive orders" in Figure 27(c)) for the specified other commercial transaction target.

[0071] [Unit Price Estimation Management Operation] Next, the unit price estimation management operation of the unit price estimation management device 100 of this embodiment will be described.

[0072] (Overall processing) Figure 3 is a flowchart illustrating the overall processing flow of the control unit 102 of the unit price estimation management device 100. The overall processing flow of the control unit 102 of the unit price estimation management device 100 will be explained with reference to Figure 3.

[0073] In Figure 3, the unit price estimate input unit 102a executes the estimate input process (step S1). Specifically, in the estimate input process, the unit price estimate input unit 102a provides an estimate input screen in response to access from the sales representative terminal device 410, and registers 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, approval-after-master immediate reflection flag, product, quantity, unit price, and amount into the estimate data file 106g in response to the sales representative's operations on the estimate input screen of the sales representative terminal device 410.

[0074] The approval processing unit 102c executes the approval process (step S2). Specifically, in the approval process, if the estimate data is approved, the approval processing unit 102c updates the temporary master 106a based on the estimate data. Upon approval by the supervisor, the temporary master 106a for updating the unit price master is updated.

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

[0076] If the "immediate master update after approval" flag is set to "immediate update", the master update unit 102d updates the unit price master immediately after updating the temporary master 106a. If the "immediate master update after approval" flag is set to "do not update immediately", the unit price master updates at an arbitrary timing after updating the temporary master 106a.

[0077] The master update unit 102d selects the master to update (customer-specific product unit price master 106b, customer / delivery destination-specific product unit price master 106c, customer / supplier-specific product unit price master 106d, customer / delivery destination-specific product unit price master 106e) based on the quotation category (inventory quotation, direct shipment quotation) and the presence or absence of customers, delivery destinations, and suppliers in the quotation data (temporary master 106a). In this way, the master to update is distributed 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 "-: Data Not Available," and the supplier is "-: Data Not Available," update the customer-specific product unit price master 106b. If the quotation category is "Inventory Quotation," and the customer is "○: Data Available," the delivery destination is "○: Data Available," and the supplier is "-: Data Not Available," update the customer / delivery destination-specific product unit price master 106c. If the quotation category is "Direct Shipment Quotation," and the customer is "○: Data Available," the delivery destination is "-: Data Not Available," and the supplier is "○: Data Available," update the customer / supplier-specific product unit price master 106d. If the quotation category is "Direct Shipment Quotation," and the customer is "○: Data Available," the delivery destination is "○: Data Available," and the supplier is "○: Data Available," update the customer / delivery destination-supplier-specific product unit price master 106e.

[0079] (Sample data) Referring to Figures 4 to 13, a specific example of the processing of the control unit 102 of the unit price estimation management device 100 will be explained. Figures 4 to 13 are diagrams showing sample data to illustrate a specific example of the processing of the control unit 102 of the unit price estimation management device 100.

[0080] (S1: Estimate Input Processing) Refer to Figures 4 to 6 to explain a specific example of the quotation input process. The unit price quotation input unit 102a provides a quotation input screen in response to access from the sales representative terminal device 410, and registers 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, approval-after-master immediate reflection flag, product, quantity, unit price, and amount into the quotation data file 106g in response to the sales representative's operations on the quotation input screen of the sales representative terminal device 410.

[0081] Figure 4 shows an example of the main screen display of the estimate input screen, and Figure 5 shows an example of the detail screen display of the estimate input screen. As shown in Figure 4, the main screen of the estimate input screen has a header area for specifying (inputting) the business office, estimate date, planned order date, planned sales date, customer, person in charge, delivery destination, unit price update category, application start date, and application end date, and an area for specifying the details of the unit price estimate, which has a detail area for specifying the line number, estimate category, approval master immediate reflection flag (checked box: reflects immediately, unchecked box: does not reflect immediately), product, supplier, quantity, unit price, amount, and detail description, and a registration button (not shown). When the registration button (not shown) is pressed, estimate data corresponding to the input content on the screen is created and registered in the estimate data file 106g. If data as shown in the examples in Figures 4 and 5 is entered, the estimate data as shown in Figure 6 will be registered.

[0082] When you select a row in the details area (by double-clicking, etc.), a details screen like the one shown in Figure 5 will appear. Enter data on the details screen, and when you press the "Apply" button (not shown), the data will be reflected in the selected row in the details area.

[0083] In the header area, the "Unit Price Update Classification" can be set to either "0: Do not update" or "1: Update". If "1: Update" is selected, the estimated data will be reflected in temporary master 106a. The "Effective Start Date" is the start date for the application of the estimated unit price. The "Effective End Date" is the end date for the application of the estimated unit price and is an optional field.

[0084] In the details area, the "Quotation Category" is set to either "10: Inventory Quotation" or "20: Direct Shipment Quotation," and the unit price master that is updated is determined according to the selected quotation category. "Quantity" sets the unit price for each quantity according to the entered quantity. "Supplier" is valid when the quotation category is "20: Direct Shipment Quotation," but invalid when it is "10: Inventory Quotation" (because inventory quotations are quotations for delivering warehouse inventory to customers / delivery destinations, and suppliers are not involved). If the "Immediate Master Reflection Flag after Approval" is checked, "Immediate Reflection" means that the unit 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 content on the quotation input screen in Figures 4 and 5 above. The quotation data includes the following items: quotation number, line number, quotation category, business location, 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 master data reflection after approval, product, quantity, unit price, amount, and detail description.

[0086] In the example shown in the diagram, the first row contains the following information: Estimate number "MT001", row number "1", estimate type "Inventory estimate", business location "T100", estimate date "2022 / 4 / 1", planned order date "2022 / 5 / 10", planned sales date "2022 / 6 / 30", person in charge "TAN001", customer "TK001", delivery destination "NOU001", supplier "-", unit price update type "update", start date "2022 / 5 / 1", end date "2022 / 12 / 31", immediate master data reflection after approval "yes", product "product A", quantity "1 case", unit price "¥1,000", amount "¥1,000", and detail description "Estimate for new transaction: basic quantity".

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

[0088] Figure 7 shows an example of data in temporary master 106a. Temporary master 106a includes the following fields: estimate number, line number, estimate category, customer, delivery destination, supplier, application start date, application end date, approval-to-master immediate reflection flag, product, quantity, and unit price.

[0089] In the example shown in the diagram, the first row contains the following information: Estimate number "MT001", row number "1", estimate type "Inventory estimate", customer "TK001", delivery destination "NOU001", supplier "-", effective start date "2022 / 5 / 1", effective end date "2022 / 12 / 31", approval post-master immediate reflection flag "Reflect immediately", product "Product A", quantity "1 case", and unit price "¥1,000". For row numbers "1" and "4", the approval post-master immediate reflection flag is set to "Reflect immediately", so the unit price master is updated immediately.

[0090] (S3: Master update process) Refer to Figures 8 and 9 to explain a specific example of the master update process. The master update unit 102d updates the unit price master and route master 106f based on the updated temporary master 106a. If the "immediate master reflection after approval" flag is set to "reflect immediately", the master update unit 102d updates the unit price master immediately after updating the temporary master 106a. If the "immediate master reflection after approval" flag is set to "do not reflect immediately", the master update unit 102d updates the unit price master at an arbitrary timing after updating the temporary master 106a. In addition, the master update unit 102d selects the master to update (customer-specific product unit price master 106b, customer / delivery destination-specific product unit price master 106c, customer / supplier-specific product unit price master 106d, customer / delivery destination-specific product unit price master 106e) based on the quotation category (inventory quotation, direct shipment quotation) of the quotation data (temporary master 106a) and the presence or absence of customers, delivery destinations, and suppliers.

[0091] In the temporary master 106a in Figure 7, rows "1" and "4" with the "immediately reflect master after approval" flag set to "reflect immediately" will have their unit price master updated immediately, as shown in Figures 8(A) and (B). Rows "1" to "3" have an estimate category of "inventory estimate," customer "TK001," delivery destination "NOU001," and supplier "no data," so the customer / delivery destination-specific product unit price master 106c will be updated. Row "4" has an estimate category of "direct estimate," customer "TK001," delivery destination "NOU001," and supplier "SR001," so the customer / delivery destination-specific product unit price master 106e will be updated.

[0092] Figure 8(A) shows an example of updating the customer-delivery-location product unit price master 106c. The customer-delivery-location product unit price master 106c includes the fields for customer, delivery location, start date, end date, product, quantity, and unit price. In the example shown in the figure, the customer is "TK001", the delivery location is "NOU001", the start date is "2022 / 5 / 1", the end date is "2022 / 12 / 31", the product is "Product A", the quantity is "1 case", and the unit price is "¥1,000".

[0093] Figure 8(B) shows 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 includes the fields for customer, delivery destination, supplier, effective start date, effective end date, product, quantity, and unit price. In the example shown in the figure, the customer is "TK001", delivery destination is "NOU001", supplier is "SR001", effective start date is "2022 / 5 / 1", effective end date is "2022 / 12 / 31", product is "product B", quantity is "1", and unit price is "¥200".

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

[0095] In the temporary master 106a in Figure 7, row numbers "2" and "3," where the information for immediate master reflection after approval is "not reflected immediately," will be updated in the customer / delivery destination-specific product unit price master 106c at any time after updating the temporary master 106a, as shown in Figure 9(A).

[0096] Figure 9(A) shows an example of updating the customer delivery destination-specific product unit price master 106c. Figure 9(B) shows an example of updating the route master 106f. For the route master 106f, since the same record already exists, it will be overwritten.

[0097] Next, we will explain the case where the estimate is revised at a later date and the revised estimate data is registered, referring to Figures 10 and 11.

[0098] Figure 10 shows an example of revised quotation data. In Figure 10, the data in row number "1" of the quotation data in Figure 6 has been revised. In Figure 10, the quotation number has been revised to "MT002", the quotation date to "2022 / 6 / 1", the expected order date to "2022 / 6 / 10", the effective date to "2022 / 6 / 1", the unit price to "¥1,100", the amount to "¥1,100", and the detail description to "Revision of quotation for existing transaction".

[0099] Figure 11(A) shows an example of updating the provisional master 106a based on the revised estimate data in Figure 10.

[0100] Figure 11(B) shows an example of updating the customer-delivery-location-specific product unit price master 106c based on the temporary master 106a in Figure 11(A). The second row shows the record created with the revised estimate.

[0101] Figure 11(C) shows an example of updating the root master 106f. Since the same record already exists for the root master 106f, it will be overwritten.

[0102] (Example of using route master and unit price master) Referring to Figures 12 and 13, the usage of the route master and unit price master on the order entry screen will be explained. Figure 12 is a diagram showing an example of the order entry screen display. Figure 13(A) is a diagram showing an example of the route search screen display, and Figure 13(B) is a diagram showing an example of data for the customer delivery destination-specific product unit price master 106c. The screen display control unit 102e controls the display of the order entry screen as follows, for example.

[0103] As shown in Figure 12, the order entry screen includes a header area for specifying the business location, order date, shipping date, planned 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 detail area for specifying details such as line number, order type, quantity, detail description, product, unit price, amount, and supplier.

[0104] When the route search button is pressed, a route search screen like the one shown in Figure 13(A) is displayed. On the route search screen, a list of data from 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 entry 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" are displayed in the details area from the unit price master corresponding to the selected route.

[0105] In the example shown in the diagram, the route with 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" is retrieved from the customer / delivery destination-specific product unit price master 106c (because customer "TK001", delivery destination "NOU001", supplier "-") based on the order date "2022 / 5 / 1" and the corresponding effective start date "2022 / 5 / 1", and the unit price "¥1,000" and amount "¥1,000 (=¥1,000 × 1)" are displayed in the details area.

[0106] In this way, by performing a route search, the person in charge of data entry can avoid the trouble of manually entering each customer's information, and by selecting a route, information including products is set on the screen. After that, by entering the quantity, the unit price of the target product is set, thus streamlining data entry.

[0107] [Function to prevent loss of sales opportunities by product in the commercial flow] Next, the unit price estimation management device 100 of this embodiment manages the number of days elapsed since the last order date for each customer and each product, thereby preventing the loss of business opportunities and maintaining and improving business transactions (function to prevent loss of order opportunities by product in the business flow).

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

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

[0110] Once the quotation is entered in this manner, the data generation unit 102h generates the quotation data shown in Figure 16 based on the input content of the quotation input screen shown in Figures 14 and 15, and stores it in the storage unit 2. As can be seen from Figure 16, the quotation data consists of 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, and amount, along with the "order interval in days" entered on the quotation detail input screen shown in Figure 15. The quotation data in the first row of the record in Figure 15 is the quotation data with an order interval of "60 days" entered.

[0111] Furthermore, the master update unit 102d adds the "order interval in days" entered on the estimate details input screen to the aforementioned route master 106f, which indicates the commercial flow. In this case, the route master 106f is composed of the order interval in days along with the serial number, transaction type, customer code, delivery destination code, supplier code, and product code. The first row of Figure 17 is a record of route master 106f in which an order interval of "60 days" has been entered.

[0112] Next, the data generation unit 102h generates commercial transaction performance data for displaying the commercial transaction product-specific order performance table shown in Figure 18, based on the route master 106f, which has the "order interval in days" shown in Figure 19, and the customer master 106h shown in Figure 20, and stores this data in the commercial transaction product-specific 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 Figure 18(a) is registered, the latest order date detected from the order data shown in Figure 21, the number of days elapsed from the latest order date to the current date, and the number of days elapsed from the order interval days, which is the date obtained by subtracting the number of days elapsed from the order interval days, as shown in Figure 18(b).

[0114] Furthermore, the commercial transaction performance data includes partial data as shown in Figure 18(c), which includes analysis results that analyze the reasons why the number of days elapsed since an order was placed exceeded the number of days between orders, specific information that identifies other personnel handling the same product as the product for which the cause analysis was performed (warning of lost sales opportunity), factor data that shows the commercial transaction performance data that was the subject of the cause analysis, and data that suggests sales opportunities that show other products similar to the product for which the cause analysis was performed (sales opportunity available).

[0115] (Details of the process for generating the sales transaction record table by product) The process of generating a sales performance table by product based on such sales transaction data will be explained in detail. First, the person in charge specifies the display of the sales performance table by product display specification screen. Once this specification is made, the screen display control unit 102e displays the sales performance table by product display specification screen shown in Figure 22 via the output device 114. The person in charge inputs the reference date, which is the date used as the basis for calculating the number of days elapsed since the order and the number of days elapsed between orders, and the data update category, which indicates whether or not to update the sales performance work 106W by product with the sales transaction data of the reference date, to this display specification screen.

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

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

[0118] Furthermore, the transaction interval elapsed 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 commercial transaction product-specific order performance table 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 the order was placed, and the number of days between orders, and stores it in the commercial transaction product-specific performance work unit 106W.

[0120] Here, if "0: Do not update" is specified as the data update category on the display specification screen for the commercial transaction product-specific order performance table shown in Figure 22, the output control unit 102k outputs the commercial transaction performance data via the output device 114 without updating the commercial transaction performance work 106W with the commercial transaction performance data shown in Figures 23(a) to 23(c). As a result, the commercial transaction product-specific order performance table corresponding to the commercial transaction performance data shown in Figures 23(a) to 23(c) is displayed (it can also be printed out).

[0121] The person in charge sends the sales transaction data corresponding to the printed sales transaction record table by product to the sales supervisor terminal device 420 to notify the supervisor of the sales transaction status, or hands over the printed sales transaction record table by product to the supervisor to notify the supervisor of the sales transaction status.

[0122] In contrast, if "1: Update" is specified as the data update category on the display specification screen for the commercial transaction product-specific order performance table shown in Figure 22, the output control unit 102k updates the commercial transaction product-specific performance work 106W with the commercial transaction performance data shown in Figures 23(a) to 23(c). At this stage, the output control unit 102k updates the section from cause to factor root master (= the data in the part showing the analysis results of the cause) as blank (no data), for example, as null data (Null).

[0123] Furthermore, in the case of the commercial transaction performance data shown in Figure 23, the commercial transaction performance data for the second row of the record in Figure 23(b) is detected by the commercial transaction interval elapsed days detection unit 102g as having exceeded the order interval elapsed days by approximately 10 days (order interval elapsed days = +10 days). When the commercial transaction interval elapsed days detection unit 102g detects that the order interval elapsed days exceeds the order interval elapsed days, the communication control unit 102m generates notification data (e.g., email) indicating that the order interval elapsed days has exceeded the order interval elapsed days, 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 notification data via the sales supervisor terminal device 420, they analyze the cause of the order elapsed time exceeding the order interval based on the sales transaction performance data shown in Figure 23, where the problem is pointed out in the notification data. As an example, the cause is coded as follows:

[0125] A) Underreporting B) Insufficient order confirmation from the customer by the person in charge C) Decline in customer demand for products C-1) Orders from competitors C-2) No procurement required for orders of other products. C-3) No need to purchase goods for business operations. C-4) Unavailable for shipment by supplier

[0126] The supervisor sends the analysis results back to the unit price estimation management device 100 via the sales supervisor terminal device 420. For example, suppose the supervisor sends back the analysis result "C-2) No procurement required for orders of other products." The communication control unit 102m of the unit price estimation management device 100 acquires this analysis result via the communication interface unit 104.

[0127] As shown in Figure 24, once the employee receives the analysis results from their supervisor, they enter the obtained analysis result, "C-2) No procurement required due to orders for other products," into the "Cause" input field on the commercial transaction product-specific cause input screen. In addition, the employee also enters the row number and reference date of the commercial transaction data for which the cause analysis was performed into the respective input fields on the commercial transaction product-specific cause input screen.

[0128] The commercial transaction data used for the cause analysis is the second record in Figure 23(a), which has a reference date of "June 20, 2023", customer code "T001", delivery destination code "N001", supplier code "S001", product code "SH02", and order interval of "20 days". The number of this commercial transaction data on the root master 106f is "4", as shown in Figure 19. Therefore, the person in charge enters "4" in the "Serial Number" input field on the commercial transaction product-specific cause input screen. This allows them to identify the commercial transaction data for which the cause analysis of the order elapsed days exceeding the order interval was performed.

[0129] Next, the data generation unit 102h inputs the analysis result "C-2) No procurement required due to orders for other products," which was entered in the "Cause" input field of the commercial transaction performance data input screen for commercial transaction product-specific performance cause input, into the "Cause" input field of the record of the commercial transaction performance data that was the subject of the analysis, as shown in Figure 25(c). In other words, the record of the commercial transaction performance data that was the subject of the analysis is the record indicated by the arrow (B) in Figures 25(a) to 25(c). The data generation unit 102h generates commercial transaction performance data with the analysis result "C-2" returned by the supervisor as the "Cause" of the record indicated by the arrow (B).

[0130] Furthermore, the product code for the product analyzed is "SH02". As indicated by the arrows (D) and (F) in Figures 25(a) and 25(b), the product with the product code "SH02" is also handled by the person in charge of "TA002" and the person in charge of "TA003". For this reason, it is preferable to notify the person in charge of "TA002" and the person in charge of "TA003" when the number of days elapsed since the order of the "SH02" product handled by the person in charge of "TA001" exceeds the number of days between orders, and to draw their attention to prevent the same problem from occurring again.

[0131] For this reason, the data generation unit 102h generates commercial transaction data in which a "○" mark (an example of specific information) is placed in the input field for the order opportunity loss warning for the person in charge of handling the same product for which the number of days elapsed since the order has exceeded the order interval, as shown by the arrows (D) and (F) in Figure 25(c). This allows the person in charge of "TA002" and the person in charge of "TA003" to take measures such as conducting sales activities with the customer, thereby preventing the inconvenience of losing order opportunities.

[0132] Furthermore, when a "○" mark is placed in the input field for the order opportunity loss warning, the data generation unit 102h generates commercial transaction performance data by adding "4" (an example of factor data) to the input field of the factor route master, as shown by the arrows (D) and (F) in Figure 25(c). This data with "4" is the commercial transaction performance data that was the cause of the analysis, as described above. In this way, by entering the "sequential number" of the commercial transaction performance data that was the cause of the analysis into the input field of the factor route master, it is possible to easily identify the commercial transaction performance data that was the cause of the analysis.

[0133] The output control unit 102k displays the generated commercial transaction data via the output device 114. This makes it easy to grasp the number of days elapsed since the last order date, thereby preventing the loss of commercial opportunities and maintaining and improving commercial transactions.

[0134] Furthermore, since the results of the order status analysis are displayed in the order performance table by commercial product, it is possible to draw the attention of each person in charge to the potential loss of business opportunities, and thus significantly prevent the loss of business opportunities.

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

[0136] In this case, other products (SH01) that are similar to the product (SH02) whose cause was analyzed are products handled by the personnel with the respective personnel codes "TA001," "TA002," and "TA003," as indicated by the arrows (A), (C), and (E) in Figures 27(a) and 27(b). Being similar to the product (SH02) whose cause was analyzed means that the same unforeseen business transaction situation may occur. For this reason, it is preferable to encourage each person in charge of handling similar products to consider their response policies to customers.

[0137] Therefore, as indicated by the arrows (A), (C), and (E) in Figures 27(a) and 27(b), the data generation unit 102h generates commercial transaction data in which a "○" mark (an example of data suggesting an order opportunity) is added to the "Opportunity to Order" input field of the records of other products (SH01) that are similar to the product (SH02) for which the cause analysis was performed, as indicated by the arrows (A), (C), and (E) in Figure 27(c).

[0138] This allows us to encourage each person in charge of handling products similar to the product (SH01) whose cause analysis was performed (SH02) to consider how to respond to their respective customers, thereby improving opportunities for receiving orders.

[0139] [Effects of the embodiment] As is clear from the above description, the unit price estimation management device 100 of the embodiment includes at least a unit price master for storing data on customer, application start date, product, quantity (which is the unit of the unit price), and unit price items in association; a temporary master 106a for storing data for updating the unit price master; a unit price estimation input unit 102a for inputting estimation data including items such as estimation number, estimation date, planned order date, planned sales date, customer, delivery destination, supplier, application start date, product, quantity, unit price, and amount; an approval processing unit 102c for updating the temporary master 106a based on the approved estimation data when the input estimation data is approved; and a master update unit 102d for updating the unit price master based on the updated temporary master 106a. Therefore, the efficiency of the unit price estimation work can be improved.

[0140] Furthermore, since the route master 106f stores the number of days between orders, it is easy to determine the number of days elapsed since the last order, which helps prevent the loss of business opportunities and helps maintain and improve business transactions.

[0141] Furthermore, by analyzing the order status and displaying the results in a sales performance report by product, it is possible to draw the attention of each person in charge to the potential loss of business opportunities, thereby significantly preventing the loss of business opportunities.

[0142] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This embodiment can contribute to improving operational efficiency and promoting appropriate management decisions by companies, thereby contributing to SDG Goals 8 and 9.

[0143] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0144] Furthermore, this embodiment can contribute to strengthening control and governance, and thus contribute to SDG Goal 16.

[0145] [Other embodiments] In addition to the embodiments described above, the present invention may be implemented in various different embodiments within the scope of the technical idea described 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 by known methods.

[0147] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each process, screen examples, and database configuration shown in this specification and in the drawings may be changed at will unless otherwise specified.

[0148] Furthermore, with respect to the unit price estimation management device 100, each component shown in the diagram is a functional concept and does not necessarily need to be physically configured as shown.

[0149] For example, the processing functions of the unit price estimation management device 100, particularly the control unit 102 and each processing function performed by the control unit 102, may be implemented in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or they may be implemented as wired logic hardware. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in this embodiment, and is mechanically read by the unit price estimation management device 100 as needed. That is, a storage unit such as ROM or HDD records a computer program that, in cooperation with the OS, gives instructions to the CPU and performs various processing. This computer program is executed by being loaded into RAM and, in cooperation with the CPU, constitutes the control unit 102.

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

[0151] Furthermore, the unit price estimation management program for executing the processing described in this embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product. Here, "recording medium" includes any "portable physical medium" such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical Disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0152] Furthermore, "program" refers to a data processing method described in any language or writing method, regardless of its format, such as source code or binary code. Note that "program" is not necessarily limited to a single, monolithic structure; it also includes distributed structures consisting of multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions. Regarding the specific configuration and reading procedure for reading the recording medium in the unit price estimation management device 100 shown in the embodiment, as well as the installation procedure after reading, well-known configurations and procedures can be used.

[0153] The storage unit 2 is a storage means such as memory devices like RAM and ROM, fixed disk devices like hard disks, flexible disks, and optical disks, and stores various programs, tables, databases, and web page files used for various processes and website provision.

[0154] Furthermore, the unit price estimation management device 100 may be composed of a known personal computer device or an information processing device such as a workstation, or it may be composed of an information processing device to which any peripheral device is connected. In addition, the information processing device may be implemented by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

[0155] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the illustration, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above may be implemented in any combination, or the embodiments may be implemented selectively. [Industrial applicability]

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

[0157] 100 Unit Price Estimation Management System 102 Control Unit 102a Unit Price Estimate Input Section 102b Workflow Processing Unit 102c Approval Processing Unit 102d Master Update Department 102e Screen display control unit 102f Elapsed Days Detection Unit 102g Commercial Transaction Interval Elapsed Days Detection Unit 102h Data Generation Unit 102k Output Control Unit 102m Communication Control Unit 104 Communication Interface Section 106 Storage section 106a Provisional Master 106b Customer-Specific Product Unit Price Master 106c Customer Delivery Destination-Specific Product Unit Price Master 106d Customer / Supplier-Specific Product Unit Price Master 106e Customer, Delivery Destination, and Supplier Product Unit Price Master 106f Route Master 106g Quotation Data File 106h Customer Master 106W Commercial Flow Product-Specific Performance Work 108 Input / Output Interface Section 112 Input device 114 Output device 200 Server Devices 300 Networks 410 Sales Representative Terminal Device 420 Sales Supervisor Terminal Device

Claims

1. A day elapsed detection unit detects the number of days elapsed since the date a business transaction was conducted with a customer, based on business transaction data, from the date the transaction was conducted to the current date. A business transaction interval elapsed days detection unit detects the number of days that is the difference between the number of business transaction intervals, which is the interval between business transactions with the customer, stored in advance in the memory unit, and the detected number of days that have elapsed since the business transaction. A data generation unit generates transaction performance data for each transaction, including the customer, the number of days elapsed since the transaction, the number of days between transactions, the number of days between transactions, and the date on which a transaction was conducted with the customer. An output control unit that outputs the aforementioned commercial transaction data via an external device, A business support device having the following features.

2. When the elapsed days between commercial transactions, which indicates that the number of days elapsed between commercial transactions has exceeded the number of days between commercial transactions, is detected by the elapsed days between commercial transactions detection unit, the data generation unit generates notification data indicating that the elapsed days between commercial transactions have exceeded the number of days between commercial transactions. The system further includes a communication control unit that controls the communication unit to transmit the generated notification data to the terminal device of the person in charge. The business support device according to claim 1, characterized by the following:

3. The communication control unit obtains, via the communication unit, the analysis results of the cause of the number of days elapsed for the commercial transaction exceeding the number of days between commercial transactions, which are returned via the terminal device by the person in charge after performing an analysis based on the notification data. The data generation unit generates the commercial transaction performance data with the acquired analysis results of the cause added. The business support device according to claim 2, characterized by the following:

4. The data generation unit generates the commercial transaction performance data with added specific information that identifies other personnel handling the same commercial transaction subject as the commercial transaction subject for which the cause analysis was performed. The business support device according to claim 3, characterized by the following:

5. The data generation unit generates the commercial transaction performance data, which includes, along with the specific information, factor data indicating the commercial transaction performance data that was the subject of the cause analysis. The business support device according to claim 4, characterized by the following:

6. The data generation unit, when another commercial transaction target similar to the commercial transaction target for which the cause analysis was performed is specified, generates the commercial transaction performance data with added data suggesting order opportunities indicating the specified other commercial transaction target. The business support device according to claim 5, characterized by the following:

7. The elapsed days detection unit detects the number of days elapsed from the date a business transaction was conducted with a customer to the current date, based on the business transaction data. A business transaction interval elapsed days detection unit detects the business transaction interval elapsed days, which is the difference between the business transaction interval days, which is the interval between business transactions with the customer, stored in advance in the storage unit, and the detected business transaction interval days. The data generation unit performs a data generation step that generates transaction performance data for each transaction target, including at least the customer, the number of days elapsed since the transaction, the number of days between transactions, the number of days elapsed since the transaction, and the date on which a transaction was conducted with the customer. The output control unit performs an output control step in which it outputs the commercial transaction data via an external device, A business support method that has the following characteristics.

8. Computers, A day elapsed detection unit detects the number of days elapsed since the date a business transaction was conducted with a customer, based on business transaction data, from the date the transaction was conducted to the current date. A business transaction interval elapsed days detection unit detects the number of days that is the difference between the number of business transaction intervals, which is the interval between business transactions with the customer, stored in advance in the memory unit, and the detected number of days that have elapsed since the business transaction. A data generation unit generates transaction performance data for each transaction, including the customer, the number of days elapsed since the transaction, the number of days between transactions, the number of days between transactions, and the date on which a transaction was conducted with the customer. Output control unit that outputs the aforementioned commercial transaction data via external device A business support program designed to function as such.

Images