Enterprise employment information management method and related equipment

Abstract

The embodiment of the invention discloses an enterprise employment information management method and related equipment, which are used for performing enterprise employment information management under the conditions of reducing storage space occupation and improving query efficiency. The method provided by the embodiment of the invention comprises the following steps: acquiring employment information of employee dimensions of each employee of an enterprise and employment information of organization distribution dimensions; generating and storing a target employee main table and a target organization distribution main table of each employee based on employee dimension employment information of each employee and organization distribution dimension employment information of each employee; acquiring main table employment information of target time in a target time stage from a target employee main table of the target employee and a target organization distribution main table of the target employee, and / or acquiring auxiliary table employment information of the target time from the target employee auxiliary table of the target employee and the target organization distribution auxiliary table of the target employee based on the index value corresponding to the target time stage.

Description

Technical Field

[0001] This application relates to the field of enterprise employment information management, and more specifically, to enterprise employment information management methods, enterprise employment information management devices, enterprise employment information management equipment, computer-readable storage media, and computer program products containing instructions. Background Technology

[0002] With the development of information technology, enterprises' demand for employment information management is constantly growing. Therefore, an effective method for enterprise employment information management is needed.

[0003] Existing enterprise employment information management methods employ a three-tiered structure to record the relationship between employees and the enterprise: natural persons, enterprise persons, and organizational persons. The natural person tier records basic employee information, such as identification details and contact information, along with other related supplementary information. The enterprise person tier includes employee information within the enterprise, such as their permanent work location and length of service, along with other related supplementary information. The organizational person tier records employee work experience within the organizational structure, reporting relationships, and other related supplementary information. This information is managed through a historical model, which records data changes over time horizontally and data revision history vertically. The system uses master data recording to enable traceability of historical data such as employee salaries, attendance, talent evaluation, and performance.

[0004] However, existing technologies use a three-tiered structure (natural person, enterprise person, organization person) to manage employee information, leading to data redundancy and excessively long data chains. The repeated storage of information such as employee ID and name increases update and maintenance costs, while strong correlations complicate data management. Furthermore, historical models store large amounts of data, resulting in significant storage space consumption and low query efficiency. Summary of the Invention

[0005] This application provides a method, device, equipment, computer-readable storage medium, and computer program product containing instructions for managing enterprise employment information, which can reduce storage space usage and improve query efficiency while managing enterprise employment information.

[0006] In a first aspect, embodiments of this application provide a method for managing enterprise employment information, including:

[0007] Obtain employment information for each employee of the enterprise, including both employee-level and organizational allocation-level employment information.

[0008] Based on the time sequence of each employment status corresponding to the time stage, and based on the employment information of each employee in the employee dimension and the employment information in the organization allocation dimension, a target employee master table and a target organization allocation master table for each employee are generated and stored. The target employee master table for each employee is associated with a target employee supplementary table for each employee, and the target organization allocation master table for each employee is associated with a target organization allocation supplementary table for each employee.

[0009] The query request for employment information based on the target employee's target time involves retrieving the target main table employment information for the target time period from the target employee's target employee main table and target organization allocation main table, and / or retrieving the target supplementary table employment information for the target time period from the target employee supplementary table and target organization allocation supplementary table based on the index value corresponding to the target time period.

[0010] Secondly, embodiments of this application provide an enterprise employment information management device, comprising:

[0011] The acquisition unit is used to acquire employment information for each employee of the enterprise, including employee-level and organizational allocation-level employment information.

[0012] The generation unit is used to generate and store the target employee master table and the target organization allocation master table for each employee according to the time sequence of the time stage corresponding to each employment status, based on the employment information of each employee in the employee dimension and the employment information in the organization allocation dimension. The target employee master table of each employee is associated with the target employee supplementary table of each employee, and the target organization allocation master table of each employee is associated with the target organization allocation supplementary table of each employee.

[0013] The acquisition unit is further configured to, based on the query request for the employment information of the target employee at the target time, obtain the target main table employment information of the target time under the target time period from the target employee main table and the target organization allocation main table of the target employee, and / or obtain the target supplementary table employment information of the target time from the target employee supplementary table and the target organization allocation supplementary table of the target employee based on the index value corresponding to the target time period.

[0014] Thirdly, embodiments of this application provide an enterprise employment information management device, comprising:

[0015] Central processing unit, memory, input / output interfaces, wired or wireless network interfaces, and power supply;

[0016] The memory is either a short-term storage memory or a persistent storage memory;

[0017] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the aforementioned enterprise employment information management method.

[0018] Fourthly, embodiments of this application provide a computer-readable storage medium including instructions that, when executed on a computer, cause the computer to perform the aforementioned enterprise employment information management method.

[0019] Fifthly, embodiments of this application provide a computer program product containing instructions that, when run on a computer, cause the computer to execute the aforementioned enterprise employment information management method.

[0020] As can be seen from the above technical solutions, the embodiments of this application have the following advantages: Based on the time sequence corresponding to each employment status and the employment information of each employee (employee dimension and organization allocation dimension), a target employee master table and a target organization allocation master table are generated and stored for each employee, and associated with corresponding supplementary tables. This avoids duplicate storage of the same information and reduces data redundancy. By organizing and indexing enterprise employment information according to time stages, queries can quickly locate data at a specific time point, thereby reducing storage requirements and improving query efficiency. Therefore, the enterprise employment information management method of this application has a small storage space requirement and high query efficiency.

[0021] Accordingly, the enterprise employment information management device, enterprise employment information management equipment, computer-readable storage medium, and computer program product containing instructions provided in this application also have the aforementioned technical effects. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the architecture of an enterprise employment information management system disclosed in an embodiment of this application;

[0023] Figure 2-1 This is a flowchart illustrating a method for managing enterprise employment information disclosed in an embodiment of this application;

[0024] Figure 2-2 This is a schematic diagram of an organizational allocation table for an employee based on redundancy design during the employment phase, as disclosed in an embodiment of this application.

[0025] Figure 2-3 This is a schematic diagram of a method for generating transaction change records based on changing transactions disclosed in this application;

[0026] Figure 2-4 This is a schematic diagram illustrating a method for storing transaction change records in JSON format, as disclosed in an embodiment of this application.

[0027] Figure 2-5 This is a schematic diagram illustrating the management of extreme value information based on a historical highest record table, as disclosed in an embodiment of this application.

[0028] Figure 3This is a schematic diagram of the structure of an enterprise employment information management device disclosed in an embodiment of this application;

[0029] Figure 4 This is a schematic diagram of the structure of an enterprise employment information management device disclosed in an embodiment of this application. Detailed Implementation

[0030] This application provides a method, device, equipment, computer-readable storage medium, and computer program product containing instructions for managing enterprise employment information, which can reduce storage space usage and improve query efficiency while managing enterprise employment information.

[0031] Please see Figure 1 The architecture of the enterprise employment information management system in this application embodiment includes:

[0032] The enterprise employment information management device 101 and client 102 are configured. When managing enterprise employment information, the enterprise employment information management device 101 can connect to the client 102. The enterprise employment information management device 101 can obtain employment information of each employee of the enterprise from the client 102, including employee-level and organization-level employment information. It can generate and store target employee master tables and target organization-level master tables for each employee based on the time sequence corresponding to each employment status and the employee-level and organization-level employment information. Based on query requests for target employee employment information at target time sent by the client 102, it can retrieve target time master table employment information for the target time period from the target employee master table and the target employee target organization-level master table, and / or retrieve target time supplementary table employment information from the target employee supplementary table and the target employee target organization-level supplementary table based on the index value corresponding to the target time period.

[0033] based on Figure 1 Please refer to the enterprise employment information management system shown. Figure 2-1 , Figure 2-1 This is a flowchart illustrating a method for managing enterprise employment information disclosed in an embodiment of this application. The method includes:

[0034] 201. Obtain employment information for each employee of the enterprise, including both employee-level and organizational allocation-level employment information.

[0035] In one alternative implementation, "employee" refers to a specific identity of a natural person after establishing an employment relationship with an enterprise. This includes formal employees, interns, temporary workers, international workers, and other external personnel. Employment information at the employee level refers to information related to the individual employee, such as identification information and contact details. Employment information at the organizational level refers to the employee's specific responsibilities and job assignments within the organization, including department, position, role, reporting relationship, work location, salary, and benefits.

[0036] 202. Based on the time sequence of each employment status corresponding to the time stage, generate and store the target employee master table and target organization allocation master table for each employee, based on the employment information of each employee in the employee dimension and the employment information in the organization allocation dimension. The target employee master table of each employee is associated with the target employee supplementary table of each employee, and the target organization allocation master table of each employee is associated with the target organization allocation supplementary table of each employee.

[0037] In one optional implementation, the time phase corresponding to each employment status refers to the time period corresponding to different employment statuses of an employee within the company, such as onboarding, currently employed, and offboarding. The employee's target employee master table is a database table storing the employee's main employment information, such as employee ID, name, and onboarding date. The employee's target organization assignment master table is a database table storing the employee's specific responsibilities and job assignments within the organization. The employee's target employee supplementary table is a database table containing detailed employee information, such as educational background and work experience. The employee's target organization assignment supplementary table is a database table containing detailed information about the employee's specific responsibilities and job assignments within the organization, such as work experience and years of service. By associating and binding time phases with employment information, core information (i.e., main employment information) is stored in the employee master table and organization assignment master table in chronological order (from onboarding date to offboarding date), ensuring the continuity of business data, simplifying the data model, and achieving data decoupling and weak associations. This timeline-based approach can retain only the final result of the personnel master data, reducing unnecessary data storage and lowering storage requirements. It is understandable that specific employment status and time phases can present multiple patterns, such as continuous and non-overlapping, intermittent and non-overlapping, and intermittent and possibly overlapping, etc., and the specific pattern is not limited here.

[0038] 203. Query requests for employment information based on the target employee's target time: retrieve the main table employment information for the target time under the target time period from the target employee's main table and the target organization allocation main table, and / or retrieve the supplementary table employment information for the target time from the target employee's supplementary table and the target organization allocation supplementary table based on the index value corresponding to the target time period.

[0039] In one optional implementation, the main table employment information refers to key employment information stored in the employee main table, such as employee ID, position, department, etc. The supplementary table employment information refers to detailed information stored in the supplementary table, such as employee educational background, work history, skills certificates, etc. The triggering condition (triggering mechanism) is determined by the specific content of the query request: if the query request is only used to retrieve main table employment information, the required data is retrieved from the main table (employee main table and / or organization allocation main table). If the query request is only used to retrieve supplementary table employment information, the index value for the time period is first determined, and then information is retrieved from the corresponding supplementary table (employee supplementary table and / or organization allocation supplementary table) based on the index value for the time period. If the query request is used to retrieve both main table employment information and supplementary table employment information, the required data is retrieved from the main table (employee main table and / or organization allocation main table), and after determining the index value for the time period, information is retrieved from the corresponding supplementary table (employee supplementary table and / or organization allocation supplementary table) based on the index value for the time period.

[0040] In this way, based on the time sequence corresponding to each employment status, and using the employment information at the employee and organizational levels for each employee, a target employee master table and a target organizational allocation master table are generated and stored, and associated with the corresponding supplementary tables. This avoids duplicate storage of the same information and reduces data redundancy. By organizing and indexing enterprise employment information by time period, queries can quickly locate data at a specific time point, thereby reducing storage requirements and improving query efficiency. Therefore, the enterprise employment information management method of this application has a small storage space requirement and high query efficiency.

[0041] In one optional implementation, according to the time sequence of the time stages corresponding to each employment status, a target employee master table and a target organization allocation master table are generated and stored for each employee based on the employment information of each employee's employee dimension and the employment information of each employee's organization allocation dimension. This includes: determining each employment stage of each employee based on the target employee supplementary table and the target organization allocation supplementary table, and the time stages corresponding to each employment status under each employment stage of each employee; and generating and storing the target employee master table and the target organization allocation master table for each employee based on the time sequence of the time stages corresponding to each employment status under each employment stage of each employee. Furthermore, the query request based on the target employee's target time employment information retrieves the target main table employment information for the target time period from the target employee's target employee main table and the target organization allocation main table, and / or retrieves the target supplementary table employment information for the target time period from the target employee's target employee supplementary table and the target organization allocation supplementary table based on the index value corresponding to the target time period. This includes: retrieving the initial main table employment information for the target employment period corresponding to the target time from the target employee's target employee main table and the target organization allocation main table, and retrieving the target main table employment information for the target time period from the initial main table employment information, and / or retrieving the initial supplementary table employment information for the target employment period from the target employee supplementary table and the target organization allocation supplementary table based on the index value corresponding to the target employment period, and retrieving the target supplementary table employment information for the target time period from the initial supplementary table employment information.

[0042] Specifically, an employee's employment stages refer to different time periods during which an employee is employed by a company. Employment stages include the time periods of employment status such as onboarding, starting work, and leaving the company. For example, the time period when an employee first works for this company is employment stage 1, and the time period when the employee leaves and then rejoins the same company is employment stage 2. Employment stages are related to the employee's employment contract or work status and are arranged chronologically. Each stage may contain different employment information, such as job changes, departmental adjustments, and salary changes. The index value corresponding to the target employment stage refers to a reference value or identifier in the database used to quickly find data for a specific employment stage. Based on the target employee appendix and the target organization allocation appendix for each employee, the employment stages for each employee can be determined by recording the start and end dates of each stage, thus achieving decoupling of the data model. Please refer to [link / reference] for details. Figure 2-2 , Figure 2-2 This is a schematic diagram of an organizational allocation table for an employee based on redundancy design during the employment phase, as disclosed in an embodiment of this application. Figure 2-2It can be seen that an employee has two employment phases, namely Employment Phase 1 and Employment Phase 2. Employment Phase 1 includes three time periods: probationary period (January 1, 2000 - June 30, 2000), formal employment period (July 2, 2000 - September 1, 2002), and termination period (September 2, 2002 - October 31, 2003). Employment Phase 2 includes two time periods: probationary period (November 1, 2003 - April 30, 2004), and formal employment period (May 1, 2004 - present, after formal employment).

[0043] It's important to understand that you should first determine the employment stage you're querying. This is a broad time frame, which helps you quickly locate the relevant dataset. After defining the broad scope (employment stage), you can then further refine it to the specific time frame corresponding to the employment status, allowing for more precise data queries.

[0044] Organizing employee hiring information by hiring stage achieves data isolation and orderly management. Linking these stages with supplementary tables (such as employee and organization assignment tables) reduces strong correlations between data. Redundant fields (hiring stages) are calculated by recording the start and end dates of each stage, decoupling the data model. When processing query requests, a broad time range (hiring stage) is first determined, and then more precise queries are performed within this range. This hierarchical query method not only more efficiently links related tables, improving query efficiency, but also makes data management more flexible and easier to maintain. In this way, the system can better adapt to changes in business needs and also facilitates future data expansion and system upgrades.

[0045] In one optional implementation, according to the time sequence of each employment status corresponding to the time stage, a target employee master table and a target organization allocation master table for each employee are generated and stored based on the employment information of each employee at the employee dimension and the employment information at the organization allocation dimension. This includes: generating and storing an initial employee master table and an initial organization allocation master table for each employee according to the time sequence of each employment status corresponding to the time stage, based on the employment information of each employee at the employee dimension and the employment information at the organization allocation dimension. Each initial employee master table is associated with an initial employee supplementary table for each employee, and each initial organization allocation master table is associated with an initial organization allocation supplementary table for each employee. A corresponding target transaction change record is generated based on at least one employment information change transaction of the enterprise. The transaction change record includes change information of each employee's employment information at the employee dimension and the employment information at the organization allocation dimension. Based on the target transaction change record, the employment information in the master tables of the initial employee master table and the initial organization allocation master table for each employee is updated, and the employment information in the supplementary tables of the initial employee supplementary table and the initial organization allocation supplementary table for each employee is updated.

[0046] Specifically, at least one employment information change transaction for an enterprise refers to an event in which an employee's employment status changes, such as onboarding, resignation, or job change. Each change triggers a transaction, recording the relevant employment information changes. The transaction change record refers to the record generated by the system for each employment information change transaction, which details the content of the change, including changes in information at the employee level (such as personal information) and organizational allocation level (such as department and position).

[0047] It's important to understand that core data (core information, i.e., primary employment information) is stored in the employee master table and organization assignment master table in chronological order (from start date to finish date) to ensure the continuity of business data. Each data addition or revision is logged. When the start or end dates in the employee master table and organization assignment master table are adjusted, the system automatically updates the start and end times in the relevant supplementary tables (employee supplementary table and organization assignment supplementary table) to ensure data continuity and consistency. This timeline model, retaining only the final result of the personnel master data, reduces unnecessary data storage and lowers storage requirements. It's understandable that specific employment statuses and time periods can have various patterns, such as non-interrupted and non-overlapping, intermittent and non-overlapping, and intermittent and overlapping, but no specific limitations are made here.

[0048] Please refer to details. Figure 2-3 , Figure 2-3 This is a schematic diagram of a method for generating transaction change records based on changing transactions disclosed in this application. Figure 2-3 As can be seen, changes in personnel master data are driven by transaction changes, and these changes in personnel master data are then written back to the transaction change details. This process ensures that every change in employment information is recorded in detail, and these records can be used to update the master data (data in the employee master table and the organization assignment master table), thereby maintaining data accuracy and integrity. Secondly, transaction change records can be stored in JSON format, which ensures both the future scalability of the personnel master data model and prevents data loss, allowing downstream data consumption. For details, please refer to [link to relevant documentation]. Figure 2-4 , Figure 2-4 This is a schematic diagram of a JSON format storage of transaction change records disclosed in an embodiment of this application. The system generates a transaction change record for each change in employee information. These transaction change records are stored in JSON format and include detailed information such as the changed entity, data changes, data ID, and data before and after the change. The stored JSON format data can be consumed by downstream systems or applications for data analysis, auditing, or other business logic.

[0049] By separating currently valid data (the personnel model table) from historical change records (the transaction change record table), query performance can be optimized. Secondly, database transactions ensure consistency between core model data changes and change records, guaranteeing data accuracy. Thirdly, downstream systems can subscribe to the change record table, consuming historical data changes on demand, improving system flexibility and scalability. Furthermore, by ensuring consistency between the core model and change records through database transactions, and by designing and constructing a continuous and unambiguous data timeline, the traceability of the data lifecycle is ensured, meeting audit and compliance requirements. In summary, this approach improves the efficiency and reliability of enterprise employment information management by optimizing data storage structure and query mechanisms, while maintaining data integrity and traceability.

[0050] In one optional implementation, a corresponding target transaction change record is generated based on at least one employment information change transaction of the enterprise, including at least one of the following situations: if at least one employment document of the enterprise meets the preset transaction change rules, a target transaction change record is generated; the target transaction change record is generated based on the modification information of each employee's initial employee master table, initial organization allocation master table, initial employee supplementary table and / or initial organization allocation supplementary table.

[0051] Specifically, an employment document refers to a single event or record document that documents changes in employee employment information, such as documents for employee transfers, promotions, or demotions. Preset transaction change rules refer to the standards or conditions set by the company for these changes. When a change meets these rules, the system automatically generates a transaction change record, including but not limited to documents meeting rules for transfers, promotions, or demotions; specific details are not limited here. Modifying information refers to correcting existing data, such as correcting incorrect start dates or updating incorrect department information.

[0052] This allows for the automated recording of changes in employee information, reducing manual operations, ensuring data accuracy and integrity, and improving the efficiency of data management.

[0053] In an optional implementation, the method further includes: periodically checking whether there are any target employment information change transactions of an enterprise that have not generated corresponding transaction change records; if there are target employment information change transactions, generating transaction change records corresponding to the target employment information change transactions; and updating the main table employment information in the initial employee main table and the initial organization allocation main table of each employee, as well as the supplementary table employment information in the initial employee supplementary table and the initial organization allocation supplementary table of each employee, based on the transaction change records corresponding to the target employment information change transactions.

[0054] Specifically, the system periodically (e.g., daily or weekly) automatically checks for any employment information changes that failed to generate corresponding transaction change records. This could be due to system errors, operational mistakes, or other reasons that prevented the changes from being recorded. To ensure data accuracy, the system uses real-time calculation and scheduled tasks to update employment information. Real-time calculation means that whenever employment information changes, the system immediately generates and updates the transaction change record. Scheduled tasks mean that the system will run at a predetermined time (e.g., at the end of each day) to check and update all unprocessed changes. The system can update the relevant main and supplementary tables of employment information one by one based on the employee's employee ID, ensuring that each employee's information is up-to-date and accurate.

[0055] In this way, through this model of "real-time calculation + scheduled task checking + update by employee number," the system can ensure data reliability even if problems occur during the execution of information-changing transactions, thanks to the scheduled checking and updating mechanism. This approach ensures the accuracy and completeness of employment information, supporting enterprises in making decisions based on the latest data.

[0056] In an optional implementation, the method further includes: determining a historical maximum record table for each employee from a target employee appendix and / or a target organization allocation appendix, wherein the historical maximum record table for each employee includes historical maximum information for each employee; and determining and returning the target historical maximum information from the historical maximum record table for each target employee based on a query request for target historical maximum information for a target time.

[0057] Specifically, "highest historical information" refers to an employee's highest educational attainment, highest job level, highest salary, and other highest records achieved within the company; the specific type is not limited. The highest record table records the "highest historical value" valid within a specific time interval, rather than a detailed record of each change. This means the table stores the highest record an employee achieved at a given point in time, not the detailed process of each change. Furthermore, the system does not directly maintain historical highest values ​​in frequently changing main business tables (such as job level tables), but instead stores this information through a separate, simply structured highest record table. This achieves decoupling of data storage, reducing dependencies between different data tables and simplifying data management. For example, during the job level promotion process, when an employee first obtains a job level, the system creates a record in the highest record table, recording that the job level is the current historical highest value, and recording its effective start and end times. When an employee is promoted, the system does not modify the existing records. Instead, it first terminates the old records, updates the end time of the original highest record to the day before the promotion, and then inserts a new highest record with the new job level, a start time of the promotion date, and an end time of a distant future date, representing the current validity. Please refer to details. Figure 2-5 , Figure 2-5 This is a schematic diagram illustrating the management of maximum / minimum value information based on a historical maximum record table, as disclosed in an embodiment of this application. When an employee first obtains a job level (e.g., L1), a record is created in the maximum record table, recording that job level as the current historical maximum value, and its effective start and end times. When an employee is promoted (e.g., from L2 to L3), the system does not modify the existing record. Instead, it first terminates the old record, updating the end time of the original maximum record (L2) to the day before the promotion. Then, a new record is inserted—a new maximum record with job level L3, a start time of the promotion day, and an end time of a distant future date (e.g., 2999-12-31) representing the current validity. This design ensures that querying the historical maximum value at any point in time can quickly locate a unique record through time matching. Next, please refer to Table 1.

[0058]

[0059] Table 1

[0060] As shown in Table 1, Zhang San's highest record ID for job grade and rank was L1 during the period from January 1, 2021 to December 31, 2021; L2 during the period from January 1, 2022 to December 31, 2024; and L3 during the period from January 1, 2025 to December 31, 2029.

[0061] In this way, a historical high record table is generated for each employee. When querying the historical high value at any point in time, the unique maximum value record in the historical high record table can be quickly located directly by time matching, thereby improving the query efficiency and accuracy of historical high information and simplifying data maintenance.

[0062] It is worth mentioning that the "model-record decoupling" and "strong-weak association separation" architecture proposed in this application refers to separating the data model (i.e., the structural definition of data) from specific data records (i.e., data instances) in system design, while reducing strong dependencies between modules, allowing each module to operate and expand independently. This design allows for adjustments to only the affected specific modules when business requirements change, without having to rebuild the entire data model, thereby improving the system's adaptability and flexibility, and providing greater flexibility and expansion space for future business development. In short, this architecture makes the system more adaptable to changes and easier to expand with new functions by reducing the coupling between modules.

[0063] In an optional implementation, the method further includes: based on a query request for target historical maximum information of target employees at a target time, determining a historical maximum record table for each employee from a target employee appendix and / or a target organization allocation appendix, wherein the historical maximum record table for each employee includes the historical maximum information of each employee, and determining and returning the target historical maximum information from the historical maximum record table of the target employees.

[0064] It's important to understand that if the data in the supplementary tables changes frequently, pre-generating a historical high record table might lead to constant regeneration due to frequent data updates, resulting in wasted resources. Generating the historical high record table only after receiving a query request avoids this redundant and ineffective generation, thus saving system resources. Secondly, since the historical high record table is dynamically generated based on actual query needs, it ensures that the returned information is up-to-date and accurate, improving query efficiency and accuracy. Furthermore, dynamically generating the historical high record table reduces the need to maintain static tables. System administrators do not need to periodically update or verify the accuracy of the historical high record table because each query generates a new record table, simplifying data maintenance.

[0065] For further details, please refer to Figure 3 One embodiment of the enterprise employment information management device in this application includes:

[0066] The acquisition unit is used to acquire employment information for each employee of the enterprise, including employee-level and organizational allocation-level employment information.

[0067] The generation unit is used to generate and store the target employee master table and the target organization allocation master table for each employee according to the time sequence of the time stage corresponding to each employment status, based on the employment information of each employee in the employee dimension and the employment information in the organization allocation dimension. The target employee master table of each employee is associated with the target employee supplementary table of each employee, and the target organization allocation master table of each employee is associated with the target organization allocation supplementary table of each employee.

[0068] The acquisition unit is further configured to, based on the query request for the employment information of the target employee at the target time, obtain the target main table employment information of the target time under the target time period from the target employee main table and the target organization allocation main table of the target employee, and / or obtain the target supplementary table employment information of the target time from the target employee supplementary table and the target organization allocation supplementary table of the target employee based on the index value corresponding to the target time period.

[0069] In one alternative implementation, the generating unit may be used for:

[0070] Based on the target employee appendix and target organization allocation appendix of each employee, determine each employment stage of each employee, and the time stage corresponding to each employment status under each employment stage of each employee. According to the time order of each employment status corresponding to each employment stage of each employee, generate and store the target employee master table and target organization allocation master table of each employee based on the employment information of each employee dimension and the employment information of each employee organization allocation dimension.

[0071] The acquisition unit can be used for:

[0072] The query request for employment information based on the target employee's target time involves retrieving the initial master table employment information of the target employment stage corresponding to the target time from the target employee master table and the target organization allocation master table of the target employee, retrieving the target master table employment information of the target time under the target time stage from the initial master table employment information, and / or retrieving the initial supplementary table employment information of the target employment stage from the target employee supplementary table and the target organization allocation supplementary table of the target employee based on the index value corresponding to the target employment stage, and retrieving the target supplementary table employment information of the target time from the initial supplementary table employment information.

[0073] In one alternative implementation, the generating unit may be used for:

[0074] Based on the time sequence corresponding to each employment status, initial employee master tables and initial organization allocation master tables are generated and stored for each employee, based on their employment information at the employee level and their employment information at the organization allocation level. Each employee's initial employee master table is associated with its initial employee supplementary table, and each employee's initial organization allocation master table is associated with its initial organization allocation supplementary table. Based on at least one employment information change transaction of the enterprise, a corresponding target transaction change record is generated. The transaction change record includes change information of each employee's employment information at the employee level and their employment information at the organization allocation level. Based on the target transaction change record, the employment information in the master tables of each employee's initial employee master table and initial organization allocation master table is updated, as are the employment information in the supplementary tables of each employee's initial employee supplementary table and initial organization allocation supplementary table.

[0075] In one alternative implementation, the generating unit may be used for:

[0076] If at least one employment document of the enterprise satisfies the preset transaction change rules, the target transaction change record is generated based on the modification information of the initial employee master table, the initial organization allocation master table, the initial employee supplementary table and / or the initial organization allocation supplementary table for each employee.

[0077] In one optional implementation, the enterprise employment information management device further includes: a checking unit and an updating unit;

[0078] The inspection unit can be used for:

[0079] Regularly check whether there are any changes in the target employment information of the enterprise that have not generated corresponding transaction change records;

[0080] The update unit can be used for:

[0081] If a transaction involving changes to the target employment information exists, a transaction change record corresponding to the target employment information change transaction is generated. Based on the transaction change record corresponding to the target employment information change transaction, the employment information in the main table of the initial employee table and the main table of the initial organization allocation table for each employee, as well as the employment information in the supplementary table of the initial employee table and the supplementary table of the initial organization allocation table for each employee, are updated.

[0082] In an optional implementation, the enterprise employment information management device further includes: a determining unit, which can be used to:

[0083] The historical highest record table of each employee is determined from the target employee appendix and / or the target organization allocation appendix of each employee. The historical highest record table of each employee includes the historical highest information of each employee. Based on the query request for the target historical highest information of the target employee at the target time, the target historical highest information is determined from the historical highest record table of the target employee and returned.

[0084] For further details, please refer to Figure 4 One embodiment of the enterprise employment information management device in this application includes:

[0085] Central processing unit 401, memory 405, input / output interface 404, wired or wireless network interface 403, and power supply 402;

[0086] Memory 405 is either a short-term storage memory or a persistent storage memory;

[0087] The central processing unit 401 is configured to communicate with the memory 405 and execute instructions stored in the memory 405 to perform the aforementioned operations. Figure 2-1 The method in the illustrated embodiment.

[0088] Furthermore, embodiments of this application also provide a computer-readable storage medium, which includes instructions that, when executed on a computer, cause the computer to perform the aforementioned... Figure 2-1 The method in the illustrated embodiment.

[0089] Furthermore, embodiments of this application also provide a computer program product containing instructions, which, when run on a computer, causes the computer to perform the aforementioned... Figure 2-1 The method in the illustrated embodiment.

[0090] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0091] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0092] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0093] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0094] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0095] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for managing enterprise employment information, characterized in that, include: Obtain employment information for each employee of the enterprise, including both employee-level and organizational allocation-level employment information. Based on the time sequence of each employment status corresponding to the time stage, and based on the employment information of each employee in the employee dimension and the employment information in the organization allocation dimension, a target employee master table and a target organization allocation master table for each employee are generated and stored. The target employee master table for each employee is associated with a target employee supplementary table for each employee, and the target organization allocation master table for each employee is associated with a target organization allocation supplementary table for each employee. The query request for employment information based on the target employee's target time involves retrieving the target main table employment information for the target time period from the target employee's target employee main table and target organization allocation main table, and / or retrieving the target supplementary table employment information for the target time period from the target employee supplementary table and target organization allocation supplementary table based on the index value corresponding to the target time period.

2. The method according to claim 1, characterized in that, The process of generating and storing a target employee master table and a target organization allocation master table for each employee, based on the employee-level employment information and organization allocation-level employment information of each employee, according to the time sequence corresponding to each employment status and time stage, includes: Based on the target employee appendix and the target organization allocation appendix for each employee, determine each employment stage of each employee, and the time stage corresponding to each employment status under each employment stage of each employee. Based on the time sequence of each employment status corresponding to each employment stage of each employee, and the employment information of each employee in the employee dimension and the employment information in the organization allocation dimension, the target employee master table and the target organization allocation master table of each employee are generated and stored. The query request for employment information based on the target employee's target time involves retrieving the target main table employment information for the target time period from the target employee's target employee main table and the target organization allocation main table, and / or retrieving the target supplementary table employment information for the target time period from the target employee supplementary table and the target organization allocation supplementary table based on the index value corresponding to the target time period, including: The query request for employment information based on the target employee's target time involves retrieving the initial master table employment information of the target employment stage corresponding to the target time from the target employee master table and the target organization allocation master table of the target employee, retrieving the target master table employment information of the target time under the target time stage from the initial master table employment information, and / or retrieving the initial supplementary table employment information of the target employment stage from the target employee supplementary table and the target organization allocation supplementary table of the target employee based on the index value corresponding to the target employment stage, and retrieving the target supplementary table employment information of the target time from the initial supplementary table employment information.

3. The method according to claim 1, characterized in that, The process of generating and storing a target employee master table and a target organization allocation master table for each employee, based on the employee-level employment information and organization allocation-level employment information of each employee, according to the time sequence corresponding to each employment status and time stage, includes: According to the time sequence of each employment status corresponding to the time stage, based on the employment information of each employee in the employee dimension and the employment information in the organization allocation dimension, the initial employee master table and the initial organization allocation master table of each employee are generated and stored. The initial employee master table of each employee is associated with the initial employee supplementary table of each employee, and the initial organization allocation information master table of each employee is associated with the initial organization allocation supplementary table of each employee. Based on at least one employment information change transaction of the enterprise, a corresponding target transaction change record is generated. The transaction change record includes the employment information of each employee in the employee dimension and the employment information in the organization allocation dimension. Based on the target transaction change record, update the main table employment information in the initial employee main table and the initial organization allocation main table of each employee, and update the supplementary table employment information in the initial employee supplementary table and the initial organization allocation supplementary table of each employee.

4. The method according to claim 3, characterized in that, The generation of the corresponding target transaction change record based on at least one employment information change transaction of the enterprise includes at least one of the following: If at least one employment document of the enterprise satisfies the preset transaction change rule, then the target transaction change record is generated; Based on the modification information of the initial employee master table, initial organization allocation master table, initial employee supplementary table and / or initial organization allocation supplementary table for each employee, the target transaction change record is generated.

5. The method according to claim 3, characterized in that, The method further includes: Regularly check whether there are any changes in the target employment information of the enterprise that have not generated corresponding transaction change records; If a transaction involving changes to the target employment information exists, a transaction change record corresponding to the target employment information change transaction is generated. Based on the transaction change record corresponding to the target employment information change transaction, the main table employment information in the initial employee main table and the initial organization allocation main table of each employee, as well as the supplementary table employment information in the initial employee supplementary table and the initial organization allocation supplementary table of each employee, are updated.

6. The method according to claim 1, characterized in that, The method further includes: The historical highest record table for each employee is determined from the target employee appendix and / or target organization allocation appendix for each employee, and the historical highest record table for each employee includes the historical highest information for each employee. Based on the query request for the target employee's target time's target historical highest information, determine and return the target historical highest information from the target employee's historical highest record table.

7. A device for managing enterprise employment information, characterized in that, include: The acquisition unit is used to acquire employment information for each employee of the enterprise, including employee-level and organizational allocation-level employment information. The generation unit is used to generate and store the target employee master table and the target organization allocation master table for each employee according to the time sequence of the time stage corresponding to each employment status, based on the employment information of each employee in the employee dimension and the employment information in the organization allocation dimension. The target employee master table of each employee is associated with the target employee supplementary table of each employee, and the target organization allocation master table of each employee is associated with the target organization allocation supplementary table of each employee. The acquisition unit is further configured to, based on the query request for the employment information of the target employee at the target time, obtain the target main table employment information of the target time under the target time period from the target employee main table and the target organization allocation main table of the target employee, and / or obtain the target supplementary table employment information of the target time from the target employee supplementary table and the target organization allocation supplementary table of the target employee based on the index value corresponding to the target time period.

8. An enterprise employment information management device, characterized in that, include: Central processing unit and memory; The memory is either a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 6.

10. A computer program product containing instructions, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1 to 6.

Images