JP7693565B2 - Order management device, order management method, and order management program - Google Patents

Description

The present invention relates to an order management device, an order management method, and an order management program.

Traditionally, when placing and receiving orders within a company, invoicing and sales would inevitably flow to later processes, and internal transaction processing would often be mixed with external processing, resulting in complicated management, and as a result, operational proposals were often difficult to make. In addition, data on internal transactions was mixed in when it came to grasping income and expenditures, making it difficult to grasp accurate income and expenditures by project. For example, Patent Document 1 is an example of a conventional system for managing internal orders.

JP 2011-242859 A

However, Patent Document 1 does not state anything about how a structure consisting of a parent job generated from contract details and a child job derived from the parent for placing orders with other departments can be used to streamline in-house ordering operations and accurately capture project income and expenditures.

The present invention has been made in consideration of the above, and aims to provide an order management device, an order management method, and an order management program that can streamline in-house ordering operations by using a structure consisting of a parent job generated from contract details and a child job derived from the parent for placing orders with other departments.

In order to solve the above problems and achieve the object, the present invention is an order management device equipped with a control unit, the control unit being characterized by comprising: a contract work processing means for creating contract detail data including a contract detail number, an order receiving department, and an order amount for a target project, and parent job data including a contract detail number, a job number, and a cost department; a budget work processing means for creating child job data for the parent job data including a contract detail number, a job number, a cost department that is an internal supplier, a cost amount, and a source job number that is the parent job number of the parent job data; an order processing means for creating order data including an order number, a contract detail number, a job number, an external supplier, and an order amount for the target project; and a sales processing means for creating sales data including a sales number, a contract detail number, a sales department, and a sales amount based on the contract detail data.

According to one aspect of the present invention, the control unit may further include an income/expense creation means for creating income/expense data by job number, including the order department, order amount, internal order amount, cost department, cost amount, internal cost amount, and gross profit, based on the contract details data, the parent job data, the child job data, the order data, and the sales data.

According to one aspect of the present invention, the income/expense creation means may create income/expense data by contract detail, including the order receiving department, order amount, internal order amount, cost department, cost amount, and gross profit, on a contract detail basis, based on the job-specific income/expense data.

According to one aspect of the present invention, the income/expense creation means may create departmental income/expense data including order-receiving department, order amount, cost amount, and gross profit on a department basis based on the job-specific income/expense data.

In order to solve the above-mentioned problems and achieve the object, the present invention provides an order management method executed by an information processing device equipped with a control unit, characterized in that it includes a contract work processing step executed by the control unit for creating contract detail data including a contract detail number, an order receiving department, and an order amount for a target project, and parent job data including a contract detail number, a job number, and a cost department; a budget work processing step for creating child job data for the parent job data including a contract detail number, a job number, a cost department that is an internal supplier, a cost amount, and a source job number that is the parent job number of the parent job data; an order processing step for creating order data for the target project including an order number, a contract detail number, a job number, an external supplier, and an order amount; and a sales processing step for creating sales data including a sales number, a contract detail number, a sales department, and a sales amount based on the contract detail data.

In order to solve the above-mentioned problems and achieve the object, the present invention is an order management program to be executed by an information processing device having a control unit, and is characterized in that the order management program causes the control unit to execute a contract work processing step of creating, for a target project, contract detail data including a contract detail number, an order receiving department, and an order amount, and parent job data including a contract detail number, a job number, and a cost department; a budget work processing step of creating, for the parent job data, child job data including a contract detail number, a job number, a cost department that is an internal supplier, a cost amount, and a source job number that is the parent job number of the parent job data; an order processing step of creating, for the target project, order data including an order number, a contract detail number, a job number, an external supplier, and an order amount; and a sales processing step of creating sales data including a sales number, a contract detail number, a sales department, and a sales amount based on the contract detail data.

The present invention has the effect of making it possible to streamline in-house ordering operations by using a structure consisting of a parent job generated from contract details and a child job derived from the parent for ordering from other departments.

FIG. 1 is a diagram showing a processing image of an order management device according to the present embodiment. FIG. 2 is a block diagram showing an example of the configuration of the order management device according to the present embodiment. FIG. 3 is a flow chart showing an example of the overall processing of the order management device according to this embodiment. FIG. 4 is a diagram for explaining a specific example of the process of the control unit of the order management device according to this embodiment. FIG. 5 is a diagram for explaining a specific example of the process of the control unit of the order management device according to this embodiment. FIG. 6 is a diagram for explaining a specific example of the process of the control unit of the order management device according to this embodiment. FIG. 7 is a diagram for explaining a specific example of the process of the control unit of the order management device according to this embodiment. FIG. 8 is a diagram for explaining a specific example of the process of the control unit of the order management device according to the present embodiment. FIG. 9 is a diagram for explaining a specific example of the process of the control unit of the order management device according to this embodiment. FIG. 10 is a diagram for explaining a specific example of the process of the control unit of the order management device according to this embodiment. FIG. 11 is a diagram for explaining a specific example of the process of the control unit of the order management device according to this embodiment.

An embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment.

[1. Overview]
In the past, when placing and receiving orders within a company, billing and sales would inevitably flow to later processes, and internal transaction processing and external processing would often be mixed, resulting in complicated management, and as a result, there were many cases where operational proposals were difficult to make.In addition, data on internal transactions was mixed in, making it difficult to grasp accurate income and expenditure by project.

In this embodiment, therefore, by using a structure consisting of a parent job that arises from the contract details and a child job derived from the parent for placing orders with other departments, we have made it possible to streamline in-house ordering and receive work and to accurately grasp the income and expenditures of projects.

More specifically, (1) in the past, in the case of internal orders, other companies often operated by separating contract details. Although there was only one contract with the customer, the amount had to be transferred between departments for internal reasons. This meant that it was necessary to process sales for contracts for internal orders, but this has been made unnecessary in this embodiment.

(2) In this embodiment, by linking a job linked to contract data with a parent job (originating job number) and providing an amount field, it is possible to operate separate jobs for internal ordering. In other words, in this embodiment, jobs can be separated by department, amounts can be managed, and transfer amounts by department can be checked using internal reports, etc.

(3) In this embodiment, it is now possible to easily manage the income and expenditures of one's own department or job.

As a result of (1) to (3), this embodiment is a system that has a data structure that can accurately capture project income and expenditures while improving the efficiency of the registration process for in-house orders and receipts.

According to this embodiment, it is possible to carry out internal order management, which is common in the IT and construction industries, and to reflect this in the working budget and income and expenditures. In addition, since sales processing for internal orders is not required, operations can be carried out without affecting the administrative work that is actually required. Furthermore, the system can centrally manage the many internal transactions.

Figure 1 is a diagram showing a processing image of the order management device of this embodiment. The following describes a case where department A receives an order for 1 million yen, places an internal order with department B at a cost of 300,000 and department C at a cost of 100,000, and places an external order with company P at a cost of 300,000, and department B further places an internal order with department D at a cost of 50,000, and an external order with company Q at a cost of 200,000.

First, in case registration T1, a project is registered. In contract work T2, contract details are registered (for example, Department A receives an order for 1 million yen) and Job registration (1) (Department A's planned cost is 700,000 yen) is performed.

In budget work (parent job) T3, internal order job registration (2) (B department cost "300,000"), internal order job registration (3) (C department cost "100,000"), and order input for regular order (P company cost "300,000") are performed.

In budget work (parent job) T4, for job registration (2), an internal order job registration (4) (cost of D department "50,000") and order input for regular order (cost of Q company "200,000") are performed.

2. Configuration
An example of the configuration of the order management device 100 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the configuration of the order management device 100.

The order management device 100 is a commercially available desktop personal computer. The order management 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 order management 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 order management device 100 is connected to each other so that they can communicate with each other via any communication path.

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

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 achieve 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. Displaying information on the monitor 114 and the user operating the input device 112 may be referred to as "user operation via a UI."

The storage unit 106 stores various databases, tables, files, and the like. The storage 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. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) or a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, an optical disk, and the like can be used. The storage unit 106 includes a data table 106a, and the like.

Data table 106a is a table for storing project data, contract details data, job data, order data, sales data, etc.

Project data may include project number and project name. Contract detail data may include project number, contract detail number, order receiving department, and order amount. Job data may include project number, contract detail number, Job number, cost department, cost amount, and issuing Job number. Order data may include data on order number, line number, project number, contract detail number, Job number, supplier, and order amount. Sales data may include data on sales slip, project number, contract detail number, Job number, sales department, and sales amount.

The control unit 102 is a CPU or the like that controls the order management device 100. The control unit 102 has an internal memory for storing control programs such as an OS, programs that define various processing procedures, required data, etc., and executes various information processing based on these stored programs. In terms of function, the control unit 102 includes a case registration unit 102a, a contract work processing unit 102b, a budget work processing unit 102c, an order processing unit 102d, a sales processing unit 102e, an income/expense creation unit 102f, and a screen display control unit 102g.

The case registration unit 102a, for example, inputs project data and registers it in the data table 106a in response to an operator's operation on a case input screen (not shown) displayed on the monitor 114.

The contract work processing unit 102b creates contract detail data for the target project, including the contract detail number, order receiving department, and order amount, in response to, for example, the operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the data in the data table 106a. The contract work processing unit 102b also creates parent job data for the target project, including the contract detail number, job number, and cost department, in response to, for example, the operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the data in the data table 106a.

For example, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, the budget processing unit 102c creates child job data for parent job data, including a contract detail number, a job number, an internal cost department to which the order is placed, a cost amount, and a job number from which the order is issued, which is used as the job number of the parent job data, and registers the child job data in the data table 106a.

For example, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, the order processing unit 102d creates order data for the target project based on the parent job data and child job data, including the order number, contract detail number, job number, external supplier, and order amount, and registers the data in the data table 106a.

The sales processing unit 102e creates sales data including the sales number, contract detail number, sales department, and sales amount based on the contract detail data in response to, for example, the operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the data in the data table 106a.

The income/expense creation unit 102f creates and outputs income/expense data by job, including the order department, order amount, internal order amount, cost department, cost amount, internal cost amount, and gross profit, by job number, based on the contract detail data, parent job data, child job data, order data, and sales data.

In addition, the income/expense creation unit 102f creates and outputs income/expense data by contract detail, including the order receiving department, order amount, in-house order amount, cost department, cost amount, and gross profit, on a contract detail basis, based on the job-specific income/expense data.

In addition, the income/expense creation unit 102f creates and outputs department-specific income/expense data, including the order-receiving department, order amount, cost amount, and gross profit, on a department-by-department basis, based on the job-specific income/expense data.

The screen display control unit 102g controls the display and input of various screens (e.g., various input screens, etc.) displayed on the monitor 114.

3. Specific Examples
2 to 11, a specific example of the processing performed by the control unit 102 of the order management device 100 in this embodiment will be described.

(3-1. Overall processing)
FIG. 3 is a diagram illustrating an outline of the overall processing of the control unit 102 of the order management device 100 according to this embodiment.

With reference to FIG. 3, an overview of the overall processing of the control unit 102 of the order management device 100 in this embodiment will be described. In FIG. 3, the case registration unit 102a executes a case registration process (step S1). Specifically, in the case registration process, the case registration unit 102a inputs project data and registers it in the data table 106a in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, for example.

The contract work processing unit 102b executes the contract work processing (step S2). Specifically, in the contract work processing, the contract work processing unit 102b creates contract detail data including the contract detail number, order receiving department, and order amount for the target project in response to the operator's operation on an input screen (not shown) displayed on the monitor 114, for example, and registers it in the data table 106a. In addition, in the contract work processing, the contract work processing unit 102b creates parent job data including the contract detail number, job number, and cost department for the target project in response to the operator's operation on an input screen (not shown) displayed on the monitor 114, for example, and registers it in the data table 106a.

The budget work processing unit 102c executes budget work processing (step S3). Specifically, in the budget work processing, the budget work processing unit 102c creates child job data for parent job data, including a contract detail number, a job number, an in-house cost department to which the order is placed, a cost amount, and a job number from which the order is issued, which is set as the job number of the parent job data, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the child job data in the data table 106a.

The order processing unit 102d executes the order processing (step S4). Specifically, in the order processing, the order processing unit 102d creates order data including the order number, contract detail number, job number, external supplier, and order amount for the target project based on the parent job data and child job data in response to the operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the data in the data table 106a.

The sales processing unit 102e executes sales transaction processing (step S5). For example, in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, the sales processing unit 102e creates sales data including a sales number, a contract detail number, a sales department, and a sales amount based on the contract detail data, and registers the data in the data table 106a.

The income/expenses creation unit 102f executes income/expenses management processing (step S6). Specifically, in the income/expenses management processing, the income/expenses creation unit 102f creates income/expenses data by job number, including the order department, order amount, in-house order amount, cost department, cost amount, in-house cost amount, and gross profit, based on the contract details data, parent job data, child job data, order data, and sales data.

In addition, in the income and expenditure management process, the income and expenditure creation unit 102f creates income and expenditure data by contract detail, including the order receiving department, order amount, internal order amount, cost department, cost amount, and gross profit, on a contract detail basis, based on the income and expenditure data by job.

In addition, in the income and expenditure management process, the income and expenditure creation unit 102f creates department-specific income and expenditure data, including the order-receiving department, order amount, cost amount, and gross profit, on a department-by-department basis, based on the job-specific income and expenditure data.

(3-2. Sample data)
4 to 11 are diagrams showing sample data for explaining a specific example of the processing of the control unit 102 of the order management device 100 in this embodiment. A specific example of the processing of the control unit 102 of the order management device 100 in this embodiment will be explained with reference to FIG. 4 to FIG.

(S1: Case registration process)
A specific example of the case registration process will be described with reference to Fig. 4. The case registration unit 102a inputs project data in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, for example, and registers the input data in the data table 106a.

Figure 4 is a diagram showing an example of project data. In project data, the project number is the primary key. In the example of project data shown in Figure 4, the first line has the project number "PJ0001" and the project name "Project XX", the second line has the project number "PJ0002" and the project name "Project △△", and the third line has the project number "PJ0003" and the project name "Project XX".

In the following explanation, for project number "PJ0001," department A receives an order from outside the company for "1 million yen," places internal orders with department B for "300,000 yen" and department C for "100,000 yen," places an external order with company P for "300,000 yen," and then department B places an external order with company Q for "200,000 yen."

(Conventional Processing)
Conventional contract operations, ordering operations, and sales operations will be described with reference to FIGS.

The order receiving department registers contract detail data for orders from Department A as usual, and also registers job data. Figure 5 (A) is a diagram showing an example of contract detail data. In contract detail data, the project number and contract detail number are used as primary keys. In the example of contract detail data shown in Figure 5 (A), the project number is "PJ0001", the contract detail number is "0001", the order receiving department is "Department A", and the order amount is "1,000,000".

Figure 5 (B) is a diagram showing an example of job data. Job data has project number, contract detail number, and job number as primary keys. In the example of job data shown in Figure 5 (B), the project number is "PJ0001", contract detail number is "0001", job number is "0001", and cost department is "Department A".

Contracts are also registered in the department that receives internal orders. In this way, contract registration for internal orders was previously required. Figure 5 (C) shows an example of contract detail data for an internal order recipient. In the example of contract detail data shown in Figure 5 (C), the first line shows project number "PJ0001", contract detail number "0002", order receiving department "Department B", and order amount "300,000", and the second line shows project number "PJ0001", contract detail number "0003", order receiving department "Department C", and order amount "100,000".

Register the job data for this contract. Figure 5 (D) is a diagram showing an example of job data for an internal contractor. In the example of job data shown in Figure 5 (D), the first line has project number "PJ0001", contract detail number "0002", job number "0001", and cost department "B department", and the second line has project number "PJ0001", contract detail number "0003", job number "0001", and cost department "C department". The cost of the work is incurred in this job.

In ordering operations, order data is registered. Figure 6 (A) shows an example of order data. Order data has the order number and row number as primary keys. In the example of order data shown in Figure 6 (A), the first row has order number "H0001", row number "001", project number "J0001", contract detail number "0001", job number "0001", supplier "Company P", and order amount "300,000", and the second row has order number "H0002", row number "001", project number "J0001", contract detail number "0002", job number "0001", supplier "Company Q", and order amount "200,000".

In sales operations, sales data is registered. FIG. 6(B) is a diagram showing an example of sales data. In the example of sales data shown in FIG. 6(B), the first line has sales slip "U0001", project number "PJ0001", contract detail number "0001", sales department "Department A", and sales amount "1,000,000". The second line has sales slip "U0002", project number "PJ0001", contract detail number "0002", sales department "Department B", and sales amount "300,000". The third line has sales slip "U0003", project number "PJ0001", contract detail number "0003", sales department "Department C", and sales amount "100,000".

Previously, sales had to be processed according to the timing of the accounting month (recognition of cost of sales). In other words, two sales entries would be generated, so it was necessary to separate the items and control the accounting so that sales were not recognized.

In addition, previously, in order to see the income and expenditures of a project, it was necessary to look at the two contracts together, and the internal sales invoices (U0002, U0003) had to be excluded.

Conventionally, when placing and receiving orders within a company, data on intra-company transactions would flow to downstream processes such as sales, and would become mixed with external processing, resulting in cumbersome management. Therefore, in this embodiment, the efficiency of intra-company ordering operations is improved by using a structure that consists of a parent job generated from contract detail data and a child job derived from the parent for placing orders from other departments, as shown below.

(S2: Contract processing)
The contract work processing will be described with reference to Fig. 7. The contract work processing unit 102b creates contract detail data including a contract detail number, an order receiving department, and an order amount for a target project in response to an operation by an operator on an input screen (not shown) displayed on the monitor 114, and registers the data in the data table 106a.

The order receiving department registers contract detail data for orders from Department A in the usual way. Figure 7 (A) is a diagram showing an example of contract detail data. In contract detail data, the project number and contract detail number are used as primary keys. In the example of contract detail data shown in Figure 7 (A), the project number is "PJ0001", the contract detail number is "0001", the order receiving department is "Department A", and the order amount is "1,000,000".

The contract work processing unit 102b creates parent job data for the target project, including the contract detail number, job number, and cost department, in response to, for example, the operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the data in the data table 106a.

Figure 7 (B) is a diagram showing an example of parent job data. Parent job data has project number, contract detail number, and job number as primary keys. In the example of parent job data shown in Figure 7 (B), the project number is "PJ0001", contract detail number is "0001", job number is "0001", and cost department is "Department A". 300,000 yen will be outsourced from this parent job.

(S3: Budget processing)
The budget work process will be described with reference to Fig. 8. The budget work process section 102c creates child job data for parent job data, including a contract detail number, a job number, a cost department to which the company is contracted, a cost amount, and a job number of the issuing party which is to be the job number of the parent job data, and registers the child job data in the data table 106a. A budget is registered for the parent job, and an internal order (child job registration) is made.

Figure 8 is a diagram showing an example of child job data for an internal order. Child job data has the project number, contract detail number, and job number as primary keys. In the example of child job data for department B shown in Figure 8, the project number is "PJ0001", the contract detail number is "0001", the job number is "0002", the cost department is "Department B", the cost amount is "300,000", and the issuing job number is "0001". 200,000 is to be outsourced from this job. The cost amount (internal order amount) and the issuing job number (order originator) can be selected. When selecting, it is controlled so that it can be selected from the job group of the contract details of the user's own.

Furthermore, the child job data for Department C is project number "PJ0001", contract detail number "0001", job number "0003", cost department "Department C", cost amount "100,000", and issuing job number "0001". 50,000 will be outsourced from this job.

(S4: Order processing)
The order processing will be described with reference to Fig. 9. The order processing unit 102d creates order data including an order number, a contract detail number, a job number, an external supplier, and an order amount for a target project based on parent job data and child job data, and registers the data in the data table 106a.

Figure 9 shows an example of order data. Order data has the order number and row number as the primary keys. In the example of order data shown in Figure 9, the first row has order number "H0001", row number "001", project number "J0001", contract detail number "0001", job number "0001", supplier "Company P", and order amount "300,000". The second row has order number "H0002", row number "001", project number "J0001", contract detail number "0002", job number "0001", supplier "Company Q", and order amount "200,000".

(S5: Sales processing)
The sales transaction process will be described with reference to Fig. 9. The sales processing section 102e creates sales data including a sales number, a contract detail number, a sales department, and a sales amount based on the contract detail data in response to an operator's operation on an input screen (not shown) displayed on the monitor 114, and registers the data in the data table 106a.

Figure 9 shows an example of sales data, with sales slip "U0001", project number "PJ0001", contract detail number "0001", sales department "Department A", and sales amount "1,000,000". The sales journal entry is Debit: Accounts receivable "1,000,000" / Credit: Sales "1,000,000", and only one sales journal entry is generated. This simplifies the process as there is no need to match the timing of the accounting month for sales processing. The project income and expenditure can be viewed on a single contract.

(S6: Income and expenditure management process)
The income and expenditure management process will be described with reference to Figs. 10 and 11. Fig. 10 is a diagram for explaining conventional income and expenditure management. Fig. 10 shows conventional income and expenditure by job, and the first line shows project number "PJ0001", contract detail number "0001", job number "0001", order receiving department "Department A", order amount "1,000,000", cost department "Department A", cost amount "700,000", gross profit "300,000", and the second line shows project number "PJ0001", contract detail number "0002", job number "0003", order amount "1,000,000", cost department "Department A", cost amount "700,000", gross profit "300,000". The first line is "Project No. "PJ0001", order receiving department "Department B", order amount "300,000", cost department "Department B", cost amount "250,000", gross profit "500,000", and the second line is "Project No. "PJ0001", contract detail No. "0003", Job No. "0001", order receiving department "Department C", order amount "100,000", cost department "Department C", cost amount "0", gross profit "100,000". It is difficult to grasp the amount of internal transactions.

Figure 11 is a diagram for explaining the income and expenditure management of this embodiment. The income and expenditure creation unit 102f creates income and expenditure data by job number, including the order department, order amount, in-house order amount, cost department, cost amount, in-house cost amount, and gross profit, based on the contract details data, parent job data, child job data, order data, and sales data.

Figure 11 (A) is a diagram showing an example of income and expenditure data by job. The first line has project number "PJ0001", contract detail number "0001", job number "0001", order department "Department A", order amount "1,000,000", internal order amount "0", cost department "Department A", cost amount "300,000", internal original amount "400,000", and gross profit "300,000". The internal original amount "400,000" is calculated by taking the cost amount "300,000" + "100,000" of the child job data of destination jobs "0002" and "0003" of source Job No. "0001". The gross profit amount is calculated by (order amount + internal order amount) - (cost amount + internal cost amount).

The second line has the project number "PJ0001", contract detail number "0001", job number "0002", order department "Department B", order amount "0", internal order amount "300,000", cost department "Department B", cost amount "250,000", internal raw amount "0", and gross profit "50,000". The internal order amount "300,000" is the cost amount "300,000" of the child job data of the destination job "0002" of the issuing job number "0001".

The third line has project number "PJ0001", contract detail number "0001", job number "0003", order department "Department C", order amount "0", internal order amount "100,000", cost department "Department C", cost amount "0", internal raw amount "0", gross profit "100,000". The internal order amount "100,000" is the cost amount "100,000" of the child job data of destination job "0003" of source job number "0001".

The income/expense creation unit 102f creates income/expense data by contract detail, including the order department, order amount, internal order amount, cost department, cost amount, and gross profit, on a contract detail basis, based on the income/expense data by job.

Figure 11 (B) is a diagram showing an example of income and expenditure data by contract detail. In the example of contract detail unit income and expenditure data in Figure 11 (B), the project number is "PJ0001", contract detail number is "0001", job number is "0001", order receiving department is "Department A", order amount is "1,000,000", cost department is "Department A", cost amount is "550,000", and gross profit is "450,000". "Order amount" is the total amount of order amounts in the income and expenditure data by job. "Cost amount" is the total amount of cost amounts in the income and expenditure data by job. "Gross profit" is the total amount of gross profit in the income and expenditure data by job.

The income/expense creation unit 102f creates departmental income/expense data including order-receiving department, order amount, cost amount, and gross profit on a department basis based on the job-specific income/expense data.

Figure 11 (C) is a diagram showing an example of departmental income and expenditure data. The first line shows the order receiving department "Department A", the order amount "1,000,000", and the cost amount "700,000". The second line shows the order receiving department "Department B", the order amount "300,000", the cost amount "250,000", and the gross profit "50,000". The third line shows the order receiving department "Department C", the order amount "300,000", the cost amount "0", and the gross profit "100,000". The cost amount is calculated by adding the cost amount of the job-by-job income and expenditure data + the in-house cost amount.

In this way, it is possible to grasp income and expenditures by contract details, job, and department. It is easy to adjust controls so that the income and expenditures of other departments are not visible.

As described above, according to this embodiment, there are a contract work processing unit 102b which creates, for a target project, contract detail data including a contract detail number, an order receiving department, and an order amount, and parent job data including a contract detail number, a job number, and a cost department; a budget work processing unit 102c which creates, for the parent job data, child job data including a contract detail number, a job number, a cost department which is an internal supplier, a cost amount, and an issuing job number which is used as the job number of the parent job data; and an order processing unit 102d which creates, for the target project, order data including an order number, a contract detail number, a job number, an external supplier, and an order amount.
It is equipped with a sales processing unit 102e that creates sales data including the sales number, contract detail number, sales department, and sales amount based on the contract detail data. Therefore, the structure of a parent job generated from the contract detail and a child job derived from the parent for placing orders with other departments makes it possible to streamline in-house ordering operations.

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

In addition, with regard to the order management 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 order management 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 order management device 100 as necessary. That is, a computer program is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to give instructions to the CPU and perform various processes. This computer program is executed by being loaded into RAM, and works with the CPU to form the control unit.

This computer program may also be stored in an application program server connected to the order management 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 on a non-transitory computer-readable recording medium, or may 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 DVD (registered trademark) or 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 order management 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 order management device 100 may 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.

REFERENCE SIGNS LIST 100 Order management device 102 Control unit 102a Item registration unit 102b Contract processing unit 102c Budget processing unit 102d Order processing unit 102e Sales processing unit 102f Income/expense creation unit 102g Screen display control unit 104 Communication interface unit 106 Storage unit 106a Data table 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (6)

An order management device including a control unit,
The control unit is
A contract processing means for creating contract detail data including a contract detail number, an order receiving department, and an order amount for a target project, and parent job data including the contract detail number, a job number of a parent job, and a cost department of the parent job which is the order receiving department;
a budget processing means for creating child job data including the contract detail number, the job number of the child job, the cost department of the child job, the cost amount, and a job number of the issuing party which is the job number of the parent job for linking the parent job and the child job with each other, for the parent job data;
an order processing means for creating order data including an order number, the contract detail number, the job numbers of the parent job and the child job , an external supplier, and an order amount for a target project;
a sales processing means for generating sales data including a sales number, the contract detail number, a sales department, and a sales amount based on the contract detail data;
An order management device comprising: The order management device according to claim 1, characterized in that the control unit further includes an income/expense creation means for creating job-specific income/expense data including the order receiving department, order amount, in-house order amount, cost department, cost amount, in-house cost amount, and gross profit by job number based on the contract details data, the parent job data, the child job data, the order data, and the sales data. The order management device according to claim 2, characterized in that the income/expense creation means creates income/expense data by contract detail, including the order receiving department, order amount, in-house order amount, cost department, cost amount, and gross profit, on a contract detail basis, based on the job-specific income/expense data. The order management device according to claim 2, characterized in that the income/expense creation means creates departmental income/expense data including order department, order amount, cost amount, and gross profit on a department basis based on the job-specific income/expense data. An order management method executed by an information processing device having a control unit,
The control unit executes:
A contract processing process for creating contract detail data including a contract detail number, an order receiving department, and an order amount for a target project, and parent job data including the contract detail number, a job number of a parent job, and a cost department of the parent job which is the order receiving department;
a budget work processing step of creating child job data including the contract detail number, the job number of the child job , the cost department of the child job, the cost amount, and the job number of the parent job which is the job number of the parent job for linking the parent job and the child job ;
an order processing step of creating order data including an order number, the contract detail number, the job numbers of the parent job and the child job , an external supplier, and an order amount for the target project;
a sales processing step of creating sales data including a sales number, the contract detail number, a sales department, and a sales amount based on the contract detail data;
13. An order management method comprising: An order management program to be executed by an information processing device having a control unit,
The control unit ,
A contract processing process for creating contract detail data including a contract detail number, an order receiving department, and an order amount for a target project, and parent job data including the contract detail number, a job number of a parent job, and a cost department of the parent job which is the order receiving department;
a budget work processing step of creating child job data including the contract detail number, the job number of the child job , the cost department of the child job, the cost amount, and the job number of the parent job which is the job number of the parent job for linking the parent job and the child job ;
an order processing step of creating order data including an order number, the contract detail number, the job numbers of the parent job and the child job , an external supplier, and an order amount for the target project;
a sales processing step of creating sales data including a sales number, the contract detail number, a sales department, and a sales amount based on the contract detail data;
An order management program for executing the above.

Images