Order backlog management device, order backlog management method, and order backlog management program

Abstract

To effectively manage the outstanding stock of pharmaceutical orders. [Solution] The order backlog management device according to this embodiment includes a product master 106a in which a product code and an internal code for defining the identity of a product are registered in association, and an order backlog processing unit 102c which, in the order backlog data, sets the slip cancellation flag to "slip cancellation" for order numbers for which the set number of days for order backlog deletion has elapsed, and if the slip cancellation flag in the order backlog data is not "slip cancellation", clears the number of undelivered items calculated by subtracting the number of received items from the order backlog data using the number of purchased items, and sets the purchase completion flag to "purchase completion" when the number of undelivered items becomes 0.

Description

Technical Field

[0001] The present invention relates to an order backlog management device, an order backlog management method, and an order backlog management program.

Background Art

[0002] For example, in the pharmaceutical industry, pharmaceutical wholesalers and pharmaceutical manufacturers cooperate (use) via pharmaceutical EDI (JD-NET or email) (hereinafter referred to as "(pharmaceutical) VAN") to place orders and make deliveries. Conventionally, as a system for managing products, there is, for example, Patent Document 1.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the pharmaceutical industry, due to shortages of pharmaceuticals, there are cases where deliveries are not made as ordered. Even when the number of ordered items is less than expected in such situations, no confirmation of full delivery is received for the order. Also, for orders of new products, there are cases where deliveries are made with old products. Thus, conventionally, it has not been possible to suitably manage the order backlog of products.

[0005] The present invention has been made in view of the above, and an object thereof is to provide an order backlog management device, an order backlog management method, and an order backlog management program capable of suitably managing the order backlog of products.

Means for Solving the Problems

[0006] To solve the above-mentioned problems and achieve the objective, the present invention provides an order backlog management device equipped with a control unit, wherein the control unit is configured to access a product master in which a product code and an internal code for defining the identity of a product are registered in association with each product code, order backlog data including an order number, supplier code, order date, product code, internal code, order quantity, received quantity, a purchase completion flag indicating whether the purchase is complete or not, and a slip cancellation flag indicating whether the slip is canceled or not, and purchase data including a purchase number, supplier code, purchase date, product code, and purchase quantity, and wherein the order backlog processing means sets the slip cancellation flag to "slip cancellation" for order numbers for which the set number of days for order backlog deletion has elapsed in the order backlog data, and if the slip cancellation flag in the order backlog data is not "slip cancellation", it clears the number of unreceived items calculated by subtracting the number of received items from the order backlog data using the number of purchased items in the purchase data, and sets the purchase completion flag to "purchase complete" when the number of unreceived items = 0.

[0007] Furthermore, according to one aspect of the present invention, the order backorder processing means may sequentially compare the purchase data with the order backorder data in ascending order of order date, using the purchase number unit, and if the order backorder data does not have a purchase completion flag of "Purchase Completed". If the order cancellation flag of the order backorder data is not "Order Cancelled", and the supplier code and product code of the purchase data and the order backorder data match, the number of undelivered items in the order backorder data is deducted from the number of purchases in the purchase data, and if the number of undelivered items becomes 0, the purchase completion flag is set to "Purchase Completed". Alternatively, if the supplier code and product code of the purchase data and the order backorder data do not match, and the supplier code of the purchase data and the internal code associated with that product code in the product master match, the number of undelivered items in the order backorder data is deducted from the number of purchases in the purchase data, and if the number of undelivered items becomes 0, the purchase completion flag is set to "Purchase Completed".

[0008] Furthermore, according to one aspect of the present invention, the product may be a pharmaceutical product.

[0009] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention provides an order backlog management method executed by an information processing device equipped with a control unit, wherein the control unit is configured to access a product master registered by associating a product code with an internal code for defining the identity of a product, order backlog data including an order number, supplier code, order date, product code, internal code, order quantity, received quantity, a purchase completion flag indicating whether the purchase is complete or not, and a slip cancellation flag indicating whether the slip is canceled or not, and purchase data including a purchase number, supplier code, purchase date, product code, and purchase quantity, and the method is executed by the control unit, wherein for order numbers in the order backlog data for which the set number of days for order backlog deletion has elapsed, the slip cancellation flag is set to "slip cancellation", and if the slip cancellation flag in the order backlog data is not "slip cancellation", the number of unreceived items calculated by subtracting the number of received items from the order backlog data is cleared using the number of purchased items in the purchase data, and if the number of unreceived items = 0, the purchase completion flag is set to "purchase complete".

[0010] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the present invention provides an order balance management program to be executed by an information processing device equipped with a control unit, wherein the control unit includes a product master registered by associating a product code with an internal code for defining the identity of a product, order balance data including order number, supplier code, order date, product code, internal code, order quantity, received quantity, purchase completion flag indicating whether the purchase is complete or not, and slip cancellation flag indicating whether the slip is canceled or not, and purchase data including purchase number, supplier code, purchase date, product code, and purchase quantity. The program is configured to allow access to the control unit and is characterized by being an order back management program that causes the control unit to execute an order back processing process in which, in the order back data, for order numbers for which the set number of days for order back deletion has elapsed, the slip cancellation flag is set to "slip cancellation", and if the slip cancellation flag in the order back data is not "slip cancellation", the number of undelivered items calculated by subtracting the number of received items from the order back data using the number of purchased items in the purchase data is cleared, and if the number of undelivered items becomes 0, the purchase completion flag is set to "purchase completion". [Effects of the Invention]

[0011] The present invention has the effect of enabling efficient management of outstanding product orders. [Brief explanation of the drawing]

[0012] [Figure 1] Figure 1 is a block diagram showing an example of the configuration of the order backlog management device according to this embodiment. [Figure 2] Figure 2 shows an example of the structure of a product master. [Figure 3] Figure 3 shows an example of a company master data structure. [Figure 4] Figure 4 is a diagram illustrating a specific example of the processing performed by the control unit of the order backlog management device according to this embodiment. [Figure 5] Figure 5 is a diagram illustrating a specific example of the processing performed by the control unit of the order backlog management device according to this embodiment. [Figure 6] Figure 6 is a diagram illustrating a specific example of the processing performed by the control unit of the order backlog management device according to this embodiment. [Figure 7A] Figure 7A is a diagram illustrating a specific example of the processing performed by the control unit of the order backlog management device according to this embodiment. [Figure 7B] Figure 7B is a diagram illustrating a specific example of the processing performed by the control unit of the order backlog management device according to this embodiment. [Modes for carrying out the invention]

[0013] Embodiments of the order backlog management device, order backlog management method, and order backlog management program according to the present invention will be described in detail below with reference to the drawings. However, the present invention is not limited to these embodiments.

[0014] [1. Overview] For example, in the pharmaceutical industry, pharmaceutical wholesalers and pharmaceutical manufacturers cooperate (connect) via pharmaceutical EDI (JD-NET or email) (hereinafter referred to as "(pharmaceutical) VAN") to place orders and make deliveries. Pharmaceutical wholesalers use VAN to daily link with pharmaceutical information service companies (e.g., Medicode Co., Ltd.) that provide pharmaceutical information.

[0015] For example, in the pharmaceutical industry, due to shortages of pharmaceuticals, there are cases where the ordered quantity is not received as ordered (e.g., distribution by ratio or partial delivery, etc.). Even when the ordered quantity is less than the ordered amount in such a situation, no notice of full payment for the order is received. Also, for orders of new products (e.g., the same product but different packages), there are cases where the old product is received.

[0016] It is necessary to refine the debit and credit information of the forecast inventory, but there are cases where the order number is not returned, so there is a problem that the remaining data cannot be managed by order number. Therefore, it is necessary to extract from the remaining order data by the target supplier and the "internal code" of the product master and perform remaining management in ascending order of the order date. Here, the "internal code" is a code that identifies the same product (new product / old product) although the product codes (GTIN, SHOCD) are different due to differences in generations (packages), etc.

[0017] In addition, there is a need for the idea of canceling order slips after a certain period (e.g., two weeks) (executing "processing regarded as a deleted slip" while maintaining the slip records) and issuing new slips, and a mechanism for deleting incomplete slips after a certain period (e.g., two weeks) is required. Here, the "processing regarded as a deleted slip" is necessary for investigating the order quantity and order timing at the next order from the quantity confirmation of the ordered quantity and the non-received quantity and the receipt ratio for the ordered quantity.

[0018] Also, since the goods are not necessarily received using the product code (GTINCD) at the time of order (there are cases where the old product is received), there are cases where the remaining order is cleared by internal code unit, and there may be receipt data without an order.

[0019] Therefore, in this embodiment, the management of the outstanding purchase orders for pharmaceuticals is preferably carried out as follows.

[0020] (1) The pharmaceutical wholesaler creates the purchase accounting data upon receipt and at the same time offsets the outstanding purchase orders in the process of placing orders → scheduled receipt → actual receipt with the pharmaceutical manufacturer using JD-NET or email (hereinafter referred to as VAN).

[0021] (2) The supplier code and product code are used to offset the outstanding purchase orders. However, since the product code returned in the receipt data (actual receipt) may be the code of a new product (different generation), a function is installed to assign an internal code to the product code linked from the pharmaceutical information providing service company (registered in the product master), and the function to offset the outstanding purchase orders is implemented. Here, the pharmaceutical information providing service company performs unified management of the SHO code and GS1 code of medical pharmaceuticals, and items necessary for the safety management of each pharmaceutical (regulation classification, storage method, etc.). When importing product data (product code, old product code) from the pharmaceutical information providing service company into the product master, the old and new products are managed, and an internal code that defines the identity of the product is automatically assigned a serial number and registered in association with the product code.

[0022] (3) Since it is necessary to cancel (delete) the purchase order after a certain period (two weeks) has passed and issue a new order, a mechanism is required to delete the outstanding orders after two weeks. Therefore, the "number of days for deleting outstanding purchase orders" is held in the company master, and the data of the outstanding purchase orders after that number of days has passed is cancelled.

[0023] In the following description, the case where the outstanding order management device of the present invention is applied to a company engaged in the pharmaceutical wholesale business will be described. However, the present invention is not limited to this, and it is also applicable to other industries such as the chemical industry.

[0024] [2. Configuration] An example of the configuration of the order backlog management device 100 according to this embodiment will be described with reference to Figure 1. Figure 1 is a block diagram showing an example of the configuration of the order backlog management device 100. Below, an example will be given of the application of the order backlog management device 100 according to this embodiment to a company engaged in the pharmaceutical wholesale business.

[0025] The order backlog management device 100 is a commercially available desktop personal computer. However, the order backlog management device 100 is not limited to stationary information processing devices such as desktop personal computers; it may also be a portable information processing device such as a commercially available notebook computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0026] The order balance 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 order balance management device 100 is connected to communicate via any communication path.

[0027] The communication interface unit 104 connects the order balance management device 100 to the network 300 via communication devices such as routers and wired or wireless communication lines such as dedicated lines, enabling communication between the network and the network. The communication interface unit 104 has the function of communicating data with other devices via communication lines. Here, the network 300 consists of the order balance management device 100 and the server 200. The system has the function of enabling communication between the system of a pharmaceutical information service company (e.g., Medicode Co., Ltd.) (not shown), the customer's system (not shown), the pharmaceutical manufacturer's system (not shown), etc., and uses, for example, the Internet or a LAN (Local Area Network). Various master data, as described later, may be stored on, for example, server 200. The order balance management device 100 is connected (cooperative) with the system of the pharmaceutical information service company (e.g., Medicode Co., Ltd.) (not shown), the customer's system (not shown), the pharmaceutical manufacturer's system (not shown), etc. via a VAN.

[0028] 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), a speaker, or a printer. The input device 112 can be a keyboard, mouse, microphone, or a monitor that works in conjunction with a mouse to provide pointing device functionality. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or mouse 112.

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

[0030] The storage unit 106 stores product master data 106a, company master data 106b, outstanding order data, incoming goods data, purchase data, etc. Figure 2 shows an example of the configuration of product master data 106a. Figure 3 shows an example of the configuration of company master data 106b.

[0031] As shown in Figure 2, the product master 106a can consist of tables that associate and register product codes, internal codes, and product names. When product data (product codes, old product codes, etc.) is imported from the pharmaceutical manufacturer's system, the product master 106a automatically assigns an internal code that manages new and old products and defines the identity of the products, and registers it in association with the product code.

[0032] Company Master 106b can be composed of tables such as the one that registers the number of days for deleting outstanding orders, as shown in Figure 3. In the example shown in the figure, the number of days for deleting outstanding orders is "14 days".

[0033] The outstanding order data may include the order number, supplier code, order date, product code, order quantity, received quantity, purchase completion flag (True: purchase completed, false: purchase not completed), and invoice cancellation flag (True: invoice cancelled, false: invoice not cancelled). The outstanding order is calculated as order quantity - received quantity.

[0034] Incoming data may include supplier code, product code, and quantity received.

[0035] Purchase data may include purchase number, supplier code, purchase date, product code, and quantity purchased.

[0036] The control unit 102 is a CPU or similar component that comprehensively controls the order balance 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.

[0037] The control unit 102 is configured to access the product master 106a, company master 106b, outstanding order data, incoming delivery data, purchase data, etc., which are stored in the storage unit 106. The product master 106a, company master 106b, outstanding order data, incoming delivery data, purchase data, etc. may be stored in another location (for example, server 200), as long as the control unit 102 can access them.

[0038] Functionally, the control unit 102 comprises a master maintenance unit 102a, a procurement processing unit 102b, an order balance processing unit 102c, and a screen display control unit 102d.

[0039] The master maintenance unit 102a performs editing such as data input, addition, modification, and updating on the product master 106a and company master 106b in response to operator operations on a master maintenance screen (not shown) displayed on the monitor 114.

[0040] The procurement processing unit 102b acquires incoming data from the pharmaceutical manufacturer's system and stores it in the storage unit 106. Based on the acquired incoming data, it generates procurement data and stores it in the storage unit 106.

[0041] The order balance processing unit 102c generates order balance data based on orders and stores it in the storage unit 106, and also updates (reconciles) the order balance data based on procurement data.

[0042] The order backorder processing unit 102c sets the "cancel invoice" flag to "cancel invoice" for order numbers in the order backorder data for which the set number of days for order backorder deletion has elapsed. If the "cancel invoice" flag in the order backorder data is not "cancel invoice", it clears the number of undelivered items calculated by subtracting the number of received items from the order backorder data using the number of purchased items in the purchase data. If the number of undelivered items becomes 0, it sets the "purchase completion" flag to "purchase completion".

[0043] In this case, the order backorder processing unit 102c may sequentially compare the purchase data for each purchase number with the order backorder data in ascending order of order date, and if the order backorder data does not have a purchase completion flag of "Purchase Completed," the unit may also set the purchase completion flag to "Purchase Completed" if the order backorder data does not have a "Order Cancellation" flag, and the supplier code and product code of the purchase data and the order backorder data match. If the number of undelivered items in the purchase data is 0, the unit may set the purchase completion flag to "Purchase Completed." Alternatively, if the supplier code and product code of the purchase data and the order backorder data do not match, and the supplier code and the internal code linked by the product code in the product master 106a match, the unit may set the purchase completion flag to "Purchase Completed" if the number of undelivered items in the purchase data is 0.

[0044] The screen display control unit 102e controls the display of various screens (for example, the master maintenance screen, etc.) displayed on the monitor 114 and the acceptance of inputs on the screen.

[0045] [3. Specific examples of processing] A specific example of the processing of the control unit 102 of the order backlog management device 100 according to this embodiment will be explained with reference to Figures 1 to 7. Figures 4 to 7B are diagrams illustrating a specific example of the processing of the control unit 102 of the order backlog management device 100 according to this embodiment (processing flow when VAN is linked).

[0046] (i) Initial data Refer to Figure 4 to explain the initial data. We will assume that the company master 106b, product master 106a, and outstanding order data are pre-registered in the storage unit 106, as shown in Figure 4. In the following explanation, the processing date will be 2024 / 10 / 10.

[0047] Company master data 106b has "14 days" registered as the number of days for deleting outstanding orders.

[0048] Figure 4(A) shows an example of data in product master 106a. Product master 106a has fields for product code, internal code, and product name. In the example shown in the figure, the first row is product code "SHO101-7", internal code "AA101", product name "Pharmaceutical A (old)", the second row is product code "SHO101-8", internal code "AA101", product name "Pharmaceutical A (new)", the third row is product code "SHO201", internal code "BB201", product name "Pharmaceutical B (old)", the fourth row is product code "SHO202", internal code "BB201", product name "Pharmaceutical B (new)", and the fifth row is product code "SHO999", internal code "ZZ999", product name "Equipment".

[0049] Figure 4(B) shows an example of outstanding order data. Outstanding order data includes the following fields: order number, supplier code, order date, product code, order quantity, received quantity, purchase completion flag, and invoice cancellation flag. In the example shown in the figure, the first row contains the order number "HA001", supplier code "00001", order date "2024 / 9 / 26", product code "SHO101-7", order quantity "30", received quantity "0", purchase completion flag "false", and invoice cancellation flag "false". Outstanding order is calculated as order quantity - received quantity.

[0050] (ii) Importing incoming goods / recording purchases Refer to Figure 5 to explain the import of incoming data and accounting for purchases. The purchase processing unit 102b acquires incoming data from the pharmaceutical manufacturer's system and stores it in the storage unit 106. Based on the acquired incoming data, it generates and updates purchase data and stores it in the storage unit 106.

[0051] Figure 5(A) shows an example of incoming data. The incoming data includes the following fields: supplier code, product code, and quantity received. In the example shown in the figure, the first row is supplier code "00001", product code "SHO101-8", and quantity received "90", the second row is supplier code "00001", product code "SHO201", and quantity received "50", and the third row is supplier code "00001", product code "SHO999", and quantity received "100".

[0052] Figure 5(B) shows an example of purchase data. The purchase data includes the following fields: purchase number, supplier code, purchase date, product code, and quantity purchased. In the example shown in the figure, the first row is: purchase number "SII001", supplier code "00001", purchase date "2024 / 10 / 10", product code "SHO101-8", quantity purchased "90", the second row is: purchase number "SII001", supplier code "00001", purchase date "2024 / 10 / 10", product code "SHO201", quantity purchased "50", and the third row is: purchase number "SII001", supplier code "00001", purchase date "2024 / 10 / 10", product code "SHO999", quantity purchased "100". As shown in the third line, purchase data is generated even if there are no outstanding orders (as shown in the outstanding order data in Figure 4(B), there are no outstanding orders for product code "SHO999").

[0053] The outstanding order data is reconciled using the purchase data as follows:

[0054] (iii) Settlement of outstanding orders The process of clearing outstanding orders will be explained with reference to Figures 6 to 7B. Figure 6 is an explanatory diagram for explaining the clearing of outstanding orders, and Figures 7A and 7B are diagrams for explaining the process of clearing outstanding orders. The outstanding order processing unit 102c sets the "cancel invoice" flag to "cancel invoice" for order numbers in the outstanding order data for which the set number of days for clearing outstanding orders has elapsed. If the "cancel invoice" flag in the outstanding order data is not "cancel invoice", it clears the number of undelivered items calculated by subtracting the number of received items from the number of orders in the outstanding order data using the number of purchases in the purchase data, and sets the "purchase completion" flag to "purchase completion" when the number of undelivered items becomes 0. Furthermore, the order backorder processing unit 102c may also compare the purchase data by purchase number with the order backorder data in ascending order of order date, and if the order backorder data does not have a purchase completion flag of "Purchase Completed," the unit may also set the purchase completion flag to "Purchase Completed." If the order cancellation flag for the order backorder data is not "Order Cancelled," and the supplier code and product code of the purchase data and the order backorder data match, the unit may subtract the number of undelivered items in the order backorder data from the number of purchases in the purchase data, and if the number of undelivered items becomes 0, the unit may set the purchase completion flag to "Purchase Completed." Alternatively, if the supplier code and product code of the purchase data and the order backorder data do not match, and the supplier code and the internal code associated with the product code in the product master 106a match, the unit may subtract the number of undelivered items in the order backorder data from the number of purchases in the purchase data, and if the number of undelivered items becomes 0, the unit may set the purchase completion flag to "Purchase Completed."

[0055] In Figure 6, (A) shows purchase data, and (B) shows outstanding order data. Using the product code of the outstanding order data as the key, internal data is retrieved from product master 106a. Among the group of products in the outstanding order data that have the same internal code as the internal data linked to the "product code" in the purchase data in product master 106a, the outstanding order data is cleared using the purchase data for those from the same supplier, in ascending order of "order date" > order number. The clearing completion flag is updated to "True" when the outstanding order, calculated as order quantity - received quantity, becomes "0".

[0056] For example, in the first row of the purchase data, the purchase number "SII001" and product code "SHO101-8" are linked to the internal code "AA101" in product master 106a. Therefore, product code "SHO101-7," which is linked to the internal code "AA101," will also be subject to reconciliation. Consequently, product codes "SHO101-8" and "SHO101-7" in the outstanding order data will be subject to reconciliation. Note that in the example shown in Figure 6(B), since "SHO101-7" does not exist, product code "SHO101-8" will be subject to reconciliation.

[0057] Furthermore, the product code "SHO002" for the purchase number "SII002" in the first row of the purchase data is linked to the internal code "BB201" in product master 106a. Therefore, the product code "SHO201" linked to the internal code "BB201" is also subject to reconciliation. Consequently, the product codes "SHO202" and "SHO201" in the outstanding order data are subject to reconciliation.

[0058] For the voucher cancellation flag, the order data is deleted by setting it to "True" based on the number of days for deleting outstanding orders in company master 106b. The voucher cancellation flag is set to "True" when the processing date - the order date of the outstanding orders data is greater than or equal to the number of days for deleting outstanding orders in company master 106b. For the order number "HA001" in the first row of the outstanding orders data, the processing date "2024 / 10 / 10" - the order date "2024 / 9 / 26" is greater than or equal to the number of days for deleting outstanding orders in company master 106b "14", so the voucher cancellation flag is set to "True".

[0059] The first line of the purchase data, purchase number "SII001," has product code "SHO101-8" and quantity "90 units." Therefore, the quantities received for order numbers "HA002" and "HA003" in the second and third lines of the outstanding order data are matched with "20 units" and "70 units," respectively, and the match completion flag is updated to "True." The fourth line, order number "HA004," is from a different supplier and is therefore not included in the match.

[0060] The purchase number "SII002" on the second line of the purchase data has product code "SHO201" and quantity "50". Therefore, the quantities received for order numbers "HA006" and "HA007" on the sixth and seventh lines of the outstanding order data are set to "30" and "20", respectively, and the settlement is performed, updating the settlement completion flag for order number "HA006" to "True". The settlement completion flag for order number "HA007" remains "false" because the settlement is incomplete. Order number "HA008" on the eighth line is excluded from settlement because the slip cancellation flag is "True".

[0061] The flow of the order balance reconciliation process in Figures 7A and 7B is explained below. The process loops through the purchase data by purchase number (step S1). The data is processed in ascending order of purchase number. The process loops through the order balance data by order number (step S2). For the order balance data with the purchase completion flag = False, the data is processed in ascending order of order date > order number.

[0062] The system determines whether the order cancellation flag for outstanding order data is True (Step S3). If True, the data is excluded from the reconciliation process (Step S4), and the system proceeds to the next loop (Step S2).

[0063] In step S3, if the slip cancellation flag is False, it is determined whether the supplier code and product code match (step S5). If they match (if True), the number of undelivered items in the outstanding order data is cleared from the number of purchased items in the purchase data (step S4), and the process moves to the next loop (step S2). If the number of undelivered items (outstanding order) is 0, the purchase completion flag is updated to "True". Here, the number of undelivered items (outstanding order) = number of ordered items - number of received items. For example, if the number of purchased items is 90 and the number of undelivered items is 20, the remaining number of purchased items is 90 - 70 = 20, and the process moves to the next clearing step (loop).

[0064] In step S3, if there is no match (false), it is determined whether the supplier code and internal code match (step S7). If there is a match (true), the number of undelivered items in the outstanding order data is cleared from the number of purchased items in the purchase data (step S8), and the process moves to the next loop (step S2). If the number of undelivered items (outstanding order) is 0, the purchase completion flag is updated to "True". Here, the number of undelivered items (outstanding order) = number of ordered items - number of received items. For example, if the number of purchased items is 90 and the number of undelivered items is 20, the number of undelivered items is calculated as 90 - 70 = 20, and the process moves to the next clearing step (loop).

[0065] In step S7, if there is no match (false), it is determined whether the remaining purchase quantity in the purchase data is 0 (step S9). If the remaining purchase quantity in the purchase data is 0 (True), the remaining purchase quantity is updated to the number of received items in the remaining order data (step S10), and the process moves to the next loop (step S1). If the remaining purchase quantity in the purchase data is not 0 (True), the process moves to the next loop (step S1).

[0066] As described above, the product management device of this embodiment is configured to provide access to a product master 106a in which a product code is registered in association with an internal code for defining the identity of a product, order balance data including order number, supplier code, order date, product code, internal code, order quantity, received quantity, purchase completion flag indicating whether the purchase is complete or not, and slip cancellation flag indicating whether the slip is canceled or not, and purchase data including purchase number, supplier code, purchase date, product code, and purchase quantity. In the order balance data, for order numbers for which the set number of days for order balance deletion has elapsed, the slip cancellation flag is set to "slip cancellation". If the slip cancellation flag in the order balance data is not "slip cancellation", the order balance processing unit 102c clears the number of undelivered items calculated by subtracting the number of received items from the order balance data using the number of purchased items in the purchase data, and sets the purchase completion flag to "purchase complete" when the number of undelivered items = 0.

[0067] [4. 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 SDGs Goals 8 and 9.

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

[0069] Furthermore, this embodiment can contribute to strengthening control and governance, thereby enabling contributions to SDG Goal 16.

[0070] [5. 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.

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

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

[0073] Furthermore, with respect to the order balance management device 100, each component shown in the illustration is a functional concept and does not necessarily need to be physically configured as shown.

[0074] For example, the processing functions of the order balance management device 100, particularly those performed by the control unit 102, may be implemented entirely or partially by a CPU 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 the information processing device to execute the processing described in this embodiment, and is mechanically read by the order balance management device 100 as needed. That is, a storage unit such as ROM or HDD (Hard Disk Drive) stores a computer program that works in cooperation with the OS to give instructions to the CPU and perform various processing tasks. This computer program is executed by being loaded into RAM and works in cooperation with the CPU to constitute the control unit.

[0075] Furthermore, this computer program may be stored on an application program server connected to the order balance management device 100 via any network, and it is possible to download all or part of it as needed.

[0076] Furthermore, the 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.

[0077] 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 procedures for reading the recording medium in each device shown in the embodiments, as well as the installation procedures after reading, well-known configurations and procedures can be used.

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

[0079] Furthermore, the order backlog management device 100 may be configured as a known personal computer or workstation or other information processing device, or as an information processing device to which any peripheral devices are connected. Alternatively, the order backlog management device 100 may be implemented by installing software (including programs or data, etc.) on the device that enables the processing described in this embodiment.

[0080] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, 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. [Explanation of Symbols]

[0081] 100 Order backlog management device 102 Control Unit 102a Master Maintenance Department 102b Purchasing Processing Unit 102c Order Backlog Processing Unit 102d Screen display control unit 104 Communication Interface Section 106 Storage section 106a Product Master 106b Company Master 108 Input / Output Interface Section 112 Input device 114 Output device 200 servers 300 Networks

Claims

1. An order balance management device equipped with a control unit, The control unit, A product master is registered by associating the product code with an internal code that defines the identity of the product. Order balance data including order number, supplier code, order date, product code, internal code, order quantity, received quantity, purchase completion flag indicating whether the purchase is complete or not, and order cancellation flag indicating whether the order is cancelled or not, Purchase data including purchase number, supplier code, purchase date, product code, and quantity purchased, It is configured to be accessible, An order backlog management device characterized by having order backlog processing means that, in the order backlog data, sets the slip cancellation flag to "slip cancellation" for order numbers for which the set number of days for order backlog deletion has elapsed, and if the slip cancellation flag in the order backlog data is not "slip cancellation", clears the number of undelivered items calculated by subtracting the number of received items from the order backlog data using the number of purchased items in the purchase data, and sets the purchase completion flag to "purchase completed" when the number of undelivered items becomes 0.

2. The aforementioned order processing means is: For each purchase number in the aforementioned purchase data, compare it sequentially with the remaining order data in ascending order of order date, where the purchase completion flag is not "purchase completed," for each order number. The order back management device according to claim 1, characterized in that, if the slip cancellation flag for the outstanding order data is not "slip cancellation", and the supplier code and product code of the purchase data and the outstanding order data match, the number of undelivered items in the outstanding order data is deducted from the number of purchases in the purchase data, and if the number of undelivered items becomes 0, the purchase completion flag is set to "purchase completed", and if the supplier code and product code of the purchase data and the outstanding order data do not match, and the supplier code of the purchase data and the internal code associated with the product code in the product master match, the number of undelivered items in the outstanding order data is deducted from the number of purchases in the purchase data, and if the number of undelivered items becomes 0, the purchase completion flag is set to "purchase completed".

3. The order backlog management device according to claim 1 or 2, characterized in that the aforementioned product is a pharmaceutical product.

4. A method for managing outstanding orders, which is performed by an information processing device equipped with a control unit, The control unit, A product master is registered by associating the product code with an internal code that defines the identity of the product. Order balance data including order number, supplier code, order date, product code, internal code, order quantity, received quantity, purchase completion flag indicating whether the purchase is complete or not, and order cancellation flag indicating whether the order is cancelled or not, Purchase data including purchase number, supplier code, purchase date, product code, and quantity purchased, It is configured to be accessible, The control unit is executed as follows: A method for managing outstanding orders, characterized in that, for order numbers in the outstanding order data for which the set number of days for deletion of outstanding orders has elapsed, the slip cancellation flag is set to "slip cancellation", and if the slip cancellation flag in the outstanding order data is not "slip cancellation", the number of undelivered items calculated by subtracting the number of received items from the number of orders in the outstanding order data is cleared by the number of purchased items in the purchase data, and if the number of undelivered items becomes 0, the purchase completion flag is set to "purchase completion".

5. An order balance management program to be executed by an information processing device equipped with a control unit, The control unit, A product master is registered by associating the product code with an internal code that defines the identity of the product. Order balance data including order number, supplier code, order date, product code, internal code, order quantity, received quantity, purchase completion flag indicating whether the purchase is complete or not, and order cancellation flag indicating whether the order is cancelled or not, Purchase data including purchase number, supplier code, purchase date, product code, and quantity purchased, It is configured to be accessible, The control unit, An order back management program that executes an order back processing step, in which, for order numbers in the order back data for which the set number of days for order back deletion has elapsed, the slip cancellation flag is set to "slip cancellation", and if the slip cancellation flag in the order back data is not "slip cancellation", the number of undelivered items calculated by subtracting the number of received items from the order back data using the number of purchased items in the purchase data is cleared, and if the number of undelivered items = 0, the purchase completion flag is set to "purchase completion".

Images