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

Abstract

To facilitate inventory control for unpacked articles and case articles provided as a sample article, for example.SOLUTION: An acquisition unit acquires any segmentation information and commodity code among commodities of single article segmentation information indicating that a handling unit is a single commodity or case article segmentation information indicating that the handling unit is a case commodity gathering a plurality of commodities. A storage control unit stores the segmentation information acquired by the acquisition unit and the commodity code in association with each other in a database. Then, when the case article segmentation information is acquired by the acquisition unit as segmentation information, the storage control unit stores the case article segmentation information and the commodity code in association with each other in the database, and generates a single article commodity code to be added to the commodity having the handling unit of the single article to store it at least in association with the single segmentation information in the database. A master can be separately created without considering the case article or the single article to facilitate inventory management for the case article and the single article.SELECTED DRAWING: Figure 11

Description

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

Today, sample products for the purpose of sales promotion, etc. are sometimes provided individually (individually) or in units of cases.

In the case of the inventory management device disclosed in Patent Document 1 (Japanese Unexamined Patent Application Publication No. 2007-276990), for each product sold in a set composed of a combination of one or more types of products sold separately, a product for sale in a set is created. Receives the input of the number of points and the quantity of individual products to be sold separately to be incorporated into the product for set sale. When the number of items to be sold as a set and the quantity by type of the product for sale as a set are input, the number of items to be created for the product for sale as a set for each type of product for each individual product incorporated in the product for sale as a set is calculated. The product inventory data stored in the inventory management file is updated by subtracting the multiplied value. As a result, even in the case of dealing in a set product composed of a combination of one or more types of individual products, the stock quantity of each product can be managed accurately.

JP 2007-276990 A

However, when products are provided in bulk units and case units, it is necessary to perform inventory management for two different products, bulk and case products. For this reason, it is necessary to operate while judging bulk products and case products each time, which causes the occurrence of operational errors and increases the workload of business operators.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and an object of the present invention is to provide an information processing apparatus, an information processing method, and an information processing program that facilitate inventory management of bulk products and case products provided as sample products, for example. do.

In order to solve the above-described problems and achieve the object, an information processing apparatus according to the present invention provides single item classification information indicating that the handling unit is a single item, or collectively handles a plurality of items as a handling unit. an acquisition unit that acquires one of the case product category information indicating that the product is a case product and the product code of the product, and associates the category information and the product code acquired by the acquisition unit. a storage control unit for storing in a database, the storage control unit, when the acquisition unit acquires the case product classification information as the category information, stores the case product classification information and the product code in the database in association with each other; It is characterized by generating a single-item product code to be added to a single-item product as a handling unit, and storing it in a database in association with at least the single-item classification information.

In order to solve the above-described problems and achieve the object, the information processing method according to the present invention provides an information processing method in which the acquisition unit obtains single product classification information indicating that the handling unit is a single product, or a plurality of handling units. an acquisition step of acquiring any of the category information and the product code of the product out of the case product category information indicating that the product is a case product grouped together from the products; a storage control step of associating the acquired category information with the product code and storing them in a database; when the case product category information is acquired as the category information in the acquiring step, the storage control step stores the case product category information and the product code; A product code is associated and stored in a database, and a product code for a single product is generated to be added to a product handled as a single product, and stored in the database in association with at least single product classification information.

In order to solve the above-described problems and achieve the object, an information processing program according to the present invention provides a computer with single product classification information indicating that the handling unit is a single product, or a plurality of handling units. An acquisition unit that acquires any of the category information and the product code of the product from among the case product category information indicating that the product is a case product grouped together, and the category information acquired by the acquisition unit and the product code to be stored in the database, and when the acquisition unit acquires the case product classification information as the category information, the storage control unit associates the case product classification information and the product code and stores them in the database. In addition to storing, a product code for a single product is generated to be added to a product whose handling unit is a single product, and stored in a database in association with at least the single product classification information.

ADVANTAGE OF THE INVENTION According to this invention, it is effective in the ability to facilitate the inventory management of the bulk goods and case goods provided as a sample goods, for example.

FIG. 1 is a block diagram showing the hardware configuration of an information processing apparatus according to an embodiment. FIG. 2 is a diagram showing an example of a product master. FIG. 3 is a diagram showing an example of an asset classification master. FIG. 4 is a diagram showing an example of the subject division master. FIG. 5 is a diagram showing an example of a general-purpose master. FIG. 6 is a diagram showing an example of a transaction classification master. FIG. 7 is a diagram showing an example of a transaction classification association master. FIG. 8 is a diagram showing an example of a supplier master. FIG. 9 is a diagram showing an example of a customer master. FIG. 10 is a flow chart showing the flow of the product master creation operation. FIG. 11 is a diagram showing an example of data registered in the product master. FIG. 12 is a flow chart showing the flow of an operation for generating order input data. FIG. 13 is a diagram showing an example of order input data. FIG. 14 is a flow chart showing the flow of the purchase input data generation operation. FIG. 15 is a diagram showing an example of purchase input data. FIG. 16 is a diagram showing an example of shipping input data. FIG. 17 is a flow chart showing the flow of operations for generating sales input data. FIG. 18 is a diagram showing an example of sales input data. FIG. 19 is a flow chart showing the flow of the operation for generating product change input data. FIG. 20 is a diagram showing an example of payout data and acceptance data at the time of product change input. FIG. 21 is a diagram showing an example of product change input data.

An information processing apparatus according to an embodiment to which the present invention is applied will be described in detail below with reference to the drawings. It should be noted that the present invention is not limited by this embodiment.

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

An input device 6 and an output device 7 are connected to the input/output interface section 5 . A monitor device (including a home television) can be used as the output device 7 . As the input device 6, in addition to a keyboard device, a mouse device, and a microphone device, a monitor device that realizes a pointing device function in cooperation with a mouse device can be used.

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

In addition, the storage unit 2 stores an information processing program for inventory management of products that are handled individually (bulk products) and products that are handled in units of cases (case products) that are a collection of multiple products. remembered. The storage unit 2 also stores various data such as order input data, purchase input data, shipment input data, sales input data, product change input data, and the like, which are generated based on this information processing program.

In the product master 11, as illustrated in FIG. 2, product code, product name, case loose classification (an example of classification information), quantity, Japanese Article Number Code (JANCD), loose product code, asset classification , product data including each information such as sample debt item category. In the information processing apparatus 1 according to the embodiment, when product data with a case loose classification of "case product (an example of case product classification information)" is registered in the product master 11, the "loose product" constituting the "case product" is automatically generated, and registered in the product master 11 in association with the product data of "case product". As a result, the person in charge of creating the master and the business operator can manage the master without being conscious of case products and bulk products separately. Details will be described later.

The asset classification master 12 stores asset classification data including information such as asset classification codes and asset classification names, as illustrated in FIG. In the example of FIG. 3, the asset classification code "S001" is associated with the asset classification name "Sales Promotion Expenses", and the asset classification code "S003" is registered as the asset classification "Supplies". This is an example in which first names are associated and registered.

The subject classification master 13 stores subject classification data including information such as subject classification codes and subject classification names, as illustrated in FIG. In the example of Fig. 4, the account class name "Accounts receivable" is associated with the account class code "KA001" and the account class name "Accounts payable" is registered. are registered in association with each other.

In the general-purpose master 14, as shown in FIG. 5, by registering product data with a case loose classification of "case product" for the product master 11, product data of "individual product" is automatically generated. A rule for generating a bulk item code (an example of a single item code) is stored. Specifically, the general-purpose master 14 stores bulk product end data to be added to the end of the product code of the “case product”. The example of FIG. 5 shows that the code "-01" is added to the end of the product code of "case product" to generate bulk product end data. Details will be described later.

As illustrated in FIG. 6, the transaction classification master 15 stores transaction classification data including information such as transaction classification codes, transaction classification names, and sample transactions. The example of FIG. 6 is an example in which a transaction category code of "JT001" is stored in association with a transaction category name of "order placement" and a sample transaction of "non-applicable". Also, the example of FIG. 6 is an example in which a transaction category name of "sample sales" and a sample transaction of "corresponding" are associated with a transaction category code of "UT002" and stored.

The transaction category association master 16 stores transaction category association data including transaction category codes and transaction category names as illustrated in FIG. The example of FIG. 7 is an example in which a transaction category code of "JT002" is stored in association with a transaction category name of "sample order placement". Also, the example of FIG. 7 is an example in which a transaction category name of "sample sales" is associated with a transaction category code (sales) of "UT002" and stored. The example of FIG. 7 is an example in which the transaction category code (purchase) of "ST002" is associated with the transaction category name of "sample purchase" and stored.

The supplier master 17 stores supplier data including a supplier code and an obligation item classification as shown in FIG. In the example of FIG. 8, each of the vendor codes of "Vendor A", "Vendor B" and "Vendor C" is associated with the debt item category of "KB001" and stored. This is an example of

The customer master 18 stores customer data including customer codes and debt item classifications, as illustrated in FIG. In the example shown in FIG. 9, each of the customer codes "customer A", "customer B" and "customer C" is stored in association with the debt item category "KB001". is.

(Functional configuration)
Next, the control unit 3 functions as the transaction unit 21 , the storage control unit 22 , the data generation unit 23 and the display control unit 24 by executing the information processing program stored in the storage unit 2 .

The trading unit 21 acquires product data input via the input device 6 by a business operator or the like when the product master 11 is generated. The acquisition unit 21 also acquires order input data input by a business operator or the like when inputting an order, receipt input data input by a business operator or the like when inputting purchases, and the like. 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. Further, when the product master 11 is generated, product data of bulk products automatically generated by a data generation unit 23 (to be described later) is registered in association with product data of case products.

The data generation unit 23 automatically generates product data for bulk products when product data for case products is registered in the product master 11 when the product master 11 is generated. The display control unit 24 displays on the output device 7 a product data registration screen that is input and operated by the business operator when product data is registered in the product master 11 . In addition, the display control unit 24 displays an order entry screen that is input and operated by the business operator on the output device 7 when inputting an order, and outputs a purchase input screen that is input and operated by the business operator when inputting purchases. Displayed on device 7 . The display control unit 24 also displays, on the output device 7, an input screen or the like corresponding to the input operation of the business operator.

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

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

FIG. 11(a) shows an example of product data input by a business operator. In the example of FIG. 11(a), the product code is "A001", the jean code is "123456", and the case loose classification is "case". This is an example entered by

Among the product data shown in FIG. 11(a), the "asset classification" is displayed on the output device 7 by the business operator as a list of the asset classification data stored in the asset classification master 12 shown in FIG. Select and enter the asset classification corresponding to the product data to be registered. The example of FIG. 11A is an example in which "sales promotion expenses" with an asset classification code of "S001" is selected and input as the "asset classification".

11(a), the business operator displays a list of the item classification data stored in the item classification master 13 shown in FIG. From among these, select and enter the item category corresponding to the product data to be registered. The example of FIG. 11(a) is an example in which the item classification code "KB002" and "accounts payable" are selected and input as the "sample debt item classification".

Next, in step S2, the data generation unit 23 determines whether or not the case-discretion classification of the product data input by the business operator is "case". If the case loose classification is "case" (step S2: Yes), the process proceeds to step S3. Go to step S6.

In the case of the example of FIG. 11(a), the case-by-case classification of the product data input 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 (case data) of "case" as shown in the record in the upper row of FIG. 11(b). The storage control unit 22 registers the generated case data in the product master 11 of the storage unit 2 .

Further, the data generation unit 23 generates case data as described above, and also generates separate product codes for separate products obtained by dividing the case product into individual products (step S4). That is, the data generator 23 acquires the loose product end data by referring to the general-purpose master 14 shown in FIG. Then, the data generation unit 23 adds this bulk product end data to the end of the product code of the case product to generate a bulk product code for the bulk product. In the case of the example of FIG. 5, the loose product end data is "-01". In addition, in the examples of FIGS. 11(a) and 11(b), the product code of the case product is "A001". Therefore, the data generation unit 23 generates the bulk product code of "A001-01" by adding the bulk product end data of "-01" to the end of the case product code of "A001". .

After generating the bulk product code in this way, the data generation unit 23 generates the bulk product code with the above-mentioned "A001-01" as the product code, as shown in the lower row record in FIG. 11(b). Generate a separate product code. The storage control unit 22 registers the generated loose product code in the product master 11 . At this time, as shown in FIG. 11(b), the storage control unit 22 registers the separate product code of "A001-01" in the input field of "separate product code" of the previously registered case data. (step S5), and the product data registration operation shown in the flow chart of FIG. 10 is completed. As a result, the case data and the separate data can be registered in the product master 11 in association with each other. Further, when the case loose classification is "case", separate data can be automatically generated and registered in the product master 11 .

Therefore, the person in charge of master creation or the business operator can perform master management without being conscious of separately creating masters for case products and bulk products. In addition, the business operator or the like can eliminate the need to judge the commodity code by simply judging whether the current shipping business is case goods or bulk goods (just by judging the case bulk classification). Therefore, it is possible to prevent inconveniences such as the occurrence of operation errors and an increase in the work load of the business operator due to the production of two commodities having different stock management units and the operation being performed while making judgments each time.

On the other hand, in step S2, when it is determined that the case loose classification is "loose" (step S2: No), and the process proceeds to step S6, the data generation unit 23 performs the processing shown in FIG. In b), loose data exemplified as records in the lower row are generated. The storage control unit 22 registers the generated separate data in the product master 11, and ends the product data registration operation shown in the flowchart of FIG. In this way, the product master 11 is generated by registering the case data and the separate data each time.

(Order entry operation)
Next, the operation of inputting an order for cased items, bulk items, or regular order items distributed as samples will be described with reference to the flow chart of FIG. When the business operator designates 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. FIG. When the business operator inputs information about the ordered product through this order entry screen, the information is acquired by the acquiring unit 21 (step S12). The data generation unit 23 generates order input data with the product code for the case product as the product code for the case product regardless of whether it is a case product or a bulk product (step S13). That is, the data generation unit 23 generates order input data to which case product codes are assigned to both case products and bulk products. The storage control unit 22 stores the generated order input data in the storage unit 2 .

Next, the storage control unit 22 detects the input order data whose case loose classification is "separate" from the order input data stored in the storage unit 2 (step S14). When the storage control unit 22 detects order input data whose case loose classification is "separate" (step S14: Yes), the separate product code is detected by referring to the product master 11 shown in FIG. do. Then, the product code for the case product in the order input data whose case loose classification is "separate" is updated (rewritten) to the loose product code detected from the product master 11 (step S15). All the processing of the order input operation shown in 12 is ended.

More specifically, FIG. 13(a) shows input data input 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 inputs the transaction category code "JT002" of "sample order placement" as the transaction category code. In addition, "A001" is entered as the product code, and "case" is entered as the case loose classification. As shown in FIG. 13(b), the memory control unit 22 automatically assigns an order receipt number such as "J001", and once according to the input data, the transaction classification code is "JT002", the product code is "A001", the case The order input data whose separate classification is "case" is generated and stored in the storage unit 2. - 特許庁In this case, since the case-variable classification is "case", the storage control unit 22 does not perform the product code updating process described in steps S14 and S15.

The examples of FIGS. 13(e) and 13(f) are examples of input data and order input data when a case product is normally ordered. This case is also the same as in FIGS. 13(a) and 13(b), and since the case variation classification is "case", the storage control unit 22 performs the product code updating process described in steps S14 and S15. is not performed.

On the other hand, FIGS. 13(c) and 13(d) are examples of input data and order input data when receiving an order for bulk sample products. In this case, "individual" is specified as the case-individual category. Even in this case, the storage control unit 22 once generates order input data with a transaction classification code of “JT002”, a commodity code of “A001”, and a case loose classification of “separate” according to the input data. memorize to However, since the case loose classification is "separate", the product code of "A001", which is the product code of the case product, is replaced with the product code of the loose product detected from the product master 11, as shown in FIG. 13(d). Update processing (rewriting processing) is performed to a product code of a certain “A001-01”.

As a result, even if the business operator uses the case product code for both the case product and bulk product product codes, if the case loose classification is "individual", the product will automatically be classified as a bulk product. You can fix it in your code. Therefore, the business operator can input the input data without worrying about the product codes of case products and bulk products.

(Purchase input operation)
Next, the commodity purchase input operation will be described with reference to the flow chart of FIG. When the business operator designates 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. FIG. When the business operator inputs information on the product to be purchased via this purchase input screen, the acquisition unit 21 acquires the input information on the product as input data. The data generator 23 generates purchase input data based on the acquired input data (step S22). The storage control unit 22 stores the generated purchase input data in the storage unit 2 .

FIG. 15(a) is an example of input data of sample products distributed in cases. In this case, the business operator refers to the transaction classification master 15 shown in FIG. 6, and inputs the transaction classification code "ST002" indicating the purchase of sample products. Also, "A001" is entered as the product code, and "case" is entered as the case-by-case classification. FIG. 15(b) is an example of purchase input data generated by the data generator 23 based on the input data of FIG. 15(a). When the transaction classification code of the input data is "ST002", the data generator 23 refers to the product master 11 to indicate "purchase of sample goods (sample purchase)" as shown in FIG. Then, "KB002", which is the sample debt item category code of the case product with the product code "A001", is acquired. Then, as shown in FIG. 15(b), the data generation unit 23 generates the automatically numbered purchase number "S001", the transaction classification code "ST002", the product code "A001", and the product "syringe". Generate purchase input data for sample purchases, including name, case loose classification of "Case", number of purchases, and liability item classification code of "KB002".

Here, the data generator 23 determines whether or not the transaction classification code included in the generated purchase input data is a transaction classification code (in this example, ST002) indicating "sample purchase" ( step S23). If the transaction classification code is a transaction classification code indicating "sample purchase" (step S23: Yes), the data generator 23 sets the asset classification to debit and the sample debt item classification to credit in step S24. Generate set journal data.

That is, in the example of FIG. 15B, referring to the product master shown in FIG. 2 based on the product code of "A001", which is the product code of the case product, the asset classification code of "S001" can be obtained. can. The data generator 23 obtains the asset classification of "sales promotion expenses" by referring to the asset classification master 12 shown in FIG. 3 based on the asset classification code of "S001". The data generation unit 23 sets this "sales promotion fee" to the debit side of the journal data.

Further, the data generator 23 refers to the item classification master 13 shown in FIG. 4 based on the debt item classification code "KB002". This will give you a sample debt line item category of "Accounts Payable". The data generator 23 sets this "accounts payable" as the credit of the journal data. As a result, it is possible to generate journal data of "sales promotion expenses/accounts payable" as shown in FIG. 15(b). The storage control unit 22 stores this journal data in the storage unit 2 by adding it to the purchase input data.

Similarly, in FIGS. 15(c) and 15(d), the transaction classification code included in the generated purchase input data is the transaction classification code "ST002" indicating "sample purchase" (step S23: Yes). In this case, the data generation unit 23 automatically generates the product code (A001-01) for the loose product, as described above, since the loose case classification is "separate".

Along with this, the data generator 23 refers to the product master shown in FIG. 2 based on the product code “A001-01”, which is the product code for the bulk, and obtains the asset classification code “S001”. The data generator 23 obtains the asset classification of "sales promotion expenses" by referring to the asset classification master 12 shown in FIG. 3 based on the asset classification code of "S001". The data generation unit 23 sets this "sales promotion fee" to the debit side of the journal data.

Further, the data generation unit 23 refers to the item classification master 13 shown in FIG. 4 based on the obligation item classification code of "KB002" to obtain the sample obligation item classification of "accounts payable". The data generator 23 sets this "accounts payable" as the credit of the journal data. As a result, it is possible to generate journal data of "sales promotion expenses/accounts payable" as shown in FIG. 15(b). The storage control unit 22 stores this journal data in the storage unit 2 by adding it to the purchase input data.

On the other hand, FIG. 15(e) is an example of input data when the product with the product code "A001" is normally purchased by the case. In other words, this is an example of input data when a product with a product code of "A001" is not purchased as a sample but purchased. In this case, the business operator refers to the transaction classification association master 16 shown in FIG. 7, and inputs the transaction classification code "ST001" indicating normal purchase as shown in FIG. 15(e). do.

The data generation unit 23 refers to the supplier master shown in FIG. 8 based on the supplier from whom the product "A001" was purchased, and obtains, for example, the debt item classification code "KB001". Then, as shown in FIG. 15(f), the data generation unit 23 generates a purchase number that is automatically subdivided such as "S003", a transaction classification code of "ST001", and a debt item classification of "KB001". Generate purchase entry data for regular purchases, including codes.

Here, in the examples of FIGS. 15(e) and 15(f), the transaction classification code is not a transaction classification code indicating "sample purchase" but a transaction classification code (ST001) indicating normal "purchase". Yes (step S23: No). Therefore, in step S25, the data generator 23 detects the account item (purchase) corresponding to the transaction category code "ST001" from the transaction category item association master 16 shown in FIG. Set to debit.

Further, the data generator 23 refers to the item classification master 13 shown in FIG. 4 based on the debt item classification code of "KB001" to obtain the item classification of "accounts payable". Then, this item classification is set as the credit of the journal data. As a result, journal data of "Purchase/Accounts Payable" can be generated as shown in FIG. 15(f). The storage control unit 22 stores this journal data in the storage unit 2 by adding it to the purchase input data.

This journal data is recorded in an accounting system provided in a server device on a predetermined network or in an accounting system provided in the storage unit 2. FIG.

(Shipping input operation)
Next, the shipping input operation will be described. When a business operator performs a shipping business, a handheld barcode reader reads a barcode printed or attached with a sticker to a box (case) in which products are packed. Therefore, as shown in FIGS. 16(a), 16(c) and 16(e), the product code of the input data is "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 shipping one case of sample products. FIG. 16(c) is an example of input data when shipping five loose sample products. FIG. 16(e) is an example of input data for normal shipment of one case of merchandise.

Such input data is acquired by the acquisition unit 21 . When the input data indicating the shipment of one case of sample products shown in FIG. to generate That is, as shown in FIG. 16(b), the data generating unit 23 generates a shipment number such as "B001" that is automatically numbered, a transaction classification name such as "shipment", and a product code of the case product "A001". , a product name such as "syringe," a separate classification from "case," and shipping input data including the number of shipments. The storage control unit 22 stores this shipping input data in the storage unit 2 .

Also, when the input data indicating the shipment of five individual sample products shown in FIG. 16(c) is acquired, the shipment input data shown in FIG. 16(d) is generated based on this input data. do. That is, as shown in FIG. 16D, the data generation unit 23 generates automatically numbered shipment numbers such as "B002", transaction classification names such as "shipment", product names such as "syringes", and "barrels". ” and shipping input data including the number of shipments.

Also, in this example, the case loose classification is "separate". Therefore, the data generator 23 refers to the product master 11 as described above and obtains the product code for the bulk product, which is "A001-01". Then, the data generation unit 23 reads the barcode using a handheld barcode reader, thereby changing the product code of "A001", which was uniformly used for cases, to the product code of "A001-01" for bulk products. Update (rewrite) the code. As a result, the person in charge of master preparation or the business operator can obtain the same effects as described above, such as being able to perform master management without being conscious of preparing separate masters for case products and bulk products. The storage control unit 22 stores this shipping input data in the storage unit 2 .

16(e), the data generating unit 23 acquires the input data indicating normal shipment of one case of products, based on this input data, generates the shipment data shown in FIG. 16(f). Generate input data. That is, as shown in FIG. 16(f), the data generation unit 23 generates an automatically numbered shipment number such as "B003", a transaction classification name such as "shipment", and a case product code "A001". , a product name such as "syringe," a separate classification from "case," and shipping input data including the number of shipments. The storage control unit 22 stores this shipping input data in the storage unit 2 .

(Sales input operation)
Next, the product sales input operation will be described with reference to the flow chart of FIG. When the business operator designates 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. FIG. When the business operator inputs the information on the product via this sales input screen, the acquisition unit 21 acquires the input information on the product as input data. The data generator 23 generates sales input data based on the acquired input data (step S32). The storage control unit 22 stores the generated sales input data in the storage unit 2 .

FIG. 18(a) is an example of input data of sample products distributed in cases. In this case, the business operator refers to the transaction classification master 15 shown in FIG. 6 and inputs the transaction classification code "UT002" indicating the sales of sample products. Also, "A001" is entered as the product code, and "case" is entered as the case-by-case classification. FIG. 18(b) is an example of sales input data generated by the data generator 23 based on the input data of FIG. 18(a). As shown in FIG. 18(b), the data generator 23 generates the automatically numbered purchase number "U001", the transaction classification code "UT002", the product code "A001", and the product name "syringe". , the sales input data for the sample sales, including the case loose classification of "Cases", the number of sales, and the liability category of "Receivables".

Here, the data generation unit 23 determines whether or not the transaction classification code included in the generated sales input data is a transaction classification 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), sales of "0 yen" are assumed. Therefore, in step S34, the data generation unit 23 generates journal data of "no journal". The storage control unit 22 adds this “no journal” journal data to the sales input data and stores it in the storage unit 2 .

Similarly, in FIGS. 18(c) and 18(d), the transaction classification code included in the generated sales input data is the transaction classification code "UT002" indicating "sample sales" (step S33: Yes). , is an example in which the case rose category is "rose". In this case, the data generation unit 23 automatically updates the case product code (A001) to the separate product code (A001-01) because the case loose classification is “separate”. As mentioned above.

Also, in the case of "loose", since the transaction classification code is a transaction classification code indicating "sample sales" (step S33: Yes), sales of "0 yen" are assumed. Therefore, in step S34, the data generation unit 23 generates journal data of "no journal". The storage control unit 22 adds this “no journal” journal data to the sales input data and stores it in the storage unit 2 .

On the other hand, FIG. 18E is an example of input data in the case of normal sales of the product with the product code "A001" in the case. That is, this is an example of input data when the product with the product code "A001" is sold, not distributed as a sample product. 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" indicating normal sales as shown in FIG. 18(e). .

Based on this input data, as shown in FIG. Generate sales input data for regular sales, including the product name of "Syringe", the case loose category of "Case", the number of sales, and the liability category of "Accounts Receivable".

Here, in the examples of FIGS. 18(e) and 18(f), the transaction classification code is not a transaction classification code indicating "sample sales" but a transaction classification code (UT001) indicating normal "sales" ( Step S33: No). Therefore, in step S35, the data generator 23 detects the account item (sales) corresponding to the transaction category code "UT001" from the transaction category item association master 16 shown in FIG. set to

In addition, the data generation unit 23 sets the item classification of "accounts receivable" to the debit side of the journal data based on the debt item classification of the sales input data. As a result, journal data of "accounts receivable/sales" can be generated as shown in FIG. 18(f). The storage control unit 22 stores this journal data in the storage unit 2 by adding it to the sales input data.

The journal data stored in the storage unit 2 is accounted for by an accounting system installed in a server device on a predetermined network or an accounting system installed in the storage unit 2 .

(Product change input operation)
Next, the product change input operation will be described with reference to the flowchart of FIG. This product change input is used, for example, when performing inventory management by breaking case product inventory into separate product inventory in advance. When the business operator designates 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 payout information input screen via the output device 7. FIG. When the business operator inputs product payout information via this payout information input screen, the acquisition unit 21 acquires the input product payout information as input data. The data generator 23 generates payout data illustrated in FIG. 20(a) based on the acquired input data (step S42). The storage control unit 22 stores the generated payout data in the storage unit 2 . The example of payout data illustrated in FIG. 20(a) indicates that one case of the product with the product code "A001" has been paid out.

In step S43, the data generation unit 23 determines whether or not the case-variable classification of the payout data is "case". In the case of the payout data exemplified in FIG. 20(a), the case loose classification is "Case" (step S43: Yes). Therefore, in step S44, the data generation unit 23 sets the loose case classification to "separate" as illustrated in FIG. , and the number of goods received when the case goods are disassembled into bulk goods is generated as the acceptance data.

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

Next, in step S45, the data generation unit 23 generates commodity change input data corresponding to the payout data and the acceptance data. FIG. 21 shows an example of product change input data. As shown in FIG. 21, the data generation unit 23 generates product change input data corresponding to a "case" with a transaction classification of "product change", 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 corresponding to the transaction classification of "product change", the product code of "A001-01", and the product name of "syringe", corresponding to "separate". . Then, the data generation unit 23 inputs the number of incoming/outgoing items in the product change input data of "case" as "-1", and the number of incoming/outgoing items in one case of the product master 11 shown in FIG. 20 pieces in a case), and the number of pieces stored in one case, for example, "20 pieces", is input as the number of incoming/outgoing goods change input data for "pieces". The storage control unit 22 stores the product change input data in the storage unit 2 . As a result, it is possible to perform inventory management by disassembling case product inventory into separate product inventory in advance.

(Effect of Embodiment)
As is clear from the above description, the information processing apparatus 1 of the embodiment can obtain the following effects.

1. A person in charge of master creation, a business operator, or the like can perform master management without being conscious of separately creating masters for case products and bulk products.

2. The judgment of the person in charge of the operation is only a judgment as to whether the current shipping business is case or bulk, and it is possible to eliminate the necessity of judging the product code of the case product and the bulk product.

3. It is possible to eliminate the need for an accountant or the like to transfer expenses for slips recorded as purchases for the purpose of sales promotion.

[Contribution to the Sustainable Development Goals (SDGs) led by the United Nations]
Since this embodiment can contribute to improving operational efficiency and promoting appropriate management decisions of companies, it is possible to contribute to Goals 8 and 9 of the SDGs.

In addition, the present embodiment can contribute to the reduction of disposal loss and the promotion of paperless and computerization.

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

[Other embodiments]
The present invention may be implemented in various different embodiments other than the embodiments described above within the scope of the technical idea described in the claims.

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all of the processes described as being manually performed Alternatively, some can be done automatically by known methods.

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

Further, with respect to the information processing apparatus 1, each component shown in the drawing is functionally conceptual, and does not necessarily need to be physically configured as shown in the drawing.

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 interpreted in whole or in part by a CPU (Central Processing Unit) and the CPU. It may be implemented by a program to be executed, or may be implemented as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing apparatus to execute the processing described in this embodiment, and the information processing apparatus as necessary. 1 is mechanically read. That is, a storage unit such as a ROM or HDD stores a computer program for giving commands to the CPU in cooperation with the OS to perform various processes. This computer program is executed by being loaded into the RAM, and constitutes the control section 3 in cooperation with the CPU.

Further, the information processing program of this information processing device 1 may be stored in another server device connected to the information processing device 1 via an arbitrary network, and all or part of it may be stored as necessary. can also be downloaded.

Further, the information processing program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" means memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical Disk), DVD (Digital Versatile Disk), Blu-ray (registered trademark) Disc, etc. shall include any "portable physical medium".

A "program" is a data processing method written in any language or writing method, regardless of the format such as source code or binary code. In addition, the "program" is not necessarily limited to a single structure, but is distributed as a plurality of modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. including things. Known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in the information processing apparatus 1 shown in the embodiment, the installation procedure after reading, and the like.

The storage unit 2 is storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and stores various programs, tables, databases, and the like used for various processes and website provision. , to store files for web pages, etc.

The information processing apparatus 1 may be configured by a known information processing apparatus such as a personal computer or a work station, or may be configured by an information processing apparatus to which arbitrary peripheral devices are connected. Also, the information processing apparatus may be implemented by installing software (including programs, data, etc.) that implements the processing described in the present embodiment.

Furthermore, the specific form of distribution and integration of the device is not limited to the one shown in the figure, and all or part of it can be functionally or physically implemented in any unit according to various additions or functional additions. It can be distributed and integrated. In other words, the embodiments described above may be arbitrarily combined and implemented, or the embodiments may be implemented selectively.

INDUSTRIAL APPLICABILITY The present invention is useful for inventory management of bulk products and case products provided as sample products.

1 information processing device 2 storage 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 item classification master 14 general-purpose master 15 transaction classification master 16 transaction classification association master 17 specification Destination master 18 Customer master 21 Acquisition unit 22 Storage control unit 23 Data generation unit 24 Display control unit

Claims (9)

Either single product classification information indicating that the handling unit is a single product, or case product classification information indicating that the handling unit is a case product in which multiple products are grouped together. , and an acquisition unit that acquires the product code of the product;
a storage control unit that associates the classification information and the product code acquired by the acquisition unit and stores them in a database;
When the case product classification information is acquired as the category information by the acquisition unit, the storage control unit stores the case product classification information and the product code in the database in association with each other, and the handling unit is a single item. generating a single-item product code to be added to the product, and storing it in the database in association with at least the single-item classification information;
An information processing device characterized by: The storage control unit associates the generated single-item product code with the single-item item classification information, and stores it in association with the case product classification information stored in the database;
The information processing apparatus according to claim 1, characterized by: further comprising a data generation unit that generates predetermined data including the input product code and the classification information,
The storage control unit stores the predetermined data generated by the data generation unit in the storage unit, and when the classification information is the single item classification information, the storage control unit stores the data associated with the single item classification information from the database. extracting a product code for a single item, and rewriting the product code of the predetermined data to the product code for a single item extracted from the database;
3. The information processing apparatus according to claim 1 or 2, characterized by: The data generation unit indicates, as the predetermined data, whether the product is at least a purchased product or a product purchased as a sample product, along with the product code and the classification information. Generating data containing transaction class information;
4. The information processing apparatus according to claim 3, characterized by: The storage control unit associates the asset classification information and the debt item classification information with the classification information and the product code and stores them in the database;
When the data generation unit generates purchase input data including, as the predetermined data, transaction classification information indicating that the product was purchased as the sample product, the debt item stored in the database Adding journal data generated based on the debt item classification indicated by the classification information and the asset classification indicated by the asset classification information;
5. The information processing apparatus according to claim 4, characterized by: When the data generation unit generates sales input data including transaction classification information indicating that the product is purchased as the sample product as the predetermined data, the data generation unit adds journal data of "no journal entry". ,
6. The information processing apparatus according to claim 4 or 5, characterized by: When the case product is selected as the product of the payout data, the data generation unit generates the single product classification information, the single product product code, and the number of goods received, which is the number of the single products separated from the case product. generating associated product change input data;
7. The information processing apparatus according to any one of claims 3 to 6, characterized by: The acquisition unit obtains either single product classification information indicating that the handling unit is a single product, or case product classification information indicating that the handling unit is a case product in which multiple products are grouped together. an acquisition step of acquiring the classification information and the product code of the product;
a storage control step in which a storage control unit associates the classification information and the product code acquired by the acquisition unit and stores them in a database;
When the case product classification information is acquired as the category information in the acquisition step, the storage control step stores the case product classification information and the product code in association with each other in the database, and the handling unit is a single product. generating a single-item product code to be added to the product, and storing it in the database in association with at least the single-item classification information;
An information processing method characterized by: the computer,
Either single product classification information indicating that the handling unit is a single product, or case product classification information indicating that the handling unit is a case product in which multiple products are grouped together. , and an acquisition unit that acquires the product code of the product;
Functioning as a storage control unit that associates the classification information and the product code acquired by the acquisition unit and stores them in a database;
When the case product classification information is acquired as the category information by the acquisition unit, the storage control unit stores the case product classification information and the product code in the database in association with each other, and the handling unit is a single item. generating a single-item product code to be added to the product, and storing it in the database in association with at least the single-item classification information;
An information processing program characterized by

Images