Commodity management apparatus, commodity management method, and commodity management program

Abstract

To provide a commodity management apparatus, a commodity management method, and a commodity management program configured to manage the same commodities received from and manufactured by different manufacturers, for each manufacturer, using one code for the commodities, thereby facilitating highly accurate management.SOLUTION: A commodity management apparatus equipped with a control unit is allowed to access receipt data, which is formed by associating a commodity code of a commodity to be received with the quantity thereof, and a commodity master in which the commodity code is associated with a transfer commodity code for setting a management transfer commodity to the commodity. The control unit includes: acquisition means which acquires the receipt data at each receipt of the commodity; determination means which determines whether the commodity code included in the receipt data is a commodity code associated with the transfer commodity code in the commodity master; and generation means which generates, when the commodity code included in the receipt data is a commodity code associated with the transfer commodity code, transfer data for transferring the quantity of the commodity included in the receipt data to the quantity of the transfer commodity.SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] In the food manufacturing industry, there are cases where the same product is manufactured at multiple locations, or where the company outsources production to secure supply and purchases OEM (Original Equipment Manufacturing) products. In these cases, all products will be the same when sold, so inventory management requires them to be managed as a single type of product, but it is also necessary to manage OEM products and products manufactured at each location separately.

[0003] For example, Patent Document 1 discloses that product categories (for example, the same type but different volumes) are set for products received from multiple suppliers, and product category codes are assigned to the receiving information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 2018-181238 Summary of the Invention [Problem to be solved by the invention]

[0005] When accepting and selling the same products manufactured by different manufacturers, it is necessary to understand the inventory quantity and cost of the products at the time of sale. However, the cost of completing the product may differ depending on the manufacturer, and it is also necessary to understand these costs. For example, OEM products and products manufactured in the company's own factory can be managed by each manufacturer by managing them with different codes. In this case, however, since the inventory quantity is also separated by the separate product codes, operation becomes difficult and it may be difficult to understand the cost of products manufactured in the company's own factory. It is also possible to manage products with the same product code at the time of sale and additionally assign lot numbers for each manufacturer, but in this case, it may be difficult to evaluate the inventory of products from different lots as the same product.

[0006] The present invention has been made in consideration of the above, and aims to provide a product management device, a product management method, and a product management program that can easily perform highly accurate management by managing the products by integrating them into a single code while still managing them by manufacturer, even when the same products manufactured by different manufacturers are received. [Means for solving the problem]

[0007] In order to solve the above-mentioned problems and achieve the objective, the product management device of the present invention is a product management device equipped with a control unit, which is capable of accessing acceptance data that corresponds the product code and quantity of the product to be accepted, and a product master that corresponds the product code with a transfer product code that sets a transfer product for management for the product, and the control unit is characterized by comprising: an acquisition means that acquires the acceptance data each time a product is accepted; a determination means that determines whether the product code included in the acceptance data is the product code to which the transfer product code is associated in the product master; and a generation means that, when the product code included in the acceptance data is the product code to which the transfer product code is associated, generates transfer data that transfers the quantity of the product included in the acceptance data to the quantity of the transfer product.

[0008] In addition, the product management device of the present invention is characterized in that the generation means generates the transfer data including a dispensing record in which dispensing is set in the receipt / payment category that distinguishes between the dispensing of the product and the receiving of the transfer product, and in which the quantity of the product included in the receiving data is dispensed, and a receiving record in which receiving is set in the receipt / payment category, and in which the quantity of the transfer product is received.

[0009] In addition, the product management device of the present invention is further capable of accessing current inventory data having records indicating the current inventory status for each product, and is characterized in that the control unit, each time the acquisition means acquires the receipt data, generates temporary inventory data by adding the received quantity to the record in the current inventory data corresponding to the acquired receipt data, and when the generation means generates the transfer data, updates the current inventory data by subtracting the quantity of the product in the withdrawal record for which the receipt / payment category of the transfer data is set to withdrawal from the corresponding record in the temporary inventory data, and adding the quantity of the transferred product in the receipt record for which the receipt / payment category of the transfer data is set to acceptance to the corresponding record in the temporary inventory data.

[0010] In addition, the product management device of the present invention is characterized in that the acceptance data includes purchase data when the product manufactured by a subcontractor is accepted and transfer data when the product manufactured in-house is accepted, the purchase data corresponds to the purchase quantity purchased from the subcontractor with the subcontractor product code of the product at the subcontractor, the transfer data corresponds to the quantity received from the manufacturing location with the manufacturing location product code at the manufacturing location of the product, and the generation means transfers the quantity of the product included in the purchase data to the quantity of the transfer product, transfers the subcontractor product code to the product code of the transfer product, and generates transfer data that transfers the quantity of the product included in the transfer data to the quantity of the transfer product and transfers the manufacturing location product code to the product code of the transfer product.

[0011] Furthermore, the product management device of the present invention is characterized in that the purchase data further includes a purchase price of the product, the movement data further includes a stock receipt price of the product, and the control unit further includes a calculation means for calculating the cost of the product manufactured by the subcontractor based on the purchase quantity and the purchase price, calculating the cost of the product manufactured in-house based on the stock receipt quantity and the stock receipt price, and calculating the cost of the transfer product based on the received quantity of the transfer product based on the purchase quantity and the stock receipt quantity and the received price of the transfer product based on the purchase price and the stock receipt price.

[0012] In addition, the product management device of the present invention is further capable of accessing monthly inventory data including the number of purchases and the purchase amount for each month, the number of previously recorded inventories and the inventory amount for each month, and the number of stocks and inventory amount of the transfer product at the end of the previous month, and the calculation means calculates the cost of the transfer product at the end of the current month based on the number of purchases and the number of previously recorded inventories for each month, the amount of costs to be included in the current month based on the purchase amount for each month and the previously recorded inventory amount for each month, and the number of stocks and inventory amount of the transfer product at the end of the previous month.

[0013] In addition, the product management method of the present invention is a product management method executed in a product management device equipped with a control unit, wherein the control unit has access to acceptance data that associates the product code and quantity of the product to be accepted, and a product master that associates the product code with a transfer product code that sets a transfer product for management for the product, and is characterized in that it includes: an acquisition step executed by the control unit to acquire the acceptance data for each product acceptance; a determination step to determine whether the product code included in the acceptance data is the product code to which the transfer product code is associated in the product master; and a generation step to generate transfer data that transfers the quantity of the product included in the acceptance data to the quantity of the transfer product when the product code included in the acceptance data is the product code to which the transfer product code is associated.

[0014] In addition, the product management program of the present invention is a product management program to be executed by a product management device equipped with a control unit, wherein the control unit is capable of accessing acceptance data that associates the product code and quantity of the product to be accepted, and a product master that associates the product code with a transfer product code that sets a transfer product for management for the product, and causes the control unit to execute an acquisition step of acquiring the acceptance data for each product acceptance, a determination step of determining whether the product code included in the acceptance data is the product code to which the transfer product code is associated in the product master, and a generation step of generating transfer data that transfers the quantity of the product included in the acceptance data to the quantity of the transfer product if the product code included in the acceptance data is the product code to which the transfer product code is associated. [Effects of the Invention]

[0015] According to the present invention, even when the same products manufactured by different manufacturers are received, it is possible to manage the products by integrating them into a single code while still managing them by manufacturer, thereby achieving the effect of easily managing with high accuracy. [Brief explanation of the drawings]

[0016] [Figure 1] FIG. 1 is a block diagram illustrating an example of a configuration of a product management device according to an embodiment. [Figure 2A] FIG. 2A is a diagram illustrating an example of application of the product management device according to the embodiment. [Figure 2B] FIG. 2B is a schematic diagram illustrating processing by the product management device according to the embodiment. [Figure 3] FIG. 3 is a flowchart illustrating an example of processing by the product management device according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a product master according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of purchase data according to the embodiment. [Figure 6]FIG. 6 is a diagram illustrating an example of a temporary image of current inventory data according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of product transfer data according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating an example of current inventory data according to the embodiment. [Figure 9] FIG. 9 is a diagram illustrating an example of monthly inventory data according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of monthly inventory data according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of current inventory data according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of purchase data according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of a temporary image of current inventory data according to the embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of product transfer data according to the embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of current inventory data according to the embodiment. [Figure 16] FIG. 16 is a diagram illustrating an example of monthly inventory data according to the embodiment. [Figure 17] FIG. 17 is a diagram illustrating an example of current inventory data according to the embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of movement data according to the embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of a temporary image of current inventory data according to the embodiment. [Figure 20] FIG. 20 is a diagram illustrating an example of product transfer data according to the embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of current inventory data according to the embodiment. [Figure 22] FIG. 22 is a diagram illustrating an example of monthly inventory data according to the embodiment. [Figure 23] FIG. 23 is a diagram illustrating an example of inventory valuation unit price data according to the embodiment. [Figure 24] FIG. 24 is a diagram illustrating an example of monthly inventory data according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0017] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of a product management device, a product management method, and a product management program according to the present invention will be described in detail below with reference to the accompanying drawings. However, the present invention is not limited to the preferred embodiments.

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

[0019] As shown in FIG. 1, the product management device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input / output interface unit 108, and is communicatively connected to a server 200 (e.g., a Web server) that stores various data (e.g., the data stored in the memory unit 106, which may be the data described below) via a network 300 (e.g., the Internet, an intranet, a LAN (Local Area Network), etc.).

[0020] The components of the product management device 100 are communicably connected via any communication path.

[0021] The product management device 100 may be, for example, a stationary device such as a desktop personal computer, or may be a portable device such as a notebook personal computer, a PDA (Personal Digital Assistant), a smartphone, or a tablet personal computer.

[0022] The control unit 102 is a CPU or the like that performs overall control of the product 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 processes based on these stored programs.

[0023] The control unit 102 conceptually includes an acquisition unit 102a, a determination unit 102b, a generation unit 102c, an update unit 102d, a calculation unit 102e, and the like.

[0024] The acquiring unit 102a acquires receiving data for each receipt of goods. The receiving data is data that associates the product code and quantity of the received goods, and includes purchase data when goods manufactured by a subcontractor are received and transfer data when goods manufactured in-house are received. The purchase data associates the number of goods purchased from the subcontractor (e.g., an OEM manufacturer) with the subcontractor product code of the product, and may also include the supplier, product name, purchase price, purchase amount, etc. The purchase amount is an amount obtained by multiplying the purchase quantity by the purchase price. The transfer data associates the number of goods received from the manufacturing location (e.g., the company's own factory) with the manufacturing location product code, and may also include the manufacturing location, product name, unit cost, cost amount, etc. The cost amount is an amount obtained by multiplying the number of goods received by the manufacturing location.

[0025] The determination unit 102b determines whether the product code included in the acceptance data is a product code associated with a transfer product code in the product master. The product master associates product codes with transfer product codes that set transfer products for management purposes for the product, and may also include product names, etc. Specifically, the product master has a record in which the consignee product code at the product's consignee is associated with the transfer product code, and a record in which the manufacturing location product code at the product's manufacturing location is associated with the transfer product code. The transfer product is a product name that the seller uses to unify and manage the products when receiving the same product from different manufacturers. The transfer product code is a product code set for the transfer product.

[0026] The determination unit 102b determines whether the consignee product code included in the purchase data acquired by the acquisition unit 102a is a code associated with a transfer product code in the product master. The determination unit 102b also determines whether the manufacturing location product code included in the movement data acquired by the acquisition unit 102a is a code associated with a transfer product code in the product master.

[0027] The generating unit 102c generates transfer data for transferring the quantity of the product included in the receipt data to the quantity of the transfer product when the product code included in the receipt data is a product code associated with a transfer product code. The transfer data includes a payment record in which payment is set to "payment" and the quantity of the product included in the receipt data is transferred, and a receipt record in which payment is set to "payment" and the quantity of the transfer product is transferred, the same as the payment record.

[0028] The generation unit 102c generates transfer data that transfers the quantity of the product included in the purchase data to the quantity of the transfer product, transfers the consignee product code to the product code of the transfer product, transfers the quantity of the product included in the transfer data to the quantity of the transfer product, and transfers the manufacturing location product code to the product code of the transfer product.

[0029] Each time the acquiring unit 102a acquires receipt data, the updating unit 102d generates temporary inventory data by adding the received quantity to the record in the current inventory data corresponding to the acquired receipt data, and when the generating unit 102c generates transfer data, the updating unit 102d updates the current inventory data by subtracting the quantity of the product in the withdrawal record for which the receipt / payment category of the transfer data is set to "payment" from the corresponding record in the temporary inventory data, and adding the quantity of the transferred product in the receipt record for which the receipt / payment category of the transfer data is set to "payment" to the corresponding record in the temporary inventory data. The current inventory data has records that indicate the current inventory status for each product.

[0030] Here, the current inventory data includes records containing the consignee product code and quantity of the product corresponding to the purchase data (products purchased from the consignee), records containing the manufacturing location product code and quantity of the product corresponding to the transfer data (products manufactured in-house and stored), and records containing the transfer product code and quantity of the transfer product.

[0031] The calculation unit 102e calculates the cost of goods manufactured by the subcontractor based on the purchase quantity and purchase amount included in the purchase data, calculates the cost of goods manufactured in-house based on the inventory quantity and inventory amount included in the transfer data, and calculates the cost of the transfer goods based on the number of transfer goods received based on the purchase quantity and inventory quantity and the receipt amount of the transfer goods based on the purchase amount and inventory amount.

[0032] The calculation unit 102e calculates the cost of the transfer product at the end of the current month based on the number of costs to be included in the current month, which is based on the monthly purchase quantity and monthly inventory quantity, the amount of costs to be included in the current month, which is based on the monthly purchase amount and monthly inventory amount, and the number and amount of stock of the transfer product at the end of the previous month. Here, the monthly purchase quantity and purchase amount, the monthly inventory quantity and inventory amount, and the number and amount of stock of the transfer product at the end of the previous month are included in the monthly inventory data. The monthly inventory data is updated by the update unit 102d.

[0033] The communication interface unit 104 communicably connects the product management device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line.

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

[0035] The storage unit 106 stores a product master 106a, purchase data 106b, movement data 106c, product transfer data 106d, inventory data 106e, and inventory evaluation unit price data 106f.

[0036] The product master 106a has records that associate product codes (consignee product codes or manufacturing location product codes) with transfer product codes, and is referenced by the determination unit 102b. The product master 106a can be changed and updated as needed.

[0037] The purchase data 106b is an example of receiving data, and is acquired and stored by the acquisition unit 102a when a product is purchased from a consignee.

[0038] The movement data 106c is an example of receipt data, and is acquired and stored by the acquisition unit 102a when a product manufactured in-house is stored in stock.

[0039] The product transfer data 106d is generated by the generating unit 102c and stored.

[0040] The inventory data 106e includes current inventory data and monthly inventory data, and is updated by the update unit 102d.

[0041] The inventory evaluation unit price data 106f has records that associate the product code of a product with the cost price, and stores the cost price for each product calculated by the calculation unit 102e.

[0042] An input device 400 and an output device 500 are connected to the input / output interface unit 108. The output device 500 includes display devices such as a display or projector, audio devices such as speakers, printing devices such as printers, as well as devices that allow downloading in data file format. The data file format may be a file format known in the art, such as PDF, CSV, document file, spreadsheet file, or text file. The input device 400 may include a keyboard, mouse, microphone, or a monitor that functions as a pointing device in cooperation with a mouse.

[0043] [2. Specific Examples] Hereinafter, the information processing by the product management device 100 according to this embodiment will be described using a specific example with reference to FIGS. 2A to 24. FIG.

[0044] Fig. 2A is a diagram showing an example of application of the product management device 100 according to this example, and Fig. 2B is a schematic diagram showing processing by the product management device 100 according to this example.

[0045] For example, product management device 100 is placed in the commercial warehouse shown in Figure 2A and manages products purchased from OEM manufacturers 1, 2, and 3, and products received from company factories 1 and 2. The same products are manufactured at OEM manufacturers 1, 2, 3, company factories 1, and 2. The commercial warehouse receives the same products manufactured by multiple manufacturers (OEM manufacturers 1, 2, 3, company factories 1, and 2) and stores the received products until they are sold.

[0046] Here, even for the same product, products manufactured by multiple manufacturers may have different costs. For example, as shown in Figure 2A, the cost at OEM manufacturer 1 may be "500 yen," the cost at OEM manufacturer 2 may be "600 yen," the cost at OEM manufacturer 3 may be "400 yen," the cost at factory 1 may be "350 yen," and the cost at factory 2 may be "300 yen." Furthermore, the costs of such manufacturers may fluctuate.

[0047] For such products, the product management device 100 registers slips using product codes (consignee product codes or manufacturing site product codes) for each OEM and factory for the ordering, planned receipt, and receipt stages, and automatically transfers them to the seller's product code (transfer product code) upon receipt. This allows the inventory quantity in the commercial warehouse to be grasped using the seller's product code, and also enables cost management for each manufacturer.

[0048] 2A, the product management device 100 manages the product code (consignee product code) of products manufactured by OEM manufacturer 1 as "A001," the product code (consignee product code) of products manufactured by OEM manufacturer 2 as "A002," and the product code (consignee product code) of products manufactured by OEM manufacturer 3 as "A003." The product management device 100 also manages the product code (manufacturing location product code) of products manufactured by factory 1 as "B001," and the product code (manufacturing location product code) of products manufactured by factory 2 as "B002."

[0049] As shown in Fig. 2B, when purchasing from an OEM partner, the product management device 100 (1) acquires purchase data in response to purchase input, (3) generates product transfer data, and (4) updates inventory data. Furthermore, the product management device 100 (2) acquires movement data in response to the arrival of manufactured products at the company's own factory, (3) generates product transfer data, and (4) updates inventory data. Furthermore, the product management device 100 generates inventory evaluation unit price data through a cost calculation process that calculates costs based on the receipt and payment data of (1) to (4).

[0050] FIG. 3 is a flowchart illustrating an example of processing by the product management device according to the embodiment.

[0051] When receiving a product, the product management device 100 transfers current inventory data (current stock data and monthly inventory data) to the update unit 102d for data processing (S1).

[0052] The acquiring unit 102a acquires receiving data including product codes, quantities, etc. in response to purchase input or transfer receiving input input entered via the input device 400 (S2). The updating unit 102d creates temporary inventory data from the inventory data based on the receiving data acquired by the acquiring unit 102a.

[0053] The determining unit 102b obtains the product code included in the acceptance data obtained by the obtaining unit 102a, and determines whether or not a transfer product code is set for the obtained product code by referring to the product master (S3).

[0054] Here, if a transfer product code is set in the product code (S3, Yes), the generation unit 102c generates product transfer data including a dispensing record indicating the dispensing of the accepted product and a receiving record indicating the receiving of the transfer product (S4).

[0055] The update unit 102d updates the inventory data by subtracting the temporary inventory data using the withdrawal record in the product transfer data and adding the temporary inventory data using the receipt record in the product transfer data (S5). Note that, if it is determined in S3 that a transfer product code is not set in the product code (S3, No), the update unit 102d does not process the temporary inventory data and confirms it as inventory data.

[0056] The calculation unit 102e calculates the cost price of each manufacturer of the products manufactured by the multiple manufacturers and the cost price of the transfer product that integrates the products manufactured by each manufacturer, based on the inventory data (S6).

[0057] Below, detailed processing will be explained for the transfer of inventory data, processing according to purchase input, processing according to transfer receipt input, and cost calculation processing, using the commercial warehouse shown in FIG. 2A as an example.

[0058] Fig. 4 is a diagram showing an example of a product master according to the embodiment. In the product master used in the product management device 100 arranged in the commercial warehouse shown in Fig. 2A, for example, as shown in Fig. 4, records each consisting of a combination of "product code," "product name," and "transfer product code" are registered for each product code. The product master registers product codes for all products handled in the commercial warehouse, and has records corresponding to consignee product codes, manufacturing location product codes, and transfer product codes.

[0059] Since "OEM product 1" managed with product code "A001", "OEM product 2" managed with product code "A002", "OEM product 3" managed with product code "A003", "in-house manufactured product 1" managed with product code "B001", and "in-house manufactured product 2" managed with product code "B002" are the same product, a transfer product code "C001" is set for these records. Product code "C001" is the product code for "transfer product 1", and no transfer product code is set. The product management device 100 manages the same products manufactured by multiple manufacturers using the product master shown in FIG. 4.

[0060] (Transfer of inventory data) The transfer of inventory data is performed, for example, upon completion of monthly closing processing, and the previous month's inventory data is transferred to the current month's inventory data. Figure 5 is a diagram showing an example of purchase data according to an embodiment. Below, we will explain an example in which a product corresponding to the purchase data shown in Figure 5 is not shipped and is transferred as the previous month's inventory data. For example, when a purchase slip is entered through purchase input, the acquisition unit 102a acquires the purchase data shown in Figure 5. The purchase data acquired by the acquisition unit 102a stores records consisting of combinations of "purchase number," "purchase date," "supplier," "warehouse," "line number," "product code," "product name," "purchase price," "quantity," and "purchase amount," as shown in Figure 5.

[0061] The purchase data record shown in Figure 5 indicates that 50 units of "OEM Product 1" with product code "A001" were purchased from "OEM Customer 1" on "2023 / 12 / 12," the unit purchase price was "400 yen," and the purchase amount was "20,000 yen."

[0062] Fig. 6 is a diagram showing an example of a temporary image of current inventory data according to the embodiment. For example, as shown in Fig. 6, the current inventory data stores records each consisting of a combination of "warehouse," "product code," "product name," and "quantity." When the purchase data shown in Fig. 5 is acquired, the update unit 102d generates temporary inventory data in which the quantity of product code "A001" is updated to "50," as shown in Fig. 6.

[0063] 5 is acquired, the determination unit 102b acquires the product code included in the purchase data and performs a determination process based on the product master. For example, the determination unit 102b refers to the product master shown in FIG. 4 and determines that the transfer product code "C001" is set for the product code "A001" in the purchase data shown in FIG.

[0064] In response to the determination by the determining unit 102b, the generating unit 102c generates product transfer data based on the purchase data.

[0065] Fig. 7 is a diagram showing an example of product transfer data according to the embodiment. For example, as shown in Fig. 7, the product transfer data stores records each consisting of a combination of "product transfer number," "warehouse," "receipt / payment classification," "line number," "product code," "product name," "quantity," "origin document number," and "origin document line number." Here, the generation unit 102c generates two records for one purchase data record, as shown in Fig. 7: a record (payment record) in which "receipt / payment classification" is set to "payment," and a record (receipt record) in which "receipt / payment classification" is set to "payment."

[0066] For example, because the transfer product code "C001" for the product code "A001" is set in the product master shown in Fig. 4, the generation unit 102c generates a record (payment record) with the "receipt / payment classification" set to "payment" for "50" units of "OEM product 1" with the product code "A001" shown in the purchase data in Fig. 5. The generation unit 102c also generates a record (acceptance record) with the "receipt / payment classification" set to "acceptance" for "transfer product 1" with the transfer product code "C001" set to the product code "A001", in which "50" units of "transfer product 1" are received, the same number as "OEM product 1".

[0067] The update unit 102d updates the inventory data based on the product transfer data generated by the generation unit 102c. Figure 8 is a diagram showing an example of current inventory data according to an embodiment. The current inventory data shown in Figure 8 shows a diagram in which the current inventory data (temporary inventory data) shown in Figure 6 has been updated. For example, the update unit 102d updates the temporary inventory data by setting records in the product transfer data where the "receipt / payment classification" is "payment" as a minus and records where the "receipt / payment classification" is "received" as a plus.

[0068] That is, the update unit 102d subtracts the quantity "50" from "OEM product 1" of product code "A001" for which "withdrawal" is set in the product transfer data of FIG. 7, and adds this to the current inventory data (temporary inventory data) shown in FIG. 6. As a result, the quantity of "OEM product 1" of product code "A001" in the updated current inventory data shown in FIG. 8 becomes "0." Furthermore, the update unit 102d adds the quantity "50" to "transfer product 1" of product code "C001" for which "receive" is set in the product transfer data of FIG. 7, and adds this to the current inventory data (temporary inventory data) shown in FIG. 6. As a result, in the updated current inventory data shown in FIG. 8, a new record for "transfer product 1" of product code "C001" is created, and the quantity becomes "50."

[0069] Further, the updating unit 102d updates the monthly inventory data. Fig. 9 is a diagram showing an example of monthly inventory data according to an embodiment. As shown in Fig. 9, for example, the monthly inventory data stores records each consisting of a combination of "accounting year and month," "warehouse," "product code," "product name," "inventory quantity at the end of previous month," "inventory value at the end of previous month," "inventory quantity at the end of current month," "inventory value at the end of current month," "inventory valuation unit price at the end of current month," "purchase quantity," "warehousing quantity," "product transfer acceptance quantity," "purchase amount," "warehousing amount," and "product transfer acceptance amount."

[0070] For example, the update unit 102d stores "50" in the "Purchase quantity" and "20,000" in the "Purchase amount" in the record for "OEM product 1" with product code "A001" based on the purchase data shown in Fig. 5. Furthermore, the update unit 102d stores "50" in the "Month-end stock quantity" and "20,000" in the "Month-end stock amount" in the record for "Transfer product 1" with product code "C001" based on the purchase data shown in Fig. 5 and the product transfer data shown in Fig. 7.

[0071] Here, when the monthly closing process for December is completed, the inventory data for "2023 / 12" is transferred to the inventory data for "2024 / 01." FIG. 10 is a diagram illustrating an example of monthly inventory data according to an embodiment. For example, as shown in FIG. 10, the update unit 102d adds a new record for "OEM Product 1" with product code "A001" for "2024 / 01" and a new record for "Transfer Product 1" with product code "C001" for "2024 / 01" to the monthly inventory data for "2023 / 12." The update unit 102d then transfers the "Inventory quantity at the end of this month" and "Inventory value at the end of this month" of each record for "2023 / 12" to the "Inventory quantity at the end of the previous month" and "Inventory value at the end of the previous month" for "2024 / 01."

[0072] (Processing according to purchase input) Next, the processing according to purchase input will be explained using a purchase in "2024 / 01" as an example. FIG. 11 is a diagram showing an example of current inventory data according to the embodiment. For a purchase in "2024 / 01", current inventory data showing the inventory of the purchase in "2023 / 12" is used as shown in FIG.

[0073] 12 is a diagram illustrating an example of purchase data according to the embodiment. For example, on "2024 / 1 / 12," "OEM Product 1" with product code "A001" was purchased from "OEM Customer 1" at a quantity of "10," a unit purchase price of "500 yen," and a purchase amount of "5,000 yen." As a result, the acquiring unit 102a acquires a record with purchase number "SI0001" in FIG. 12. Also, on "2024 / 1 / 13," "OEM Product 2" with product code "A002" was purchased from "OEM Customer 2" at a quantity of "5," a unit purchase price of "600 yen," and a purchase amount of "3,000 yen." As a result, the acquiring unit 102a acquires a record with purchase number "SI0002" in FIG. 12. In addition, since "OEM Product 3" with product code "A003" was purchased from "OEM Customer 3" on "2024 / 1 / 14" at a quantity of "20" units, a purchase price of "400 yen", and a purchase amount of "8,000 yen", the acquisition unit 102a acquires the record for purchase number "SI0003" in Figure 12.

[0074] Fig. 13 is a diagram showing an example of a temporary image of current stock data according to the embodiment. Here, Fig. 13 shows temporary stock data generated from the current stock data shown in Fig. 11. When the purchase data shown in Fig. 12 is acquired, the update unit 102d stores "10" in the quantity field for product code "A001," adds new records for product codes "A002" and "A003," and generates temporary stock data in which "5" and "20" are stored in the respective quantities, as shown in Fig. 13.

[0075] Furthermore, when the purchase data shown in Figure 12 is acquired, the determination unit 102b refers to the product master shown in Figure 4 and determines that the transfer product code "C001" is set for the product codes "A001," "A002," and "A003" of the purchase data shown in Figure 12.

[0076] Fig. 14 is a diagram showing an example of product transfer data according to the embodiment. For example, because the transfer product code "C001" for the product code "A001" is set in the product master shown in Fig. 4, the generation unit 102c generates a record (payment record) in which the "receipt / payment classification" is set to "payment" for "10" units of "OEM product 1" with the product code "A001" shown in the purchase data of Fig. 12. In addition, the generation unit 102c generates a record (acceptance record) in which the "receipt / payment classification" is set to "acceptance" for "transfer product 1" with the transfer product code "C001" set in the product code "A001" and in which "10" units of "transfer product 1" are received, the same number as "OEM product 1."

[0077] Similarly, because the transfer product code "C001" for product code "A002" is set in the product master shown in Fig. 4, the generation unit 102c generates a record (payment record) with the "receipt / payment classification" set to "payment" for "5" units of "OEM product 2" with product code "A002" shown in the purchase data in Fig. 12. Furthermore, the generation unit 102c generates a record (acceptance record) with the "receipt / payment classification" set to "acceptance" for "transfer product 1" with transfer product code "C001" set to product code "A002", in which "5" units of "transfer product 1" are received, the same number as "OEM product 2".

[0078] Similarly, because the transfer product code "C001" for product code "A003" is set in the product master shown in Fig. 4, the generation unit 102c generates a record (payment record) with the "receipt / payment classification" set to "payment" for 20 units of "OEM product 3" with product code "A003" shown in the purchase data in Fig. 12. Furthermore, the generation unit 102c generates a record (acceptance record) with the "receipt / payment classification" set to "acceptance" for "transfer product 1" with transfer product code "C001" set to product code "A003", in which 20 units of "transfer product 1" are received, the same number as "OEM product 3".

[0079] 15 is a diagram illustrating an example of current stock data according to the embodiment. The current stock data illustrated in FIG. 15 is a diagram obtained by updating the current stock data (temporary stock data) illustrated in FIG.

[0080] The updating unit 102d subtracts the quantity "10" from "OEM product 1" of product code "A001" for which "withdrawal" is set in the product transfer data of FIG. 14, and adds this subtracted quantity to the current inventory data (temporary inventory data) shown in FIG. 13. As a result, the quantity of "OEM product 1" of product code "A001" in the updated current inventory data shown in FIG. 15 becomes "0." Furthermore, the updating unit 102d subtracts the quantity "5" from "OEM product 2" of product code "A002" for which "withdrawal" is set in the product transfer data of FIG. 14, and adds this subtracted quantity to the current inventory data (temporary inventory data) shown in FIG. As a result, the quantity of "OEM product 2" of product code "A002" in the updated current inventory data shown in FIG. 15 becomes "0." Furthermore, the update unit 102d subtracts the quantity "20" from the "OEM product 3" of product code "A003" for which "withdrawal" is set in the product transfer data of Fig. 14, and adds this to the current stock data (temporary stock data) shown in Fig. 13. As a result, the quantity of "OEM product 3" of product code "A003" in the updated current stock data shown in Fig. 15 becomes "0".

[0081] Furthermore, the update unit 102d adds the quantities "10," "5," and "20" to the quantity "50" in the current inventory data (temporary inventory data) shown in Fig. 13 for "Transfer Product 1" with product code "C001" for which "Accept" is set in the product transfer data in Fig. 14. As a result, in the updated current inventory data shown in Fig. 15, the quantity of "Transfer Product 1" with product code "C001" becomes "85 (=50+10+5+20)."

[0082] The updating unit 102d also updates the monthly inventory data. FIG. 16 is a diagram illustrating an example of monthly inventory data according to an embodiment. Based on the purchase data shown in FIG. 12, the updating unit 102d stores "10" in the "purchase quantity" field and "5,000" in the "purchase amount" field in the record for the product code "A001" in "2024 / 01." Based on the purchase data shown in FIG. 12, the updating unit 102d also stores "5" in the "purchase quantity" field and "3,000" in the "purchase amount" field in the record for the product code "A002" in "2024 / 01." Based on the purchase data shown in FIG. 12, the updating unit 102d also stores "20" in the "purchase quantity" field and "8,000" in the "purchase amount" field in the record for the product code "A003" in "2024 / 01."

[0083] In addition, based on the purchase data shown in Figure 12 and the product transfer data shown in Figure 14, the update unit 102d stores "80" in the "Inventory quantity at the end of this month", "36,000" in the "Inventory amount at the end of this month", "35" in the "Product transfer acceptance quantity", and "16,000" in the "Product transfer acceptance amount" in the record for "Transfer product 1" with product code "C001".

[0084] (Processing according to transfer receipt input) Next, processing in response to input of a transfer of goods received in "2024 / 01" will be described using an example of a transfer of goods received in "2024 / 01." FIG. 17 is a diagram showing an example of current inventory data according to an embodiment. In the transfer of goods received in "2024 / 01," as shown in FIG. 17, current inventory data including products manufactured in the company's own factory is used. Here, the current inventory data shown in FIG. 17 indicates the state of the products manufactured in the company's own factory before they are moved to the business warehouse. Therefore, "200" units of "In-house Manufactured Product 1" manufactured in company factory 1 are warehoused in "In-house Factory 1 Warehouse." Furthermore, "100" units of "In-house Manufactured Product 2" manufactured in company factory 2 are warehoused in "In-house Factory 2 Warehouse."

[0085] Fig. 18 is a diagram showing an example of transfer data according to the embodiment. For example, when a transfer / receive input is executed, the acquiring unit 102a acquires the transfer data shown in Fig. 18. As shown in Fig. 18, the transfer data acquired by the acquiring unit 102a stores records each consisting of a combination of "transfer number," "transfer date," "shipping warehouse," "receiving warehouse," "row number," "product code," "product name," "cost unit price," "quantity," and "cost amount."

[0086] For example, on "2024 / 1 / 15," a quantity of "200" of "In-house Manufactured Product 1" with product code "B001" was transferred from "In-house Factory 1 Warehouse," causing the acquisition unit 102a to acquire the record with transfer number "ID0001" in FIG. 18. Here, the record with transfer number "ID0001" also stores the unit cost price of "350 yen" and the cost amount of "70,000 yen." Also, on "2024 / 1 / 16," a quantity of "100" of "In-house Manufactured Product 2" with product code "B002" was transferred from "In-house Factory 2 Warehouse," causing the acquisition unit 102a to acquire the record with transfer number "ID0002" in FIG. 18. Here, the record with transfer number "ID0002" also stores the unit cost price of "300 yen" and the cost amount of "30,000 yen."

[0087] Fig. 19 is a diagram showing an example of a temporary image of current inventory data according to the embodiment. Here, Fig. 19 shows temporary inventory data generated from the current inventory data shown in Fig. 17. When the movement data shown in Fig. 18 is acquired, the update unit 102d adds a new record for product code "B001" in which the warehouse is a "commercial warehouse" and a new record for product code "B002" in which the warehouse is a "commercial warehouse," and generates temporary inventory data in which "200" and "100" are stored in the respective quantities, as shown in Fig. 19.

[0088] Furthermore, when the transfer data shown in Figure 18 is acquired, the determination unit 102b refers to the product master shown in Figure 4 and determines that the transfer product code "C001" is set for the product codes "B001" and "B002" of the transfer data shown in Figure 18.

[0089] Fig. 20 is a diagram showing an example of product transfer data according to an embodiment. For example, because the transfer product code "C001" for the product code "B001" is set in the product master shown in Fig. 4, the generation unit 102c generates a record (payment record) with the "receipt / payment classification" set to "payment" for 200 units of "self-manufactured product 1" with the product code "B001" shown in the transfer data of Fig. 18. In addition, the generation unit 102c generates a record (acceptance record) with the "receipt / payment classification" set to "acceptance" for "transfer product 1" with the transfer product code "C001" set to the product code "B001," in which 200 units of "transfer product 1" are received, the same number as the "self-manufactured product 1."

[0090] Similarly, because the transfer product code "C001" for product code "B002" is set in the product master shown in Fig. 4, the generation unit 102c generates a record (payment record) with the "payment classification" set to "payment" for "100" units of "in-house manufactured product 2" with product code "B002" shown in the transfer data in Fig. 18. Furthermore, the generation unit 102c generates a record (receive record) with the "payment classification" set to "receive" for "transfer product 1" with transfer product code "C001" set to product code "B002", in which "100" units of "transfer product 1" are received, the same number as "in-house manufactured product 2".

[0091] 21 is a diagram illustrating an example of current stock data according to the embodiment. The current stock data illustrated in FIG. 21 is a diagram obtained by updating the current stock data (temporary stock data) illustrated in FIG.

[0092] The updating unit 102d subtracts the quantity "200" from the quantity of "in-house manufactured product 1" with product code "B001" for which "withdrawal" is set in the product transfer data of FIG. 20, and adds this subtraction to the quantity of the business warehouse in the current inventory data (temporary inventory data) shown in FIG. 19. As a result, the quantity of "in-house manufactured product 1" with product code "B001" in the updated current inventory data shown in FIG. 21 becomes "0." Furthermore, the updating unit 102d subtracts the quantity "100" from the quantity of "in-house manufactured product 2" with product code "B002" for which "withdrawal" is set in the product transfer data of FIG. 20, and adds this subtraction to the quantity of the business warehouse in the current inventory data (temporary inventory data) shown in FIG. As a result, the quantity of "in-house manufactured product 2" with product code "B002" in the updated current inventory data shown in FIG. 21 becomes "0."

[0093] Furthermore, the update unit 102d adds the quantities "200" and "100" to the quantity "85" of the current inventory data (temporary inventory data) shown in Fig. 19 for "Transfer Product 1" of product code "C001" for which "Accept" is set in the product transfer data in Fig. 20. As a result, in the updated current inventory data shown in Fig. 21, the quantity of "Transfer Product 1" of product code "C001" becomes "385 (=85+200+100)".

[0094] The update unit 102d also updates the monthly inventory data. FIG. 22 is a diagram showing an example of monthly inventory data according to an embodiment. Based on the transfer data shown in FIG. 18, the update unit 102d stores "200" in the "Quantity Inventory" field and "70,000" in the "Amount Inventory" field in the record for "2024 / 01" with product code "B001." Based on the transfer data shown in FIG. 18, the update unit 102d also stores "100" in the "Quantity Inventory" field and "30,000" in the "Amount Inventory" field in the record for "2024 / 01" with product code "B002."

[0095] In addition, based on the transfer data shown in Figure 18 and the product transfer data shown in Figure 20, the update unit 102d stores "385" in the "Inventory quantity at the end of this month" in the record for "Transfer product 1" with product code "C001", stores "136,000" in the "Inventory amount at the end of this month", stores "335 (= 10 + 5 + 20 + 200 + 100)" in the "Product transfer acceptance quantity", and stores "116,000 (= 5,000 + 3,000 + 8,000 + 70,000 + 30,000)" in the "Product transfer acceptance amount".

[0096] (Cost accounting processing) Next, the cost calculation process will be described. Figure 23 is a diagram showing an example of inventory valuation unit price data according to an embodiment. As shown in Figure 23, the inventory valuation unit price data stores records each consisting of a combination of "product code," "product name," and "cost unit price." Here, the inventory valuation unit price data stores records corresponding to the product codes (A001, A002, and A003) assigned to products manufactured by the OEM partner, the product codes (B001 and B002) assigned to products manufactured in the company's own factory, and the product code (C001) transferred after being received at the commercial warehouse.

[0097] For example, the calculation unit 102e calculates the unit cost price of "500 (=5,000÷10)" for "OEM Product 1" based on the purchase quantity of "10" and the purchase amount of "5,000" stored in the record for product code "A001" for "2024 / 01" in the monthly inventory data shown in Fig. 22. Similarly, the calculation unit calculates the unit cost price of "600 (=3,000÷5)" for "OEM Product 2" based on the purchase quantity of "5" and the purchase amount of "3,000" stored in the record for product code "A002" for "2024 / 01" in the monthly inventory data shown in Fig. 22, and calculates the unit cost price of "400 (=8,000÷20)" for "OEM Product 3" based on the purchase quantity of "20" and the purchase amount of "8,000" stored in the record for product code "A003" for "2024 / 01."

[0098] Furthermore, the calculation unit 102e calculates the unit cost price "350 (=70,000÷200)" of "In-house manufactured product 1" based on the inventory quantity "200" and inventory amount "70,000" stored in the record for product code "B001" for "2024 / 01" in the monthly inventory data shown in Fig. 22. Similarly, the calculation unit 102e calculates the unit cost price "300 (=30,000÷100)" of "In-house manufactured product 2" based on the inventory quantity "100" and inventory amount "30,000" stored in the record for product code "B002" for "2024 / 01" in the monthly inventory data shown in Fig. 22.

[0099] In addition, for transfer product 1, which is an integration of OEM products and in-house manufactured products, the calculation unit 102e calculates the unit cost price of the entire identical product stored in the commercial warehouse by calculating the following formula (1).

[0100] Inventory valuation unit price at the end of this month = (inventory amount at the end of the previous month + amount of costs incurred in this month) ÷ (inventory quantity at the end of the previous month + amount of costs incurred in this month) (1)

[0101] In addition, in formula (1), the "amount of costs incurred in the current month included" is calculated by "purchase amount + inventory amount + amount of goods transferred and accepted", and the "number of costs incurred in the current month included" is calculated by "number of purchases + number of goods received + number of goods transferred and accepted".

[0102] FIG. 24 is a diagram illustrating an example of monthly inventory data according to an embodiment. For simplicity, the monthly inventory data illustrated in FIG. 24 excludes the monthly inventory data for "2023 / 12." For example, the calculation unit 102e calculates the "Amount of Costs Incurred in the Current Month" based on all "Purchase Amounts," all "Receipt Amounts," and "Amount of Product Transfer Receipt" in the monthly inventory data illustrated in FIG. 24. The calculation unit 102e also calculates the "Number of Items Incurred in the Current Month" based on all "Purchase Quantities," all "Receipt Quantities," and "Number of Product Transfer Receipt" in the monthly inventory data illustrated in FIG. 24. Furthermore, the calculation unit 102e calculates the unit cost "353" for "Transfer Product 1" by calculating Equation (1) using the "Quantity in Stock at the End of Previous Month" and "Inventory Amount at the End of Previous Month" in the monthly inventory data illustrated in FIG. 24 and the calculated "Amount of Costs Incurred in the Current Month" and "Number of Items Incurred in the Current Month":

[0103] The updating unit 102d updates the monthly inventory data as shown in FIG. 24 by storing the cost unit price of each product calculated by the calculation unit 102e in the "Month-end inventory evaluation unit price" in the corresponding record of the monthly inventory data.

[0104] The product management device 100 executes the above-mentioned processes to generate, for example, the current inventory data shown in FIG. 24, thereby enabling cost management for each manufacturer and integrating and managing inventory quantities into a single code.

[0105] According to the embodiment described above, even when the same products manufactured by different manufacturers are received, it is possible to manage the products by integrating them into a single code while still managing them by manufacturer, making it easy to perform highly accurate management.

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

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

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

[0109] 4. Other Embodiments Although the embodiments of the present invention have been described above, the present invention may be implemented in various different embodiments other than those described above within the scope of the technical concept described in the claims.

[0110] For example, among the processes described in the above-mentioned 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.

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

[0112] Furthermore, with regard to the product management device 100, the components shown in the drawings are functional concepts, and do not necessarily have to be physically configured as shown in the drawings.

[0113] For example, all or any part of the processing functions of each device constituting the product management device 100, particularly the processing functions performed by the control unit, 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 each device as needed. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. The computer program is executed by being loaded into RAM and works with the CPU to constitute the control unit.

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

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

[0116] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as 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 the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

[0117] The various databases stored in the memory unit 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.

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

[0119] 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. [Industrial Applicability]

[0120] The present invention is useful for accounting processes in manufacturing industries such as agricultural equipment manufacturing, large machinery manufacturing, and semiconductor manufacturing. [Explanation of symbols]

[0121] 100 Product management device 102 Control section 102a Acquisition Department 102b Judgment section 102c generator 102d Update Department 102e Calculation Unit 104 Communication interface unit 106 Storage section 106a Product Master 106b Purchase Data 106c Movement Data 106d Product Transfer Data 106e inventory data 106f Inventory valuation unit price data 108 Input / Output Interface Section 200 servers 300 Network 400 Input Device 500 output devices

Claims

1. A product management device including a control unit, The system is capable of accessing receiving data that associates product codes and quantities of products to be received, and a product master that associates the product codes with transfer product codes that set transfer products for management purposes for the products, The control unit an acquisition means for acquiring the receipt data for each receipt of a product; a determination means for determining whether the product code included in the acceptance data is the product code associated with the transfer product code in the product master; and a generating means for generating transfer data for transferring the quantity of the product included in the acceptance data to the quantity of the transfer product when the product code included in the acceptance data is the product code associated with the transfer product code. A merchandise management device characterized by:

2. The generating means The transfer data is generated, which includes a withdrawal record in which the receipt and payment classification that distinguishes between the withdrawal of the product and the receipt of the transfer product is set to "payment," and in which the product is withdrawn in the quantity included in the receipt data, and a receipt record in which the receipt and payment classification is set to "acceptance," and in which the transfer product in the quantity is received.

2. The product management device according to claim 1.

3. Further, the system has access to inventory data, which includes records showing current inventory status for each product; The control unit The data acquisition system further includes an update unit that updates the current inventory data by generating temporary inventory data by adding the received quantity to a record in the current inventory data corresponding to the received receipt data each time the acquisition unit acquires the receipt data, and, when the generation unit generates the transfer data, subtracting the quantity of the product in the withdrawal record for which the receipt / payment classification of the transfer data is set to "delivery" from the corresponding record in the temporary inventory data, and adding the quantity of the transferred product in the receipt record for which the receipt / payment classification of the transfer data is set to "receipt" to the corresponding record in the temporary inventory data.

3. The product management device according to claim 2.

4. The receiving data includes purchase data when the goods manufactured by the outsourced company are received, and movement data when the goods manufactured by the company are received, The purchase data associates the quantity purchased from the consignee with the consignee product code of the product at the consignee, The movement data is a data set in which the number of goods received from a manufacturing location is associated with a manufacturing location product code of the goods, and The generating means Generate transfer data that transfers the quantity of the product included in the purchase data to the quantity of the transfer product, transfers the consignee product code to the product code of the transfer product, transfers the quantity of the product included in the transfer data to the quantity of the transfer product, and transfers the manufacturing location product code to the product code of the transfer product.

4. The product management device according to claim 1, wherein the product management device is a product management device for managing a product.

5. The purchase data further includes a purchase price of the product, The movement data further includes the inventory amount of the commodity; The control unit The system further comprises a calculation means for calculating the cost of the goods manufactured by the outsourcee based on the purchase quantity and the purchase amount, for calculating the cost of the goods manufactured by the company based on the inventory quantity and the inventory amount, and for calculating the cost of the transfer goods based on the number of transfer goods received based on the purchase quantity and the inventory quantity and the amount of transfer goods received based on the purchase amount and the inventory amount.

5. The product management device according to claim 4.

6. The system is further able to access monthly inventory data including the purchase quantity and purchase amount for each month, the previous inventory quantity and inventory amount for each month, and the stock quantity and stock amount of the transfer product at the end of the previous month; The calculation means calculates the cost of the transfer product at the end of the current month based on the number of purchases for each month and the number of previously recorded inventories for each month, the amount of costs to be included for each month based on the purchase amount for each month and the previously recorded inventory amount for each month, and the inventory number and inventory amount of the transfer product at the end of the previous month.

6. The product management device according to claim 5.

7. A product management method executed in a product management device including a control unit, The control unit The system is capable of accessing receiving data that associates product codes and quantities of products to be received, and a product master that associates the product codes with transfer product codes that set transfer products for management purposes for the products, Executed by the control unit, an acquisition step of acquiring the receipt data for each receipt of the product; a determining step of determining whether or not the product code included in the acceptance data is a product code to which the transfer product code is associated in the product master; and a generating step of generating transfer data for transferring the quantity of the product included in the acceptance data to the quantity of the transfer product when the product code included in the acceptance data is a product code associated with the transfer product code. A merchandise management method comprising:

8. A product management program to be executed by a product management device having a control unit, The control unit The system is capable of accessing receiving data that associates product codes and quantities of products to be received, and a product master that associates the product codes with transfer product codes that set transfer products for management purposes for the products, The control unit an acquisition step of acquiring the receipt data for each receipt of the product; a determining step of determining whether or not the product code included in the acceptance data is a product code to which the transfer product code is associated in the product master; a generating step of generating transfer data for transferring the quantity of the product included in the acceptance data to the quantity of the transfer product when the product code included in the acceptance data is the product code associated with the transfer product code; Product management program to run.

Images