JP6750982B2 - Authority control device, authority control method, and authority control program - Google Patents

Description

The present invention relates to an authority control device, an authority control method, and an authority control program.

As a technology related to authority control of budget organization work, for example, Patent Document 1 discloses an access authority database that defines access authority (search, registration, change, delete, etc.) to a budget database and the like for each department to which a user belongs. It is disclosed.
Further, in the embodiment described in Patent Document 1, “search” is permitted to any department in the access authority database, and “register, change, delete” is permitted only to the applying department. The data structure is set.

JP, 2005-258733, A

However, in the conventional technology, the budget approval authority is unified to one department, and the budget responsible department and the application flow are set for each subject, and the same department is set in multiple layers of the application flow. There was a problem that I could not do it.

The present invention has been made in view of the above problems, and provides an authority control device, an authority control method, and an authority control program capable of setting hierarchies, departments, and authorities for each budget type. To aim.

In order to solve the above problems and achieve an object, an authority control device according to the present invention is an authority control device including a control unit and a storage unit, wherein the storage unit includes user ID data and a user group code. A first master data table storing records including data, and a second master data table storing records including budget type code data, hierarchy level data, user group code data, and responsible department user group code data, And the control unit refers to the first master data table, refers to the second master data table, and a group code acquisition unit that acquires user group code data corresponding to the input user ID. Data acquisition means for acquiring budget type code data, hierarchy level data, and responsible department user group code data corresponding to the acquired user group code data, and based on the data acquired by the data acquisition means. , A data deciding means for deciding a combination of budget type, department and subject available to the user, and a screen for inputting or displaying the budget type, department and subject based on the combination decided by the data deciding means And a screen control unit for controlling the screen.

Also, in the authority control device according to the present invention, in the authority control device, the data acquisition unit further refers to the second master data table, and hierarchy level data equal to or higher than a value of the acquired hierarchy level data. And a record having the same user group code data as the acquired user group code data in the responsible department user group code is acquired.

Further, in the authority control device according to the present invention, in the authority control device, the storage unit further stores a third master data table that stores a record including user group code data and department code data, and the control unit Is further provided with a department code acquisition unit for referring to the third master data table and acquiring department code data corresponding to the user group code data acquired by the data acquisition unit.

Also, in the authority control device according to the present invention, in the authority control device, the screen control means performs the selection according to a budget type selected from budget types included in the combination determined by the data determination means. It is characterized in that the departments and subjects included in the combination including the selected budget type are controlled so that they can be selected.

The authority control device according to the present invention is characterized in that, in the authority control device, the budget type is a group of account items or set items.

An authority control method according to the present invention is an authority control method executed by an information processing device including a control unit and a storage unit, wherein the storage unit stores a record including user ID data and user group code data. Storing a first master data table for storing and a second master data table for storing records including budget type code data, hierarchy level data, user group code data, and responsible department user group code data, and A group code acquisition step, which is executed by the control unit, refers to the first master data table to obtain user group code data corresponding to the input user ID, and refers to the second master data table, Data acquisition step of acquiring budget type code data, hierarchy level data, and responsible department user group code data corresponding to the acquired user group code, and the acquired budget type code data, hierarchy level data, and responsibility Input the budget type, department and subject based on the data determination step that determines the combination of budget type, department and subject available to the user based on the department user group code data, and the combination determined in the data determination step. Or a screen control step of controlling a screen to be displayed.

Further, the authority control program according to the present invention is an authority control program for causing an information processing apparatus including a control unit and a storage unit to execute, and the storage unit includes a record including user ID data and user group code data. And a second master data table for storing records including budget type code data, hierarchy level data, user group code data, and responsible department user group code data. A group code acquisition step for acquiring the user group code data corresponding to the input user ID by referring to the first master data table, which is executed by the control unit, and referring to the second master data table. A data acquisition step of acquiring budget type code data, hierarchy level data, and responsible department user group code data corresponding to the acquired user group code; and the acquired budget type code data, hierarchy level data, And a responsible department user group code data, a data determining step for determining a combination of a budget type, a department and an item available to the user, and a budget type, a department and an item based on the combination determined in the data determining step. And a screen control step of controlling a screen for inputting or displaying.
It is characterized by

According to the present invention, it is possible to set the hierarchy, department, and authority for each budget type.

FIG. 1 is a block diagram showing an example of the configuration of the authority control device according to the embodiment. FIG. 2 is a diagram showing an example of the user master data table. FIG. 3 is a diagram showing an example of the user group master data table. FIG. 4 is a diagram showing an example of a user group member master data table. FIG. 5 is a diagram showing an example of the department master data table. FIG. 6 is a diagram showing an example of a user group belonging department master data table. FIG. 7 is a diagram showing an example of the budget type master data table. FIG. 8 is a diagram showing an example of the account item master data table. FIG. 9 is a diagram showing an example of the budget type element master data table. FIG. 10 is a diagram showing an example of a user group hierarchy master data table for each budget type. FIG. 11 is a diagram showing an example of a non-operating profit/loss budget application flow. FIG. 12 is a diagram showing an example of an application flow for a general administrative expense budget. FIG. 13 is a diagram showing an example of a sales application flow. FIG. 14 is a diagram showing an example of the budget formation department security table. FIG. 15 is a flowchart showing an example of processing of the authority control device according to the embodiment. FIG. 16 is a diagram showing an example of a user group member master data table. FIG. 17 is a diagram showing an example of a budget type-specific user group hierarchy master data table. FIG. 18 is a diagram showing an example of the budget formation department security table. FIG. 19 is a diagram showing an example of a user group belonging department master data table. FIG. 20 is a diagram showing an example of the budget formation department security table. FIG. 21 is a diagram showing an example of the budget type element master data table. FIG. 22 is a diagram showing an example of the budget input screen. FIG. 23 is a diagram showing an example of a user group member master data table. FIG. 24 is a diagram showing an example of a budget type-based user group hierarchy master data table. FIG. 25 is a diagram showing an example of the budget formation department security table. FIG. 26 is a diagram showing an example of a user group belonging department master data table. FIG. 27 is a diagram showing an example of the budget compilation department security table. FIG. 28 is a diagram showing an example of the budget type element master data table. FIG. 29 is a diagram showing an example of the budget input screen. FIG. 30 is a diagram showing an example of a user group member master data table. FIG. 31 is a diagram showing an example of a user group hierarchy master data table for each budget type. FIG. 32 is a diagram showing an example of the budget compilation department security table. FIG. 33 is a diagram showing an example of a user group belonging department master data table. FIG. 34 is a diagram showing an example of the budget formation department security table. FIG. 35 is a diagram showing an example of a user group belonging department master data table. FIG. 36 is a diagram showing an example of the budget formation department security table. FIG. 37 is a diagram showing an example of the budget type element master data table. FIG. 38 is a diagram showing an example of the budget input screen. FIG. 39 is a diagram showing an example of a user group member master data table. FIG. 40 is a diagram showing an example of a budget type-specific user group hierarchy master data table. FIG. 41 is a diagram showing an example of the budget formation department security table. FIG. 42-1 is a diagram showing an example of a user group hierarchy master data table by budget type. FIG. 42-2 is a diagram for explaining record reacquisition of the user group hierarchy master data table by budget type. FIG. 43 is a diagram showing an example of the budget formation department security table. FIG. 44 is a diagram showing an example of a user group belonging department master data table. FIG. 45 is a diagram showing an example of the budget compilation department security table. FIG. 46 is a diagram showing an example of the budget type element master data table. FIG. 47 is a diagram showing an example of the budget input screen.

Embodiments of the present invention will be described in detail with reference to the drawings. The present invention is not limited to this embodiment.

[1. Overview]
The present embodiment relates to authority control (application/approval/registration/change/deletion/inquiry) of departments/subjects in budgeting work. According to this embodiment, the budget responsible department can be set for each subject in the budgeting work.

With the conventional system, even if the responsible departments and responsible departments within the company are not standardized for each budget item, the accounting department has final approval or has the entire authority. I could only do it. Also, if the accounting department was set to have reference authority for all departments and subjects, the budget of the accounting department could not be referenced by other departments. Moreover, although the reference authority of the department or the subject was set for each user, the same department could not be set for multiple layers of the application flow, and the hierarchy of the application flow could not be set for each subject.

Therefore, the present embodiment provides an authority control device capable of setting the hierarchy, department, and authority for each budget type. For example, since it is assumed that the general affairs department approves the application made by the accounting department, and then the accounting department approves it, the accounting department always performs final approval in operation. In addition, because the same department appears in multiple hierarchies, and because it was not possible to express the WF (workflow) hierarchy for each subject, a unique WF function for budget management is realized so that these can be done. .. It should be noted that the same department can be set up to twice in the hierarchy, but it can also be set up, for example, three times or more.

In this embodiment, first, the department to which the login user belongs is set. Next, create a budget type (eg non-operating profit/loss, general administrative expenses) according to the account item. Next, for the budget type, the setting of the hierarchy level of the application flow, the user group, and the linking of the responsible user group to be the responsible department are made. As a result, the department that can handle the budget type is controlled so that only the department to which the login user belongs or the responsible department can apply, approve, register, change, and inquire. It also controls the accounts that can be handled for each budget type. Regarding the application flow, it is possible to set the application flow for each budget type. For example, the account department (non-operating profit and loss) can be set as the accounting department, and the account department (general administrative expenses) can be set as the general affairs department. If the budget formation is complicated, it is possible for the general affairs department to approve the budget requested by the accounting department, and the accounting department to finally approve the budget.

[2. Constitution]
An example of the configuration of the authority control device according to the present embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the configuration of the authority control device.

The authority control device 100 is a commercially available desktop personal computer. Note that the authority control device 100 is not limited to a stationary information processing device such as a desktop personal computer, but is a portable type such as a commercially available notebook personal computer, PDA (Personal Digital Assistants), smartphone, or tablet personal computer. It may be an information processing device.

The authority control device 100 includes a control unit 102, a communication interface unit 104, a storage unit 106, and an input/output interface unit 108. The respective units included in the authority control device 100 are communicably connected via an arbitrary communication path.

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

The storage unit 106 stores various databases, a master data table (hereinafter, the master data table may be simply referred to as a master), a table, a file, and the like. Further, the storage unit 106 includes a user master 106a, a user group master 106b, a user group member master 106c, a department master 106d, a user group belonging department master 106e, a budget type master 106f, an account item master 106g, a budget type element master 106h, and a budget. A type-specific user group hierarchy master 106i and a budget organization department security table 106j are stored. Further, the storage unit 106 stores a computer program for giving instructions to a CPU (Central Processing Unit) in cooperation with an OS (Operating System) to perform various processes. As the storage unit 106, for example, a memory device such as a RAM (Random Access Memory) and a ROM (Read Only Memory), a fixed disk device such as a hard disk, a flexible disk, and an optical disk can be used.

The user master 106a stores a record including user ID data and user name data, and is used when setting a login user. The user group master 106b stores records including user group code data and user group name data, and is used when setting the group to which the logged-in user belongs. The user group member master 106c stores records including user ID data and user group code data, and is used when setting the association between the user ID and the user group code. The department master 106d stores records including department code data and department name data, and is used when setting a department. The user group belonging department master 106e stores records including user group code data and department code data, and is used when setting the association between the user group code and the department code. The budget type master 106f stores records including budget type code data and budget type name data, and is used when setting a budget type used for budget compilation. The budget type is a grouping of subjects, and for example, account items, budget items, expense items, and the like can be grouped. The account item master 106g stores records including account item code data and account item name data, and is used when setting an account item. The budget type element master 106h stores records including budget type code data and account item data, and is used when setting an account item that is an element that constitutes a budget type. The budget type-specific user group hierarchy master 106i stores records including budget type code data, hierarchy level data, user group code data, and responsible user group code data. The budget type-specific user group hierarchy master 106i can set the approval flow for each budget type, sets the user group code that is the responsible department in the responsible user group code, and converts it to the department by the user group belonging department master 106e. This is the application flow for the department.

The budget organization department security table 106j is a table used during program processing, and no record is stored when the program is started.

An input device 112 and an output device 114 are connected to the input/output interface unit 108. As the output device 114, a speaker or a printer can be used in addition to a screen or monitor (including a home-use television). As the input device 112, a keyboard, a mouse, a microphone, and a monitor that realizes a pointing device function in cooperation with the mouse can be used. In the following, the output device 114 may be described as the screen 114 or the monitor 114, and the input device 112 may be described as the keyboard 112 or the mouse 112.

The control unit 102 is a CPU or the like that totally controls the authority control device 100. The control unit 102 includes a setting unit 102a, a determination unit 102b, and a screen control unit 102c. Further, the control unit 102 has an internal memory for storing a control program such as an OS, a program defining various processing procedures, and required data, and various information based on the stored programs. Execute the process.

When the budget application is input, the setting unit 102a sets the responsible department according to the type of budget requested, and includes the group to which the user who applied for the budget belongs in the lower rank and the group set as the responsible department in the higher rank. Set the hierarchical structure and set the application flow according to the set hierarchical structure.

The deciding unit 102b refers to the user group member master 106c, refers to the group code acquisition unit that acquires the user group code data corresponding to the input user ID, and refers to the budget type-specific user group hierarchy master 106i to refer to the group. Based on the data acquisition means for acquiring the budget type code data, the hierarchy level data, and the responsible department user group code data corresponding to the user group code data acquired by the code acquisition means, and the data acquired by the data acquisition means , A data determination means for determining the combination of budget type, department, and subject available to the user.

The screen control unit 102c controls the screen 114 for inputting or displaying the budget type, department, and subject based on the combination determined by the determination unit 102b.

[3. Concrete example]
A specific example of this embodiment will be described with reference to FIGS. 2 to 47. 2 to 10 are diagrams showing examples of various masters. 11 to 13 are diagrams showing examples of various application flows. FIG. 14 is a diagram showing an example of a data table used for processing. FIG. 15 is a flowchart showing an example of the processing in this embodiment. 16 to 47 are diagrams for explaining the process in this embodiment.

3-1. Master Set in Advance In this embodiment, the setting unit 102a creates various masters set in advance, and the various masters are stored in the storage unit 106. FIG. 2 is a diagram showing an example of the user master 106a. As shown in FIG. 2, the user master 106a stores a record including user ID data and user name data, and is used when setting a login user. As the user ID data, for example, "USER1", "USER2", "USER3", and "USER4" are user name data "○ Accounting", "○○ General Affairs", "○○ Taro", and "○○". Hanako” is associated with each item.

FIG. 3 is a diagram showing an example of the user group master 106b. As shown in FIG. 3, the user group master 106b stores records including user group code data and user group name data, and is used when setting the group to which the logged-in user belongs. As the user group code data, for example, "USERGROUP001", "USERGROUP002", "USERGROUP003", and "USERGROUP004" are user group name data "final responsible department", "responsible department", "operator 1", and "operator 2". ], respectively.

FIG. 4 is a diagram showing an example of the user group member master 106c. As shown in FIG. 4, the user group member master 106c stores records including user ID data and user group code data, and is used when setting the association between the user ID and the user group code. As the user ID data, "USER1", "USER2", "USER3", and "USER4" are associated with user group code data "USERGROUP001", "USERGROUP002", "USERGROUP003", and "USERGROUP004".

FIG. 5 is a diagram showing an example of the department master 106d. As shown in FIG. 5, the department master 106d stores records including department code data and department name data, and is used when setting a department. As the department code data, for example, “BUMON1, “BUMON2”, “BUMON3”, and “BUMON4” are associated with department name data “accounting department”, “general affairs department”, “system department”, and “sales department”. Has been.

FIG. 6 is a diagram showing an example of the user group belonging department master 106e. As shown in FIG. 6, the user group belonging department master 106e stores records including user group code data and department code data, and is used when setting the association between the user group code and the department code. As the user group codes, "USERGROUP001", "USERGROUP002", "USERGROUP003", and "USERGROUP004" are respectively associated with department code data "BUMON1, "BUMON2", "BUMON3", and "BUMON4".

FIG. 7 is a diagram showing an example of the budget type master 106f. As shown in FIG. 7, the budget type master 106f stores records including budget type code data and budget type name data, and is used when setting a budget type used for budget compilation. The budget type is a grouping of subjects, and for example, account items, budget items, expense items, and the like can be grouped. As the budget type code data, for example, “Y001”, “Y002”, and “Y003” are associated with the budget type name data “non-operating profit/loss budget”, “general administrative expense budget”, and “sales”, respectively. There is.

FIG. 8 is a diagram showing an example of the account title master 106g. As shown in FIG. 8, the account item master 106g stores records including account item code data and account item name data, and is used when setting an account item. As the account item data, for example, “K001”, “K002”, “K003”, “K004”, “K005”, and “K006” have account item names “item A”, “item B”, and “item C”. , “Subject D”, “Subject E”, and “Subject F”, respectively.

FIG. 9 is a diagram showing an example of the budget type element master 106h. As shown in FIG. 9, the budget type element master 106h stores records including budget type code data and account item data, and is used when setting an account item that is an element that constitutes a budget type.

FIG. 10 is a diagram showing an example of a budget type-based user group hierarchy master 106i. As shown in FIG. 10, the budget type-specific user group hierarchy master 106i stores records including budget type code data, hierarchy level data, user group code data, and responsible user group code data. The budget type-specific user group hierarchy master 106i can set the approval flow for each budget type, sets the user group code that is the responsible department in the responsible user group code, and converts it to the department by the user group belonging department master 106e. This is the application flow for the department.

Next, the application flow will be described. FIG. 11 is a diagram showing an example of a non-operating profit/loss budget application flow. The budget type code of the non-operating profit/loss budget is “Y001”. As shown in FIG. 11, in the non-operating profit/loss budget application flow, the application department is a system department and the responsible department is an accounting department.

FIG. 12 is a diagram showing an example of an application flow for a general administrative expense budget. The budget type code of the general administrative budget is “Y002”. As shown in FIG. 12, in the general administrative budget budget application flow, the application department is a sales department and the like, and the responsible department is a general affairs department and an accounting department.

FIG. 13 is a diagram showing an example of a sales application flow. The budget type code for the sales amount is “Y003”. As shown in FIG. 13, in the sales application flow, the application department is the accounting department, the sales department, etc., and the responsible department is the general affairs department and the accounting department.

3-2. Table Used During Program Processing Next, a table used during program processing will be described. FIG. 14 is a diagram showing an example of the budget formation department security table. As shown in FIG. 14, the budget organization department security table can store records including login user group data, department conversion user group data, budget type code data, and department code data. The budget formation department security table is a table used during program processing, and no record is stored when the program is started.

3-3. System Control Flow Next, the system control flow in this embodiment will be described. FIG. 15 is a flowchart showing an example of processing of the authority control device 100 according to this embodiment. As shown in FIG. 15, in step S1, the determination unit 102b searches the user group member master 106c with the login user ID and acquires the user group code.
Next, in step S2, the determination unit 102b searches the budget type-specific user group hierarchy master 106i with the user group code acquired in step S1 and acquires the corresponding record.
Next, in step S3, the determination unit 102b adds the record acquired in step S2 to the budget organization department security table 106j.
Subsequently, in step S4, the determination unit 102b searches for a record in the budget type-specific user group hierarchy master 106i, the hierarchy level data is a value equal to or higher than the hierarchy level data of the record acquired in step S2, and A record in which the user group code acquired in step S2 is set as the responsible user group code is acquired again.
Next, in step S5, the determination unit 102b sets the user group code acquired in step S1 as a login user group in the budget organization department security table 106j, and the user group included in the record acquired in step S2. The code is set as the department conversion user group, the budget type code included in the record obtained in step S2 is set as the budget type code, and the user group belonging department master 106e is searched in the department conversion user group to obtain the department code. The acquired department code is updated to the budget formation department security table 106j.
In step S6, the determination unit 102b searches the budget type element master 106h with the budget type code set in step S5, and selects the account item code from the record including the same budget type code as the budget type code set in step S5. To get.
Finally, in step S7, the screen control unit 102c causes the budget type, department, and item corresponding to the budget type code and department code existing in the budget organization department security table 106j and the account item code acquired in step S6. The screen 114 is controlled so that only the combination of

3-3-1. When Taro XX logs in Next, an example of processing when Taro XX (user ID “USER3”) who is an operator of the system unit in the authority control device 100 according to the present embodiment logs in will be described. FIG. 16 is a diagram showing an example of the user group member master 106c. FIG. 17 is a diagram showing an example of the budget type-based user group hierarchy master 106i. 18 and 20 are diagrams showing an example of the budget compilation department security table 106j. FIG. 19 is a diagram showing an example of the user group belonging department master 106e. FIG. 21 is a diagram showing an example of the budget type element master 106h. FIG. 22 is a diagram showing an example of the budget input screen 114.

In step S1, as shown in FIG. 16, the login user ID “USER3” is searched for the user group member master 106c, and the user group code “USERGROUP003” is acquired from the record M1 including “USER3”.
Next, in step S2, as shown in FIG. 17, the user group code “USERGROUP003” acquired in step S1 is searched for the budget type-specific user group hierarchy master 106i, and a record M2 including “USERGROUP003” is acquired. ..
Next, as shown in FIG. 18, in step S3, the record M2 acquired in step S2 is added to the budget organization department security table 106j (M3).
Further, in step S4, for the budget type-specific user group hierarchy master 106i, a record in which the hierarchy level “20” or higher of the record M2 acquired in step S2 and the responsible user group code set to “USERGROUP003” are set. Although it is searched, there is no corresponding record as shown in FIG.
In step S5, as shown in FIG. 19, the user group belonging department master 106e is searched for in the department conversion user group “USERGROUP003” included in the record M3 of the budget organization department security table 106j shown in FIG. The department code “BUMON3” is acquired from the record M4 including USERGROUP003, and the acquired department code “BUMON3” is updated in the budget compilation department security table 106j as shown in FIG.
In step S6, as shown in FIG. 21, the budget type code “Y001” set in step S5 is searched for the budget type element master 106h, and the account item code “K001” is calculated from the record M6 including the budget type code “Y001”. , “K002”, and “K003” are acquired.
Finally, in step S7, as shown in FIG. 22, the budget type code “Y001” and the department code “BUMON3” existing in the budget organization department security table 106j in FIG. 20 and the account title code “K001” acquired in step S6. , "K002", and "K003", the budget input screen 114 is controlled so that only a combination of budget items, departments, and subjects can be handled.

3-3-2. When Hanako ○○ logs in Next, in the authority control device 100 according to the present embodiment, an example of processing when Hanako ○○ (user ID “USER4”) who is the operator of the sales department logs in will be described. FIG. 23 is a diagram showing an example of the user group member master 106c. FIG. 24 is a diagram showing an example of the user group hierarchy master 106i for each budget type. 25 and 27 are diagrams showing an example of the budget compilation department security table 106j. FIG. 26 is a diagram showing an example of the user group belonging department master 106e. FIG. 28 is a diagram showing an example of the budget type element master 106h. FIG. 29 is a diagram showing an example of the budget input screen 114.

In step S1, as shown in FIG. 23, the login user ID “USER4” is searched for the user group member master 106c, and the user group code “USERGROUP004” is acquired from the record M7 including “USER4”.
Next, in step S2, as shown in FIG. 24, the user group code "USERGROUP004" acquired in step S1 is searched for the budget type-specific user group hierarchy master 106i, and records M8 and M9 including "USERGROUP004" are searched. get.
Next, in step S3, as shown in FIG. 25, the records M8 and M9 acquired in step S2 are added to the budget organization department security table 106j (M10).
Furthermore, in step S4, the hierarchy level "30" or higher of the records M8 and M9 acquired in step S2 and the responsible user group code "USERGROUP004" are set for the budget type-specific user group hierarchy master 106i. Although a record is searched, there is no corresponding record as shown in FIG.
In step S5, as shown in FIG. 26, the department conversion user group “USERGROUP004” included in the record M10 of the budget formation department security table 106j shown in FIG. 25 is searched for the user group belonging department master 106e, and “ The department code "BUMON4" is acquired from the record M11 including "USERGROUP004", and the acquired department code "BUMON4" is updated in the budget compilation department security table 106j as shown in FIG.
In step S6, as shown in FIG. 28, the budget type element master 106h is searched with the budget type codes “Y002” and “Y003” set in step S5, and the account is recorded from the record M12 including the budget type code “Y002”. The account code “K004”, “K005”, and “K006” and the account item codes “K007”, “K008”, and “K009” are acquired from the record M13 including the budget type code “Y003”.
Finally, in step S7, as shown in FIG. 29, the budget type codes “Y002” and “Y003” existing in the budget organization department security table 106j of FIG. 27, the department code “BUMON3”, and the budget type code “Y002”. For the account type codes “K004”, “K005”, and “K006” obtained in step S6, and the account type codes “K007”, “K008” obtained in step S6 for the budget type code “Y003”. , And “K009”, the budget input screen 114 is controlled so that only a combination of budget items, departments, and subjects can be handled. That is, when “Y002” is designated as the budget type, only “K004”, “K005”, and “K006” can be used as subjects. When "Y003" is designated as the budget type, only "K007", "K008", and "K009" can be used as subjects.

3-3-3. When XX General Affairs Logs In Next, an example of processing when XX general affairs (user ID “USER2”) logs in in the authority control device 100 according to the present embodiment will be described. FIG. 30 is a diagram showing an example of the user group member master 106c. 31 and 33 are diagrams showing an example of the budget type-specific user group hierarchy master 106i. 32, 34, and 36 are diagrams showing an example of the budget compilation department security table 106j. FIG. 35 is a diagram illustrating an example of the user group belonging department master 106e. FIG. 37 is a diagram showing an example of the budget type element master 106h. FIG. 38 is a diagram showing an example of the budget input screen 114.

In step S1, as shown in FIG. 30, the login user ID “USER2” is searched for the user group member master 106c, and the user group code “USERGROUP002” is acquired from the record M14 including “USER2”.
Next, in step S2, as shown in FIG. 31, the user group code “USERGROUP002” acquired in step S1 is searched for the budget type-specific user group hierarchy master 106i, and records M15 and M16 including “USERGROUP002” are searched. get.
Next, in step S3, as shown in FIG. 32, the records M15 and M16 acquired in step S2 are added to the budget organization department security table 106j (M17).
Further, in step S4, as shown in FIG. 33, with respect to the budget type-specific user group hierarchy master 106i, the hierarchy level “20” or higher of the records M15 and M16 acquired in step S2 and the responsible user group code are “. A record in which "USERGROUP002" is set is searched, and the corresponding records M18 and M19 are reacquired and added as a record M20 to the budget compilation department security table 106j as shown in FIG.
In step S5, as shown in FIG. 35, in the department conversion user groups “USERGROUP001”, “USERGROUP002”, and “USERGROUP004” included in the records M17 and M20 of the budget organization department security table 106j shown in FIG. 34, The user group belonging department master 106e is searched, the department codes "BUMON1" and "BUMON2" are acquired from the record M21 including "USERGROUP001" and "USERGROUP002", and the department code "BUMON4" is acquired from the record M22 including "USERGROUP004". 36, the acquired department codes “BUMON1”, “BUMON2”, and “BUMON4” are respectively updated in the budget organization department security table 106j.
In step S6, as shown in FIG. 37, the budget type element master 106h is searched with the budget type codes “Y002” and “Y003” set in step S5, and the account is recorded from the record M24 including the budget type code “Y002”. The account code “K004”, “K005”, and “K006” and the account code “K007”, “K008”, and “K009” are acquired from the record M25 including the budget type code “Y003”.
Finally, in step S7, as shown in FIG. 38, based on the combination of the department code and the account item code respectively corresponding to the budget type codes “Y002” and “Y003” existing in the budget organization department security table 106j of FIG. Then, the budget input screen 114 is controlled. That is, when the budget type code “Y002” is specified, it corresponds to the department codes “BUMON2” and “BUMON4” and the account item codes “K004”, “K005”, and “K006” acquired in step S6. , Only budget subjects, departments, and subject combinations are available. If the budget type code “Y003” is designated, the department codes “BUMON1”, “BUMON2”, and “BUMON4”, and the account item codes “K007”, “K008”, and “K009” acquired in step S6. Only the combination of budget subject, department, and subject corresponding to "" can be used.

3-3-4. When XX Accounting Logs In Next, an example of processing when XX accounting (user ID “USER1”) logs in in the authority control device 100 according to the present embodiment will be described. In this embodiment, the accounting department is set so that it can refer to all budgets. FIG. 39 is a diagram showing an example of the user group member master 106c. 40 and 42-1 are diagrams showing an example of the budget type-specific user group hierarchy master 106i. 41, 43, and 45 are diagrams showing an example of the budget compilation department security table 106j. FIG. 42-2 is a diagram for explaining record reacquisition of the user group hierarchy master data table by budget type. FIG. 44 is a diagram illustrating an example of the user group belonging department master 106e. FIG. 46 is a diagram showing an example of the budget type element master 106h. FIG. 47 is a diagram showing an example of the budget input screen 114.

In step S1, as shown in FIG. 39, the login user ID “USER1” is searched for the user group member master 106c, and the user group code “USERGROUP001” is acquired from the record M26 including “USER1”.
Next, in step S2, as shown in FIG. 40, the user group code "USERGROUP001" acquired in step S1 is searched for the budget type-specific user group hierarchy master 106i, and records M27 to M30 including "USERGROUP001" are searched. get.
Next, in step S3, as shown in FIG. 41, the records M27 to M30 acquired in step S2 are added to the budget organization department security table 106j (M31).
Here, in this embodiment, the accounting section is set so that all budgets can be referred to.
Therefore, in step S4, as shown in FIG. 42-1 with respect to the budget type-specific user group hierarchy master 106i, based on the records M27 to M30 acquired in step S2, the hierarchy level is “10” or higher, and the responsibility is set. A record in which "USERGROUP001" is set in the user group code is searched, and the corresponding record is acquired again.
Here, as shown in FIG. 42-2, the record in which the responsible user group code is set to “USERGROUP001” is a record in which the user group code is set to “USERGROUP002”, and then the responsible user. A record in which "USERGROUP002" is set in the group code is acquired again. A record in which "USERGROUP002" is set in the responsible user group code is a record in which "USERGROUP003" is set in the user group code, and subsequently, a record in which "USERGROUP003" is set in the responsible user group code. To get again. By repeating the above, the records M32 to M35 of FIG. 42-1 are reacquired, and as shown in FIG. 43, added to the budget compilation department security table 106j as a record M36. Note that a record in which the responsible user group code is set to “USERGROUP001” means that the responsible department is the accounting department, and a record in which the responsible user group code is set to “USERGROUP002” indicates that the responsible department is in charge of general affairs. Means a part.
In step S5, as shown in FIG. 44, department conversion user groups “USERGROUP001”, “USERGROUP002”, “USERGROUP003”, and “USERGROUP004” included in the records M31 and M36 of the budget organization department security table 106j shown in FIG. 43. , The user group belonging department master 106e is searched for, and the department codes “BUMON1”, “BUMON2”, “BUMON3”, and “BUMON4” are acquired from the record M37, and the acquired department codes are obtained as shown in FIG. “BUMON1”, “BUMON2”, BUMON3”, and “BUMON4” are updated in the budget compilation department security table 106j (M38).
In step S6, as shown in FIG. 46, the budget type element master 106h is searched with the budget type codes "Y001", "Y002" and "Y003" set in step S5, and the budget type code "Y001" is included. Account item codes “K001”, “K002”, and “K003” from record M39, account item codes “K004”, “K005”, and “K006” from record M40 including budget type code “Y002” Account item codes “K007”, “K008”, and “K009” are acquired from the record M41 including the code “Y003”.
Finally, in step S7, as shown in FIG. 47, department codes and account items respectively corresponding to the budget type codes “Y001”, “Y002”, and “Y003” existing in the budget compilation department security table 106j of FIG. 45. The budget input screen 114 is controlled based on the combination of codes. That is, when the budget type code “Y001” is designated, it corresponds to the department codes “BUMON1” and “BUMON3” and the account item codes “K001”, “K002”, and “K003” acquired in step S6. Only budget, budget, department, and subject combinations can be used. If the budget type code “Y002” is designated, the department codes “BUMON1”, “BUMON2”, and “BUMON4” and the account item codes “K004”, “K005”, and “K006” acquired in step S6 Only combinations of budget subjects, departments, and subjects that correspond to are available. If the budget type code “Y003” is designated, the department codes “BUMON1”, “BUMON2”, and “BUMON4”, and the account item codes “K007”, “K008”, and “K009” acquired in step S6. Only the combination of budget subject, department, and subject corresponding to "and" can be used.

[4. Other Embodiments]
The present invention may be implemented in various different embodiments within the scope of the technical idea described in the claims other than the above-described embodiments.

For example, of the processes described in the embodiments, all or part of the processes described as being automatically performed may be manually performed, or all the processes described as manually performed may be performed. Alternatively, a part thereof can be automatically performed by a known method.

In addition, unless otherwise specified, processing procedures, control procedures, specific names, information including parameters such as registration data and search conditions for each processing, screen examples, and database configurations shown in this specification and the drawings are excluded. Can be changed arbitrarily.

Further, regarding the authority control device 100, the constituent elements shown in the drawings are functionally conceptual ones, and do not necessarily have to be physically configured as illustrated.

For example, the processing functions of the authority control device 100, particularly the respective processing functions performed by the control unit, may be realized in whole or in part by a CPU and a program interpreted and executed by the CPU. Alternatively, the hardware may be realized by wired logic. The program is recorded in a non-transitory computer-readable recording medium that includes programmed instructions for causing the information processing apparatus to execute the processing described in the present embodiment, and if necessary, the authority control device. Mechanically read to 100. That is, in a storage unit such as a ROM or a hard disk drive (HDD), a computer program for giving a command to the CPU in cooperation with the OS and performing various processes is recorded. This computer program is executed by being loaded in the RAM, and constitutes a control unit in cooperation with the CPU.

Further, this computer program may be stored in an application program server connected to the authority control device 100 via an arbitrary network, and it is possible to download all or a part of it as necessary. is there.

Further, the program for executing the processing described in the present embodiment may be stored in a non-transitory computer-readable recording medium, or may be configured as a program product. Here, the “recording medium” includes a memory card, a USB (Universal Serial Bus) memory, an SD (Secure Digital) card, a flexible disk, a magneto-optical disk, a ROM, an EPROM (Erasable Programmable Read Only Memory), and an EEPROM (registered). (Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical disk), MO (Magneto-Optical disk), etc. It shall include any "portable physical medium".

The "program" is a data processing method described in any language or description method, and may be in any format such as source code or binary code. Note that the "program" is not necessarily limited to a single configuration, and it achieves its function in cooperation with a distributed configuration of a plurality of modules and libraries, and a separate program represented by an OS. Including things. Note that known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in each device shown in the embodiment, and the installation procedure after reading.

Various databases and the like stored in the storage unit are storage devices such as RAM, ROM and other memory devices, hard disk and other fixed disk devices, flexible disks, and optical disks, and are used for various processes and website provision. It stores programs, tables, databases, files for web pages, etc.

The authority control device 100 may be configured as an information processing device such as a known personal computer or workstation, or may be configured as the information processing device to which any peripheral device is connected. Further, the authority control device 100 may be realized by installing software (including a program, data, or the like) for realizing the processing described in the present embodiment in the device.

Further, the specific form of the device dispersion/integration is not limited to that shown in the drawings, and all or part of the device may be functionally or physically arranged in arbitrary units according to various additions or functional loads. It can be distributed and integrated. That is, the embodiments described above may be implemented in any combination, or the embodiments may be selectively implemented.

The present invention is particularly useful for budgeting work and the like.

100 authority control device 102 control unit 102a setting unit 102b determining unit 102c screen control unit 104 communication interface unit 106 storage unit 106a user master 106b user group master 106c user group member master 106d department master 106e user group belonging department master 106f budget type master 106g Account item master 106h Budget type element master 106i Budget type user group hierarchy master 106j Budget organization department security table 108 Input/output interface 112 Input device 114 Output device 200 Server 300 Network

Claims (7)

An authority control device including a control unit and a storage unit,
The storage unit is
A first master data table storing records including user ID data and user group code data;
A second master data table for storing records including budget type code data, hierarchy level data, user group code data, and responsible department user group code data;
Store
The control unit is
Group code acquisition means for acquiring user group code data corresponding to the input user ID by referring to the first master data table,
Data acquisition means for acquiring budget type code data, hierarchy level data, and responsible department user group code data corresponding to the acquired user group code data by referring to the second master data table;
Data determination means for determining a combination of budget type, department, and subject available to the user based on the data acquired by the data acquisition means;
Screen control means for controlling a screen for inputting or displaying the budget type, department, and subject based on the combination determined by the data determination means;
With
An authority control device characterized by the above. The data acquisition means,
Further, referring to the second master data table, the responsible department is assigned the user group code data which is the layer level data equal to or higher than the value of the acquired layer level data and which is the same as the acquired user group code data. Get the record that has the user group code,
The authority control device according to claim 1, wherein: The storage unit is
Further storing a third master data table storing records including user group code data and department code data,
The control unit is
Further comprising a department code acquisition unit for referring to the third master data table and acquiring department code data corresponding to the user group code data acquired by the data acquisition unit,
The authority control device according to claim 1 or 2, characterized in that. The screen control means,
According to the budget type selected from the budget types included in the combination determined by the data determining means, the departments and subjects included in the combination including the selected budget type are controlled to be selectable.
The authority control device according to any one of claims 1 to 3, wherein: The budget type is a grouping of account items or setting items,
The authority control device according to any one of claims 1 to 4, wherein: A privilege control method executed by an information processing device including a control unit and a storage unit,
The storage unit is
A first master data table storing records including user ID data and user group code data;
A second master data table for storing records including budget type code data, hierarchy level data, user group code data, and responsible department user group code data;
Store
Executed by the control unit,
A group code acquisition step of acquiring user group code data corresponding to the input user ID by referring to the first master data table;
A data acquisition step of acquiring budget type code data, hierarchy level data, and responsible department user group code data corresponding to the acquired user group code with reference to the second master data table;
A data deciding step of deciding a combination of budget type, department and subject available to the user, based on the acquired budget type code data, hierarchy level data, and responsible department user group code data,
Based on the combination determined in the data determination step, a screen control step for controlling the screen for inputting or displaying the budget type, department and subject,
including,
An authority control method characterized by the above. An authority control program to be executed by an information processing device including a control unit and a storage unit,
The storage unit is
A first master data table storing records including user ID data and user group code data;
A second master data table for storing records including budget type code data, hierarchy level data, user group code data, and responsible department user group code data;
Store
In order for the control unit to execute,
A group code acquisition step of acquiring user group code data corresponding to the input user ID with reference to the first master data table;
A data acquisition step of acquiring budget type code data, hierarchy level data, and responsible department user group code data corresponding to the acquired user group code with reference to the second master data table;
A data deciding step of deciding a combination of budget type, department and subject available to the user, based on the acquired budget type code data, hierarchy level data, and responsible department user group code data,
A screen control step for controlling a screen for inputting or displaying the budget type, department, and subject based on the combination determined in the data determination step,
including,
An authority control program characterized in that

Images