Delivery delay management device, delivery delay management method, and delivery delay management program

Abstract

To provide a delivery delay management device, method and program for analyzing the delivery delay of a supplier with a low task load.SOLUTION: The delivery date delay management device 100 includes an arrival input device 102c that creates arrival information including an arrival date, an arrival number, an arrival line number, a supplier, a commodity, the number of arrivals, an ordering number, and an ordering line number based on ordering information when a commodity arrives at a company, an automatic sales accounting device 102d that creates sales information including a sales number, a customer, a person in charge of sales, a sales date set as a scheduled delivery date, a commodity, the number of sales, a sales unit price, a sales amount, an ordering number, and a scheduled delivery date when the scheduled delivery date arrives in a case where an order-receiving classification in the order-receiving information is "direct delivery". This system is provided with a delivery date delay inquiry part 102e for outputting a reference result including the number of delay days and a delay rate for each supplier by referring to ordering date, order-receiving date, arrival date and sales date based on a sales entry part 102f for changing a sales date into an actual delivery date and an extraction condition including a designated supplier.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a delivery delay management device, a delivery delay management method, and a delivery delay management program. [Background technology]

[0002] Recently, suppliers are increasingly storing inventory in-house, and when an order quantity cannot be fulfilled at a single inventory location of the supplier, products are delivered at different times from multiple inventory locations of the supplier. Conventionally, a system for managing delivery dates is known, for example, from Patent Document 1. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-149947 Summary of the Invention [Problem to be solved by the invention]

[0004] As a result of this split delivery, the number of delivery opportunities increases, and the traditional method of registering delivery dates each time poses the problem of complicated delivery date management for products.In addition, there has been an increase in delivery delays from suppliers, which has led to revenue losses and customer (client) dissatisfaction.

[0005] The present invention has been made in consideration of the above, and aims to provide a delivery delay management device, a delivery delay management method, and a delivery delay management program that are capable of analyzing supplier delivery delays with low workload. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a delivery date delay management device equipped with a control unit, the control unit being configured to be able to access a storage area that stores order data including order number, order line number, order classification specifying "arrival" from the supplier to the company or "direct delivery" from the supplier to the customer, order number, customer, sales representative, expected delivery date, product, order quantity, order unit price, and order amount, and order data including order number, supplier, expected arrival date, product, order quantity, order unit price, and order amount, and obtains delivery date response data from the supplier including order number, responded delivery date, delivery quantity, and a schedule confirmation classification that specifies "confirmed" or "scheduled" delivery date, and stores it in the storage area, and if the schedule confirmation classification is "confirmed", updates the expected arrival date of the order data to the responded delivery date, and if the order classification is "direct delivery", updates the scheduled delivery date of the order data to the responded delivery date; and The system is characterized by comprising: an arrival input means for, when goods arrive at the company, creating arrival data including the arrival date, arrival number, arrival line number, supplier, product, arrival quantity, order number, and order line number based on the order data, and storing the data in the storage area; an automatic sales accounting means for, when the scheduled delivery date arrives based on the order data and the order category is "direct delivery", creating sales data including the sales number, customer, sales representative, sales date set as the scheduled delivery date, product, sales quantity, sales price, sales amount, order number, and scheduled delivery date, and storing the data in the storage area; a sales input means for changing the sales date to the actual delivery date if there is a delivery delay in the sales data; and a delivery delay inquiry means for referencing the order data, order data, arrival data, and sales data based on extraction conditions including a specified supplier, and outputting a reference result including the number of delay days and the delay rate for each supplier.

[0007] According to another aspect of the present invention, the reference results may include a description with the following fields: supplier, product, delivery quantity, inbound or direct delivery, expected arrival and delivery date, arrival and delivery date, number of days delayed, order number, order quantity, order unit price, and order amount.

[0008] Furthermore, according to one aspect of the present invention, the reference result is an aggregation of the details, and may include an aggregation with the following fields: supplier, number of transaction details, which is the number of lines; number of late details, which is the number of lines with a number of late days ≠ 0; total number of late days, which is the sum of lines with a number of late days ≠ 0; and lateness rate, which is the number of late details divided by the number of transaction details.

[0009] Furthermore, according to one aspect of the present invention, the control unit may further include a delivery date response inquiry means for referencing the order data, the order data, and the delivery date response data based on extraction conditions including a designated person in charge, and outputting reference results including the schedule confirmation category, order category, customer, person in charge, product, number of orders, number of deliveries, number of unsold items, expected arrival date, expected delivery date, order unit price, and order number.

[0010] In order to solve the above-mentioned problems and achieve the object, the present invention provides a delivery date delay management method executed by an information processing device having a control unit, wherein the control unit is configured to be able to access a storage area that stores order data including an order number, an order line number, an order classification specifying "arrival" from a supplier to the company or "direct delivery" from the supplier to a customer, an order number, a customer, a sales representative, a scheduled delivery date, a product, an order quantity, an order unit price, and an order amount, and order data including the order number, the supplier, a scheduled arrival date, a product, an order quantity, an order unit price, and an order amount, and the control unit executes the process of obtaining delivery date response data from the supplier, including the order number, the responded delivery date, the delivery quantity, and a scheduled confirmation classification that specifies a delivery date "confirmed" or a delivery date "scheduled", and storing the data in the storage area, and if the scheduled confirmation classification is "confirmed", updating the scheduled arrival date of the order data to the responded delivery date, and if the order classification is "direct delivery", updating the scheduled delivery date of the order data to the responded delivery date. a delivery date response input process for updating the delivery date to the requested delivery date; a delivery data input process for creating delivery data including the delivery date, delivery number, delivery line number, supplier, product, quantity of goods received, and order number based on the order data when the product arrives, and storing the data in the storage area; an automatic sales accounting process for creating sales data including the sales number, customer, sales representative, sales date set as the delivery date, product, sales quantity, sales price, sales amount, order number, and scheduled delivery date based on the order data when the order category is "direct delivery," and storing the data in the storage area when the scheduled delivery date arrives; a sales input process for changing the sales date to the actual delivery date when there is a delivery date delay in the sales data; and a delivery delay inquiry process for referencing the order data, order data, delivery data, and sales data based on extraction conditions including a specified supplier, and outputting reference results including the number of delay days and the delay rate for each supplier.

[0011] In order to solve the above-mentioned problems and achieve the object, the present invention provides a delivery date delay management program to be executed by an information processing device having a control unit, the control unit being configured to be able to access a storage area that stores order data including an order number, an order line number, an order classification specifying "arrival" from a supplier to the company or "direct delivery" from the supplier to a customer, an order number, a customer, a salesperson, a scheduled delivery date, a product, an order quantity, an order unit price, and an order amount, and order data including the order number, the supplier, the scheduled arrival date, the product, the order quantity, the order unit price, and the order amount, and the control unit executes a delivery date response import step of acquiring from the supplier delivery date response data including the order number, the responded delivery date, the delivery quantity, and a schedule confirmation classification that specifies a delivery date "confirmed" or a delivery date "scheduled", and storing the acquired delivery date response data in the storage area, and if the schedule confirmation classification is "confirmed", updating the scheduled arrival date of the order data to the responded delivery date, and if the order classification is "direct delivery", updating the scheduled delivery date to the responded delivery date for the order data; and a sales input process for, when an item arrives, creating arrival data including the arrival date, arrival number, arrival line number, supplier, item, arrival quantity, order number, and order line number based on the order data and storing the data in the storage area; an automatic sales accounting process for, when the scheduled delivery date arrives, creating sales data including the sales number, customer, sales representative, sales date set as the scheduled delivery date, item, sales quantity, sales price, sales amount, order number, and scheduled delivery date based on the order data and storing the data in the storage area if the order category is "direct delivery"; a sales input process for changing the sales date to the actual delivery date if there is a delivery delay in the sales data; and a delivery delay inquiry process for referencing the order data, order data, arrival data, and sales data based on extraction conditions including a specified supplier, and outputting reference results including the number of delay days and the delay rate for each supplier. [Effects of the Invention]

[0012] The present invention has the effect of enabling analysis of supplier delivery delays with a low workload. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a delivery delay management device according to this embodiment. [Figure 2] FIG. 2 is a flowchart illustrating the overall processing flow of the control unit of the delivery date delay management device according to this embodiment. [Figure 3] FIG. 3 is a diagram for explaining a specific example of the process of the control unit of the delivery date delay management device according to the present embodiment. [Figure 4] FIG. 4 is a diagram for explaining a specific example of the process of the control unit of the delivery date delay management device according to the present embodiment. [Figure 5] FIG. 5 is a diagram for explaining a specific example of the process of the control unit of the delivery date delay management device according to the present embodiment. [Figure 6] FIG. 6 is a diagram for explaining a specific example of the process of the control unit of the delivery date delay management device according to the present embodiment. [Figure 7] FIG. 7 is a diagram for explaining a specific example of the process of the control unit of the delivery date delay management device according to the present embodiment. [Figure 8] FIG. 8 is a diagram for explaining a specific example of the process of the control unit of the delivery date delay management device according to the present embodiment. [Figure 9] FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the delivery date delay management device according to the present embodiment. [Figure 10] FIG. 10 is a diagram for explaining a specific example of the process of the control unit of the delivery date delay management device according to the present embodiment. [Figure 11] FIG. 11 is a diagram for explaining a specific example of the process of the control unit of the delivery date delay management device according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to the embodiment.

[0015] [1. Overview] The present invention will be outlined in the following order: "1-1. Background and Problems," "1-2. Focus on Solutions to Problems," "1-3. Contents of the Present Invention," and "1-4. Effects of the Present Invention."

[0016] [1-1. Background / Issues] Suppliers are increasingly storing less inventory in-house. If a supplier cannot fulfill an order quantity at one inventory location, products are delivered at different times from multiple inventory locations. This split delivery makes managing product delivery dates more complicated. Suppliers are also experiencing delivery delays, which can lead to revenue loss and customer dissatisfaction.

[0017] [1-2. Focus on problem solving] Two types of delivery date response data, scheduled data (scheduled confirmation category: "scheduled") and confirmed data (scheduled confirmation category: "confirmed"), are linked with suppliers, and the quantity for each scheduled arrival date is managed using the scheduled data, while delivery delays are analyzed using the confirmed data and delivery results.

[0018] [1-3. Contents of the present invention] 1. The following information is imported and managed from suppliers as "delivery date response data." Purchase order number: The purchase order data contains information on the supplier, product, and order quantity, and this number serves as a key to link the order data. Purchase order line number: This is the key to identify the details of the purchase order data. Response deadline: Response deadline from supplier Delivery quantity: The quantity to be delivered Notes: Register notes that cannot be entered in the date. Schedule confirmation category: Judgment items for scheduled data and confirmed data

[0019] 2. The imported delivery date information can be viewed on the inquiry screen and updated to the expected arrival date of the order data from the supplier. For direct shipments, the information is updated to the expected delivery date of the order data.

[0020] 3. After the goods are delivered, compare the expected arrival and delivery dates with the actual dates and analyze delivery delays for each supplier.

[0021] [1-4. Effects of the present invention] According to the present invention, it is possible to analyze supplier delivery delays with a low workload. Specifically, the following effects can be achieved. (1) By linking supplier and delivery date response data, the burden on operators who process the data can be reduced, and the risk of human error due to input errors, miscommunication, and omissions can be reduced, thereby improving work efficiency. (2) By analyzing delivery delays (for example, calculating the number of days of delay and the rate of delay), it is possible to request suppliers to prevent delivery delays and also to use the results as material for price negotiations, thereby reducing costs.

[0022] The delivery delay management device of the present invention can be suitably used in the retail industry, where products are purchased in small units each time.

[0023] [2. Configuration] An example of a delivery delay management device according to this embodiment will be described with reference to FIG. 2. FIG. 2 is a block diagram showing an example of the configuration of the delivery delay management device according to this embodiment. The delivery delay management device 100 is a commercially available desktop personal computer. Note that the delivery delay management device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer. In FIG. 2, the delivery delay management device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the delivery delay management device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0024] The communication interface unit 104 communicatively connects the delivery delay 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 exchanging data with other devices via the communication line. Here, the network 300 has a function of communicatively connecting the delivery delay management device 100 with the server 200 and supplier systems 400, etc., and is, for example, the Internet or a local area network (LAN). The delivery delay management device 100 cooperates with the supplier systems 400, etc., for example, regarding order data, delivery date response data, etc. The delivery delay management device 100 creates order data, which is imported into the supplier system 400. The supplier system 400 creates delivery date response data based on the imported order data, and the delivery date response data is imported into the delivery delay management device 100.

[0025] An input device 112 and an output device 114 are connected to the input / output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in cooperation with a mouse. Note that hereinafter, the output device 114 may be referred to as the monitor 114.

[0026] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can be, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, etc.

[0027] The storage unit 106 stores received order data, order data, delivery date response data, arrival data, sales data, and the like.

[0028] The delivery date response data may include an order number, an order line number, a response delivery date, the number of items to be delivered, notes, and a schedule confirmation classification (1: confirmed, 0: scheduled).

[0029] The order data may include an order number, an order line number, a supplier, an expected arrival date, an item, an order quantity, an order unit price, and an order amount.

[0030] The order data may include the order number, order line number, order category ("Order (= "arrival" from supplier to our company), "Direct order (= "direct delivery" sent directly from supplier to customer)"), purchase order number, purchase order line number, customer, sales representative, expected delivery date, product, order quantity, order unit price, and order amount.

[0031] The receipt data may include the date of receipt, receipt number, receipt line number, supplier, product, quantity received, purchase order number, and purchase order line number.

[0032] The sales data may include sales number, sales line number, customer, sales representative, sales date, product, sales quantity, sales price, sales amount, order number, order line number, and expected delivery date.

[0033] The control unit 102 is a CPU or the like that comprehensively controls the delivery date delay 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, etc., and executes various information processing based on these stored programs.

[0034] The control unit 102 is configured to be able to access the order data, order data, delivery date response data, arrival data, sales data, etc. stored in the storage unit 106. Note that the order data, order data, delivery date response data, arrival data, sales data, etc. may be stored in another location (for example, the server 200) as long as the control unit 102 is able to access them.

[0035] The control unit 102, in terms of functional concept, comprises a delivery date response import unit 102a, a delivery date response inquiry unit 102b, an arrival input unit 102c, an automatic sales calculation unit 102d, a sales input unit 102e, a delivery date delay inquiry unit 102f, and a screen display control unit 102g.

[0036] The delivery date response import unit 102a imports delivery date response data including the order number, order line number, replied delivery date, quantity of delivery, and scheduled confirmation classification specifying whether the delivery date is "confirmed" or "scheduled" from the supplier's system 400..., and stores it in the memory unit 106.

[0037] If the "scheduled confirmation classification" of the delivery date response data is "confirmed," the delivery date response import unit 102a updates the "scheduled arrival date" of the order data to the "answered delivery date" of the delivery date response data, and if the "order classification" of the order data is "direct delivery," it updates the "scheduled delivery date" of the order data to the "answered delivery date" of the delivery date response data.

[0038] For example, in response to an operator's operation on a delivery date reply inquiry screen (not shown) displayed on the monitor 114, the delivery date reply inquiry unit 102b refers to the order data, order data, and delivery date reply data stored in the memory unit 106 based on extraction conditions including the designated person in charge, and displays and outputs the reference results (extraction results) including the scheduled confirmation category, order category, customer, person in charge, product, number of orders, number of deliveries, number of unsold items, expected arrival date, expected delivery date, order unit price, and order number.

[0039] When a product arrives, the arrival input unit 102c creates arrival data including the arrival date, arrival number, arrival line number, supplier, product, number of arrivals, order number, and order line number based on the order data stored in the memory unit 106, for example, in response to an operator's operation on an arrival input screen (not shown) displayed on the monitor 114, and stores the data in the memory unit 106.

[0040] Based on the order data stored in the memory unit 106a, when the order category is "direct delivery," the automatic sales accounting unit 102d creates sales data including the sales number, sales line number, customer, sales representative, sales date, product, sales quantity, sales price, sales amount, order number, order line number, and scheduled delivery date when the scheduled delivery date arrives, and stores the data in the memory unit 106.

[0041] The sales input unit 102e changes the sales date to the actual delivery date for the sales data stored in the memory unit 106, for example, in response to an operator's operation on a sales input screen (not shown) displayed on the monitor 114, if there is a delivery delay.

[0042] The delivery delay inquiry unit 102f, for example, in response to an operator's operation on a delivery delay inquiry screen (not shown) displayed on the monitor 114, references the order data, order data, arrival data, and sales data stored in the memory unit 106 based on extraction conditions including the specified supplier, and displays and outputs the reference results including the number of delay days and delay rate for each supplier.

[0043] The reference results may include details with the following fields: supplier, product, delivery quantity, inbound or direct delivery, expected delivery date, delivery date, number of days delayed, order number, order quantity, order unit price, and order amount.

[0044] In addition, the reference result is a summary of the details and may include the following items: supplier, number of transaction details (number of lines), number of delayed details (number of lines with delayed days ≠ 0), total number of delayed days (sum of lines with delayed days ≠ 0), and lateness rate (number of delayed details divided by number of transaction details).

[0045] The screen display control unit 102g controls the display and input of various screens (for example, a stock input screen, a sales input screen, a delivery date reply inquiry screen, a delivery date delay inquiry screen, etc.) displayed on the monitor 114.

[0046] [3. Specific Examples] A specific example of the processing by the control unit 102 of the delivery date delay management device 100 according to the present embodiment will be described with reference to Fig. 2 to Fig. 11. Fig. 2 to Fig. 11 are diagrams for explaining a specific example of the processing by the control unit 102 of the delivery date delay management device 100 according to the present embodiment.

[0047] [3-1. Overall processing] The overall processing flow of the control unit 102 of the delivery date delay management device 100 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing a flow for explaining the overall processing flow of the control unit 102 of the delivery date delay management device 100 according to this embodiment.

[0048] It is assumed that the control unit 102 creates "received order data" based on orders from customers and stores it in the storage unit 106, and further creates "ordering data" based on the received order data and stores it in the storage unit 106. The supplier's system 400 works with and imports this "ordering data", and the supplier checks the order data and creates "delivery date response data" for each product. The control unit 102 works with and imports this "delivery date response data". Figure 2 explains the processing flow after the delivery date response data is linked.

[0049] 2, delivery date reply import unit 102a executes delivery date reply import processing (step S1). Specifically, in the delivery date reply import processing, delivery date reply import unit 102a imports delivery date reply data including the order number, order line number, replied delivery date, delivery quantity, and planned confirmation classification that specifies the delivery date as "confirmed" or "planned" from supplier systems 400..., stores the data in storage unit 106, and if the "planned confirmation classification" of the delivery date reply data is "confirmed", updates the "scheduled arrival date" of the order data to the "replied delivery date" of the delivery date reply data, and if the "order classification" of the order data is "direct delivery", updates the "scheduled delivery date" of the order data to the "replied delivery date" of the delivery date reply data.

[0050] The delivery date answer inquiry unit 102b executes delivery date answer inquiry processing (step S2). Specifically, in the delivery date answer processing, the delivery date answer inquiry unit 102b refers to the order data, order data, and delivery date answer data stored in the storage unit 106 based on the extraction conditions designated in response to an operator's operation on a delivery date answer inquiry screen (not shown) displayed on the monitor 114, and displays and outputs the reference result (extraction result).

[0051] The arrival input unit 102c executes the arrival input process (step S3). Specifically, in the arrival input process, when products arrive at the company, the arrival input unit 102c creates arrival data including the arrival date, arrival number, arrival line number, supplier, product, arrival quantity, order number, and order line number based on the order data stored in the storage unit 106, and stores the data in the storage unit 106. In other words, the arrival data is created for the products arriving at the company. For direct shipment products, no arrival data is created because the products are not received at the company.

[0052] The automatic sales accounting unit 102d executes the automatic sales accounting process (step S4). Specifically, in the automatic sales accounting process, based on the order data stored in the memory unit 106a, when the order category is "direct delivery," the automatic sales accounting unit 102d creates sales data including the sales number, sales line number, customer, sales representative, sales date set as the scheduled delivery date, product, sales quantity, sales price, sales amount, order number, order line number, and scheduled delivery date when the scheduled delivery date arrives, and stores this data in the memory unit 106. Sales data is automatically created for direct delivery.

[0053] The sales input unit 102e executes a sales input process (step S5). Specifically, the sales input unit 102e changes the sales date of the sales data stored in the storage unit 106 to the actual delivery date if there is a delivery date delay, for example, in response to an operator's operation on a sales input screen (not shown) displayed on the monitor 114.

[0054] The delivery delay inquiry unit 102f executes a delivery delay inquiry process (step S6). Specifically, in the delivery delay inquiry process, the delivery delay inquiry unit 102f, for example, in response to an operator's operation on a delivery delay inquiry screen (not shown) displayed on the monitor 114, references the order data, order data, arrival data, and sales data stored in the storage unit 106 based on extraction conditions including a specified supplier, and displays and outputs the reference results including the number of delay days and the delay rate for each supplier.

[0055] [3-2. Sample Data] 3 to 11 are diagrams showing sample data for explaining a specific example of the processing of the control unit 102 of the delivery delay management device 100 in this embodiment. With reference to FIGS. 3 to 11, a specific example of the processing of the control unit 102 of the delivery delay management device 100 in this embodiment will be explained using sample data. In FIGS. 3 to 11, to make the explanation easier to understand, each piece of data is assigned a number indicating its correspondence, with "1" to "3" being assigned a scheduled confirmation category of "confirmed" and assuming incoming shipments, "4" to "6" being assigned a scheduled confirmation category of "confirmed" and assuming direct shipments, and "7" to "9" being assigned a scheduled confirmation category of "scheduled."

[0056] (S1: Delivery date response import process) A specific example of delivery date reply import processing will be described with reference to Figures 3 and 4. Delivery date reply import unit 102a imports delivery date reply data including the order number, order line number, replied delivery date, delivery quantity, and planned confirmation class that specifies the delivery date as "confirmed" or "planned" and stores it in memory unit 106, and if the "planned confirmation class" of the delivery date reply data is "confirmed", it updates the "scheduled arrival date" of the order data to the "replied delivery date" of the delivery date reply data, and if the "order classification" of the order data is "direct delivery", it updates the "scheduled delivery date" of the order data to the "replied delivery date" of the delivery date reply data.

[0057] Figure 3 is a diagram showing an example of delivery date response data. Delivery date response data may include the purchase order number, purchase order line number, responded delivery date, delivery quantity, remarks, and scheduled confirmation classification (1: confirmed, 0: scheduled). In the example shown in the figure, the first line contains the purchase order number "HA9000005364," the purchase order line number "1," the responded delivery date "2024 / 04 / 10," the delivery quantity "1," and the scheduled confirmation classification "1: confirmed." The data in bold is updated in this process.

[0058] Figure 4(A) is a diagram showing an example of order data. When delivery date response data is imported, the "estimated arrival date" is updated to the "answered delivery date" only for confirmed order data (those with an expected confirmation classification of "1: Confirmed"). (Only the expected arrival date is updated.) Order data may include the order number, order line number, supplier, expected arrival date, product, order quantity, order price, and order amount. In the example shown in the figure, the first line contains the order number "HA9000005364," order line number "1," supplier "XX Company," expected arrival date "2024 / 04 / 10," product "AAAA," order quantity "1," order price "1000," and order amount "1000." The data updated during this process is in bold.

[0059] Figure 4(B) shows an example of order data. When delivery date response data is imported, the expected delivery date is updated to the response delivery date only for direct delivery items (those with the order category "Direct Delivery Order"). (Only the expected delivery date for direct delivery items is updated.) Order data may include the order number, order line number, order category, purchase order number, purchase order line number, customer, sales representative, expected delivery date, product, order quantity, order price, and order amount. In the example shown in the figure, the fourth line contains the order number "JU9000003468," order line number "1," order category "Direct Delivery Order," purchase order number "HA9000005367," order line number "1," customer "Company R," sales representative "YYY," expected delivery date "2024 / 04 / 12," product "DDDD," order quantity "30," order price "1,000," and order amount "30,000." The data updated during this process is in bold.

[0060] (S2: Delivery date reply inquiry process) A specific example of delivery date answer inquiry processing will be described with reference to Figures 5 and 6. The delivery date answer inquiry unit 102b, for example, in response to an operation by an operator (for example, a sales representative) on a delivery date answer inquiry screen (not shown) displayed on the monitor 114, references the order data, order data, and delivery date answer data stored in the storage unit 106 based on a specified extraction condition (for example, a sales representative), and displays and outputs the reference result (extraction result). In the delivery date answer inquiry processing, for example, each sales representative can make an inquiry to create a delivery plan for a customer.

[0061] Figure 5 shows the contents of each item in the extraction conditions and reference results. As extraction conditions, for example, one or more of the following can be specified: sales representative, customer, schedule confirmation category, order category, expected arrival date (specified range), expected delivery date (specified range), etc.

[0062] Figure 6 shows an example of the reference result (extraction result). The reference result outputs the following items: schedule confirmation category, order category, customer, sales representative, product, order quantity, delivery quantity, unsold quantity, expected arrival date, expected delivery date, remarks, order unit price, order number, and order line number. Here, "schedule confirmation category" is the schedule confirmation category in the delivery date response data. "Order category" is the order category in the order data. "Customer" is the "customer" in the order data. "Sales representative" is the sales representative in the order data. "Product" is the "product" in the order data. "Order quantity" is the number of orders in the order data. "Delivery quantity" is the number of deliveries in the delivery date response data. "Unsold quantity" is the number of orders in the order data minus the number of sales in the sales data. "Expected arrival date" is the expected arrival date in the order data. "Expected delivery date" is the expected delivery date in the order data. "Remarks" are remarks in the delivery date response data. "Order unit price" is the order unit price in the order data. "Order number" is the order number of the order data. "Order line number" is the order line number of the order data.

[0063] Figure 6(A) shows the reference results when the extraction condition is sales representative XXX. Figure 6(B) shows the reference results when the extraction condition is sales representative YYY. Figure 6(C) shows the reference results when the extraction condition is sales representative ZZZ.

[0064] (S3: Incoming goods input processing) A specific example of the arrival entry process will be described with reference to Fig. 7. When goods arrive at the company, the arrival entry unit 102c creates arrival data including the arrival date, arrival number, arrival line number, supplier, product, arrival quantity, order number, and order line number based on the order data stored in the storage unit 106, and stores the data in the storage unit 106. The company checks the goods and invoices that have arrived at the company and enters the arrival information.

[0065] An example of the receipt data is shown in Figure 3. The receipt data may include the date of receipt, receipt number, receipt line number, supplier, product, number of items received, purchase order number, and purchase order line number.

[0066] The item arrived on the scheduled arrival date on 4 / 10. The first line of the arrival data for 4 / 10 is arrival date "2024 / 04 / 10", arrival number "NK9000001018", arrival line number "1", supplier "XX Company", product "AAAA", quantity arrived "1", purchase order number "HA9000005364", and purchase order line number "1". The data in bold is the updated data for this process.

[0067] The product was scheduled to arrive on April 12th, but due to a delay in delivery, it did not arrive.

[0068] On April 13th, the item that was scheduled to arrive on April 12th arrived one day late due to a delivery delay.

[0069] (S4: Automatic sales accounting process) A specific example of automatic sales accounting processing will be described with reference to Figure 8. Based on the order data stored in the memory unit 106a, when the order category is "direct order," the automatic sales accounting unit 102d creates sales data including the sales number, sales line number, customer, sales representative, sales date set as the scheduled delivery date, product, sales quantity, sales price, sales amount, order number, order line number, and scheduled delivery date when the scheduled delivery date arrives, and stores this data in the memory unit 106. For direct delivery orders, sales accounting is automatically performed for order data whose scheduled delivery date has arrived. Automatic accounting is performed every day at a specified time (for example, late at night).

[0070] FIG. 8 is a diagram showing an example of sales data. The sales data may include a sales number, a sales line number, a customer, a sales representative, a sales date, a product, a sales quantity, a sales price, a sales amount, an order number, an order line number, and a scheduled delivery date. In this example, the scheduled delivery dates are 4 / 12 and 4 / 16, and sales data is automatically created. In the example of sales data created on 4 / 12, the first line contains the sales number "UR9000012224," the sales line number "1," the customer "Company R," the sales representative "YYY," the sales date "2024 / 04 / 12," the product "DDDD," the sales quantity "1," the sales price "1000," the sales amount "10000," the order number "JU9000003468," the order line number "1," and the scheduled delivery date "2024 / 04 / 12."

[0071] (S5: Sales input processing) 9, a sales input process is executed (step S5). Specifically, the sales input unit 102e changes the sales date to the actual delivery date (the date of delivery from the supplier to the customer) for the sales data stored in the storage unit 106 in response to, for example, an operator's operation on a sales input screen (not shown) displayed on the monitor 114, if there is a delivery delay. For direct delivery items, if there is a delivery delay, the sales date is changed in the sales input.

[0072] Figure 9 shows an example of changed sales data. On April 18th, the direct delivery item from April 16th was delivered two days later than the due date, and the sales date for item number "6" was changed from "2024 / 4 / 16" to "2024 / 4 / 18".

[0073] (S6: Delivery delay inquiry process) A specific example of the delivery delay inquiry process will be described with reference to Figures 10 and 11. The delivery delay inquiry unit 102f, for example, refers to the order data, order data, arrival data, and sales data stored in the storage unit 106 based on the specified extraction conditions (supplier, etc.) in response to an operator's operation on a delivery delay inquiry screen (not shown) displayed on the monitor 114, and displays and outputs the reference results including the number of delay days and the delay rate for each supplier. In the delivery delay inquiry process, after arrival, data on the expected arrival date and arrival date (actual arrival date), and the expected delivery date and delivery date (actual delivery date) are queried and output for each supplier.

[0074] Figure 10 shows the extraction conditions, details of the reference results, and the contents of each item in the summary. As extraction conditions, for example, one or more of the following can be specified: supplier, product, expected arrival date (specify range), expected delivery date (specify range), and direct delivery (select arrival or direct delivery).

[0075] Figure 11 shows an example of the details of the reference results (extraction results) and their aggregation. Figure 11(A) shows an example of the details when the extraction condition is supplier "XX Company", and Figure 11(B) shows an example of the aggregation of the details of Figure 11(A).

[0076] As shown in Figure 11(A), the details output include the following items: supplier, product, delivery quantity, direct delivery of goods, estimated delivery date of goods received, delivery date of goods received, number of days delayed, order number, order line number, order quantity, order price, and order amount. Here, "Supplier" is the supplier in the receipt data in the case of receipt, and the supplier in the order data in the case of direct delivery. "Product" is the product in the receipt data in the case of receipt, and the product in the order data in the case of direct delivery. "Delivery quantity" is the number of goods received in the receipt data in the case of receipt, and the sales number in the sales data in the case of direct delivery. "Estimated delivery date of goods received" is the estimated delivery date in the order data in the case of receipt, and the estimated delivery date in the order data in the case of direct delivery. The delivery date is the arrival date in the receipt data in the case of receipt, and the sales date in the sales data in the case of direct delivery.

[0077] In the example shown in the figure, the first line contains the following information: supplier "XX Company", product "AAAA", delivery quantity "1", direct delivery "Arrived", expected delivery date "2024 / 04 / 10", delivery date "2024 / 04 / 10", number of days delayed "-", order number "HA9000005364", order line number "1", order quantity "1", order price "1000", and order amount "1000".

[0078] As shown in Figure 11(B), the following items are output for the summary: supplier, number of transaction details, number of delayed details, total number of delayed days, and lateness rate. Here, "Supplier" refers to the supplier. "Number of transaction details" is the number of rows. "Number of delayed details" is the number of rows where the number of delayed days is not equal to 0. "Total number of delayed days" is the sum of rows where the number of delayed days is not equal to 0. "Lateness rate" is the number of delayed details divided by the number of transaction details. In the example shown in the figure, the supplier is "Company XX", the number of transaction details is "6", the number of delayed details is "2", the total number of delayed days is "3 (= 1 + 2)", and the lateness rate is "33.33% (= 2 ÷ 6)".

[0079] As described above, according to this embodiment, delivery date response acquisition unit 102a acquires delivery date response data from a supplier, including an order number, a replied delivery date, a delivery quantity, and a scheduled confirmation category that specifies whether the delivery date is "confirmed" or "scheduled," and stores the data in storage unit 106; if the scheduled confirmation category is "confirmed," it updates the expected arrival date of the order data to the replied delivery date; and if the order category for the order data is "direct delivery," it updates the expected delivery date to the replied delivery date; and when products arrive at the company, it creates arrival data including the arrival date, arrival number, arrival line number, supplier, product, arrival quantity, order number, and order line number based on the order data, and stores the data in storage unit 106. The system is equipped with an automatic sales accounting unit 102d that, based on order data, creates sales data including the sales number, customer, sales representative, sales date set as the scheduled delivery date, product, sales quantity, sales price, sales amount, order number, and scheduled delivery date when the scheduled delivery date arrives when the order category is "direct delivery," and stores the data in the storage unit 106a; a sales input unit 102e that changes the sales date to the actual delivery date when there is a delivery delay in the sales data; and a delivery delay inquiry unit 102f that references the order data, order data, arrival data, and sales data based on extraction conditions including the specified supplier, and outputs reference results including the number of delay days and delay rate for each supplier, making it possible to analyze supplier delivery delays with a low workload.

[0080] [4. 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 contributing to the achievement of SDGs Goals 8 and 9.

[0081] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0082] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to the achievement of Goal 16 of the SDGs.

[0083] 5. Other Embodiments The present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept set forth in the claims.

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

[0085] Furthermore, 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 can be changed as desired unless otherwise specified.

[0086] Furthermore, with regard to the delivery delay management device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0087] For example, all or any part of the processing functions of the delivery date delay management device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, 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 delivery date delay management device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0088] In addition, this computer program may be stored in an application program server connected to the delivery date delay management device 100 via any network, and all or part of it may be downloaded as needed.

[0089] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or 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.

[0090] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known configurations and procedures.

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

[0092] The delivery date delay management device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The delivery date delay management device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

[0093] 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 configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Explanation of symbols]

[0094] 100 Delivery Delay Management Device 102 Control section 102a Delivery date response acquisition section 102b Delivery date response inquiry section 102c Arrivals Input Section 102d Automatic Sales Recording Department 102e Sales Input Section 102f Delivery Delay Inquiry Department 102g Screen display control unit 104 Communication interface unit 106 Storage section 200 servers 300 Network 400 Supplier's System

Claims

1. A delivery delay management device equipped with a control unit, The control unit Order data including order number, order line number, order classification specifying "arrival" from supplier to our company or "direct delivery" from supplier to customer, order number, customer, sales representative, expected delivery date, product, order quantity, order unit price, and order amount; Order data including order number, supplier, expected arrival date, product, order quantity, order unit price, and order amount; The storage area storing the a delivery date response taking-in means for acquiring delivery date response data from a supplier, including an order number, a replied delivery date, the number of items to be delivered, and a scheduled confirmation category specifying whether the delivery date is "confirmed" or "scheduled," and storing the data in the storage area, and for updating the expected arrival date of the order data to the replied delivery date if the scheduled confirmation category is "confirmed," and for updating the expected delivery date of the order data to the replied delivery date if the order category is "direct delivery," an arrival input means for creating arrival data including arrival date, arrival number, arrival line number, supplier, product, arrival quantity, order number, and order line number based on the order data when the product arrives at the company, and storing the data in the storage area; an automatic sales accounting means for creating sales data including a sales number, a customer, a sales representative, a sales date set as the scheduled delivery date, a product, a sales quantity, a sales price, a sales amount, an order number, and a scheduled delivery date when the scheduled delivery date arrives, based on the order data, when the order category is "direct delivery", and storing the data in the storage area; a sales input means for changing the sales date to the actual delivery date when there is a delivery delay in the sales data; a delivery delay inquiry means for referring to the order data, the order data, the receipt data, and the sales data based on extraction conditions including a designated supplier, and outputting a reference result including the number of days of delay and the delay rate for each supplier; A delivery delay management device comprising:

2. 2. The delivery delay management device according to claim 1, wherein the reference result includes a statement with the following items: supplier, product, delivery quantity, inbound or direct delivery classification, expected arrival and delivery date, arrival and delivery date, number of days of delay, order number, order quantity, order unit price, and order amount.

3. The delivery date delay management device of claim 2, characterized in that the reference result is an aggregation of the details and includes the following items: supplier, number of transaction details (number of lines), number of delayed details (number of lines with delayed days ≠ 0), total number of delayed days (sum of lines with delayed days ≠ 0), and delay rate (number of delayed details divided by number of transaction details).

4. The control unit further A delivery date delay management device as described in any one of claims 1 to 3, characterized in that it is provided with a delivery date response inquiry means that references the order data, the order data, and the delivery date response data based on extraction conditions including a designated person in charge, and outputs reference results including the scheduled confirmation category, order category, customer, person in charge, product, number of orders, number of deliveries, number of unsold items, expected arrival date, expected delivery date, order unit price, and order number.

5. A delivery date delay management method executed by an information processing device having a control unit, The control unit Order data including order number, order line number, order classification specifying "arrival" from supplier to our company or "direct delivery" from supplier to customer, order number, customer, sales representative, expected delivery date, product, order quantity, order unit price, and order amount; Order data including order number, supplier, expected arrival date, product, order quantity, order unit price, and order amount; The storage area storing the Executed in the control unit: a delivery date response import step of acquiring delivery date response data from the supplier, including the order number, the responded delivery date, the number of items to be delivered, and a scheduled confirmation category specifying whether the delivery date is "confirmed" or "scheduled," and storing the data in the storage area, and updating the expected arrival date of the order data to the responded delivery date if the scheduled confirmation category is "confirmed," and updating the expected delivery date to the responded delivery date if the order category is "direct delivery" for the order data; an arrival input step of creating arrival data including arrival date, arrival number, arrival line number, supplier, product, arrival quantity, order number, and order line number based on the order data when the product arrives at the company, and storing the data in the storage area; an automatic sales accounting process for creating sales data including a sales number, a customer, a sales representative, a sales date set as the scheduled delivery date, a product, a sales quantity, a sales price, a sales amount, an order number, and a scheduled delivery date when the scheduled delivery date arrives, based on the order data, and storing the data in the storage area, when the order category is "direct delivery"; a sales input step of changing the sales date to the actual delivery date when there is a delivery delay in the sales data; a delivery delay inquiry step of referring to the order data, the order data, the receipt data, and the sales data based on extraction conditions including a designated supplier, and outputting a reference result including the number of days of delay and the delay rate for each supplier; A delivery delay management method comprising:

6. A delivery delay management program to be executed by an information processing device having a control unit, The control unit Order data including order number, order line number, order classification specifying "arrival" from supplier to our company or "direct delivery" from supplier to customer, order number, customer, sales representative, expected delivery date, product, order quantity, order unit price, and order amount; Order data including order number, supplier, expected arrival date, product, order quantity, order unit price, and order amount; The storage area storing the Executed in the control unit: a delivery date response import step of acquiring delivery date response data from the supplier, including the order number, the responded delivery date, the number of items to be delivered, and a scheduled confirmation category specifying whether the delivery date is "confirmed" or "scheduled," and storing the data in the storage area, and updating the expected arrival date of the order data to the responded delivery date if the scheduled confirmation category is "confirmed," and updating the expected delivery date to the responded delivery date if the order category is "direct delivery" for the order data; an arrival input step of creating arrival data including arrival date, arrival number, arrival line number, supplier, product, arrival quantity, order number, and order line number based on the order data when the product arrives at the company, and storing the data in the storage area; an automatic sales accounting process for creating sales data including a sales number, a customer, a sales representative, a sales date set as the scheduled delivery date, a product, a sales quantity, a sales price, a sales amount, an order number, and a scheduled delivery date when the scheduled delivery date arrives, based on the order data, and storing the data in the storage area, when the order category is "direct delivery"; a sales input step of changing the sales date to the actual delivery date when there is a delivery delay in the sales data; a delivery delay inquiry step of referring to the order data, the order data, the receipt data, and the sales data based on extraction conditions including a designated supplier, and outputting a reference result including the number of days of delay and the delay rate for each supplier; A delivery delay management program to execute this.

Images