A data filling and publishing method, system and electronic device

Abstract

The application provides a data filling and publishing method, system and electronic equipment. It relates to the technical field of data processing. In response to an initial template download request from any branch, the system obtains reference values corresponding to the initial template and pre-fills them into the initial template to form a pre-filled template and feed back to the branch to receive filling data submitted by the branch after filling confirmation based on the pre-filled template to form a flexible version. In response to a check operation and merging instruction of the existing flexible version from the headquarters, the system merges the selected flexible versions to generate a merged version and feed back to the headquarters for review. In response to the review not passing, the review results of this review are recorded in the review history. In response to the review passing, the system upgrades the merged version that passes the review to a fixed version of the current period and displays it. In this way, the history version is traceable, the multi-source data is unified and managed, and the final merging efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, system and electronic device for data entry and publication. Background Technology

[0002] In scenarios involving collaborative data reporting from branch offices to headquarters, a version overwrite mechanism is often used, where newer versions overwrite older ones, making historical data untraceable. Furthermore, the data submitted by multiple branches is tightly coupled with the final report presented to headquarters. In addition, existing technologies often only support single-type data entry, making it difficult to integrate data obtained through different methods such as automated upstream data retrieval and manual entry. Moreover, integrating multi-branch data requires manually opening, copying, and merging documents one by one, which is inefficient and prone to errors. Summary of the Invention

[0003] In view of this, this application provides a method, system and electronic device for data entry and publication, which aims to solve the problems of difficulty in tracing the history of multi-branch data and difficulty in integrating multiple data sources.

[0004] Firstly, this application provides a method for data entry and publication, the method comprising: In response to an initial template download request from any branch office, the system obtains the reference values ​​corresponding to the initial template and pre-fills them into the initial template, forming a pre-filled template and feeding it back to the branch office so that the branch office can receive the data submitted after filling in and confirming the data based on the pre-filled template, thus forming a flexible version. In response to the headquarters' selection operation and merging instruction for the existing flexible versions, the system merges the multiple flexible versions selected by the selection operation to generate a merged version and sends it back to the headquarters for review. The merged version includes a merged report, a merged version number, and the mapping relationship between the merged version number and the multiple flexible versions. In response to a failure to pass the headquarters' review, the review result will be entered into the review history. In response to the headquarters' approval, the system will upgrade the approved merged version to the fixed version for this cycle and display it, and record the approval result in the approval history.

[0005] Optionally, after upgrading the approved merged version to the fixed version for the current cycle and displaying it, and after recording the review results in the review history, the method further includes: Based on the targeted return instruction triggered by the headquarters in response to the return request from the branch, the system marks the status of the flexible version corresponding to the branch indicated by the targeted return instruction as returned, and causes the branch to re-enter the data to generate a new flexible version. The headquarters then replaces the corresponding flexible version in the check operation with the new flexible version, re-merges and generates a new merged version, and reviews it. In response to the headquarters' approval, the system will upgrade the approved merged version to the fixed version for this cycle and display it, and record the approval result in the approval history.

[0006] Optionally, only one fixed version may be retained for each cycle; Before upgrading the approved merged version to the fixed version of the current cycle and displaying it, the process also includes: determining whether a fixed version already exists in the current cycle; if a fixed version already exists in the current cycle, downgrading the existing fixed version to a flexible version and recording the downgrade trajectory.

[0007] Optionally, before downgrading an existing fixed version to a flexible version, the method further includes: displaying the latest fixed version for the current period on the group side, wherein the fixed version includes data of all associated flexible versions.

[0008] Optionally, obtaining the reference value corresponding to the initial template and pre-filling it into the initial template to form a pre-filled template includes: The system requests reference values ​​for each first data item in the initial template from the upstream system to obtain the value result of each first data item. The value result is either the reference value corresponding to the first data item or the value anomaly. The first data item is the data item in the initial template that needs to obtain a reference value from the upstream system. The initial template is pre-filled based on the value results of each of the first data items to form a pre-filled template.

[0009] Optionally, the initial template may further include a second data item, which is a data item that does not require manual input from the upstream system; The pre-filled template is configured with a first identifier for the first data item with pre-filled reference values, a second identifier for the first data item with abnormal values, and a third identifier for the second data item.

[0010] Optionally, the system merges multiple flexible versions selected by the checkbox operation to generate a merged version, including: The system concatenates the data corresponding to the selected flexible versions in a preset order, generates a merged report with an automatic directory and a merged version number, and records the mapping relationship between the merged version number and the multiple flexible versions to form a merged version.

[0011] Secondly, this application also provides a data entry and publication system, the system comprising: The acquisition unit is used to respond to the initial template download request at any branch office. The system acquires the reference value corresponding to the initial template and pre-fills it into the initial template to form a pre-filled template and feeds it back to the branch office so as to receive the data submitted by the branch office after filling and confirming the data based on the pre-filled template, thus forming a flexible version. The merging unit is used to respond to the headquarters' selection operation and merging instruction for the existing flexible versions. The system merges the multiple flexible versions selected by the selection operation to generate a merged version and sends it back to the headquarters for review. The merged version includes a merged report, a merged version number, and the mapping relationship between the merged version number and the multiple flexible versions. An exception handling unit is used to respond to a failure to pass the review at the headquarters and to record the review result into the review history. The upgrade unit is used to respond to the headquarters' approval. The system upgrades the approved merged version to the fixed version for the current cycle and displays it, and records the approval result into the approval history.

[0012] Optionally, only one fixed version is retained for each cycle; before upgrading the approved merged version to the fixed version of this cycle and displaying it, the upgrade unit is also used to determine whether a fixed version already exists in this cycle. If a fixed version already exists in this cycle, the existing fixed version is downgraded to a flexible version and the downgrade trajectory is recorded.

[0013] Thirdly, this application provides an electronic device that connects a headquarters and multiple branch offices to implement a data entry and publication method as described in any of the above-mentioned methods.

[0014] Fourthly, this application provides a computer storage medium storing code, wherein when the code is executed, a device executing the code implements the method described in any of the first aspects above.

[0015] This application provides a method, system, and electronic device for data entry and publication. When executing the method, this application first obtains reference values ​​from an initial template for pre-filling, achieving automatic data retrieval. Then, it receives the data submitted by branch offices after confirmation based on the pre-filled template, enabling manual entry and verification. This allows for unified management of data from both sources within the same version, solving the problem of merging multi-source data. Simultaneously, this application stores the final data provided by each branch office as a flexible version, and generates a merge version number and a mapping relationship between multiple flexible versions during merging. This ensures that each submitted flexible version and its merging source are completely recorded. Even if a new merge version is generated subsequently, historical merge versions can still be traced through the mapping relationship, avoiding data loss caused by overwrite updates. Furthermore, by selecting multiple flexible versions at headquarters and executing a one-click merge, a merge version and merge version number are automatically generated, replacing the tedious manual operation of opening, copying, and pasting data from each branch office. Thus, it achieves traceability of historical versions, unified management of multi-source data, and improved efficiency in the final merging process. Attached Figure Description

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

[0017] Figure 1 A flowchart illustrating a data entry and publication method provided in an embodiment of this application; Figure 2 This application provides a schematic diagram of the application process for a data entry and publication method. Figure 3 This is a schematic diagram of the structure of a data entry and publishing system provided in an embodiment of this application. Detailed Implementation

[0018] In multi-branch collaborative reporting scenarios such as group monthly reports, industry data collection, and supply chain collaboration, each subordinate unit (branch office) typically fills in data in a preset template and submits it, which is then aggregated and released by the group headquarters. However, existing reporting systems have many problems in practical applications, such as: single data source, with existing systems either accepting data automatically retrieved from upstream systems or only accepting manual entry, making it impossible to integrate and manage these two sources in the same process; unreliable upstream systems leading to reporting interruptions, such as when upstream systems time out or malfunction, business parties cannot obtain reference values, forcing the reporting process to stop; lack of system entry for manual data, such as competitor prices and industry research reports, which are purely manual sources and can only be transmitted offline, without version management or traceability; new version releases directly overwrite old versions, resulting in the loss of historical data that cannot be retrieved; when data from a branch office is returned, the data from that branch disappears from the report, causing the report to be fragmented and resulting in an incomplete view for senior management; finally, multiple branch documents need to be opened, copied, and merged manually one by one, which is labor-intensive, error-prone, and inefficient. Therefore, a data entry and publishing solution is needed that can uniformly access multi-source data, manage the versioning of the data, and ensure the continuity of publication and display without interruption of data return and retransmission.

[0019] To address the aforementioned issues, this application provides a method, apparatus, and electronic device for data entry and publication. This application describes a combination of upstream system data acquisition and branch office data entry, stored in flexible versions. A merged version is then created by selecting the flexible versions to be merged, and subsequently reviewed and published. During review, approved versions are upgraded to the current cycle's fixed version (the original fixed version is downgraded to a flexible version), while unapproved versions are not displayed, and the review results are recorded. Furthermore, for approved fixed versions, branch offices can proactively initiate a rollback request, and the group office can initiate a targeted rollback. The system marks the status of the corresponding flexible version for that branch office as rolled back (the system only marks an anomaly at the flexible version level; the data in each flexible version still exists and does not affect the complete data display of the published fixed version, achieving decoupling between the entry and display layers and ensuring that the displayed reports are always complete). The branch office re-enters the data to form a new flexible version, which is then merged and reviewed again by the group office. Finally, the approved merged version is determined and upgraded to the fixed version for display.

[0020] To provide a more detailed understanding of the features and technical content of the embodiments of this disclosure, the implementation of the embodiments of this disclosure will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for illustrative purposes only and are not intended to limit the embodiments of this disclosure. In the following technical description, for ease of explanation, several details are used to provide a full understanding of the disclosed embodiments. However, one or more embodiments may still be implemented without these details. In other cases, well-known structures and devices may be simplified in their depiction to simplify the drawings.

[0021] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate for the embodiments of this disclosure described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0022] Unless otherwise stated, the term "multiple" means two or more. In embodiments of this disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B means: A or B. The term "and / or" describes an association between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.

[0023] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of 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 application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0024] See Figure 1 , Figure 1 This application provides a flowchart illustrating a data entry and publishing method, which includes: S101. In response to an initial template download request from any branch office, the system obtains the reference value corresponding to the initial template and pre-fills it into the initial template to form a pre-filled template and feeds it back to the branch office so as to receive the data submitted by the branch office after filling in and confirming the data based on the pre-filled template, thus forming a flexible version.

[0025] The aforementioned system connects branch offices, headquarters, and upstream systems to achieve end-to-end data interaction and collaborative processing for this application. The branch office refers to the various business units or regional nodes under headquarters, used to provide business data for their respective branches and as the executing entities for data submission. The headquarters refers to the higher-level management of the branches, used to select, trigger merging, review, and publish the data submitted by each branch.

[0026] The reference values ​​mentioned above can refer to the values ​​of data items that can be synchronized from the upstream system (such as databases maintained by upstream servers) or preset default values.

[0027] The aforementioned initial template refers to a standardized form file used to regulate the format and content of data entry. Optionally, this initial template can be an Excel spreadsheet that is familiar to business personnel in each branch office. It can consist of several data items and serves as the basic carrier for data entry at each branch office.

[0028] The system obtains reference values ​​corresponding to the initial template and pre-fills them into the initial template to form a pre-filled template. Then, the branch offices fill in and confirm based on the existing reference values, reducing the amount of manual data entry and also reducing the workload and errors in data entry. Furthermore, each submission of a flexible version (which may include the flexible version number, submission time, and the branch office submitting it) is recorded and stored by the system. Multiple versions can coexist, and each flexible version submitted by each branch office is recorded and stored by the system, which facilitates subsequent traceability, comparison, and auditing, and also overcomes the aforementioned deficiency of manual data entry without versioning.

[0029] S102. In response to the headquarters' selection operation and merging instruction for the existing flexible versions, the system merges the multiple flexible versions selected by the selection operation to generate a merged version and sends it back to the headquarters for review. The merged version includes a merged report, a merged version number, and the mapping relationship between the merged version number and the multiple flexible versions.

[0030] The aforementioned consolidated report refers to a report document formed by combining and summarizing the data corresponding to the flexible versions submitted by multiple selected branches.

[0031] The above merge version number is a number that uses a unique identifier to identify each merge version.

[0032] The merged versions mentioned above include merge version numbers and mapping relationships, thus each merged version comes with its own source index, enabling traceability of the merged versions and ensuring clear data sources and accountability. Furthermore, merging multiple flexible versions here is executed uniformly by the system, which solves the problems of offsetting and error-proneness caused by manually opening and copying each version one by one.

[0033] S103. In response to the headquarters' failure to pass the review, the review result of this review will be entered into the review history.

[0034] S104. If the headquarters approves the review, the system will upgrade the approved merged version to the fixed version for this cycle and display it, and record the review results of this review into the review history.

[0035] Optionally, the above audit results may include fixed versions for each period, audited merged versions, flexible versions associated with the merged version number mapping of each merged version, and audit conclusions for each audit.

[0036] The audit history can include fixed versions for each period (release results record), audited merged versions (audit object record), flexible versions associated with the merged version number of each merged version (source link record), and audit conclusions for each audit (approval, disapproval of merged versions, and flexible versions with anomalies in merged versions that failed audits), providing a complete link for data review, regulatory audit, and error location.

[0037] If a flexible version fails the review of the merged version at headquarters, headquarters will directly return that failed version. The return is limited to the flexible versions at the branch office level and does not involve any status changes or data rollbacks to other approved flexible versions, reducing the amount of data processed. In this way, even if multiple versions are retained in the system (meaning that a fixed version has already been generated in the current cycle), headquarters can still view the reports of the generated fixed version completely, based on the complete version retention in the system. During subsequent returns and retransmissions, the report content displayed at headquarters remains continuous, avoiding the interruption of the overall report display caused by partial data return and re-entry, as is common in existing technologies.

[0038] Based on the above steps S101 to S104, it can be seen that this application involves the entire process of report filling, including pre-filling, merging, reviewing, and finalizing the report, and realizes the merging of multi-branch data reporting.

[0039] In the embodiments of this application, the above Figure 1 There are several possible implementations of step S101, which will be described below. It should be noted that the implementations given below are merely illustrative examples and do not represent all implementations of the embodiments of this application.

[0040] In step S101, the reference values ​​corresponding to the initial template are obtained and pre-filled into the initial template to form a pre-filled template. Specifically, this can be done as follows: The system requests reference values ​​for each first data item in the initial template from the upstream system to obtain the value result of each first data item. The value result is either the reference value corresponding to the first data item or an abnormal value. The first data item is the data item in the initial template that needs to obtain a reference value from the upstream system. The initial template is pre-filled based on the value result of each first data item to form a pre-filled template.

[0041] Among these, abnormal values ​​include situations such as incorrect data format returned by the upstream system and network request timeouts. Therefore, in the event of abnormal values, such as an unreliable upstream system causing an interruption, manual supplementation based on pre-filled templates can be used as a backup to ensure the smooth progress of the process and prevent interruptions in data entry due to upstream system anomalies or other factors.

[0042] Based on this, the initial template also includes a second data item, which is a data item that does not involve the upstream system and requires manual input, such as industry data, competitor prices, industry research report data, etc.

[0043] Furthermore, the system can configure differentiated identifiers for different data items in the pre-filled template to distinguish the data source and status, making it easier for users to quickly identify data items that require manual entry. The specific method is as follows: The pre-filled template is configured with a first identifier for the first data item with pre-filled reference values, a second identifier for the first data item with abnormal values, and a third identifier for the second data item.

[0044] Optionally, the first, second, and third identifiers mentioned above may be distinguished by one or more methods, such as using different colors, icons, or text labels.

[0045] When branch office users fill out and confirm the pre-filled template, the specific process can be as follows: users review and confirm or modify data items with the first identifier, manually supplement data items with the second identifier, and manually fill in data items with the third identifier. In this way, this application can achieve visual differentiation of three types of data (automatically retrieved data from upstream / backup data for upstream anomalies / purely manual data) in the same template, providing clear guidance for filling out the form, reducing omissions and errors, and improving filling efficiency and data accuracy.

[0046] In the embodiments of this application, the above Figure 1 There are several possible implementations of step S102, which will be described below. It should be noted that the implementations given below are merely illustrative examples and do not represent all implementations of the embodiments of this application.

[0047] In step S102, the system merges the multiple flexible versions selected by the selection operation to generate a merged version. The specific implementation process can be as follows: The system concatenates the data corresponding to the selected flexible versions in a preset order, generates a merged report with an automatic directory and a merged version number, and records the mapping relationship between the merged version number and the multiple flexible versions to form a merged version.

[0048] For example, the preset order can be the order of the branch offices corresponding to each flexible version, the order in which the check operation is performed, or other orders.

[0049] This application provides a method to combine data into a consolidated report, which can be stored in the form of an Excel spreadsheet or other document for headquarters to download. This eliminates the need to write each data row in the report back into the database, reducing data redundancy.

[0050] Based on the above embodiments, after a fixed version is formed within this cycle, if a branch office discovers an error in its data, it can also initiate a rollback request. The specific implementation process is as follows: S105. Based on the targeted return instruction triggered by the headquarters in response to the return request from the branch office, the system marks the status of the flexible version corresponding to the branch office indicated by the targeted return instruction as returned, and causes the branch office to re-enter the data to generate a new flexible version. The headquarters replaces the corresponding flexible version in the check operation with the new flexible version, re-merges and generates a new merged version and reviews it. S106. In response to the headquarters' approval, the system will upgrade the approved merged version to the fixed version for this cycle and display it, and record the review results in the review history.

[0051] S107. In response to the headquarters' review being deemed unsuccessful, the review result will be entered into the review history.

[0052] Understandably, when a branch office initiates a rollback request, the headquarters responds by triggering a targeted rollback instruction, returning the flexible version corresponding to the branch office involved in the request. In this way, errors in published content have a formal correction channel; publication does not equate to locking, and data quality can still be continuously improved. Furthermore, the system only marks the error; the versions and selections of other branches remain unaffected. The published fixed versions remain unchanged until re-merging and reviewing. Therefore, this correction process does not affect other branches or interrupt the existing display on the headquarters.

[0053] It should be noted that only one fixed version is retained at any given time in each period in this application. Optionally, the period can be a week, month, year, etc., for example, retaining one fixed version for each calendar month, and the fixed version for each calendar month can be maintained independently. In particular, during the merging and review process of the new merged version, the original merged version remains visible to ensure the continuity and stability of data display.

[0054] Before upgrading the approved merged version to the fixed version of the current cycle and displaying it, the process also includes: determining whether a fixed version already exists in the current cycle; if a fixed version already exists in the current cycle, downgrading the existing fixed version to a flexible version and recording the downgrade trajectory.

[0055] This downgrade trajectory records both the original fixed version that was downgraded to a flexible version and the new fixed version that replaced it. This allows for tracing the original fixed version and the flexible versions mapped to each branch office, as well as the new fixed version and the flexible versions mapped to each branch office. Thus, the original fixed version is downgraded to a flexible version rather than being overwritten or deleted; historical versions are fully preserved as flexible versions, ensuring no loss of history and enabling backtracking, effectively overcoming the problem of history loss caused by version overwriting. Furthermore, recording the downgrade trajectory and version replacement process facilitates subsequent retrieval and viewing.

[0056] Before downgrading an existing fixed version to a flexible version, the process also includes: displaying the latest fixed version for the current period on the group's end, whereby the fixed version includes data from all mapped and associated flexible versions. In other words, the complete original fixed version is displayed before generating a new one.

[0057] Based on the above method embodiments, see Figure 2 The flowchart shown illustrates a data entry and publication method. This application provides a specific application embodiment of the data entry and publication method, taking as an example three branches of a group in Beijing, Shanghai, and Guangdong that need to submit monthly operating data to the group on a monthly basis. The specific steps are as follows: S1: The branch office initiates a template download request.

[0058] For example, a business staff member at the Shanghai branch logs into the system and initiates a download request for the current month's (e.g., January 2026) business data reporting template through the user interface. This template can be in Excel format and contains multiple data fields for each item.

[0059] S2: The system requests a reference value from the upstream system.

[0060] For example, after receiving a download request, the system automatically initiates a reference value query request to the upstream core business system according to the mapping rules of the first data item in the pre-configured template, requesting to obtain the relevant operating data of the Shanghai branch for the current period.

[0061] S3: The system automatically pre-fills templates.

[0062] For example, the system receives reference values ​​for each first data item returned by the upstream system and automatically fills the reference values ​​into the corresponding cells of the template according to the mapping relationship of each first data item in the template. If the upstream system times out or fails to return a value due to an error, the cell corresponding to the first data item is left blank and marked with a preset color for subsequent manual entry. At the same time, a different preset color is used to mark the second data items that are not involved in the upstream system.

[0063] S4: Branch office staff fill in or confirm data.

[0064] For example, business personnel in the Shanghai branch open the pre-filled template provided by the system and verify the data automatically entered by the system; for the first and second data items that the upstream system could not obtain, they manually enter them in full based on the local ledger.

[0065] S5: Branch offices submit the data.

[0066] For example, after the business personnel of the Shanghai branch confirmed that all the data was correct, they submitted the data through the system interface.

[0067] S6: The system generates flexible versions.

[0068] For example, after receiving the data submitted by the Shanghai branch, the system generates a flexible version based on the data, and its flexible version number can be recorded as "Shanghai_202601_V1".

[0069] S7: The system stores flexible version data.

[0070] For example, the system will store the generated flexible version "Shanghai_202601_V1" and its complete data in the system's version storage area for subsequent tracing and merging.

[0071] S8: The group terminal selects the source versions that need to be merged based on actual needs.

[0072] For example, when the group-level auditor logs into the system and enters the version merging interface, the system automatically displays a list of all flexible versions stored for the current month (Shanghai_202601_V1, Beijing_202601_V1, Guangdong_202601_V1). Based on the audit plan, the group-level auditor selects the flexible versions of the three branch offices that need to be merged.

[0073] S9: One-click merge is executed on the group side.

[0074] For example, when the group-level auditor clicks the one-click merge button, a merge instruction is generated. After receiving the merge instruction, the system appends and concatenates the Excel reports corresponding to the selected flexible versions in a preset order (such as ascending branch codes), automatically generates a table of contents, and forms a complete consolidated report file. At the same time, a merge version number is generated, denoted as "merge_202601_V1". The version relationship information is also recorded, that is, "merge_202601_V1" comes from the mapping relationship between "Shanghai_202601_V1", "Beijing_202601_V1", and "Guangdong_202601_V1".

[0075] S10: Submit for review at the group level.

[0076] The system sends the merged version generated in step S9 back to the group end, where the group end auditors review the data in the merged report "merge_202601_V1".

[0077] S11: Determine whether the review is approved.

[0078] If the merged version _202601_V1 passes the review, proceed to steps S12-S15 for fixed version release and display; if it fails the review, proceed to step S16.

[0079] S12: If the review is approved, the system will determine whether a fixed version already exists for the current month.

[0080] Assuming that the system approves and confirms the release in step S11, it queries whether a fixed version already exists for the current month (January 2026). If a fixed version already exists, it proceeds to step S13; otherwise, it proceeds to step S14.

[0081] S13: The original fixed version is downgraded to a flexible version, and the downgrade trajectory is recorded.

[0082] If a fixed version already exists for the current month (e.g., "fixed_202601" mentioned above), the system will automatically downgrade the original fixed version to a flexible version, recorded as "flexible_202601_history", and record the downgrade history (e.g., downgrade time, original fixed version number, downgrade reason, etc.). If there is no fixed version for the current month, this step will be skipped.

[0083] S14: Merged versions become fixed versions.

[0084] The system will upgrade the newly released merged version "Merge_202601_V1" to the new fixed version in January 2026, denoted as "Fixed_202601_New".

[0085] S15: The interface charts display a fixed version.

[0086] The system's fixed version pointer is updated to point to the new fixed version "fixed_202601_new", and the review history is entered. Afterward, the group leadership interface charts automatically query and display the data for this fixed version.

[0087] S16: Enter the audit results into the audit history.

[0088] Furthermore, the upgraded version will be entered into the review history, and the upgrade status will be reported back to each branch office.

[0089] S17. Each branch office can determine, based on changes in operating data and the audit history recorded in the system, whether the data submitted in the earliest fixed version for a certain period needs to be returned for adjustment. If a return is required, a targeted return application should be initiated to the group, and step S18 should be executed. If no return is required, the current fixed version status should be maintained.

[0090] S18: Group-level targeted refund

[0091] The branch office initiates a return request, and the group instructs the branch office to execute the return operation using the flexible version requested.

[0092] S19: The system marks the status of flexible versions that have failed the review as returned.

[0093] If a fixed version already exists for this period, the chart will still display that fixed version.

[0094] For example, after receiving the rollback instruction, the system changes the status flag of "Guangdong_202601_V1" to "Rolled Back", but the original data of this flexible version is still completely preserved. At this time, since the system interface chart only displays the current fixed version (if any), the data of the fixed version does not change due to the rollback action. Therefore, the original data of the Guangdong branch is still completely preserved in the report view, and no data loss occurs.

[0095] S20: The branch office should re-enter the correct data.

[0096] For example, after receiving the return notice, the Guangdong branch re-verifies the abnormally high operating data and completes the correction.

[0097] S21: Submit a new flexible version at the branch office end.

[0098] For example, the Guangdong branch generates a new flexible version based on the revised data, denoted as "Guangdong_202601_V2".

[0099] S22: The group terminal replaces the flexible version "Guangdong_202601_V1" selected in step S8 with the new flexible version "Guangdong_202601_V2", and performs one-click merging and review again.

[0100] The group-level reviewers re-entered the merge interface. The system displayed a list of selected flexible versions, including "Shanghai_202601_V1" for Shanghai, "Beijing_202601_V1" for Beijing, and "Guangdong_202601_V1" previously entered for Guangdong. This time, the group switched the selection for the Guangdong branch from the original V1 version to V2 version, while keeping the selections for the other branches unchanged. They then executed the one-click merge again, generating a new merged version "Merge_202601_V2" and its mapping relationships, which was then submitted for review. The review was successful, and steps S12-S14 were executed.

[0101] This completes the entire closed loop for the month, from multi-source data access, version generation, merging and review, targeted rollback, re-entry and re-merging, to fixed version release and display.

[0102] The above are some specific implementations of the methods provided in the embodiments of this application. Based on this, this application also provides corresponding apparatus. The apparatus provided in the embodiments of this application will be described below from the perspective of functional modularity.

[0103] See Figure 3 The diagram shown illustrates the structure of a data entry and publishing system. Such a system may include: The acquisition unit 301 is used to respond to the initial template download request at any branch office. The system acquires the reference value corresponding to the initial template and pre-fills it into the initial template to form a pre-filled template and feeds it back to the branch office so as to receive the data submitted by the branch office after filling and confirming the data based on the pre-filled template, thus forming a flexible version. Merging unit 302 is used to respond to the selection operation and merging instruction of the existing flexible versions at the headquarters. The system merges the multiple flexible versions selected by the selection operation to generate a merged version and sends it back to the headquarters for review. The merged version includes a merged report, a merged version number and the mapping relationship between the merged version number and the multiple flexible versions. The exception handling unit 303 is used to respond to the headquarters' failure to pass the review by entering the review result of this review into the review history. Upgrade unit 304 is used to respond to the headquarters' approval. If the headquarters approves the merged version, the system will upgrade the approved version to the fixed version of the current cycle and display it, and record the approval result of this review into the review history.

[0104] In one possible implementation, only one fixed version is retained for each period; the upgrade unit 304 is further configured to, if a fixed version already exists for the current period, downgrade the existing fixed version to a flexible version and record the downgrade trajectory, upgrade the merged version to the fixed version for the current period, and update and display the upgraded fixed version at the headquarters; if there is no fixed version for the current period, directly upgrade the merged version to the fixed version for the current period and display the fixed version at the headquarters.

[0105] In one possible implementation, the acquisition unit 301 is specifically used to request reference values ​​for each first data item in the initial template from the upstream system, and obtain the value result of each first data item. The value result is either the reference value corresponding to the first data item or an abnormal value. The first data item is the data item in the initial template that needs to obtain a reference value from the upstream system. The initial template is pre-filled based on the value result of each first data item to form a pre-filled template.

[0106] Optionally, the initial template further includes a second data item, which is a data item that does not require manual input from the upstream system. Optionally, the pre-filled template is configured with a first identifier for the first data item with pre-filled reference values, a second identifier for the first data item with abnormal values, and a third identifier for the second data item.

[0107] In one possible implementation, the merging unit 302 is specifically used to concatenate the data corresponding to the selected multiple flexible versions in a preset order, generate a merged report with an automatic directory and a merged version number, and record the mapping relationship between the merged version number and the multiple flexible versions to form a merged version.

[0108] After the approved merged version is upgraded to the fixed version of the current cycle, or after a flexible version fails the review of the merged version at the headquarters, the system also includes a recording unit for recording the review history. The review history includes the fixed version of each cycle, the approved merged version, the flexible version associated with the merged version number of each merged version, and the review conclusion of each review.

[0109] This application also provides corresponding devices and computer storage media for implementing the solutions provided in this application.

[0110] The device includes a memory and a processor. The memory is used to store instructions or code, and the processor is used to execute the instructions or code to enable the device to perform a data filling and publishing method according to any embodiment of this application.

[0111] The computer storage medium stores code, and when the code is run, the device running the code implements a data entry and publishing method as described in any embodiment of this application.

[0112] In the embodiments of this application, the terms "first" and "second" (if they exist) are used only as name identifiers and do not represent the order of first and second.

[0113] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the methods of the above embodiments can be implemented by means of software plus a general-purpose hardware platform. Based on this understanding, the technical solution of this application can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as a read-only memory (ROM) / RAM, magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network communication device such as a router) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0114] 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 its differences from other embodiments. In particular, the apparatus embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0115] The above description is merely an exemplary implementation of this application and is not intended to limit the scope of protection of this application.

Claims

1. A method for data entry and publication, characterized in that, The method includes: In response to an initial template download request from any branch office, the system obtains the reference values ​​corresponding to the initial template and pre-fills them into the initial template, forming a pre-filled template and feeding it back to the branch office so that the branch office can receive the data submitted after filling in and confirming the data based on the pre-filled template, thus forming a flexible version. In response to the headquarters' selection operation and merging instruction for the existing flexible versions, the system merges the multiple flexible versions selected by the selection operation to generate a merged version and sends it back to the headquarters for review. The merged version includes a merged report, a merged version number, and the mapping relationship between the merged version number and the multiple flexible versions. In response to a failure to pass the headquarters' review, the review result will be entered into the review history. In response to the headquarters' approval, the system will upgrade the approved merged version to the fixed version for this cycle and display it, and record the approval result in the approval history.

2. The method according to claim 1, characterized in that, After upgrading the approved merged version to the fixed version for the current cycle and displaying it, and recording the review results in the review history, the method further includes: Based on the targeted return instruction triggered by the headquarters in response to the return request from the branch, the system marks the status of the flexible version corresponding to the branch indicated by the targeted return instruction as returned, and causes the branch to re-enter the data to generate a new flexible version. The headquarters then replaces the corresponding flexible version in the check operation with the new flexible version, re-merges and generates a new merged version, and reviews it. In response to the headquarters' approval, the system will upgrade the approved merged version to the fixed version for this cycle and display it, and record the approval result in the approval history.

3. The method according to claim 2, characterized in that, Only one fixed version is retained for each cycle; Before upgrading the approved merged version to the fixed version of the current cycle and displaying it, the process also includes: determining whether a fixed version already exists in the current cycle; if a fixed version already exists in the current cycle, downgrading the existing fixed version to a flexible version and recording the downgrade trajectory.

4. The method according to claim 3, characterized in that, Before downgrading an existing fixed version to a flexible version, the process also includes: displaying the latest fixed version for the current period on the group side, wherein the fixed version includes data for all associated flexible versions.

5. The method according to claim 1, characterized in that, The step of obtaining the reference value corresponding to the initial template and pre-filling it into the initial template to form a pre-filled template includes: The system requests reference values ​​for each first data item in the initial template from the upstream system to obtain the value result of each first data item. The value result is either the reference value corresponding to the first data item or the value anomaly. The first data item is the data item in the initial template that needs to obtain a reference value from the upstream system. The initial template is pre-filled based on the value results of each of the first data items to form a pre-filled template.

6. The method according to claim 5, characterized in that, The initial template also includes a second data item, which is a data item that does not require manual input from the upstream system; The pre-filled template is configured with a first identifier for the first data item with pre-filled reference values, a second identifier for the first data item with abnormal values, and a third identifier for the second data item.

7. The method according to claim 1, characterized in that, The system merges multiple flexible versions selected by the checkbox operation to generate a merged version, including: The system concatenates the data corresponding to the selected flexible versions in a preset order, generates a merged report with an automatic directory and a merged version number, and records the mapping relationship between the merged version number and the multiple flexible versions to form a merged version.

8. A system for data entry and publication, characterized in that, The system includes: The acquisition unit is used to respond to the initial template download request at any branch office. The system acquires the reference value corresponding to the initial template and pre-fills it into the initial template to form a pre-filled template and feeds it back to the branch office so as to receive the data submitted by the branch office after filling and confirming the data based on the pre-filled template, thus forming a flexible version. The merging unit is used to respond to the headquarters' selection operation and merging instruction for the existing flexible versions. The system merges the multiple flexible versions selected by the selection operation to generate a merged version and sends it back to the headquarters for review. The merged version includes a merged report, a merged version number, and the mapping relationship between the merged version number and the multiple flexible versions. An exception handling unit is used to respond to a failure to pass the review at the headquarters and to record the review result into the review history. The upgrade unit is used to respond to the headquarters' approval. The system upgrades the approved merged version to the fixed version for the current cycle and displays it, and records the approval result into the approval history.

9. The system according to claim 8, characterized in that, Only one fixed version is retained for each cycle; before upgrading the approved merged version to the fixed version of this cycle and displaying it, the upgrade unit is also used to determine whether a fixed version already exists in this cycle. If a fixed version already exists in this cycle, the existing fixed version is downgraded to a flexible version and the downgrade trajectory is recorded.

10. An electronic device, characterized in that, The electronic device connects the headquarters and multiple branch offices to implement the data entry and publication method described in any one of claims 1-7.

Images