Fixed asset transfer control device, fixed asset transfer control method, and fixed asset transfer control program

Abstract

To provide a fixed asset change control device, a fixed asset change control method, and a fixed asset change control program that can execute exclusion control for assets being approved so that another change processing cannot be performed on the assets.SOLUTION: A fixed asset change control device acquires change request data that is set with a target change reason for a target fixed asset to be changed, determines whether an approval state of the target fixed asset is set to history data for approval based on the change request data, and when determining that the approval state of the target fixed asset is set to the history data for approval, restricts a request for changing the target fixed asset based on the change request data.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a fixed asset transfer control device, a fixed asset transfer control method, and a fixed asset transfer control program. [Background technology]

[0002] Patent Document 1 discloses a configuration in which, when asset information of a fixed asset is recorded or updated, a processing history is recorded for each content of asset processing. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-59263 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the invention described in Patent Document 1 above has a problem in that when there is data in the process of being approved for one asset, it is not possible to control so that other transfer processes cannot be performed.

[0005] The present invention has been 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 in the approval state. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, 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 an approval memory means for storing the reasons for transfer of fixed assets whose approval status is not complete and approval history data linked to the approval status, and the control unit comprises a transfer request acquisition means for acquiring transfer request data setting the target transfer reason of the target fixed asset to be transferred, 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, and a transfer restriction means for restricting the transfer request of 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.

[0007] In addition, 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 allows modification of the target fixed asset based on the transfer request data.

[0008] In addition, 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 of the target fixed asset is set to anything other than application, rejection, or withdrawal in the approval history data, it disallows all transfer requests for the target fixed asset based on the transfer request data.

[0009] In addition, 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 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.

[0010] In addition, in the fixed asset transfer control device of the present invention, the transfer restriction means is further characterized in that, when 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.

[0011] In the fixed asset transfer control device according to the present invention, the transfer restriction means further displays a message corresponding to the restriction content for the transfer request of the target fixed asset.

[0012] In addition, in the fixed asset transfer control device of the present invention, the memory unit further comprises a post-approval storage means for storing post-approval history data in which the transfer reason of the fixed asset whose approval status is complete is set, and the control unit further comprises an approval completion means for, when the target fixed asset set in the approval history data is approved, deleting the approval history data in which the target fixed asset is set from the approval storage means and storing the post-approval history data in which the target transfer reason of the target fixed asset is set in the post-approval storage means.

[0013] In addition, in the fixed asset transfer control device of the present invention, the control unit is characterized by further comprising 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 approval status of the target fixed asset set in the approval history data.

[0014] In addition, in the fixed asset transfer control device of the present invention, the control unit is characterized by further comprising a report output means for outputting list report data of the fixed asset 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 differences in the approval status is selected.

[0015] In addition, the fixed asset transfer control device according to the present invention is characterized in that it further comprises a report output means for outputting depreciation list report data that sets the depreciation amount for the fixed asset on an asset type basis or an asset basis, based on the selected reflection unit, the selected approval status reflection category, the approval history data, and the post-approval history data, when a reflection unit that can select an asset type basis or an asset basis and an approval status reflection category that can select a difference in the approval status are selected.

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

[0017] Furthermore, 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 has an approval memory means for storing the reasons for transfer of fixed assets whose approval status is not complete and approval history data set in association with the approval status, and is characterized by including: a transfer request acquisition step executed by the control unit for acquiring transfer request data setting the target transfer reason of a 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 of 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.

[0018] In addition, 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 has an approval memory means for storing the reasons for transfer of fixed assets whose approval status is not complete and approval history data set in association with the approval status, and the control unit executes the following steps: a transfer request acquisition step for acquiring transfer request data setting the target transfer reason of 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 of 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. [Effects of the Invention]

[0019] According to the present invention, by systemizing approval procedures previously performed outside the system, security and control are strengthened, enabling early understanding of management figures. Furthermore, according to the present invention, approval can be performed for each of multiple fixed asset transfer reasons (acquisition, transfer, disposal, etc.). Furthermore, according to the present invention, depreciation calculation results can be grasped for assets currently undergoing approval. Furthermore, according to the present invention, asset purchasing procedures can be handled in response to increasingly complex approval procedures and control requirements involving field departments, particularly in large companies. Furthermore, according to the present invention, processing can be performed according to the closing status and the reason for the transfer, and processing can be switched between the field screen and the accounting screen. Furthermore, particularly in companies that manage on-site, approval is essential as a control requirement, but delays in approval processing by field departments have the disadvantage of making it difficult to obtain the figures necessary for management. However, according to the present invention, while satisfying control requirements, management figures can be grasped early due to missed or delayed approvals. [Brief explanation of the drawings]

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

[0021] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the accompanying drawings. However, the present invention is not limited to this embodiment.

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

[0023] 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. Since the depreciation calculation results for fixed asset data change depending on the transfer event, it is necessary to apply chronological processing control, and there is a demand for control to prevent the registration of other transfer data for assets that are currently being approved. There is also a demand for the ability to check the results of data currently being approved, in order to obtain preliminary depreciation calculation results for assets that are currently being approved.

[0024] 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® for reporting early accounting and on-site control, resulting in missed accounting, delayed approvals, and missed controls.

[0025] As a result, particularly in companies that have traditionally managed assets in field departments, operations have become complicated by processing approvals outside the system, and control requirements have not been met. System implementation has been delayed due to missed or delayed approvals, making it difficult to obtain the figures necessary for management.

[0026] Therefore, in this embodiment, 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 the data, a mechanism is provided in which, when a fixed asset change is registered, depreciation calculations are performed and the calculation results after the change (e.g., for 24 months) are retained, and whether or not there is data under approval is checked, the registration of the change data is controlled, data output before and after approval is controlled, and report output before and after approval is implemented.

[0027] Here, in the data management of this embodiment, as in the fixed asset ledger registration shown in Figure 1 and the transfer registration shown in Figure 2, a pre-approval table (a table for approval) and a post-approval table (a table in which data for which approval has been completed is updated) are each maintained in the same system, and the pre-approval table is updated at the time of registration, and the post-approval table is updated when final approval is completed.

[0028] 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. In addition, in this embodiment, as data output before and after approval, a depreciation calculation is performed when the transfer is registered, the data is updated and stored in the pre-approval table, and when outputting a report, it is controlled whether to include pre-approval data or not, or to output only unapproved data.

[0029] In addition, the transfer events (reason for transfer) that are subject to approval in this embodiment may be "acquisition": purchase of an asset, "transfer": transfer of the location of an asset, "disposal": disposal or sale of an asset, "division": division of an asset that had multiple assets 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 and useful life due to change in use of the asset, etc., or "change in asset type": change in asset type due to change in use of the asset, etc.

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

[0031] 3, the fixed asset transfer control device 100 is a commercially available desktop personal computer. 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.

[0032] 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 as to be able to communicate with each other via any communication path.

[0033] The communication interface unit 104 communicably connects the fixed asset transfer control device 100 to a 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 a communication line. Here, the network 300 has a 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).

[0034] 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 cooperates with a mouse to achieve a pointing device function. In the following, 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.

[0035] The storage unit 106 stores various databases, tables, files, etc. The storage unit 106 stores computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes. The storage unit 106 may be, 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, or an optical disk. The storage unit 106 includes an approval database 106a and a post-approval database 106b.

[0036] The approval database 106a stores approval data. Here, the approval database 106a may store approval history data that is set in association with the reasons for transfer of 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.

[0037] An example of approval history data in this embodiment will now be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of approval history data in this embodiment.

[0038] As shown in Figure 4, the approval history data in this embodiment is a table that manages the approval status of all transfer events, and 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.

[0039] Returning to FIG. 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.

[0040] The control unit 102 is a CPU or the like that performs overall control of the fixed asset transfer control 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. Functionally, the control unit 102 conceptually includes 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.

[0041] The transfer request acquisition unit 102a acquires transfer request data for the target fixed asset to be transferred. Here, the transfer request acquisition unit 102a may acquire transfer request data that sets the target transfer reason for the target fixed asset to be transferred. In addition, the target transfer reason may be acquisition, transfer, division, impairment, suspension, or change, etc.

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

[0043] The transfer restriction unit 102c controls transfer requests for the target fixed asset based on the transfer request data. Here, when 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, when 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, when 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 disallow all transfer requests for the target fixed asset based on the transfer request data. Furthermore, 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. Furthermore, 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 the transfer request for the target fixed asset based on the transfer request data. Furthermore, the transfer restriction unit 102c may display a message corresponding to the restrictions on the transfer request 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, which is the acquisition of the target fixed asset, is set, and new approval history data in which the approval status for the change reason, which is the transfer of the target fixed asset, is set in the approval database 106a.

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

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

[0046] 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, the approval history data, and the post-approval history data. Furthermore, when a reflection unit that allows selection of an asset type unit or an 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 each asset type or each asset of fixed assets based on the selected reflection unit, the selected approval status reflection category, the approval history data, and the post-approval history data.

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

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

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

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

[0051] Then, 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 the processing to step SA-3.

[0052] Then, the transfer restriction unit 102c restricts the transfer request for the target fixed asset based on the transfer request data (step SA-3), and moves the process to step SA-5.

[0053] 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 processing to step SA-4.

[0054] Then, the transfer restriction unit 102c permits the transfer request for the target fixed asset based on the transfer request data (step SA-4), and moves the process to step SA-5.

[0055] 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).

[0056] 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 the processing.

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

[0058] As shown in Figure 6, in this embodiment, when a change in a fixed asset occurs, the user calls up the target fixed asset that is the subject of the change on the change registration screen (step SB-1), and it is determined whether the target fixed asset is a fixed asset that is currently being approved (step SB-2).

[0059] In this embodiment, if it is determined that the target fixed asset is not a fixed asset under approval (step SB-2: No), processing proceeds to step SB-11, and if it is determined that the target fixed asset is a fixed asset 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).

[0060] In this embodiment, if it is determined that the reason for the target change of the target fixed asset is not a split (step SB-3: No), processing proceeds to step SB-7, and if it is determined that the 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).

[0061] 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, and if it is determined that the target fixed asset has multiple system history numbers (step SB-4: Yes), it is determined whether there is a target fixed asset with a transfer reason of "transfer" within the same system history number (step SB-5).

[0062] 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, and 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).

[0063] In this embodiment, if it is determined that there is no fixed asset subject to the transfer reason "disposal" within the same system history number (step SB-6: No), processing proceeds to step SB-10, and if it is determined that there is a fixed asset subject to the transfer reason "disposal" 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).

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

[0065] In this embodiment, if it is determined that the approval status of the fixed asset under approval does not correspond to any of "Application", "Rejection", or "Withdrawal" (step SB-8: No), processing proceeds to step SB-10, and if it is determined that the approval status of the fixed asset under approval corresponds to any of "Application", "Rejection", or "Withdrawal" (step SB-8: Yes), it is determined whether the processing mode (update category) is "Modification" (step SB-9).

[0066] In this embodiment, if it is determined that the processing mode (update classification) is "correction" (step SB-9: Yes), the processing proceeds to step SB-11, and if it is determined that the processing mode (update classification) is not "correction" (step SB-9: No), the request for change of the target fixed asset is restricted, the approval data cannot be called up (step SB-10), and the processing ends.

[0067] On the other hand, 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 the processing ends.

[0068] An example of data update processing in this embodiment will be described with reference to Fig. 7 to Fig. 18. Fig. 7 to Fig. 18 are diagrams showing an example of data update processing in this embodiment.

[0069] As shown in Figure 7, in the "acquisition" data update process for "new" in this embodiment, 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.

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

[0071] Furthermore, as shown in FIG. 9, in the "acquisition" data update process at the time of "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.

[0072] Furthermore, as shown in FIG. 10, in the "movement" data update process at the time of "modification" 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.

[0073] Furthermore, as shown in FIG. 11, in the "acquisition" data update process at the time of "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.

[0074] Also, as shown in Figure 12, in the "movement" data update process at the time of "deletion" 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.

[0075] As shown in FIG. 13, in the approval status update process in this embodiment, approval data is registered at the time of fixed asset registration application, the approval data is updated at the time of interim approval, and when approval is completed, the approval data is deleted and post-approval data is registered.

[0076] Also, as shown in Figure 14, if the approver notices a registration error or the like and returns the application 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.

[0077] Also, as shown in Figure 15, if the applicant realizes that they have made a registration error and wants to withdraw 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.

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

[0079] As shown in FIG. 18, in this embodiment, at the time of each change registration, the presence or absence of data in the target fixed asset that is currently being approved is determined and controlled in the "history data_data for approval" table (history data for approval).

[0080] An example of form output processing in this embodiment will be described with reference to Fig. 19 to Fig. 27. Fig. 19 to Fig. 22, Fig. 24, and Fig. 25 are diagrams showing an example of form output processing in this embodiment. Fig. 23 is a diagram showing an example of approval data and post-approval data in this embodiment. Fig. 26 and Fig. 27 are diagrams showing an example of a form in this embodiment.

[0081] 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 in accordance with the criteria of "final approval completed only," "reflects data before final approval completion," or "unapproved only," allowing the ledger to reflect the contents of the transfers currently being approved, printing out the reason for the transfers currently being approved, and determining whether or not data exists in the "history data_approval data" table, allowing only the unapproved portions to be output. Figure 19 shows the fixed asset ledger ledger data output when a new fixed asset is registered in this embodiment, Figure 20 shows the fixed asset ledger ledger data output when a fixed asset is amended in this embodiment, and Figure 21 shows the fixed asset ledger ledger data output when a transfer is registered in this embodiment.

[0082] In this embodiment, the list can reflect the contents before and during approval, and the presence or absence of data in the "History Data_Approval Data" table is checked to determine whether the form is reflected, and the details of the approval are printed so that they can be seen. Figure 22 shows the form data of the transfer list that is output when registering a transfer in this embodiment.

[0083] In this embodiment, the depreciation expense table, which confirms the depreciation calculation results when a change is registered based on the approval data and post-approval data shown in FIG. 23, is output based on the following criteria: "Final approval only," "Reflects data before final approval," or "Unapproved only." The depreciation expense table can reflect both pre-approval and pending approval data. The presence or absence of data in the "Historical Data_Approval Data" table determines whether the report is reflected. When printing each fixed asset, the reason for the change is printed to indicate which fixed assets are currently being approved. In this embodiment, if the user selects asset type as the reflection unit on the fixed asset ledger screen shown in FIG. 24, the depreciation expense table is printed as shown in FIG. 25. In this embodiment, if the user selects asset type as the reflection unit on the fixed asset ledger screen shown in FIG. 26, the depreciation expense table is printed as shown in FIG. 27.

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

[0085] In this embodiment, as shown in Figure 28, when a fixed asset consisting of a set of machines A and B is divided from department A to department B, as this is a partial transfer, as shown in the transfer registration screen in Figure 29, the asset is transferred to department B, which is the division destination of machine B, and an asset number for the division destination is automatically assigned.

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

[0087] 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 transfer reason classification: "7: Split", and there are multiple system history numbers, and the transfer reason classification within the same system history number is "3: Transfer", it is determined to be a partial transfer process, and only corrections are permitted, and other registrations are prevented. 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 transfer reason classification: "1: Acquisition" or "3: Transfer", multiple approval data exist, and therefore all registrations are prevented. Also, as shown in Figure 32, in this embodiment, when a ledger registration call is made for asset number: "N001" of pattern (3), if the "History Data_Approval Data" table contains data for transfer reason classification: "7: Split", and there are multiple system history numbers, and the transfer reason classification within the same system history number is "3: Transfer", it is determined to be a partial transfer process and control is exercised to prevent all registrations. Also, as shown in Figure 32, in this embodiment, when a ledger registration call is made for asset number: "N002", if the "History Data_Approval Data" table contains data for transfer reason classification: "1: Acquisition" or "3: Transfer", multiple approval data exist, and control is exercised to prevent all registrations.

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

[0089] Furthermore, this embodiment can contribute to reducing waste and promoting paperless and electronic systems, thereby contributing to the achievement of SDGs Goals 12, 13, and 15.

[0090] Furthermore, this embodiment can contribute to strengthening control and governance, which can contribute to Goal 16 of the SDGs.

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

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

[0093] Furthermore, the processing procedures, control procedures, specific names, information including parameters such as registered data and search conditions for each process, screen examples, and database configurations shown in this specification and drawings can be changed as desired unless otherwise specified.

[0094] Furthermore, with regard to the fixed asset transfer control device 100, the components shown in the figures are functional concepts, and do not necessarily have to be physically configured as shown in the figures.

[0095] For example, all or any part of the processing functions of the fixed asset transfer control device 100, particularly those performed by the control unit 102, may be implemented by a CPU and a program interpreted and executed by the CPU, or by hardware using wired logic. The program is stored 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. That is, a computer program is stored in a storage unit such as a ROM or HDD (Hard Disk Drive) for working with the OS to issue instructions to the CPU and perform various processes. The computer program is executed by being loaded into RAM and cooperates with the CPU to form the control unit.

[0096] In addition, this computer program may be stored in 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.

[0097] Furthermore, the program for executing the processes described in this embodiment may be stored in a non-transitory computer-readable recording medium or configured as a program product. Here, the term "recording medium" includes any "portable physical medium" such as a memory card, a Universal Serial Bus (USB) memory, a Secure Digital (SD) card, a flexible disk, a magneto-optical disk, a ROM, an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable and Programmable Read Only Memory (EEPROM (registered trademark)), a Compact Disk Read Only Memory (CD-ROM), a Magneto-Optical disk (MO), a Digital Versatile Disk (DVD), and a Blu-ray (registered trademark) disc.

[0098] Furthermore, a "program" is a data processing method written in any language or description method, and does not matter whether it is in the form of source code or binary code. Note that a "program" is not necessarily limited to a single structure, but also includes a structure that is distributed as multiple modules or libraries, or a structure that achieves its function by cooperating with a separate program, such as an OS. Note that the specific configuration 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 configurations and procedures.

[0099] The various databases stored in the memory unit 106 are storage means 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 providing websites.

[0100] The fixed asset transfer control 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 fixed asset transfer control device 100 may also be realized by installing software (including programs, data, etc.) that causes the device to perform the processing described in this embodiment.

[0101] Furthermore, the specific form of distribution and integration of the devices is not limited to that shown in the drawings, and all or part of them can be configured by functionally or physically distributing and integrating them in any unit depending on various additions or functional loads. In other words, the above-described embodiments can be implemented in any combination, or embodiments can be implemented selectively. [Industrial Applicability]

[0102] The present invention is useful in industries such as manufacturing, retail, or finance. [Explanation of symbols]

[0103] 100 Fixed asset transfer control device 102 Control section 102a Transfer request acquisition department 102b Approval status determination unit 102c Transfer Restrictions Department 102d Update Department 102e Approval Completion Section 102f Report output section 104 Communication interface unit 106 Storage section 106a Approval Database 106b Post-approval database 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. 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:

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

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

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

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

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

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

8. 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:

9. 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:

10. 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:

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

12. 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:

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

Images