Business data checking method and apparatus

Abstract

The application provides a business data checking method and device. The method is suitable for a business system which is marked with main data, and comprises the following steps: setting a checking rule according to the main data, the checking rule comprising at least one of a length rule, a consistency rule and a non-empty rule, the length rule being used for checking the field length of business data, the consistency rule being used for checking whether the field of the business data is consistent with the field of the main data, and the non-empty rule being used for checking whether the field value of the business data is non-empty; determining the corresponding relationship between the metadata of the main data and the checking rule; obtaining the metadata of the business data; determining the mapping relationship between the metadata of the business data and the checking rule according to the metadata of the business data and the corresponding relationship; determining the checking rule corresponding to the first business data according to the mapping relationship; and checking the first business data according to the checking rule corresponding to the first business data and the main data. The business data checking method can improve the business data checking efficiency.

Description

Technical Field

[0001] This application relates to the field of database technology, and in particular to a method and apparatus for business data inspection. Background Technology

[0002] Currently, enterprises typically use master data as the benchmark data for various business departments within the enterprise. Master data refers to basic data shared between systems and can be reused across different business departments within the enterprise. For enterprises, master data has a single and accurate data source, making it benchmark data with high business value. Therefore, master data serves as the data standard for enterprises to perform business operations and decision analysis. However, data quality issues often arise during the use of master data by different business departments within an enterprise, resulting in inconsistent data quality across different departments.

[0003] Currently, the common method to check the data quality of business data from various business departments is to compare business data with master data. First, the business data to be checked from the business systems of each business department within the enterprise is exported along with the master data from the master data system. Then, the exported business data and master data are manually compared and verified.

[0004] However, existing methods for inspecting business data are inefficient. Summary of the Invention

[0005] To improve the efficiency of business data inspection, this application provides a business data inspection method and apparatus, which adopts the following technical solution.

[0006] Firstly, this application provides a business data inspection method, applicable to business systems where business data has been standardized with master data, the method comprising:

[0007] The master data is used to set inspection rules, which include at least one of length rules, consistency rules, and non-empty rules. The length rule is used to check the field length of the business data, the consistency rule is used to check whether the fields of the business data are consistent with the fields of the master data, and the non-empty rule is used to check whether the field values ​​of the business data are not empty.

[0008] Determine the correspondence between the metadata of the master data and the inspection rules;

[0009] Obtain the metadata of the business data;

[0010] The mapping relationship between the metadata of the business data and the inspection rules is determined based on the metadata of the business data and the correspondence.

[0011] The inspection rules corresponding to the first business data are determined based on the mapping relationship;

[0012] The first business data is checked according to the check rules corresponding to the first business data and the master data.

[0013] The business data inspection method provided in this application determines inspection rules based on master data and establishes a correspondence between the master data metadata and the inspection rules. Then, it determines the mapping relationship between the business data and the inspection rules based on the business data metadata and the aforementioned correspondence, and inspects the business data according to the corresponding inspection rules. This effectively solves the problem of time-consuming and labor-intensive manual inspection in existing business data inspection methods, thereby improving the efficiency of business data inspection.

[0014] Secondly, this application provides a business data inspection device, applicable to business systems where business data has been standardized with master data, the device comprising:

[0015] The setting module is used to set inspection rules based on the master data. The inspection rules include at least one of length rules, consistency rules, and non-empty rules. The length rule is used to verify the field length of the business data, the consistency rule is used to verify the field type of the business data, and the non-empty rule is used to verify whether the field value of the business data is not empty.

[0016] The first determining module is used to determine the correspondence between the metadata of the master data and the inspection rules;

[0017] The acquisition module is used to acquire the metadata of the business data;

[0018] The second determining module is used to determine the mapping relationship between the metadata of the business data and the inspection rules based on the metadata of the business data and the correspondence relationship;

[0019] The third determining module is used to determine the inspection rules corresponding to the first business data based on the mapping relationship;

[0020] The inspection module is used to inspect the first business data according to the inspection rules corresponding to the first business data and the master data.

[0021] Thirdly, this application provides an electronic device, including: a processor and a memory storing computer-executable instructions; the processor is configured to execute the method as described in the first aspect when executing the computer-executable instructions stored in the memory.

[0022] Fourthly, this application provides a computer-readable storage medium storing instructions that, when executed, perform the functions described in the first aspect.

[0023] The beneficial effects of the second to fourth aspects of this application are the same as those of the first aspect mentioned above, and will not be repeated here. Attached Figure Description

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

[0025] Figure 1 Flowchart of the business data inspection method provided in the embodiments of this application Figure 1 ;

[0026] Figure 2 Flowchart of the business data inspection method provided in the embodiments of this application Figure 2 ;

[0027] Figure 3 A schematic diagram of the business data inspection device provided in the embodiments of this application;

[0028] Figure 4 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0029] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. It should be understood that these descriptions are exemplary only and are not intended to limit the scope of this disclosure. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily obscuring the concepts of this disclosure.

[0030] The accompanying drawings illustrate various structural schematics according to embodiments of the present disclosure. These drawings are not to scale, and some details have been enlarged for clarity, and some details may have been omitted. The shapes of the various regions and layers shown in the drawings, as well as their relative sizes and positional relationships, are merely exemplary and may deviate from reality due to manufacturing tolerances or technical limitations. Furthermore, those skilled in the art can design regions / layers with different shapes, sizes, and relative positions as needed.

[0031] In the following description, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first," "second," etc., may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0032] As companies grow, the conflicts between departments regarding information transmission and collaboration become increasingly prominent. To alleviate these conflicts, companies typically establish a master data system, providing a single set of common data as a unified standard for all departments. The master data itself is this common data.

[0033] In an enterprise, master data is used to define business objects; it is persistent, non-transactional data. Taking a bank as an example, its master data might be a list of customers. Each department within the bank uses this customer list as a standard to establish its own business data. The establishment of master data can break down "data silos" between different business departments within an enterprise, enabling the sharing of core foundational data across different business areas. However, data quality issues can still arise from the business data of different departments within an enterprise. For example, if the customer service department within the bank is not integrated into the bank's master data, when a notification needs to be sent to customer A, the notification might be sent to customer A's incorrect mobile phone number. This could easily lead to the leakage of customer A's information. Therefore, enterprises need to check the data quality of the business data of each business department.

[0034] Currently, the common method for checking the quality of business data is to compare it with master data. Specifically, this involves first conducting manual inspections, visiting the business systems of various units, checking business process forms by logging into the business system's functional interface, proposing master data control requirements for business fields, and conducting master data compliance checks. Then, the business units export the master data compliance data, and the exported business data is compared and verified with the master data offline.

[0035] However, current methods for inspecting business data are inefficient.

[0036] To address the aforementioned problems, this application provides a business data inspection method, which is described below in conjunction with... Figure 1 Please provide a detailed explanation.

[0037] Figure 1 Flowchart of the business data inspection method provided in the embodiments of this application Figure 1 .like Figure 1 As shown, this method is applicable to business systems where business data has been standardized with master data. Business data verification methods include:

[0038] S101. Set inspection rules based on master data. The inspection rules include at least one of length rules, consistency rules, and non-empty rules. The length rule is to verify the field length of the business data. The consistency rule is to verify whether the fields of the business data and the fields of the master data are consistent. The non-empty rule is to verify whether the field values ​​of the business data are not empty.

[0039] Business data refers to data generated by various business departments within an enterprise. For example, for the finance department, its business data may include invoice information for customers purchasing the company's products. Master data refers to the baseline data for each business department within an enterprise. For example, a bank's master data may include the bank's customer list and customer contact information.

[0040] Verifying the field length of the business data involves comparing its length with that of the master data. If the field lengths are the same, the business data has no data quality issues. Verifying the consistency of the business data fields with the master data involves comparing their lengths with those of the master data. If the fields are identical, the business data has no consistency issues. Verifying that the field values ​​of the business data are not nullables involves verifying that the business data has no non-nullable fields. If no non-nullable fields exist in the business data, then the business data has no data quality issues.

[0041] Specifically, inspection rules can be set based on the subject of the master data, the industry it belongs to, and the project experience of the staff. For example, for a bank, its master data consists of information such as a list of customers. In this case, the inspection rule can be set as a consistency rule, because the customer list and its contact information need to be completely consistent.

[0042] S102. Determine the correspondence between the master data metadata and the inspection rules.

[0043] Inspection rules can be set based on the master data's metadata. The master data's metadata determines its subject type and industry, and corresponding inspection rules can be set based on this. It's understandable that there can be multiple sets of inspection rules; one set of master data subject types can correspond to one set of inspection rules, or multiple master data subject types can correspond to one set of inspection rules. Furthermore, when there are multiple sets of inspection rules, each set of rules corresponds one-to-one with the master data's metadata.

[0044] S103. Obtain the metadata of business data.

[0045] Metadata for business data describes the business data itself. It can be understood that the type of business data can be determined based on its metadata. For example, when the business data consists of multiple customer lists, the metadata for the business data can be the customer lists themselves.

[0046] S104. Determine the mapping relationship between the metadata of business data and the inspection rules based on the metadata of business data and the metadata of master data.

[0047] Those skilled in the art will understand that there can be one or more sets of inspection rules, and each set of inspection rules corresponds to a separate set of master data metadata. Therefore, the mapping relationship between business data and inspection rules can be determined based on the metadata of the business data and the metadata of the master data. For example, suppose the metadata of the master data is a customer list, and the customer list corresponds to the first set of inspection rules. Then, when the metadata of the business data is a personnel list, the inspection rules mapped to this business data are the first set of inspection rules.

[0048] S105. Determine the inspection rules corresponding to the first business data based on the mapping relationship.

[0049] When the mapping relationship between the metadata of business data and the inspection rules is determined, since the business data corresponding to the metadata of business data is known, the inspection rules corresponding to the business data can be determined accordingly, that is, it can be determined which set of inspection rules to use to inspect the business data.

[0050] S106. Check the first business data according to the inspection rules and master data corresponding to the first business data.

[0051] It is understood that the first business data can refer to some or all of the aforementioned business data. When the inspection rule corresponding to the first business data is determined, the first business data will be inspected according to that inspection rule.

[0052] The business data inspection method provided in this application determines inspection rules based on master data and establishes a correspondence between the master data metadata and the inspection rules. Then, it determines the mapping relationship between the business data and the inspection rules based on the business data metadata and the aforementioned correspondence, and inspects the business data according to the corresponding inspection rules. This effectively solves the problem of time-consuming and labor-intensive manual inspection in existing business data inspection methods, thereby improving the efficiency of business data inspection.

[0053] Figure 2 Flowchart of the business data inspection method provided in the embodiments of this application Figure 2 This method is suitable for business systems where business data has been standardized with master data. For example... Figure 2 As shown, the business data inspection methods include:

[0054] S201. Set inspection rules based on master data. The inspection rules include at least one of the following: length rule, consistency rule, and non-empty rule. The length rule is to verify the field length of the business data. The consistency rule is to verify whether the fields of the business data are consistent with the fields of the master data. The non-empty rule is to verify whether the field values ​​of the business data are not empty.

[0055] It should be understood that the specific implementation of S201 is different from... Figure 1 Similar to S101, it will not be described in detail here.

[0056] S202. Determine the correspondence between the master data metadata and the inspection rules.

[0057] It should be understood that the specific implementation of S202 is different from... Figure 1 Similar to S102, it will not be described again here.

[0058] S203. Obtain metadata of business data.

[0059] It should be understood that the specific implementation of S203 is different from... Figure 1 Similar to S103, it will not be described in detail here.

[0060] S204. Determine the pre-filtering rules according to the inspection rules. The pre-filtering rules include at least one of the preset field type and preset field length. The preset field type includes at least one of text, number, image, and time.

[0061] In one possible implementation, the preset field length can be determined based on the metadata of the master data, and the preset field length can be the shortest field length of the metadata of the master data.

[0062] In another possible implementation, the preset field type can be determined based on the metadata of the master data. The field type can include the field type of the metadata of the master data. For example, when the field types of the metadata of the master data are number and image, the preset field type can be number and image.

[0063] S205. Determine whether the metadata of the business data conforms to the pre-screening rules.

[0064] Specifically, the process can begin by determining whether the metadata of the business data belongs to a preset field type. If the metadata belongs to a preset field type, then the process checks whether the field length of the business data is greater than or equal to the preset field length. If the field type of the metadata does not belong to a preset field type, the business data is not checked, and the process ends. If the field length of the metadata is greater than or equal to the preset field length, the next step is executed. If the field length of the metadata is less than the preset field length, the business data is not checked, and the process ends. Alternatively, the process can also begin by determining whether the field length of the metadata is greater than or equal to the preset field length. If the field length of the metadata is greater than or equal to the preset field length, then the process checks whether the field type of the metadata belongs to a preset field type. If the field length of the metadata is less than the preset field length, the business data is not checked, and the process ends. If the field type of the metadata belongs to a preset field type, the next step is executed. If the field type of the metadata does not belong to a preset field type, the business data is not checked, and the process ends.

[0065] S206. If the conditions are met, determine the similarity between the metadata of the business data and the pre-screening rules.

[0066] Similarity is the degree of similarity between the text of the pre-screening rules and the metadata of the business data. Specifically, the above similarity can be calculated in the following way:

[0067] The first feature value is calculated based on the name, encoding, and other textual information of the inspection rule; the second feature value is calculated based on the field names, comments, and other information of the business data metadata; and the similarity between the inspection rule and the business data metadata is calculated based on the first and second feature values.

[0068] It can be understood that the name of the inspection rule can be the metadata of the master data corresponding to the inspection rule, such as a customer list. The first and second feature values ​​mentioned above are feature vectors. The first feature value is calculated after processing the text and other information contained in the business data's metadata through word segmentation, etc.; the second feature value is calculated after processing the text and other information contained in the pre-screening rule through word segmentation, etc. Similarity can be the distance between the first and second feature vectors. The closer the distance, the higher the similarity between the business data's metadata and the pre-screening rule.

[0069] S207. Determine whether the similarity is greater than or equal to the preset threshold.

[0070] The preset threshold can be any positive value, for example, 0.9.

[0071] S208. If the similarity is greater than or equal to the preset threshold, then establish a thesaurus of metadata for the master data.

[0072] If the similarity is less than a preset threshold, the aforementioned business data will not be checked, and the process will end. A thesaurus is a collection of multiple synonyms related to the metadata of business data. For example, when the metadata of master data is a personnel list, its thesaurus can group fields named such as personnel name, user name, and employee into one category, serving as the thesaurus for the personnel list. Therefore, when the metadata of business data is a user name, the corresponding checking rules for the personnel list can be used for checking.

[0073] S209. Determine the mapping relationship between the metadata of business data and the inspection rules based on the metadata of business data and the thesaurus.

[0074] S210. Determine the inspection rules corresponding to the first business data based on the mapping relationship.

[0075] S211. Check the first business data according to the inspection rules and master data corresponding to the first business data.

[0076] It should be understood that the specific implementation methods of S209 to S211 are different from those of S209 to S211. Figure 1 S104 to S106 are similar and will not be described again here.

[0077] The above combination Figure 1 and Figure 2 The business data inspection method provided in the embodiments of this application has been described below, in conjunction with... Figure 3 and Figure 4 The apparatus provided in the embodiments of this application will be described in detail.

[0078] Figure 3 This is a schematic diagram of the business data inspection device 300 provided in an embodiment of this application. Device 300 is suitable for systems including master data and business data. Figure 3 As shown, the device 300 includes: a setting module 301, a first determining module 302, an acquisition module 303, a second determining module 304, a third determining module 305, and a checking module 306.

[0079] The setting module 301 is used to set inspection rules based on master data. The inspection rules include at least one of length rules, consistency rules, and non-empty rules. The length rule is used to verify the field length of the business data, the consistency rule is used to verify the field type of the business data, and the non-empty rule is used to verify whether the field value of the business data is not empty.

[0080] The first determining module 302 is used to determine the correspondence between the metadata of the master data and the inspection rules;

[0081] Module 303 is used to obtain metadata of business data;

[0082] The second determining module 304 is used to determine the mapping relationship between the metadata of the business data and the inspection rules based on the metadata of the business data and the corresponding relationship;

[0083] The third determining module 305 is used to determine the inspection rules corresponding to the first business data according to the mapping relationship;

[0084] The inspection module 306 is used to inspect the first business data according to the inspection rules and master data corresponding to the first business data.

[0085] Optionally, the device 300 further includes: a building module for building a thesaurus of metadata for master data;

[0086] The second determining module 304 is specifically used to: determine the mapping relationship between the metadata of the business data and the inspection rules based on the metadata of the business data and the thesaurus.

[0087] Optionally, the device 300 further includes: a fourth determining module, used to determine pre-screening rules according to inspection rules, the pre-screening rules including preset field types, the preset field types including at least one of text, number, image, and time;

[0088] Determine whether the metadata of the business data belongs to the preset field type;

[0089] If so, the mapping relationship between the metadata of the business data and the inspection rules is determined based on the metadata of the business data and the corresponding relationships.

[0090] Optionally, the filtering rules may also include preset field lengths;

[0091] The device 300 also includes: a fifth determining module, used to determine whether the field length of the metadata of the business data is greater than or equal to the preset field length; if so, it determines the mapping relationship between the metadata of the business data and the inspection rules based on the metadata of the business data and the corresponding relationship.

[0092] Optionally, the fourth determining module is further configured to not check the business data if the metadata of the business data does not belong to the preset field type.

[0093] Optionally, the fifth determining module is further configured to, if the field length of the metadata of the business data is less than the preset field length, then not to check the business data.

[0094] Optionally, the device 300 further includes: a sixth determining module, configured to determine the similarity between the metadata of the business data and the pre-screening rules; if the similarity is greater than or equal to a preset threshold, then determine the mapping relationship between the metadata of the business data and the inspection rules based on the metadata of the business data and the correspondence.

[0095] The business data inspection device provided in this application embodiment is applicable to business data inspection methods, and its principle and technical effect are similar, so it will not be described again here.

[0096] This application also provides an electronic device, including: a processor and a memory storing computer-executable instructions; the processor is configured to execute the above-described method embodiment when executing the computer-executable instructions stored in the memory. The following is in conjunction with... Figure 4 Please provide a detailed explanation.

[0097] Figure 4 This is a schematic diagram of the hardware structure of an electronic device 400 provided in an embodiment of this application. Figure 4 As shown, the device 400 includes: a processor 401, a communication interface 402, a communication line 403, and a memory 404.

[0098] The processor 401 described above can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present invention. The communication interface 402 described above can be one or more. The communication interface can use any transceiver-like device for communicating with other devices or communication networks. The communication line 403 can include a path for transmitting information between the aforementioned components. The memory 404 is used to store computer execution instructions for executing the present invention, and its execution is controlled by the processor. The processor executes the computer execution instructions stored in the memory to implement the method provided in the embodiments of the present invention.

[0099] The aforementioned memory 404 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. Memory 404 may exist independently and be connected to processor 401 via communication line 403. Memory 404 may also be integrated with processor 401.

[0100] Optionally, the computer execution instructions in the embodiments of the present invention may also be referred to as application code, and the embodiments of the present invention do not specifically limit this.

[0101] It should be understood that processor 401 may include one or more CPUs, and this application does not impose a specific limitation on the number of CPUs. Furthermore, each of processors 401 may be a single-core processor or a multi-core processor, and this application does not impose a specific limitation on the product form of the processor.

[0102] The method embodiments shown in the above-described embodiments of this application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly embodied in the execution of a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0103] On the one hand, a computer-readable storage medium is provided, which stores instructions that, when executed, implement the above-described method embodiments.

[0104] On the one hand, a chip is provided for use in assessment and evaluation equipment. The chip includes at least one processor and a communication interface. The communication interface and at least one processor are coupled together. The processor is used to execute instructions to implement the above-described method embodiments.

[0105] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present invention are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a terminal, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc (DVD); or it can be a semiconductor medium, such as a solid-state drive (SSD).

[0106] Although the invention has been described herein in conjunction with various embodiments, those skilled in the art will understand and implement other variations of the disclosed embodiments by reviewing the accompanying drawings, the disclosure, and the appended claims in carrying out the claimed invention. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0107] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the device embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

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

Claims

1. A service data inspection method, characterized by, The method is suitable for a business system in which business data is marked with master data, and the method comprises: setting a check rule according to the master data, the check rule comprising at least one of a length rule, a consistency rule and a non-empty rule, the length rule being for checking the field length of the business data, the consistency rule being for checking whether the field of the business data is consistent with the field of the master data, and the non-empty rule being for checking whether the field value of the business data is non-empty; determining a correspondence between the metadata of the master data and the check rule, comprising: determining the subject type and the industry to which the master data belongs according to the metadata of the master data, and setting a corresponding check rule according to the subject type and the industry of the master data; the check rule has multiple sets, and one check rule corresponds to at least one subject type of the master data; obtaining the metadata of the business data; determining a pre-screening rule according to the check rule, the pre-screening rule comprising a preset field type, the preset field type comprising at least one of text, number, picture and time; determining whether the metadata of the business data belongs to the preset field type; if yes, determining a mapping relationship between the metadata of the business data and the check rule according to the metadata of the business data and the correspondence; determining the check rule corresponding to the first business data according to the mapping relationship; checking the first business data according to the check rule corresponding to the first business data and the master data; before the determining of the mapping relationship between the metadata of the business data and the check rule according to the metadata of the business data and the correspondence, the method further comprises: establishing a synonym library of the metadata of the master data; the determining of the mapping relationship between the metadata of the business data and the check rule according to the metadata of the business data and the correspondence specifically comprises: determining the mapping relationship between the metadata of the business data and the check rule according to the metadata of the business data and the synonym library.

2. The method of claim 1, wherein, the screening rule further comprises a preset field length; after the determining of the pre-screening rule according to the check rule, the method further comprises: determining whether the field length of the metadata of the business data is greater than or equal to the preset field length; if yes, determining the mapping relationship between the metadata of the business data and the check rule according to the metadata of the business data and the correspondence.

3. The method of claim 1, wherein, the method further comprises: if the metadata of the business data does not belong to the preset field type, the business data is not checked.

4. The method of claim 2, wherein, the method further comprises: if the field length of the metadata of the business data is less than the preset field length, the business data is not checked.

5. The method according to any of claims 2-4, characterized by, before the determining of the mapping relationship between the metadata of the business data and the check rule according to the metadata of the business data and the correspondence, the method further comprises: determining the similarity between the metadata of the business data and the pre-screening rule; If the similarity is greater than or equal to a preset threshold, a mapping relationship between the metadata of the business data and the check rule is determined according to the metadata of the business data and the corresponding relationship.

6. A service data inspection apparatus characterized by comprising: The device is suitable for a business system in which main data is involved in business data, and the device comprises: A setting module is configured to set a check rule according to the main data, the check rule comprising at least one of a length rule, a consistency rule, and a non-empty rule, the length rule being used to check a field length of the business data, the consistency rule being used to check a field type of the business data, and the non-empty rule being used to check whether a field value of the business data is non-empty; A first determining module is configured to determine a corresponding relationship between the metadata of the main data and the check rule, and specifically configured to: determine a subject type and an industry of the main data according to the metadata of the main data, and set a corresponding check rule according to the subject type and the industry of the main data, the check rule having multiple sets, and one check rule corresponding to at least one subject type of the main data; An obtaining module is configured to obtain metadata of the business data; A second determining module is configured to determine a mapping relationship between the metadata of the business data and the check rule according to the metadata of the business data and the corresponding relationship; A third determining module is configured to determine a check rule corresponding to first business data according to the mapping relationship; A checking module is configured to check the first business data according to the check rule corresponding to the first business data and the main data; A fourth determining module is configured to determine a pre-screening rule according to the check rule, the pre-screening rule comprising a preset field type, the preset field type comprising at least one of text, number, picture, and time; determine whether the metadata of the business data belongs to the preset field type.

7. An electronic device, comprising: The device comprises: a processor and a memory storing computer-executable instructions; the processor is configured to execute the computer-executable instructions stored in the memory to perform the method of any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions, and when the instructions are executed, the method of any one of claims 1-5 is implemented.

Images