Method, device and electronic equipment for checking a baseline table

Abstract

The application provides a baseline table checking method and device and electronic equipment, and relates to the technical field of finance. The method comprises the following steps: receiving a baseline table checking request; the request carries a specified database identifier and at least one specified plan identifier; for each specified plan identifier, the following checking steps are performed: finding a source table corresponding to the specified plan identifier from a database corresponding to the database identifier; performing data extraction and data processing on the source table to obtain a baseline table corresponding to the source table; comparing the baseline table with the source table in terms of to-be-checked field data to obtain a comparison result; and displaying a checking result of the baseline table based on the comparison result. The application can perform batch baseline table checking operations according to the set specified plan identifier, thereby improving the checking efficiency and checking accuracy of the baseline table.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of finance, in particular to a baseline table checking method and device and electronic equipment. BACKGROUND

[0002] An intelligent repayment plan usually needs to extract its baseline table from the basic data of a core system such as a credit card or an account. The baseline table is the basic data for subsequent calculation of the repayment plan, and the correctness of the data determines the correctness and reliability of the output results of the subsequent processes and steps. Once the basic data is wrong, a lot of time and manpower will be wasted, and the calculated repayment time and amount are all wrong. Therefore, the correctness checking of the baseline table is the basis for all subsequent steps.

[0003] In the traditional way of manual comparison, the process is tedious, the table fields are compared, and it is difficult to check one by one manually. Long-term repeated operation of manual work is prone to errors, and the comparison cannot be started until the JOB is executed. The manual efficiency is low. SUMMARY

[0004] The purpose of the present application is to provide a baseline table checking method and device and electronic equipment, which can perform batch baseline table checking operations according to the specified plan identifier set, and improve the checking efficiency and accuracy of the baseline table.

[0005] In the first aspect, the present application provides a baseline table checking method, which comprises: receiving a baseline table checking request; the request carries a specified database identifier and at least one specified plan identifier; for each specified plan identifier, the following checking steps are performed: finding a source table corresponding to the specified plan identifier from a database corresponding to the database identifier; performing data extraction and data processing on the source table to obtain a baseline table corresponding to the source table; comparing the baseline table with the source table in the to-be-checked field data to obtain a comparison result; and displaying the checking result of the baseline table based on the comparison result.

[0006] Further, the step of comparing the baseline table with the source table in the to-be-checked field data to obtain a comparison result comprises: extracting to-be-checked field data from the baseline table and the source table respectively to obtain a first data table and a second data table; and sequentially judging whether the values corresponding to the matched to-be-checked fields in the first data table and the second data table satisfy a preset mapping relationship to obtain a comparison result.

[0007] Further, the step of extracting to-be-checked field data from the baseline table and the source table respectively to obtain a first data table and a second data table comprises: sequentially extracting a first to-be-checked field and a value corresponding to the first to-be-checked field from the baseline table and adding them to the first data table; sequentially extracting a second to-be-checked field and a value corresponding to the second to-be-checked field from the source table and adding them to the second data table; and the second to-be-checked field corresponds to the first to-be-checked field.

[0008] Further, the step of judging whether the values corresponding to the matched to-be-checked fields in the first data table and the second data table satisfy the preset mapping relationship in sequence to obtain a comparison result comprises: extracting a first value corresponding to a first to-be-checked field from the first data table and a second value corresponding to a second to-be-checked field from the second data table in a row-by-row checking manner; judging whether the relationship between the first value and the second value satisfies the corresponding preset mapping relationship; if yes, the comparison result is that the checking is passed; and if no, the comparison result is that the checking is not passed.

[0009] Further, the step of displaying the checking result of the baseline table based on the comparison result comprises: if the comparison result is that the checking is passed, displaying the corresponding checking result of the baseline table as that the checking is passed; and if the comparison result is that the checking is not passed, displaying the to-be-checked field that does not satisfy the preset mapping relationship in a preset format and stopping the continuous checking.

[0010] Further, before the step of performing the checking for each specified plan identifier, the method further comprises: extracting the plan identifiers in an updating state in a preset time period from the database; judging whether the specified plan identifier exists in the plan identifiers in the updating state for each specified plan identifier; if yes, continuing to perform the checking step; and if no, stopping the checking step.

[0011] Further, the source table comprises: a plan table and a plan deduction card table; and the baseline table comprises: a plan baseline table corresponding to the plan table and a plan deduction card baseline table corresponding to the plan deduction card table.

[0012] In a second aspect, the present application further provides a baseline table checking device, which comprises: a request receiving module configured to receive a baseline table checking request, wherein the request carries a specified database identifier and at least one specified plan identifier; and a checking module configured to perform the following checking steps for each specified plan identifier: searching for a source table corresponding to the specified plan identifier from a database corresponding to the database identifier; performing data extraction and data processing on the source table to obtain a baseline table corresponding to the source table; comparing to-be-checked field data of the baseline table with to-be-checked field data of the source table to obtain a comparison result; and displaying a checking result of the baseline table based on the comparison result.

[0013] In a third aspect, the present application further provides an electronic device comprising a processor and a memory, wherein the memory stores computer executable instructions capable of being executed by the processor, and the processor executes the computer executable instructions to implement the method of the first aspect.

[0014] In a fourth aspect, the present application also provides a computer readable storage medium, which stores computer executable instructions. When the computer executable instructions are invoked and executed by a processor, the computer executable instructions cause the processor to implement the method of the first aspect.

[0015] The baseline table checking method, device and electronic equipment provided by the present application first receive a baseline table checking request. The request carries a specified database identifier and at least one specified plan identifier. Then, for each specified plan identifier, the following checking steps are performed: a source table corresponding to the specified plan identifier is found from a database corresponding to the database identifier; data extraction and data processing are performed on the source table to obtain a baseline table corresponding to the source table; the baseline table and the source table are compared in terms of to-be-checked field data to obtain a comparison result; and the checking result of the baseline table is displayed based on the comparison result. This way can perform batch baseline table checking operation according to the specified plan identifier set, thereby improving the checking efficiency and checking accuracy of the baseline table. BRIEF DESCRIPTION OF DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the specific embodiments or prior art of the present application, the drawings needed in the specific embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0017] Figure 1 A flowchart of a baseline table checking method provided by an embodiment of the present application;

[0018] Figure 2 A flowchart of a data comparison process provided by an embodiment of the present application;

[0019] Figure 3 A schematic diagram of a baseline table checking process provided by an embodiment of the present application;

[0020] Figure 4 A structural block diagram of a baseline table checking device provided by an embodiment of the present application;

[0021] Figure 5 A structural schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0022] The technical solutions of the present application will be described in detail below with reference to the embodiments. Obviously, the described embodiments are only some of the embodiments of the present application, not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0023] At present, the baseline table check is completed by manual comparison when checking the baseline table, the process is tedious, the comparison table field is large, and errors are prone to occur, and the manual efficiency is low.

[0024] Based on this, the embodiment of the application provides a baseline table checking method, device and electronic equipment, which can perform batch baseline table checking operation according to the set specified plan identifier, and improve the checking efficiency and checking accuracy of the baseline table.

[0025] In order to facilitate the understanding of the embodiment, first, a baseline table checking method disclosed by the embodiment of the application is introduced in detail.

[0026] Figure 1 A flowchart of a baseline table checking method provided by the embodiment of the application, the method specifically includes the following steps:

[0027] Step S102, receiving a baseline table checking request; the request carries a specified database identifier and at least one specified plan identifier.

[0028] Before initiating the request, the database related information needs to be configured first, such as FAT (File Allocation Table, file allocation table) connection setting, and the plan identifier needs to be set, such as plan ID or batch plan ID.

[0029] Step S104, for each specified plan identifier, the following checking steps are performed:

[0030] Here, the following checking steps completed for each specified plan identifier are processed by a business JOB, after initiating the above baseline table checking request, the business JOB is automatically triggered, and then the following steps are automatically run:

[0031] Step S1042, searching for a source table corresponding to the specified plan identifier from a database corresponding to the database identifier;

[0032] Step S1044, performing data extraction and data processing on the source table to obtain a baseline table corresponding to the source table;

[0033] The specific data extraction and processing process is prior art, and different rules are used to process different repayment plans to obtain the baseline table corresponding to the source table.

[0034] In the embodiment of the application, the above source table can include a plan table and a plan deduction card table; and the baseline table includes a plan baseline table corresponding to the plan table and a plan deduction card baseline table corresponding to the plan deduction card table.

[0035] Step S1046, comparing the baseline table with the source table in the to-be-inspected field data to obtain a comparison result.

[0036] In specific implementation, the data of the to-be-inspected field can be extracted and added to a new table, and then the new table is used for line-by-line data comparison to determine whether the preset mapping relationship is met, so as to obtain the comparison result.

[0037] Step S1048, displaying the inspection result of the baseline table based on the comparison result.

[0038] If the comparison result meets the mapping relationship, it means that the inspection is passed, and if not, it means that the inspection is failed, and the to-be-inspected field with problems is displayed in red.

[0039] In the baseline table inspection method provided by the embodiment of the present application, first, a baseline table inspection request is received; the request carries a specified database identifier and at least one specified plan identifier; then, for each specified plan identifier, the following inspection steps are performed: a source table corresponding to the specified plan identifier is searched from a database corresponding to the database identifier; data extraction and data processing are performed on the source table to obtain a baseline table corresponding to the source table; the baseline table is compared with the source table in the to-be-inspected field data to obtain a comparison result; and the inspection result of the baseline table is displayed based on the comparison result. This way can perform batch baseline table inspection operation according to the set specified plan identifier, and improve the inspection efficiency and accuracy of the baseline table.

[0040] The embodiment of the present application also provides another baseline table inspection method, which is implemented on the basis of the above-mentioned embodiment; the data comparison process is mainly described in this embodiment.

[0041] Referring to Figure 2 The step of comparing the baseline table with the source table in the to-be-inspected field data to obtain a comparison result includes:

[0042] Step S202, extracting to-be-inspected field data from the baseline table and the source table respectively to obtain a first data table and a second data table.

[0043] In specific implementation, the first to-be-inspected field and the value corresponding to the first to-be-inspected field are extracted from the baseline table in sequence and added to the first data table; the second to-be-inspected field and the value corresponding to the second to-be-inspected field are extracted from the source table in sequence and added to the second data table; the second to-be-inspected field corresponds to the first to-be-inspected field.

[0044] For example, the to-be-inspected fields extracted from the baseline table are X, Y and Z, and the to-be-inspected fields extracted from the source table are A, B and C, which respectively correspond to X, Y and Z. There is a certain mapping relationship between the values corresponding to X and A, between the values corresponding to Y and B, and between the values corresponding to Z and C.

[0045] In step S204, it is judged whether the values corresponding to the matched fields in the first data table and the second data table respectively satisfy the preset mapping relationship, and a comparison result is obtained.

[0046] In a specific implementation, the first value corresponding to the first field to be checked is extracted from the first data table, and the second value corresponding to the second field to be checked is extracted from the second data table in a row-by-row checking manner; it is judged whether the relationship between the first value and the second value satisfies the corresponding preset mapping relationship; if yes, the comparison result is that the checking is passed; if no, the comparison result is that the checking is not passed.

[0047] For example, there is a certain mapping relationship between the values corresponding to X and A, that is, DataX = DataA + 1; then, the first value X1 corresponding to the first field to be checked X is extracted from the first data table, and the second value A1 corresponding to the second field to be checked A is extracted from the second data table, and it is judged whether the relationship between X1 and A1 satisfies DataX = DataA + 1; if yes, the checking is passed; if no, the checking is not passed.

[0048] The mapping relationship is not specifically limited in the embodiment of the application.

[0049] Further, the step of displaying the checking result of the baseline table based on the comparison result comprises: if the comparison result is that the checking is passed, displaying the checking result corresponding to the baseline table as that the checking is passed; and if the comparison result is that the checking is not passed, displaying the field to be checked which does not satisfy the preset mapping relationship according to a preset format, and stopping the continuous checking.

[0050] In order to avoid repeated and redundant checking and waste of resources, the embodiment of the application further comprises the following steps before the checking step is performed for each specified plan identifier: extracting the plan identifiers in an updating state in a preset time period from a database; judging whether the specified plan identifier exists in the plan identifiers in the updating state; if yes, the checking step is continuously performed; and if no, the checking step is stopped.

[0051] For example, the JOB sharing batch range is the data updated in the past two days, and it is considered that the data more than two days has been executed and does not need to be repeatedly run. If the data two days ago needs to be checked, the update time of the data needs to be updated, which is generally new plan data or the nearest data. It can be considered as a pre-checking condition, and the data not processed by the JOB does not need to be executed in the subsequent checking step.

[0052] The entire process is described below, and the entire program is mainly divided into four functional areas, as shown in Figure 3

[0053] ​(1) Set up and input area: manual intervention is required, and the database environment setup only needs to be configured once.

[0054] (2) Automatic execution area: automatically connects database operations and checks table data.

[0055] (3) Automatic check area: automatically connects the database to compare the differences between the source table and the target table, and the comparison is achieved by writing a small amount of code.

[0056] (4) Result collection area: a function provided by the framework that collects the execution results of the above steps. Each step is added with an assertion comparison. If it is successful, it will show a green pass; if it fails, it will show a red stop execution.

[0057] For ease of explanation, each step is numbered, and in principle, it is executed from top to bottom. The node steps provided by the framework are skipped unless necessary. The data checking workflow is as follows:

[0058] The entire process, except for the initial setup and input, requires manual intervention. After clicking the "Start" button, it is automatically processed until the execution is successful or fails. The result collection area will show which step the execution has reached, whether it is successful or failed.

[0059] 2. Thread group-check baseline table data: the default number of threads is 1, i.e., single-threaded execution;

[0060] 3. Intelligent repayment library FAT connection setup: manual setup once, and if the connection fails during execution, an error will be reported. Configure the database connection string, login user and password in advance, and verify the database connectivity. If the connection fails after starting, an error will be reported.

[0061] 4. Verify specified plan_id: input the execution plan ID. Manual input, plan_id is the identification ID throughout the entire process; plan_id is generated by the previous operation and can be generated by the front-end APP interface or retrieved from the database table.

[0062] 5. Batch verification of specified plan_id: if batch processing is required, fill in each plan ID in the CSV (Comma-Separated Values) table file, and fill in the CSV file path in Filename. Generally, export the excel table file from the database batch. Steps 5 and 4 are mutually exclusive, and step 4 is manually disabled when step 5 is enabled; based on the Jmeter framework and writing a small amount of java code, the entire manual verification step is connected into an automated step. Script development is simple, and direct database operation inspection is fast.

[0063] 7. Execute job-${plan_id}: The program automatically resets the job (a set of associated tasks or processes) state to initialization 0, the script automatically executes SQL, the job is executed by another program on a time basis, and no manual intervention is required; the application background will periodically detect the job state and process all qualified plans. The current background job is executed every 5 minutes and the database state is updated.

[0064] Steps 10-14: The program polls the database every 2 minutes to check the job execution result (the check frequency can be dynamically adjusted according to the running speed of the test environment execution machine), and when the detected job state is not 0, the background job has been successfully executed, the loop detection process is exited and the subsequent process is entered.

[0065] 10. While controller: jobStatus = 0 continues to loop, and 0 is exited from the loop detection.

[0066] 12. Check job--${plan_id}: Check the job state through SQL query, ${plan_id} is a variable, and the specific plan ID will be printed during execution, which facilitates problem positioning.

[0067] Steps 16-17: The job is to extract all the plans changed in the past 2 days and execute, and it is necessary to verify whether the plan is in this batch, if it meets the conditions, then comparison is made within the data range, and if there is one verification that does not meet the conditions, it is terminated.

[0068] 16. Verify whether in the job data range: Through business logic SQL query, it is queried whether the specified plan ID exists, 1 is returned if it exists, otherwise 0 is returned, plan_id is passed in by parameter ${plan_id} from the previous step, and the query result is saved to variable planIsExist.

[0069] 17. BeanShell assertion: Java code written for relevant personnel, the function is to compare the results, and the API provided by the framework is used to display the results. The expected value expectedReturn = 1, planIsExist is the actual return value of the above step, the expected and actual values are compared, if they are consistent, the next step is entered, if they are not consistent, the execution is aborted.

[0070] Steps 21-29, if the data in the data range is compared: the plan baseline table and the plan table are compared, the plan deduction card baseline table and the plan deduction card table are compared, and if they are inconsistent, the verification fails. Table 1 shows the source table and baseline table involved in the embodiment of the application:

[0071] Table 1

[0072]

[0073]

[0074] 22. Schedule ACCT_SR_PLAN_TAB: The required fields are queried out by SQL and saved to the variable plan.

[0075] 24. Schedule baseline table ACCT_SR_PLAN_BASE_TAB: The required fields are queried out by SQL and saved to the variable plan_base.

[0076] 25. BeanShell assertion: The written java code compares the results of the schedule table plan and the schedule baseline table plan_base variables, which is currently a whole row comparison, and can be further refined according to needs. If the comparison result is consistent, it passes, otherwise it fails. The framework parses and executes the java code through the built-in BeanShell engine.

[0077] Steps 26-29 are similar to the above, and will not be repeated here.

[0078] The baseline table checking method provided by the embodiment has the following advantages:

[0079] 1. Support for performing plan batch verification.

[0080] 2. Automatic polling of JOB execution results, without manual intervention.

[0081] 3. Automatically check whether the input plan of the input parameter is valid.

[0082] 4. The results are automatically compared with the source table in multiple fields to avoid manual item-by-item checking errors.

[0083] 5. Integrate multiple table checking processes together for batch processing to improve efficiency.

[0084] Based on the above method embodiment, the embodiment of the application further provides a baseline table checking device, as shown in Figure 4 The device includes: a request receiving module 42, configured to receive a baseline table checking request; the request carries a specified database identifier and at least one specified plan identifier; a checking module 44, configured to perform the following checking steps for each specified plan identifier: find the source table corresponding to the specified plan identifier from the database corresponding to the database identifier; perform data extraction and data processing on the source table to obtain the baseline table corresponding to the source table; compare the baseline table with the source table in the to-be-checked field data to obtain a comparison result; and display the checking result of the baseline table based on the comparison result.

[0085] Further, the check module 44 is configured to extract the field data to be checked from the baseline table and the source table respectively to obtain a first data table and a second data table; and determine whether the values corresponding to the matched fields to be checked in the first data table and the second data table satisfy the preset mapping relationship in sequence to obtain a comparison result.

[0086] Further, the check module 44 is configured to extract the first field to be checked and the value corresponding to the first field to be checked from the baseline table in sequence and add them to the first data table; extract the second field to be checked and the value corresponding to the second field to be checked from the source table in sequence and add them to the second data table; and the second field to be checked corresponds to the first field to be checked.

[0087] Further, the check module 44 is configured to extract the first value corresponding to the first field to be checked from the first data table and the second value corresponding to the second field to be checked from the second data table in sequence according to the row-by-row checking manner; determine whether the relationship between the first value and the second value satisfies the corresponding preset mapping relationship; if yes, the comparison result is that the check is passed; and if no, the comparison result is that the check is failed.

[0088] Further, the check module 44 is configured to display the check result corresponding to the baseline table as passed if the comparison result is that the check is passed; and display the field to be checked that does not satisfy the preset mapping relationship according to a preset format and stop the continuous checking if the comparison result is that the check is failed.

[0089] Further, the check module 44 is configured to extract the plan identifiers in the updating state in a preset time period from the database before performing the checking step for each specified plan identifier; determine whether the specified plan identifier exists in the plan identifiers in the updating state for each specified plan identifier; if yes, continue to perform the checking step; and if no, stop performing the checking step.

[0090] Further, the source table includes a plan table and a plan deduction card table; and the baseline table includes a plan baseline table corresponding to the plan table and a plan deduction card baseline table corresponding to the plan deduction card table.

[0091] The device provided in the embodiments of the present application has the same implementation principle and technical effects as the foregoing method embodiments. For brief description, the part of the device embodiments not mentioned can be referred to the corresponding content in the foregoing method embodiments.

[0092] The embodiments of the present application further provide an electronic device, as shown in Figure 5 The electronic device includes a processor 51 and a memory 50. The memory 50 stores computer executable instructions executable by the processor 51. The processor 51 executes the computer executable instructions to implement the following steps:

[0093] receiving a baseline table inspection request; the request carrying a specified database identifier and at least one specified plan identifier; for each specified plan identifier, performing the following inspection steps: finding a source table corresponding to the specified plan identifier from a database corresponding to the database identifier; performing data extraction and data processing on the source table to obtain a baseline table corresponding to the source table; comparing the baseline table with the source table in terms of to-be-inspected field data to obtain a comparison result; and displaying an inspection result of the baseline table based on the comparison result.

[0094] Further, the step of comparing the baseline table with the source table in terms of to-be-inspected field data to obtain a comparison result comprises: extracting to-be-inspected field data from the baseline table and the source table respectively to obtain a first data table and a second data table; and judging in sequence whether values corresponding to matched to-be-inspected fields in the first data table and the second data table respectively satisfy a preset mapping relationship to obtain the comparison result.

[0095] Further, the step of extracting to-be-inspected field data from the baseline table and the source table respectively to obtain a first data table and a second data table comprises: extracting a first to-be-inspected field and a value corresponding to the first to-be-inspected field from the baseline table in sequence and adding them to the first data table; extracting a second to-be-inspected field and a value corresponding to the second to-be-inspected field from the source table in sequence and adding them to the second data table; the second to-be-inspected field corresponds to the first to-be-inspected field.

[0096] Further, the step of judging in sequence whether values corresponding to matched to-be-inspected fields in the first data table and the second data table respectively satisfy a preset mapping relationship to obtain a comparison result comprises: extracting a first value corresponding to a first to-be-inspected field from the first data table and a second value corresponding to a second to-be-inspected field from the second data table in sequence in a row-by-row inspection manner; judging whether a relationship between the first value and the second value satisfies a corresponding preset mapping relationship; if yes, the comparison result is inspection passed; if no, the comparison result is inspection failed.

[0097] Further, the step of displaying an inspection result of the baseline table based on the comparison result comprises: if the comparison result is inspection passed, displaying the inspection result of the baseline table as inspection passed; and if the comparison result is inspection failed, displaying, in a preset format, to-be-inspected fields that do not satisfy the preset mapping relationship and stopping further inspection.

[0098] Further, before the inspection step is performed for each specified plan identifier, the method further comprises: extracting, from the database, plan identifiers in an updating state within a preset time period; for each specified plan identifier, judging whether the specified plan identifier exists in the plan identifiers in the updating state; if yes, continuing to perform the inspection step; and if no, stopping performing the inspection step.

[0099] Further, the source tables include: a plan table and a plan deduction card table; the baseline tables include: a plan baseline table corresponding to the plan table, and a plan deduction card baseline table corresponding to the plan deduction card table.

[0100] In Figure 5 In the illustrated embodiment, the electronic device further includes a bus 52 and a communication interface 53, wherein the processor 51, the communication interface 53 and the memory 50 are connected through the bus 52.

[0101] The memory 50 can include a high-speed random access memory (RAM), and can also include a non-volatile memory, such as at least one disk memory. The communication connection between the system network element and at least one other network element is realized through at least one communication interface 53 (which can be wired or wireless), and the Internet, a wide area network, a local area network, a metropolitan area network, etc. can be used. The bus 52 can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 52 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 In the figure, only one bidirectional arrow is used to represent, but it does not mean that there is only one bus or one type of bus.

[0102] The processor 51 can be an integrated circuit chip with processing capability. In implementation process, each step of the above method can be completed by integrated logic circuit of hardware in the processor 51 or by instructions in the form of software. The processor 51 described above can be a general processor, including a central processing unit (CPU), a network processor (NP), etc.; can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as a hardware code processor to execute, or be executed by a combination of hardware and software modules in the code processor. The software module can be located in a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, or other mature storage medium in the art. The storage medium is located in the storage, and the processor 51 reads the information in the storage, and combines the hardware to complete the steps of the method of the foregoing embodiments.

[0103] The embodiment of the present application further provides a computer readable storage medium, which stores computer executable instructions. When the computer executable instructions are called and executed by a processor, the computer executable instructions cause the processor to implement the above method. For details, refer to the foregoing method embodiments, which will not be described here.

[0104] The computer program product of the method, device and electronic equipment provided by the embodiment of the present application includes a computer readable storage medium storing program codes. The instructions included in the program codes can be used to execute the method described in the foregoing method embodiments. For details, refer to the method embodiments, which will not be described here.

[0105] Unless otherwise specifically stated, the relative steps, numerical expressions and values of the components and steps set forth in these embodiments do not limit the scope of the present application.

[0106] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a nonvolatile computer readable storage medium executable by a processor. Based on this understanding, the technical solutions of the present application or the part of the prior art that essentially contributes to the prior art or the part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various storage medium that can store program codes.

[0107] In the description of the present application, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer" and the like indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, and are only for the purpose of facilitating the description of the present application and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as limiting the present application. In addition, the terms "first", "second", "third" are only for the purpose of description, and cannot be understood as indicating or implying relative importance.

[0108] Finally, it should be noted that: the above-described embodiments are only specific embodiments of the present application, used to illustrate the technical solutions of the present application, and are not limited thereto, the protection scope of the present application is not limited thereto, although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art within the technical scope disclosed by the present application can modify or easily think of changes to the technical solutions recorded in the foregoing embodiments, or make equivalent replacements to part of the technical features; and these modifications, changes or replacements do not make the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for checking a baseline table, characterized in that, The method includes: Receive a baseline table check request; the request carries a specified database identifier and at least one specified plan identifier; For each of the specified plan identifiers, the following check steps are performed: Search for the source table corresponding to the specified plan identifier in the database corresponding to the database identifier; Data extraction and processing are performed on the source table to obtain the baseline table corresponding to the source table; The baseline table is compared with the source table for the fields to be checked to obtain the comparison results. The inspection results of the baseline table are displayed based on the comparison results; The step of comparing the baseline table with the source table for the fields to be checked to obtain the comparison results includes: Data of the fields to be checked are extracted from the baseline table and the source table respectively to obtain a first data table and a second data table; The values ​​corresponding to the matching fields to be checked in the first data table and the second data table are judged sequentially to see if they meet the preset mapping relationship, and the comparison results are obtained.

2. The method according to claim 1, characterized in that, The steps of extracting data of the fields to be inspected from the baseline table and the source table respectively to obtain a first data table and a second data table include: The first field to be checked and its corresponding value are sequentially extracted from the baseline table and added to the first data table. The second field to be checked and its corresponding value are sequentially extracted from the source table and added to the second data table; the second field to be checked corresponds to the first field to be checked.

3. The method according to claim 1, characterized in that, The steps of sequentially determining whether the values ​​corresponding to the matching fields to be checked in the first data table and the second data table satisfy a preset mapping relationship to obtain the comparison results include: According to the row-by-row inspection method, the first value corresponding to the first field to be inspected is extracted from the first data table, and the second value corresponding to the second field to be inspected is extracted from the second data table; Determine whether the relationship between the first value and the second value satisfies the corresponding preset mapping relationship; If so, the comparison result indicates that the check has passed; If not, the comparison result is "check failed".

4. The method according to claim 3, characterized in that, The step of displaying the inspection results of the baseline table based on the comparison results includes: If the comparison result is that the check passes, the check result corresponding to the baseline table will be displayed as "check passed". If the comparison result is that the check fails, the fields to be checked that do not meet the preset mapping relationship will be displayed according to the preset format, and the check will stop.

5. The method according to claim 1, characterized in that, Before performing the check step for each of the specified plan identifiers, the method further includes: Extract the plan identifiers that are in an update state within a preset time period from the database; For each specified plan identifier, determine whether the specified plan identifier exists among the plan identifiers in the update state; If so, continue with the aforementioned inspection steps; If not, stop performing the inspection steps.

6. The method according to claim 1, characterized in that, The source tables include: a plan table and a plan deduction card table; the baseline tables include: a plan baseline table corresponding to the plan table and a plan deduction card baseline table corresponding to the plan deduction card table.

7. A baseline table inspection device, characterized in that, The device includes: A request receiving module is used to receive baseline table check requests; the request carries a specified database identifier and at least one specified plan identifier. The inspection module is used to perform the following inspection steps for each specified plan identifier: locate the source table corresponding to the specified plan identifier in the database corresponding to the database identifier; extract and process data from the source table to obtain a baseline table corresponding to the source table; compare the data of the fields to be inspected in the baseline table with the source table to obtain a comparison result; and display the inspection result of the baseline table based on the comparison result. The step of comparing the baseline table with the source table for the fields to be checked to obtain the comparison results includes: Data of the fields to be checked are extracted from the baseline table and the source table respectively to obtain a first data table and a second data table; The values ​​corresponding to the matching fields to be checked in the first data table and the second data table are judged sequentially to see if they meet the preset mapping relationship, and the comparison results are obtained.

8. An electronic device, characterized in that, The method includes a processor and a memory, the memory storing computer-executable instructions executable by the processor, the processor executing the computer-executable instructions to implement the method of any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when invoked and executed by a processor, cause the processor to perform the method according to any one of claims 1 to 6.

Images