A Management Method, Device and Medium for Grassroots Data

Abstract

The present application discloses a method, device and medium for managing grass-roots data. The method includes: receiving a ledger management task issued by a superior department, and creating a corresponding ledger template according to the ledger management task; determining at least one management object for executing the ledger management task, and distributing the ledger template to at least one management object; obtaining specified fields with data association logic in the ledger template, and matching the specified fields with preset data tables in the grass-roots database to determine target data tables associated with the ledger template; through at least one management object, filling the corresponding ledger template according to the target data tables to obtain a filled ledger; summarizing the ledgers generated by at least one management object to the superior department for managing the ledgers.

Description

Technical Field

[0001] This application relates to the technical field of data processing, and particularly to a management method, device, and medium for grass-roots data. Background Art

[0002] Grass-roots data refers to the relevant management data collected during the grass-roots governance process. In recent years, certain achievements have been made in the work of reducing the burden on grass-roots levels. However, with the continuous expansion of the scale of grass-roots governance, the amount of data to be managed has gradually increased, resulting in a problem of decreased work efficiency. Thus, how to improve the management efficiency of grass-roots data has become an urgent problem to be solved currently. Summary of the Invention

[0003] To solve the above problems, this application proposes a management method for grass-roots data, which is applied to a preset ledger designer and includes:

[0004] Receiving a ledger management task issued by a superior department, and creating a corresponding ledger template according to the ledger management task;

[0005] Determining at least one management object for executing the ledger management task, and distributing the ledger template to the at least one management object;

[0006] Obtaining a specified field with data association logic in the ledger template, and matching the specified field with a preset data table in the grass-roots database to determine a target data table associated with the ledger template;

[0007] Through the at least one management object, filling the corresponding ledger template according to the target data table to obtain a filled ledger;

[0008] Summarizing the ledgers generated by the at least one management object to the superior department to implement the management of the ledgers.

[0009] In an implementation manner of this application, distributing the ledger template to the at least one management object specifically includes:

[0010] Generating a ledger template copy of the ledger template, and distributing the ledger template copy to the at least one management object.

[0011] In an implementation manner of this application, through the at least one management object, filling the corresponding ledger template according to the target data table to obtain a filled ledger specifically includes:

[0012] Determining the filling type corresponding to the ledger template, where the filling type includes row-by-row filling type and batch filling type;

[0013] For the ledger template with the filling type of line-by-line filling, determine the first field in the target data table that has a data association logic with the specified field;

[0014] Use the field value corresponding to the first field as the candidate field value corresponding to the specified field, so as to fill the ledger template by selecting the candidate field value;

[0015] For the ledger template with the filling type of batch filling, generate a matching rule corresponding to the specified field, and determine the second field in the target data table that has a data association logic with the specified field according to the matching rule;

[0016] Use the field value corresponding to the second field as the field value corresponding to the specified field to achieve batch filling of the ledger template.

[0017] In an implementation manner of the present application, after filling the corresponding ledger template according to the target data table, the method further includes:

[0018] Determine the field types corresponding to the multiple fields included in the ledger template, and obtain the format verification rules corresponding to the multiple field types;

[0019] Verify the format of the fields that meet their corresponding field types through the format verification rules, so as to determine whether the fields conform to the preset format specified by the format verification rules;

[0020] If not, assign a specified mark to the field to give a format error prompt.

[0021] In an implementation manner of the present application, after summarizing the ledgers generated by the at least one management object to the superior department, the method further includes:

[0022] When the at least one management object needs to change the ledger to be changed that has been submitted to the superior department, submit a ledger withdrawal request for withdrawing the ledger to be changed;

[0023] If the ledger withdrawal request is approved, return the ledger to be changed to the at least one management object, and delete the ledger to be changed from the superior database corresponding to the superior department.

[0024] In an implementation manner of the present application, after creating a corresponding ledger template according to the ledger management task, the method further includes:

[0025] Based on the grass-roots database, synchronously create a data table corresponding to the ledger template;

[0026] After filling the corresponding ledger template according to the target data table and obtaining the filled ledger, the method further includes:

[0027] Synchronize the filled ledger to the data table, so as to fill the ledger template associated with the ledger through the data table.

[0028] In an implementation manner of the present application, creating a corresponding ledger template according to the ledger management task specifically includes:

[0029] Determine the information items required to be configured for the ledger template to be created according to the ledger management task, and generate each field of the ledger template according to the information items;

[0030] Configure the attribute information of each field to obtain the configured ledger template; the attribute information includes at least one or more of the following: filling requirements, field format, format verification rules, metadata association logic.

[0031] In an implementation manner of the present application, the filling requirements include periodic submission, single statistics, and daily maintenance.

[0032] An embodiment of the present application provides a management device for grass-roots data, which is characterized in that it is applied to a preset ledger designer, and the device includes:

[0033] At least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can:

[0034] Receive the ledger management task issued by the superior department, and create a corresponding ledger template according to the ledger management task;

[0035] Determine at least one management object for executing the ledger management task, and distribute the ledger template to the at least one management object;

[0036] Obtain the specified fields with data association logic in the ledger template, and match the specified fields with the preset data tables in the grass-roots database to determine the target data table associated with the ledger template;

[0037] Through the at least one management object, fill the corresponding ledger template according to the target data table to obtain the filled ledger;

[0038] Summarize the ledgers generated by the at least one management object to the superior department to realize the management of the ledgers.

[0039] An embodiment of the present application provides a non-volatile computer storage medium storing computer-executable instructions, characterized in that it is applied to a preset ledger designer, and the computer-executable instructions are set as:

[0040] Receive the ledger management tasks issued by the superior department, and create corresponding ledger templates according to the ledger management tasks;

[0041] Determine at least one management object for executing the ledger management task, and distribute the ledger template to the at least one management object;

[0042] Obtain the specified fields with data association logic in the ledger template, and match the specified fields with the preset data tables in the grass-roots database to determine the target data tables associated with the ledger template;

[0043] Through the at least one management object, fill the corresponding ledger template according to the target data table to obtain the filled ledger;

[0044] Summarize the ledgers generated by the at least one management object to the superior department to realize the management of the ledgers.

[0045] The management method of grass-roots data proposed by this application can bring the following beneficial effects:

[0046] Associating the ledger with the data table realizes the collaborative management between the ledger and the database table. In this way, through the collaborative linkage method, the ledger template can be assisted in filling through the data table, improving the data reuse rate and helping to improve the management efficiency of grass-roots data. Description of the Drawings

[0047] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation of the present application. In the drawings:

[0048] Figure 1 It is a flowchart of a management method of grass-roots data provided by an embodiment of the present application;

[0049] Figure 2 It is a flowchart of another management method of grass-roots data provided by an embodiment of the present application;

[0050] Figure 3 It is a structural diagram of a management device of grass-roots data provided by an embodiment of the present application. Detailed Embodiments

[0051] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of them. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts belong to the scope of protection of this application.

[0052] The following will detail the technical solutions provided by each embodiment of this application in conjunction with the drawings.

[0053] As Figure 1 shown, a method for managing grass-roots data provided by an embodiment of this application is applied to a preset ledger designer and includes:

[0054] S101: Receive the ledger management task issued by the superior department, and create a corresponding ledger template according to the ledger management task.

[0055] A ledger is an auxiliary account book set up by an enterprise to strengthen management in a certain aspect and understand information in that aspect in more detail. In this application, the ledger is used as the carrier of grass-roots data for relevant management. In the embodiment of this application, the ledger designer is a low-code development platform that can receive the ledger management task issued by the superior department and then create a corresponding ledger template according to the ledger management task.

[0056] Specifically, according to the ledger management task, determine the information items required to be configured for the ledger template to be created, and generate each field of the ledger template according to the information items. On the basis of generating the fields, the attribute information of each field can be configured to obtain the configured ledger template. The attribute information includes at least one or more of the following: filling requirements, field format, format verification rules, and metadata association logic.

[0057] Among them, the filling requirements include periodic submission, single - time statistics, and daily maintenance. When creating a ledger template, any one of the above - mentioned filling requirements can be selected. If the submission type of periodic submission is selected, the submission period and periodic submission time also need to be set additionally. The submission period can be divided by month, week, day, hour, etc. By setting multiple filling types, it can adapt to the actual business needs of grass - roots work and is conducive to improving the governance efficiency of grass - roots data. The field format defines the field types of each field in the ledger template. For example, text, date, number, etc. The format verification rules and field format adaptability settings are used to verify whether the field values entered by users conform to the preset field formats. For example, for text fields, the length requirement and whether null values are allowed need to be set; for number fields, the specific data format, integer, decimal, and the number of decimal places to be retained need to be set; for date fields, the corresponding style (such as 2022 - 02 - 08, 2022 / 02 / 08, February 8, 2022) needs to be set; for ID card fields, whether format verification is required and whether to display encrypted need to be set; for mobile phone number fields, whether format verification is required and whether to display encrypted need to be set; for amount fields, the style (such as ￥***, *** yuan, ****) needs to be set; for drop - down selection fields, the options for auxiliary filling of fields need to be set, and users can select content from the options to fill each field of the ledger template. The metadata association logic can associate fields with different literal descriptions but the same meaning between different ledgers, thus establishing data association relationships and further realizing the efficient reuse of grass - roots data.

[0058] S102: Determine at least one management object for executing the ledger management task and distribute the ledger template to at least one management object.

[0059] After creating the ledger template, the ledger designer can use the real - time computing engine and message queue to construct a data extraction service, so as to synchronously create a data table corresponding to the ledger template in the grass - roots database. In this way, when the user fills the ledger template, the filled ledger can be directly and real - time synchronized to the data table, realizing real - time data storage. And the data table can be filled with the relevant ledger template, without the user filling all the contents of the ledger template, improving the generation efficiency of the ledger.

[0060] After each ledger template is created, it is necessary to determine the online distribution management object corresponding to the ledger template. After confirming at least one management object for distribution, a copy of the ledger template is generated and the copy of the ledger template is distributed to at least one management object. In this way, each management object holds the same copy of the ledger template, and when filling in the content, they are independent of each other and do not interfere with each other.

[0061] S103: Obtain the specified fields in the ledger template that have data association logic, and match the specified fields with the preset data tables in the grass-roots database to determine the target data table associated with the ledger template.

[0062] After receiving the ledger template, the management object can fill in the ledger template according to the actual business content. Since the corresponding metadata association logic has been set for the fields during the creation of the ledger template, when filling in the data, the specified fields with data association logic in the ledger template can be obtained, and the specified fields are matched with the preset data tables in the grass-roots database to determine the target data table associated with the ledger template. Then, the stock data and shared data in the target data table are used to recommend and automatically fill in the content of the set specified fields, saving a lot of repetitive labor in searching and verifying information.

[0063] S104: Through at least one management object, fill in the corresponding ledger template according to the target data table to obtain the filled ledger.

[0064] After determining the target data table associated with the current ledger template to be filled, the ledger template can be filled in assistively according to the existing data in the target data table.

[0065] In one embodiment, the filling type corresponding to the ledger template is determined, and the filling types include line-by-line filling type and batch filling type. Among them, line-by-line filling is applicable to the situation where the number of ledger records is uncertain and needs to be filled line by line according to the actual business. In this case, the first field in the target data table that has a data association logic with the specified field needs to be determined, and then the field value corresponding to the first field is used as the candidate field value corresponding to the specified field. When the management object performs data filling, it can select a suitable field value from the candidate field values to fill the ledger template, saving the data filling volume and improving the ledger processing efficiency. Batch filling is applicable to the situation where most columns of the ledger template have been filled, and the data in a certain column has existed in a certain ledger in the cloud. At this time, the batch filling function can be used to obtain the existing data to fill the ledger template to further improve the data filling efficiency. In this case, a matching rule corresponding to the specified field needs to be generated. According to the matching rule, the second field in the target data table that has a data association logic with the specified field is determined, and then the field value corresponding to the second field is used as the field value corresponding to the specified field to achieve batch filling of the ledger template. It should be noted that the second field should correspond to one or more field values. The matching rule is used to represent the filling condition of the field. When the matching rule is set to B can only be done when A, for example, when the ID card field in the cloud ledger is the same as the ID card number in the ledger template to be filled currently, the mobile phone number in the cloud ledger can be filled into the mobile phone number field in the current ledger template. By setting different filling types, the threshold for data reuse is reduced, and the quality and efficiency of grass-roots management objects filling in ledgers are improved.

[0066] During the process of filling the ledger, it is necessary to perform real-time verification on the filled data, determine the field types corresponding to the multiple fields included in the ledger template, and obtain the format verification rules corresponding to the multiple field types. Through the format verification rules, the fields that meet their corresponding field types are format-verified to determine whether the fields conform to the preset format specified by the format verification rules. If not, a specified mark is assigned to the field to give a format error prompt. It should be noted that the specified mark can be a display mark. For example, a mark with an obvious color is added to the input box where the field is located, or the input box where it is located blinks. The specified mark can also exist in the form of prompt text. When there is a field value that does not conform to the preset format, a corresponding prompt window pops up for text prompt.

[0067] S105: Summarize the ledgers generated by at least one management object to the superior department to achieve the management of the ledgers.

[0068] After generating the filled ledger through the above process, if the issued ledger management task clearly requires the ledger to be summarized at multiple levels, then the ledgers corresponding to each management object need to be summarized level by level to the superior department. This process is an automatic summary and does not require the management object to summarize manually, avoiding data errors during summarization.

[0069] The summarized ledger will be stored in the superior database corresponding to the superior department. If the business corresponding to at least one management object needs to change the ledger to be changed that has been submitted to the superior department, at this time, a ledger withdrawal request for withdrawing the ledger to be changed needs to be submitted. When the ledger withdrawal request passes the approval, the ledger to be changed is returned to at least one management object that submitted the ledger withdrawal request, and the ledger to be changed is deleted from the superior database corresponding to the superior department, thus realizing the requirement of withdrawing and modifying at the business level. After the ledger modification is completed, it can be submitted to the superior department again.

[0070] Figure 2 It is a flowchart of another method for managing grass-roots data provided by an embodiment of the present application. As Figure 2 shown, the superior department issues a ledger management task, designs a ledger template according to the ledger management task, and obtains the designed ledger template. The ledger data to be obtained is collected by filling in the ledger or collecting devices, and the ledger template is filled accordingly, and then the filled data is synchronized to the grass-roots database. The ledger data in the grass-roots database can be summarized into the superior database corresponding to the superior department in the form of a data table. After the summarization is completed, the ledger management task is completed. Among them, the data in the superior database can be shared with the grass-roots database corresponding to the grass-roots department to assist the grass-roots department in collecting and processing the corresponding data.

[0071] The embodiment of the present application solves problems in many aspects such as low informatization level of grass-roots data collaboration services, no retention of business data, inability to review and reuse, etc., and provides a new way and approach for sharing superior data levels to the grass-roots, which helps to exert the effectiveness of data sharing. Through grass-roots data management, the purpose of data businessization can be achieved, realizing one-time collection and multi-party utilization, and increasing efficiency and reducing burden for grass-roots governance work.

[0072] The above is the method embodiment proposed by the present application. Based on the same idea, one or more embodiments of this specification also provide the device and medium corresponding to the above method.

[0073] Figure 3 It is a structural diagram of a device for managing grass-roots data provided by an embodiment of the present application, which is applied to a preset ledger designer. The device includes:

[0074] At least one processor; and,

[0075] A memory communicatively connected to at least one processor; wherein,

[0076] The memory stores instructions executable by at least one processor, and the instructions are executed by at least one processor to enable the at least one processor to:

[0077] Receive the ledger management task issued by the superior department, and create a corresponding ledger template according to the ledger management task;

[0078] Determine at least one management object for executing the ledger management task, and distribute the ledger template to at least one management object;

[0079] Obtain the specified fields in the ledger template with data association logic, and match the specified fields with the preset data tables in the grass-roots database to determine the target data tables associated with the ledger template;

[0080] Through at least one management object, fill the corresponding ledger template according to the target data table to obtain the filled ledger;

[0081] Summarize the ledgers generated by at least one management object to the superior department to realize the management of the ledgers.

[0082] An embodiment of the present application provides a non-volatile computer storage medium, storing computer-executable instructions, which are applied to a preset ledger designer, and the computer-executable instructions are set as:

[0083] Receive the ledger management task issued by the superior department, and create a corresponding ledger template according to the ledger management task;

[0084] Determine at least one management object for executing the ledger management task, and distribute the ledger template to at least one management object;

[0085] Obtain the specified fields in the ledger template with data association logic, and match the specified fields with the preset data tables in the grass-roots database to determine the target data tables associated with the ledger template;

[0086] Through at least one management object, fill the corresponding ledger template according to the target data table to obtain the filled ledger;

[0087] Summarize the ledgers generated by at least one management object to the superior department to realize the management of the ledgers.

[0088] The embodiments in the present application are all described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other, and the key points of each embodiment are the differences from other embodiments. In particular, for the embodiments of the device and the medium, since they are basically similar to the method embodiments, the description is relatively simple, and for the relevant parts, reference can be made to the partial description of the method embodiments.

[0089] The device and the medium provided in the embodiments of the present application correspond one by one to the method. Therefore, the device and the medium also have beneficial technical effects similar to those of the corresponding method. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the device and the medium will not be elaborated here.

[0090] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0091] The present application is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram can be implemented by computer program instructions, and the combination of the flows and / or blocks in the flowchart and / or block diagram can also be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0092] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device implements the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.

[0093] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 steps of the functions specified in one block or multiple blocks.

[0094] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0095] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM) and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

[0096] Computer-readable media includes permanent and non-permanent, removable and non-removable media and can be implemented by any method or technology for information storage. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory media such as modulated data signals and carrier waves.

[0097] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of another identical element in the process, method, commodity or device including the said element.

[0098] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims

1. A method for managing basic data, characterized in that, Applied to a preset ledger designer, the method includes: Receiving a ledger management task issued by a superior department, and creating a corresponding ledger template according to the ledger management task; Determining at least one management object for executing the ledger management task, and distributing the ledger template to the at least one management object; Obtaining a specified field in the ledger template that has a data association logic, and matching the specified field with a preset data table in the grass-roots database to determine a target data table associated with the ledger template; Filling the corresponding ledger template according to the target data table through the at least one management object to obtain a filled ledger; Summarizing the ledgers generated by the at least one management object to the superior department to implement the management of the ledger; After creating a corresponding ledger template according to the ledger management task, the method further includes: Based on the grass-roots database, synchronously creating a data table corresponding to the ledger template; After filling the corresponding ledger template according to the target data table to obtain a filled ledger, the method further includes: Synchronizing the filled ledger to the data table, so as to fill the ledger template associated with the ledger through the data table.

2. The management method of grass-roots data according to claim 1, characterized in that, Distributing the ledger template to the at least one management object specifically includes: Generating a ledger template copy of the ledger template, and distributing the ledger template copy to the at least one management object.

3. The management method of grass-roots data according to claim 1, characterized in that Filling the corresponding ledger template according to the target data table through the at least one management object to obtain a filled ledger specifically includes: Determining the filling type corresponding to the ledger template, where the filling type includes row-by-row filling type and batch filling type; For the ledger template with the filling type of row-by-row filling type, determining a first field in the target data table that has a data association logic with the specified field; Taking the field value corresponding to the first field as the candidate field value corresponding to the specified field, so as to fill the ledger template by selecting the candidate field value; For the ledger template with the filling type of batch filling type, generating a matching rule corresponding to the specified field, and determining a second field in the target data table that has a data association logic with the specified field according to the matching rule; Taking the field value corresponding to the second field as the field value corresponding to the specified field to implement batch filling of the ledger template.

4. A method for managing grass-roots data according to claim 1, characterized in that, After filling the corresponding ledger template according to the target data table, the method further includes: Determining the field types corresponding to multiple fields included in the ledger template, and obtaining the format verification rules corresponding to the multiple field types; Verifying the format of the fields that meet their corresponding field types through the format verification rules to determine whether the fields conform to the preset format specified by the format verification rules; If not, assigning a specified mark to the field to give a format error prompt.

5. A method for managing grass-roots data according to claim 1, characterized in that, After summarizing the ledgers generated by the at least one management object to the superior department, the method further includes: When at least one management object needs to modify the ledger to be changed that has been submitted to the superior department, a ledger withdrawal request for withdrawing the ledger to be changed is submitted. In the case where the ledger withdrawal request is approved, the ledger to be changed is returned to the at least one management object, and the ledger to be changed is deleted from the superior database corresponding to the superior department.

6. The management method of grass-roots data according to claim 1, characterized in that, According to the ledger management task, a corresponding ledger template is created, specifically including: According to the ledger management task, determine the information items required to be configured for the ledger template to be created, and generate each field of the ledger template according to the information items. Configure the attribute information of each field to obtain the configured ledger template; the attribute information includes at least one or more of the following: filling requirements, field format, format verification rules, metadata association logic.

7. A management method for grass-roots data according to claim 6, characterized in that, The filling requirements include periodic submission, single statistics, and daily maintenance.

8. A management device for grass-roots data, characterized in that, Applied to a preset ledger designer, the device includes: At least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can: Receive the ledger management task issued by the superior department, and create a corresponding ledger template according to the ledger management task. Determine at least one management object for executing the ledger management task, and distribute the ledger template to the at least one management object. Obtain the specified fields in the ledger template with data association logic, and match the specified fields with the preset data tables in the grass-roots database to determine the target data tables associated with the ledger template. Through the at least one management object, fill the corresponding ledger template according to the target data table to obtain the filled ledger. Summarize the ledgers generated by the at least one management object to the superior department to realize the management of the ledgers. After creating a corresponding ledger template according to the ledger management task, it further includes: Based on the grass-roots database, synchronously create the data tables corresponding to the ledger template. After filling the corresponding ledger template according to the target data table to obtain the filled ledger, it further includes: Synchronize the filled ledger to the data table, so as to fill the ledger template associated with the ledger through the data table.

9. A non-volatile computer storage medium stores computer-executable instructions, characterized in that, Applied to a preset ledger designer, the computer-executable instructions are set to: Receive the ledger management task issued by the superior department, and create a corresponding ledger template according to the ledger management task. Determine at least one management object for executing the ledger management task, and distribute the ledger template to the at least one management object. Obtain the specified fields in the ledger template with data association logic, and match the specified fields with the preset data tables in the grass-roots database to determine the target data tables associated with the ledger template. Through the at least one management object, fill the corresponding ledger template according to the target data table to obtain the filled ledger. Summarize the ledger generated corresponding to the at least one management object to the superior department to achieve the management of the ledger; After creating the corresponding ledger template according to the ledger management task, it further includes: Based on the grass-roots database, synchronously create a data table corresponding to the ledger template; After filling the corresponding ledger template according to the target data table to obtain the filled ledger, it further includes: Synchronize the filled ledger to the data table so as to fill the ledger template associated with the ledger through the data table.

Images