JP7569341B2 - Information processing device, information processing method, and information processing program - Google Patents

Description

The present invention relates to an information processing device, an information processing method, and an information processing program.

Nowadays, sample products for promotional purposes are sometimes provided individually or by the case.

In the case of the inventory management device disclosed in Patent Document 1 (JP Patent Publication 2007-276990), for each set product consisting of a combination of one or more types of individual products, the device accepts input of the number of items created for that set product and the number of items by type of individual product included in the set product. When the number of items created for the set product and the number of items by type of individual product are input, the device updates the inventory data for individual products stored in the inventory management file by subtracting a value obtained by multiplying the number of items created for the set product by the number of items created for the individual product for each individual product included in the set product. This allows the inventory quantity of each product to be accurately managed even when dealing in set products consisting of a combination of one or more types of individual products.

JP 2007-276990 A

However, when products are provided in both loose and case units, it is necessary to manage the inventory of two different products: loose and cased. This requires a decision to be made on each occasion as to whether to use loose or cased products, which can lead to operational errors and increases the workload of operators.

The present invention has been made in consideration of the above-mentioned problems, and aims to provide an information processing device, an information processing method, and an information processing program that facilitate inventory management of loose items and cased items provided as sample items, for example.

In order to solve the above-mentioned problems and achieve the object, the information processing device of the present invention comprises an acquisition unit that acquires either single item classification information indicating that the handling unit is a single item, or case item classification information indicating that the handling unit is a case item in which multiple items are bundled together, and the product code of the product, a memory control unit that associates the classification information and product code acquired by the acquisition unit and stores them in a database, and a data generation unit that generates specified data including the input product code and classification information, and the memory control unit stores the specified data generated by the data generation unit in the memory unit, and, if the classification information is single item classification information, extracts from the database a single item product code associated with the single item classification information and rewrites the product code of the specified data to the single item product code extracted from the database .

In addition, in order to solve the above-mentioned problems and achieve the object, the information processing method of the present invention includes an acquisition step in which an acquisition unit acquires either single item classification information indicating that the handling unit is a single item, or case item classification information indicating that the handling unit is a case item in which multiple items are bundled together, and a product code of the product; a storage control step in which a memory control unit associates the classification information and product code acquired by the acquisition unit and stores them in a database; and a data generation step in which a data generation unit generates predetermined data including the input product code and classification information, respectively.The storage control step is characterized in that the predetermined data generated by the data generation step is stored in the memory unit, and if the classification information is single item classification information, a single item product code associated with the single item classification information is extracted from the database, and the product code of the predetermined data is rewritten to the single item product code extracted from the database .

In addition, in order to solve the above-mentioned problems and achieve the object, the information processing program of the present invention causes a computer to function as an acquisition unit that acquires either single item classification information indicating that the handling unit is a single item, or case item classification information indicating that the handling unit is a case item in which multiple items are bundled together, and the product code of the product, a memory control unit that associates the classification information and product code acquired by the acquisition unit and stores them in a database , and a data generation unit that generates specified data including the input product code and classification information , and the memory control unit stores the specified data generated by the data generation unit in the memory unit, and, if the classification information is single item classification information, extracts from the database a single item product code associated with the single item classification information and rewrites the product code of the specified data to the single item product code extracted from the database .

The present invention has the effect of facilitating inventory management of loose items and cased items provided as sample items, for example.

FIG. 1 is a block diagram showing a hardware configuration of an information processing apparatus according to an embodiment. FIG. 2 is a diagram illustrating an example of the product master. FIG. 3 is a diagram illustrating an example of the asset classification master. FIG. 4 is a diagram illustrating an example of the subject category master. FIG. 5 is a diagram illustrating an example of the general-purpose master. FIG. 6 is a diagram showing an example of the transaction classification master. FIG. 7 is a diagram illustrating an example of the transaction category association master. FIG. 8 is a diagram illustrating an example of the supplier master. FIG. 9 is a diagram illustrating an example of the customer master. FIG. 10 is a flowchart showing the flow of the operation for creating a product master. FIG. 11 is a diagram illustrating an example of data registered in the product master. FIG. 12 is a flowchart showing the flow of the operation for generating order input data. FIG. 13 is a diagram showing an example of the order input data. FIG. 14 is a flowchart showing the flow of the operation for generating purchase input data. FIG. 15 is a diagram showing an example of purchase input data. FIG. 16 is a diagram showing an example of the shipment input data. FIG. 17 is a flowchart showing the flow of the operation for generating sales input data. FIG. 18 is a diagram showing an example of sales input data. FIG. 19 is a flowchart showing the flow of the operation for generating product change input data. FIG. 20 is a diagram showing an example of dispensing data and receiving data when a product change is input. FIG. 21 is a diagram showing an example of product change input data.

Below, an information processing device according to an embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

(Hardware configuration)
1 is a block diagram showing a hardware configuration of an information processing device 1 according to an embodiment. As the information processing device 1, in addition to a desktop personal computer, a notebook personal computer, or a tablet personal computer can be used. Also, as the information processing device 1, a portable information processing device such as a PDA (Personal Digital Assistant) device or a smartphone can be used. Such an information processing device 1 includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input/output interface unit 5.

An input device 6 and an output device 7 are connected to the input/output interface unit 5. A monitor device (including a home television) can be used as the output device 7. The input device 6 can be a keyboard device, a mouse device, a microphone device, or a monitor device that works with a mouse device to realize a pointing device function.

The storage unit 2 may be, for example, a storage device such as a ROM (Read Only Memory), a RAM (Random Access Memory), a HDD (Hard Disk Drive), or an SSD (Solid State Drive). The storage unit 2 includes a product master 11 (an example of a database), an asset classification master 12, an item classification master 13, a general-purpose master 14, a transaction classification master 15, a transaction classification association master 16, a supplier master 17, and a customer master 18, each of which is a storage area in which specific information is stored.

The storage unit 2 also stores an information processing program that performs inventory management for products that are handled as single items (loose items) and products that are handled in case units that contain multiple items (case items). The storage unit 2 also stores various data generated based on this information processing program, such as order input data, purchase input data, shipment input data, sales input data, and product change input data.

As shown in FIG. 2, the product master 11 stores product data including information such as product code, product name, case bulk category (an example of category information), quantity, genre code (JANCD: Japanese Article Number Code), bulk product code, asset classification, sample debt subject category, etc. When product data with a case bulk category of "case item (an example of case item category information)" is registered in the product master 11, the information processing device 1 according to the embodiment automatically generates product data for the "bulk items" that make up the "case item" and registers it in the product master 11 in association with the product data for the "case item." This allows the master creator and business operators to manage the master without being aware of case items and bulk items separately. Details will be described later.

Asset classification master 12 stores asset classification data including information such as asset classification code and asset classification name, as shown in FIG. 3. The example in FIG. 3 shows an example in which an asset classification name of "Sales Promotion Expenses" is associated and registered with an asset classification code of "S001," and an asset classification name of "Supplies" is associated and registered with an asset classification code of "S003."

The subject category master 13 stores subject category data including information such as subject category code and subject category name, as shown in FIG. 4. The example in FIG. 4 shows an example in which the subject category name "accounts receivable" is associated and registered with the subject category code "KA001", and the subject category name "accounts payable" is associated and registered with the subject category code "KB001".

As shown in the example of FIG. 5, the general-purpose master 14 stores rules for generating bulk product codes (an example of a single product code) that are used to automatically generate bulk product data when product data for a "case item" case bulk classification is registered in the product master 11. Specifically, the general-purpose master 14 stores bulk product suffix data to be added to the end of the "case item" product code. The example of FIG. 5 shows that the code "-01" is added to the end of the "case item" product code to generate bulk product suffix data. This will be described in more detail later.

As shown in FIG. 6, the transaction category master 15 stores transaction category data including information such as transaction category code, transaction category name, and sample transaction. The example in FIG. 6 is an example in which a transaction category code of "JT001" is associated with a transaction category name of "ordering" and a sample transaction of "non-applicable" and stored. The example in FIG. 6 is also an example in which a transaction category code of "UT002" is associated with a transaction category name of "sample sales" and a sample transaction of "applicable" and stored.

The transaction category association master 16 stores transaction category association data including transaction category codes and transaction category names, as shown in FIG. 7. The example in FIG. 7 is an example in which a transaction category code of "JT002" is associated with a transaction category name of "sample ordering". The example in FIG. 7 is an example in which a transaction category code (sales) of "UT002" is associated with a transaction category name of "sample sales". The example in FIG. 7 is an example in which a transaction category code (purchases) of "ST002" is associated with a transaction category name of "sample purchases".

The supplier master 17 stores supplier data including supplier codes and debt subject categories, as shown in FIG. 8. The example in FIG. 8 shows that the debt subject category "KB001" is associated with each of the supplier codes "Supplier A," "Supplier B," and "Supplier C."

The customer master 18 stores customer data including customer codes and debt subject categories, as shown in the example of FIG. 9. The example of FIG. 9 shows that the debt subject category "KB001" is associated with each of the customer codes "Customer A," "Customer B," and "Customer C."

(Functional configuration)
Next, the control unit 3 executes the information processing program stored in the memory unit 2, thereby functioning as a trading unit 21, a memory control unit 22, a data generation unit 23, and a display control unit 24.

The transaction unit 21 acquires product data input by the business operator or the like via the input device 6 when the product master 11 is generated. The acquisition unit 21 also acquires order input data input by the business operator or the like when an order is input, and purchase input data input by the business operator or the like when a purchase is input. The storage control unit 22 registers the product data acquired by the acquisition unit 21 in the product master 11 when the product master 11 is generated. Furthermore, when the product master 11 is generated, the storage control unit 22 registers the product data of loose items automatically generated by the data generation unit 23 (described later) in association with the product data of cased items.

The data generation unit 23 automatically generates product data for loose items when product data for cased items is registered in the product master 11 during generation of the product master 11. The display control unit 24 displays on the output device 7 a product data registration screen for input operations by the business operator when registering product data in the product master 11. The display control unit 24 also displays on the output device 7 an order input screen for input operations by the business operator during order input, and also displays on the output device 7 a purchase input screen for input operations by the business operator during purchase input. The display control unit 24 also displays on the output device 7 input screens etc. that correspond to input operations by the business operator.

(Product data registration operation for product master)
Next, the operation of registering product data in the product master 11 in the information processing device 1 according to the embodiment will be described with reference to the flowchart of Fig. 10. The control unit 3 operates based on the information processing program stored in the storage unit 2 to execute each process in the flowchart of Fig. 10.

In other words, when the business operator specifies the registration of product data in the product master 11, the display control unit 24 displays a registration screen for the product data in the product master 11 on the output device 7. The business operator operates the input device 6 to input the desired product data into this registration screen. In step S1, the acquisition unit 21 acquires the input information (product data) input by the business operator.

Figure 11(a) shows an example of product data entered by a business operator. The example in Figure 11(a) shows product data entered by a business operator for a product code of "A001", a genre code of "123456", a bulk case category of "case", and 20 syringes per case.

For the product data shown in Figure 11(a), the "asset classification" is selected by the business operator by displaying a list of asset classification data stored in the asset classification master 12 shown in Figure 3 on the output device 7, and selecting and inputting the asset classification that corresponds to the product data to be registered. The example in Figure 11(a) is an example in which "sales promotion expenses" with asset classification code "S001" is selected as the "asset classification" and input.

In addition, for the product data shown in FIG. 11(a), the "sample debt subject category" is entered by the business operator by displaying a list of the subject category data stored in the subject category master 13 shown in FIG. 4 on the output device 7, and selecting and entering from this the subject category that corresponds to the product data to be registered. The example in FIG. 11(a) is an example in which "Unpaid Amount" with subject category code "KB002" is selected and entered as the "sample debt subject category".

Next, in step S2, the data generation unit 23 determines whether the case-individual classification of the product data entered by the business operator is "case." If the case-individual classification is "case" (step S2: Yes), the process proceeds to step S3, and if the case-individual classification is "individual (an example of single item classification information)" (step S2: N0), the process proceeds to step S6.

In the example of FIG. 11(a), the case breakdown category of the product data entered by the business operator is "case". Therefore, the process proceeds to step S3. In step S3, the data generation unit 23 first generates product data for "case" (data for case) as shown in the records in the top column of FIG. 11(b). The memory control unit 22 registers the generated data for case in the product master 11 in the memory unit 2.

The data generating unit 23 generates the case data in this way, and also generates bulk product codes for bulk products obtained by dividing the case products into individual products (step S4). That is, the data generating unit 23 obtains bulk product suffix data by referencing the general-purpose master 14 shown in FIG. 5. The data generating unit 23 then adds this bulk product suffix data to the end of the product code of the case product to generate a bulk product code for the bulk product. In the example of FIG. 5, the bulk product suffix data is "-01". Also, in the examples of FIG. 11(a) and FIG. 11(b), the product code of the case product is "A001". Therefore, the data generating unit 23 generates a bulk product code of "A001-01" by adding the bulk product suffix data of "-01" to the end of the product code of the case product, "A001".

When the bulk product code is generated in this way, the data generation unit 23 generates a bulk product code for bulk products with the above-mentioned "A001-01" as the product code, as exemplified by the record in the lower column in FIG. 11(b). The memory control unit 22 registers the generated bulk product code in the product master 11. At this time, as shown in FIG. 11(b), the memory control unit 22 registers the bulk product code "A001-01" in the "Bulk Product Code" input field of the case data previously registered (step S5), and ends the product data registration operation shown in the flowchart in FIG. 10. This allows the case data and bulk data to be associated and registered in the product master 11. Furthermore, if the case bulk category is "case", bulk data can be automatically generated and registered in the product master 11.

As a result, the master creation staff or business operators can manage the master data without having to be aware of creating master data separately for cased products and loose products. Furthermore, business operators etc. can eliminate the need to determine the product code by simply determining whether the current shipment is for cased products or loose products (by simply determining the cased loose category). This prevents operational errors that would occur when creating two products with different inventory management units and having to make decisions each time during operation, and prevents the inconvenience of increased workload for business operators.

On the other hand, if the case bulk category is determined to be "bulk" in step S2 (step S2: No) and the process proceeds to step S6, the data generation unit 23 generates bulk data, as exemplified by the records in the lower column in FIG. 11(b). The storage control unit 22 registers the generated bulk data in the product master 11, and ends the product data registration operation shown in the flowchart in FIG. 10. In this way, the product master 11 is generated by registering case data and bulk data each time.

(Order entry operation)
Next, the order input operation for cased products, loose products, or normal order products distributed as samples will be described with reference to the flowchart of FIG. 12. When the business operator specifies the display of the order input screen, the process proceeds from step S11 to step S12, and the display control unit 24 displays the order input screen via the output device 7. When the business operator inputs information about the ordered product via this order input screen, the acquisition unit 21 acquires it (step S12). The data generation unit 23 generates order input data in which the product code is a product code for cased products, regardless of whether the product is cased or loose (step S13). That is, the data generation unit 23 generates order input data in which the product code for cased products is assigned to both cased products and loose products. The storage control unit 22 stores the generated order input data in the storage unit 2.

Next, the memory control unit 22 detects order input data stored in the memory unit 2 for which the case loose category is "loose" (step S14). If the memory control unit 22 detects order input data for which the case loose category is "loose" (step S14: Yes), it detects the loose product code by referring to the product master 11 shown in FIG. 2. Then, it updates (rewrites) the product code for cased items in the order input data for which the case loose category is "loose" to the loose product code detected from the product master 11 (step S15), and ends the entire process of the order input operation shown in FIG. 12.

Specifically, FIG. 13(a) shows input data entered by a business operator for sample products distributed as case products. In this case, the business operator refers to the transaction category association master 16 shown in FIG. 7 and enters "JT002", which is the transaction category code for "sample ordering", as the transaction category code. The product code is also entered as "A001" and the case bulk category is "case". The storage control unit 22 automatically assigns an order number such as "J001" as shown in FIG. 13(b), and first generates order input data with a transaction category code of "JT002", a product code of "A001", and a case bulk category of "case" according to the input data and stores it in the storage unit 2. In this case, since the case bulk category is "case", the storage control unit 22 does not perform the product code update process described in steps S14 and S15.

The examples in Figures 13(e) and 13(f) are examples of input data and order input data when a cased product is normally ordered. In this case, as in Figures 13(a) and 13(b), the case loose category is "case", so the memory control unit 22 does not perform the product code update process described in steps S14 and S15.

In contrast, Figures 13(c) and 13(d) are examples of input data and order input data when an order is received for loose sample items. In this case, "loose" is specified as the case loose category. Even in this case, the memory control unit 22 first generates order input data with a transaction category code of "JT002", product code of "A001", and case loose category of "loose" according to the input data, and stores it in the memory unit 2. However, because the case loose category is "loose", as shown in Figure 13(d), the product code of "A001", which is the product code of the case item, is updated (rewritten) to the product code of "A001-01", which is the product code of the loose item detected from the product master 11.

As a result, even if the business operator uses the product code for cased items as the product code for both cased items and loose items, if the case loose item classification is "loose," the product code can be automatically corrected to that of the loose item. This allows the business operator to enter data without having to worry about the product codes for cased items and loose items.

(Purchase input operation)
Next, the operation of inputting a purchase of a product will be described with reference to the flowchart of FIG. 14. When the business operator specifies the display of the purchase input screen, the process proceeds from step S21 to step S22, and the display control unit 24 displays the purchase input screen via the output device 7. When the business operator inputs information about the product to be purchased via this purchase input screen, the acquisition unit 21 acquires the input information about the product as input data. The data generation unit 23 generates purchase input data based on the acquired input data (step S22). The memory control unit 22 stores the generated purchase input data in the memory unit 2.

Figure 15(a) is an example of input data for sample items distributed in cases. In this case, the business operator refers to the transaction category master 15 shown in Figure 6 and inputs the transaction category code of "ST002", which indicates that the item is a purchase of sample items. In addition, "A001" is input as the product code, and "case" is input as the case-by-case category. Figure 15(b) is an example of purchase input data generated by the data generation unit 23 based on the input data in Figure 15(a). When the transaction category code of the input data is "ST002", the data generation unit 23 refers to the product master 11 and obtains "KB002", which is the sample debt subject category code for the case item with the product code "A001", in order to indicate that the item is a "purchase of sample items (sample purchase)" as shown in Figure 7. Then, as shown in FIG. 15(b), the data generation unit 23 generates purchase input data for a sample purchase, including the automatically generated purchase number "S001", the transaction category code "ST002", the product code "A001", the product name "syringe", the case bulk category "case", the purchase quantity, and the debt subject category code "KB002".

Here, the data generation unit 23 determines whether the transaction classification code included in the generated purchase input data is a transaction classification code indicating "sample purchase" (ST002 in this example) (step S23). If the transaction classification code is a transaction classification code indicating "sample purchase" (step S23: Yes), the data generation unit 23 generates journal entry data in step S24 in which the asset classification is set to the debit side and the sample liability item classification is set to the credit side.

In the example of Figure 15(b), by referencing the product master shown in Figure 2 based on the product code "A001", which is the product code for the cased product, the asset classification code "S001" can be obtained. The data generation unit 23 obtains the asset classification of "sales promotion expenses" by referencing the asset classification master 12 shown in Figure 3 based on this asset classification code of "S001". The data generation unit 23 sets this "sales promotion expenses" on the debit side of the journal entry data.

The data generation unit 23 also references the item classification master 13 shown in FIG. 4 based on the debt item classification code of "KB002". This allows a sample debt item classification of "accrued money" to be obtained. The data generation unit 23 sets this "accrued money" to the credit side of the journal entry data. This allows the journal entry data of "sales promotion expenses/accrued money" to be generated as shown in FIG. 15(b). The memory control unit 22 adds this journal entry data to the purchase input data and stores it in the memory unit 2.

Similarly, Figures 15(c) and 15(d) show an example in which the transaction category code included in the generated purchase input data is "ST002", which indicates "sample purchase" (Step S23: Yes), and the case bulk category is "bulk". In this case, as the case bulk category is "bulk", the data generation unit 23 automatically generates a product code for bulk items (A001-01), as described above.

At the same time, the data generation unit 23 references the product master shown in FIG. 2 based on the product code "A001-01", which is the product code for loose items, and obtains an asset classification code of "S001". The data generation unit 23 references the asset classification master 12 shown in FIG. 3 based on this asset classification code of "S001", and obtains the asset classification of "sales promotion expenses". The data generation unit 23 sets this "sales promotion expenses" on the debit side of the journal entry data.

The data generation unit 23 also references the subject classification master 13 shown in FIG. 4 based on the debt subject classification code of "KB002" to obtain a sample debt subject classification of "accounts payable". The data generation unit 23 sets this "accounts payable" to the credit side of the journal entry data. This makes it possible to generate journal entry data for "sales promotion expenses/accounts payable" as shown in FIG. 15(b). The memory control unit 22 adds this journal entry data to the purchase input data and stores it in the memory unit 2.

In contrast, FIG. 15(e) is an example of input data for a case of a product with product code "A001" that has been purchased normally. In other words, this is an example of input data for a case in which a product with product code "A001" has been purchased not as a sample product but by purchase. In this case, the business operator refers to the transaction category association master 16 shown in FIG. 7 and inputs the transaction category code "ST001", which indicates that this is a normal purchase, as shown in FIG. 15(e).

The data generation unit 23 refers to the supplier master shown in FIG. 8 based on the supplier that purchased the "A001" product, and obtains a debt subject classification code of, for example, "KB001". The data generation unit 23 then generates purchase input data for normal purchases, including a purchase number that is automatically subdivided into "S003" and the like, a transaction classification code of "ST001", and a debt subject classification code of "KB001", as shown in FIG. 15(f).

Here, in the examples of Figures 15(e) and 15(f), the transaction category code is not a transaction category code indicating "sample purchase" but a transaction category code (ST001) indicating a normal "purchase" (step S23: No). Therefore, in step S25, the data generation unit 23 detects the account item (purchase) corresponding to the transaction category code of "ST001" from the transaction category item association master 16 shown in Figure 7, and sets this on the debit side of the journal entry data.

The data generation unit 23 also references the subject classification master 13 shown in FIG. 4 based on the debt subject classification code of "KB001" to obtain the subject classification of "accounts payable". This subject classification is then set on the credit side of the journal entry data. This makes it possible to generate journal entry data for "purchases/accounts payable" as shown in FIG. 15(f). The memory control unit 22 adds this journal entry data to the purchase input data and stores it in the memory unit 2.

This accounting data is recorded in an accounting system installed on a server device on a specified network, or in an accounting system installed in the memory unit 2.

(Shipping input operation)
Next, the shipment input operation will be described. When performing shipment operations, the business operator reads the barcode printed or attached by a sticker on the box (case) in which the product is packed, using a handy barcode reader. Therefore, as shown in Fig. 16(a), Fig. 16(c) and Fig. 16(e), the product code of the input data becomes "A001", which is the product code of the case. The business operator inputs the case classification and the number of shipments for this input data. Fig. 16(a) is an example of input data when one case of sample products is shipped. Fig. 16(c) is an example of input data when five loose sample products are shipped. Fig. 16(e) is an example of input data when one case of products is normally shipped.

Such input data is acquired by the acquisition unit 21. When the data generation unit 23 acquires input data indicating that one case of sample products is to be shipped, as shown in FIG. 16(a), the data generation unit 23 generates the shipping input data shown in FIG. 16(b) based on this input data. That is, as shown in FIG. 16(b), the data generation unit 23 generates shipping input data including an automatically generated shipping number such as "B001", a trade category name with "shipment", a product code of "A001" which is the product code for cased products, a product name such as "syringe", a case-by-case category with "case", and the number of shipments. The memory control unit 22 stores this shipping input data in the memory unit 2.

When input data is acquired indicating that five loose sample items are to be shipped, as shown in FIG. 16(c), the data generating unit 23 generates the shipping input data shown in FIG. 16(d) based on this input data. That is, the data generating unit 23 generates the shipping input data including an automatically generated shipping number such as "B002", a trade category name such as "shipment", a product name such as "syringe", a case loose category such as "loose", and the number of items shipped, as shown in FIG. 16(d).

In this example, the case bulk category is "bulk". Therefore, the data generation unit 23 references the product master 11 as described above to obtain the bulk product code, "A001-01". The data generation unit 23 then reads the barcode with a handy barcode reader, updating (rewriting) the product code "A001", which was uniformly for cases, to the bulk product code "A001-01". This allows the master creation staff or business operator to achieve the same effect as described above, such as being able to manage the master without having to be aware of creating masters separately for cased products and bulk products. The storage control unit 22 stores this shipment input data in the storage unit 2.

Furthermore, when the data generation unit 23 acquires input data showing that one case of products is to be shipped normally, as shown in FIG. 16(e), the data generation unit 23 generates the shipping input data shown in FIG. 16(f) based on this input data. That is, as shown in FIG. 16(f), the data generation unit 23 generates shipping input data including an automatically generated shipping number such as "B003", the trade category name "shipment", the product code "A001" which is the product code for cased products, the product name such as "syringe", the case bulk category "case", and the number of shipments. The memory control unit 22 stores this shipping input data in the memory unit 2.

(Sales input operation)
Next, the operation of inputting sales of a product will be described with reference to the flowchart of FIG. 17. When the business operator specifies the display of the sales input screen, the process proceeds from step S31 to step S32, and the display control unit 24 displays the sales input screen via the output device 7. When the business operator inputs information about a product via this sales input screen, the acquisition unit 21 acquires the input information about the product as input data. The data generation unit 23 generates sales input data based on the acquired input data (step S32). The memory control unit 22 stores the generated sales input data in the memory unit 2.

Figure 18(a) is an example of input data for sample products distributed in cases. In this case, the business operator refers to the transaction category master 15 shown in Figure 6 and inputs the transaction category code of "UT002" indicating that the sale is of sample products. In addition, "A001" is input as the product code, and "case" is input as the case-specific category. Figure 18(b) is an example of sales input data generated by the data generation unit 23 based on the input data of Figure 18(a). As shown in Figure 18(b), the data generation unit 23 generates sales input data for sample sales, including the automatically generated purchase number of "U001", the transaction category code of "UT002", the product code of "A001", the product name of "syringe", the case-specific category of "case", the sales quantity, and the debt subject category of "accounts receivable".

The data generation unit 23 then determines whether the transaction category code included in the generated sales input data is a transaction category code indicating "sample sales" (UT002 in this example) (step S33). If the transaction category code is a transaction category code indicating "sample sales" (step S33: Yes), a sales of "0 yen" is assumed. Therefore, in step S34, the data generation unit 23 generates journal entry data for "no journal entry". The memory control unit 22 adds this journal entry data for "no journal entry" to the sales input data and stores it in the memory unit 2.

Similarly, Figures 18(c) and 18(d) show an example in which the transaction category code included in the generated sales input data is "UT002", which indicates "sample sales" (step S33: Yes), and the case bulk category is "bulk". In this case, as the case bulk category is "bulk", the data generation unit 23 automatically updates the case product code (A001) to the bulk product code (A001-01), as described above.

In the case of "single items," the transaction category code is also a transaction category code indicating "sample sales" (step S33: Yes), so sales of "0 yen" are expected. Therefore, in step S34, the data generation unit 23 generates journal entry data for "no journal entry." The storage control unit 22 adds this journal entry data for "no journal entry" to the sales input data and stores it in the storage unit 2.

In contrast, FIG. 18(e) is an example of input data for a case of a product with product code "A001" that has been sold normally. In other words, this is an example of input data for a case in which a product with product code "A001" has been sold, rather than distributed as a sample. In this case, the business operator refers to the transaction category association master 16 shown in FIG. 7, and inputs the transaction category code "UT001", which indicates that this is a normal sale, as shown in FIG. 18(e).

Based on this input data, the data generation unit 23 generates sales input data for normal sales, including the automatically generated purchase number "U003", the transaction category code "UT001", the product code "A001", the product name "syringe", the loose case category "case", the sales quantity, and the debt item category "accounts receivable", as shown in FIG. 18 (f).

Here, in the examples of Figures 18(e) and 18(f), the transaction category code is not a transaction category code indicating "sample sales" but a transaction category code (UT001) indicating normal "sales" (step S33: No). Therefore, in step S35, the data generation unit 23 detects the account item (sales) corresponding to the transaction category code of "UT001" from the transaction category item association master 16 shown in Figure 7, and sets this on the credit side of the journal entry data.

The data generation unit 23 also sets the account category of "accounts receivable" to the debit side of the journal entry data based on the debt account category of the sales input data. This makes it possible to generate journal entry data of "accounts receivable/sales" as shown in FIG. 18(f). The memory control unit 22 adds this journal entry data to the sales input data and stores it in the memory unit 2.

The accounting data stored in the memory unit 2 is recorded in an accounting system provided on a server device on a specified network, or in an accounting system provided in the memory unit 2.

(Product change input operation)
Next, the product change input operation will be described with reference to the flowchart of FIG. 19. This product change input is used when inventory management is performed by breaking down case product inventory into bulk product inventory in advance. When the business operator specifies the display of the product change input screen, the process proceeds from step S41 to step S42, and the display control unit 24 displays the dispensing information input screen via the output device 7. When the business operator inputs product dispensing information via the dispensing information input screen, the acquisition unit 21 acquires the input product dispensing information as input data. The data generation unit 23 generates dispensing data as exemplified in FIG. 20(a) based on the acquired input data (step S42). The memory control unit 22 stores the generated dispensing data in the memory unit 2. The example of dispensing data as exemplified in FIG. 20(a) indicates that one case of product with product code "A001" has been dispensed.

In step S43, the data generation unit 23 determines whether the loose case classification of the dispensing data is "case." In the case of the dispensing data illustrated in FIG. 20(a), the loose case classification is "case" (step S43: Yes). Therefore, in step S44, the data generation unit 23 generates receiving data in which the loose case classification is set to "loose" as illustrated in FIG. 20(b), the loose product code detected by referencing the product master 11 as described above is set, and the number of products when the cased products are broken down into loose products is set as the inventory quantity.

If the case classification of the dispensing data is "Bulk" (step S43: No), the product change input operation shown in FIG. 19 is terminated.

Next, in step S45, the data generation unit 23 generates product change input data corresponding to the dispensing data and receiving data. An example of product change input data is shown in FIG. 21. As shown in FIG. 21, the data generation unit 23 generates product change input data for a "case" with a transaction category of "product change" and a product code of "A001" and a product name of "syringe."

At the same time, the data generation unit 23 generates product change input data for the transaction category "product change", product code "A001-01", and product name "syringe" for "loose". The data generation unit 23 then inputs the number of items in and out of stock in the product change input data for "case" as "-1", and references the number of items in one case in the product master 11 shown in FIG. 2 (in this example, one case contains 20 items), and inputs the number of loose items stored in one case, for example "20 items", as the number of items in and out of stock in the product change input data for "loose". The memory control unit 22 stores the product change input data in the memory unit 2. This makes it possible to manage inventory by breaking down case item inventory into loose item inventory in advance.

(Effects of the embodiment)
As is clear from the above description, the information processing device 1 according to the embodiment can achieve the following effects.

1. Master data creators or business operators can manage master data without having to worry about creating master data for cased items and loose items separately.

2. The only decision that the person in charge of operations has to make is whether the shipment is for cases or loose items, and they do not need to determine the product codes for cased and loose items.

3. Accounting staff will no longer need to transfer expenses for invoices recorded for promotional purposes.

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

In addition, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, which can contribute to the achievement of SDGs goals 12, 13, and 15.

In addition, this embodiment can contribute to strengthening control and governance, making it possible to contribute to Goal 16 of the SDGs.

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

For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.

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

Furthermore, with regard to the information processing device 1, each component shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure.

For example, the processing functions of the information processing device 1, particularly the control unit 3 and each processing function performed by the control unit 3, may be realized in whole or in part by a CPU (Central Processing Unit) and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-transient computer-readable recording medium that contains programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the information processing device 1 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD to work with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit 3.

In addition, the information processing program of the information processing device 1 may be stored in another server device connected to the information processing device 1 via any network, and all or part of it may be downloaded as necessary.

In addition, the information processing 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 product. Here, this "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.

A "program" is a data processing method written in any language or description method, and may be in any format, such as source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, and a structure that achieves its function by working together with a separate program, such as an OS. Note that the specific structure and reading procedure for reading a recording medium in the information processing device 1 shown in the embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

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

In addition, the information processing device 1 may be configured as an information processing device such as a known personal computer device or a workstation, or may be configured as an information processing device to which any peripheral device is connected. In addition, the information processing device may be realized by implementing software (including programs or data, etc.) that realizes the processing described in this embodiment.

Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various additions or function additions. In other words, the above-mentioned embodiments can be implemented in any combination, or the embodiments can be implemented selectively.

The present invention is useful for inventory management of loose items and cased items provided as samples, etc.

REFERENCE SIGNS LIST 1 Information processing device 2 Memory unit 3 Control unit 4 Communication interface unit 5 Input/output interface unit 6 Input device 7 Output device 11 Product master 12 Asset classification master 13 Subject classification master 14 General master 15 Transaction classification master 16 Transaction classification association master 17 Supplier master 18 Customer master 21 Acquisition unit 22 Memory control unit 23 Data generation unit 24 Display control unit

Claims (9)

An acquisition unit that acquires classification information of either single item classification information indicating that the handling unit is a single item or case item classification information indicating that the handling unit is a case item in which multiple items are bundled together, and a product code of the product;
a storage control unit that associates the category information and the product code acquired by the acquisition unit and stores them in a database;
a data generating unit that generates predetermined data including the input product code and the category information,
the storage control unit stores the predetermined data generated by the data generation unit in a storage unit, and when the classification information is the single item classification information, extracts a single item product code associated with the single item classification information from a database, and rewrites the product code of the predetermined data to the single item product code extracted from the database;
An information processing device comprising: when the acquisition unit acquires the case item classification information as the classification information, the storage control unit associates the case item classification information with the product code and stores them in the database, and generates a single item product code to be added to the product whose handling unit is a single item, and stores the code in the database in association with at least the single item classification information;
2. The information processing apparatus according to claim 1, the storage control unit associates the generated single item product code with the single item classification information and also associates the single item product code with the case item classification information stored in the database;
3. The information processing apparatus according to claim 2 , the data generating unit generates, as the predetermined data, data including the commodity code and the category information, as well as transaction category information indicating whether the commodity is at least a purchased commodity or a sample commodity;
4. The information processing device according to claim 1, wherein : The storage control unit stores the asset classification information and the debt subject classification information in the database in association with the classification information and the product code,
when generating purchase input data including transaction classification information indicating that the product is purchased as the sample product as the predetermined data, the data generating unit adds journal entry data generated based on the debt item classification indicated by the debt item classification information stored in the database and the asset classification indicated by the asset classification information;
5. The information processing apparatus according to claim 4, When the data generation unit generates sales input data including transaction classification information indicating that the product is a sample product as the predetermined data, the data generation unit adds journal entry data of "no journal entry" to the sales input data.
6. The information processing device according to claim 4 or 5, the data generating unit generates product change input data in which the single item classification information, the single item product code, and the number of items received, which is the number of items obtained by breaking down the case items into the single items, are associated with each other when the case items are selected as the product of the dispensing data;
7. The information processing device according to claim 3, wherein: an acquisition step in which an acquisition unit acquires classification information of either single item classification information indicating that the handling unit is a single item or cased item classification information indicating that the handling unit is a cased item in which a plurality of the items are bundled together, and a product code of the item;
a storage control step of storing, in a database, the category information and the product code acquired by the acquisition unit in association with each other, by a storage control unit;
a data generating step in which a data generating unit generates predetermined data including the input product code and the category information,
In the storage control step, the predetermined data generated in the data generation step is stored in a storage unit, and when the classification information is the single item classification information, a single item product code associated with the single item classification information is extracted from a database, and the product code of the predetermined data is rewritten to the single item product code extracted from the database;
An information processing method comprising: Computer,
An acquisition unit that acquires classification information of either single item classification information indicating that the handling unit is a single item or case item classification information indicating that the handling unit is a case item in which a plurality of the items are bundled together, and a product code of the item;
a storage control unit that associates the category information and the product code acquired by the acquisition unit and stores them in a database ;
a data generating unit that generates predetermined data including the input product code and the category information;
the storage control unit stores the predetermined data generated by the data generation unit in a storage unit, and when the classification information is the single item classification information, extracts a single item product code associated with the single item classification information from a database, and rewrites the product code of the predetermined data to the single item product code extracted from the database;
An information processing program characterized by:

Images