JP7748351B2 - Fixed asset transfer control device, fixed asset transfer control method, and fixed asset transfer control program - Google Patents

Description

The present invention relates to a fixed asset transfer control device, a fixed asset transfer control method, and a fixed asset transfer control program.

Patent Document 1 discloses a configuration in which, when asset information for fixed assets is recorded or updated, a processing history is recorded for each asset processing operation.

Japanese Patent Application Laid-Open No. 2006-59263

However, the invention described in Patent Document 1 above had the problem that if data for an asset is currently being approved, it was not possible to control the process so that other transfers could not be processed.

The present invention was made in consideration of the above-mentioned problems, and aims to provide a fixed asset transfer control device, a fixed asset transfer control method, and a fixed asset transfer control program that can exercise exclusive control to prevent other transfer processing from being performed on assets that are currently in the approval state.

To solve the above-mentioned problems and achieve the objectives, the fixed asset transfer control device of the present invention is a fixed asset transfer control device comprising a memory unit and a control unit, wherein the memory unit comprises approval storage means for storing transfer reasons for fixed assets whose approval status is not complete and approval history data linked to the approval status, and the control unit comprises transfer request acquisition means for acquiring transfer request data that sets the target transfer reason for the target fixed asset to be transferred, approval status determination means for determining, based on the transfer request data, whether the approval status of the target fixed asset is set in the approval history data, and transfer restriction means for restricting transfer requests for the target fixed asset based on the transfer request data when the approval status determination means determines that the approval status of the target fixed asset is set in the approval history data.

Furthermore, in the fixed asset transfer control device of the present invention, the transfer restriction means is characterized in that, when the approval status determination means determines that the approval status of the target transfer reason for the target fixed asset is set to application, rejection, or withdrawal in the approval history data, it only permits modifications to the target fixed asset based on the transfer request data.

Furthermore, in the fixed asset transfer control device of the present invention, the transfer restriction means is characterized in that, if the approval status determination means determines that the approval status for the target transfer reason of the target fixed asset is set in the approval history data as anything other than applied, rejected, or recalled, the transfer restriction means disallows all transfer requests for the target fixed asset based on the transfer request data.

Furthermore, in the fixed asset transfer control device of the present invention, the transfer restriction means is characterized in that, if the approval status determination means determines that the approval status of a transfer reason other than the target transfer reason of the target fixed asset is set in the approval history data, it disallows all transfer requests for the target fixed asset based on the transfer request data.

Furthermore, in the fixed asset transfer control device according to the present invention, the transfer restriction means is further characterized in that, if the approval status determination means determines that the approval status of the target fixed asset is not set in the approval history data, it permits a transfer request for the target fixed asset based on the transfer request data.

Furthermore, in the fixed asset transfer control device according to the present invention, the transfer restriction means is further characterized in that it displays a message corresponding to the restrictions imposed on the transfer request for the target fixed asset.

Furthermore, in the fixed asset transfer control device of the present invention, the storage unit further comprises post-approval storage means for storing post-approval historical data that sets the transfer reason for the fixed asset whose approval status is complete, and the control unit further comprises approval completion means for, when approval is complete for the target fixed asset set in the approval historical data, deleting the approval historical data that sets the target fixed asset from the approval storage means and storing post-approval historical data that sets the target transfer reason for the target fixed asset in the post-approval storage means.

In the fixed asset transfer control device according to the present invention, the control unit further includes an update means for updating the approval status of the target fixed asset set in the approval history data based on a request for change to interim approval, rejection, or withdrawal of the target fixed asset set in the approval history data, when the request for change is made.

In addition, in the fixed asset transfer control device of the present invention, the control unit is further characterized by including a report output means that, when an approval status reflection category that allows selection of differences in the approval status is selected, outputs list report data for the fixed asset based on the selected approval status reflection category, the approval history data, and the post-approval history data.

The fixed asset transfer control device of the present invention is further characterized by comprising a report output means that, when a reflection unit that can be selected by asset type or asset, and an approval status reflection category that can select the difference in approval status, outputs depreciation list report data that sets the depreciation amount for the fixed asset by asset type or asset, based on the selected reflection unit, selected approval status reflection category, the approval history data, and the post-approval history data.

Furthermore, in the fixed asset transfer control device of the present invention, the transfer restriction means is further characterized in that, when the target transfer reason is a split and the approval status determination means determines that the approval status of the target fixed asset is set in the approval history data, it updates the transfer reason set in the approval history data to the split, and stores in the approval storage means new approval history data in which the approval status of the transfer reason, which is the acquisition of the target fixed asset, is set, and new approval history data in which the approval status of the transfer reason, which is the transfer of the target fixed asset, is set.

The fixed asset transfer control method of the present invention is a fixed asset transfer control method to be executed by a fixed asset transfer control device having a memory unit and a control unit, wherein the memory unit includes approval storage means for storing transfer reasons for fixed assets whose approval status is not complete and approval history data linked to the approval status, and includes a transfer request acquisition step executed by the control unit to acquire transfer request data setting the target transfer reason for the target fixed asset to be transferred, an approval status determination step to determine whether the approval status of the target fixed asset is set in the approval history data based on the transfer request data, and a transfer restriction step to restrict the transfer request for the target fixed asset based on the transfer request data if it is determined in the approval status determination step that the approval status of the target fixed asset is set in the approval history data.

The fixed asset transfer control program of the present invention is a fixed asset transfer control program to be executed by a fixed asset transfer control device having a memory unit and a control unit, wherein the memory unit includes an approval storage means for storing the reasons for transfers of fixed assets whose approval status is not complete and approval history data linked to the approval status, and the control unit executes the following steps: a transfer request acquisition step for acquiring transfer request data that sets the target transfer reason for the target fixed asset to be transferred; an approval status determination step for determining, based on the transfer request data, whether the approval status of the target fixed asset is set in the approval history data; and a transfer restriction step for restricting the transfer request for the target fixed asset based on the transfer request data if it is determined in the approval status determination step that the approval status of the target fixed asset is set in the approval history data.

The present invention provides the advantages of strengthening security and control by systematizing approval procedures previously performed outside the system, and enabling early understanding of management figures. The present invention also provides the advantage of enabling approval for multiple fixed asset transfer reasons (acquisition, transfer, disposal, etc.). The present invention also provides the advantage of being able to grasp depreciation calculation results for assets currently under approval. The present invention also provides the advantage of addressing the increasingly complex approval procedures and control requirements that involve field departments, particularly in large companies, in asset purchasing procedures. The present invention also provides the advantage of enabling processing based on the closing status and transfer reason, and enabling switching between processing on the field screen and the accounting screen. While approval is essential as a control requirement, particularly for companies that manage operations on the field, delays in approval processing by field departments have the disadvantage of making it difficult to obtain the figures necessary for management. However, the present invention provides the advantage of satisfying control requirements while enabling early understanding of management figures due to missed or delayed approvals.

FIG. 1 is a diagram showing an example of a data structure in this embodiment. FIG. 2 is a diagram showing an example of a data structure in this embodiment. FIG. 3 is a block diagram showing an example of the configuration of a fixed asset transfer control device according to this embodiment. FIG. 4 is a diagram showing an example of approval history data in this embodiment. FIG. 5 is a flowchart showing an example of processing by the fixed asset transfer control device in this embodiment. FIG. 6 is a flowchart showing an example of fixed asset transfer control processing in this embodiment. FIG. 7 is a diagram showing an example of data update processing in this embodiment. FIG. 8 is a diagram showing an example of data update processing in this embodiment. FIG. 9 is a diagram illustrating an example of data update processing in this embodiment. FIG. 10 is a diagram showing an example of data update processing in this embodiment. FIG. 11 is a diagram illustrating an example of data update processing in this embodiment. FIG. 12 is a diagram illustrating an example of data update processing in this embodiment. FIG. 13 is a diagram illustrating an example of data update processing in this embodiment. FIG. 14 is a diagram illustrating an example of data update processing in this embodiment. FIG. 15 is a diagram illustrating an example of data update processing in this embodiment. FIG. 16 is a diagram illustrating an example of data update processing in this embodiment. FIG. 17 is a diagram illustrating an example of data update processing in this embodiment. FIG. 18 is a diagram showing an example of data update processing in this embodiment. FIG. 19 is a diagram showing an example of the form output process in this embodiment. FIG. 20 is a diagram showing an example of a form output process in this embodiment. FIG. 21 is a diagram showing an example of a form output process in this embodiment. FIG. 22 is a diagram showing an example of a form output process in this embodiment. FIG. 23 is a diagram showing an example of approval data and post-approval data in this embodiment. FIG. 24 is a diagram showing an example of the form output process in this embodiment. FIG. 25 is a diagram showing an example of a form output process in this embodiment. FIG. 26 is a diagram showing an example of a form in this embodiment. FIG. 27 is a diagram showing an example of a form in this embodiment. FIG. 28 is a diagram showing an example of fixed asset division processing in this embodiment. FIG. 29 is a diagram showing an example of a movement registration screen in this embodiment. FIG. 30 is a diagram showing an example of fixed asset division processing in this embodiment. FIG. 31 is a diagram showing an example of fixed asset division processing in this embodiment. FIG. 32 is a diagram showing an example of data update processing in this embodiment.

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

[1. Overview]
First, an overview of the present invention will be described with reference to Figures 1 and 2. Figures 1 and 2 are diagrams showing an example of a data structure in this embodiment.

There has long been a demand for the ability to approve fixed assets that have multiple transfer events (acquisition, transfer, disposal, etc.) for a single asset. Because the depreciation calculation results for fixed asset data change depending on the transfer event, it is necessary to apply chronological processing control. There is also a demand for controls to prevent the registration of additional transfer data for assets currently under approval. Furthermore, there is a demand for the ability to check the results of data currently under approval in order to obtain preliminary depreciation calculation results for assets currently under approval.

Traditionally, large corporations and other companies have made purchasing decisions at the field level, making it difficult to manage asset-like purchases. Furthermore, companies have often used Excel (registered trademark) for reporting purposes and for on-site controls, resulting in missed accounting entries, delayed approvals, and incomplete controls.

As a result, particularly in companies that previously managed assets in field departments, operations were complicated by processing approvals outside the system, preventing them from meeting control requirements. System implementation was delayed due to missed or delayed approvals, making it difficult to obtain the figures necessary for management.

In this embodiment, therefore, a table for storing data under approval and a table for managing the approval status (e.g., a pre-approval table) are constructed separately from a table for storing data after approval is complete (e.g., a post-approval table), and by managing this data, a mechanism is provided in which, when a fixed asset change is registered, depreciation calculations are performed and the post-change calculation results (e.g., 24 months' worth) are retained, the existence of data under approval is checked, the registration of change data is controlled, data output before and after approval is controlled, and report output before and after approval is implemented.

Here, as with the fixed asset ledger registration shown in Figure 1 and the transfer registration shown in Figure 2, data management in this embodiment has the same system of pre-approval tables (tables for approval) and post-approval tables (tables in which data for approved items is updated), and the pre-approval table is updated at the time of registration, and the post-approval table is updated when final approval is completed.

In this embodiment, if there is data currently being approved for an asset, other transfer processing is prevented. The presence or absence of data is determined in the "Historical Data_Data for Approval" table, and an error message is displayed when the transfer is registered. Furthermore, in this embodiment, to output data before and after approval, a depreciation calculation is performed when the transfer is registered, and the data is updated and saved in the pre-approval table. When outputting reports, control is exercised as to whether pre-approval data is included or not, or whether only unapproved data is output.

In this embodiment, the transfer events (reason for transfer) that are subject to approval may include "acquisition": purchase of an asset, "transfer": relocation of an asset, "disposal": disposal or sale of an asset, "division": division of an asset that was registered as a set, "impairment": decrease in asset value, "suspension": suspension of use or operation of an asset, "change in depreciation method and useful life": change in depreciation method or useful life due to change in asset use, etc., or "change in asset type": change in asset type due to change in asset use, etc.

2. Configuration
An example of the configuration of the fixed asset transfer control device 100 according to this embodiment will be described with reference to Figures 3 and 4. Figure 3 is a block diagram showing an example of the configuration of the fixed asset transfer control device 100 according to this embodiment.

As shown in FIG. 3, the fixed asset transfer control device 100 is a commercially available desktop personal computer. Note that the fixed asset transfer control device 100 is not limited to a stationary information processing device such as a desktop personal computer, but may also be a portable information processing device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

The fixed asset transfer control device 100 comprises a control unit 102, a communication interface unit 104, a memory unit 106, and an input/output interface unit 108. Each unit of the fixed asset transfer control 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 fixed asset transfer control 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 the function of communicating data with other devices via a communication line. Here, the network 300 has the function of connecting the fixed asset transfer control 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).

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 touch panel), a speaker, or a printer. The input device 112 may be a keyboard, a mouse, a microphone, or a monitor that functions as a pointing device in conjunction with a mouse. Note that, below, the output device 114 may be referred to as the monitor 114 or the printer 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 stores computer programs that work in conjunction with the OS (Operating System) to issue commands to the CPU (Central Processing Unit) to perform various processes. The memory unit 106 can be, for example, a memory device such as RAM (Random Access Memory) or ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, or an optical disk. The memory unit 106 includes an approval database 106a and a post-approval database 106b.

The approval database 106a stores approval data. Here, the approval database 106a may store approval history data linked to the reasons for changes in fixed assets whose approval status is not complete, and the approval status. The approval database 106a may also store approval asset data, approval depreciation data, approval transfer data, and/or approval monthly depreciation data.

Here, an example of approval history data in this embodiment will be described with reference to Figure 4. Figure 4 is a diagram showing an example of approval history data in this embodiment.

As shown in Figure 4, the approval history data in this embodiment is a table that manages the approval status of all transfer events. When a transfer application (registration) is made, a record is updated in "History data_Approval data," and when approval is made, the approval status is updated.

Returning to Figure 3, the post-approval database 106b stores post-approval data. Here, the post-approval database 106b may store post-approval history data that sets the reasons for changes to fixed assets whose approval status is complete. The post-approval database 106b may also store asset data, depreciation data, transfer data, and/or monthly depreciation data.

The control unit 102 is a CPU or the like that provides overall control of the fixed asset transfer control device 100. The control unit 102 has internal memory for storing control programs such as an OS, programs that define various processing procedures, and required data, and executes various information processing operations based on these stored programs. Functionally, the control unit 102 conceptually comprises a transfer request acquisition unit 102a, an approval status determination unit 102b, a transfer restriction unit 102c, an update unit 102d, an approval completion unit 102e, and a report output unit 102f.

The transfer request acquisition unit 102a acquires transfer request data for the target fixed asset that is the subject of the transfer. Here, the transfer request acquisition unit 102a may acquire transfer request data that sets the target transfer reason for the target fixed asset that is the subject of the transfer. Furthermore, the target transfer reason may be acquisition, transfer, division, impairment, suspension, or change, etc.

The approval status determination unit 102b determines whether the approval status of the target fixed asset is set in the approval history data. Here, the approval status determination unit 102b may determine whether the approval status of the target fixed asset is set in the approval history data based on the transfer request data.

The transfer restriction unit 102c controls transfer requests for the target fixed asset based on the transfer request data. Here, if the approval status determination unit 102b determines that the approval status of the target fixed asset is set in the approval history data, the transfer restriction unit 102c may restrict transfer requests for the target fixed asset based on the transfer request data. Furthermore, if the approval status determination unit 102b determines that the approval status of the target change reason for the target fixed asset is set to apply, reject, or withdraw in the approval history data, the transfer restriction unit 102c may only permit modifications to the target fixed asset based on the transfer request data. Furthermore, if the approval status determination unit 102b determines that the approval status of the target change reason for the target fixed asset is set to anything other than apply, reject, or withdraw in the approval history data, the transfer restriction unit 102c may disallow all transfer requests for the target fixed asset based on the transfer request data. In addition, when the approval status determination unit 102b determines that the approval status of a transfer reason other than the target transfer reason of the target fixed asset is set in the approval history data, the transfer restriction unit 102c may disallow all transfer requests for the target fixed asset based on the transfer request data.In addition, when the approval status determination unit 102b determines that the approval status of the target fixed asset is not set in the approval history data, the transfer restriction unit 102c may permit transfer requests for the target fixed asset based on the transfer request data.In addition, the transfer restriction unit 102c may display a message corresponding to the restrictions on transfer requests for the target fixed asset. Furthermore, if the target change reason for the target fixed asset set in the change request data is split, and the approval status determination unit 102b determines that the approval status of the target fixed asset is set in the approval history data, the change restriction unit 102c may update the change reason set in the approval history data to split, and store new approval history data in which the approval status for the change reason for the acquisition of the target fixed asset is set, and new approval history data in which the approval status for the change reason for the transfer of the target fixed asset is set in the approval database 106a.

The update unit 102d updates the approval status of the target fixed asset set in the approval history data. Here, if a request is made to change the approval status of the target fixed asset set in the approval history data to interim approval, rejection, or withdrawal, the update unit 102d may update the approval status of the target fixed asset set in the approval history data based on the change request.

The approval completion unit 102e deletes the approval historical data in which the target fixed asset is set from the approval database 106a, and stores (registers) the post-approval historical data in which the target change reason for the target fixed asset is set in the post-approval database 106b. Here, when the target fixed asset set in the approval historical data has been approved, the approval completion unit 102e may delete the approval historical data in which the target fixed asset is set from the approval database 106a, and store the post-approval historical data in which the target change reason for the target fixed asset is set in the post-approval database 106b.

The report output unit 102f outputs report data for fixed assets. Here, when an approval status reflection category that allows selection of differences in approval status is selected, the report output unit 102f may output list report data for fixed assets based on the selected approval status reflection category, approval history data, and post-approval history data. Furthermore, when a reflection unit that allows selection of an asset type unit or asset unit, and an approval status reflection category that allows selection of differences in approval status, are selected, the report output unit 102f may output depreciation list report data that sets the depreciation amount for fixed assets by asset type or asset unit based on the selected reflection unit, selected approval status reflection category, approval history data, and post-approval history data.

3. Specific Examples
A specific example of this embodiment will be described with reference to FIGS.

[Fixed asset transfer control processing]
An example of the fixed asset transfer control process in this embodiment will now be described with reference to Fig. 5. Fig. 5 is a flowchart showing an example of the process of the fixed asset transfer control device 100 in this embodiment.

As shown in Figure 5, when a fixed asset transfer occurs and the user sets the target fixed asset and the target transfer reason on the transfer registration screen via the input device 112, the transfer request acquisition unit 102a acquires the transfer request data that sets the target transfer reason for the target fixed asset (step SA-1).

Then, the approval status determination unit 102b determines, based on the transfer request data, whether the approval status of the target fixed asset is set in the approval history data stored in the approval database 106a (step SA-2).

If the approval status determination unit 102b determines that the approval status of the target fixed asset is set in the approval history data stored in the approval database 106a (step SA-2: Yes), it transitions to step SA-3.

Then, the transfer restriction unit 102c restricts transfer requests for the target fixed asset based on the transfer request data (step SA-3) and proceeds to step SA-5.

On the other hand, if the approval status determination unit 102b determines that the approval status of the target fixed asset is not set in the approval history data stored in the approval database 106a (step SA-2: No), it transitions the process to step SA-4.

Then, the transfer restriction unit 102c authorizes the transfer request for the target fixed asset based on the transfer request data (step SA-4) and proceeds to step SA-5.

Then, when the user selects an approval status reflection category that allows selection of different approval statuses on the fixed asset ledger screen via the input device 112, the report output unit 102f displays fixed asset list report data on the output device 114 based on the selected approval status reflection category, approval history data, and post-approval history data (step SA-5).

Then, when approval is completed for the target fixed asset set in the approval history data stored in the approval database 106a, the approval completion unit 102e deletes the approval history data in which the target fixed asset is set from the approval database 106a, stores the post-approval history data in which the target change reason for the target fixed asset is set in the post-approval database 106b (step SA-6), and terminates processing.

Now, with reference to Figure 6, an example of fixed asset transfer control processing in this embodiment will be described. Figure 6 is a flowchart showing an example of fixed asset transfer control processing in this embodiment.

As shown in Figure 6, in this embodiment, when a fixed asset change occurs, the user calls up the target fixed asset on the change registration screen (step SB-1), and a determination is made as to whether the target fixed asset is a fixed asset currently being approved (step SB-2).

In this embodiment, if it is determined that the target fixed asset is not a fixed asset currently under approval (step SB-2: No), processing proceeds to step SB-11. If it is determined that the target fixed asset is a fixed asset currently under approval (step SB-2: Yes), it is determined whether the target change reason for the target fixed asset is a split (step SB-3).

In this embodiment, if it is determined that the target change reason for the target fixed asset is not a split (step SB-3: No), processing proceeds to step SB-7. If it is determined that the target change reason for the target fixed asset is a split (step SB-3: Yes), it is determined whether the target fixed asset has multiple system history numbers (step SB-4).

In this embodiment, if it is determined that the target fixed asset does not have multiple system history numbers (step SB-4: No), processing proceeds to step SB-7. If it is determined that the target fixed asset has multiple system history numbers (step SB-4: Yes), it is determined whether the target fixed asset has a transfer reason of "transfer" within the same system history number (step SB-5).

In this embodiment, if it is determined that a fixed asset with a transfer reason of "transfer" exists within the same system history number (step SB-5: Yes), processing proceeds to step SB-7. If it is determined that a fixed asset with a transfer reason of "transfer" does not exist within the same system history number (step SB-5: No), it is determined whether a fixed asset with a transfer reason of "disposal" exists within the same system history number (step SB-6).

In this embodiment, if it is determined that there is no fixed asset with a transfer reason of "retirement" within the same system history number (step SB-6: No), processing proceeds to step SB-10. If it is determined that there is a fixed asset with a transfer reason of "retirement" within the same system history number (step SB-6: Yes), it is determined whether the transfer reason being processed is the same as the transfer reason for the fixed asset being approved (step SB-7).

In this embodiment, if it is determined that the reason for the target change being processed is not the same as the reason for the change of the fixed asset being approved (step SB-7: No), processing proceeds to step SB-10. If it is determined that the reason for the target change being processed is the same as the reason for the change of the fixed asset being approved (step SB-7: Yes), it is determined whether the approval status of the fixed asset being approved is "Apply," "Reject," or "Withdraw" (step SB-8).

In this embodiment, if it is determined that the approval status of the fixed asset being approved does not correspond to "Apply," "Reject," or "Withdraw" (step SB-8: No), processing proceeds to step SB-10. If it is determined that the approval status of the fixed asset being approved corresponds to "Apply," "Reject," or "Withdraw" (step SB-8: Yes), it is determined whether the processing mode (update category) is "Modify" (step SB-9).

In this embodiment, if the processing mode (update classification) is determined to be "modification" (step SB-9: Yes), processing proceeds to step SB-11. If the processing mode (update classification) is determined not to be "modification" (step SB-9: No), the transfer request for the target fixed asset is restricted, the approval data cannot be called (step SB-10), and processing ends.

In contrast, in this embodiment, transfer request data is entered via the transfer registration screen (step SB-11), processing is executed based on the transfer request data, fixed asset transfer registration is completed (step SB-12), and processing ends.

Furthermore, an example of data update processing in this embodiment will be described with reference to Figures 7 to 18. Figures 7 to 18 are diagrams showing an example of data update processing in this embodiment.

As shown in Figure 7, in this embodiment, in the "acquisition" data update process for "new" fixed asset registration, approval data is registered when a fixed asset registration application is made, and when approval is completed, the approval data is deleted and post-approval data is registered.

Furthermore, as shown in Figure 8, in the "movement" data update process for "new" in this embodiment, approval data is registered when a movement registration application is made, and when approval is completed, the approval data is deleted and the registered post-approval data is updated.

Furthermore, as shown in Figure 9, in the "acquisition" data update process during "modification" in this embodiment, approval data is registered when a fixed asset registration (modification) application is made, and when approval is completed, the approval data is deleted and the registered post-approval data is updated.

Furthermore, as shown in Figure 10, in the "movement" data update process when "modification" is made in this embodiment, approval data is registered when a movement registration (modification) application is made, and when approval is completed, the approval data is deleted and the registered post-approval data is updated.

Furthermore, as shown in Figure 11, in the "acquisition" data update process during "deletion" in this embodiment, approval data is registered when a fixed asset registration (deletion) application is made, and the approval data is deleted when approval is completed, and the registered post-approval data is deleted.

Furthermore, as shown in Figure 12, in the "movement" data update process when "deletion" is performed in this embodiment, approval data is registered when a movement registration (deletion) application is made, and the approval data is deleted when approval is completed, and the registered post-approval data is deleted.

Furthermore, as shown in Figure 13, in the approval status update process in this embodiment, approval data is registered when a fixed asset registration application is made, the approval data is updated when intermediate approval is granted, and when approval is completed, the approval data is deleted and post-approval data is registered.

Also, as shown in Figure 14, if the approver notices a registration error and returns the document to the applicant, the "rejected" data update process in this embodiment updates the approval data registered at the time of the fixed asset registration application to rejected.

Also, as shown in Figure 15, if the applicant realizes they have made a registration error and withdraws the data, the "withdrawal" data update process in this embodiment updates the approval data registered at the time of the fixed asset registration application to the withdrawal.

Furthermore, in this embodiment, as shown in Figure 16, when the approval status is "10: Apply," "30: Reject," or "40: Withdraw," only modifications for the same reason for change are permitted, and other registrations are prevented; and as shown in Figure 17, when the approval status is "20: Approval in progress," all registrations may be prevented.

Also, as shown in Figure 18, in this embodiment, when each change is registered, the presence or absence of data currently being approved for the target fixed asset is determined and controlled using the "History Data - Approval Data" table (history data for approval).

Furthermore, an example of the report output process in this embodiment will be described with reference to Figures 19 to 27. Figures 19 to 22, 24, and 25 are diagrams showing an example of the report output process in this embodiment. Figure 23 is a diagram showing an example of approval data and post-approval data in this embodiment. Figures 26 and 27 are diagrams showing an example of a report in this embodiment.

In this embodiment, data is output from the ledger that checks the status of fixed assets and the list that checks the status of transfers based on the criteria of "final approval completed only," "reflects data before final approval," or "unapproved only." The ledger can reflect the contents currently being approved, the reason for the transfer being approved is printed, and the presence or absence of data in the "Historical data_Approval data" table is checked to determine whether the report should be reflected, allowing only the unapproved portion to be output. Figure 19 shows the fixed asset ledger report data output when a new fixed asset is registered in this embodiment, Figure 20 shows the fixed asset ledger report data output when a fixed asset is amended in this embodiment, and Figure 21 shows the fixed asset ledger report data output when a transfer is registered in this embodiment.

In addition, in this embodiment, the list can reflect the contents before and during approval, and the report reflection is determined by checking whether there is data in the "History Data - Approval Data" table, and the details of the approval are printed so that they can be seen. Here, Figure 22 shows the report data of the transfer list that is output when registering a transfer in this embodiment.

In addition, in this embodiment, the depreciation expense list, which confirms the depreciation calculation results when a change is registered based on the approval data and post-approval data shown in Figure 23, outputs data based on "final approval completed only," "reflects data before final approval," or "unapproved only." The depreciation expense list can reflect pre-approval and pending content, and the presence or absence of data in the "history data_approval data" table determines whether the report is reflected. When printing each fixed asset, the reason for the change is printed so that fixed assets currently under approval can be identified. Here, in this embodiment, if the user selects asset type as the reflection unit on the fixed asset ledger screen shown in Figure 24, the depreciation expense list is printed as shown in Figure 25. Also, in this embodiment, if the user selects asset type as the reflection unit on the fixed asset ledger screen shown in Figure 26, the depreciation expense list is printed as shown in Figure 27.

Furthermore, an example of fixed asset division in this embodiment will be described with reference to Figures 28 to 32. Figures 28, 30, and 31 are diagrams showing an example of fixed asset division processing in this embodiment. Figure 29 is a diagram showing an example of a transfer registration screen in this embodiment. Figure 32 is a diagram showing an example of data update processing in this embodiment.

In this embodiment, as shown in Figure 28, when a fixed asset consisting of a set of machines A and B is split from Division A to Division B, as shown in the transfer registration screen in Figure 29, since this is a partial transfer, the asset is transferred to Division B, the division into which machine B is to be split, and an asset number for the division into which it is to be split is automatically assigned.

Furthermore, in the "partial transfer" data update process when "splitting" in this embodiment, as shown in Figure 30, the transfer reason set in the "history data_approval data" table at the time of transfer registration is updated to "split," new approval data is registered that sets the approval status for the transfer reason, which is the acquisition of the target fixed asset, and new approval data that sets the approval status for the transfer reason, which is the transfer of the target fixed asset, and as shown in Figure 31, when approval is completed, the approval data is deleted and the registered post-approval data is updated.

Also, as shown in Figure 32, in this embodiment, when a transfer registration call is made for asset number "N001" in pattern (1), if the "History Data_Approval Data" table contains data for the transfer reason category "7: Split", and there are multiple system history numbers, and the transfer reason category within the same system history number is "3: Move", it is determined to be a partial transfer process, and only modifications are permitted, with no other registrations being allowed. Also, as shown in Figure 32, in this embodiment, when a transfer registration call is made for asset number "N002" in pattern (2), if the "History Data_Approval Data" table contains data for the transfer reason category "1: Acquisition" or "3: Move", multiple approval data exists, and no registrations are allowed. Also, as shown in FIG. 32, in this embodiment, when calling for ledger registration for asset number "N001" in pattern (3), if the "History Data_Approval Data" table contains data for the transfer reason category "7: Split", and there are multiple system history numbers, and the transfer reason category within the same system history number is "3: Transfer", it is determined to be a partial transfer process and control is performed to prevent all registrations. Also, as shown in FIG. 32, in this embodiment, when calling for ledger registration for asset number "N002", if the "History Data_Approval Data" table contains data for the transfer reason category "1: Acquisition" or "3: Transfer", multiple approval data exists and control is performed to prevent all registrations.

[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 contributing to the achievement of SDGs Goals 8 and 9.

Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to SDGs goals 12, 13, and 15.

Furthermore, this embodiment can contribute to strengthening control and governance, thereby contributing to Goal 16 of the SDGs.

5. Other Embodiments
The present invention may be implemented 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 known methods.

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 fixed asset transfer control device 100, the components shown in the figure are functional concepts and do not necessarily have to be physically configured as shown.

For example, all or any part of the processing functions of the fixed asset transfer control device 100, particularly the processing functions performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or may be implemented as hardware using wired logic. The program is recorded on a non-transitory, computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processes described in this embodiment, and is mechanically read by the fixed asset transfer control device 100 as needed. In other words, a computer program that works in conjunction with the OS to issue commands to the CPU and perform various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). This computer program is executed by being loaded into RAM, and works in conjunction with the CPU to form the control unit.

This computer program may also be stored on an application program server connected to the fixed asset transfer control 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-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" includes memory cards, USB (Universal Serial Bus) memories, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (registered trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical disks), DVDs (Digital Versatile Disks), and more. This includes any "portable physical media" such as a Blu-ray Disc (registered trademark) 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. It should be noted that a "program" is not necessarily limited to a single structure, but also includes a distributed structure consisting of multiple modules or libraries, or a structure that achieves its function by working in conjunction with a separate program, such as an OS. The specific structure and reading procedure for reading a recording medium in each device shown in this embodiment, as well as the installation procedure after reading, can use well-known structures and procedures.

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

The fixed asset transfer control device 100 may also be configured as an information processing device such as a known personal computer or workstation, or as such an information processing device to which any peripheral device is connected. The fixed asset transfer control device 100 may also be implemented by installing software (including programs or data, etc.) on such a device that enables 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 may be implemented in any combination, or embodiments may be implemented selectively.

The present invention is useful in industries such as manufacturing, retail, or finance.

REFERENCE SIGNS LIST 100 Fixed asset transfer control device 102 Control unit 102a Transfer request acquisition unit 102b Approval status determination unit 102c Transfer restriction unit 102d Update unit 102e Approval completion unit 102f Report output unit 104 Communication interface unit 106 Storage unit 106a Approval database 106b Post-approval database 108 Input/output interface unit 112 Input device 114 Output device 200 Server 300 Network

Claims (13)

A fixed asset transfer control device including a storage unit and a control unit,
The storage unit
an approval storage means for storing approval history data set in association with the reasons for transfer of fixed assets whose approval status is not complete and the approval status;
Equipped with
The control unit
a transfer request acquisition means for acquiring transfer request data in which a target transfer reason of the target fixed asset to be transferred is set;
an approval status determination means for determining whether the approval status of the target fixed asset is set in the approval history data based on the transfer request data;
a transfer restriction means for restricting a transfer request for the target fixed asset based on the transfer request data when the approval status determination means determines that the approval status of the target fixed asset is set in the approval history data;
A fixed asset transfer control device comprising: The transfer restriction means is
A fixed asset transfer control device as described in claim 1, characterized in that if the approval status determination means determines that the approval status of the target fixed asset for the target transfer reason is set to application, rejection, or withdrawal in the approval history data, only modifications to the target fixed asset are permitted based on the transfer request data. The transfer restriction means is
A fixed asset transfer control device as described in claim 1, characterized in that if the approval status determination means determines that the approval status of the target transfer reason for the target fixed asset is set to anything other than application, rejection, or withdrawal in the approval history data, all transfer requests for the target fixed asset are disapproved based on the transfer request data. The transfer restriction means is
A fixed asset transfer control device as described in claim 1, characterized in that if the approval status determination means determines that the approval status of a transfer reason other than the target transfer reason of the target fixed asset is set in the approval history data, all transfer requests for the target fixed asset are disapproved based on the transfer request data. The transfer restriction means is
The fixed asset transfer control device as described in claim 1 further characterized in that, if the approval status determination means determines that the approval status of the target fixed asset is not set in the approval history data, a transfer request for the target fixed asset is permitted based on the transfer request data. The transfer restriction means is
5. The fixed asset transfer control device according to claim 1, further comprising a message corresponding to the restriction content imposed on the transfer request for the target fixed asset. The storage unit
a post-approval storage means for storing post-approval history data in which the reason for the transfer of the fixed asset whose approval status is "completed" is set;
Further provided with
The control unit
an approval completion means for, when approval of the target fixed asset set in the approval history data is completed, deleting the approval history data in which the target fixed asset is set from the approval storage means, and storing post-approval history data in which the target change reason of the target fixed asset is set in the post-approval storage means;
2. The fixed asset transfer control device according to claim 1, further comprising: The control unit
an update means for updating the approval status of the target fixed asset set in the approval history data based on an application for change to interim approval, rejection, or withdrawal of the target fixed asset set in the approval history data;
2. The fixed asset transfer control device according to claim 1, further comprising: The control unit
a report output means for outputting list report data of the fixed assets based on the selected approval status reflection category, the approval history data, and the post-approval history data when an approval status reflection category that allows selection of a difference in the approval status is selected;
8. The fixed asset transfer control device according to claim 7, further comprising: a report output means for outputting depreciation list report data in which the depreciation amount of the fixed asset for each asset type or each asset unit is set based on the selected reflection unit, the selected approval status reflection class, the approval history data, and the post-approval history data, when a reflection unit that can select an asset type unit or an asset unit and an approval status reflection class that can select a difference in the approval status are selected;
8. The fixed asset transfer control device according to claim 7, further comprising: The transfer restriction means is
Furthermore, when the target transfer reason is a division and the approval status determination means determines that the approval status of the target fixed asset is set in the approval history data, the transfer reason set in the approval history data is updated to the division, and new approval history data in which the approval status of the transfer reason, which is the acquisition of the target fixed asset, is set, and new approval history data in which the approval status of the transfer reason, which is the transfer of the target fixed asset, is set are stored in the approval storage means. A fixed asset transfer control method to be executed by a fixed asset transfer control device having a storage unit and a control unit,
The storage unit
an approval storage means for storing approval history data set in association with the reasons for transfer of fixed assets whose approval status is not complete and the approval status;
Equipped with
Executed in the control unit:
a transfer request acquisition step for acquiring transfer request data in which a target transfer reason of a target fixed asset to be transferred is set;
an approval status determination step of determining whether the approval status of the target fixed asset is set in the approval history data based on the change request data;
a transfer restriction step of restricting a transfer request for the target fixed asset based on the transfer request data when it is determined in the approval status determination step that the approval status of the target fixed asset is set in the approval history data;
A fixed asset transfer control method comprising: A fixed asset transfer control program to be executed by a fixed asset transfer control device having a storage unit and a control unit,
The storage unit
an approval storage means for storing approval history data set in association with the reasons for transfer of fixed assets whose approval status is not complete and the approval status;
Equipped with
In the control unit,
a transfer request acquisition step for acquiring transfer request data in which a target transfer reason of a target fixed asset to be transferred is set;
an approval status determination step of determining whether the approval status of the target fixed asset is set in the approval history data based on the change request data;
a transfer restriction step of restricting a transfer request for the target fixed asset based on the transfer request data when it is determined in the approval status determination step that the approval status of the target fixed asset is set in the approval history data;
A fixed asset transfer control program for executing the above.