JP2024049154A - Automatic judgment device, automatic judgment method, and automatic judgment program - Google Patents

Abstract

The present invention provides an automatic judgment device, an automatic judgment method, and an automatic judgment program that can make appropriate judgments about commercial flow. The automatic judgment device of this embodiment refers to a business company cooperation judgment master and judges whether or not non-window company data can be created for each order number in order placement and receipt data. [Selected Figure] Figure 1

Description

The present invention relates to an automatic judgment device, an automatic judgment method, and an automatic judgment program.

Patent Document 1 discloses a deposit-linked loan transaction system that uses loan application data and cash flow data to perform a predetermined calculation for a deposit-linked loan in which interest is not charged on the amount of the borrowing amount that corresponds to the deposit balance.

JP 2002-183290 A

Incidentally, in a group of companies that has multiple business companies and sales companies, a company that acts as an order window (hereafter referred to as the "window company") is set up within the group, and notable voucher registration is carried out at this window company.

However, because the order processing company determines the flow of trade and records the invoices on a case-by-case basis, there are problems with the content of decisions differing or even incorrect decisions being made because the process relies on human experience and judgment.

The present invention has been made in consideration of the above, and aims to provide an automatic judgment device, an automatic judgment method, and an automatic judgment program that can make appropriate judgments about commercial flow.

In order to solve the above-mentioned problems and achieve the objective, the automatic judgment device of the present invention is an automatic judgment device equipped with a control unit, and is capable of accessing window company order data in which at least a delivery destination code, a supplier code, an order unit price, an order unit price, and an order number are associated with each customer code, and a business company collaboration judgment master in which at least a delivery destination code, a supplier code, and a company number indicating a window company or a non-window company are associated with each customer code, and the control unit is characterized by having a judgment unit that references the business company collaboration judgment master and judges whether non-window company data can be created for each order number in the order data.

The automatic judgment method according to the present invention is an automatic judgment method executed by an automatic judgment device having a control unit, and is capable of accessing purchase and delivery data in which at least a delivery destination code, a supplier code, an order unit price, an order unit price, and an order number are associated with each customer code, and a business company collaboration judgment master in which at least a delivery destination code, a supplier code, and a company number indicating a window company or a non-window company are associated with each customer code, and is characterized in that it includes a judgment step executed by the control unit, which refers to the business company collaboration judgment master and determines whether non-window company data can be created for each order number in the purchase and delivery data.

The automatic judgment program according to the present invention is an automatic judgment program to be executed by an automatic judgment device having a control unit, and is capable of accessing order data in which at least a delivery destination code, a supplier code, an order unit price, an order unit price, and an order number are associated with each customer code, and a business company cooperation judgment master in which at least a delivery destination code, a supplier code, and a company number indicating a window company or a non-window company are associated with each customer code, and is characterized in that it includes a judgment step for having the control unit execute the program by referring to the business company cooperation judgment master and determining whether non-window company data can be created for each order number in the order data.

The present invention has the effect of making it possible to make appropriate judgments about the flow of trade.

FIG. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of an automatic determination device according to an embodiment. FIG. 2 is a diagram showing an example of a customer product unit price master table in the customer product unit price master of the automatic judgment device according to the embodiment. FIG. 3 is a diagram showing an example of a supplier product unit price master table in the supplier product unit price master of the automatic judgment device according to the embodiment. FIG. 4 is a diagram showing an example of a customer product sales price master table in the customer product sales price master of the automatic judgment device according to the embodiment. FIG. 5 is a diagram showing an example of a supplier product unit price master table in the supplier product unit price master of the automatic judgment device according to the embodiment. FIG. 6 is a diagram illustrating an example of a business company price control judgment master table in the business company cooperation judgment master of the automatic judgment device according to the embodiment. FIG. 7 is a schematic diagram for explaining an overview of automatic data linkage by processing executed by the automatic determination device of the embodiment. FIG. 8 is a flowchart showing an outline of processing executed by the automatic determination device according to the embodiment. FIG. 9 is a diagram illustrating an outline of an accounting process for placing and receiving orders by the accounting unit of the automatic judgment device according to the embodiment. FIG. 10 is a diagram showing an outline of the accounting process for sales and purchases performed by the accounting unit of the automatic judgment device according to the embodiment. FIG. 11 is a diagram illustrating an outline of a business company collaboration determination process in which the determination unit of the automatic determination device according to the embodiment determines the commercial flow of order placement and receipt data. FIG. 12 is a diagram illustrating an outline of a business company collaboration determination process in which the determination unit of the automatic determination device according to the embodiment determines the commercial flow of purchase/sale data. FIG. 13 is a diagram showing an example of order placement and receipt data of a non-window company created by the non-window company data creation unit of the automatic decision-making device according to the embodiment. FIG. 14 is a diagram showing another example of the order placement and receipt data of the non-window company created by the non-window company data creation unit of the automatic judgment device according to the embodiment. FIG. 15 is a diagram showing an example of purchase and sale data of a non-window company created by the non-window company data creation unit of the automatic judgment device according to the embodiment. FIG. 16 is a diagram showing another example of the purchase and sale data of the non-window company created by the non-window company data creation unit of the automatic judgment device according to the embodiment. FIG. 17 is a diagram showing an example of a journal data table in the journal data of the liaison company created by the journal data creation unit of the automatic judgment device according to the embodiment. FIG. 18 is a diagram showing an example of a journal data table in the journal data of the non-window company "1" created by the journal data creation unit of the automatic judgment device according to the embodiment. FIG. 19 is a diagram showing an example of a journal data table in the journal data of the non-window company "2" created by the journal data creation unit of the automatic judgment device according to the embodiment.

Below, an embodiment of an automatic judgment device, an automatic judgment method, and an automatic judgment program according to the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to the embodiment.

[1. Configuration]
An example of the configuration of an automatic determination device according to the present embodiment will be described with reference to Fig. 1 etc. Fig. 1 is a schematic diagram showing an overview in a block diagram of an example of the configuration of an automatic determination device.

The automatic judgment device 100 shown in FIG. 1 is a commercially available desktop personal computer. Note that the automatic judgment device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The automatic judgment device 100 includes a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the automatic judgment device 100 is connected to be able to communicate with each other via any communication path.

The communication interface unit 104 communicatively connects the automatic decision-making device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the automatic decision-making device 100 and the server 200 so that they can communicate with each other, and is, for example, the Internet or a LAN (Local Area Network). The data stored in the memory unit 106 may be stored in the server 200, for example.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. The output device 114 may be a monitor (including a home television), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that works with a mouse to provide a pointing device function. In the following, the output device 114 may be referred to as the monitor 114, and the input device 112 may be referred to as the keyboard 112 or the mouse 112.

The memory unit 106 stores various databases, tables, files, and the like. The memory unit 106 records computer programs that work with the OS (Operating System) to give commands to the CPU (Central Processing Unit) to perform various processes. For example, memory devices such as RAM (Random Access Memory) and ROM (Read Only Memory), fixed disk devices such as hard disks, flexible disks, and optical disks can be used as the memory unit 106. The memory unit 106 stores a customer product unit price master 106a, a supplier product unit price master 106b, a customer product sales unit price master 106c, a supplier product purchase unit price master 106d, and a business company collaboration judgment master 106e.

The customer product unit price master 106a stores product codes and unit prices in association with each customer code.

Figure 2 is a diagram showing an example of a customer product unit price master table in the customer product unit price master 106a. In the first row of the customer product unit price master table T1 shown in Figure 2, the customer code "TOK0001" is stored in association with the product code "SHO0001" and the unit price "100".

The supplier product unit price master 106b stores product codes and unit prices in association with each customer code.

Figure 3 is a diagram showing an example of a supplier product unit price master table in the supplier product unit price master 106b. In the first row of the supplier product unit price master table T2 shown in Figure 3, the purchase code "SII0001" is stored in association with the product code "SHO0001" and the unit price "100".

The customer product sales price master 106c stores product codes and sales prices in association with each customer code.

Figure 4 is a diagram showing an example of a customer product unit sales price master table in the customer product unit sales price master 106c. In the first row of the customer product unit sales price master table T3 shown in Figure 4, the customer code "TOK0001" is stored in association with the product code "SHO0001" and the sales price "100".

The supplier product unit price master 106d stores product codes and unit prices in association with each customer code.

Figure 5 is a diagram showing an example of a supplier product unit price master table in the supplier product unit price master 106d. The first row of the supplier product unit price master table T4 shown in Figure 5 stores the customer code "SII0001" in association with the product code "SHO001" and the unit price "100".

The business company collaboration judgment master 106e stores at least the delivery destination code, supplier code, and company number indicating the contact company or non-contact company in association with each customer code.

Figure 6 is a diagram showing an example of the business company price control committee judgment master table in the business company cooperation judgment master 106e. In the first row of the business company cooperation judgment master table T5 shown in Figure 6, the customer code "TOK0001" is stored in correspondence with the delivery destination code "NOU0001", the supplier code "SII0001", the company number "100", the business company customer code "ZTOK0001", the business company delivery destination code "ZNOU0001" and the business company supplier code "ZSII0001". For example, the business company cooperation judgment master 106e uses the customer code, delivery destination code and supplier code as keys to convert each code on the business company side to determine which company needs cooperation. Specifically, the company numbers are "100" for non-window company "1", "200" for non-window company "2" and "300" for non-window company "3". In other words, the company number is a number that indicates which company within a group is the window company and which is not, and is used to determine which company's area to link to.

Returning to FIG. 1, the description of the configuration of the automatic decision-making device 100 will continue.
The control unit 102 is a CPU or the like that comprehensively controls the automatic judgment device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing based on these stored programs. The control unit 102 includes an accounting unit 102a, a judgment unit 102b, a non-window company data creation unit 102c, a journal data creation unit 102d, and an output control unit 102e.

The accounting unit 102a imports the input data from the order entry entered by the user via the input device 112 and the EDI data (order data) linked to the EDI system.

The judgment unit 102b executes a business company collaboration judgment process that judges the trade flow of each of the order placement and receipt data and the purchase and sale data by referring to the business company collaboration judgment master 106e. Specifically, the judgment unit 102b judges whether or not it is possible to create non-window company data for each order number of the order placement and receipt data by referring to the business company collaboration judgment master 106e. Furthermore, the judgment unit 102b judges whether or not it is possible to create non-window company data for each order number of the purchase and sale data by referring to the business company collaboration judgment master 106e.

The non-window company data creation unit 102c executes a non-window company data creation process that creates order and purchase data and sales and purchase data for non-window companies that have been determined to be non-window companies through the business company collaboration determination process by the determination unit 102b.

The journal data creation unit 102d executes a journal data creation process that creates journal data for each of the contact companies and non-contact companies.

The output control unit 102e displays the journal data created by the journal data creation unit 102d by outputting it to the monitor 114.

[2. Overview of automatic data linkage through processing performed by the automatic decision-making device]
Next, an overview of the automatic data linkage performed by the automatic determination device 100 will be described. FIG.

As shown in FIG. 7, first, the automatic judgment device 100 executes an accounting process (step S1). Specifically, the automatic judgment device 100 executes an accounting process to account for order data by importing order input data by the user via the input device 112 and EDI data linked with EDI (order data). Furthermore, the automatic judgment device 100 executes an accounting process to account for purchase and sale data by importing sales input data by the user via the input device 112 and EDI data linked with EDI (sales data).

Next, the automatic judgment device 100 executes a business company collaboration judgment process that refers to the business company collaboration judgment master 106e and judges the trade flow of each of the order/order data and the purchase/sale data (step S2).

Then, the automatic judgment device 100 executes a non-window company data creation process to create order and purchase data and sales and purchase data for non-window companies that have been determined to be non-window companies by the business company collaboration judgment process (step S3).

Then, the automatic judgment device 100 executes a journal data creation process to create journal data for each of the contact company and the non-contact company (step S4).

[3. Details of the process performed by the automatic decision-making device]
Next, an outline of the processing executed by the automatic determination device 100 will be described.

As shown in FIG. 8, the accounting unit 102a executes an accounting process to account for each of the order/order data and the purchase/sale data (step S101).

First, we will explain the accounting process for order data executed by the accounting unit 102a. Figure 9 is a diagram that shows a schematic overview of the accounting process for order data executed by the accounting unit 102a.

As shown in FIG. 9, the accounting unit 102a imports data from order entry input by the user via the input device 112 and EDI-linked EDI data (order data). As shown in the order data table T100 in FIG. 9, the accounting unit 102a creates multiple order data at the contact company.

In the case shown in FIG. 9, the accounting unit 102a references the customer code in the customer product unit price master table T1 and the customer code in the supplier product unit price master table T2, and sets the unit price of the order price and the unit price of the received order. Here, the customer represents the customer's corporation, the delivery destination represents the customer's business establishment, and the supplier represents the supplier's corporation.

For example, customer "TOK001" represents Company A. In this case, when the customer is "TOK001" and the delivery destination is "NOU0001", it represents Company A's Tokyo office, and when the delivery destination is "NOU002", it represents Company A's Osaka office. Also, supplier "SII001" represents Company A.

Next, we will explain the accounting process for sales and purchases data executed by the accounting unit 102a. Figure 10 is a diagram that shows a schematic overview of the accounting process for sales and purchases executed by the accounting unit 102a.

As shown in FIG. 10, the accounting unit 102a imports data from sales input entered by the user via the input device 112 and EDI-linked EDI data (sales data). In this case, the accounting unit 102a creates multiple sales and purchase data at the intermediary company, similar to the order placement and receipt in FIG. 9. Furthermore, the accounting unit 102a references the customer code in the customer product sales unit price master table T3 and the customer code in the supplier product purchase unit price master table T4, and sets the sales unit price and purchase unit price.

Returning to FIG. 8, the description of step S102 and subsequent steps will be continued.
In step S102, the judgment unit 102b refers to the business company cooperation judgment master 106e and executes a business company cooperation judgment process for judging the trade flow of each of the order placement and receipt data and the purchase and sale data.

First, the business company collaboration judgment process in which the judgment unit 102b judges the commercial flow of order data will be described. FIG. 11 is a diagram showing a schematic overview of the business company collaboration judgment process in which the judgment unit 102b judges the commercial flow of order data.

As shown in FIG. 11, the judgment unit 102b refers to the business company collaboration judgment master table T5 of the business company collaboration judgment master 106e, and determines whether or not non-window company data can be created by determining whether or not the company number, business company customer code, business company delivery destination code, and business company supplier code can be obtained using the customer code, delivery destination code, and supplier code in the order data created by the accounting unit 102a in step S1 as keys.

For example, in the case of customer code "TOK001", delivery code "NOU001" and supplier code "SII001" in the first row of order data table T100, the judgment unit 102b judges that non-window company data can be created because the company number "100", business company customer code "ZTOK001", business company delivery code "ZUOU0001" and business company supplier code "ZSII001" can be obtained from business company collaboration judgment master table T5.

Similarly, in the case of the customer code "TOK002", delivery code "NOU002", and supplier code "SII002" in the second row of the order data table T100, the judgment unit 102b determines that non-window company data can be created because the company number "200", business company customer code "ZTOK002", business company delivery code "ZUOU0002", and business company supplier code "ZSII002" can be obtained from the business company collaboration judgment master table T5.

On the other hand, in the case of the customer code "TOK003", delivery code "NOU002", and supplier code "SII002" in the third row of the order data table T100, the judgment unit 102b determines that it is not possible to create non-window company data because it is unable to obtain the company number, business company customer code, business company delivery code, and business company supplier code, and ends the process by only creating the window company data.

Next, the business company collaboration judgment process in which the judgment unit 102b judges the commercial flow of the purchase and sale data will be described. FIG. 12 is a diagram showing a schematic overview of the business company collaboration judgment process in which the judgment unit 102b judges the commercial flow of the purchase and sale data.

As shown in FIG. 12, the judgment unit 102b, like the purchase and sale data, refers to the business company collaboration judgment master table T5 of the business company collaboration judgment master 106e, and determines whether non-window company data can be created by determining whether the company number, business company customer code, business company delivery destination code, and business company supplier code can be obtained using the customer code, delivery destination code, and supplier code in the purchase and sale data created by the accounting unit 102a in step S1 as keys.

Returning to FIG. 8, the description of step S103 and subsequent steps will be continued.
In step S103, the non-window company data creation unit 102c executes a non-window company data creation process to create order/sale data and purchase/sale data based on the business company customer code, business company delivery destination code, and business company supplier code for which the judgment unit 102b has determined that non-window company data can be created.

First, we will explain how to create non-window company data based on order data. First, we will explain the case of non-window company "1" with company number "100" in the order data. Figure 13 is a diagram showing an example of non-window company order data created by the non-window company data creation unit 102c.

As shown in FIG. 13, first, the non-window company data creation unit 102c acquires the business company customer code "ZTOK001," the business company delivery destination code "ZUOU0001," and the business company supplier code "ZSII001," for which the judgment unit 102b has judged that non-window company data can be created, from the business company collaboration judgment master 106e.

Next, the non-window company data creation unit 102c sets the acquired business company customer code "ZTOK001", business company delivery code "ZUOU0001", and business company supplier code "ZSII001" to the customer code, delivery code, and supplier code in the order/receive data table T101, respectively.

Then, the non-window company data creation unit 102c sets the unit price "150" corresponding to the customer code "ZTOK0001" in the customer product unit price master table T11 stored in the customer product unit price master 106a as the order unit price in the order data table T101. In this case, the non-window company data creation unit 102c sets the sales price "100" of the window company, which is the parent company, as the order unit price in the order data table T101.

Next, the non-window company data creation unit 102c creates the window company voucher number in the order/receive data table T101 by storing the voucher "UR00001" with the window company, which is the parent company.

Then, the non-contact company data creation unit 102c creates the other items in the order/placement data table T101 by setting the contact company items as is, or by setting them to fixed values.

Next, we will explain the case of non-window company "2" with company number "200" in the order placement and placement data. Figure 14 is a diagram showing another example of non-window company order placement and placement data created by the non-window company data creation unit 102c.

As shown in FIG. 14, first, the non-window company data creation unit 102c obtains the business company customer code "ZTOK002," the business company delivery destination code "ZUOU0002," and the business company supplier code "ZSII002," for which the judgment unit 102b has judged that non-window company data can be created, from the business company collaboration judgment master 106e.

Then, the non-window company data creation unit 102c sets the acquired business company customer code "ZTOK002", business company delivery code "ZUOU0002", and business company supplier code "ZSII002" to the customer code, delivery code, and supplier code in the order/receive data table T102, respectively.

Then, the non-window company data creation unit 102c sets the unit price "200" corresponding to the customer code "ZTOK0002" in the customer product unit price master table T12 stored in the customer product unit price master 106a as the order unit price in the order data table T102. In this case, the non-window company data creation unit 102c sets the sales price "150" of the window company, which is the parent company, as the order unit price in the order data table T102.

Then, the non-window company data creation unit 102c creates the window company voucher number in the order/receive data table T102 by storing the voucher "UR00002" with the window company, which is the parent company.

Then, the non-contact company data creation unit 102c creates the other items in the order/placement data table T101 by setting the contact company items as is, or by setting them to fixed values.

Finally, we will explain the case of non-window company "3" with company number "300" in the order placement and receipt data. In this case, the non-window company data creation unit 102c does not create order placement and receipt data for the non-window company because the judgment unit 102b judges that the non-window company data creation unit 102c cannot create non-window company data.

Next, we will explain how to create non-window company data based on purchase and sale data. First, we will explain the case of non-window company "1" with company number "100" in the order data. Figure 15 is a diagram showing an example of non-window company purchase and sale data created by the non-window company data creation unit 102c.

As shown in FIG. 15, first, the non-window company data creation unit 102c obtains the business company customer code "ZTOK001," the business company delivery destination code "ZUOU0001," and the business company supplier code "ZSII001" for which the judgment unit 102b has judged that non-window company data can be created from the business company collaboration judgment master 106e.

Next, the non-window company data creation unit 102c sets the acquired business company customer code "ZTOK001", business company delivery code "ZUOU0001", and business company supplier code "ZSII001" to the customer code, delivery code, and supplier code, respectively, of the purchase/sale data table T201.

Then, the non-window company data creation unit 102c sets the unit price "150" corresponding to the customer code "ZTOK0001" in the customer product unit price master table T31 stored in the customer product unit price master 106a as the sales unit price in the purchase/sale data table T201. In this case, the non-window company data creation unit 102c sets the sales unit price "100" of the window company, which is the parent company, as the purchase unit price in the purchase/sale data table T201.

Next, the non-window company data creation unit 102c creates the window company voucher number in the purchase/sale data table T201 by storing the voucher "UR00001" with the window company, which is the parent company.

Then, the non-window company data creation unit 102c creates the other items in the purchase and sale data table T201 by setting the window company items as is, or by setting them to fixed values.

Next, we will explain the case of non-window company "2" with company number "200" in the sales and purchase data. Figure 16 is a diagram showing another example of non-window company sales and purchase data created by the non-window company data creation unit 102c.

As shown in FIG. 16, first, the non-window company data creation unit 102c obtains the business company customer code "ZTOK002," the business company delivery destination code "ZUOU0002," and the business company supplier code "ZSII002," for which the judgment unit 102b has judged that non-window company data can be created, from the business company collaboration judgment master 106e.

Next, the non-window company data creation unit 102c sets the acquired business company customer code "ZTOK002", business company delivery code "ZUOU0002", and business company supplier code "ZSII002" to the customer code, delivery code, and supplier code, respectively, of the purchase/sale data table T202.

Then, the non-window company data creation unit 102c sets the unit price "200" corresponding to the customer code "ZTOK0002" in the customer product unit price master table T32 stored in the customer product unit price master 106a as the sales unit price in the purchase/sales data table T202. In this case, the non-window company data creation unit 102c sets the sales unit price "150" of the window company, which is the parent company, as the purchase unit price in the purchase/sales data table T202.

Next, the non-window company data creation unit 102c creates the window company voucher number in the purchase/sale data table T202 by storing the voucher "UR00002" with the window company, which is the parent company.

Then, the non-window company data creation unit 102c creates the other items in the purchase and sale data table T201 by setting the window company items as is, or by setting them to fixed values.

Finally, we will explain the case of non-window company "3" with company number "300" in the order placement and receipt data. In this case, the non-window company data creation unit 102c does not create order placement and receipt data for the non-window company because the judgment unit 102b judges that the non-window company data creation unit 102c cannot create non-window company data.

Returning to FIG. 8, the description of step S104 and subsequent steps will be continued.
In step S104, the journal data creation unit 102d executes a journal data creation process to create journal data based on the non-window company data generated by the non-window company data creation unit 102c, the order data, and the purchase and sale data.

Figure 17 is a diagram showing an example of a journal data table in the journal data of a window company created by the journal data creation unit 102d. Figure 18 is a diagram showing an example of a journal data table in the journal data of a non-window company "1" created by the journal data creation unit 102d. Figure 19 is a diagram showing an example of a journal data table in the journal data of a non-window company "2" created by the journal data creation unit 102d.

As shown in FIG. 17, the journal data creation unit 102d generates a journal data table T300 for the journal data of the window company based on the non-window company data generated by the non-window company data creation unit 102c, the order data, and the purchase and sale data.

The first row of the journal data table T300 corresponds to the journal number "SW0001," the journal line number "1," the client code "TOk0001," the client name "Customer (non-window company "1")," the debit side "Accounts receivable," the debit amount "100,000," the credit side item "Sales," the credit amount "100,000," and the source document number "UR00001."

As shown in Figures 18 and 19, the journal data creation unit 102d generates journal data table T301 and journal data table T302 for the journal data of non-window company "1" and non-window company "2" based on the non-window company data generated by the non-window company data creation unit 102c, the order data, and the purchase and sale data. In each of these journal data tables T301 and T302, the source voucher number "UR00004" and the source voucher number "UR00005" are associated with each other, as in the journal data table T300 for the account company's journal data. This links the voucher numbers of the window company and the non-window company, allowing the user to later check which voucher generated the non-window company voucher.

Returning to FIG. 8, the description of step S105 and subsequent steps will be continued.
The output control unit 102e executes an output process to output the journal data created by the journal data creation unit 102d to the monitor 114. Of course, the output control unit 102e may output the journal data as a delivery note, an invoice, and a purchase order using a printer or the like. After step S105, the automatic judgment device 100 ends this process.

According to the embodiment described above, the judgment unit 102b refers to the business company collaboration judgment master 106e and executes a business company collaboration judgment process to judge the commercial flow of each of the order/order data and the purchase/sale data, so that an appropriate commercial flow judgment can be made.

In addition, according to the embodiment, the non-window company data creation unit 102c executes a non-window company data creation process that creates order and purchase data and sales and purchase data based on the business company customer code, business company delivery destination code, and business company supplier code for which the judgment unit 102b has determined that non-window company data can be created, so that order and purchase data and sales and purchase data for the non-window company can be created. This allows the user to efficiently perform subsequent shipping and receiving, sales, and purchasing tasks.

In addition, according to the embodiment, the journal data creation unit 102d executes a journal data creation process to create journal data based on the non-window company data generated by the non-window company data creation unit 102c, the order data, and the purchase and sale data, and the voucher numbers of the window company and the non-window company are linked and set. This allows the user to easily check later which voucher generated the non-window company voucher.

Furthermore, according to the embodiment, the output control unit 102e executes an output process in which the journal data created by the journal data creation unit 102d is output to the monitor 114. This allows the user to intuitively understand the journal data.

[4. Contribution to the United Nations-led Sustainable Development Goals (SDGs)]
This embodiment can contribute to improving business efficiency and promoting appropriate management decisions by companies, thereby 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.

5. 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 parameters such as search conditions, screen examples, and database configurations shown in this specification and drawings may be changed as desired unless otherwise specified.

Furthermore, with regard to the automatic judgment device 100, 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 automatic judgment device 100, particularly the processing functions performed by the control unit, may be realized in whole or in part by a CPU 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 automatic judgment device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) to give instructions to the CPU in cooperation with the OS and perform various processes. This computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the automatic decision-making device 100 via any network, and all or part of it may be downloaded as needed.

In addition, the program for executing the processing described in this embodiment may be stored in a non-transitory computer-readable recording medium, and may also be configured as a program product. Here, the term "recording medium" refers to a memory card, a USB (Universal Serial Bus) memory, a SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), an EEPROM (registered trademark) (Electrically Erasable and Programmable Read Only Memory), a CD-ROM (Compact Disk Read Only Memory), an MO (Magneto-Optical disk), a DVD (Digital Versatile This includes any "portable physical media" such as a Blu-ray (registered trademark) Disc, 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 configuration, but also includes a distributed configuration consisting of multiple modules or libraries, and a program that works in conjunction with a separate program, such as an OS, to achieve its function. Note that the specific configuration and reading procedure for reading a recording medium in each device shown in the embodiments, as well as the installation procedure after reading, can use well-known configurations and procedures.

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

The automatic judgment device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. The automatic judgment device 100 may also be realized by implementing software (including programs or data, etc.) that causes the device to realize 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 functional loads. 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 in data creation operations for group companies that have multiple business companies and a parent company that is a sales company.

100 Automatic judgment device 102 Control unit 102a Accounting unit 102b Judgment unit 102c Non-window company data creation unit 102d Journal data creation unit 102c Output control unit 104 Communication interface unit 106 Memory unit 106a Customer product unit price master 106b Supplier product unit price master 106c Customer product sales unit price master 106d Supplier product unit purchase price master 106e Business company collaboration judgment master 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (10)

An automatic decision-making device including a control unit,
Order data of the contact company that corresponds at least the delivery destination code, the supplier code, the order unit price, the order unit price, and the order number for each customer code;
A business company cooperation judgment master in which at least a delivery destination code, a supplier code, and a company number indicating a contact company or a non-contact company are associated with each customer code;
is accessible to
The control unit is
a determination unit that refers to the business company cooperation determination master and determines whether or not non-window company data can be created for each order number of the order placement and receipt data;
To have
An automatic decision-making device characterized by: The automatic decision-making device according to claim 1,
Sales and purchase data of the contact company that corresponds at least the delivery destination code, supplier code, sales price, purchase price, and order number for each customer code,
is more accessible to
The determination unit is
By referring to the business company cooperation judgment master, it is judged whether or not non-window company data can be created for each order number of the sales and purchase data;
An automatic decision-making device characterized by: The automatic decision-making device according to claim 2,
The business company collaboration judgment master is
For each customer code, a business company customer code, a business company delivery destination code, and a business company supplier code are further associated.
The control unit is
a non-window company data creation unit which, when it is determined by the determination unit that the non-window company data can be created, references the business company cooperation determination master, acquires a business company customer code, a business company delivery destination code, and a business company supplier code corresponding to the customer code, the delivery destination code, and the supplier code of the order/sale data or the purchase/sale data, and creates non-window company data by setting the business company customer code, the business company delivery destination code, and the business company supplier code to the customer code, the delivery destination code, and the supplier code;
and
An automatic decision-making device characterized by: The automatic decision-making device according to claim 3,
For each customer code, it is possible to further access the customer product unit price master that corresponds to the product code and unit price,
The non-contact company data creation unit
By referring to the customer product-specific unit price master, the order unit price or sales unit price of the non-window company data is set, and the order number of the order data or the sales/purchase data is linked to the slip number of the window company and set.
An automatic decision-making device characterized by: The automatic decision-making device according to claim 4,
For each customer code, it is possible to further access the supplier product unit price master that corresponds to the product code and unit price,
The control unit is
an accounting section which acquires input data and EDI data of order entry, and records and generates the order entry data in which an order unit price and an order unit price are set for each order number based on the order entry data, the order entry EDI data, the customer product unit price master, and the supplier product unit price master;
and
An automatic decision-making device characterized by: The automatic decision-making device according to claim 5,
A customer product sales price master that matches product codes and sales prices for each customer code, and a supplier product purchase price master that matches product codes and purchase prices for each customer code,
is more accessible to
The accounting section includes:
Acquiring input data and EDI data of sales input, and recording and generating the sales and purchase data in which the sales unit price and purchase unit price are set for each order number based on the input data of sales and purchase, the EDI data of sales and purchase, the customer product sales unit price master, and the supplier product purchase unit price master;
An automatic decision-making device characterized by: The automatic decision-making device according to claim 6,
The control unit is
a journal data creation unit that creates journal data for each of the window companies and the non-window companies based on the order data, the purchase and sale data, and the non-window company data;
and
An automatic decision-making device characterized by: The automatic decision-making device according to claim 7,
The control unit is
an output control unit that outputs the journalization data to an outside;
and
An automatic decision-making device characterized by: An automatic judgment method executed by an automatic judgment device having a control unit,
Order data in which at least a delivery destination code, a supplier code, an order unit price, an order unit price, and an order number are associated with each customer code;
A business company cooperation judgment master in which at least a delivery destination code, a supplier code, and a company number indicating a contact company or a non-contact company are associated with each customer code;
is accessible to
Executed by the control unit,
A determination step of determining whether or not non-window company data can be created for each order number of the order placement and receipt data by referring to the business company collaboration determination master;
containing,
The automatic judgment method is characterized by the above. An automatic judgment program to be executed by an automatic judgment device having a control unit,
Order data in which at least a delivery destination code, a supplier code, an order unit price, an order unit price, and an order number are associated with each customer code;
A business company cooperation judgment master in which at least a delivery destination code, a supplier code, and a company number indicating a contact company or a non-contact company are associated with each customer code;
is accessible to
To cause the control unit to execute
A determination step of determining whether or not non-window company data can be created for each order number of the order placement and receipt data by referring to the business company collaboration determination master;
containing,
An automatic decision-making program characterized by:

Images