JP2013196349A - Employee information management system, information processing apparatus, employee information management system generation method, employee information management system generation program and information acquisition method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing apparatus, an information management system and an information processing program for efficiently managing a plurality of assignment information.SOLUTION: The employee information management system includes: a member master storage unit for acquiring information from a personnel information storage unit, and storing permanent address information in which a first identification number for identifying members in one organization to which the members are assigned is associated with attribute information as information on the attributes of the members in the organization and additional information in which the first identification number is associated with attribute information in the other organization when the members are also assigned to the other organization in association; a member information storage unit for storing a second identification number for identifying the members in the organization to which the members are assigned and registration information as information on the members in the organization as a pair; a register storage unit for storing the permanent address information corresponding to the second identification number relating to one member in the member information storage unit and the additional information corresponding to the permanent address information and/or the registration information relating to the second identification number; and a master storage unit for storing data for output generated from the permanent address information and the additional information or the registration information.

Description

  The present invention relates to an employee information management system, an information processing apparatus, an employee information management system generation method, an employee information management system generation program, and an information acquisition method.

  When using information about employees in the application, log in by entering the employee ID and password before executing the application. Then, there is a company that has an employee database that can authenticate employees based on input information and obtain related information about logged-in employees. Such an employee database is conventionally configured to register one affiliation information for one identification number.

  If an employee belongs to only one company, authentication is obtained by logging in with one identification number, and necessary information is acquired. However, in a corporate entity having a group company, if the employee is also registered at the seconded company in addition to the permanent address, it is necessary to register the second party affiliation information in addition to the first affiliation affiliation information in the employee database. In addition, when an employee is concurrently working in a plurality of organizations in the home company, that is, when belonging to a plurality of organizations in the same company, it is necessary to register the affiliation information of the concurrently serving company in the employee database.

  In this case, in addition to the identification number and affiliation information of the registered domicile, registering the identification number and affiliation information of the second or second office in the employee database will result in the employee having a plurality of identification numbers. It is necessary to manage each identification information and the corresponding password. The more employees belong to many organizations, such as seconded employees and outsourced companies, in addition to their permanent address, the more complicated the management becomes.

  The present invention has been made in view of the above points, and is an employee information management system, an information processing apparatus, an employee information management system generation method, and an employee information management system capable of efficiently managing a plurality of belonging information An object is to provide a generation program and an information acquisition method.

  Therefore, in order to solve the above-described problem, the employee information management system of the present invention acquires information from a personnel information storage unit that stores information of members of a plurality of organizations, and the configuration of the organization belongs to one organization to which the members belong. A first identification number for identifying a member and attribute information that is attribute information of the member's attribute in the organization, and the first member when the member belongs to another organization. A member master storage unit for storing the identification number and the additional information corresponding to the attribute information in the other organization, and a second member for identifying the member in the organization to which the member belongs. A member information storage unit that stores a pair of an identification number and registration information that is information of the member in the organization, and the second identification number relating to one member in the member information storage unit Compatible with The registration information relating to the permanent information stored in the member master storage unit, the additional information corresponding to the permanent member information stored in the member master storage unit, and / or the second identification number And a master storage unit that stores output data generated from the additional information and / or the registration information. It is characterized by.

  In order to solve the above problems, the present invention may be an information processing apparatus using the employee information management system, an employee information management system generation method, an employee information management system generation program, and an information acquisition method in the information processing apparatus. .

  According to the present invention, it is possible to provide an employee information management system, an information processing apparatus, an employee information management system generation method, an employee information management system generation program, and an information acquisition method capable of efficiently managing a plurality of belonging information. it can.

1 is an overall configuration diagram of a system. It is a functional block diagram of this system. It is a sequence diagram in generation of a SUID employee master database. It is a figure for demonstrating the data generation of a SUID employee master database. It is a figure which shows an example of employee information. It is a figure which shows an example of registration information. It is a sequence diagram of output data generation processing. It is a figure for demonstrating the production | generation process of registration information and additional information. It is a figure which shows an example of additional information. It is a sequence diagram of a registration application process. It is a functional block diagram of a common authentication module. It is a sequence diagram for demonstrating the process performed with a common authentication module.

(Overall system configuration)
Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is an overall configuration diagram of the system.

  The employee information management system 1 in this embodiment includes an Oracle (registered trademark) database 11, a SUID (Single User IDentification) employee master database 12, an address book database 13, a SUID database 14, a SUID register database 18, an LDAP master database 10, and an LDAP. A replica database 15 and a common authentication module 16 are provided. The user side using this system is provided with a corresponding application 17.

  The employee information management system 1 is a system corresponding to a case where a plurality of companies belong to one group, and the Oracle database 11 stores personnel information, which is information related to personnel regarding the employees belonging to the group. . The personnel information includes all information used for personnel, such as information on employee name, company, date of hire, time of secondment, and employee address.

  The SUID employee master database 12 extracts and stores information used by the user in the corresponding application 17 and information for determining the authority to use the corresponding application 17 from the personnel information included in the Oracle database 11. The SUID employee master database 12 has company register information relating to a company in which an employee is registered at the time of joining the company, that is, a company having a so-called permanent register. The SUID employee master database 12 stores additional information, which is information on other companies that are seconded or outsourced, when the employee is assigned to another company belonging to the same group by seconding or outsourcing. And memorize it. Furthermore, when the SUID employee master database 12 belongs to a plurality of departments within the same company, information relating to the department where the person concurrently serves is stored as additional information in association with the permanent account information.

  The address book database 13 is a database that stores the email addresses of employees belonging to the group and information related to the email addresses.

  The SUID database 14 is a database that manages a user ID that is a login ID when an employee belonging to a group uses the corresponding application 17. The SUID database 14 includes a user ID of an employee given for each organization and registration information regarding a company to which the employee belongs. When one employee belongs to a plurality of companies including his / her permanent address, different user IDs and passwords for each company and registration information related to the company can be stored for the number of companies to which the employee belongs.

  The LDAP master database 10 is a database that can be commonly used by employees belonging to a group, and corresponds to one user ID and password for each company and all departments to which the employee belongs. It has affiliation information that is information in the company. If the LDAP master database 10 is accessed using one user ID and password, affiliation information of all organizations to which the employee belongs can be acquired.

  The information of the SUID database 14 is used to generate the LDAP master database 10, but when the amount of data that the SUID database 14 or the LDAP database has is large, the information of the SUID database 14 is directly output to the LDAP database. It is not preferable for safety of each database. For this reason, the database for processing is mediated as the SUID register database 18 to buffer the influence on the LDAP database. That is, setting the SUID register database 18 as a primary data storage location contributes to improving the security of the SUID database 14 and the LDAP database.

  The LDAP replica database 15 is a database in which data included in the LDAP master database 10 is copied and can be directly accessed by the user. The LDAP master database 10 is a database in which group human resource information is integrated, and an excessive load is applied when a user directly accesses the LDAP master database. Therefore, a dedicated database that can be used by the application called the LDAP replica database 15 is generated, and the load of the LDAP master database 10 is distributed. As a result, the security of the LDAP master database 10 is also improved.

  The common authentication module 16 is a module commonly used for each corresponding application 17 when accessing the LDAP replica database 15 from the corresponding application 17 used by the user. The common authentication module 16 performs user authentication using the LDAP replica database based on the authentication information of the logged-in user, and acquires necessary affiliation information from the LDAP replica database.

  The common authentication module 16 also authenticates the corresponding application 17 itself. When there is an access from the corresponding application 17, the common authentication module 16 refers to the authentication information of the corresponding application 17 in the LDAP replica database 15 and determines whether or not the accessed corresponding application 17 is appropriate. Authenticate.

  The corresponding application 17 is an application corresponding to the common authentication module 16 in the present system, and the type thereof is not limited and is various.

  When an employee belonging to the group activates the corresponding application 17, a screen for inputting an ID and a password is displayed. Conventionally, when an employee inputs a user ID and password used in a company to log in, the corresponding application 17 accesses the LDAP master database 10. The information transmitted from the SUID database 14 is registered in the LDAP master database 10, and the corresponding application 17 makes an authentication request for the user ID to the LDAP master database 10 and acquires the corresponding information. Since the SUID database 14 stores user IDs and registration information for each company, a user belonging to a plurality of companies inputs the user ID and password of the company for which information is to be acquired separately when logging in the corresponding application 17. It was.

  In this system, necessary information is copied to the SUID employee master database 12 from the Oracle database 11 in which the personnel information of the group is stored. The SUID employee master database 12 has additional information, which is information on a seconded employee, a business consignee, or a part-time employee, corresponding to the permanent account information that is information relating to the permanent address.

  The SUID database 14 having a different user ID for each company to which the user belongs and registration information about the company to which the user belongs is regularly updated based on the address book database 13 having the mail address and the address related information. In this system, the SUID register database 18 is stored based on the registration information and the additional information included in the SUID employee master database 12 and the registration information included in the SUID database 14. Then, data in the LDAP master database 10 is generated and updated using information in the SUID register database 18.

  By using the LDAP master database 10 generated by this configuration, the user can acquire the latest affiliation information related to a plurality of organizations to which the user belongs by inputting one user ID and password.

(System function)
Next, functions of the employee information management system 1 will be described. FIG. 2 is a functional block diagram of this system.

  This system includes a system control unit 20 in addition to the aforementioned Oracle database 11, SUID employee master database 12, address book database 13, SUID database 14, SUID register database 18, LDAP master database 10, and corresponding application 17. The system control unit 20 manages data replication from each database to the database.

  Data replication to each database is performed by batch processing. The necessary information out of the personnel information is read from the Oracle database 11 by batch processing, and is stored in the SUID employee master database 12 as permanent information and additional information.

  Based on the permanent address information and additional information included in the SUID employee master database 12, the e-mail address and address related information included in the address book database 13, and the registration information included in the SUID database 14, the system control unit 20 performs a new process by batch processing. The permanent account information and additional information are generated and stored in the SUID register database 18 and the SUID database 14. Information stored in the SUID register database 18 is output to the LDAP master database 10 under the control of the system control unit 20 and stored as affiliation information.

  The permanent information and additional information stored in the SUID employee master database 12 are output and used as employee information when data is used. Since the SUID database 14 has been used for conventional login authentication and information provision, the SUID database 14 holds a user ID and registration information corresponding to the user ID in advance for each company to which the employee belongs.

  When authentication information is input from the corresponding application 17, the common authentication module 16 is called. The common authentication module 16 reads out the affiliation information stored in the LDAP master database 10 and performs authentication, and notifies the corresponding application 17 of information necessary for authentication.

  It is desirable to transfer such information by batch processing for security and data safety. However, if security or data safety is secured by other methods, it may be performed via the network. . By moving data in real time, it is possible to respond quickly to changes in data.

(Creation of SUID employee master database 12)
Next, creation of the SUID employee master database 12 will be described. FIG. 3 is a sequence diagram in data generation of the SUID employee master database. Data generation of the SUID employee master database 12 is automatically executed by batch processing of the system control unit 20.

  In S11, the system control unit 20 generates an information acquisition statement for reading necessary information from the Oracle database 11 using SQL. The generated SQL statement is executed on the Oracle database 11 (S12). The system controller 20 acquires the personnel information read from the Oracle database 11 (S13).

  FIG. 4 is a diagram for explaining data generation in the SUID employee master database. The personnel information read from the Oracle database 11 in S13 is information relating to the affiliation of all employees. The personnel information stored in the Oracle database 11 stores information relating to the permanent affiliation, for example, as shown in FIG. 4A, and when the affiliation increases, information relating to the new affiliation is added to the information relating to the permanent affiliation. ing. In S14 of FIG. 3, the system control unit 20 combines the personnel information read from the Oracle database 11. As shown in FIG. 4B, the combined data is generated by combining information about the new affiliation with the permanent affiliation.

  Returning to FIG. 3, the system control unit 20 transmits an acquisition result (OK or NG) indicating whether or not personnel information has been acquired to the Oracle database 11 (S15). Based on the above-mentioned data combined with respect to affiliation, the system control unit 20 generates a permanent account information and additional information to generate a CSV file (S16). The generated CSV file is transmitted to the SUID employee master database 12 (S17).

(Personal information and additional information)
Next, the permanent information and the employee information output with the additional information stored in the SUID employee master database 12 will be described. FIG. 5 is a diagram illustrating an example of employee information.

  Based on the personnel information read from the Oracle database 11, the system control unit 20 generates employee information that is correspondence information between the permanent account information and the additional information. An example of permanent register information is shown in FIG. In the permanent register information, in addition to the company code, the name and the employee number of the permanent register, information such as the department to which the employee belongs and the title is stored.

  An example of the additional information is shown in FIG. In the additional information, information on the affiliation other than the permanent affiliation is stored when the employee belongs to another company in the same group as the permanent registrant due to seconding or dispatching. For example, information such as the company name, company code, and employee number at the second destination is described in the additional information. The SUID employee master database 12 stores one employee's permanent register information and additional information in association with each other. The additional information is not limited to one. If you belong to a seconded company in addition to your permanent account and you are dispatched to another company, the additional information of your permanent account, seconded employee information, and additional information of your new employee Corresponding and stored.

  Since the Oracle database 11 includes all information related to employees, information related to affiliation is extracted from the Oracle database 11, and a SUID employee master database 12 is created that summarizes information about a plurality of affiliations for each employee as employee information. This facilitates the transition to an employee information management system that manages a plurality of affiliation information with one ID. Further, by extracting only the information necessary for using the corresponding application 17 from the Oracle database 11 and storing it, the required resources are reduced and the security is improved.

(Registration information)
Next, registration information stored in the SUID database 14 will be described. FIG. 6 is a diagram illustrating an example of registration information.

  The registration information is information such as the company name of each organization to which the employee belongs, such as the permanent address, the secondee, the dispatch destination, and the concurrent job, the employee number at the company to which the employee belongs, the registration information and the user ID that is the login ID, etc. Describe it in correspondence.

  The address book database 13 holds the latest information regarding the mail address and work location. Therefore, the system control unit 20 can periodically refer to the address book database 13 and update the e-mail address and work location of the registration information based on the information in the address book database 13.

(Generation of output data)
Next, a process of generating output data based on information stored in the SUID employee master database 12 and information stored in the SUID database 14 will be described. FIG. 7 is a sequence diagram of output data generation processing.

  The system control unit 20 reads registration information in the SUID database 14 by batch processing (S21). The system control unit 20 acquires registration information for one employee (S22). Next, employee information in the SUID employee master database 12 is searched based on the company code and employee number of the acquired registration information (S23).

  The SUID database 14 holds, for each company to which an employee belongs, a user ID of the company and registration information related to the company in association with each other. Therefore, when an employee related to the registration information that is the search source information belongs to a plurality of companies, the registration information may be a document relating to the permanent address, or may be a document relating to a belonging address that is not the permanent account, such as a seconded employee. In S23, the corresponding employee information is searched regardless of whether the registration information is related to the permanent address.

  The system control unit 20 acquires employee information having the same company code and employee number as the acquired registration information from the SUID employee master database 12 (S24). When the acquired employee information includes additional information, the system control unit 20 needs to acquire registration information corresponding to either the permanent register information or the additional information.

  The system control unit 20 searches the SUID database 14 for registration information corresponding to the additional information if the registration information acquired in S22 is a document related to the permanent address information, and for registration information corresponding to the permanent address information if the document is related to the additional information. (S25). From the SUID database 14, the system control unit 20 acquires all registration information corresponding to the permanent information or additional information (S26).

  In S27, the system control unit 20 corresponds to new registration information corresponding to the permanent address information of the employee information and additional information of the employee information based on the employee information acquired in S24 and the registration information acquired in S22 and S26. Create new additional information. The created new registration information and additional information are stored in the SUID register database 18 (S28) and the SUID database 14 by the system control unit 20 (S29). When a CSV file is generated based on the information stored in the SUID register database 18 and output to the LDAP master database 10 (S30), the generated CSV file is registered in the LDAP master database 10 (S31).

  Through the above processing, the employee information in the SUID employee master database 12 generated based on the personnel information in the Oracle database 11 and the contents of the registration information in the SUID database 14 used in the conventional system are integrated. The integrated new affiliation information is stored in the LDAP master database 10 and utilized.

(Generate new registration information and additional information)
Next, a process for generating new registration information and new additional information performed in S27 will be described. FIG. 8 is a diagram for explaining registration information and additional information generation processing. The following description corresponds to S27 in FIG. 7 and will be described assuming that the processing up to S26 has been completed.

  As processing from S21 to S26, registration information and additional information are read from the SUID database 14, and employee information corresponding to the read registration information and additional information is read from the SUID employee master database 12. Furthermore, if there is additional information in the employee information, registration information and additional information related to the additional information are acquired in S26. That is, in the employee information, the system control unit 20 has acquired registration information and additional information as many as the number of affiliations to which the user belongs (including the permanent address).

  FIG. 8A is a flowchart of registration information and additional information generation processing. In S <b> 271, the system control unit 20 stores registration information related to the permanent address information in the employee information in the SUID register database 18. Proceeding to S272, if the system control unit 20 refers to the employee information and there is additional information, the process proceeds to S273. FIG. 8B shows employee information when there is additional information. “002” represents the company code of the secondee. If there is no additional information, the process ends.

  In S273, the system control unit 20 refers to the user registration information read from the SUID database 14, and if there is registration information corresponding to the additional information, the process proceeds to S274. FIG. 8C shows a case where there is registration information corresponding to the additional information. As the registered information, in addition to the company code “001” of the registered address, information of the employee regarding the company code “002” of the secondee is read.

  Proceeding to S274, new additional information is created from the registration information corresponding to the additional information. The system control unit 20 creates new additional information based on the registration information corresponding to the company code “002” which is the original additional information. In S273, when the registration information corresponding to the additional information has not been read, the process proceeds to S275. FIG. 8D shows a state where the registration information corresponding to the additional information has not been read. Registration information related to the company code “002” corresponding to the additional information is not read.

  In S275, the system control unit 20 stores the created new additional information or the original additional information in the SUID register database 18 and the SUID database 14 when no new additional information is created. The new registration information and additional information stored in the SUID register database 18 are output to the LDAP master database 10, and the process ends.

  Although the additional information is also stored in the SUID database 14, the system control unit 20 periodically performs an information update batch process on the additional information in the SUID database 14, and collates the additional information with the employee information. For example, when the personnel information is updated in the Oracle database 11 and the information related to one destination is deleted, the system control unit 20 updates the employee information based on the data in the Oracle database 11. In addition, the system control unit 20 collates the employee information with the registration information and the additional information, and sets the status of the additional information in the SUID database 14 to “invalid”.

  The system control unit 20 further updates the additional information in the SUID register database 18 based on the affiliation information in the SUID database 14. The updated additional information is output to the LDAP master database 10 and reflected in the data of the LDAP master database 10.

  Further, the additional information may be configured to have an expiration date. The system control unit 20 periodically performs an information update batch process on the additional information in the SUID database 14, and sets the status of the additional information as “expired” when the expiration date has expired. The updated additional information is reflected in the LDAP master database 10 by the same processing as described above.

  With this configuration, the contents of registration information and employee information are integrated, and employees who belong to multiple affiliations can acquire multiple affiliation information with one user ID. The LDAP master database 10 is configured to be updated with new information even when the Oracle database 11 is changed.

(Additional Information)
Next, the new additional information created in S274 described above will be described. FIG. 9 is a diagram illustrating an example of additional information.

  Based on the data stored in the SUID employee master database 12 and the SUID database 14, the system control unit 20 creates, as additional information, information related to the affiliated company that is not a permanent employee, such as a seconding destination and a business consignment destination. The newly created additional information is stored in the LDAP master database 10 via the SUID register database 18.

(Application for registration of new affiliation)
Next, an exceptional registration application process when a user belonging to the group of this system belongs to a new company will be described. FIG. 10 is a sequence diagram of the registration application process. When a user belonging to a group of this system belongs to a new company, in principle, information related to the affiliation destination is updated in the Oracle database 11, and data is generated in the SUID employee master database 12 by the procedure shown in FIG. Thereafter, the new affiliation information is stored in the SUID database 14 and the LDAP master database 10 in the procedure shown in FIG.

  However, there may be employment forms that do not involve a change in register, such as outsourcing. In this case, since the information related to the affiliation is not updated in the Oracle database 11 or the SUID employee master database 12, the information related to the new affiliation is registered in the LDAP master database 10 by performing the registration application process described below.

  In addition, since the information about the new affiliation mail address and the new affiliation is frequently updated in the address book database 13, the system control unit 20 may acquire the new affiliation information from the address book database 13. Configure.

  The user A assigned to the new affiliation starts the application module of the new affiliation and inputs information necessary for the application (S41). The information necessary for the application is, for example, information on the department or boss to which the new affiliation belongs. The system control unit 20 displays a screen for inputting authentication information to the user A (S42). User A inputs the user ID and password, which are authentication information, on the screen (S43).

  The system control unit 20 requests the affiliation information associated with the user ID from the LDAP master database 10 (S44). The system control unit 20 acquires affiliation information from the LDAP master database 10 (S45). The system control unit 20 refers to the authentication information input by the user A and the acquired affiliation information, and authenticates the user A (S46).

  The system control unit 20 indicates the user ID to the address book database 13 and requests a company code associated with the user ID (S47). When the company code is acquired from the address book database 13 (S48), the system control unit 20 displays a screen for selecting a newly belonging company for the user A when there are a plurality of company codes associated with the user ID. (S49). The system control unit 20 acquires the company information selected by the user A (S50).

  The system control unit 20 searches for registration information and additional information in the SUID database 14 using the user ID (S51). In S52, registration information and additional information associated with the user ID of the user A are acquired from the SUID database 14. At this point in time, additional information regarding the new affiliation has not been generated and cannot be acquired.

  The system control unit 20 creates additional information corresponding to the acquired user registration information based on the information input by the user A (S53). The system control unit 20 transmits an approval request mail indicating the content of the additional information to the user B who is the supervisor of the destination of the user A (S54). The user B who receives the approval request mail instructs the system control unit 20 to start the approval module (S55). The approval module displays an approval screen for user B (S56).

  When the user B approves the approval screen (S57), the additional information created in S53, the registration information acquired in S52, and the existing additional information are notified to the SUID database 14 and (S58) the SUID register database 18. (S59). A CSV file is generated based on the document notified to the SUID register database 18 (S60), and information about the new affiliation is registered in the LDAP master database 10 (S61). If registration is completed normally, additional information is deleted from the SUID register database 18.

  When the user applies to the application module, information regarding the new affiliation is automatically registered in the LDAP server. Thereby, the user can use new affiliation information from the application.

  In S47 and S48, the system control unit 20 acquires a company code associated with the user ID from the address book database 13. Here, the system control unit 20 acquires user usage environment information based on information from the application module, searches the SUID database 14 based on the acquired information, and from the company information list stored in the SUID database 14. The company code may be acquired.

  In addition, when an employee belongs to a new organization, a change of register is required due to a seconding or the like, and thus the exceptional registration application process described above, which is originally unnecessary even though there is information on the seconding destination in the Oracle database 11. May start. In this case, the additional information acquired from the SUID database 14 in S52 includes information on the new affiliation. When the information input by the user A in the application module overlaps with the additional information acquired in S52, the system control unit 20 ends the process here.

(Function of common authentication module 16)
Next, the function of the common authentication module 16 that uses information registered in the LDAP master database 10 will be described. FIG. 11 is a functional block diagram of the common authentication module.

  The common authentication module 16 includes an application I / F 101, an authentication unit 102, an affiliation information acquisition unit 103, an application authentication unit 104, an LDAP server I / F 105, a screen display control unit 106, and an affiliation information storage unit 107. The application I / F 101 is an interface with each application in the common authentication module 16. The LDAP server I / F 105 is an interface between the LDAP replica database 15 and the common authentication module 16.

  The application authentication unit 104 authenticates the stored application when the application itself started by the user is stored in the LDAP replica database 15 as an appropriate application. The authentication unit 102 performs authentication by checking the LDAP replica database 15 for the user ID and password of the user input from the application.

  The affiliation information acquisition unit 103 acquires affiliation information of the authenticated user from the LDAP replica database 15 and notifies the application. The affiliation information storage unit 107 stores the affiliation information acquired from the LDAP replica database 15. The screen display control unit 106 displays the affiliation information acquired by the affiliation information acquisition unit 103 on the screen and prompts the user to select. The screen display control unit 106 may exist in each application.

(Process of common authentication module 16)
Next, processing performed by the common authentication module 16 will be described. FIG. 12 is a sequence diagram for explaining processing performed in the common authentication module. In addition to authenticating the person who uses the application, the common authentication module 16 provides affiliation information to the application as necessary. For example, in the case of an educational application, units acquired by a plurality of companies to which the user belongs can be displayed together. Here, the applications using the common authentication module 16 are various such as an application related to sales orders and an application related to production design in addition to an educational application.

  In S71, the user A activates an application on the PC. The activated application accesses the common authentication module 16 and activates the common authentication module 16 (S72). At this time, the application authentication unit 104 of the common authentication module 16 stores information for specifying the application started by the user A in the buffer.

  The screen display control unit 106 of the common authentication module 16 displays a login screen on the PC operated by the user A (S73). In S74, the authentication unit 102 of the common authentication module 16 acquires the user ID and password input by the user A and temporarily stores them.

  The application authentication unit 104 of the common authentication module 16 inquires the LDAP replica database 15 about information related to the application started by the user A (S75). The common authentication module 16 acquires application information related to the application started by the user A from the LDAP replica database 15 (S76). The application authentication unit 104 of the common authentication module 16 detects that the application started by the user A is stored as an appropriate application based on the application information acquired from the LDAP replica database 15, and authenticates the application ( S77).

  The common authentication module 16 may be configured to transmit information specifying an application to the LDAP replica database 15, authenticate the application in the LDAP replica database 15, and the common authentication module 16 acquires an authentication result.

  Next, the authentication unit 102 of the common authentication module 16 requests the affiliation information associated with the user ID from the LDAP replica database 15 (S78). When the authentication unit 102 acquires the affiliation information of the user A (S79), the authentication unit 102 authenticates the user A based on the affiliation information of the LDAP server (S80). Here, as in the case of application authentication, the LDAP replica database 15 can authenticate the user A and the common authentication module 15 can acquire the authentication result.

  The common authentication module 16 displays a screen that allows the user A to select which affiliation information to acquire when the affiliation destination of the user A is plural (S81). When the user A selects an affiliation for which information about the activated application is to be acquired (S82), the common authentication module 16 notifies the application of information regarding the selected affiliation among the affiliation information acquired from the LDAP replica database 15. (S83). The application provides the user with a function corresponding to the affiliation information that the user desires to acquire (S84).

  In S82, the user selects a company from which information is desired to be acquired. However, the user may always acquire information about the company designated as the default. Moreover, it is good also as setting the company which acquired information last time as a default. Furthermore, it goes without saying that a plurality of companies can be selected and a plurality of affiliation information can be used in an application.

  The affiliation information of a plurality of companies belonging to the same group can be acquired using a single user ID. Further, the common authentication module 16 is automatically activated from the application, and the user can use the affiliation information of the selected company in the application by selecting the company from, for example, a pull-down menu.

(Correspondence of each claim)
In this specification, a company corresponds to an organization, and an employee corresponds to a member. The Oracle database 11 corresponds to a personnel information storage unit, and the SUID employee master database 12 corresponds to a member master storage unit. The CSV file generated based on the information stored in the SUID register database 18 corresponds to output data. The SUID register database 18 corresponds to a register storage unit. The LDAP master database 10 corresponds to a master storage unit. The common authentication module 16 corresponds to affiliation information acquisition means.

  As mentioned above, although this invention has been demonstrated based on each embodiment, this invention is not limited to the requirements shown in the said embodiment. With respect to these points, the gist of the present invention can be changed without departing from the scope of the present invention, and can be appropriately determined according to the application form.

DESCRIPTION OF SYMBOLS 1 Employee information management system 10 LDAP master database 11 Oracle database 12 SUID employee master database 14 SUID database 16 Common authentication module 20 System control part 103 Affiliation information acquisition part

Claims (10)

Information is acquired from a personnel information storage unit that stores information of members of a plurality of organizations, and a first identification number for identifying the members in one organization to which the members belong and the members of the organizations in the organizations Addition in which the first identification number and the attribute information in the other organization are associated with each other when the member information belongs to another organization and the permanent address information that associates the attribute information that is attribute information A member master storage unit for storing information in correspondence;
A member information storage unit that stores a pair of a second identification number for identifying the member in the organization to which the member belongs and registration information that is information of the member in the organization;
The permanent register information stored in the member master storage unit corresponding to the second identification number relating to the one member in the member information storage unit, and the member information stored in the member master storage unit A register storage unit for storing the additional information corresponding to the permanent address information and / or the registration information related to the second identification number;
A master storage unit that stores data for output generated from the register information stored in the register storage unit and the additional information and / or the registration information;
An employee information management system characterized by having   The register storage unit, when the additional information corresponding to the second identification number is deficient, stores the registration information and the registration information related to the second identification information, The employee information management system according to claim 1.   The register storage unit refers to the member master storage unit for the additional information, and stores the additional information with information indicating revocation when the member does not belong to the other organization. The employee information management system according to claim 1 or 2, characterized by the above-mentioned.   The said output corresponding to the said identification number from the master memory | storage part of the said employee information management system as described in any one of Claim 1 to 3 which receives the identification number of the said member from the application using the said data for output. An information processing apparatus comprising affiliation information acquisition means for acquiring business data. The master storage unit has authentication information of the application,
The information processing apparatus according to claim 4, wherein the affiliation information acquisition unit permits access from the application to the master storage unit when the application is authenticated. Information is acquired from a personnel information storage unit that stores information of members of a plurality of organizations, and a first identification number for identifying the members in one organization to which the members belong and the members of the organizations in the organizations Addition in which the first identification number and the attribute information in the other organization are associated with each other when the member information belongs to another organization and the permanent address information that associates the attribute information that is attribute information A member master storage unit for storing information in correspondence;
Based on a member information storage unit that stores a pair of a second identification number for identifying the member in the organization to which the member belongs and registration information that is information of the member in the organization,
The permanent register information stored in the member master storage unit corresponding to the second identification number relating to the one member in the member information storage unit, and the member information stored in the member master storage unit An information storage procedure for storing, in a register storage unit, the additional information corresponding to the domicile information and / or the registration information related to the second identification number;
An output data generation procedure for generating output data from the permanent information stored in the register storage unit by the information storage procedure, and the additional information and / or the registration information;
A master storage procedure for reading out the output data and storing it in a master storage unit;
A method for generating an employee information management system, comprising:   In the information storage procedure, when the additional information corresponding to the second identification number is insufficient, the permanent information and the registration information related to the second identification information are stored. The employee information management system generation method according to claim 6. The additional information includes information indicating an expiration date of the additional information,
8. The employee information management system generation method according to claim 6 or 7, wherein, in the information storage procedure, when the expiration date is exceeded, information indicating revocation is added to the additional information and stored.   An employee information management system generation program for causing a computer to execute the employee information management system generation method according to any one of claims 6 to 8.   The said output data corresponding to the said identification number from the master memory | storage part of the said employee information management system as described in any one of Claim 1 to 3 which receives the employee's identification number from the application using the said data for output An information acquisition method comprising a belonging information acquisition procedure for acquiring.

Images