JP7180017B1 - UPDATE CONTROL DEVICE, UPDATE CONTROL METHOD, AND UPDATE CONTROL PROGRAM - Google Patents

Abstract

An update control device, an update control method, and an update control program for updating a database with accurate data are provided.
Kind Code: A1 In an update control system, an update control device 1 includes an authority determination unit 33, an approval necessity determination unit 34, and a storage control unit 35. The authority determination unit 33 determines whether or not there is an update authority for the real table. The approval necessity determining unit 34 determines whether or not the data requires the approval of the approver at the time of update. If the user does not have update authority for the real table, or if the real table in which the data requested to be updated is stored is a database that requires the approval of an approver at the time of update, the storage control unit 35 receives the update request. The data stored in the form table different from the actual table is stored in a form table different from the actual table, and when the approver's approval is obtained, the data stored in the form table is transferred to the actual table.
[Selection drawing] Fig. 1

Description

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

2. Description of the Related Art Today, for example, companies and the like have introduced workflow systems that digitize business procedures such as various applications and requests for approval that are performed in the company. Regarding this workflow system, Patent Document 1 (Japanese Unexamined Patent Application Publication No. 2003-108720) discloses a workflow support system.

In the workflow support system disclosed in Patent Document 1, when a preset extraction date arrives, patent application data that matches the preset extraction conditions is transferred from the domestic patent master on the mainframe to the examination on the server. It is read out to the billing DB. After that, using exclusively the data in the request for examination DB (data as of the date of extraction), we will examine whether or not a request for examination is necessary for each application, and we will examine the results of this examination and discover or Corrected errors are also stored exclusively in the examination request DB. The data in this examination request DB is written back to the domestic patent master at a predetermined time. During the period from reading to writing back, the data in the domestic special data master is updated at any time. As a result, it is possible to maintain the stability of data in individual tasks while ensuring the reliability of database data used in various tasks.

JP-A-2003-108720

However, the conventional workflow system treats the input data as immediately valid data, which causes the inconvenience of updating the database with erroneous data.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and aims to provide an update control device, an update control method, and an update control program that enable updating of a database with accurate data.

In order to solve the above-described problems and achieve the object, an update control device according to the present invention includes: an authority determination unit that determines whether or not a user who has made an update request for a real database has the authority to update the real database; Whether or not the real database that stores the requested data is a database that requires an approver's approval at the time of update is determined based on the approval necessity information set in the real database for which the update is requested. Approval Necessity Determining Unit, Determination Result of Authorization Determining Unit, Determination Result Indicates That User Requesting Update to Real Database Is Not Authorized to Update Actual Database, and Approval Necessity Determining Unit If at least one of the determination results indicating that the actual database that stores the data requested to be updated is a database that requires the approval of the approver at the time of update is obtained , the data to be stored in the actual database in response to an update request is stored in a drafting database that is a database different from the actual database, and if the approver's approval is not obtained, the data stored in the drafting database is stored in the actual database and a storage control unit that rejects the update of the data and transfers the data stored in the form issuing database to the real database and stores the data when the approval of the approver is obtained.

Further, in order to solve the above-mentioned problems and achieve the object, an update control method according to the present invention is characterized in that the authority determination unit determines whether or not a user who has made an update request for the real database has the authority to update the real database. and an approval necessity determination unit determines whether or not the real database storing the data requested to be updated is a database requiring the approval of the approver at the time of update. an approval necessity determination step for determining based on the approval necessity information set in the authorization determination step; The determination result indicating that the user is not authorized to update, and the actual database that stores the update-requested data, which is the determination result in the approval necessity determination step, is a database that requires the approval of the approver at the time of update. If at least one of the determination results indicating that the If the approval is not obtained, the update of the actual database with the data stored in the draft database is rejected, and if the approver's approval is obtained, the data stored in the draft database is transferred to the actual database. and a storage control step of transferring and storing.

Further, in order to solve the above-described problems and achieve the object, an update control program according to the present invention provides a computer with an authority to determine whether a user who has made an update request for a real database has the authority to update the real database. The determination unit and the real database storing the data requested to be updated determine whether or not the approval of the approver is required at the time of updating, based on the approval necessity information set in the real database requested to be updated. and a determination result of the authorization determination unit indicating that the user who has made the update request for the real database is a user without update authority for the real database, and At least one of the determination results obtained by the approval necessity determining unit indicating that the actual database storing the update-requested data is a database requiring the approval of the approver at the time of update. If obtained, the data to be stored in the actual database in response to the update request is stored in the form submission database, which is a database different from the actual database. Rejecting the update of the real database with the data obtained from the data, and functioning as a storage control unit that transfers the data stored in the form issuing database to the real database and stores it when the approval of the approver is obtained. do.

ADVANTAGE OF THE INVENTION According to this invention, it is effective in the ability to update a database with correct data.

FIG. 1 is a diagram showing the system configuration of an update control system according to an embodiment. FIG. 2 is a diagram showing an update form of a database of an update control system as a comparative example with respect to the update control system of the embodiment. FIG. 3 is a diagram showing an outline of system operation in the update control system of the embodiment. FIG. 4 is a diagram for explaining settings of an approver for an administrator setting master that is referred to when updating a real table. FIG. 5 is a diagram showing how various types of department or user information registered in the administrator setting master are acquired from other masters and registered in the administrator setting master. FIG. 6 is a diagram for explaining the setting of the table requiring approval for the application type category allocation master referenced when updating the actual table. FIG. 7 is a diagram showing how application types and categories (table) are associated and registered in the application type category allocation master. FIG. 8 is a flowchart for explaining the update operation of the real table in the update control device according to the embodiment. FIG. 9 is a diagram showing the update operation for the real table when an employee of the Tokyo personnel department of the Tokyo head office applies for address registration. FIG. 10 is a diagram showing a provisional registration operation for the form issuing table when an employee of the Kansai General Affairs Department of the Kansai branch office applies for registration of an address. FIG. 11 is a diagram showing an update operation for the actual table when an employee of the Kansai General Affairs Department of the Kansai Branch submits an application for registration of previous job information. Fig. 12 shows that when an administrator who does not require the approval of an approver for updating applies for new registration, correction, or deletion of data, or when the category of the applied data is registered in the application type category allocation master FIG. 11 is a diagram collectively showing the operation of the update control device when the update control device is not set. FIG. 13 shows a case where a user whose update requires the approval of an approver applies for new registration, correction, or deletion of data, or when the applied data category is registered in the application type category allocation master. FIG. 11 is a diagram collectively showing the operation of the update control device when

An update control system according to an embodiment to which the present invention is applied will be described in detail below with reference to the drawings. It should be noted that the present invention is not limited by this embodiment. Note that the concept of "update" is a broad concept that includes not only registration of data, but also all actions that change the data configuration of the database, such as correction, addition, and deletion.

(System configuration)
FIG. 1 is a diagram showing the system configuration of an update control system according to an embodiment. As shown in FIG. 1, the update control system is configured by interconnecting an update control device 1, an application terminal device 9, and an approval terminal device 10 via a network 8. FIG. As the network 8, for example, a wide area network such as the Internet, or a private network such as a LAN (Local Area Network) can be used.

The application terminal device 9 is a terminal device operated by a user who applies for updating a database (table). The approval terminal device 10 is the approver's terminal device that approves the update of the table requested from the application terminal device 9 . The update control device 1 receives a table update application from the terminal device 9, and updates the database of the requested data when an approver approves the update via the approval terminal device 10. FIG.

As the update control device 1, the application terminal device 9, and the approval terminal device 10, a desktop personal computer device, a notebook personal computer device, or a tablet personal computer device can be used. As the update control device 1, the application terminal device 9, and the approval terminal device 10, a PDA (Personal Digital Assistants) device or a portable information processing device such as a smart phone can be used.

(Hardware configuration of update control device)
The update control device 1 includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input/output interface unit 5, as shown in FIG.

An input device 6 and an output device 7 are connected to the input/output interface section 5 . As the output device 7, a display unit such as a monitor device (including home television) can be used.

As the input device 6, in addition to a keyboard device, a mouse device, and a microphone device, a monitor device that realizes a pointing device function in cooperation with a mouse device can be used.

As the storage unit 2, for example, a storage device such as ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive) or SSD (Solid State Drive) can be used. The storage unit 2 stores an administrator setting master 11, an application type category allocation master 12, an organization master 13, a department master 14, a user master 15, an actual table 16, a form table 17, and an application type group master 18. ing. The storage unit 2 also stores an application type master 19, a code master 20, an employee information category master 21, and an update control program.

The administrator setting master 11 stores a user or a department authorized to approve updates to the requested data database. The application type category allocation master 12 stores update application types and data types (categories) that require an approver's approval for updating. The organization master 13 stores organization codes, organization names, and the like. The department master 14 stores the department code, the organization code of the organization to which the department belongs, the department name, and the like. The user master 15 stores user identification numbers (user IDs), passwords, user names, and the like.

The application type group master 18 stores an application type group ID, an application type group name, and the like. The application type master 19 stores application type codes, application type names, and application type group codes. The code master 20 stores types, code values, and table names. The employee information category master 21 stores category group IDs, category IDs, category names, display flags, display order, and the like.

The real table 16 is an example of a real database, and is a storage area for officially registered data. The actual table 16 includes, for example, a table storing data of the "Basic" category, a table storing data of the "Address" category, a table storing data of the "Family" category, and the like. It has a separate storage area (table). The requested data is stored in the corresponding category table.

The form table 17 is an example of a form database, and serves as a storage area for temporarily storing data before the actual table 16 is updated. The update control device 1 temporarily stores the requested data in the form table 17, and when the approval of the approver is obtained, transfers the data from the activation table 17 to the actual table 16, and restores the actual table 16. Change (update) the data configuration. As a result, the actual table 16 can be updated only with accurate data approved by the approver. Note that the form issuing table 17 is also composed of tables of the same plurality of categories as the actual table 16 .

(Functional configuration of update control device)
Next, the control unit 3 of the update control device 1 executes the update control program stored in the storage unit 2 to obtain the master setting unit 31, the acquisition unit 32, the authority determination unit 33, and the approval necessity determination unit 34. , a storage control unit 35 , a display control unit 36 , and a communication control unit 37 .

The master setting unit 31 sets various data for the administrator setting master 11, the application type category allocation master 12, and the like. The acquisition unit 32 acquires data and the like applied by the applicant via the application terminal device 9 . The authority determination unit 33 determines whether or not the applicant who applied for the data has the authority to update the real table 16 . The approval necessity determination unit 34 determines whether or not the table of the category for which update is requested is a table that requires the approval of the approver for update.

The storage control unit 35 temporarily stores data before approval by the approver in the form issuing table 17, and after approval, stores the data in the real table 16. FIG. The display control unit 36 displays on the output device 7 a screen for setting various data for the administrator setting master 11, the application type category allocation master 12, and the like. The communication control unit 37 communicates with the application terminal device 9 and the approval terminal device 10 . The communication control unit 37 receives data to be updated from the application terminal device 9 . The communication control unit 37 also communicates with the approval terminal device 10 to obtain approval for updating the real table 16 with the requested data.

(Update form of comparative example)
FIG. 2 is a diagram showing an update form of a database of an update control system as a comparative example with respect to the update control system of the embodiment. In FIG. 2, an employee A of the Tokyo Personnel Department and an employee G of the Kansai Branch are both users who have the authority to update the database. As shown in FIG. 2, in the case of the update control system of the comparative example, it was possible to freely access the database and update the database if there was an authority to update the database.

For this reason, for example, data such as employee information applied by a person in charge of a base such as the Kansai branch office (employee G without authority) is registered in the database as actual data without being scrutinized, and is incorrect data. However, there was an inconvenience that it was used as personnel data as it was.

Certain specific information (family information, address information, etc.) can be scrutinized by the employee himself from the application called personnel report, but employee information from bases such as the Kansai branch can be directly entered or accepted as a file. It was difficult for the approver to carefully check the input because it was input in one of the input forms among all the inputs.

Moreover, even if the data in the database were corrected to correct data, it was possible for a user who has the authority to change the data to rewrite the data later.

(System outline of embodiment)
For this reason, when updating the database, the update control system of the embodiment updates the database with accurate data carefully examined by the approver.

FIG. 3 is a diagram showing an outline of system operation in the update control system of the embodiment. As shown in FIG. 3, the update control device 1 of the update control system according to the embodiment refers to the administrator setting master 11 when a request for update of the database (table) is made, and the user who made the request Determine whether the user has update authority for the database. Also, it is determined whether or not the table storing the data for which update is requested is a table that requires the approval of the approver.

If the user who made the application is a user who has update authority for the database, the requested data is updated for the real table 16 . Also, if the table storing the data for which update is requested is not a table that requires the approval of the approver, the actual table 16 is updated with the requested data.

On the other hand, if the user who made the application is not a user who has the update authority for the database, the requested data is temporarily stored in the form issuing table 17 . If the table that stores the data for which update is requested is a table that requires the approval of the approver, the requested data is temporarily stored in the form issuing table 17 .

Once the update control device 1 stores the requested data in the form issuing table 17, it applies to the approval terminal device 10 for approval of updating the real table 16 with the requested data (employee in FIG. 3). (equivalent to information request). The approver decides whether to approve or reject the update of the actual table 16 by the data for which the approval application has been applied, and notifies the update control device 1 of the decision via the approval terminal device 10 .

The update control device 1 transfers only the data approved via the approval terminal device 10 from the form issuing table 17 to the real table 16 and updates the real database 16 . The update control device 1 discards (deletes) the data not approved by the approver from the form issuing table 17 and rejects (rejects) the updating of the actual table 16 . As a result, the real table 16 can be updated using only the data approved by the approver.

(Configuration of administrator setting master)
Next, FIG. 4 is a diagram for explaining the setting of the approver for the administrator setting master 11 that is referred to when updating the actual table 16. As shown in FIG. As an example, the setting for the administrator setting master 11 is performed on the side of the Tokyo head office shown in FIG. 4(a). A user or department user registered in the administrator setting master 11 becomes a user or department user who has the authority to update actual data without administrator approval. An example is an example in which the Tokyo personnel department is set in the administrator setting master 11 as a “department” that has the authority to update actual data without administrator approval. In this case, employees A and B of the Tokyo Human Resources Department have the authority to update the actual data without the approval of the manager. 4(a) and 4(b), an employee C of the Tokyo general affairs department writes to the administrator setting master 11 as a "user" who has the authority to update actual data without administrator's approval. An example is set. In this case, employee C of the Tokyo General Affairs Department has the authority to update the actual data without the approval of the manager.

That is, when the business operator or the like designates the approver setting for the administrator setting master 11, the display control unit 36 displays the administrator setting screen shown in FIG. 4B on the output device 7. FIG. The business operator sets a department or a user as an approver via this administrator setting screen.

In the example of FIG. 4B, the record in the upper row indicates that a "department" with approval authority is set. That is, the upper record indicates that on December 1, 2021, approval authority was set for the department of the Tokyo Personnel Department. Also, the example in FIG. 4B indicates that the record at the bottom of the row is set with a "user" who has approval authority. That is, the lower record indicates that approval authority has been set for "employee C" whose user ID is "UserIdC". In this way, the administrator master 11 stores (sets) information indicating departments or users to whom approval authority is selectively granted.

FIG. 5 is a diagram showing how department or user information registered in the administrator setting master 11 is acquired from another master and registered in the administrator setting master 11 . As shown in FIG. 5, when a department to be an approver is specified by an employee of the Tokyo Personnel Department, the master setting unit 31 obtains an organization code and an organization revision from the organization master 13 shown in FIG. 5(a). Along with acquiring the date and time, the organization code, organization revision date and time, and department code are acquired from the department master 14 as shown in FIG. 5(b), and set in the administrator setting master 11 as shown in FIG. 5(c). (sign up. Similarly, when a user to be an approver is specified by an employee of the Tokyo Personnel Department, the master setting section 31 acquires a user ID from the user master 15 as shown in FIG. It is set (registered) in the administrator setting master 11 as shown in (c).

(Application type category allocation master settings)
Next, FIG. 6 is a diagram for explaining the setting of the table requiring approval for the application type category allocation master 12 that is referred to when updating. When the business operator or the like designates the setting of the table that requires approval for the application type category allocation master 12, the display control unit 36 displays the application type/employee information shown in FIG. 6(b) or FIG. 6(c). A category allocation screen is displayed on the output device 7 . The business operator performs a setting operation for associating each table (category name) requiring approval with the application type via this application type/employee information category allocation screen.

In the example of FIG. 6B, for the application type of "employee attribute" with the application type code of "CD1010", the categories of "basic", "address", "family", "educational background" and "hometown" is set as a table requiring approval. The example of FIG. 6C is an example in which each table of a different category is set as a table requiring approval for the application type of "employee attribute" with the application type code of "CD1010". . That is, in the example of FIG. 6(c), the categories of "basic", "family", "social insurance" and "tax table classification" are applied to the application type of "employee attribute" with the application type code of "CD1020". is set as a table requiring approval.

FIG. 6A shows an example of an approval route for each application type. That is, an approval route A indicated by a dotted line in FIG. 6A indicates an approval route for an employee attribute whose application type code is "CD1010". For example, the update of the real table 16 by employee attribute data by employee F of the Yokohama general affairs department of the Yokohama branch office and employee G of the Kansai branch office is to be finally approved by employee A of the Tokyo personnel department.

Approval route B indicated by a solid line in FIG. 6A indicates an approval route related to employee insurance whose application type code is “CD1020”. For example, the updating of the actual table 16 by employee insurance-related data by employee E of the Yokohama General Affairs Department of the Yokohama branch and employee G of the Kansai branch is subject to approval by employee D of the Tokyo general affairs department, followed by employee C's final update. It is getting approval.

FIG. 7 is a diagram showing how application types and categories (tables) are associated and registered in the application type category allocation master 12. As shown in FIG. The master setting unit 31 refers to the application type group master 18 shown in FIG. 7A and the application type master 19 shown in FIG. It is set (registered) in the application type category allocation master 12 as shown in c).

Further, the master setting unit 31 obtains the table name by referring to the code master 20 shown in FIG. 7(d), and obtains the category group ID by referring to the employee information category master 21 shown in FIG. 7(e). , the category ID and display order are obtained, and set (registered) in the application type category allocation master 12 as shown in FIG. 7(c). As a result, the application type and category (table) can be associated and registered in the application type category allocation master 12 .

(table update behavior)
Next, the table update operation in the update control device 1 will be described with reference to the flowchart of FIG. Based on the update control program stored in the storage unit 2, the control unit 3 executes each process shown in the flowchart of FIG. First, in step S1, the communication control unit 37 receives, via the communication interface unit 4, the data for the update application transmitted from the application terminal device 9 via the network 8, and the acquisition unit 32 receives the data. get the data

Next, the acquired data is attached with the department information of the user making the application, the user ID, and the application type code indicating the application type. Therefore, in step S2, the authority determination unit 33 refers to the administrator setting master 11 shown in FIG. do. Then, it is determined whether or not at least one of the user department information and the user ID attached to the acquired data is registered in the administrator setting master 11 .

If at least one of the user's department information and user ID attached to the acquired data is registered in the administrator setting master 11 (step S2: Yes), the application is currently being made. The user indicates that the user has update authority. In this case, the process proceeds to step S3, and the storage control unit 35 updates the actual table 16 corresponding to the category of the requested data with the requested data.

On the other hand, if at least one of the user's department information and user ID attached to the acquired data is not registered in the administrator setting master 11 (step S2: No), currently This indicates that the user making the application is a user without update authority. In this case, the process proceeds to step S4, and the storage control unit 35 temporarily stores the requested data in the form issuing table 17 corresponding to the category of the requested data (temporary registration).

When the requested data is stored in the form issuing table 17, the communication control unit 37 communicates with the approval terminal device 10 and sends the actual table 16 based on the currently applied data to the approver. Request approval for updates to In step S5, the storage control unit 35 determines whether or not the approver has approved the update of the actual table 16 or not.

If the approver approves the update (step S5; Yes), the storage control unit 35 replaces the data currently temporarily stored in the form issuing table 17 with the requested data in step S3. It shifts to the actual table 16 corresponding to the category and updates it. As a result, the actual table 16 can be updated with the data that has been approved by the approver, so that the actual table 16 can be updated with accurate data.

On the other hand, if the approver rejects the update (step S5; No), rejection processing is performed in step S6. As the rejection process, for example, the data temporarily stored in the form issuing table 17 is erased by the storage control unit 35, and the communication control unit 37 sends the application terminal device 9 of the user who made the application , send an error message that the update was not approved and rejected. As a result, the actual table 16 can be prevented from being updated with data not approved by the approver, and the actual table 16 can be updated with accurate data.

On the other hand, in step S2, the approval necessity determination unit 34 determines whether or not the table in which the currently applied data is to be updated is data for a table that can be updated even by an unauthorized user.

That is, in the case of the update control device 1 of the embodiment, the actual table 16 of the same category as that of the data is updated by the applied data. Therefore, the approval necessity determining unit 34 determines whether or not the category of the applied data is registered in the application type category allocation master 12 shown in FIG. 7(c).

If the category of the applied data is not registered in the application type category allocation master 12 (step S2: Yes), the actual table 16 to be updated with the applied data will be updated without the approver's approval. means not required.

Therefore, if the category of the applied data is not registered in the application type category allocation master 12, the storage control unit 35 updates the actual table 16 of the corresponding category with the applied data in step S3. .

On the other hand, if the category of the applied data is registered in the application type category allocation master 12 (step S2: No), the real table 16 to be updated with the applied data will not be updated. Approver approval is required. Therefore, in step S4, the storage control unit 35 temporarily stores the requested data in the form issuing table 17 corresponding to the category of the requested data (temporary registration).

Note that the table and category have different meanings, but in the update control device 1 of the embodiment, when registering employee information, attributes are divided into categories and input, and one category equals one table. Therefore, the explanation is given with the meaning of table=category.

When the requested data is stored in the form issuing table 17, the communication control unit 37 communicates with the approval terminal device 10 and sends the actual table 16 based on the currently applied data to the approver. Request approval for updates to In step S5, the memory control unit 35 determines whether or not the update has been approved by the approver. If the approver approves the update (step S5; Yes), the storage control unit 35 replaces the data currently temporarily stored in the form issuing table 17 with the requested data in step S3. It shifts to the real table 16 corresponding to the category and updates the real table 16 . As a result, the real table 16 can be updated with the data after being approved by the approver, so the real table 16 can be updated with accurate data.

On the other hand, if the approver rejects the update (step S5; No), rejection processing is performed in step S6. As the rejection process, for example, the data temporarily stored in the form issuing table 17 is erased by the storage control unit 35, and the communication control unit 37 sends the application terminal device 9 of the user who made the application , send an error message that the update was not approved and rejected. As a result, the actual table 16 can be prevented from being updated with data not approved by the approver, and the actual table 16 can be updated only with correct data.

(Specific example of update)
FIG. 9 shows an example in which an application for address registration is made by employee A of the Tokyo Personnel Department of the Tokyo head office. The Tokyo personnel department of the Tokyo head office shown in FIG. 9A is set in the administrator setting master 11 as a department that performs approval, as described with reference to FIG. For this reason, employee A of the Tokyo Human Resources Department of the Tokyo head office has authority as an approver. Therefore, when employee A applies for address registration via the employee information management screen as shown in FIG. , the data of the applied address is registered.

On the other hand, FIG. 10 shows an example in which an application for address registration is made by an employee G of the Kansai General Affairs Department of the Kansai branch. Employee G of the Kansai general affairs department of the Kansai branch office shown in FIG. 10A is not set as an administrator in the administrator setting master 11, as described with reference to FIG. For this reason, the approval necessity determining unit 34 determines that the "address" category of the data applied through the employee information management screen as shown in FIG. 10B is the application type category shown in FIG. It is determined whether or not it is registered in the allocation master 12 .

When the address category of the applied data is registered in the application type category allocation master 12 shown in FIG. need. Therefore, the storage control unit 35 temporarily stores the data of the address requested by the employee G in the form table 17 of the address category, as shown in FIG. 10(c). The address data stored in the billing table 17 is transferred to the actual table 16 of the address category after approval by the approver, and the actual table 16 is updated.

FIG. 11 shows an example in which an application for registration of previous job information is made by employee G of the Kansai General Affairs Department of the Kansai Branch. Employee G of the Kansai general affairs department of the Kansai branch office shown in FIG. 11A is not set as an administrator in the administrator setting master 11, as described with reference to FIG. For this reason, the approval necessity determination unit 34 determines that the category of "previous job information" of the data applied through the employee information management screen as shown in FIG. It is determined whether or not it is registered in the type category allocation master 12 .

If the category of the previous job information of the applied data is not registered in the application type category allocation master 12 shown in FIG. The approver's approval is no longer required. Therefore, as shown in FIG. 11(c), the storage control unit 35 updates the previous job information category actual table 16 with the data of the previous job information requested by the employee G. FIG.

(Operation when application by administrator or category is not registered)
FIG. 12 shows when an administrator who does not require the approval of an approver applies for new registration, correction, or deletion of data, or when an application is applied to the application type category allocation master 12 3 is a diagram collectively showing the operation of the update control device 1 when no data category is registered; FIG. In this case, the data for which new registration is requested is directly registered in the real table 16 without being temporarily stored in the form issuing table 17, as shown in FIG. 12(a). "Modification" is the same, and as shown in FIG. 12(b), the data stored in the actual table 16 can be freely modified. The same applies to "delete", and as shown in FIG. 12(c), data stored in the real table 16 can be freely deleted.

(Operation when an application or category is registered by a user other than the administrator)
FIG. 13 shows that when a user whose update requires the approval of an approver applies for new registration, correction, or deletion of data, or when the requested data category is registered in the application type category allocation master 12 3 is a diagram collectively showing the operation of the update control device 1 when the update control device 1 is set. In this case, the data for which new registration has been applied is temporarily stored in the form issuing table 17, as shown in FIG. 13(a). Then, when the approval of the approver is obtained, the data is transferred from the billing table 17 to the real table 16 and registered.

The same applies to "correction", and data used for correction is temporarily stored in the form issuing table 17, as shown in FIG. 13(b). Then, when the approval of the approver is obtained, the form table 17 is transferred to the actual table 16, and the desired data is corrected. The same applies to "deletion", and data used for deletion is temporarily stored in the form issuing table 17 as shown in FIG. 13(c). Then, when the approval of the approver is obtained, the form table 17 is transferred to the actual table 16, and the desired data is deleted.

(Effect of Embodiment)
As is clear from the above description, in the update control device 1 of the embodiment, for example, the same input screen is used by the person in charge of human resources at a base such as the Kansai branch office and the person in charge of personnel (final approver) at the Tokyo headquarters. Determine whether or not to apply for each person in charge and each table. The requested data is temporarily stored in the form data 17 until approval is obtained from the final approver. The requested data is migrated to the table 16 and the real table 16 is updated.

As a result, the real table 16 can be updated using the data approved by the approver, and the database (real table 16) can be updated with accurate data.

In addition, by processing the data applied from bases such as the Kansai branch office in accordance with the flow of the workflow system, the approver can examine the data and eliminate erroneous data. In addition, since application availability can be set for each table (category), an approval route can be set for each employee attribute information unit. As a result, for example, evaluation information can be processed by the superior's approval route, and address or family information can be processed by the personnel department's approval route.

[Contribution to the Sustainable Development Goals (SDGs) led by the United Nations]
Since this embodiment can contribute to improving operational efficiency and promoting appropriate management decisions of companies, it is possible to contribute to goals 8 and 9 of the SDGs.

In addition, the present embodiment can contribute to the reduction of disposal loss and the promotion of paperless and computerization.

In addition, since this embodiment can contribute to strengthening control and governance, it is possible to contribute to Goal 16 of the SDGs.

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

For example, among the processes described in the embodiments, all or part of the processes described as being automatically performed can be manually performed, or all of the processes described as being manually performed Alternatively, some can be done automatically by known methods.

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

Also, with regard to the update control device 1, each component shown in the drawing is functionally conceptual, and does not necessarily need to be physically configured as shown in the drawing.

For example, the processing functions provided by the update control device 1, particularly the control unit 3 and each processing function performed by the control unit 3, are interpreted in whole or in part by a CPU (Central Processing Unit) and the CPU. It may be implemented by a program to be executed, or may be implemented as hardware by wired logic. The program is recorded on a non-temporary computer-readable recording medium containing programmed instructions for causing the information processing device to execute the processing described in the present embodiment, and the update control device is executed as necessary. 1 is mechanically read. That is, a storage unit such as a ROM or HDD stores a computer program for giving commands to the CPU in cooperation with the OS to perform various processes. This computer program is executed by being loaded into the RAM, and constitutes the control section 3 in cooperation with the CPU.

Further, the update control program of this update control device 1 may be stored in another server device connected to the update control device 1 via an arbitrary network, and all or part of it may be stored as necessary. can also be downloaded.

Also, the update control program for executing the processing described in this embodiment may be stored in a non-temporary computer-readable recording medium, or may be configured as a program product. Here, this "recording medium" means memory card, USB (Universal Serial Bus) memory, SD (Secure Digital) card, flexible disk, magneto-optical disk, ROM, EPROM (Erasable Programmable Read Only Memory), EEPROM (registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROM (Compact Disk Read Only Memory), MO (Magneto-Optical Disk), DVD (Digital Versatile Disk), Blu-ray (registered trademark) Disc, etc. shall include any "portable physical medium".

A "program" is a data processing method written in any language or writing method, regardless of the format such as source code or binary code. In addition, the "program" is not necessarily limited to a single configuration, but is distributed as multiple modules or libraries, or cooperates with a separate program represented by the OS to achieve its function. Including things. Known configurations and procedures can be used for the specific configuration and reading procedure for reading the recording medium in the update control device 1 shown in the embodiment, the installation procedure after reading, and the like.

The storage unit 2 is storage means such as memory devices such as RAM and ROM, fixed disk devices such as hard disks, flexible disks, and optical disks, and stores various programs, tables, databases, and , to store files for web pages, etc.

Further, the update control device 1 may be configured by an information processing device such as a known personal computer device or workstation, or may be configured by an information processing device to which arbitrary peripheral devices are connected. Also, the information processing apparatus may be implemented by installing software (including programs, data, etc.) that implements the processing described in the present embodiment.

Furthermore, the specific form of distribution and integration of the device is not limited to the one shown in the figure, and all or part of it can be functionally or physically implemented in any unit according to various additions or functional additions. It can be distributed and integrated. In other words, the embodiments described above may be arbitrarily combined and implemented, or the embodiments may be implemented selectively.

INDUSTRIAL APPLICABILITY The present invention is useful for database data management and the like.

1 update control device 2 storage unit 3 control unit 4 communication interface unit 5 input/output interface unit 6 input device 7 output device 8 network 9 application terminal device 10 approval terminal device 11 administrator setting master 12 application type category allocation master 13 organization master 14 Department master 15 User master 16 Actual table 17 Draft table 18 Application type group master 19 Application type master 20 Code master 21 Employee information category master 31 Master setting unit 32 Acquisition unit 33 Authority determination unit 34 Approval necessity determination unit 35 Storage control unit 36 display control unit 37 communication control unit

Claims (6)

an authority determination unit that determines whether or not a user who has made an update request for the real database has the authority to update the real database;
Whether or not the real database storing data requested to be updated is a database requiring approval by an approver at the time of update is determined based on approval necessity information set in the real database requested to be updated. an approval necessity determination unit that determines by
A determination result of the authority determining unit, which indicates that the user who has made the update request for the real database is a user who does not have update authority for the real database, and a determination result of the approval necessity determining unit. When at least one of the determination results indicating that the real database storing the data requested to be updated is a database requiring approval by an approver at the time of update is obtained, The data to be stored in the actual database in response to an update request is stored in a form issuing database that is a database different from the actual database, and if the approver's approval is not obtained, the data stored in the form issuing database is used. a storage control unit that rejects the update of the real database and transfers the data stored in the form issuing database to the real database and stores the data in the case where an approver's approval is obtained;
update controller with The storage control unit determines whether a determination result of the authority determination unit indicating that a user who has issued an update request to the real database is a user who has update authority to the real database, or the authorization request. When the determination result of the denial determining unit, which is the determination result indicating that the actual database storing the update-requested data is a database that does not require the approval of the approver at the time of update, the update is requested. storing the obtained data in the real database without storing it in the billing database;
The update control device according to claim 1, characterized by: The authority determination unit is configured to select a user who is registered in the administrator setting master and has update authority for the real database, or a user of a department who is registered in the administrator setting master and has update authority for the real database. as a user with update authority for the real database;
3. The update control device according to claim 1 or 2, characterized by: The approval necessity determination unit associates an application type, which is a type of data for which an update is requested, with a category that requires approval by an approver for updating, among categories indicating classification of data stored in the actual database. When a category corresponding to the data requested to be updated is detected in the application type category master in which the approval necessity information is stored, the actual database requested to be updated is updated by the approver. Determining that the database requires approval;
The update control device according to any one of claims 1 to 3, characterized by: an authority determination step in which an authority determination unit determines whether or not a user who has made an update request for the real database has update authority for the real database;
An approval necessity determining unit determines whether or not the real database in which the data requested to be updated is a database requiring approval by an approver at the time of updating is set in the real database requested to be updated. an approval necessity determination step for determining based on the approval necessity information received;
The determination result obtained by the storage control unit in the authority determination step, which indicates that the user who requested the update to the real database is a user who does not have the update authority to the real database, and the approval request. At least one of the determination results obtained in the reject determination step, which indicates that the actual database storing the data requested to be updated is a database requiring the approval of an approver at the time of update. is obtained, the data to be stored in the actual database in response to an update request is stored in a form issuing database that is a database different from the actual database, and if the approver's approval is not obtained, the data is stored in the form issuing database a storage control step of rejecting the update of the actual database by the data stored in the above, and transferring the data stored in the form issuing database to the actual database and storing the data when the approval of the approver is obtained;
update control method. the computer,
an authority determination unit that determines whether or not a user who has made an update request for the real database has the authority to update the real database;
Whether or not the real database storing data requested to be updated is a database requiring approval by an approver at the time of update is determined based on approval necessity information set in the real database requested to be updated. an approval necessity determination unit that determines by
A determination result of the authority determining unit, which indicates that the user who has made the update request for the real database is a user who does not have update authority for the real database, and a determination result of the approval necessity determining unit. When at least one of the determination results indicating that the real database storing the data requested to be updated is a database requiring approval by an approver at the time of update is obtained, The data to be stored in the actual database in response to an update request is stored in a form issuing database that is a database different from the actual database, and if the approver's approval is not obtained, the data stored in the form issuing database is used. Rejecting the update of the real database, and functioning as a storage control unit that transfers and stores the data stored in the form issuing database to the real database when the approval of the approver is obtained;
An update control program characterized by:

Images