A method and device for reporting a report

Abstract

The application discloses a report form reporting implementation method and device, and belongs to the technical field of computer and data processing. The method comprises the following steps: obtaining a to-be-collected report form template, and judging a data type corresponding to report form data in the to-be-collected report form template; when the data type is external data, determining a task code of an external system to which the report form data belongs, and issuing the task code and a filling task by calling an interface of the external system; receiving the report form data filled based on the filling task in the case that the external system successfully identifies the task code, and filling the report form data into the to-be-collected report form template; when the data type is internal data, issuing the filling task to a subordinate organization of an internal system after introducing a sub-report form into the filling task; collecting a sub-report form completed by the subordinate organization based on the filling task, and filling the sub-report form into the to-be-collected report form template after the sub-report form is summarized.

Description

Technical Field

[0001] This application relates to the field of computer and data processing technology, and in particular to a method and device for implementing report submission. Background Technology

[0002] As medium and large enterprises continue to develop, more and more companies are setting up regional subsidiaries to expand their business. At the same time, as the number of employees continues to grow, the division of corporate headquarters levels is becoming more obvious.

[0003] In this situation, when the corporate headquarters needs to compile reports and other data, the headquarters employees are required to submit the reports layer by layer, which takes a lot of time. At the same time, regional subsidiaries also need to submit reports across systems, resulting in multiple reports being submitted by the company. Organizing and summarizing these reports also wastes a lot of time and manpower, thus leading to low efficiency in report collection. Summary of the Invention

[0004] This application provides a method and device for reporting reports, which addresses the following technical problem: existing report collection schemes are inefficient.

[0005] The embodiments of this application adopt the following technical solutions:

[0006] On one hand, this application provides a method for implementing a report submission, the method comprising: obtaining a report template to be collected, and determining the data type corresponding to the report data in the report template to be collected, the data type including internal data and external data; when the data type is external data, determining the task code of the external system to which the report data belongs, and sending the task code and the reporting task by calling the interface of the external system; receiving the report data filled in by the external system based on the execution of the reporting task when the task code is successfully identified, and filling the report data into the report template to be collected; when the data type is internal data, introducing a sub-report in the reporting task and sending the reporting task to the lower-level organization of the internal system; collecting the sub-reports completed by the lower-level organization based on the execution of the reporting task, and summarizing the sub-reports and filling them into the report template to be collected.

[0007] In one or more examples of this application specification, when the data type is external data, the method further includes: adding the external system to the internal system and generating a task code corresponding to the external system.

[0008] In one or more examples of this application specification, when the data type is external data, the method further includes: after the external system successfully identifies the task code, determining whether the filling task is a periodic filling task; if so, adding a periodic task in the external system, and periodically reporting the report data to the internal system based on the periodic task.

[0009] In one or more examples of this application specification, when the data type is internal data, the method further includes: the lower-level organization determining that the data entry task needs to be redistributed a second time; generating a sub-data entry task based on the report data in the sub-report, and redistributing the sub-data entry task a second time; receiving report data reported by a lower-level organization based on the execution of the sub-data entry task; summarizing the report data reported by the lower-level organization into the sub-report of the data entry task, and reporting the sub-report.

[0010] In one or more examples of this application specification, before filling the summarized sub-reports into the report template to be collected, the method further includes: determining the summary mode corresponding to the sub-report, the summary mode including summation summary, detailed summary, and detailed summation summary; wherein, the summation summary is to display the report data corresponding to the sub-report as a summation result in the report template to be collected; the detailed summary is to directly display the report data corresponding to the sub-report in the report template to be collected; and the detailed summation summary is to sum the report data corresponding to the sub-report in the report template to be collected by column and then display the summation result in a flat layout.

[0011] In one or more examples of this application specification, before collecting the sub-reports completed by the subordinate organization based on the execution of the reporting task, the method further includes: adding a data block to the sub-report page and determining the data retrieval model corresponding to the data block; mapping the data retrieval model to the database table of the internal system; obtaining the data corresponding to the data segment in the data retrieval model from the database of the internal system; and obtaining the data returned by the data block through the data retrieval formula in the sub-report.

[0012] In one or more examples of this application specification, before collecting the sub-reports completed by the subordinate organization based on the execution of the filling task, the method further includes: determining the report data that needs to be manually added in the sub-reports; adding a specified identifier to the cell corresponding to the report data that needs to be manually added; when the subordinate organization executes the filling task, recognizing the specified identifier and generating a click event; and in response to clicking the click event, popping up an input box in the sub-report to support manual data input.

[0013] In one or more examples of this application specification, before filling the report data into the report template to be collected, the method further includes: determining cells with added indicator labels in the report template to be collected; when adding data to cells with added indicator labels, verifying the data to be added according to the verification formula corresponding to the indicator label, and obtaining the verification result; when the level of the verification result is warning, filling the cells with added indicator labels with yellow; and when the level of the verification result is error, displaying an error message and canceling the data addition.

[0014] In one or more examples of this application specification, after obtaining the report template to be collected, the method further includes: uploading the report template to be collected to the system and storing it to a file server; parsing the report template to be collected by introducing the Python third-party library openpyxl into the system; and converting the parsed template content into an HTML file and displaying it on the system page.

[0015] On the other hand, embodiments of this application also provide an implementation device for reporting reports, the device comprising: 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 to enable the at least one processor to execute a reporting report implementation method as described above.

[0016] The reporting method and device provided in this application have the following advantages: For internal data, multi-level reporting is possible. Multi-level reporting means that users can send reports to lower-level organizations within the system, and these lower-level organizations can then send the reports back to their own higher-level organizations. There are no restrictions on the sending level; lower-level organizations can send reports to their own lower-level organizations, thus achieving multi-level data reporting onto a single report. This saves time spent on reporting reports level by level and improves the efficiency of report collection. Simultaneously, for external systems and tenants, cross-tenant reporting is possible. Cross-tenancy means that users can send and receive data between different tenants or different systems. This allows different tenants or systems to collect all the data that needs to be reported onto a single report, saving headquarters time in summarizing reports and further improving the efficiency of report collection. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0018] Figure 1 A flowchart illustrating a method for implementing a reporting report, as provided in this application embodiment;

[0019] Figure 2 A flowchart of a report submission process provided in an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of the structure of a device for implementing a reporting report, as provided in an embodiment of this application. Detailed Implementation

[0021] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this application.

[0022] The methods in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0023] Figure 1 A flowchart illustrating a method for implementing a reporting report, as provided in this application embodiment, is shown below. Figure 1 As shown, the report submission method in this application embodiment includes at least the following execution steps:

[0024] Step 101: Obtain the report template to be collected and determine the data type of the report data in the report template.

[0025] The report templates to be collected can be reports to be filled in the system. These reports contain multiple data items that need to be reported by lower-level organizations or external systems. This data is categorized as internal or external data based on whether it is provided by a lower-level organization or an external system; that is, the data required in the reports is categorized by its source. For ease of description, in this application, the system that needs to report data is referred to as an external system, and the system that issues the report reporting task is referred to as an internal system.

[0026] In one example of this application, after obtaining the template of the report to be collected, the template is uploaded to the system and stored on the file server. The system uses the Python third-party library openpyxl to parse the template, and then converts the parsed template content into an HTML file to be displayed on the system page, thereby realizing the personalized display of the report template.

[0027] Step 102: When the report data is external data, determine the task code of the external system to which the report data belongs, and send the task code and the data entry task by calling the interface of the external system.

[0028] If the data to be filled in the report needs to be provided by an external system, the internal system will call the corresponding task of the external system and send the task code and the data entry task to the external system. The data entry task here is executed by the external system, which fills in the report data when the task code is successfully recognized.

[0029] In one example of this application, the task code is generated when an external system is added to the internal system. It is used to distinguish the external system within the internal system and to enable the external system to identify the internal system.

[0030] In another example of this application, the internal system issues a data entry task to the external system. When the data that the external system needs to enter is periodically generated data or the external system needs to periodically report data to the internal system, the entry task can be set as a periodic entry task. In this case, after the external system successfully recognizes the task code, it adds a periodic task in the system. In this way, the external system will periodically execute the data reporting task to periodically report the report data to the internal system.

[0031] Step 103: Receive the report data filled in by the external system performing the data entry task, and summarize the report data into the report template to be collected.

[0032] After receiving the report data from the external system, the internal system will summarize the report data into the aforementioned report template to be collected.

[0033] In one example of this application, the summary mode has the following three methods: first, displaying the report data as the summation result; second, displaying the report data directly in a tiled format when the report data is in list form; and third, summing the report data column by column and then displaying the summation result as a row, thus meeting various display needs.

[0034] Step 104: When the data type is internal data, after introducing a sub-report in the data entry task, the data entry task is sent to the lower-level organization of the internal system.

[0035] When the data required in the report template to be collected is data from the internal system, i.e., internal data, the subordinate organizations of the internal system need to upload the report data. In order to avoid the irregular data reporting by various subordinate organizations, the reporting task will be issued to the subordinate organizations in this embodiment of the application. At the same time, the reporting task introduces sub-reports. At this time, the subordinate organizations only need to execute the reporting task to fill in the sub-reports, thereby avoiding the chaos caused by the irregular data reporting by all subordinate organizations.

[0036] Furthermore, when a lower-level organization receives a data entry task, it determines whether the task needs to be redistributed. If so, it generates a sub-data entry task based on the report data in the sub-report and redistributes it. After the second redistribution, if the lower-level organization still needs to redistribute the data, the data entry task is redistributed again. Then, the lower-level organization receives the report data returned by the next lower-level organization, summarizes it into the sub-report, and then submits the sub-report upwards. It should be noted that the summarization method here can still be implemented using the three summarization methods mentioned above.

[0037] Step 105: Collect the sub-reports completed by the subordinate organizations based on the execution of the reporting tasks, and then summarize the sub-reports and fill them into the report template to be collected.

[0038] After the subordinate organizations submit their sub-reports, the internal system will collect and summarize the sub-reports, consolidating all the report data into the aforementioned report template. It should be noted that the summarization method described above can still be used here.

[0039] In one example of this application, when a subordinate organization performs a data entry task, it can use the following two data entry methods to fill in the sub-report: The first is automatic entry. Specifically, a data block is added to the sub-report page, containing a corresponding data retrieval model. This data retrieval model is mapped to a database table in the internal system. After mapping, the data corresponding to the data segment in the data retrieval model is retrieved from the internal system's database. Then, the retrieved data is calculated using the data retrieval formula in the sub-report, and the calculation result is entered into the sub-report as the data to be entered. It should be noted that the sub-report may not contain a data retrieval formula; in this case, the data corresponding to the data segment can be directly entered into the sub-report. The second method is manual entry. Specifically, the data that needs to be added manually is first identified in the sub-report, and the cells corresponding to this manually added data are marked. When the subordinate organization performs the data entry task, the aforementioned markings are recognized, and a click event is generated. When the user clicks the click event, an input box automatically pops up to support manual data entry.

[0040] In one example of this application, the report filling process also includes data validation. Specifically, taking the filling of sub-reports by subordinate organizations as an example, the cells with added indicator labels in the report template to be collected are first identified. When filling report data in these cells, the validation formula corresponding to the indicator label is obtained, and the data is validated using the validation formula. If the validation result is a warning, the cells with added indicator labels are filled in yellow. If the validation result is an error, an error message is displayed, and the data in the cells with added indicator labels is removed.

[0041] To provide a more detailed description of the report submission scheme in this application embodiment, the following content is also provided for explanation.

[0042] In one or more possible implementations of the embodiments of this application, the above-mentioned reporting report implementation scheme may further include the following execution process:

[0043] 1) Process design for submitting reports:

[0044] like Figure 2 As shown, during the report design phase, the superior organization adds report schemes and customizes the report template, while also adding subordinate organizations and assigning data entry schemes to their respective subordinates. During the report distribution phase, if the report is a periodic report, a collection activity with a specified period is first added based on the report scheme. The system automatically generates multiple collection instances based on the collection activity and subordinate organizations, such as Collection Instance 1, Collection Instance 2, and Collection Instance n. These multiple collection instances are then distributed to subordinate organizations to generate data entry tasks. After the subordinate organizations complete their data entry, they submit the data to the superior organization's collection instances. The superior organization can view the detailed data submitted by each subordinate organization within the collection instances, and can also click on report calculations within the collection activities to summarize and display the data in the collection instances.

[0045] 2) Display design of submitted reports:

[0046] The report display style can be customized by uploading an Excel file. Specifically, the user sets up the report template in Excel, clicks "upload template," and saves the Excel file to the file server. Then, the system uses the Python third-party library openpyxl to parse the Excel file and convert its content into an HTML file for display on the webpage. This allows for personalized report style customization, including but not limited to cell merging, table freezing, and customizable table and font colors.

[0047] 3) Data entry design for submitted reports:

[0048] The report submission supports both system data retrieval and manual data entry.

[0049] The system allows users to add multiple data blocks to the report page. Each data block can have a custom data retrieval model and be associated with other models for list retrieval and statistical retrieval. Then, SQLAlchemy is used to map the data retrieval model to the system database table. List retrieval directly retrieves the corresponding model fields from the database, while statistical retrieval involves dimension fields and statistical fields: dimension fields are set as grouping fields, aggregate functions are used to perform statistical retrieval on statistical fields, and the data block return content is obtained in the report template using the data retrieval formula specified by the system.

[0050] Furthermore, manual data refers to reports where data can be manually edited and modified. Specifically, users add specified identifiers to data cells in the report template that need to be manually added or modified. In edit mode, during the conversion of the Excel page to HTML, this specified identifier is recognized, and a click event is added to the corresponding cell. Clicking this event automatically pops up an input box that supports data editing and modification. Afterwards, clicking save will send the content of the front-end input box to the back-end for data saving and page data updates.

[0051] 4) Validation design for submitted reports:

[0052] The essence of report submission lies in the submission of indicator data. During the design process, the cells that need to be submitted are bound to indicators. During the submission process of the lower level, the data is stored in the database according to the format of the data corresponding to the indicator. Before submission, the indicator data is validated by plugging the validation formula into the data. When submitting, the indicator data is directly transmitted to the upper level.

[0053] In other words, when defining the template for the report, users need to add specific indicator identifiers to the cells corresponding to the reported data. The indicators for different cells are different, and the specific identifiers are defined by the user. After the template is uploaded, the system uses openpyxl to traverse the file, obtain the cells bound to the indicators, retrieve the indicator identifiers and data formats of those cells, and save the indicator group information in the database.

[0054] Afterwards, users can add custom validation rules during the design phase. On the rule editing page, cells can be selected to set validation rules based on system formulas. Validation levels are divided into warning and error. When lower-level systems report data, the system automatically retrieves indicator data from the database, applies it to the formula, and runs the validation. When the validation result is a warning, the corresponding cell turns yellow; when the validation result is an error, a pop-up message displays the error and cancels the data reporting.

[0055] 5) Supports the submission and distribution of reports across tenants.

[0056] Report distribution organizations are divided into two types: intra-system organizations and cross-tenant organizations. Intra-system organizations can be added directly and registered. For cross-tenant organizations, you need to add the external organization in the parent organization's system to obtain the task code. When adding the data entry task in the external organization's system, fill in the corresponding task code and the address of the parent organization's system, and then click register.

[0057] A client-side and server-side tool engine is added to the code. When a higher-level organization issues a report task, it calls the server-side engine to determine whether the issuing node is internal or external. If it is an external organization, the issuing information and task code are transmitted to the lower-level tenant via a cross-system API call. After receiving the information, the lower-level tenant identifies the task code and the reporting period, finds the corresponding reporting task, adds the task for that period, calls the client-side engine to request relevant report definition information from the higher-level organization, and saves it to its own database and file server. When users fill in the report, they directly use the information defined within their own system. When a lower-level organization reports data, the lower-level system calls the client-side engine to transmit the data to the higher-level tenant. Similarly, the higher-level tenant identifies the task code and the reporting period to which the data belongs, and saves the data to its own collection instance.

[0058] 6) Supports the submission and distribution of multi-level reports.

[0059] Data submission for reports primarily relies on the design of the form and indicators. When a subordinate receives the reporting task for the current period, if a secondary distribution is needed, the report scheme addition page can be navigated to import the report scheme from the reporting task. Subordinate organizations can then be added and the task distributed. After collecting all data reported by subordinates, the summary information can be viewed on the collection activity page. If the data is correct, the "Summarize Reporting Activity" button can be selected to summarize the collected data into the received reporting task. After verification and modification based on the actual situation, the report can be submitted. The same operation can be performed at lower levels. For the same task, only the scheme needs to be imported once; subsequent collection activities at this level can be initiated directly.

[0060] 7) Supports multiple report summary modes

[0061] The report supports three modes when collecting activity summary data. These modes are specified on each sheet during the report template design (using an Excel file). During report calculation, the report automatically iterates through the Excel file to obtain the summary mode for each page and summarizes and displays the lower-level data as required.

[0062] Summarize: Sum all reported data directly in each cell bound to an indicator and display the sum in the collection activity.

[0063] Detailed summary: The data submitted by the subordinate is in list format. The superior directly displays the multiple list data submitted by the subordinate in a flat layout at this level.

[0064] Detailed Summation and Summary: This mode is consistent with detailed summary in terms of summarization. The difference is that when the data is summarized to the current level's reporting task after the lower level issues it for the second time, the list data of the lower level will be summed column by column. Then the summed results will be merged into a row of data and reported to the upper level.

[0065] Based on the same inventive concept, this application also provides a device for reporting reports, the structure of which is as follows: Figure 3 As shown.

[0066] Figure 3 This is a schematic diagram of the structure of a device for implementing a reporting function, as provided in an embodiment of this application. Figure 3 As shown, the device 300 in this embodiment of the application specifically includes: at least one processor 301; and a memory 303 communicatively connected to at least one processor 301 (connected via a bus 302); wherein the memory 303 stores instructions that can be executed by at least one processor 301 to enable at least one processor 301 to execute a reporting method as described in the above embodiment.

[0067] In one or more possible implementations of the embodiments of this application, the aforementioned processor is configured to perform the following actions: obtain a report template to be collected, and determine the data type corresponding to the report data in the report template to be collected, wherein the data type includes internal data and external data; when the data type is external data, determine the task code of the external system to which the report data belongs, and send the task code and the filling task by calling the interface of the external system; receive the report data filled in by the external system based on the execution of the filling task when the task code is successfully identified, and fill the report data into the report template to be collected; when the data type is internal data, introduce a sub-report in the filling task and send the filling task to the lower-level organization of the internal system; collect the sub-reports completed by the lower-level organization based on the execution of the filling task, and summarize the sub-reports and fill them into the report template to be collected.

[0068] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the embodiments of this specification 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.

[0069] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0070] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0071] This specification can be described in the general context of computer-executable instructions that are executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This specification can also be practiced in distributed computing environments, where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0072] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the embodiments of apparatus, devices, and non-volatile computer storage media are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0073] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0074] The above description is merely one or more embodiments of this specification and is not intended to limit this specification. Various modifications and variations can be made to the one or more embodiments of this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of one or more embodiments of this specification should be included within the scope of the claims of this specification.

Claims

1. A method for implementing report submission, characterized in that, The method includes: Obtain the report template to be collected, and determine the data type of the report data in the report template to be collected, wherein the data type includes internal data and external data; When the data type is external data, the task code of the external system to which the report data belongs is determined, and the task code and the filling task are sent out by calling the interface of the external system. When the external system successfully recognizes the task code, the report data filled in based on the execution of the filling task is received, and the report data is filled into the report template to be collected. When the data type is external data, the method further includes: adding an external system to the internal system and generating a task code corresponding to the external system; and, after the external system successfully identifies the task code, determining whether the reporting task is a periodic reporting task. If so, adding a periodic task to the external system and periodically reporting the report data to the internal system based on the periodic task. When the data type is internal data, after introducing sub-reports in the filling task, the filling task is sent to the lower-level organization of the internal system, the sub-reports completed by the lower-level organization based on the execution of the filling task are collected, and the sub-reports are summarized and filled into the report template to be collected. Before summarizing the sub-reports and filling them into the report template to be collected, the method further includes: determining the summary mode corresponding to the sub-reports, wherein the summary mode includes summation summary, detail summary, and detail summation summary; wherein, the summation summary is to display the report data corresponding to the sub-reports as a summation result in the report template to be collected; the detail summary is to directly display the report data corresponding to the sub-reports in the report template to be collected; and the detail summation summary is to sum the report data corresponding to the sub-reports in the report template to be collected by column and then display the summation result in a flat layout.

2. The method for implementing a reporting report according to claim 1, characterized in that, When the data type is internal data, the method further includes: The subordinate organization determined that the reporting task needed to be issued a second time; Sub-reporting tasks are generated based on the report data in the sub-report, and the sub-reporting tasks are then distributed a second time. Receive report data from lower-level organizations based on the execution of the sub-reporting tasks; The report data reported by the lower-level organizations are summarized into the sub-report of the reporting task, and the sub-report is then submitted.

3. The method for implementing a reporting report according to claim 1, characterized in that, Before collecting the sub-reports completed by the subordinate organization based on the execution of the reporting task, the method further includes: Add a data block to the sub-report page and determine the data retrieval model corresponding to the data block; Map the data retrieval model to the database tables of the internal system; Retrieve the data corresponding to the data segment in the data retrieval model from the database of the internal system; The data returned by the data block is processed using the data retrieval formula in the subreport.

4. The method for implementing a reporting report according to claim 1, characterized in that, Before collecting the sub-reports completed by the subordinate organization based on the execution of the reporting task, the method further includes: Determine the report data that needs to be manually added in the sub-report; Add a specified identifier to the cell corresponding to the report data that needs to be added manually; When the subordinate organization performs the data entry task, the specified identifier is identified and a click event is generated; In response to the click event, an input box pops up in the sub-report to support manual data input.

5. The method for implementing a reporting report according to claim 1, characterized in that, Before filling the report data into the report template to be collected, the method further includes: Identify the cells with added indicator labels in the report template to be collected; When adding data to a cell with an indicator label, the data to be added is validated according to the validation formula corresponding to the indicator label, and the validation result is obtained. When the level of the verification result is warning, the cell with the added indicator is filled with yellow; and when the level of the verification result is error, a pop-up message is displayed indicating the error and the data addition is canceled.

6. The method for implementing a reporting report according to claim 1, characterized in that, After obtaining the report template to be collected, the method further includes: The report templates to be collected are uploaded to the system and stored on the file server; The system uses the Python third-party library openpyxl to parse the report template to be collected. The parsed template content is converted into an HTML file and displayed on the system page.

7. A device for reporting data, characterized in that, 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 to enable the at least one processor to execute a method for implementing a reporting report according to any one of claims 1-6.

Images