Business support apparatus, business support method, and business support program

Abstract

To provide a business support apparatus or the like capable of reducing a creation load of an approval route of movement of an asset.SOLUTION: In the present embodiment, a business support method includes: specifying a movement destination approver who is an approver in charge of approval in a movement destination department by referring to department master data and affiliation master data based on asset movement application information including a movement destination department input from an applicant; creating approver master data for each applicant including a movement destination approver specifying information column that stores information for specifying the movement destination approver; and creating workflow data for performing a workflow of approval based on the approver master data for each applicant.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to a business support device, a business support method, and a business support program. [Background technology]

[0002] After acquiring a fixed asset, a company, organization, etc. may transfer the asset to another location or department. Transferring a fixed asset to another location may involve transferring a department (for example, transferring the first manufacturing department in the first building to the third manufacturing department in the third building), or it may not involve transferring a department (for example, transferring the personnel of the first manufacturing department to a different building).

[0003] When a fixed asset is transferred between departments, a transfer of depreciation expenses occurs, so the second department needs to know and confirm in advance what fixed asset will be transferred and when. Also, when registering the transfer of a fixed asset in the fixed asset management system, there is a requirement to separate the approval route depending on the organization to which the asset will be transferred.

[0004] Patent Document 1 discloses an asset management data creation device that is less likely to cause management errors even when assets are transferred between two organizations. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Publication No. 2019-61391 Summary of the Invention [Problem to be solved by the invention]

[0006] Consider a case where you are trying to set up a fixed asset management system in which the approval route for the transfer of fixed assets is branched by the destination department. In this case, when creating an approval route for fixed asset transfers, it is necessary to create branches for each department in the entire organization (potential destination departments). For companies with many departments or that undergo frequent organizational changes, the burden of creating approval routes becomes extremely heavy.

[0007] Consider a case in which an applicant (fixed asset manager) from the first department, from which a fixed asset is to be transferred, attempts to add an approver (fixed asset manager) from the second department, to which the fixed asset is to be transferred, at the time of application in a fixed asset management system. In this case, the fixed asset manager from the first department and the fixed asset manager from the second department often communicate with each other in advance. Therefore, the fixed asset manager from the first department often knows the fixed asset manager from the second department, but may not know the manager's superior (fixed asset manager). In this case, the fixed asset manager from the first department cannot select and add the fixed asset manager from the second department to the approval route.

[0008] The present invention has been made in view of the above, and aims to provide a business support device, a business support method, and a business support program that can reduce the burden of creating an approval route for asset transfers. [Means for solving the problem]

[0009] In order to solve the above-mentioned problems and achieve the object, a business support device according to the present invention is a business support device having a control unit that supports approval work when assets of a transfer source department are transferred to a transfer destination department, and includes department master data including organizational chart information related to the application and approval of asset transfers, affiliation master data including a department code column that stores information identifying positions in each department of the organization that are responsible for application or approval of asset transfers, and a person information column that stores information identifying people assigned to positions that are responsible for application or approval, and a plurality of records that correspond to a plurality of approval stages, and a record among the plurality of records that corresponds to an approval stage in the transfer destination department that stores positions that are responsible for approval at the transfer destination. and stage approval master data in which temporary approver information representing a temporary approver is stored in a temporary approver information column corresponding to the temporary approver information stored in the temporary approver information column, and the control unit is capable of accessing ...

[0010] In addition, in the business support device of the present invention, the asset transfer application information includes information identifying a first destination approval position that will be first responsible for approval in the destination department, and the destination approver identification processing means may identify a first destination approver who is a person assigned to the first destination approval position by referring to the affiliation master data using the information identifying the first destination approval position as a key, obtain information identifying a second destination approval position that will next be responsible for approval in the destination department by referring to the department master data using the information identifying the first destination approval position as a key, and identify a second destination approver who is a person assigned to the second destination approval position by referring to the affiliation master data using the information identifying the second destination approval position as a key.

[0011] In the business support device according to the present invention, the control unit may further comprise an approval route maintenance processing means for displaying an approval route maintenance screen for inputting information relating to a plurality of approval stages, and for creating the stage approval master data including records corresponding to approval stages in the source department, records corresponding to approval stages in the destination department, and records corresponding to approval stages in the final approving department, based on the information inputted on the approval route maintenance screen.

[0012] In addition, in the business support device of the present invention, the control unit may further include an organization / department affiliation maintenance processing means that displays an organization / department affiliation maintenance screen that includes an organizational chart regarding applications and approvals for asset transfers based on the department master data and input fields for inputting information to be stored in the affiliation master data, and creates the affiliation master data based on the information input in the input fields.

[0013] In addition, in the business support device according to the present invention, the control unit may further comprise an approval route identification processing means for creating preparatory work data including the same number of records in the stage approval master data as the number of records corresponding to the approval stages in the destination department, and including an approver column by applicant storing temporary approver information, and a destination approver identification information column for storing information identifying the destination approver, and the destination approver identification processing means may store the identified destination approver in the destination approver identification information column of the preparatory work data, and create the applicant-specific approver master data based on the preparatory work data.

[0014] Furthermore, a business support method according to the present invention is a business support method executed by a business support device having a control unit that supports approval work when assets from a transfer source department are transferred to a transfer destination department, and the business support device includes department master data including organizational chart information related to asset transfer applications and approvals, affiliation master data including a department code column that stores information identifying positions in each department of the organization that are responsible for asset transfer applications or approvals, and a person information column that stores information identifying people assigned to positions that are responsible for application or approvals, and a plurality of records that correspond to a plurality of approval stages, and stores positions that are responsible for approval at the transfer destination among the records that correspond to the approval stages in the transfer destination department. a destination approver identification step that is accessible to the stage approval master data in which temporary approver information representing a temporary approver is stored in a temporary approver information column that is accessed by the control unit, and that identifies a destination approver who is an approver who will be responsible for approval in the destination department by referring to the department master data and the affiliation master data based on asset transfer application information including the destination department input by the applicant, and creates applicant-specific approver master data that includes a destination approver identification information column that stores information that identifies the destination approver; and a workflow data creation step that creates workflow data for performing an approval workflow based on the applicant-specific approver master data.

[0015] Furthermore, a business support program according to the present invention is a business support program to be executed by a business support device having a control unit that supports approval work when assets of a transfer source department are transferred to a transfer destination department, and the business support device includes department master data including organizational chart information related to the application and approval of asset transfers, affiliation master data including a department code column that stores information identifying positions in each department of the organization that are responsible for application or approval of asset transfers, and a person information column that stores information identifying people assigned to positions that are responsible for application or approval, and a plurality of records that correspond to a plurality of approval stages, and a position that is responsible for approval at the transfer destination among the records that correspond to the approval stage in the transfer destination department among the plurality of records. the stage approval master data in which temporary approver information representing a temporary approver is stored in a temporary approver information column that is accessible to the stage approval master data, and which is executed by the control unit, by referring to the department master data and the affiliation master data, based on asset transfer application information including the destination department input by the applicant, to identify a destination approver who is an approver responsible for approval in the destination department, and create applicant-specific approver master data including a destination approver identification information column that stores information that identifies the destination approver; and a workflow data creation step that creates workflow data for performing an approval workflow based on the applicant-specific approver master data. [Effects of the Invention]

[0016] The present invention has the effect of reducing the burden of creating an approval route for asset transfer. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a business support device according to this embodiment. [Figure 2] FIG. 2 is a diagram showing an example of an organization / department / affiliation maintenance screen MA, a department master 106a, an employee master 106b, and an employee affiliation master 106c. [Figure 3]FIG. 3 is a diagram showing an example of the approval route maintenance screen MB, the approval route master 106d, and the stage approval master 106e. [Figure 4] FIG. 4 is a diagram showing an example of the approval route allocation maintenance screen MC, the department master 106a, the approval route master 106d, the approval route allocation master 106f, and the approver master for each applicant 106g. [Figure 5] FIG. 5 is a diagram showing an example of the fixed asset control master maintenance screen MD and the fixed asset control master 106h. [Figure 6] FIG. 6 is a diagram showing an example of the movement registration screen ME, the business data 106i, and the approver update preparation work 106n for each applicant. [Figure 7] FIG. 7 shows an example of the destination approver selection screen MF, the applicant-specific approver update preparation work 106n, the applicant-specific approver master 106g, the workflow data 106o, and the applicant-specific approver master 106g. [Figure 8] FIG. 8 is a diagram showing an example of the approval workflow, the workflow data 106o, and the business data 106i. [Figure 9] FIG. 9 is a diagram showing an example of the approval workflow, the workflow data 106o, and the business data 106i. [Figure 10] FIG. 10 is a diagram showing an example of the approval workflow, workflow data 106o, and business data 106i. [Figure 11] FIG. 11 is a diagram showing an example of the approval workflow, workflow data 106o, and business data 106i. [Figure 12] FIG. 12 is a diagram showing an example of the approval workflow, the workflow data 106o, and the business data 106i. DETAILED DESCRIPTION OF THE INVENTION

[0018] In the embodiment, the term "department" does not refer to a division or section of a company or organization (e.g., XX department, △△ section, □□ section), but rather to a human position responsible for applying for or approving asset transfers. An employee assigned to a position responsible for applying for asset transfers, etc. may be referred to as an "applicant." An employee assigned to a position responsible for approving asset transfers, etc. may be referred to as an "approver." A division or section of a company or organization (e.g., XX department, △△ section, □□ section) may be referred to as a "department."

[0019] In the embodiments, the case where the transfer object between departments is a fixed asset will be mainly described, but the present disclosure is not limited to this. The transfer object may be a current asset or a human asset. In other words, the present invention is also applicable to personnel transfers. In the embodiments, the transfer object may be collectively referred to as an "asset."

[0020] In the embodiments, the transfer of assets between departments will be mainly described as an example, but the present disclosure is not limited thereto. The embodiments can also be applied to the acquisition or disposal of assets. The acquisition, transfer, or disposal of assets may be collectively referred to as "transfer, etc."

[0021] In the embodiment, a case where assets of the first manufacturing department are transferred to the third manufacturing department will be mainly described as an example. In the embodiment, the person who makes the final approval of the transfer of assets is an employee of the accounting department.

[0022] In the embodiment, "creation" of each data item includes "updating" the data item.

[0023] The premise of the above-described embodiment is an example, and the present disclosure is not limited to this.

[0024] [1. Configuration] An example of the configuration of a task assistance device 100 according to this embodiment (including the task assistance device of the present invention) will be described with reference to Fig. 1 etc. Fig. 1 is a block diagram showing an example of the configuration of the task assistance device 100.

[0025] The business support device 100 is constructed based on a commercially available desktop personal computer. Note that the business support device 100 is not limited to being constructed based on a stationary business support device such as a desktop personal computer, but may also be constructed based on a portable business support device such as a commercially available notebook personal computer, PDA (Personal Digital Assistant), smartphone, or tablet personal computer.

[0026] The business assistance device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input / output interface unit 108. The units included in the business assistance device 100 are connected to each other so as to be able to communicate with each other via any communication path.

[0027] The communication interface unit 104 communicably connects the business assistance device 100 to the network 300 via a communication device such as a router and a wired or wireless communication line such as a dedicated line. The communication interface unit 104 has a function of communicating data with other devices via the communication line. Here, the network 300 has a function of connecting the business assistance 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). Note that the data stored in the memory unit 106 may be stored in the server 200, for example.

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

[0029] Various databases, tables, files, etc. are stored in the storage unit 106. Computer programs that work in conjunction with an OS (Operating System) to issue commands to a CPU (Central Processing Unit) to perform various processes are recorded in the storage unit 106. The storage unit 106 can 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, an optical disk, etc.

[0030] The memory unit 106 stores a department master 106a (corresponding to the department master data of the present invention), an employee master 106b, an employee affiliation master 106c (corresponding to the affiliation master data of the present invention), an approval route master 106d, a stage approval master 106e (corresponding to the stage approval master data of the present invention), an approval route allocation master 106f, an applicant-specific approver master 106g (corresponding to the applicant-specific approver master data of the present invention), a fixed asset control master 106h, business data 106i, an applicant-specific approver update preparation work 106n (corresponding to the preparation work data of the present invention), and workflow data 106o (corresponding to the workflow data of the present invention).

[0031] The business data 106i includes movement information data_approval 106j, history information data_approval 106k, movement information data 106l, and history information data 106m. The workflow data 106o includes case data 106p and case stage data 106q.

[0032] 2 and 4 show examples of information stored in the department master 106a. The department master 106a is used to manage the structure of departments related to applications and approvals for asset transfers, etc. (organizational chart related to applications and approvals).

[0033] As shown in Figures 2 and 4, the department master 106a stores an organization CD, which is an identifier that uniquely identifies an organization; a department CD, which is an identifier that uniquely identifies a position (department responsible for application or approval) that is responsible for application or approval of asset transfers, etc.; a division name, which is the name of a position that is responsible for application or approval of asset transfers, etc.; and a parent department CD, which is an identifier that uniquely identifies a parent position (a higher-level position related to application or approval) of a position that is responsible for application or approval of asset transfers, etc.

[0034] In the example of the department master 106a shown in Figures 2 and 4, the department CD of the first manufacturing department (manager) is "S11000", and the parent department CD is "NULL". Also, the department CD of the first manufacturing department (person in charge) is "S11100", and the parent department CD is "S11000". Therefore, in terms of the organization related to application and approval, the parent department of the first manufacturing department (person in charge) is the first manufacturing department (manager), and the first manufacturing department (manager) does not have a parent department.

[0035] 2 and 4, the department CD of the third manufacturing department (manager) is "S13000" and the parent department CD is "NULL." The department CD of the third manufacturing department (person in charge) is "S13100" and the parent department CD is "S13000." Therefore, in terms of the organization related to application and approval, the parent department of the third manufacturing department (person in charge) is the third manufacturing department (manager), and there is no parent department of the third manufacturing department (manager).

[0036] 2 and 4, the department CD of the accounting department is “S19900,” and the parent department CD is “NULL.” Therefore, in the organization related to application and approval, the accounting department does not have a parent department.

[0037] In this embodiment, the approval hierarchy for one department is two levels (a person in charge and a manager) in the department master 106a shown in Fig. 2, but the present disclosure is not limited to this. The approval hierarchy for one department may be three levels or more (for example, a person in charge, an intermediate manager, and a higher manager).

[0038] An example of information stored in the employee master 106b is shown in Figure 2. The employee master 106b is used to manage employees. As shown in Figure 2, the employee master 106b stores an employee CD, which is an identifier that uniquely identifies an employee, and an employee name, which is the name of the employee.

[0039] In the example of employee master 106b shown in Figure 2, Mr. A's employee CD is "U00001", Mr. B's employee CD is "U00002", Mr. E's employee CD is "U00005", Mr. F's employee CD is "U00006", and Mr. K's employee CD is "U00099".

[0040] An example of information stored in the employee affiliation master 106c is shown in Fig. 2. The employee affiliation master 106c is used to manage employees (employees who make applications or approvals) assigned to positions responsible for applying for or approving asset transfers, etc. As shown in Fig. 2, the employee affiliation master 106c stores organization CD, department CD (department code column of the present invention), and employee CD (person code column of the present invention).

[0041] In the example of the employee affiliation master 106c shown in FIG. 2, referring to the record 106ca, an employee CD "U00002" (Mr. B in this embodiment) is assigned to the department CD "S11100".

[0042] The creation of the employee department master 106c will be explained later in [2. Specific example of processing].

[0043] 3 and 4 show an example of information stored in the approval route master 106d. The approval route master 106d is used to manage the types of approval reasons for asset transfers, etc. (for example, approval for asset acquisition, approval for asset transfers, approval for asset disposal). As shown in FIGS. 3 and 4, the approval route master 106d stores a route CD, which is an identifier that uniquely identifies the type of approval reason for asset transfers, etc., and a route name, which is the name of the type of approval reason for asset transfers, etc.

[0044] In the example of the approval route master 106d shown in Figures 3 and 4, the route name corresponding to the route CD "N001" is "Acquisition Approval", the route name corresponding to the route CD "N002" is "Movement Approval", and the route name corresponding to the route CD "N003" is "Removal Approval".

[0045] An example of information stored in the stage approval master 106e is shown in Fig. 3. The stage approval master 106e is used to manage stages (approval stages) of an approval workflow for asset transfers and the like.

[0046] As shown in FIG. 3, the stage approval master 106e stores a route CD, a stage CD that uniquely identifies the stage of the approval workflow, a stage type that indicates the type of department corresponding to each stage, an organization CD, a department CD, an approver frame CD for each applicant (corresponding to the provisional approver information column of the present invention) that is an identifier that uniquely identifies the provisional approver (to be determined in later processing) to whom the asset will be transferred, and a final flag that indicates whether or not it is the final stage of the approval workflow.

[0047] As described above, in the embodiment, the position (final approval department) responsible for final approval in the approval workflow is the accounting department (department CD is "S19900"). That is, in the stage approval master 106e, only the final flag of the row (record) where the department CD is "S19900" is "TRUE", and the final flags of the other rows (records) are "FALSE".

[0048] The creation of the stage approval master 106e will be explained later in [2. Specific example of processing].

[0049] An example of information stored in the approval route allocation master 106f is shown in Figure 4. The approval route allocation master 106f is used to manage approval routes that can be applied for by positions (departments responsible for application or approval) that are responsible for application or approval of asset transfers, etc.

[0050] As shown in FIG. 4, the approval route allocation master 106f stores an organization CD, a department CD, an application type CD that uniquely identifies the type of approval that can be applied for (for example, asset acquisition, asset transfer, asset disposal), and a route CD.

[0051] The creation of the approval route allocation master 106f will be explained later in [2. Specific example of processing].

[0052] 4 and 7 show examples of information stored in the applicant-specific approver master 106g. The applicant-specific approver master 106g is used to manage the allocation of employees to the applicant-specific approver slots described above.

[0053] As shown in Figures 4 and 7, the applicant-specific approver master 106g stores the applicant organization CD (same value as organization CD in the embodiment), which is an identifier that uniquely identifies the applicant's organization from which the assets are to be transferred, the applicant-specific approver, who is the temporary approver to which the assets are to be transferred (determined in later processing), the applicant department CD, which is the department CD of the position that made the application (the department that made the application), the applicant employee CD, which is the employee CD of the applicant, the approver organization CD (same value as organization CD in the embodiment), which is an identifier that uniquely identifies the approver's organization, the approver department CD, which is the department CD of the position that gives approval (the department that gives approval), and the approver employee CD, which is the employee CD of the employee assigned to the position that gives approval (the department that gives approval) (the destination approver identification information column of the present invention).

[0054] The creation of the applicant-specific approver master 106g will be explained later in [2. Specific example of processing].

[0055] 5 shows an example of information stored in the fixed asset control master 106h (106h-1, 106h-2). The fixed asset control master 106h is used to manage whether approval is required for the acquisition, transfer, or disposal of fixed assets.

[0056] As shown in Figure 5, the fixed asset control master 106h stores an acquisition approval operation category indicating whether approval is required for the acquisition of an asset, a transfer approval operation category indicating whether approval is required for the transfer of an asset, a removal approval operation category indicating whether approval is required for the removal of an asset, and a transfer destination approval organization CD, which is an identifier indicating whether approval is required for the transfer destination of the asset.

[0057] The acquisition approval operation category of the fixed asset control master 106h stores "0: required" if approval is required for asset acquisition, and stores "1: not required" if approval is not required for asset acquisition. The transfer approval operation category of the fixed asset control master 106h stores "0: required" if approval is required for asset transfer between departments, and stores "1: not required" if approval is not required for asset transfer between departments. The disposal approval operation category of the fixed asset control master 106h stores "0: required" if approval is required for asset disposal, and stores "1: not required" if approval is not required for asset disposal. The destination disposal approval organization CD of the fixed asset control master 106h stores an organization CD (in the embodiment, "Sosiki01") if destination disposal approval is required for asset transfer between departments, and stores "NULL" if destination disposal approval is not required for asset transfer between departments.

[0058] Note that transfer of assets between departments requires approval of the transfer destination only when the transfer approval operation category is "1: Required" and the transfer destination approval organization CD is not "NULL" (in the embodiment, this is the case for "Sosiki01"). In other cases, transfer of assets between departments does not require approval of the transfer destination.

[0059] 5, the fixed asset control master 106h-1 indicates that the transfer of assets between departments requires approval of the transfer destination, while the fixed asset control master 106h-2 indicates that the transfer of assets between departments does not require approval of the transfer destination.

[0060] The creation of the fixed asset control master 106h will be explained later in [2. Specific example of processing].

[0061] 6, 8, 9, 10, 11, and 12 show examples of information stored in the Movement Information Data_Approval 106j. The Movement Information Data_Approval 106j is used to manage data entered for applications for asset transfers between departments.

[0062] As shown in FIGS. 6, 8, 9, 10, 11, and 12, the transfer information data_approval 106j stores an asset number, which is an identifier that uniquely identifies an asset, the asset transfer date, the asset transfer origination accounting department, and the asset transfer destination accounting department.

[0063] The creation of the movement information data_approval 106j will be explained later in [2. Specific example of processing].

[0064] 6, 8, 9, 10, 11, and 12 show examples of information stored in the history information data_approval 106k. The history information data_approval 106k is used to manage data entered for applications for asset transfer between departments.

[0065] As shown in Figures 6, 8, 9, 10, 11, and 12, the history information data_approval 106k stores the asset number, the reason for asset approval (in the embodiment, "3 (movement)"), the approval status classification indicating the approval status (stage), and the case Guid, which is an identifier that uniquely identifies the asset transfer case.

[0066] The creation of the history information data_approval 106k will be explained later in [2. Specific example of processing].

[0067] 6, 8, 9, 10, 11, and 12 show examples of information stored in the movement information data 1061. The movement information data 1061 is used to manage the registration results of asset movement between departments.

[0068] The transfer information data 106l stores the asset number, the transfer date, the transfer source accounting department, and the transfer destination accounting department, as shown in FIGS.

[0069] The creation of the movement information data 106l will be explained later in [2. Specific example of processing].

[0070] 6, 8, 9, 10, 11, and 12 show examples of information stored in the history information data 106m. The history information data 106m is used to manage the registration results of asset transfers between departments.

[0071] As shown in FIGS. 6, 8, 9, 10, 11, and 12, the history information data 106m stores the asset number and the reason for asset registration (in this embodiment, "3 (movement)").

[0072] The creation of the history information data 106m will be explained later in [2. Specific example of processing].

[0073] The movement information data_approval 106j is work data temporarily used in each process described later, and the movement information data 106l is actual data that has already been processed. Similarly, the history information data_approval 106k is work data for approval temporarily used in each process described later, and the history information data 106m is actual data that has already been processed.

[0074] The movement information data 106l and history information data 106m, which are actual data, may be used in a company-wide management system or an accounting system.

[0075] 6 and 7 show examples of information stored in the applicant-specific approver update preparation work 106n. The applicant-specific approver update preparation work 106n is used to manage cases where approval of the asset transfer destination is required.

[0076] As shown in Figures 6 and 7, the applicant-specific approver update preparation work 106n stores the applicant organization CD (in the embodiment, "Sosiki01"), a hierarchy CD that uniquely identifies the organizational hierarchy of the position responsible for approving the asset transfer, the applicant-specific approver, which is information on the temporary transfer destination approver, the applicant department CD, the applicant employee CD, the approver organization CD, the approver department CD, and the approver employee CD.

[0077] The creation of the approver update preparation work 106n for each applicant will be explained later in [2. Specific example of processing].

[0078] 7, 8, 9, 10, 11, and 12 show examples of information stored in the project data 106p. The project data 106p is used to manage the workflow of application and approval for asset transfer between departments.

[0079] As shown in FIGS. 7, 8, 9, 10, 11, and 12, the case data 106p stores case Guid, application type CD, approval status classification, and stage CD.

[0080] The creation of the case data 106p will be explained later in [2. Specific example of processing].

[0081] 7, 8, 9, 10, 11, and 12 show examples of information stored in the case stage data 106q. The case stage data 106q is used to manage approval stages in the workflow of application and approval for asset transfer between departments.

[0082] As shown in Figures 7, 8, 9, 10, 11, and 12, the case data 106p stores SEQ, which is an identifier that uniquely identifies the workflow sequence, case Guid, stage order indicating the order of the workflow stages, organization CD, department CD, final flag, approver employee CD, which is the employee CD of the approver, and completion flag indicating whether the application or approval stage has been completed.

[0083] The creation of the case stage data 106q will be explained later in [2. Specific Example of Processing].

[0084] 1, the control unit 102 is a CPU or the like that performs overall control of the business support 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 business support operations based on these stored programs.

[0085] The control unit 102 conceptually includes a maintenance processing unit 102a, an application approval processing unit 102f, and the like.

[0086] The maintenance processing unit 102a mainly performs maintenance processing of each master data, etc. The maintenance processing unit 102a receives input from a maintenance person in charge of maintaining the master data and performs processing, for example, but the present disclosure is not limited to this.

[0087] The application approval processing unit 102f mainly performs workflow processing of applications and approvals for asset transfers, etc. The application approval processing unit 102f is exemplified as accepting inputs from applicants and approvers and performing processing, but the present disclosure is not limited to this.

[0088] The maintenance processing unit 102a includes an organization / department affiliation maintenance processing unit 102b (corresponding to the organization / department affiliation maintenance processing means of the present invention), an approval route maintenance processing unit 102c (corresponding to the approval route maintenance processing means of the present invention), an approval route allocation maintenance processing unit 102d, a fixed asset control maintenance processing unit 102e, and the like.

[0089] The application approval processing unit 102f includes a destination approval necessity determination processing unit 102g, an approval route identification processing unit 102h (corresponding to the approval route identification processing means of the present invention), a destination approver identification processing unit 102i (corresponding to the destination approver identification processing means of the present invention), a workflow data creation processing unit 102j, an applicant-specific approver master deletion processing unit 102k, a workflow processing unit 102l, etc.

[0090] 2, the organization / department affiliation maintenance processing unit 102b displays an organization / department affiliation maintenance screen MA (corresponding to the organization / department affiliation maintenance screen of the present invention) that includes an organization chart MAa related to asset transfers and the like, and an input field MAb for inputting employees to be assigned to positions responsible for applications and approvals.The organization / department affiliation maintenance processing unit 102b then has an operator (e.g., a person in charge of maintaining the master data) input employees to be assigned to positions responsible for applications and approvals based on the employee master 106b, and creates an employee master 106c.

[0091] In this embodiment, the approval hierarchy for one department is two levels (a person in charge and a manager) in the department master 106a and the organizational chart MAa shown in Fig. 2, but the present disclosure is not limited to this. The approval hierarchy for one department may be three or more levels (for example, a person in charge, an intermediate manager, and a higher manager).

[0092] Returning to FIG. 3, the approval route maintenance processing unit 102c displays an approval route maintenance screen MB (MB-1, MB-2, MB-3) (corresponding to the approval route maintenance screen of the present invention) which includes input fields MBa (MBa-1, MBa-2, MBa-3) for inputting the route CD and the route name, and input fields MBb (MBb-1, MBb-2, MBb-3) for inputting the position responsible for approval.

[0093] The approval route maintenance screen MB-1 is a screen that shows approval for asset acquisition. The approval route maintenance screen MB-2 is a screen that shows approval for asset transfer, which requires approval for the asset transfer destination. The approval route maintenance screen MB-2 is a screen that shows approval for asset transfer, which does not require approval for the asset transfer destination.

[0094] The approval route maintenance processing unit 102c has an operator (e.g., a person in charge of maintaining master data) input a route CD and a route name based on the approval route master 106d. Furthermore, the approval route maintenance processing unit 102c has the operator input the position responsible for approval, and creates a stage approval master 106e (see FIG. 3).

[0095] 4, the approval route allocation maintenance processing unit 102d displays an approval route allocation maintenance screen MC including an organizational chart MCa relating to asset transfers, etc., and an input field MCb for inputting approval routes that can be applied for by positions responsible for application or approval (departments responsible for application or approval).The approval route allocation maintenance processing unit 102d then has an operator (e.g., a person in charge of master data maintenance) input approval routes that can be applied for by positions responsible for application or approval, based on the approval route master 106d, and creates the approval route allocation master 106f.

[0096] 5, the fixed asset control maintenance processing unit 102e displays a fixed asset control master maintenance screen MD (MD-1, MD-2) including input fields MDa (MDa-1, MDa-2) for inputting the acquisition approval operation class, transfer approval operation class, and removal approval operation class, and input fields MDb (MDb-1, MDb-2) for inputting the transfer destination approval organization code.The fixed asset control maintenance processing unit 102e then has an operator (e.g., a person in charge of maintaining the master data) input the acquisition approval operation class, transfer approval operation class, and removal approval operation class, and the transfer destination approval organization code, and creates the fixed asset control master 106h (106h-1, 106h-2).

[0097] The fixed asset control master maintenance screen MD-1 is a screen used when approval is required for the destination of a fixed asset, and the fixed asset control master maintenance screen MD-2 is a screen used when approval is not required for the destination of a fixed asset.

[0098] 6, the destination approval necessity determination processing unit 102g displays a transfer registration screen ME including a display field MEa for displaying the employee CD (in this specific example, employee CD "U00002") of the applicant for the asset transfer, etc. (in this specific example, Mr. B), an input field MEb for inputting the asset transfer date and the transfer destination recording department, an input field MEc for inputting the target asset and the transfer source recording department, and a register button MEd.The destination approval necessity determination processing unit 102g then prompts the operator to input the asset transfer date and the transfer destination recording department in the input field MEb, and the target asset and the transfer source recording department in the input field MEc, and when the register button MEd is clicked, creates business data 106i.

[0099] The approval route identification processing unit 102h creates an approver update preparation work 106n for each applicant based on the business data 106i.

[0100] The approval route identification processing unit 102h creates the applicant-specific approver update preparation work 106n only when approval of the destination is required for the transfer of assets between departments (as described above, when the transfer approval operation classification is "0: Required" for transfer approval and the destination approval organization CD is not "NULL"), and does not create the applicant-specific approver update preparation work 106n in other cases.

[0101] That is, if the transfer of assets between departments does not require approval of the transfer destination, the application approval processing unit 102f does not create the applicant-specific approver update preparation work 106n, if approval is required for the transfer of assets between departments, it creates history information data_approval 106k, and if approval is required for the transfer of assets between departments, it creates movement information data_approval 106j. In either case, the application approval processing unit 102f creates movement information data 106l and history information data 106m, which are actual data, and then terminates processing.

[0102] The movement information data 106l and history information data 106m, which are actual data, can be used in other systems such as a company-wide management system and an accounting system.

[0103] Returning to Fig. 7, the destination approver identification processing unit 102i displays a destination approver selection screen MF including a display field MFa for displaying the employee CD (in this specific example, employee CD "U00002") of the applicant (in this specific example, Mr. B) of the asset transfer, etc., an input field MFb for inputting the employee who will approve the asset at the first level of the destination, a selection input field MFc for selecting and inputting the employee who will approve the asset at the first level of the destination, and a selection button MFd. Then, based on the operator's input, the destination approver identification processing unit 102i stores information in the approver department CD column and the approver employee CD column of the applicant-specific approver update preparation work 106n. Furthermore, the destination approver identification processing unit 102i creates an applicant-specific approver master 106g based on the applicant-specific approver update preparation work 106n.

[0104] In addition, the destination approver identification processing unit 102i displays the destination approver selection screen MF (see Figure 7) when the registration button MEd in the transfer registration screen ME (see Figure 6) is clicked only when approval of the destination is required for the transfer of assets between departments (as mentioned above, when the transfer approval operation category is "0: Required" for transfer approval and the destination approval organization CD is not "NULL").

[0105] The workflow data creation processing unit 102j creates workflow data 106o based on the applicant-specific approver master 106g.

[0106] The applicant-specific approver master deletion processing unit 102k deletes the corresponding record from the applicant-specific approver master 106g based on the workflow data 106o.

[0107] The workflow processing unit 102l performs workflow processing based on the workflow data 106o and the business data 106i.

[0108] [2. Specific examples of processing] A specific example of the processing executed by the business support device 100 configured as described above will be described in detail with reference to Fig. 3 etc. along with an example of the flow of business performed using the business support device 100. In this explanation, the specific example of the processing will be described in the order of [2-1. Maintenance processing] and [2-2. Application approval processing].

[0109] In this specific example, a case where a fixed asset in the first manufacturing department is transferred to the third manufacturing department will be described.

[0110] In this specific example, assets from the First Manufacturing Department are being transferred to the Third Manufacturing Department, so the approval workflow is as follows: Mr. B (First Manufacturing Department (Person in Charge)) → Mr. A (First Manufacturing Department (Manager)) → Mr. F (Third Manufacturing Department (Person in Charge)) → Mr. E (Third Manufacturing Department (Manager)) → Accounting Department.

[0111] [2-1. Maintenance process (see Figures 2, 3, 4, and 5)] [2-1-1. Organization / Department Affiliation Maintenance Process (See Figure 2)] First, the organization / department affiliation maintenance processing unit 102b refers to the department master 106a and displays the organization / department affiliation maintenance screen MA including the organization chart MAa and the input field MAb. An operator (e.g., a person in charge of maintaining the master data) looks at the organization chart MAa and assigns employees to positions responsible for application or approval for each department.

[0112] For example, the operator assigns an employee CD "U00001" and an employee name "Mr. A" to a position of a department CD "S11000" and a department name "First Manufacturing Department (Manager)."

[0113] For example, the operator assigns an employee CD "U00002" and an employee name "Mr. B" to a position in the department CD "S11100" and the department name "First Manufacturing Department (Person in Charge)."

[0114] For example, the operator assigns an employee CD "U00005" and an employee name "Mr. E" to a position of a department CD "S13000" and a department name "Third Manufacturing Department (Manager)."

[0115] For example, the operator assigns an employee CD "U00006" and an employee name "Mr. F" to a position in the department CD "S13100" and the department name "Third Manufacturing Department (Person in Charge)."

[0116] For example, the operator assigns an employee CD "U00099" and an employee name "Mr. K" to a position in a department CD "S19900" and a division name "Accounting Department."

[0117] The organization / department / affiliation maintenance processing unit 102b creates or updates the employee affiliation master 106c based on the input information.

[0118] This allows each processing unit to identify the employee in charge of application or approval.

[0119] [2-1-2. Approval Route Maintenance Process (see Figure 3)] [2-1-2-A. Acquisition of Assets] In the case of asset acquisition, there is no specific destination for the asset, so after application and approval from the asset acquiring department (Mr. B (First Manufacturing Department (Person in Charge)) and Mr. A (First Manufacturing Department (Manager))), only approval from the final approval department (in this example, the Accounting Department) is required.

[0120] First, the approval route maintenance processing unit 102c displays an approval route maintenance screen MB-1 including an input field MBa-1 for inputting the route CD and route name, and an input field MBb-1 for inputting the position responsible for approval.

[0121] For example, an operator (e.g., a person in charge of maintaining master data) inputs a route CD "N001" into the route CD input field of input field MBa-1. The approval route maintenance processing unit 102c refers to the approval route master 106d and displays the route name "Acquisition Approval" in the route name input field of input field MBa-1.

[0122] Alternatively, the operator may input the route name "Acquisition Approval" in the route name input field of the input field MBa-1. The approval route maintenance processing unit 102c may refer to the approval route master 106d and display the route CD "N001" in the route CD input field of the input field MBa-1.

[0123] The operator enters "applicant" in the blank number column (the leftmost column) of input field MBb-1.

[0124] Alternatively, the approval route maintenance processing unit 102c may display "Applicant" in the blank number column (the leftmost column) of the input field MBb-1, regardless of the operator's input.

[0125] The operator also inputs the "upper division" in the column numbered "1" (second column from the left) of the input field MBb-1. In this specific example, the "upper division" is "First Manufacturing Department (Manager)."

[0126] Alternatively, the approval route maintenance processing unit 102c may display "Superordinate Department" in the column numbered "1" (second column from the left) of the input field MBb-1, regardless of the operator's input.

[0127] In addition, the operator enters "Designated Department" in the top row of column number "2" (third column from the left) of input field MBb-1, indicating that the department has been designated for final approval (in this specific example, the accounting department), and enters "Department CD:S19900" in the bottom row of column number "2" (third column from the left) of input field MBb-1, indicating the position responsible for approval in the final approval department (in this specific example, the accounting department).

[0128] Alternatively, the approval route maintenance processing unit 102c may display "Designated Department" in the upper row of the column numbered "2" (third column from the left) of input field MBb-1, indicating that the final approval department (in this specific example, the accounting department) has been designated, and may display "Department CD:S19900" in the lower row of the column numbered "2" (third column from the left) of input field MBb-1, indicating the position responsible for approval in the final approval department (in this specific example, the accounting department).

[0129] Next, when the operator clicks a registration icon (not shown), the approval route maintenance processing unit 102c creates a record set 106e-1 in the stage approval master 106e. The first record in the record set 106e-1 corresponds to column number "1" in the input field MBb-1. The second record in the record set 106e-1 corresponds to column number "2" in the input field MBb-1.

[0130] The approval route maintenance processing unit 102c stores "N001 (acquired approval)" in the route CD column of the first record in the record set 106e-1, stores "1" in the stage CD column, stores "1 (upper department)" in the stage type column, leaves the organization CD column blank (or NULL), leaves the department CD column blank, leaves the approver slot CD per applicant blank, and stores "FALSE" in the final flag column.

[0131] In addition, the approval route maintenance processing unit 102c stores "N001 (acquired approval)" in the route CD column of the second record in the record set 106e-1, stores "2" in the stage CD column, stores "3 (designated department)" in the stage type column, stores "Sosiki01" in the organization CD column, stores "S19900" in the department CD column, leaves the approver slot CD by applicant blank, and stores "TRUE" in the final flag column.

[0132] As a result, in the case of asset acquisition, each processing unit can refer to the record set 106e-1 and determine that approval by a total of two people is required.

[0133] [2-1-2-B. When approval of the transfer destination of assets is required] If approval is required for the destination of the asset, an application and approval from the source department (Mr. B (First Manufacturing Department (Person in Charge)) and Mr. A (First Manufacturing Department (Manager))) is required, followed by approval from the destination department (Mr. F (Third Manufacturing Department (Person in Charge)) and Mr. E (Third Manufacturing Department (Manager))), and finally approval from the final approving department (in this embodiment, the Accounting Department).

[0134] First, the approval route maintenance processing unit 102c displays an approval route maintenance screen MB-2 including an input field MBa-2 for inputting the route CD and route name, and an input field MBb-2 for inputting the position responsible for approval.

[0135] For example, an operator (e.g., a person in charge of maintaining master data) inputs a route CD "N002" into the route CD input field of input field MBa-2. The approval route maintenance processing unit 102c refers to the approval route master 106d and displays the route name "Movement Approval" in the route name input field of input field MBa-2.

[0136] Alternatively, the operator may input the route name "Move Approval" in the route name input field of input field MBa-2. The approval route maintenance processing unit 102c may refer to the approval route master 106d and display the route CD "N002" in the route CD input field of input field MBa-2.

[0137] The operator enters "applicant" in the blank number column (the leftmost column) of input field MBb-2.

[0138] Alternatively, the approval route maintenance processing unit 102c may display "Applicant" in the blank number column (the leftmost column) of the input field MBb-2, regardless of the operator's input.

[0139] The operator also inputs the "upper division" in the column numbered "1" (second column from the left) of input field MBb-2. In this specific example, the "upper division" is the "First Manufacturing Department (Manager)," as will be described later.

[0140] Alternatively, the approval route maintenance processing unit 102c may display "Superordinate Department" in the column numbered "1" (second column from the left) of the input field MBb-2, regardless of the operator's input.

[0141] In addition, the operator enters the "Approver Frame by Applicant," which is a provisional department frame for which a specific department (position) will be determined later, in the upper row of the column numbered "2" (third column from the left) of input field MBb-2, and enters the "Approver Frame CD:IS01," which is a provisional department CD frame for which a specific department CD will be determined later, in the lower row of the column numbered "2" (third column from the left) of input field MBb-2.

[0142] In addition, the operator enters the "Approver Frame by Applicant," which is a provisional department frame for which a specific department (position) will be determined later, in the upper row of the column numbered "3" (fourth column from the left) of input field MBb-2, and enters the "Approver Frame CD:IS02," which is a provisional department CD frame for which a specific department CD will be determined later, in the lower row of the column numbered "3" (fourth column from the left) of input field MBb-2.

[0143] In addition, the operator enters "Designated Department" in the upper row of the column numbered "4" (fifth column from the left) of input field MBb-2, indicating that the department has been designated for final approval (in this specific example, the accounting department), and enters "Department CD:S19900" in the lower row of the column numbered "4" (fifth column from the left) of input field MBb-2, indicating the position responsible for approval in the final approval department (in this specific example, the accounting department).

[0144] Next, when the operator clicks a registration icon (not shown), the approval route maintenance processing unit 102c creates a record set 106e-2 in the stage approval master 106e. The first record in the record set 106e-2 corresponds to column number "1" in the input field MBb-2. The second record in the record set 106e-2 corresponds to column number "2" in the input field MBb-2. The third record in the record set 106e-2 corresponds to column number "3" in the input field MBb-2. The fourth record in the record set 106e-2 corresponds to column number "4" in the input field MBb-2.

[0145] The approval route maintenance processing unit 102c stores "N002 (transfer approval)" in the route CD column of the first record in the record set 106e-2, stores "1" in the stage CD column, stores "1 (upper department)" in the stage type column, leaves the organization CD column blank (or NULL), leaves the department CD column blank (or NULL), leaves the approver quota CD for each applicant blank (or NULL), and stores "FALSE" in the final flag column.

[0146] Furthermore, the approval route maintenance processing unit 102c stores "N002 (transfer approval)" in the route CD column of the second record in the record set 106e-2, stores "2" in the stage CD column, stores "6 (applicant-specific approver frame)" in the stage type column, leaves the organization CD column blank (or NULL), leaves the department CD column blank (or NULL), stores the temporary approver CD "IS01 (transfer destination approval 1: person in charge)" in the applicant-specific approver frame CD, and stores "FALSE" in the final flag column.

[0147] Furthermore, the approval route maintenance processing unit 102c stores "N002 (transfer approval)" in the route CD column of the third record in the record set 106e-2, stores "3" in the stage CD column, stores "6 (applicant-specific approver frame)" in the stage type column, leaves the organization CD column blank (or NULL), leaves the department CD column blank (or NULL), stores the temporary approver CD "IS02 (transfer destination approval 2: responsible person)" in the applicant-specific approver frame CD, and stores "FALSE" in the final flag column.

[0148] In addition, the approval route maintenance processing unit 102c stores "N002 (transfer approval)" in the route CD column of the fourth record in the record set 106e-2, stores "4" in the stage CD column, stores "3 (designated department)" in the stage type column, stores "Sosiki01" in the organization CD column, stores "S19900" in the department CD column, leaves the approver slot CD by applicant blank (or NULL), and stores "TRUE" in the final flag column.

[0149] As a result, when approval of the destination of the asset is required, each processing unit can refer to the record set 106e-2 and determine that approval is required from a total of four people.

[0150] In the embodiment, the column numbers in the input field MBb-2 range from "1" to "4," but the present disclosure is not limited to this. For example, if the approval hierarchy of the asset transfer destination is three levels, the column numbers in the input field MBb-2 may range from "1" to "5," and "Approver Allocation by Applicant" and "Approver Allocation CD:IS03" may be entered in column number "4," and "Designated Department" and "Department CD:S19900" may be entered in column number "5." In this case, the number of records in the record set 106e-2 is 5. The number of columns in the input field MBb-2 and the number of records in the record set 106e-2 may be dynamically changeable.

[0151] [2-1-2-C. Cases where approval of the asset transfer destination is not required] If approval of the destination of the asset is not required, only approval from the final approval department (in this embodiment, the accounting department) is required after application and approval from the department from which the asset is being transferred (Mr. B (First Manufacturing Department (Person in Charge)) and Mr. A (First Manufacturing Department (Manager))).

[0152] First, the approval route maintenance processing unit 102c displays an approval route maintenance screen MB-3 including an input field MBa-3 for inputting the route CD and route name, and an input field MBb-3 for inputting the position responsible for approval.

[0153] For example, an operator (e.g., a person in charge of maintaining master data) inputs a route CD "N002" into the route CD input field of input field MBa-3. The approval route maintenance processing unit 102c refers to the approval route master 106d and displays the route name "Movement Approval" in the route name input field of input field MBa-3.

[0154] Alternatively, the operator may input the route name "Move Approval" in the route name input field of input field MBa-3. The approval route maintenance processing unit 102c may refer to the approval route master 106d and display the route CD "N002" in the route CD input field of input field MBa-3.

[0155] The operator enters "applicant" in the blank number column (the leftmost column) of input field MBb-3.

[0156] Alternatively, the approval route maintenance processing unit 102c may display "Applicant" in the blank number column (the leftmost column) of the input field MBb-3, regardless of the operator's input.

[0157] The operator also inputs the "upper division" in the column numbered "1" (second column from the left) of input field MBb-3. In this specific example, the "upper division" is the "First Manufacturing Department (Manager)," as will be described later.

[0158] Alternatively, the approval route maintenance processing unit 102c may display "Superordinate Department" in the column numbered "1" (second column from the left) of the input field MBb-3, regardless of the operator's input.

[0159] In addition, the operator enters "Designated Department" in the top row of column number "2" (third column from the left) of input field MBb-3, indicating that the department has been designated for final approval (in this specific example, the accounting department), and enters "Department CD:S19900" in the bottom row of column number "2" (third column from the left) of input field MBb-3, indicating the position responsible for approval in the final approval department (in this specific example, the accounting department).

[0160] Alternatively, the approval route maintenance processing unit 102c may display "Designated Department" in the upper row of the column numbered "2" (third column from the left) of input field MBb-3, indicating that the final approval department (in this specific example, the accounting department) has been designated, and may display "Department CD:S19900" in the lower row of the column numbered "2" (third column from the left) of input field MBb-3, indicating the position responsible for approval in the final approval department (in this specific example, the accounting department).

[0161] Next, when the operator clicks a registration icon (not shown), the approval route maintenance processing unit 102c creates (adds) a record set 106e-3 to the stage approval master 106e. The first record in the record set 106e-3 corresponds to column number "1" in the input field MBb-3. The second record in the record set 106e-3 corresponds to column number "2" in the input field MBb-3.

[0162] The approval route maintenance processing unit 102c stores "N002 (transfer approval)" in the route CD column of the first record in the record set 106e-3, stores "1" in the stage CD column, stores "1 (upper department)" in the stage type column, leaves the organization CD column blank (or NULL), leaves the department CD column blank, leaves the approver slot CD per applicant blank, and stores "FALSE" in the final flag column.

[0163] In addition, the approval route maintenance processing unit 102c stores "N002 (transfer approval)" in the route CD column of the second record in the record set 106e-3, stores "2" in the stage CD column, stores "3 (designated department)" in the stage type column, stores "Sosiki01" in the organization CD column, stores "S19900" in the department CD column, leaves the approver slot CD by applicant blank, and stores "TRUE" in the final flag column.

[0164] As a result, when approval of the destination of the asset is not required, each processing unit can refer to the record set 106e-3 and determine that approval is required from a total of two people.

[0165] [2-1-3. Approval route allocation maintenance process (see Figure 4)] First, the approval route assignment maintenance processing unit 102d refers to the department master 106a and displays the approval route assignment maintenance screen MC including the organizational chart MCa and the input field MCb. An operator (e.g., a person in charge of maintaining the master data) looks at the organizational chart MCa and assigns the approval types that can be applied for to the positions in each department that are responsible for application or approval.

[0166] For example, the operator inputs "fixed asset acquisition application" in the approval type column of the first line of the input field MCba corresponding to the position of department CD "S11100" and department name "First Manufacturing Department (Person in Charge)." The approval route assignment maintenance processing unit 102d refers to the approval route master 106d and displays "N001" in the approval route column of the first line of the input field MCba.

[0167] Alternatively, the operator may input "N001" in the approval route column in the first line of the input field MCba. The approval route allocation maintenance processing unit 102d may refer to the approval route master 106d and display "Fixed asset acquisition application" in the approval type column in the first line of the input field MCba.

[0168] For example, the operator inputs "fixed asset transfer application" in the approval type column in the second line of the input field MCba. The approval route assignment maintenance processing unit 102d refers to the approval route master 106d and displays "N002" in the approval route column in the second line of the input field MCba.

[0169] Alternatively, the operator may input "N002" in the approval route column in the second line of the input field MCba. The approval route allocation maintenance processing unit 102d may refer to the approval route master 106d and display "fixed asset transfer application" in the approval type column in the second line of the input field MCba.

[0170] Next, the approval route allocation maintenance processing unit 102d creates a record group in the approval route allocation master 106f based on the input information.

[0171] For example, the approval route allocation maintenance processing unit 102d creates a record 106fa that stores "Sosiki01" in the organization CD column, "S11100" in the department CD column, "N0110 (transfer application)" in the application type CD column, and "N002 (transfer route)" in the route CD column.

[0172] As a result, each processing unit can determine that an employee assigned to a position in department CD "S11100" and department name "First Manufacturing Department (Person in Charge)" can apply for the transfer of fixed assets.

[0173] [2-1-4. Fixed asset control master maintenance process (see Figure 5)] [2-1-4-A. When approval of the transfer destination of assets is required] First, the fixed asset control maintenance processing unit 102e displays the fixed asset control master maintenance screen MD (MD-1), which includes input fields MDa-1 for entering the acquisition approval operation category, transfer approval operation category, and removal approval operation category, as well as an input field MDb-1 for entering the transfer destination approval organization code.

[0174] For example, an operator (e.g., a master data maintenance person) enters "0: Required" in the input field for the acquisition approval operation category. Also, for example, an operator enters "0: Required" in the input field for the transfer approval operation category. Also, for example, an operator enters "0: Required" in the input field for the removal approval operation category. Also, for example, an operator enters "Sosiki01" in the input field for the transfer destination approval organization code.

[0175] The fixed asset control maintenance processing unit 102e creates a record 106ha (106ha-1) in the fixed asset control master 106h (106h-1).

[0176] The fixed asset control maintenance processing unit 102e stores "0: Required" in the acquisition approval operation classification column of record 106ha-1, stores "0: Required" in the transfer approval operation classification column, stores "0: Required" in the removal approval operation classification column, and stores "Sosiki01" in the transfer destination approval organization CD column.

[0177] As a result, each processing unit can determine that approval of the asset transfer destination and approval of the accounting department is required because the transfer approval operation category of record 106ha-1 is "0: required" and the transfer destination approval organization CD is not "NULL".

[0178] In addition, when the column for the transfer approval operation category is "1: Not required," each processing unit can determine that approval is not required for the transfer of assets.

[0179] [2-1-4-B. Cases where approval of the asset transfer destination is not required] First, the fixed asset control maintenance processing unit 102e displays the fixed asset control master maintenance screen MD (MD-2), which includes input fields MDa-2 for entering the acquisition approval operation category, transfer approval operation category, and removal approval operation category, as well as an input field MDb-2 for entering the transfer destination approval organization code.

[0180] For example, an operator (e.g., a master data maintenance person) enters "0: Required" in the input field for the acquisition approval operation category. Also, for example, an operator enters "0: Required" in the input field for the transfer approval operation category. Also, for example, an operator enters "0: Required" in the input field for the removal approval operation category. Also, for example, an operator leaves the input field for the transfer destination approval organization code blank.

[0181] The fixed asset control maintenance processing unit 102e creates a record 106ha (106ha-2) in the fixed asset control master 106h (106h-2).

[0182] The fixed asset control maintenance processing unit 102e stores "0: Required" in the acquisition approval operation classification column of record 106ha-2, stores "0: Required" in the transfer approval operation classification column, stores "0: Required" in the removal approval operation classification column, and stores "NULL" in the transfer destination approval organization CD column.

[0183] As a result, each processing unit can determine that even if the transfer approval operation category of record 106ha-2 is "0: Required", since the transfer destination approval organization CD is "NULL", approval of the asset transfer destination is not required, and approval of the transfer source approver and approval of the accounting department are required.

[0184] In addition, when the column for the transfer approval operation category is "1: Not required," each processing unit can determine that approval is not required for the transfer of assets.

[0185] [2-2. Application Approval Process (see Figures 6, 7, 8, 9, 10, 11, and 12)] [2-2-1. Processing to determine whether destination approval is required (see step 0 in Figure 6)] [2-2-1-A. When approval of the asset transfer destination is required (Step 0-A)] First, the destination approval requirement determination processing unit 102g displays a transfer registration screen ME including a display field MEa for displaying the employee CD (in this specific example, employee CD "U00002") of the applicant for asset transfer, etc. (in this specific example, Mr. B), an input field MEb for inputting the asset transfer date and the destination recording department, an input field MEc for inputting the asset to be transferred, etc. and the destination recording department, and a registration button MEd.

[0186] For example, the applicant for an asset transfer, etc. (in this specific example, Mr. B) enters the transfer date (in this specific example, "2024 / 2 / 1") in the transfer date input field of input field MEb, and enters the destination recording department (in this specific example, "Third Manufacturing Department") in the destination recording department field of input field MEb.

[0187] Also, for example, the applicant for asset transfer, etc. (in this specific example, Mr. B) enters an identifier that uniquely identifies the first asset to be transferred, etc. (in this specific example, "A1000101-000") in the target asset input field in the first line of input field MEc, and enters the source accounting department (in this specific example, "First Manufacturing Department") in the source accounting department field.

[0188] Also, for example, the applicant for asset transfer, etc. (in this specific example, Mr. B) enters an identifier that uniquely identifies the second asset to be transferred, etc. (in this specific example, "A1000102-000") in the target asset input field in the second line of input field MEc, and enters the source accounting department (in this specific example, "First Manufacturing Department") in the source accounting department field.

[0189] The destination approval requirement determination processing unit 102g refers to the record 106ha (106ha-1) in the fixed asset control master 106h (106h-1), and if the transfer approval operation category is "0: Required", determines that approval of the destination of the asset is required, and creates transfer information data_approval 106j and history information data_approval 106k (step 0-0).

[0190] For example, the destination approval requirement determination processing unit 102g stores "A1000101-000" in the asset number column of the first record 106ja of the transfer information data_approval 106j, stores "2024 / 2 / 1" in the transfer date column, stores "First Manufacturing Department" in the source accounting department column, and stores "Third Manufacturing Department" in the destination accounting department column.

[0191] For example, the destination approval requirement determination processing unit 102g stores "A1000101-000" in the asset number column of the first record 106ka of the history information data_approval 106k, stores "3 (movement)" in the reason column, stores "10 (pending)" in the approval status classification column, and stores "2f7eb180-61f~" in the case Guid column.

[0192] Also, for example, the destination approval requirement determination processing unit 102g stores "A1000102-000" in the asset number column of the second record 106jb of the transfer information data_approval 106j, stores "2024 / 2 / 1" in the transfer date column, stores "1st Manufacturing Department" in the source accounting department column, and stores "3rd Manufacturing Department" in the destination accounting department column.

[0193] For example, the destination approval requirement determination processing unit 102g stores "A1000102-000" in the asset number column of the second record 106kb of the history information data_approval 106k, stores "3 (movement)" in the reason column, stores "10 (pending)" in the approval status classification column, and stores "2f7eb180-61f~" in the case Guid column.

[0194] If the destination approval necessity determination processing unit 102g determines that approval of the destination of the asset is necessary (step 0-0), the approval route identification processing unit 102h executes step 1, which will be described later.

[0195] [2-2-1-B. When approval of the asset transfer destination is not required (Step 0-B)] First, the destination approval requirement determination processing unit 102g displays a transfer registration screen ME including a display field MEa for displaying the employee CD (in this specific example, employee CD "U00002") of the applicant for asset transfer, etc. (in this specific example, Mr. B), an input field MEb for inputting the asset transfer date and destination recording department, an input field MEc for inputting the target asset and destination recording department, and a registration button MEd.

[0196] For example, the applicant for an asset transfer, etc. (in this specific example, Mr. B) enters the transfer date (in this specific example, "2024 / 2 / 1") in the transfer date input field of input field MEb, and enters the destination recording department (in this specific example, "Third Manufacturing Department") in the destination recording department field of input field MEb.

[0197] Also, for example, the applicant for asset transfer, etc. (in this specific example, Mr. B) enters an identifier that uniquely identifies the first asset to be transferred, etc. (in this specific example, "A1000101-000") in the target asset input field in the first line of input field MEc, and enters the source accounting department (in this specific example, "First Manufacturing Department") in the source accounting department field.

[0198] Also, for example, the applicant for asset transfer, etc. (in this specific example, Mr. B) enters an identifier that uniquely identifies the second asset to be transferred, etc. (in this specific example, "A1000102-000") in the target asset input field in the second line of input field MEc, and enters the source accounting department (in this specific example, "First Manufacturing Department") in the source accounting department field.

[0199] The destination approval necessity determination processing unit 102g references the record 106ha (106ha-2) of the fixed asset control master 106h (106h-2), and if the transfer approval operation classification is "1: Not required," it further references the destination approval organization code. If the destination approval organization code is "NULL," the destination approval necessity determination processing unit 102g determines that approval of the asset transfer destination is not required, and creates transfer information data 106l and history information data 106m (step 0-1).

[0200] For example, the destination approval requirement determination processing unit 102g stores "A1000101-000" in the asset number column of the first record 106la of the transfer information data 106l, stores "2024 / 2 / 1" in the transfer date column, stores "First Manufacturing Department" in the transfer source accounting department column, and stores "Third Manufacturing Department" in the transfer destination accounting department column.

[0201] Furthermore, for example, the destination approval necessity determination processing unit 102g stores "A1000101-000" in the asset No. column of the first record 106ma of the history information data 106m, and stores "3 (transfer)" in the reason column.

[0202] Also, for example, the destination approval requirement determination processing unit 102g stores "A1000102-000" in the asset number column of the second record 106lb of the transfer information data 106l, stores "2024 / 2 / 1" in the transfer date column, stores "First Manufacturing Department" in the transfer source accounting department column, and stores "Third Manufacturing Department" in the transfer destination accounting department column.

[0203] Furthermore, for example, the destination approval necessity determination processing unit 102g stores "A1000102-000" in the asset No. column of the second record 1061b of the history information data 106m, and stores "3 (transfer)" in the reason column.

[0204] If the destination approval necessity determination processing unit 102g determines that approval of the asset transfer is not required (step 0-1), each processing unit terminates the processing without executing the next step 1 or later. Also, if the destination approval necessity determination processing unit 102g determines that approval of the asset transfer is required but approval of the asset transfer destination is not required, the workflow data creation processing unit 102j ignores the applicant-specific approver update preparation work 106n and applicant-specific approver master 106g of the transfer destination, and creates workflow data that includes only the transfer source and the accounting department.

[0205] [2-2-2. Approval Route Identification Process (see Step 1 in Figure 6)] (1) First, the approval route identification processing unit 102h uses the employee CD "U00002" of the applicant for asset transfer, etc. (in this specific example, Mr. B) as a key to refer to the employee affiliation master 106c and obtains the organization CD (in this specific example, "Sosiki01") and department CD (in this specific example, "S11100") in the record 106ca.

[0206] (2) Next, the approval route identification processing unit 102h refers to the approval route allocation master 106f using the organization CD (in this specific example, "Sosiki01") and department CD (in this specific example, "S11100") obtained in (1) above as keys, and obtains the route CD (in this specific example, "N002 (travel route)") in the record 106fa.

[0207] (3) Next, the approval route identification processing unit 102h refers to the stage approval master 106e using the route CD obtained in (2) above (in this specific example, "N002 (route for transfer)") as a key, and obtains the number "2" of records (in this specific example, the second and third records) in which "6 (approver quota per applicant)" is stored in the stage type column of the record set 106e-2, and the approver quota CD per applicant among these records (in this specific example, "IS01 (destination approval 1: person in charge)" and "IS02 (destination approval 2: manager)").

[0208] If the approver frame CD for each applicant is not set, the approval route identification processing unit 102h determines that the asset destination approval is not required, updates only the business data 106i, and ends the process. Therefore, the destination approver identification processing unit 102i does not display the destination approver selection screen MF (see FIG. 7).

[0209] Next, the approval route identification processing unit 102h creates an applicant-specific approver update preparation work 106n based on the information acquired in (1), (2), and (3) above.

[0210] In this specific example, the approval route identification processing unit 102h creates two records 106na and 106nb in the applicant-specific approver update preparation work 106n because the number of approvers at the asset transfer destination is two (in this specific example, "IS01" and "IS02").

[0211] The approval route identification processing unit 102h stores "Sosiki01" in the applicant organization CD column of record 106na, stores "1" in the hierarchy CD column, stores "IS01 (first hierarchy)" in the approver by applicant column, stores "S11100" in the applicant department CD column, stores "U00002" in the applicant employee CD column, stores "Sosiki01" in the approver organization CD column, leaves the approver department CD column blank (or "NULL"), and leaves the approver employee CD column blank (or "NULL").

[0212] The approval route identification processing unit 102h stores "Sosiki01" in the applicant organization CD column of record 106nb, stores "2" in the hierarchy CD column, stores "IS02 (second hierarchy)" in the approver by applicant column, stores "S11100" in the applicant department CD column, stores "U00002" in the applicant employee CD column, stores "Sosiki01" in the approver organization CD column, leaves the approver department CD column blank (or "NULL"), and leaves the approver employee CD column blank (or "NULL").

[0213] [2-2-3. Destination approver identification process (see step 2 in Figure 7)] First, the destination approver identification processing unit 102i displays the destination approver selection screen MF, which includes a display field MFa for displaying the employee CD (in this specific example, employee CD "U00002") of the applicant for asset transfer, etc. (in this specific example, Mr. B), an input field MFb for inputting the employee of the first-level approver of the destination of the assets, and a selection input field MFc for selecting and inputting the employee of the first-level approver of the destination of the assets.

[0214] For example, the applicant for asset transfer (Mr. B in this specific example) enters the employee name of the person in charge of the asset transfer destination (Mr. F in this specific example) in the employee name entry field of the entry field MFb.

[0215] Alternatively, the applicant for asset transfer, etc. (in this specific example, Mr. B) enters the employee code of the person in charge of the asset transfer destination (in this specific example, "U00006") in the employee code input field of input field MFb. The transfer destination approver identification processing unit 102i may refer to the employee master 106b and display the employee name "Mr. F" in the employee name input field.

[0216] Next, the destination approver identification processing unit 102i references the employee affiliation master 106c using the employee CD of the approval officer at the destination of the asset ("U00006" in this specific example) as a key, and acquires record 106cb. Then, the destination approver identification processing unit 102i references the department master 106a using the information in the department CD column of record 106cb ("S13100" in this specific example) as a key, and acquires record 106aa. In this specific example, the department name column of record 106aa stores "Third Manufacturing Department (Person in Charge)". Furthermore, "S13000" is stored in the parent department CD column of record 106aa.

[0217] Next, based on the information acquired above, the destination approver identification processing unit 102i displays "U00006" in the employee code column of the selection input field MFc, displays "Mr. F" in the employee name column, displays "S13100" in the department code column, and displays "Third Manufacturing Department (Person in Charge)" in the department name column.

[0218] The applicant for asset transfer etc. (in this specific example, person B) checks the selection input field MFc and clicks the selection button MFd.

[0219] Next, the destination approver identification processing unit 102i stores "S13100" in the approver department CD column that was previously blank (see Figure 6) of the record 106na of the applicant-specific approver update preparation work 106n, and stores "U00006" in the approver employee CD column that was previously blank (see Figure 7).

[0220] That is, the destination approver specification processing unit 102i specifies the department CD of the person in charge of approving the destination of the asset as "S13100" and the employee CD of the person in charge of approving the destination of the asset as "U00006".

[0221] Next, the destination approver specification processing unit 102i refers to the department master 106a using the parent department CD "S13000" in the record 106aa acquired above as a key, and acquires the record 106ab. In this specific example, the department name column of the record 106ab stores "Third Manufacturing Department (Manager)".

[0222] Next, the destination approver specification processing unit 102i references the employee affiliation master 106c using the parent department CD "S13000" acquired above as a key, and acquires record 106cc. In this specific example, "U00005" (Mr. E in this specific example) is stored in the employee CD column of record 106cc.

[0223] Next, the destination approver identification processing unit 102i stores "S13000" in the approver department CD column that was previously blank (see Figure 6) of the record 106nb of the applicant-specific approver update preparation work 106n, and stores "U00005" in the approver employee CD column that was previously blank (see Figure 7).

[0224] That is, the destination approver specification processing unit 102i specifies the department CD of the person in charge of approval at the destination of the asset as "S13000", and specifies the employee CD of the person in charge of approval at the destination of the asset as "U00005".

[0225] In this specific example, the destination approval hierarchy of the asset is two levels (person in charge and responsible person). Therefore, the number of records in the applicant-specific approver update preparation work 106n is also two, records 106na and 106nb. Therefore, the destination approver specification processing unit 102i may display an error on the destination approver selection screen MF if (the number of applicant-specific approver slots) > (the number of approval levels in the department master 106a).

[0226] Next, the destination approver specification processing unit 102i adds the information in the applicant-specific approver update preparation work 106n to the applicant-specific approver master 106g (see FIG. 7), which was previously blank (see FIG. 4).

[0227] For example, the destination approver identification processing unit 102i stores "Sosiki01" in the applicant organization CD column of the applicant-specific approver master record 106ga, stores "IS01 (first hierarchical level)" in the applicant-specific approver column, stores "S11100" in the applicant department CD column, stores "U00002" in the applicant employee CD column, stores "Sosiki01" in the approver organization CD column, stores "S13100" in the approver department CD column, and stores "U00006" in the approver employee CD column.

[0228] For example, the destination approver identification processing unit 102i stores "Sosiki01" in the applicant organization CD column of the 106GB record of the applicant-specific approver master, stores "IS02 (second hierarchical level)" in the applicant-specific approver column, stores "S11100" in the applicant department CD column, stores "U00002" in the applicant employee CD column, stores "Sosiki01" in the approver organization CD column, stores "S13000" in the approver department CD column, and stores "U00005" in the approver employee CD column.

[0229] [2-2-4. Workflow data creation process (see step 3 in Figure 7)] The workflow data creation processing unit 102j creates workflow data 106o by referring to the above acquired data.

[0230] The workflow data creation processing unit 102j stores "2f7eb180-61f~", an identifier that uniquely identifies the asset transfer case, in the case Guid column of record 106pa of case data 106p, stores "N0110 (transfer application)" in the application type CD column, stores "10 (application in progress)" in the approval status classification column, and stores "1" in the stage CD column.

[0231] The workflow data creation processing unit 102j also creates the case stage data 106q based on the four records of the record set 106e-2 in the stage approval master 106e.

[0232] (1) Identification of the applicant's department The workflow data creation processing unit 102j references the employee affiliation master 106c using the employee CD (in this specific example, "U00002") of the applicant for asset transfer, etc. as a key, and obtains the applicant's department CD (in this specific example, "S11100").

[0233] (2) Identifying the approval route to be used in the application The workflow data creation processing unit 102j refers to the approval route allocation master 106f using the applicant's department CD (in this specific example, "S11100") as a key, and acquires the route CD (in this specific example, "N002").

[0234] (3) Identification of the parent department and employees assigned to the parent department required for the approval route obtained in (2) above The workflow data creation processing unit 102j references the department master 106a using the applicant's department CD (in this specific example, "S11100") as a key, and acquires the parent department CD (in this specific example, "S11000").The workflow data creation processing unit 102j then references the employee affiliation master 106c using the acquired parent department CD (in this specific example, "S11000") as a key, and acquires the employee CD (in this specific example, "U00001") of the employee assigned to the parent department.

[0235] (4) Identification of the designated department and employees assigned to the designated department required for the approval route obtained in (2) above The workflow data creation processing unit 102j refers to the stage approval master 106e using the route CD ("N002" in this specific example) acquired in (2) as a key, and acquires the department CD of the designated department ("S19900" in this specific example).The workflow data creation processing unit 102j then refers to the employee affiliation master 106c using the acquired department CD ("S19900" in this specific example) as a key, and acquires the employee CD of the employee assigned to the designated department ("U00099" in this specific example).

[0236] (5) Identifying the destination department and the employee assigned to the destination department that corresponds to the "approver quota for each applicant" required for the approval route obtained in (2) above The workflow data creation processing unit 102j uses the "applicant organization CD," "applicant-specific approver slot CD," "applicant department CD," and "applicant employee CD" as keys to refer to the applicant-specific approver master 106g created in the destination approver identification process (see step 2 in Figure 7), and obtains the approver organization CD, approver department CD, and approver employee CD for applicant-specific approver slot 1 and applicant-specific approver slot 2.

[0237] The workflow data creation processing unit 102j creates the case stage data 106q based on the contents acquired in the above (1) to (5).

[0238] [2-2-5. Delete Approver Master Data by Applicant (see Step 4 in Figure 7)] After the workflow data is created in step 3 above, the applicant-specific approver master deletion processing unit 102k deletes the information stored in the records 106ga and 106gb of the applicant-specific approver master 106g.

[0239] [2-2-6. Workflow Processing (see Figures 8, 9, 10, 11, and 12)] This section explains the workflow and data creation and updating for a specific example of transferring assets from the first manufacturing department to the third manufacturing department.

[0240] [2-2-6-A.Application] Referring to Figure 8, when Person B of the First Manufacturing Department (person in charge) applies for the transfer of assets, the above-mentioned processes 2-2-1. Determining whether or not the destination approval is required to 2-2-5. Deleting the approver master data by applicant are executed, and workflow data 106o and business data 106i are created.

[0241] [2-2-6-B. Approval of transfer source manager] Referring to FIG. 9, the workflow processing unit 102l passes the workflow to Mr. A of the first manufacturing department (person in charge). Mr. A inputs his approval to the workflow processing unit 102l. When Mr. A inputs his approval, the workflow processing unit 102l updates the approval status column of the record 106pa of the case data 106p to "20 (under approval)" and the stage CD column to "2." The workflow processing unit 102l also updates the completion flag column of the first record 106qa of the case stage data 106q to "1."

[0242] [2-2-6-C. Approval of destination person in charge] Referring to FIG. 10, the workflow processing unit 102l passes the workflow to Mr. F of the third manufacturing department (person in charge). Mr. F inputs his approval to the workflow processing unit 102l. When Mr. F inputs his approval, the workflow processing unit 102l updates the stage CD column of the record 106pa of the case data 106p to "3." In addition, the workflow processing unit 102l updates the completion flag column of the second record 106qb of the case stage data 106q to "1."

[0243] [2-2-6-D. Transfer destination supervisor approval] Referring to FIG. 11, the workflow processing unit 102l passes the workflow to Mr. E of the third manufacturing department (person in charge). Mr. E inputs his approval to the workflow processing unit 102l. When Mr. E inputs his approval, the workflow processing unit 102l updates the stage CD column of the record 106pa of the case data 106p to "4." In addition, the workflow processing unit 102l updates the completion flag column of the third record 106qc of the case stage data 106q to "1."

[0244] [2-2-6-E. Accounting Department Approval] 12, the workflow processing unit 102l sends the workflow to Mr. K in the accounting department. Mr. K inputs his approval to the workflow processing unit 102l. When Mr. K inputs his approval, the workflow processing unit 102l updates the approval status column of the record 106pa of the case data 106p to "50 (completed)". In addition, the workflow processing unit 102l updates the completion flag column of the fourth record 106qd of the case stage data 106q to "1".

[0245] [2-2-6-F. Reflection in actual data] 12, when approval by Mr. K of the accounting department is completed, the workflow processing unit 102l reflects (copies) the information in the travel information data_approval 106j, which is temporary data, into the travel information data 106l, which is actual data. Also, the workflow processing unit 102l reflects (copies) the information in the history information data_approval 106k, which is temporary data, into the history information data 106m, which is actual data.

[0246] [3. Summary of this embodiment] When an inter-departmental transfer of an asset requires approval of the destination, the approval route maintenance processing unit 102c stores "IS01 (destination approval 1: person in charge)", which is a temporary approval person CD, in the column of the approver frame per applicant CD of the second record in the record set 106e-2 of the stage approval master 106e. Also, the approval route maintenance processing unit 102c stores "IS02 (destination approval 1: person in charge)", which is a temporary approval responsible person CD, in the column of the approver frame per applicant CD of the third record in the record set 106e-2 of the stage approval master 106e.

[0247] The destination approval necessity determination processing unit 102g then stores the temporary approval officer "IS01 (first hierarchical level)" in the approver per applicant column of record 106na of the approver per applicant update preparation work. The destination approval necessity determination processing unit 102g also stores the temporary approval officer "IS02 (second hierarchical level)" in the approver per applicant column of record 106nb of the approver per applicant update preparation work.

[0248] This allows the person requesting the asset transfer (Mr. B in this specific example) to apply for the asset transfer on the transfer registration screen ME without knowing the person responsible for approving the asset transfer destination (Mr. E in this specific example), thereby reducing the burden of creating an approval route for asset transfers between departments.

[0249] The destination approver identification processing unit 102i also stores "S13100", which is the department CD of the destination approver, and "U00006", which is the employee CD of the destination approver, in the approver department CD column of record 106na of the applicant-specific approver update preparation work 106n. The destination approver identification processing unit 102i also stores "S13000", which is the department CD of the destination approval manager, and "U00005", which is the employee CD of the destination approval manager, in the approver department CD column of record 106nb of the applicant-specific approver update preparation work 106n.

[0250] Furthermore, the destination approver identification processing unit 102i stores "S13100", which is the department CD of the approver at the destination, and stores "U00006", which is the employee CD of the approver at the destination, in the approver department CD column of record 106ga of the applicant-specific approver master 106g. Also, the destination approver identification processing unit 102i stores "S13000", which is the department CD of the approval manager at the destination, and stores "U00005", which is the employee CD of the approval manager at the destination, in the approver department CD column of record 106gb of the applicant-specific approver master 106g.

[0251] The workflow data creation processing unit 102j creates workflow data 106o for circulating the approval workflow based on the stage approval master 106e and the applicant-specific approver master 106g.

[0252] This allows the person who approves the asset transfer to approve the asset transfer.

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

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

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

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

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

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

[0259] Furthermore, with regard to the task support 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.

[0260] For example, all or any part of the processing functions of the business support device 100, particularly the processing functions performed by the control unit, may be realized by a CPU and a program interpreted and executed by the CPU, or may be realized as hardware using wired logic. The program is recorded on a non-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 business support device 100 as needed. That is, a computer program for providing instructions to the CPU in cooperation with the OS and performing various processes is recorded in a storage unit such as a ROM or HDD (Hard Disk Drive). The computer program is executed by being loaded into RAM, and cooperates with the CPU to form the control unit.

[0261] This computer program may be stored in an application program server connected to the business support device 100 via any network, and all or part of it may be downloaded as needed.

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

[0263] Furthermore, a "program" is a data processing method written in any language or description method, regardless of the format, such as source code or binary code. Note that a "program" is not necessarily limited to a single program, but also includes programs that are distributed as multiple modules or libraries, or programs that achieve their functions by working together with other programs, such as an OS. Note that the specific configurations and reading procedures for reading a recording medium in each device shown in the embodiments, as well as the installation procedures after reading, can use well-known configurations and procedures.

[0264] The various databases stored in the memory unit 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.

[0265] The business support 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 business support device 100 may be realized by installing software (including programs, data, etc.) that causes the device to perform the processes described in this embodiment.

[0266] 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 according to 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]

[0267] The present invention is useful in transferring assets of companies, organizations, etc. [Explanation of symbols]

[0268] 100 Business support equipment 102 Control section 102a Maintenance Processing Section 102b Organizational Department Maintenance Department 102c Approval Route Maintenance Processing Unit 102d Approval route allocation maintenance processing section 102e Fixed Asset Control and Maintenance Department 102f Application approval processing unit 102g Processing unit for determining whether or not destination approval is required 102h Approval route identification processing unit 102i Destination approver specific processing unit 102j Workflow data creation processing section 102k Approver Master Deletion Processing Unit 102l Workflow Processing Unit 104 Communication interface unit 106 Storage section 106a Department Master 106b Employee Master 106c Employee affiliation master 106d Approval Route Master 106e Stage Approval Master 106f Approval route allocation master 106g Approver Master by Applicant 106h Fixed Asset Control Master 106i Business Data 106j Movement Information Data_Approval 106k History Information Data_Approval 106l Travel Information Data 106m History Information Data 106n Approver Update Preparation Work 106o Workflow Data 106p Project Data 106q Project Stage Data 108 Input / Output Interface Section 112 Input Device 114 Output Device 200 servers 300 Network

Claims

1. A business support device including a control unit that supports approval operations when assets of a transfer source department are transferred to a transfer destination department, Department master data including organizational chart information for asset transfer requests and approvals; Affiliation master data including a department code column that stores information identifying a position in each department of an organization that is responsible for applying for or approving the transfer of assets, and a person information column that stores information identifying a person assigned to a position that is responsible for applying for or approving the transfer of assets; Stage approval master data including a plurality of records corresponding to a plurality of approval stages, in which provisional approver information representing a provisional approver is stored in a provisional approver information column storing a position responsible for approval at the transfer destination in a record corresponding to the approval stage in the transfer destination department among the plurality of records; is accessible to The control unit a destination approver identification processing means for identifying a destination approver who is an approver responsible for approval in the destination department by referring to the department master data and the affiliation master data based on asset transfer application information including the destination department input by the applicant, and creating applicant-specific approver master data including a destination approver identification information column that stores information identifying the destination approver; a workflow data creation processing means for creating workflow data for performing an approval workflow based on the applicant-specific approver master data; To have A business support device characterized by the above.

2. The asset transfer application information includes information identifying a first transfer destination approval position that will be initially responsible for approval in the transfer destination department, The destination approver specification processing means By referring to the affiliation master data using information identifying the first transfer destination approval position as a key, a first transfer destination approver who is a person assigned to the first transfer destination approval position is identified; By referring to the department master data using information specifying the first destination approval position as a key, information specifying a second destination approval position that will be the next to be responsible for approval in the destination department is acquired, and by referring to the affiliation master data using information specifying the second destination approval position as a key, a second destination approver who is a person assigned to the second destination approval position is identified; 2. The business support device according to claim 1, wherein:

3. The control unit An approval route maintenance processing means for displaying an approval route maintenance screen for inputting information on a plurality of approval stages, and for creating the stage approval master data including records corresponding to the approval stages in the transfer source department, records corresponding to the approval stages in the transfer destination department, and records corresponding to the approval stages in the final approval department, based on the information inputted on the approval route maintenance screen. Further comprising:

2. The business support device according to claim 1, wherein:

4. The control unit An organization / department affiliation maintenance processing means for displaying an organization / department affiliation maintenance screen including an organization chart related to application and approval of asset transfer based on the department master data and an input field for inputting information to be stored in the affiliation master data, and creating the affiliation master data based on information input in the input field. Further comprising:

2. The business support device according to claim 1, wherein:

5. The control unit Approval route specification processing means for creating preparatory work data including the same number of records as the number of records corresponding to the approval stages in the destination department in the stage approval master data, and including an approver column for each applicant storing temporary approver information, and a destination approver specification information column for storing information specifying the destination approver. Further provided with The destination approver specification processing means storing the identified destination approver in a destination approver identification information column of the preparatory work data, and creating the applicant-specific approver master data based on the preparatory work data; 2. The business support device according to claim 1, wherein:

6. A business support method executed by a business support device having a control unit that supports approval work when assets of a transfer source department are transferred to a transfer destination department, The business support device Department master data including organizational chart information for asset transfer requests and approvals; Affiliation master data including a department code column that stores information identifying a position in each department of an organization that is responsible for applying for or approving the transfer of assets, and a person information column that stores information identifying a person assigned to a position that is responsible for applying for or approving the transfer of assets; Stage approval master data including a plurality of records corresponding to a plurality of approval stages, in which provisional approver information representing a provisional approver is stored in a provisional approver information column storing a position responsible for approval at the transfer destination in a record corresponding to the approval stage in the transfer destination department among the plurality of records; is accessible to Executed by the control unit, a destination approver identification step of identifying a destination approver who is an approver responsible for approval in the destination department by referring to the department master data and the affiliation master data based on asset transfer application information including the destination department input by the applicant, and creating applicant-specific approver master data including a destination approver identification information column that stores information identifying the destination approver; a workflow data creation step of creating workflow data for performing an approval workflow based on the applicant-specific approver master data; containing, A business support method characterized by the above.

7. A business support program to be executed by a business support device having a control unit that supports approval work when assets of a transfer source department are transferred to a transfer destination department, The business support device Department master data including organizational chart information for asset transfer requests and approvals; Affiliation master data including a department code column that stores information identifying a position in each department of an organization that is responsible for applying for or approving the transfer of assets, and a person information column that stores information identifying a person assigned to a position that is responsible for applying for or approving the transfer of assets; Stage approval master data including a plurality of records corresponding to a plurality of approval stages, in which provisional approver information representing a provisional approver is stored in a provisional approver information column storing a position responsible for approval at the transfer destination in a record corresponding to the approval stage in the transfer destination department among the plurality of records; is accessible to To cause the control unit to execute a destination approver identification step of identifying a destination approver who is an approver responsible for approval in the destination department by referring to the department master data and the affiliation master data based on asset transfer application information including the destination department input by the applicant, and creating applicant-specific approver master data including a destination approver identification information column that stores information identifying the destination approver; a workflow data creation step of creating workflow data for performing an approval workflow based on the applicant-specific approver master data; containing, A business support program that features:

Images