Audit data warehouse division construction method and device, equipment and storage medium

Abstract

The invention discloses an audit data binning construction method and device, equipment and a storage medium, and relates to the technical field of digital auditing, and the method comprises the steps: obtaining original audit data, splitting the original audit data based on a business subject domain, and obtaining an initial data set with a region identifier; performing cleaning processing and standardization processing on the initial data set based on a preset data standard system to obtain standardized audit data assets; establishing a three-level sub-warehouse catalogue for the standardized audit data assets, and writing the three-level sub-warehouse catalogue into a metadatabase to obtain a multi-level audit data sub-warehouse catalogue; the multi-level auditing data warehouse-dividing catalog is synchronized to the group auditing digital comprehensive platform through an encryption interface, interconnected and intercommunicated catalog data is obtained, regional auditing data is rapidly warehoused according to a unified standard and safely synchronized to a group platform, and instant calling of a group is supported.

Description

Technical Field

[0001] This invention relates to the field of digital auditing technology, and in particular to a method, apparatus, equipment and storage medium for constructing audit data silos. Background Technology

[0002] As large energy groups expand their business scale, the operational, financial, and production data generated by regional companies are increasing rapidly. The group level urgently needs to grasp the audit information of each region in a timely manner to strengthen risk control and compliance management. The demand for rapid aggregation and unified supervision of audit data of group enterprises is becoming increasingly prominent.

[0003] Currently, regional systems and the group platform typically exchange data through manual export or simple interface reporting. This results in inconsistent data formats, long reporting cycles, and difficulty in ensuring security, making it impossible for the group to obtain complete and accurate audit information in a timely manner, and significantly restricting the efficiency of audit supervision.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide a method, apparatus, equipment, and storage medium for constructing audit data warehouses, aiming to solve the technical problem of how to achieve efficient and secure interoperability between regional audit data and the group platform.

[0006] To achieve the above objectives, the present invention provides a method for constructing audit data warehouses, the method comprising the following steps: Obtain the original audit data, and split the original audit data based on the business subject domain to obtain an initial data set with region identifiers; Based on a preset data standard system, the initial data set is cleaned and standardized to obtain standardized audit data assets. A three-level sub-warehouse directory is established for the standardized audit data assets, and the three-level sub-warehouse directory is written into the metadata database to obtain a multi-level audit data sub-warehouse directory; The multi-level audit data silos are synchronized to the group's digital audit platform via an encrypted interface to obtain interconnected catalog data.

[0007] In one embodiment, the step of splitting the original audit data based on business subject domains to obtain an initial data set with region identifiers includes: Read the system source identifier field from the original audit data, and match the system source identifier field with the preset business topic domain mapping table to obtain candidate topic domains; The candidate topic domains are sorted based on a preset business priority threshold, and the candidate topic domains that are higher than the preset business priority threshold are determined as data areas; Generate a region code for each of the data regions, and write the region code into the original audit data to obtain an initial data set with region identifiers.

[0008] In one embodiment, the step of cleaning and standardizing the initial dataset based on a preset data standard system to obtain standardized audit data assets includes: The original fields in the initial data set are compared with the preset data standard system to establish field mapping relationships; Based on the field mapping relationship, the initial data set is renamed and format converted to obtain intermediate converted data. The value of each numeric field in the intermediate transformed data is detected, and the entire record that exceeds the preset abnormal threshold is marked as an abnormal record; Clear the abnormal records, fill in the missing fields in the remaining records, and output the completed data as a standardized audit data asset.

[0009] In one embodiment, the step of establishing a three-level sub-warehouse directory for the standardized audit data assets and writing the three-level sub-warehouse directory into a metadata database to obtain a multi-level audit data sub-warehouse directory includes: Extract the table names and table descriptions from the standardized audit data assets, and categorize the table names and table descriptions into subject domains according to their business meanings. The tables under each subject area layer are divided into sub-sub ... A hierarchical code is generated for each level of the three-level sub-warehouse directory. The hierarchical code is then associated with the table name and written into the metadata database to obtain the multi-level audit data sub-warehouse directory.

[0010] In one embodiment, the step of synchronizing the multi-level audit data silo directory to the group's digital audit platform via an encrypted interface to obtain interconnected directory data includes: The multi-level audit data silos are converted to Extensible Markup Language format to generate directory exchange messages. The directory exchange message is encrypted using a transport layer security protocol to obtain an encrypted message; The encrypted message is sent to the group's digital audit platform, and a confirmation receipt is received from the group's digital audit platform. Write the timestamp in the confirmation receipt into the regional directory status table to obtain interconnected directory data.

[0011] In one embodiment, the method further includes: Record the transformation path of the original audit data from the source system to the multi-level audit data sub-warehouse directory, and write the transformation path into a graph database to obtain a visual analysis graph; During the data extraction phase, the source system identifier, extraction time, and extraction script number are recorded to obtain the first transformation record; During the data cleaning phase, the cleaning rule number and the rule execution order are recorded to obtain the second transformation record; During the data loading phase, the target table name and loading time are recorded to obtain the third transformation record; The first transformation record, the second transformation record, and the third transformation record are written into the graph database to form the visualization analysis graph. In one embodiment, the step of synchronizing the multi-level audit data sub-warehouse directory to the group's digital audit platform via an encrypted interface to obtain interconnected directory data further includes: Generate a hierarchical permission control table, and bind the regional user identifier with the read permission, write permission, and management permission in the hierarchical permission control table to obtain the binding result; An access token is generated based on the binding result, and the access token is input into a directory exchange message; A directory exchange message containing the access token is sent to the group audit digital integration platform so that the group audit digital integration platform verifies the access token and returns the confirmation receipt; The system receives the confirmation receipt returned by the group's digital audit platform, compares the platform directory version number in the confirmation receipt with the regional directory version number, and updates the regional directory when the version numbers are inconsistent to obtain interconnected directory data.

[0012] Furthermore, to achieve the above objectives, the present invention also proposes an audit data warehousing construction device, the device comprising: The data splitting module is used to obtain the original audit data, split the original audit data based on the business subject domain, and obtain an initial data set with region identifiers; The cleaning and standardization module is used to clean and standardize the initial data set based on a preset data standard system to obtain standardized audit data assets. The directory construction module is used to establish a three-level sub-directory for the standardized audit data assets, and write the three-level sub-directory into the metadata database to obtain a multi-level audit data sub-directory. The encrypted synchronization module is used to synchronize the multi-level audit data sub-warehouse directory to the group's digital audit platform through an encrypted interface, so as to obtain interconnected directory data.

[0013] Furthermore, to achieve the above objectives, the present invention also proposes an audit data warehousing construction device, the device comprising: a memory, a processor, and an audit data warehousing construction program stored in the memory and executable on the processor, the audit data warehousing construction program being configured to implement the steps of the audit data warehousing construction method described above.

[0014] In addition, to achieve the above objectives, the present invention also proposes a storage medium storing an audit data partitioning construction program, wherein when the audit data partitioning construction program is executed by a processor, it implements the steps of the audit data partitioning construction method described above.

[0015] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the audit data warehousing construction method described above.

[0016] One or more technical solutions proposed in this application have at least the following technical effects: By splitting raw audit data scattered across multiple business systems into unified subject areas, the heterogeneity of data sources is eliminated. Then, the data is cleaned and standardized using the same data specifications to remove format conflicts and content anomalies, ensuring consistent data quality. Subsequently, a three-tiered sub-database directory is established and written into the metadata database, forming a clearly hierarchical and quickly locatable multi-level audit data sub-database directory. Finally, this directory is synchronized to the group's comprehensive digital audit platform via an encrypted interface, enabling real-time data exchange between regions and the group. As a result, the group can directly access standardized, cataloged audit data without modifying existing systems, thereby improving audit and supervision efficiency, while data security is ensured through encrypted transmission. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0018] 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, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart illustrating the first embodiment of the method for constructing audit data warehouses in this application. Figure 2 This is a flowchart illustrating the second embodiment of the method for constructing audit data warehouses in this application. Figure 3 This is a schematic diagram of the module structure of the audit data partitioning construction device according to an embodiment of this application; Figure 4 This is a schematic diagram of the hardware operating environment involved in the audit data partitioning construction method in this application embodiment.

[0020] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0021] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0022] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0023] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device or audit data warehouse construction device capable of performing the above functions. The following description uses an audit data warehouse construction device as an example to illustrate this embodiment and the subsequent embodiments.

[0024] Based on this, the embodiments of this application provide a method for constructing audit data silos, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the audit data sub-warehouse construction method of this application.

[0025] In this embodiment, the audit data warehousing construction method includes steps S10 to S40: Step S10: Obtain the original audit data, and split the original audit data based on the business subject domain to obtain an initial data set with region identifiers; It should be noted that the purpose of this step is to assign regional-level business identities to the original audit data, enabling subsequent parallel processing by region.

[0026] The original audit data comes from the initial data sets of each subordinate unit that have not yet undergone any aggregation or cleaning; the business subject area is the high-level business division defined by the group, such as production, fuel, finance, etc.

[0027] Understandably, by reading the system source identifier field and matching it with a preset mapping table, and then filtering by priority threshold and writing back the regional code, the data region splitting and identifier writing are completed.

[0028] In one feasible implementation, step S10 includes steps A11 to A13: A11: Read the system source identifier field from the original audit data, match the system source identifier field with the preset business subject domain mapping table to obtain candidate subject domains; It should be noted that the purpose of this step is to determine the business origin of each piece of raw data.

[0029] The system source identifier field is a fixed column in the original data that records the name or code of the source system.

[0030] It should be understood that after reading this field, a string exact match is performed with the preset business subject domain mapping table, and the corresponding business subject domain is output.

[0031] A12: Sort candidate topic domains based on a preset business priority threshold, and determine the candidate topic domains that are higher than the preset business priority threshold as data areas; It should be noted that the purpose of this step is to prioritize the governance of high-value data when resources are limited. The candidate subject domains are the list of major business categories obtained in the previous step; the preset business priority threshold is a passing score set by the group based on strategic importance.

[0032] Understandably, the scoring model is called to score the candidate topic domains and sort them in descending order. The portion that is above the threshold is then officially identified as the data region.

[0033] A13: Generate area codes for each data area, write the area codes into the original audit data, and obtain an initial data set with area identifiers.

[0034] It should be noted that the purpose of this step is to assign a unique, machine-readable identity to the data area. The area code is a globally unique string consisting of "subject field letter + year + sequence number"; the initial data row before the original audit data indicators.

[0035] Understandably, after the encoding rule engine generates unique codes sequentially, it writes them back to each row of data through batch processing, thus forming an initial data set with region identifiers.

[0036] Step S20: Based on the preset data standard system, the initial data set is cleaned and standardized to obtain standardized audit data assets; It should be noted that the purpose of this step is to eliminate the differences in fields, formats and numerical quality of multi-source heterogeneous data, and to form standardized audit data assets that are uniformly recognized by the group.

[0037] The initial dataset is the dataset that has been identified by region but has not yet undergone cleaning; the preset data standard system is the unified specification for field naming, type, value range, etc., issued by the group.

[0038] Understandably, the process involves renaming and format conversion based on field mapping relationships, clearing abnormal records through anomaly threshold detection, filling in missing fields, and finally outputting standardized audit data assets.

[0039] In one feasible implementation, step S20 includes steps A21 to A23: A21: Compare the original fields in the initial dataset with the preset data standard system to establish field mapping relationships; It should be noted that the purpose of this step is to resolve the alignment issue of fields with the same name but different meanings.

[0040] Original fields refer to the original column names in the initial data set; the preset data standard system is the standard field list issued by the group, including name, type, and value range.

[0041] Understandably, by comparing the original fields with the standard list item by item and establishing one-to-one or one-to-many mapping relationships, a field mapping relationship table can be generated, providing a basis for subsequent conversions.

[0042] A22: Based on the field mapping relationship, the initial data set is renamed and formatted to obtain intermediate converted data; It should be noted that the purpose of this step is to ensure that the data structure is fully aligned with the group's standards.

[0043] Field renaming refers to changing column names to standard names according to the mapping table; format conversion refers to converting dates, numbers, etc., to a unified format.

[0044] Understandably, by calling the data conversion engine to batch rename and unify the format according to the mapping relationship, intermediate converted data with field names and formats aligned can be obtained.

[0045] A23: Detect the value of each numeric field in the intermediate transformed data and mark the entire record that exceeds the preset abnormal threshold as an abnormal record; It should be noted that the purpose of this step is to remove obviously erroneous values ​​and prevent dirty data from entering the asset database.

[0046] Intermediate transformation data refers to a data set that has completed field alignment but has not yet undergone quality inspection; the preset anomaly threshold is a reasonable upper and lower limit set based on historical statistics.

[0047] Understandably, the system scans numeric fields row by row and compares them to thresholds. Records exceeding the threshold are marked as abnormal and then removed later.

[0048] A24: Clear abnormal records, fill in the missing fields in the remaining records, and output the completed data as a standardized audit data asset.

[0049] It should be noted that the purpose of this step is to ensure the integrity and usability of data assets.

[0050] An error record is the entire row of erroneous data that was marked in the previous step; missing field completion refers to filling empty values ​​with default values, forward values, or business rules.

[0051] Understandably, after clearing abnormal records, performing missing completion on the remaining records and adding filler marks will output complete and clean standardized audit data assets.

[0052] Step S30: Establish a three-level sub-warehouse directory for standardized audit data assets, write the three-level sub-warehouse directory into the metadata database, and obtain a multi-level audit data sub-warehouse directory; It should be noted that the purpose of this step is to build a hierarchical and scalable sub-directory directory to achieve rapid location and management by "searching for tables by map".

[0053] Standardized audit data assets are high-quality data sets that have been cleaned and standardized and can be directly used for analysis; the three-level sub-warehouse directory is a tree-shaped directory structure consisting of a subject area layer, a sub-subject layer, and a data table layer.

[0054] Understandably, table names are categorized hierarchically according to their business meaning, hierarchical codes are generated and associated with the table names, and then written into the metadata database to form a multi-level audit data warehousing directory.

[0055] In one feasible implementation, step S30 includes steps A31 to A33: A31: Extract table names and descriptions from standardized audit data assets, and categorize the table names and descriptions into subject area layers according to their business meaning; It should be noted that the purpose of this step is to determine the highest-level category of the directory.

[0056] The table name and description information refer to the names and Chinese annotations in the standardized audit data assets; the subject area layer refers to major categories such as production, fuel, and finance.

[0057] Understandably, keyword matching is used to categorize table names into corresponding major categories, forming a subject domain layer, which provides a framework for subsequent subdivision.

[0058] A32: Divide the tables under each subject area layer into sub-sub ... It should be noted that the purpose of this step is to achieve a coarse-to-fine directory hierarchy. The subtopic layer refers to the business subclasses under the subject domain; the data table layer refers to the specific table nodes under the subtopics.

[0059] Understandably, when keyword matching is performed again within the same subject area, sub-topics are first divided, and then specific tables are listed to form a three-level tree directory of "sub-topic-data table".

[0060] A33: Generate a hierarchical code for each level in the three-level sub-warehouse directory, associate the hierarchical code with the table name and write it into the metadata database to obtain the multi-level audit data sub-warehouse directory.

[0061] It should be noted that the purpose of this step is to assign a unique identifier that can be recognized by the machine to the directory node.

[0062] Hierarchical encoding is a fixed-length string used to uniquely identify third-level nodes; the metadata database is a database that stores the directory structure.

[0063] Understandably, by generating hierarchical codes according to fixed rules and binding them with table names, and then writing them in batches to the metadata database, a fully functional multi-level audit data warehousing directory can be obtained.

[0064] Step S40: Synchronize the multi-level audit data sub-warehouse directory to the group's digital audit platform through an encrypted interface to obtain interconnected directory data.

[0065] It should be noted that the purpose of this step is to complete the secure synchronization of the regional directory to the group's digital audit platform under the protection of encryption and authentication, and to ensure version consistency.

[0066] The multi-level audit data silo catalog refers to the catalog data generated on the regional side and which has completed hierarchical coding; the group audit digital integrated platform is the authoritative system for the group to centrally store and manage the catalogs of each region.

[0067] It is understandable that by using Extensible Markup Language format conversion, Transport Layer Security (TLS) encryption, access token verification, and version number comparison, secure transmission and bidirectional version alignment of directory data can be achieved, resulting in interconnected directory data.

[0068] In one feasible implementation, step S40 includes steps A41 to A44: A41: Convert the multi-level audit data silos to Extensible Markup Language format and generate directory exchange messages; It should be noted that the purpose of this step is to generate intermediate files that are platform-independent and easy to transmit over a network.

[0069] Multi-level audit data warehousing directory refers to a list of data tables that have been divided into three levels; Extensible Markup Language format conversion refers to serializing the structured directory into standard text.

[0070] Understandably, calling the format conversion component to automatically generate directory exchange messages containing version and digest information allows any system to parse and use them.

[0071] A42: Encrypt directory exchange messages using transport layer security protocols to obtain encrypted messages; It should be noted that the purpose of this step is to prevent leakage or tampering during the transmission process.

[0072] Directory exchange messages are the directory text to be sent; transport layer security protocol encryption refers to network security protocols that lock the entire message.

[0073] Understandably, encrypting messages through an end-to-end encryption channel creates encrypted messages, ensuring that data is not eavesdropped on or modified during transmission.

[0074] A43: Send the encrypted message to the Group's Digital Audit Platform and receive the confirmation receipt returned by the Group's Digital Audit Platform; It should be noted that the purpose of this step is to complete the message delivery and obtain a delivery certificate.

[0075] Encrypted messages refer to locked directory text; confirmation receipts are timestamped proof of receipt returned by the platform.

[0076] Understandably, sending encrypted messages through an encrypted channel and receiving confirmation receipts can obtain legal proof of service, which can be used for subsequent auditing and traceability.

[0077] A44: Write the timestamp from the confirmation receipt into the regional directory status table to obtain the interconnected directory data.

[0078] It should be noted that the purpose of this step is to record the moment of successful synchronization, which will facilitate subsequent incremental comparison.

[0079] The confirmation receipt includes the platform's receiving timestamp; the regional directory status table is the local synchronized ledger.

[0080] Understandably, writing the timestamp from the receipt into the regional directory status table marks the end of this synchronization process, thus forming interconnected directory data.

[0081] In another feasible implementation, step S40 further includes steps A51 to A54: A51: Generate a hierarchical permission control table, bind the regional user identifier with the read permission, write permission, and management permission in the hierarchical permission control table, and obtain the binding result; It should be noted that the purpose of this step is to control upload permissions and prevent unauthorized operations.

[0082] The hierarchical access control table is a rule table that records the correspondence between users and read, write, and management permissions; the binding result is the matching record of users and permissions.

[0083] Understandably, by binding the regional user identifier to the permission table through the role-permission model, a binding result can be generated, providing a basis for subsequent token issuance.

[0084] A52: Generate an access token based on the binding result, and input the access token into the directory exchange message; It should be noted that the purpose of this step is to generate a one-time identity credential to avoid repeatedly transmitting passwords.

[0085] The access token is an encrypted string containing the validity period and role, generated from the binding result; the directory exchange message is the directory text to be sent.

[0086] Understandably, by calling the token service to generate an access token and embedding it in the message header, interface authentication can be achieved, reducing the risk of credential leakage.

[0087] A53: Send a directory exchange message containing the access token to the Group Audit Digital Integration Platform so that the Group Audit Digital Integration Platform can verify the access token and return a confirmation receipt; It should be noted that the purpose of this step is for the platform to verify that the requester's identity is genuine and that they have not exceeded their authority.

[0088] Directory exchange messages containing access tokens are directory text messages with credentials; confirmation receipts are signature credentials returned by the platform after successful authorization verification.

[0089] Understandably, once the platform gateway verifies the token's validity period and role permissions, it can receive messages and return confirmation receipts, thus completing identity verification and message reception.

[0090] A54: Receive the confirmation receipt returned by the Group's Digital Audit Platform, compare the platform directory version number in the confirmation receipt with the regional directory version number, and update the regional directory when the version numbers are inconsistent to obtain interconnected directory data.

[0091] It should be noted that the purpose of this step is to ensure that the regional and group directory versions are strictly consistent.

[0092] The platform directory version number and the regional directory version number represent the current directory version at both ends, respectively; the confirmation receipt includes the latest version number of the platform. Understandably, the regional system compares the version number in the receipt with the local version number. If they do not match, it automatically pulls the latest directory to overwrite the local version, thus achieving version alignment and obtaining interoperable directory data.

[0093] This embodiment provides a method for constructing audit data warehousing. It eliminates data source heterogeneity by splitting raw audit data scattered across multiple business systems according to a unified subject domain. Then, it cleanses and standardizes the data using the same data specifications to remove format conflicts and content anomalies, ensuring consistent data quality. Subsequently, a three-level warehousing directory is established and written into a metadata database, forming a clearly hierarchical and quickly locatable multi-level audit data warehousing directory. Finally, this directory is synchronized to the group's digital audit platform via an encrypted interface, enabling real-time data exchange between regions and the group. As a result, the group can directly access standardized, cataloged audit data without modifying existing systems, thereby improving audit and supervision efficiency, while data security is ensured through encrypted transmission.

[0094] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 After step S40, steps S401 to S405 are also included: Step S401: Record the transformation path of the original audit data from the source system to the multi-level audit data sub-warehouse directory, write the transformation path into the graph database, and obtain the visualization analysis graph; It should be noted that the purpose of this step is to completely preserve the "travel path" of data from the source to the directory, so that auditors can trace the origin and development of any table afterward.

[0095] The transformation path refers to the nodes and sequence relationships of the entire "source system → cleaning → loading" chain; the graph database is a special library that stores relational data in a "node-edge" model, which is suitable for expressing the chain.

[0096] It is understandable that by abstracting each operation into nodes and the order of operations into edges and writing them into a graph database, an interactive and visual analysis graph can be obtained, which can be directly expanded and tracked by the front end.

[0097] Step S402: Record the source system identifier, extraction time, and extraction script number during the data extraction stage to obtain the first transformation record; It should be noted that the purpose of this step is to pinpoint the origin of the transport, ensuring that the source is locatable and reproducible.

[0098] The source system identifier is the registration name or number of the system from which the data originates; the extraction time refers to the server time at which the extraction action begins; and the extraction script number is the unique version number of the extraction program.

[0099] Understandably, recording the above three pieces of information as the first conversion record at the moment the extraction script starts can provide "starting point evidence" for any subsequent data challenges.

[0100] Step S403: Record the cleaning rule number and the rule execution order during the data cleaning stage to obtain the second transformation record; It should be noted that the purpose of this step is to record "how to clean and which step to clean first" to ensure that the cleaning logic is reproducible and auditable.

[0101] The cleaning rule number is the ID of each cleaning rule uniformly assigned by the group; the rule execution order refers to the sequence number in which multiple rules are run within the same batch of data.

[0102] Understandably, by writing the number and sequence of each rule into the second transformation record after it is completed, the complete cleaning sequence, such as "desensitization first, then completion", can be restored on the graph.

[0103] Step S404: Record the target table name and loading time during the data loading phase to obtain the third transformation record; It should be noted that the purpose of this step is to confirm the destination of the transportation and form a "source to destination" closed loop.

[0104] The target table name refers to the name of the physical table that will eventually be entered into the partition; the loading time refers to the timestamp of the moment the data is written.

[0105] It is understandable that recording the target table name and loading time immediately after loading and submission as a third transformation record can connect it with the starting point and process nodes to form a complete link.

[0106] Step S405: Write the first transformation record, the second transformation record, and the third transformation record into the graph database to form a visual analysis graph.

[0107] It should be noted that the purpose of this step is to piece together the three discrete records into a traceable relationship network, enabling one-click visualization.

[0108] The first, second, and third transformation records correspond to the "start point-process-end point" nodes, respectively; the graph database stores the sequential relationship between them through the "node-edge" model.

[0109] Understandably, after writing the three records as nodes into the graph database in batches and establishing sequential edges, the front end can render a visual analysis graph of "source → cleaning → loading". Clicking on any node allows you to immediately view its time, script, or rule details.

[0110] This embodiment provides a method for constructing audit data warehouses, which can trace data hop-by-hop along the edge of the graph, eliminating the need for manual comparison across multiple business systems. The nodes are fixed and time-series, allowing any data dispute to be quickly located to the specific extraction script, cleaning rules, and loading time, forming an immutable chain of evidence. Therefore, the time required for problem tracing is reduced from hours to minutes in traditional manual cross-system verification. At the same time, due to the full traceability of the process, the credibility and compliance efficiency of the audit are significantly improved.

[0111] It should be noted that the above examples are only for understanding this application and do not constitute a limitation on the audit data partitioning construction method of this application. Any simple modifications based on this technical concept are within the protection scope of this application.

[0112] This application also provides an audit data partitioning and construction device, please refer to... Figure 3 The audit data warehousing construction device includes: The data splitting module 10 is used to obtain the original audit data, split the original audit data based on the business subject domain, and obtain an initial data set with regional identifiers. The cleaning and standardization module 20 is used to clean and standardize the initial data set based on a preset data standard system to obtain standardized audit data assets. The directory construction module 30 is used to establish a three-level sub-directory for standardized audit data assets, write the three-level sub-directory into the metadata database, and obtain a multi-level audit data sub-directory. The encrypted synchronization module 40 is used to synchronize the multi-level audit data sub-warehouse directory to the group's digital audit platform through an encrypted interface, so as to obtain interconnected directory data.

[0113] The audit data warehousing construction apparatus provided in this application, employing the audit data warehousing construction method in the above embodiments, can solve the technical problem of how to achieve efficient and secure interoperability between regional audit data and the group platform. Compared with the prior art, the beneficial effects of the audit data warehousing construction apparatus provided in this application are the same as those of the audit data warehousing construction method provided in the above embodiments, and other technical features in the audit data warehousing construction apparatus are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0114] In one embodiment, the data splitting module 10 is further configured to read the system source identifier field in the original audit data, match the system source identifier field with a preset business subject domain mapping table, and obtain candidate subject domains; Candidate topic domains are sorted based on a preset business priority threshold, and candidate topic domains with a priority higher than the preset business priority threshold are identified as data areas. Generate a region code for each data region, write the region code into the original audit data, and obtain an initial data set with region identifiers.

[0115] In one embodiment, the cleaning and standardization module 20 is further used to compare the original fields in the initial data set with a preset data standard system to establish a field mapping relationship; Based on the field mapping relationship, the initial data set is renamed and formatted to obtain intermediate converted data. The system detects the value of each numeric field in the intermediate transformed data and marks the entire record that exceeds the preset abnormal threshold as an abnormal record. Clear out the abnormal records, fill in the missing fields in the remaining records, and output the completed data as a standardized audit data asset.

[0116] In one embodiment, the directory construction module 30 is further configured to extract table names and table descriptions from standardized audit data assets, and classify the table names and table descriptions into subject domain layers according to their business meanings; The tables under each subject area layer are divided into sub-sub ... Generate a hierarchical code for each level in the three-level sub-directory directory, associate the hierarchical code with the table name, and write it into the metadata database to obtain the multi-level audit data sub-directory directory.

[0117] In one embodiment, the encryption synchronization module 40 is further configured to convert the multi-level audit data silo directory into Extensible Markup Language format and generate a directory exchange message; The directory exchange message is encrypted using a transport layer security protocol to obtain an encrypted message; Send the encrypted message to the Group's Digital Audit Platform and receive a confirmation receipt from the Group's Digital Audit Platform; Write the timestamp from the confirmation receipt into the regional directory status table to obtain interconnected directory data.

[0118] In one embodiment, the encryption synchronization module 40 is also used to record the conversion path of the original audit data from the source system to the multi-level audit data sub-warehouse directory, write the conversion path into the graph database, and obtain a visual analysis graph; During the data extraction phase, the source system identifier, extraction time, and extraction script number are recorded to obtain the first transformation record; During the data cleaning phase, the cleaning rule number and the rule execution order are recorded to obtain the second transformation record; During the data loading phase, the target table name and loading time are recorded to obtain the third transformation record; The first transformation record, the second transformation record, and the third transformation record are written into the graph database to form a visual analysis graph. In one embodiment, the encryption synchronization module 40 is further configured to generate a hierarchical permission control table, and bind the regional user identifier with the read permission, write permission and management permission in the hierarchical permission control table to obtain the binding result; Generate an access token based on the binding result, and input the access token into the directory exchange message; Send a directory exchange message containing the access token to the group's digital audit platform so that the platform can verify the access token and return a confirmation receipt. Receive confirmation receipts from the group's digital audit platform, compare the platform directory version number in the confirmation receipt with the regional directory version number, and update the regional directory if the version numbers are inconsistent to obtain interconnected directory data.

[0119] This application provides an audit data warehousing construction device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the audit data warehousing construction method in the above embodiment 1.

[0120] The following is for reference. Figure 4 The diagram illustrates a structural schematic suitable for implementing the audit data warehousing construction device in the embodiments of this application. The audit data warehousing construction device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 4 The audit data warehousing construction device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0121] like Figure 4As shown, the audit data partitioning construction device may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in ROM (Read Only Memory) 1002 or a program loaded from storage device 1003 into RAM (Random Access Memory) 1004. RAM 1004 also stores various programs and data required for the operation of the audit data partitioning construction device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via bus 1005. Input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touch screens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the audit data silo building device to communicate wirelessly or wiredly with other devices to exchange data. While the figure shows audit data silo building devices with various systems, it should be understood that implementation or possession of all the systems shown is not required. More or fewer systems may be implemented alternatively.

[0122] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0123] The audit data warehousing construction device provided in this application, employing the audit data warehousing construction method in the above embodiments, can solve the technical problem of how to achieve efficient and secure interoperability between regional audit data and the group platform. Compared with the prior art, the beneficial effects of the audit data warehousing construction device provided in this application are the same as those of the audit data warehousing construction method provided in the above embodiments, and other technical features in this audit data warehousing construction device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0124] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0125] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0126] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the audit data warehousing construction method in the above embodiments.

[0127] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, RAM (Random Access Memory), ROM (Read Only Memory), EPROM (Erasable Programmable Read Only Memory or Flash Memory), optical fibers, CD-ROM (CD-Read Only Memory), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0128] The aforementioned computer-readable storage medium may be included in the audit data sub-warehouse construction device; or it may exist independently and not be assembled into the audit data sub-warehouse construction device.

[0129] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by the audit data warehousing construction device, the audit data warehousing construction device performs the following actions: acquires raw audit data; splits the raw audit data based on business subject domains to obtain an initial data set with regional identifiers; cleans and standardizes the initial data set based on a preset data standard system to obtain standardized audit data assets; establishes a three-level warehousing directory for the standardized audit data assets; writes the three-level warehousing directory into a metadata database to obtain a multi-level audit data warehousing directory; and synchronizes the multi-level audit data warehousing directory to the group's digital audit platform through an encrypted interface to obtain interconnected directory data.

[0130] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including LAN (Local Area Network) or WAN (Wide Area Network)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0131] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0132] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0133] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., computer programs) for executing the above-described audit data warehousing construction method, thereby solving the technical problem of how to achieve efficient and secure interoperability between regional audit data and the group platform. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the audit data warehousing construction method provided in the above embodiments, and will not be repeated here.

[0134] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the audit data warehousing construction method described above.

[0135] The computer program product provided in this application can solve the technical problem of how to achieve efficient and secure interoperability between regional audit data and the group platform. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the audit data partitioning construction method provided in the above embodiments, and will not be repeated here.

[0136] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A method for constructing audit data warehouses, characterized in that, The method includes: Obtain the original audit data, and split the original audit data based on the business subject domain to obtain an initial data set with region identifiers; Based on a preset data standard system, the initial data set is cleaned and standardized to obtain standardized audit data assets. A three-level sub-warehouse directory is established for the standardized audit data assets, and the three-level sub-warehouse directory is written into the metadata database to obtain a multi-level audit data sub-warehouse directory; The multi-level audit data silos are synchronized to the group's digital audit platform via an encrypted interface to obtain interconnected catalog data.

2. The method as described in claim 1, characterized in that, The step of splitting the original audit data based on business subject domains to obtain an initial data set with region identifiers includes: Read the system source identifier field from the original audit data, and match the system source identifier field with the preset business topic domain mapping table to obtain candidate topic domains; The candidate topic domains are sorted based on a preset business priority threshold, and the candidate topic domains that are higher than the preset business priority threshold are determined as data areas; Generate a region code for each of the data regions, and write the region code into the original audit data to obtain an initial data set with region identifiers.

3. The method as described in claim 1, characterized in that, The step of cleaning and standardizing the initial dataset based on a preset data standard system to obtain standardized audit data assets includes: The original fields in the initial data set are compared with the preset data standard system to establish field mapping relationships; Based on the field mapping relationship, the initial data set is renamed and format converted to obtain intermediate converted data. The value of each numeric field in the intermediate transformed data is detected, and the entire record that exceeds the preset abnormal threshold is marked as an abnormal record; Clear the abnormal records, fill in the missing fields in the remaining records, and output the completed data as a standardized audit data asset.

4. The method as described in claim 1, characterized in that, The steps of establishing a three-level sub-warehouse directory for the standardized audit data assets and writing the three-level sub-warehouse directory into the metadata database to obtain a multi-level audit data sub-warehouse directory include: Extract the table names and table descriptions from the standardized audit data assets, and categorize the table names and table descriptions into subject domains according to their business meanings. The tables under each subject area layer are divided into sub-sub ... A hierarchical code is generated for each level of the three-level sub-warehouse directory. The hierarchical code is then associated with the table name and written into the metadata database to obtain the multi-level audit data sub-warehouse directory.

5. The method as described in claim 1, characterized in that, The step of synchronizing the multi-level audit data sub-warehouse directory to the group's digital audit platform via an encrypted interface to obtain interconnected directory data includes: The multi-level audit data silos are converted to Extensible Markup Language format to generate directory exchange messages. The directory exchange message is encrypted using a transport layer security protocol to obtain an encrypted message; The encrypted message is sent to the group's digital audit platform, and a confirmation receipt is received from the group's digital audit platform. Write the timestamp in the confirmation receipt into the regional directory status table to obtain interconnected directory data.

6. The method as described in claim 1, characterized in that, The method further includes: Record the transformation path of the original audit data from the source system to the multi-level audit data sub-warehouse directory, and write the transformation path into a graph database to obtain a visual analysis graph; During the data extraction phase, the source system identifier, extraction time, and extraction script number are recorded to obtain the first transformation record; During the data cleaning phase, the cleaning rule number and the rule execution order are recorded to obtain the second transformation record; During the data loading phase, the target table name and loading time are recorded to obtain the third transformation record; The first transformation record, the second transformation record, and the third transformation record are written into the graph database to form the visualization analysis graph.

7. The method as described in claim 1, characterized in that, The step of synchronizing the multi-level audit data sub-warehouse directory to the group's digital audit platform via an encrypted interface to obtain interconnected directory data further includes: Generate a hierarchical permission control table, and bind the regional user identifier with the read permission, write permission, and management permission in the hierarchical permission control table to obtain the binding result; An access token is generated based on the binding result, and the access token is input into a directory exchange message; A directory exchange message containing the access token is sent to the group audit digital integration platform so that the group audit digital integration platform verifies the access token and returns a confirmation receipt; The system receives the confirmation receipt returned by the group's digital audit platform, compares the platform directory version number in the confirmation receipt with the regional directory version number, and updates the regional directory when the version numbers are inconsistent to obtain interconnected directory data.

8. An audit data warehousing construction device, characterized in that, The device includes: The data splitting module is used to obtain the original audit data, split the original audit data based on the business subject domain, and obtain an initial data set with region identifiers; The cleaning and standardization module is used to clean and standardize the initial data set based on a preset data standard system to obtain standardized audit data assets. The directory construction module is used to establish a three-level sub-directory for the standardized audit data assets, and write the three-level sub-directory into the metadata database to obtain a multi-level audit data sub-directory. The encrypted synchronization module is used to synchronize the multi-level audit data sub-warehouse directory to the group's digital audit platform through an encrypted interface, so as to obtain interconnected directory data.

9. An audit data warehousing construction device, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the audit data warehousing construction method as described in any one of claims 1 to 7.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the audit data warehousing construction method as described in any one of claims 1 to 7.

Images