CN108664636B - Data list management method and device, computer equipment and storage medium - Google Patents
Data list management method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN108664636B CN108664636B CN201810462785.2A CN201810462785A CN108664636B CN 108664636 B CN108664636 B CN 108664636B CN 201810462785 A CN201810462785 A CN 201810462785A CN 108664636 B CN108664636 B CN 108664636B
- Authority
- CN
- China
- Prior art keywords
- data
- insured
- list
- historical
- matched
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the application discloses a data list management method and device, computer equipment and a storage medium. The method comprises the steps of obtaining preset screening conditions, and screening data to be guaranteed from a database according to the screening conditions; generating a data list according to the data to be insured; acquiring a historical data processing list; judging whether historical insurance data matched with the data to be insured exist in the historical data processing list; if the historical insurance data matched with the data to be insured exists, acquiring a processing result corresponding to the historical insurance data matched with the data to be insured; and if the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result, updating the data list according to the historical insurance data matched with the data to be insured. The method can improve the efficiency of managing the data list.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for managing a data list, a computer device, and a storage medium.
Background
Lists are an efficient way to manage bulk data. Many application systems can automatically generate lists at present. For example, the data management system may obtain corresponding application data according to a preset condition and generate a list, so that corresponding application operations may be performed subsequently according to the application data in the list. However, in the process of application, the failure of application may be caused by factors such as related system failure, and if the worker cannot find the application data of the failure of application in time, the total amount of application of the related applicant is easily damaged. If the staff screens the application guarantee data of the application guarantee failure from the list manually and applies the application guarantee to the application guarantee data of the application guarantee failure, under the condition that the data quantity is large, large workload is brought to the staff certainly, time consumption is long, efficiency is low, and errors such as omission can occur easily in manual operation.
Disclosure of Invention
The embodiment of the application provides a data list management method and device, computer equipment and a storage medium, so that the efficiency of managing a data list is improved, and the error rate of managing the data list is reduced.
In a first aspect, an embodiment of the present application provides a data list management method, which includes:
acquiring preset screening conditions, and screening out data to be guaranteed from a database according to the screening conditions;
generating a data list according to the data to be insured;
acquiring a historical data processing list, wherein the historical data processing list comprises historical insurance data and processing results corresponding to the historical insurance data;
judging whether historical insurance data matched with the data to be insured exist in the historical data processing list;
if the historical insurance data matched with the data to be insured exists, acquiring a processing result corresponding to the historical insurance data matched with the data to be insured;
and if the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result, updating the data list according to the historical insurance data matched with the data to be insured.
In a second aspect, an embodiment of the present application provides a data list management apparatus, including:
the data acquisition unit is used for acquiring preset screening conditions and screening the data to be guaranteed from the database according to the screening conditions;
the list generating unit is used for generating a data list according to the data to be insured;
the system comprises a list acquisition unit, a list processing unit and a display unit, wherein the list acquisition unit is used for acquiring a historical data processing list, and the historical data processing list comprises historical insurance data and processing results corresponding to the historical insurance data;
the data judgment unit is used for judging whether historical insurance data matched with the data to be insured exist in the historical data processing list or not;
the result acquisition unit is used for acquiring a processing result corresponding to the historical insurance data matched with the data to be insured if the historical insurance data matched with the data to be insured exists;
and the updating unit is used for updating the data list according to the historical insurance data matched with the data to be insured if the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result.
In a third aspect, an embodiment of the present application further provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the data list management method according to any one of the embodiments provided in the present application when executing the computer program.
In a fourth aspect, this application embodiment further provides a storage medium, where the storage medium stores a computer program, where the computer program includes program instructions, and the program instructions, when executed by a processor, cause the processor to execute any one of the data list management methods provided in this application embodiment.
The application provides a data list management method, a data list management device, computer equipment and a storage medium. The data list management method can automatically screen out the historical insurance data of the failure result, and update the current data list according to the historical insurance data, so that the historical insurance data of the failure result can be preset again when the data to be insured in the data list is preset, the whole process does not need manual operation, the time consumption is short, the efficiency is high, and the error rate is low.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of a data list management method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a data list management method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a data list management method according to an embodiment of the present application;
fig. 4 is a schematic block diagram of a data list management apparatus according to an embodiment of the present application;
fig. 5 is a schematic block diagram of a data list management apparatus according to an embodiment of the present application;
fig. 6 is a schematic block diagram of a data list management apparatus according to an embodiment of the present application;
fig. 7 is a schematic block diagram of a computer device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the present application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification of the present application and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
Referring to fig. 1, fig. 1 is a schematic flowchart of a data list management method according to an embodiment of the present application. The data list management method is applied to a management server, for example, the management server may be a server for managing data. As shown in fig. 1, the data list management method includes steps S101 to S106.
S101, obtaining preset screening conditions, and screening out data to be guaranteed from a database according to the screening conditions.
The screening condition is condition information which is preset by a user and used for screening the data to be insured. For example, the screening condition may be set to "the time of entry exceeds 60 months", "the time of entry exceeds 36 months and the position level is above the director", "the time of entry exceeds 96 months". The specific content of the screening condition may be set according to actual requirements, and is not specifically limited herein.
In this embodiment, the management server is provided with a database, and the database can be used for storing relevant data. For example, the database may be used to store personal data for each employee, which may include information such as the name of the employee, the job number, the identification number, the telephone number, the account number of the public deposit, the account number of the social security card, the time of entry, the level of position, etc.
After the management server obtains the screening conditions, at least one piece of data to be insured meeting the screening conditions can be screened from the database. For example, assuming that "the time of job exceeds 96 months" is used as the screening condition, the management server may search the database for the personal data of the employee whose time of job exceeds 96 months, and then use the personal data of the employee meeting the screening condition as the to-be-insured data corresponding to the screening condition. Alternatively, necessary data can be extracted from personal data of the staff meeting the screening condition to form the data to be insured of the staff. The necessary data refers to data necessary for processing the data to be insured subsequently. For example, necessary data such as employee names, identification numbers, and public deposit accounts are extracted from personal data of employees as data to be guaranteed, information such as user telephone numbers, time of employment, job levels, and the like is not necessary for preset processing of subsequently paying public deposits, and in order to reduce the size of files for subsequently forming a data list and reduce the flow consumed by file transmission, the unnecessary data are discarded, that is, the unnecessary data are not used as part of the data to be guaranteed.
In an embodiment, before step S101, the method further includes: judging whether the current time meets a preset condition or not; and if the current time meets the preset condition, executing step S101, namely executing the step of obtaining the preset screening condition and screening the data to be insured from the database according to the screening condition. For example, if the user sets the predetermined condition to 20 th per month, the management server will continuously determine whether the current time meets the predetermined condition at a certain frequency or time interval, i.e., determine whether the current time is 20 th, and if the management server determines that the current time is 20 th, i.e., meets the predetermined condition, step S101 will be executed.
And S102, generating a data list according to the data to be insured.
In the present embodiment, after the data list is generated, the data list will include the data to be insured in step S101. Of course, in other embodiments, the data list may include the number of times corresponding to each piece of data to be insured, in addition to the data to be insured in step S101. For example, assuming that the number of times corresponding to each piece of data to be insured is 1, it is described that the subsequent data processing system needs to perform a predetermined process such as one time of the insuring process on each piece of data to be insured.
S103, acquiring a historical data processing list, wherein the historical data processing list comprises historical insurance data and processing results corresponding to the historical insurance data.
In this embodiment, the management server stores a history data processing list, which is a list generated by the management server last time and processed by the data processing system. The historical data processing list comprises historical insurance data and corresponding processing results. The processing result includes a success result and a failure result.
For example, when the data processing system performs the personal public fund application processing on the data a to be applied in the data list generated by the last management server, the application fails due to the failure of the public fund server, and the processing result corresponding to the data a to be applied is a failure result, and the correspondence may be represented by the identifier "E". If the application is successful, the processing result corresponding to the data a to be applied is a success result, and the correspondence can be represented by a mark "Y". And the data processing system writes the processing result corresponding to each piece of data to be insured into the corresponding position of the data list generated by the last management server to form a historical data processing list.
It should be noted that the data processing system may be installed in a processing server, and the processing server is configured to perform preset processing operations such as insuring on the data to be insurable in the data list generated by the management server.
And S104, judging whether historical insurance data matched with the data to be insured exist in the historical data processing list.
In an embodiment, specifically, a judgment identifier is obtained from the data to be insured; judging whether historical insurance data containing the judgment identification exists in the historical data processing list or not; and if the historical data processing list contains the historical insurance data containing the judgment identification, judging that the historical insurance data matched with the data to be insured exists in the historical data processing list.
For example, a certain piece of data to be insured in the data list generated in step S102 includes personal data such as the name, job number, identity card number, public deposit account number, and time of enrollment of employee a, and it is assumed that the data is identified as the identity card number of employee a. At this time, the identity card number of the employee a is obtained from the data to be insured, and then whether the historical data processing list contains the historical insured data of the identity card number of the employee a is judged. If the historical insurance data containing the identity number of the employee A exists, it is indicated that the personal data of the employee A exists in the historical data processing list, and the personal data corresponding to the employee A is processed by the data processing system in the last data processing process, at this moment, it is determined that the historical insurance data matched with the data to be insured exists, and step S105 is executed.
Of course, in other embodiments, the number of the judgment marks is more than one, and may be two or more. For example, the judgment flag may include the name of employee a and the identification number of employee a, and when it is judged that there is a piece of historical insurance data including both the name of employee a and the identification number of employee a in the historical data processing list, it is judged that there is historical insurance data matching the data to be insured, and step S105 is performed. It can be understood that the specific manner of determining whether the historical insurance data matching the to-be-insured data exists in the historical data processing list may be set according to actual requirements, and is not limited specifically herein.
And S105, if the historical insurance data matched with the data to be insured exists, acquiring a processing result corresponding to the historical insurance data matched with the data to be insured.
Specifically, the management server acquires a processing result corresponding to historical insurance data matched with the data to be insured, and then judges whether the processing result is a failure result; if the processing result is a failure result, step S106 is executed; if the processing result is a successful result, the previous preset processing on the historical insurance data matched with the data to be insured is successfully completed, and the historical insurance data matched with the data to be insured is ignored at the moment.
And S106, if the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result, updating the data list according to the historical insurance data matched with the data to be insured.
Specifically, in an embodiment, updating the data list according to the historical insurance data matched with the data to be insured specifically includes: and merging the matched data to be insured and the historical insured data to update the data list.
Further, in an embodiment, when the data list includes the number of times corresponding to the data to be insured, the number of times corresponding to the matched data to be insured in the data list may be updated to complete updating the data list. For example, when the matched data to be insured and the historical data to be insured are both the personal data corresponding to the employee a, the management server may change the number of times corresponding to the data to be insured corresponding to the employee a in the data list from 1 to 2, thereby completing the merging of the matched data to be insured and the historical data to be insured. In this way, when the data processing system is configured to apply the personal public deposit for 500 yuan/time to the data to be applied in the data list sent by the management server, the data processing system applies the personal public deposit for 1000 yuan when processing the data to be applied corresponding to the employee a, so that the 500 yuan of the previous employee a application failure can be supplemented, and the total application amount of the employee a is ensured to be unchanged.
Of course, the method of updating the data list is not limited to the above method, and other methods are also possible. For example, in another embodiment, updating the data list according to the historical insurance data matching the data to be insured specifically includes: and writing the historical insurance data matched with the data to be insured into the data list to update the data list. For example, if the matched data to be insured and the historical data to be insured are both personal data corresponding to employee a, the historical data to be insured corresponding to employee a may also be written into the data list, that is, there are two pieces of data to be insured corresponding to employee a in the data list. Therefore, when the data processing system carries out personal public deposit insurance investment on the data to be insured in the data list, the data to be insured corresponding to the employee A is processed twice, and the total insurance application amount of the employee A is also ensured to be unchanged.
In this embodiment, no matter which way of updating the data list is adopted, the historical insurance data corresponding to the previous failure result can be re-embodied in the data list, so that the subsequent data processing system can re-perform the preset processing on the historical insurance data, thereby achieving the purpose of re-processing the data which has failed in the past processing.
In an embodiment, as shown in fig. 2, fig. 2 is another schematic flowchart of a data list management method provided in an embodiment of the present application. The data list management method further includes steps S107 and S108.
S107, a data processing list sent by a data processing system is obtained, wherein the data processing list is formed after the data processing system writes a processing result obtained after the data to be insured is subjected to preset processing into the data list.
After the management server updates the data list, the management server may send the data list to the data processing system. The data processing system can perform preset processing operations such as insurance application on the data to be insured in the data list. And the data processing system writes the processing result corresponding to each data to be insured into the data list to form a data processing list, and then sends the data processing list to the management server.
And S108, storing the data processing list and setting the data processing list as a historical data processing list.
And after receiving the data processing list sent by the data processing system, the management server stores and archives the data processing list, and sets the data processing list as a historical data processing list, so that historical insurance data corresponding to the failure result can be acquired from the historical data processing list when the management server generates the data list next time.
The method in the embodiment can automatically screen out the historical insurance data of the failure result, and update the current data list according to the historical insurance data, so that the historical insurance data of the failure result can be subjected to preset processing again when the data to be insured in the data list is subjected to preset processing, the whole process is free from manual operation, the time consumption is short, the efficiency is high, and the error rate is low.
Referring to fig. 3, fig. 3 is a schematic flow chart of a data list management method according to an embodiment of the present application. The data list management method is applied to a management server, for example, the management server may be a server for managing data. As shown in fig. 3, the data list management method includes steps S201 to S208.
S201, obtaining preset screening conditions and service types corresponding to the screening conditions, and screening out data to be guaranteed from a database according to the screening conditions.
The screening condition is condition information for screening data, which is preset by a user. For example, the screening condition may be "time to enter more than 60 months", "time to enter more than 36 months and job level above chief career", "time to enter more than 96 months". The specific content of the screening condition may be set according to actual requirements, and is not specifically limited herein.
The service type is used for enabling the data processing system to perform corresponding data processing on the data to be insured according to the service type. Each service type corresponds to a preset processing mode, so that the data processing system can preset corresponding data to be guaranteed according to the preset processing mode corresponding to the service type. For example, the preset processing mode corresponding to the "long-term service award" is to issue a ten-thousand-element prize to the bank card number in the data to be guaranteed, and then the data processing system performs preset processing of issuing 10000 prizes to the corresponding data to be guaranteed according to the "long-term service award".
In this embodiment, the user may preset a corresponding relationship between the service type and the screening condition, and the management server may store the corresponding relationship. When the management server is acquiring the screening condition, it is also required to acquire a service type corresponding to the screening condition. For example, when the screening condition is "the time of employment exceeds 96 months", the corresponding service type may be "personal accumulation". When the screening condition is that the enrollment time exceeds 60 months, the corresponding service type may be a long-term service award, and the like.
In this embodiment, the management server is provided with a database, and the database may be used to store personal data of each employee, where the personal data may include information such as employee name, job number, identification number, telephone number, account number of public deposit, social security account number, time of employment, and position level.
S202, establishing a corresponding relation between the data to be insured and the service type corresponding to the screening condition, and generating a data list according to the corresponding relation.
After the management server screens the data to be guaranteed from the database according to the screening conditions, a corresponding relation between the service type corresponding to the screening conditions and the data to be guaranteed needs to be established, and a data list is generated according to the corresponding relation. The data list comprises data to be insured, service types and corresponding relations between the data to be insured and the service types.
For example, the management server screens out the personal data corresponding to the employee a as the data to be guaranteed according to the screening condition that the time of entry exceeds 96 months, then establishes a corresponding relationship between the data to be guaranteed corresponding to the employee a and the business type "personal equity fund" corresponding to the screening condition that the time of entry exceeds 96 months, and generates a data list according to the data to be guaranteed corresponding to the employee a, the corresponding business type "personal equity fund" and the relationship between the data to be guaranteed and the business type "personal equity fund".
S203, obtaining a historical data processing list, wherein the historical data processing list comprises historical insurance data, processing results corresponding to the historical insurance data and corresponding business types.
In this embodiment, the management server stores a history data processing list, which is a list generated by the management server last time and processed by the data processing system. The historical data processing list comprises historical insurance data, corresponding processing results and service types. Wherein the processing result comprises a success result and a failure result.
And S204, judging whether historical insurance data matched with the data to be insured exist in the historical data processing list.
S205, if the historical insurance data matched with the data to be insured exists, acquiring a processing result corresponding to the historical insurance data matched with the data to be insured.
And S206, if the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result, judging whether the service types corresponding to the matched data to be insured and the historical insurance data are the same.
And when the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result, the management server further judges whether the service types corresponding to the matched data to be insured and the historical insurance data are the same. For example, the data list stores the data to be insured corresponding to employee a, and the corresponding service type is "personal public fund", and the historical data processing list also stores the data to be insured corresponding to employee a, and the corresponding service type is also "personal public fund", then the management server may determine that the service type of the data to be insured corresponding to employee a is the same as the service type corresponding to the historical data to be insured corresponding to employee a, and then step S207 is executed. If the service type corresponding to the history data processing of the employee a is "administrative public deposit", the management server determines that the service type of the data to be insured corresponding to the employee a is different from the service type corresponding to the history insured data corresponding to the employee a, and then step S208 is executed.
And S207, if the service types corresponding to the matched data to be insured and the historical insured data are the same, combining the matched data to be insured and the historical insured data to update the data list.
When the service types corresponding to the matched data to be insured and the historical data to be insured are the same, the matched data to be insured and the historical data to be insured can be merged to complete the updating of the data list. For example, the number of times corresponding to the to-be-insured data corresponding to the employee a in the data list is changed from 1 to 2, so that the matching to-be-insured data and the history insured data are merged. Thus, when the data processing system issues the personal public deposit according to the data to be guaranteed corresponding to the employee A, the data processing system is assumed to be configured to issue the personal public deposit for 500 yuan/time, and thus the data processing system can issue 1000 yuan to the public deposit account corresponding to the employee A through calculation, so that 500 yuan of the last guarantee failure is supplemented, and the total guarantee amount of the employee A is guaranteed to be unchanged.
And S208, if the matched data to be insured is different from the service type corresponding to the historical data to be insured, writing the historical data to be insured matched with the data to be insured and the corresponding service type into the data list so as to update the data list.
When the matched data to be insured is different from the corresponding business type of the historical data to be insured, the historical data to be insured matched with the data to be insured and the corresponding business type are written into the data list to update the data list, so that the historical data to be insured and the corresponding business type of the failure result also exist in the updated data list. When the data processing system presets the data to be insured in the data list according to the service type, the data processing system can also presets the historical insured data of the failure result according to the service type.
For example, the service type of the data to be guaranteed corresponding to the employee a in the data list is "personal public deposit", and the service type corresponding to the historical guarantee data of the matched failure result is "master public deposit", at this time, the historical guarantee data of the matched failure result and the corresponding service type are written into the data list, so that the data processing system can respectively carry out personal public deposit guarantee and master public deposit guarantee on the data to be guaranteed corresponding to the employee a and the historical guarantee data of the matched failure result when processing the data list subsequently, thereby supplementing the last failed amount of the "public deposit" guarantee, and ensuring that the total amount of the employee a is unchanged.
It should be clearly understood by those skilled in the art that, for simplicity of the description, specific descriptions of some steps in the data list management method may refer to descriptions of corresponding steps in the data list management method in the foregoing embodiment, and are not described herein again.
The method in the embodiment can automatically screen out the historical insurance data of the failure result, and update the current data list according to the historical insurance data, so that the historical insurance data of the failure result can be subjected to preset processing again when the data to be insured in the data list is subjected to preset processing, the whole process is free from manual operation, the time consumption is short, the efficiency is high, and the error rate is low.
An embodiment of the present application further provides a data list management apparatus, where the data list management apparatus is configured to execute any embodiment of the foregoing data list management method. Specifically, please refer to fig. 4, wherein fig. 4 is a schematic block diagram of a data list management apparatus according to an embodiment of the present application. The data list management apparatus 300 may be configured in a management server.
As shown in fig. 4, the data list management apparatus 300 includes a data acquisition unit 301, a list generation unit 302, a list acquisition unit 303, a data determination unit 304, a result acquisition unit 305, and an update unit 306.
The data acquisition unit 301 is configured to acquire preset screening conditions, and screen out data to be insured from the database according to the screening conditions.
In an embodiment, as shown in fig. 5, fig. 5 is another schematic block diagram of a data list management apparatus provided in an embodiment of the present application. The data list management apparatus 300 further includes a condition judgment unit 307. The condition judging unit 307 is configured to judge whether the current time satisfies a preset condition. The data obtaining unit 301 is specifically configured to, if the current time meets the preset condition, obtain a preset screening condition, and screen out data to be insured from a database according to the screening condition.
A list generating unit 302, configured to generate a data list according to the data to be insured.
The list obtaining unit 303 is configured to obtain a historical data processing list, where the historical data processing list includes historical insurance data and a processing result corresponding to the historical insurance data.
And the data judgment unit 304 is configured to judge whether there is historical insurance data matching the data to be insured in the historical data processing list.
And a result obtaining unit 305, configured to obtain a processing result corresponding to the historical insurance data matching the data to be insured, if there is historical insurance data matching the data to be insured.
And the updating unit 306 is configured to update the data list according to the historical insurance data matched with the data to be insured if the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result.
In an embodiment, the updating unit 306 is specifically configured to merge the matched data to be insured and the historical data to update the data list, or write the historical data matched with the data to be insured into the data list to update the data list.
In one embodiment, as shown in fig. 5, the data list management apparatus 300 further includes an obtaining unit 308 and a storing unit 309. The obtaining unit 308 is configured to obtain a data processing list sent by a data processing system, where the data processing list is a list formed after the data processing system writes a processing result obtained by performing preset processing on the data to be insured into the data list. The storage unit 309 is configured to store the data processing list and set the data processing list as a history data processing list.
It should be clearly understood by those skilled in the art that, for the sake of brevity of the description, the specific working processes of the data list management apparatus 300 and each unit described above may refer to the corresponding processes in the foregoing data list management method embodiment, and are not described herein again.
In this embodiment, the data list management device 300 may automatically screen out the historical insurance data of the failure result, and update the current data list according to the historical insurance data, and the whole process does not require manual operation, and is short in time consumption, high in efficiency, and low in error rate.
Please provide an embodiment of the present application with a data list management apparatus, where the data list management apparatus is configured to execute any of the embodiments of the data list management method. Specifically, please refer to fig. 6, fig. 6 is a schematic block diagram of a data list management apparatus according to an embodiment of the present application. The data list management apparatus 400 may be configured in a management server.
As shown in fig. 6, the data list management apparatus 400 includes a data acquisition unit 401, a list generation unit 402, a list acquisition unit 403, a data judgment unit 404, a result acquisition unit 405, a type judgment unit 406, and an update unit 407.
The data obtaining unit 401 is configured to obtain a preset screening condition and a service type corresponding to the screening condition, and screen out data to be insured from a database according to the screening condition.
A list generating unit 402, configured to establish a correspondence between the data to be insured and the service types corresponding to the screening conditions, and generate a data list according to the correspondence.
A list obtaining unit 403, configured to obtain a historical data processing list, where the historical data processing list includes historical insurance data, a processing result corresponding to the historical insurance data, and a corresponding service type.
A data determining unit 404, configured to determine whether there is historical insurance data matching the data to be insured in the historical data processing list.
And the result obtaining unit 405 is configured to obtain a processing result corresponding to the historical insurance data matched with the data to be insured if the historical insurance data matched with the data to be insured exists.
And a type determining unit 406, configured to determine whether the service type corresponding to the matched data to be insured and the historical data to be insured is the same if the processing result corresponding to the historical data to be insured is a failure result.
And the updating unit 407 is configured to, if the service types corresponding to the matched data to be insured and the historical data to be insured are the same, merge the matched data to be insured and the historical data to update the data list. Or the data updating module is used for writing the historical insurance data matched with the data to be insured and the corresponding service type into the data list to update the data list if the matched data to be insured is different from the service type corresponding to the historical insurance data.
It should be clearly understood by those skilled in the art that, for the sake of brevity of the description, the specific working processes of the data list management apparatus 400 and each unit described above may refer to the corresponding processes in the foregoing data list management method embodiment, and are not described herein again.
In this embodiment, the data list management device 400 may automatically screen out the historical insurance data of the failure result, and update the current data list according to the historical insurance data, and the whole process does not require manual operation, and is short in time consumption, high in efficiency, and low in error rate.
The above-mentioned data list management means may be implemented in the form of a computer program that can be run on a computer device as shown in fig. 7. Referring to fig. 7, fig. 7 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 500 may be a server.
Referring to fig. 7, the computer device 500 includes a processor 502, memory, and a network interface 505 connected by a system bus 501, where the memory may include a non-volatile storage medium 503 and an internal memory 504.
The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer programs 5032 include program instructions that, when executed, cause the processor 502 to perform a data list management method.
The processor 502 is used to provide computing and control capabilities that support the operation of the overall computer device 500.
The internal memory 504 provides an environment for the execution of the computer program 5032 in the non-volatile storage medium 503, and when the computer program 5032 is executed by the processor 502, the processor 502 can be caused to execute a data list management method.
The network interface 505 is used for network communication such as sending assigned tasks and the like. Those skilled in the art will appreciate that the configuration shown in fig. 7 is a block diagram of only a portion of the configuration associated with the present application and does not constitute a limitation of the computer device 500 to which the present application may be applied, and that a particular computer device 500 may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
Wherein the processor 502 is configured to run the computer program 5032 stored in the memory to implement the following functions: acquiring preset screening conditions, and screening out data to be guaranteed from a database according to the screening conditions; generating a data list according to the data to be insured; acquiring a historical data processing list, wherein the historical data processing list comprises historical insurance data and processing results corresponding to the historical insurance data; judging whether historical insurance data matched with the data to be insured exist in the historical data processing list; if the historical insurance data matched with the data to be insured exists, acquiring a processing result corresponding to the historical insurance data matched with the data to be insured; and if the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result, updating the data list according to the historical insurance data matched with the data to be insured.
In an embodiment, when the processor 502 updates the data list according to the historical insurance data matched with the data to be insured, the following functions are specifically implemented: and merging the matched data to be insured and the historical insured data to update the data list, or writing the historical insured data matched with the data to be insured into the data list to update the data list.
In an embodiment, the processor 502 further implements the following functions when executing the step of obtaining the preset filtering condition: acquiring a service type corresponding to the screening condition; when the processor 502 executes the generation of the data list according to the data to be insured, the following functions are also realized: establishing a corresponding relation between the data to be insured and the service type corresponding to the screening condition, and generating a data list according to the corresponding relation; the historical data processing list also comprises a service type corresponding to the historical insurance data; the processor 502 also performs the following functions before performing merging of the matched data to be insured and the historical data to be insured to update the data list, or writing the historical data to be insured that match the data to be insured to the data list to update the data list: judging whether the service types corresponding to the matched data to be insured and the historical data to be insured are the same; if the service types corresponding to the matched data to be insured and the historical data to be insured are the same, executing a step of combining the matched data to be insured and the historical data to be insured to update the data list; if the service types corresponding to the matched data to be insured and the historical data to be insured are different, writing the historical data to be insured which is matched with the data to be insured into the data list to update the data list; when the processor 502 writes the historical insurance data matched with the data to be insured into the data list to update the data list, the following functions are specifically realized: and writing the historical insurance data matched with the data to be insured and the corresponding service type into the data list to update the data list.
In one embodiment, the processor 502, after performing the update of the data list according to the historical application data matching the data to be applied, further performs the following functions: acquiring a data processing list sent by a data processing system, wherein the data processing list is formed after the data processing system writes a processing result obtained by performing preset processing on the data to be insured into the data list; and storing the data processing list and setting the data processing list as a historical data processing list.
In an embodiment, the processor 502 further implements the following functions before executing the step of obtaining the preset filtering condition: judging whether the current time meets a preset condition or not; and if the current time meets the preset condition, executing the step of obtaining the preset screening condition and screening the data to be guaranteed from the database according to the screening condition.
In an embodiment, when the processor 502 performs merging of the matched data to be insured and the historical data to update the data list, the following functions are specifically implemented: and updating the times corresponding to the matched data to be insured in the data list so as to finish updating the data list.
In one embodiment, the processor 502, after performing the update of the data list according to the historical application data matching the data to be applied, further performs the following functions: and sending the updated data list to a data processing system so that the data processing system can preset the data to be guaranteed in the updated data list.
It should be understood that in the embodiment of the present Application, the Processor 502 may be a Central Processing Unit (CPU), and the Processor 502 may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will be understood by those skilled in the art that all or part of the flow in the data list management method according to the above embodiments may be implemented by instructing the relevant hardware through a computer program. The computer program may be stored in a storage medium, which is a computer-readable storage medium. As in the embodiments of the present application, the computer program may be stored in a storage medium of a computer device, and the computer program includes program instructions that are executed by at least one processor in the computer device to implement the flow steps of the embodiments including the respective data list management methods as described above. The storage medium may be various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.
The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the application can be combined, divided and deleted according to actual needs. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a storage medium. Based on such understanding, the technical solution of the present application may be substantially or partially implemented in the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a terminal, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application.
While the invention has been described with reference to specific embodiments, the scope of the invention is not limited thereto, and those skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the invention. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (8)
1. A method for managing a data list, comprising:
acquiring preset screening conditions, and screening out data to be guaranteed from a database according to the screening conditions;
generating a data list according to the data to be insured;
acquiring a historical data processing list, wherein the historical data processing list comprises historical insurance data and processing results corresponding to the historical insurance data;
judging whether historical insurance data matched with the data to be insured exist in the historical data processing list;
if the historical insurance data matched with the data to be insured exists, acquiring a processing result corresponding to the historical insurance data matched with the data to be insured;
if the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result, updating the data list according to the historical insurance data matched with the data to be insured;
the updating the data list according to the historical insurance data matched with the data to be insured comprises the following steps:
merging the matched data to be insured and the historical insured data to update the data list, or writing the historical insured data matched with the data to be insured into the data list to update the data list;
the method for acquiring the preset screening conditions further comprises the following steps: acquiring a service type corresponding to the screening condition;
the generating a data list according to the data to be insured comprises: establishing a corresponding relation between the data to be insured and the service type corresponding to the screening condition, and generating a data list according to the corresponding relation;
the historical data processing list also comprises a service type corresponding to the historical insurance data; before the merging the matched data to be insured and the historical data to be insured to update the data list, or writing the historical data to be insured which is matched with the data to be insured into the data list to update the data list, the method further comprises the following steps:
judging whether the service types corresponding to the matched data to be insured and the historical data to be insured are the same;
if the service types corresponding to the matched data to be insured and the historical data to be insured are the same, executing a step of combining the matched data to be insured and the historical data to be insured to update the data list;
if the service types corresponding to the matched data to be insured and the historical data to be insured are different, writing the historical data to be insured which is matched with the data to be insured into the data list to update the data list;
the writing the historical insurance data matched with the data to be insured into the data list to update the data list comprises: and writing the historical insurance data matched with the data to be insured and the corresponding service type into the data list to update the data list.
2. The data list management method according to claim 1, further comprising, after the updating the data list according to the historical insurance data matching the data to be insured:
acquiring a data processing list sent by a data processing system, wherein the data processing list is formed after the data processing system writes a processing result obtained by performing preset processing on the data to be insured into the data list; and
and storing the data processing list and setting the data processing list as a historical data processing list.
3. The data list management method according to claim 1, further comprising, before said obtaining a preset filtering condition:
judging whether the current time meets a preset condition or not;
and if the current time meets the preset condition, executing the step of obtaining the preset screening condition and screening the data to be guaranteed from the database according to the screening condition.
4. The data list management method according to claim 1, wherein the merging the matched data to be insured and the historical data to be insured to update the data list comprises: and updating the times corresponding to the matched data to be insured in the data list so as to finish updating the data list.
5. The data list management method according to claim 1, further comprising, after the updating the data list according to the historical insurance data matching the data to be insured: and sending the updated data list to a data processing system so that the data processing system can preset the data to be guaranteed in the updated data list.
6. A data list management apparatus, comprising:
the data acquisition unit is used for acquiring preset screening conditions and screening the data to be guaranteed from the database according to the screening conditions;
the list generating unit is used for generating a data list according to the data to be insured;
the system comprises a list acquisition unit, a list processing unit and a display unit, wherein the list acquisition unit is used for acquiring a historical data processing list, and the historical data processing list comprises historical insurance data and processing results corresponding to the historical insurance data;
the data judgment unit is used for judging whether historical insurance data matched with the data to be insured exist in the historical data processing list or not;
the result acquisition unit is used for acquiring a processing result corresponding to the historical insurance data matched with the data to be insured if the historical insurance data matched with the data to be insured exists;
the updating unit is used for updating the data list according to the historical insurance data matched with the data to be insured if the processing result corresponding to the historical insurance data matched with the data to be insured is a failure result;
the historical data processing list further comprises a service type corresponding to the historical insurance data;
the device further comprises:
the type judging unit is used for judging whether the service types corresponding to the matched data to be insured and the historical data are the same or not, if the service types corresponding to the matched data to be insured and the historical data are the same, executing a step of merging the matched data to be insured and the historical data to update the data list, and if the service types corresponding to the matched data to be insured and the historical data are not the same, executing a step of writing the historical data matched with the data to be insured into the data list to update the data list;
the updating unit is specifically configured to merge the matched data to be insured and historical data to update the data list, or write the historical data matched with the data to be insured into the data list to update the data list;
the data acquisition unit is specifically used for acquiring preset screening conditions and service types corresponding to the screening conditions;
the list generating unit is specifically configured to establish a correspondence between the data to be insured and the service types corresponding to the screening conditions, and generate a data list according to the correspondence;
and the updating unit is more specifically used for writing the historical insurance data matched with the data to be insured and the corresponding service type into the data list so as to update the data list.
7. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the data list management method according to any one of claims 1 to 5 when executing the computer program.
8. A storage medium characterized in that the storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to perform the data list management method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810462785.2A CN108664636B (en) | 2018-05-15 | 2018-05-15 | Data list management method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810462785.2A CN108664636B (en) | 2018-05-15 | 2018-05-15 | Data list management method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108664636A CN108664636A (en) | 2018-10-16 |
| CN108664636B true CN108664636B (en) | 2022-04-01 |
Family
ID=63779497
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810462785.2A Active CN108664636B (en) | 2018-05-15 | 2018-05-15 | Data list management method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108664636B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111125083B (en) * | 2019-12-31 | 2020-11-10 | 北京金堤科技有限公司 | Historical record screening method and device |
| CN112330471B (en) * | 2020-11-17 | 2023-06-02 | 中国平安财产保险股份有限公司 | Service data processing method, device, computer equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104063782A (en) * | 2014-06-20 | 2014-09-24 | 惠州Tcl移动通信有限公司 | Payment method for water, electricity, gas and networks of family and system thereof |
| CN106157146A (en) * | 2016-08-03 | 2016-11-23 | 合肥奇也信息科技有限公司 | A kind of endowment insurance information comprehensive management system |
| CN107330983A (en) * | 2017-06-13 | 2017-11-07 | 智慧互通科技有限公司 | A kind of Roadside Parking data processing method, apparatus and system |
| CN107665234A (en) * | 2017-07-25 | 2018-02-06 | 平安科技（深圳）有限公司 | Method for processing business, device, server and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160104246A1 (en) * | 2014-10-09 | 2016-04-14 | Hartford Fire Insurance Company | System for dynamically calculating claim allocations |
-
2018
- 2018-05-15 CN CN201810462785.2A patent/CN108664636B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104063782A (en) * | 2014-06-20 | 2014-09-24 | 惠州Tcl移动通信有限公司 | Payment method for water, electricity, gas and networks of family and system thereof |
| CN106157146A (en) * | 2016-08-03 | 2016-11-23 | 合肥奇也信息科技有限公司 | A kind of endowment insurance information comprehensive management system |
| CN107330983A (en) * | 2017-06-13 | 2017-11-07 | 智慧互通科技有限公司 | A kind of Roadside Parking data processing method, apparatus and system |
| CN107665234A (en) * | 2017-07-25 | 2018-02-06 | 平安科技（深圳）有限公司 | Method for processing business, device, server and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 基于银行中间业务平台的社会保险个人缴费系统;刘欣亮;《河南科技大学学报》;20070430;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108664636A (en) | 2018-10-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112184077B (en) | Configurable flow approval method, device, computer equipment and storage medium | |
| CN111192144A (en) | Financial data prediction method, device, equipment and storage medium | |
| CN108664636B (en) | Data list management method and device, computer equipment and storage medium | |
| CN109118047B (en) | Budget data processing method and device | |
| CN112950191A (en) | Service data processing method and device based on fee refunding service and computer equipment | |
| CN116797345A (en) | Task processing method, device, computer equipment and storage medium | |
| CN108647936B (en) | Commission issuing method, apparatus, computer device and storage medium | |
| CN114969077A (en) | Service data processing method and device | |
| CN105653341A (en) | Method, device and system for upgrading network invoice client | |
| CN115526699A (en) | Payment fund reconciliation method, device, equipment and computer-readable storage medium | |
| CN115018463A (en) | Order processing method and device, computer equipment and storage medium | |
| CN109377174A (en) | A kind of data statistical analysis method and device | |
| CN111429125B (en) | Account management method and device, storage medium and electronic equipment | |
| CN107239263B (en) | Short message reminding control method and system | |
| CN113076297A (en) | Data processing method, device and storage medium | |
| CN112650911A (en) | Service message issuing method, device, computer equipment and storage medium | |
| CN109754189A (en) | A kind of distribution method of fabrication task, a kind of acquisition methods, computer installation and the computer readable storage medium of fabrication task | |
| CN114222004B (en) | Service data distribution execution method, device, computer equipment and storage medium | |
| CN109584087B (en) | Information processing method, device and storage medium | |
| CN109039691B (en) | Server, method for predicting system call amount and storage medium | |
| CN114416805B (en) | Data checking method and device, computer equipment and storage medium | |
| CN115469907A (en) | Method and device for upgrading information system, computer equipment and storage medium | |
| CN117240711B (en) | Automatic updating method, device and equipment for cluster management tool configuration file | |
| CN117710068B (en) | Temporary supplier verification method, device and equipment based on artificial intelligence | |
| CN113111631B (en) | Data processing method, apparatus, device, storage medium, and program product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |