Search

CN-121979861-A - Multi-stage verification method, system and server for business object data migration process

CN121979861ACN 121979861 ACN121979861 ACN 121979861ACN-121979861-A

Abstract

The invention discloses a multi-stage verification method, a system and a server for a business object data migration process, which are used for verifying an object to be migrated, which is generated according to migration requirements; and after mapping is completed, analyzing a return code used by the database engine for returning a writing result in real time. The problems of incomplete coverage, lack of pertinence and low automation degree of data migration verification are solved, accurate identification and intelligent treatment of abnormal behaviors of each migration link are realized, and the integrity, accuracy and smoothness of data migration are improved.

Inventors

  • LI KE
  • LI QIUXIA
  • ZHANG YING

Assignees

  • 杭州硕磐智能科技有限公司

Dates

Publication Date
20260505
Application Date
20260122

Claims (10)

  1. 1. A multi-stage verification method for a business object data migration process, comprising the steps of: S1, checking an object to be migrated generated according to migration requirements, if a first target field is detected to have no corresponding mapping rule, generating a space occupation mapping logic, and calling a corresponding default value strategy according to a target field label to carry out information complementation; S2, performing field-level verification after a data migration packet generated based on the object to be migrated enters a mapping engine to perform migration data conversion, searching a history mapping cache to perform matching if value mapping cannot be matched, and marking to generate a difference list if no matching exists; S3, analyzing a return code of the database engine for returning a writing result in real time after mapping is completed, calling a duplication elimination rule base to screen and reserve the latest or effective record if the main key conflicts, backfilling the external key after loading the object to be relied after occupying the space for writing and marking a specific mark if the external key conflicts, and triggering a safe clipping function to process data and reserve a trace-back key if the type writing fails.
  2. 2. The multi-stage verification method for business object data migration processes according to claim 1, wherein said step S2 comprises the steps of: S21, capturing and classifying various abnormal behaviors, wherein the abnormal behaviors comprise, but are not limited to, that a main object on which an external key depends is not migrated, that a difference exists in a field value under the same main key, that a sub-table external key cannot find a corresponding main key in the main table, that a character segment lack value which is required by a target system and a set format which are required by the target system are not in accordance with a target system specification; S22, generating a first compensation task according to the abnormal behavior type, keeping the migration main flow to continue to execute and asynchronously executing the first compensation task.
  3. 3. The multi-stage verification method for a business object data migration process according to claim 2, wherein the step S22 specifically comprises: If the fact that the sub-table external key cannot find the corresponding main key in the main table is detected, acquiring the corresponding preset proxy key according to the sub-table external key inquiry and occupying and writing in, and replacing the proxy key with a real main key after the corresponding main key is found; if the missing value of the character segment to be filled required by the target system is detected, acquiring a corresponding preset default value according to the character segment attribute query to be filled into a corresponding field; If the fact that the code value is missing due to the fact that the main object on which the external key depends is not migrated is detected, the history mapping knowledge base or the rule base is called to inquire the matched corresponding code value to fill, if the matched code value cannot be obtained, the occupied value is filled, and after the fact that the main object is migrated is detected, the corresponding code value is backfilled.
  4. 4. A multi-stage verification method for a business object data migration process according to claim 3, wherein said step S2 further comprises the steps of: S23, after the first supplementary task is executed, data verification and abnormal behavior capture are carried out again based on the repair data, tracking and rechecking are carried out on records with set problem marks on each strip in the difference table, and a second compensation task is triggered on the records with the secondary backfill marks, wherein the second compensation task comprises but is not limited to filling occupation value modification based on the current migration completion state of the main object.
  5. 5. The multi-stage verification method for a business object data migration process of claim 4, wherein step S1 further comprises: Checking an object to be migrated generated according to the migration requirement, if the source field type is detected to be not matched with the target field type, injecting a type conversion function, calling a preset format cleaning rule to calibrate the format of the converted field type, and generating a replacement source field type and a replacement target field type; If the detection value mapping table does not cover all the source values, generating a to-be-compensated list, injecting a set spam rule, marking the mapping record using the spam filling source values as low confidence, and filling the mapping record into the gray monitoring queue.
  6. 6. A multi-stage verification system for a business object data migration process, comprising: The migration object verification module is used for verifying an object to be migrated generated according to migration requirements, generating a space occupation mapping logic and calling a corresponding default value strategy according to a target field label to carry out information complementation if the first target field is detected to have no corresponding mapping rule, writing preliminary provision into a sub-record if main data relied on by the sub-record is detected to have no main data, and complementarily filling an external key after the main data is loaded; The data conversion verification module is used for carrying out field level verification after a data migration packet generated based on the object to be migrated enters a mapping engine to carry out migration data conversion, searching a history mapping cache to carry out matching if the value mapping cannot be matched, and marking to generate a difference list if the value mapping cannot be matched; And the conflict judging module is used for analyzing a return code of the database engine for returning a writing result in real time after mapping is finished, calling a duplication elimination rule base to screen and reserve the latest or effective record if the main key conflicts, backfilling the external key after the object to be relied is loaded after occupying the space for writing and marking a specific mark if the external key conflicts, and triggering a safe clipping function to process data and reserve a trace back key if the type writing fails.
  7. 7. The multi-stage verification system for a business object data migration process of claim 6, wherein the data transformation verification module is further configured to The behavior judging module captures and sorts various abnormal behaviors and inputs the abnormal behaviors into the difference table, wherein the abnormal behaviors comprise but are not limited to that a main object on which an external key depends is not migrated, the field value under the same main key has a difference, a sub-table external key cannot find a corresponding main key in the main table, the lack value of a character segment which is required to be filled by a target system and the set format do not accord with the target system specification; and the task execution module generates a first compensation task according to the abnormal behavior type, keeps the migration main flow to continue to execute and asynchronously executes the first compensation task.
  8. 8. The multi-stage verification system for a business object data migration process of claim 7, wherein the task execution module is further configured to: If the fact that the sub-table external key cannot find the corresponding main key in the main table is detected, acquiring the corresponding preset proxy key according to the sub-table external key inquiry and occupying and writing in, and replacing the proxy key with a real main key after the corresponding main key is found; if the missing value of the character segment to be filled required by the target system is detected, acquiring a corresponding preset default value according to the character segment attribute query to be filled into a corresponding field; If the fact that the code value is missing due to the fact that the main object on which the external key depends is not migrated is detected, the history mapping knowledge base or the rule base is called to inquire the matched corresponding code value to fill, if the matched code value cannot be obtained, the occupied value is filled, and after the fact that the main object is migrated is detected, the corresponding code value is backfilled.
  9. 9. A multi-stage verification device for a business object data migration process, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any one of claims 1-5 when executing the computer program.
  10. 10. A server comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1-5 when executing the computer program.

Description

Multi-stage verification method, system and server for business object data migration process Technical Field The present invention relates to the field of data migration technologies in enterprise information systems, and in particular, to a multi-stage verification method, system, and server for a business object data migration process. Background The business object data migration is a core technical link in enterprise information system upgrading, cross-platform data integration and business architecture adjustment, and is used for accurately and completely transmitting the business object data of a source end to a target end, so that the normal connection of a business process after migration is ensured, and therefore, the data verification capability in the migration process directly determines the overall migration quality and business risk. In the prior art, the data migration verification scheme is mostly developed around a single link, and generally, basic inspection is carried out on field mapping relations before migration, or obvious conflicts are simply intercepted in a data writing stage, and part of common abnormal behaviors are processed through preset fixed rules. However, the existing scheme still has the problems that the checking dimension is incomplete, a targeted processing mechanism is lacked, and the migration task is easily interrupted or the data quality is not up to standard. Disclosure of Invention The invention provides a multi-stage verification method for a business object data migration process, which aims at the defects in the prior art and comprises the following steps: And step S1, checking an object to be migrated generated according to the migration requirement, if the first target field is detected to have no corresponding mapping rule, generating a space occupation mapping logic, calling a corresponding default value strategy according to the target field label to carry out information complementation, and if the main data relied on by the sub-record is detected to have no main data preliminary provision, writing the main data into the sub-record, and complementarily filling the external key after the main data is loaded. And S2, performing field-level verification after the data migration packet generated based on the object to be migrated enters a mapping engine to perform migration data conversion, searching a history mapping cache to perform matching if the value mapping cannot be matched, and marking to generate a difference list if the value mapping cannot be matched. And S3, analyzing a return code of the database engine for returning a writing result in real time after mapping is finished, calling a duplication elimination rule base to screen and reserve the latest or effective record if the main key conflicts, backfilling the external key after the object to be relied is loaded after occupation writing and marking a specific mark if the external key conflicts, and triggering a safe clipping function to process data and reserve a trace-back key if the type writing fails. Preferably, the step S2 further includes the steps of: And S21, capturing and classifying various abnormal behaviors, wherein the abnormal behaviors comprise, but are not limited to, that a main object on which an external key depends is not migrated, that a difference exists in a field value under the same main key, that a sub-table external key cannot find a corresponding main key in the main table, that a character segment lack value which is required by a target system and a set format which are required by the target system are not in accordance with a target system specification. And S22, generating a first compensation task according to the abnormal behavior type, keeping the migration main flow to continue to execute and asynchronously executing the first compensation task. Preferably, the step S22 specifically includes: If the fact that the sub-table external key cannot find the corresponding main key in the main table is detected, the corresponding preset proxy key is obtained according to the sub-table external key inquiry and is written in a occupying mode, and the proxy key is replaced by the real main key after the corresponding main key is found. And if the missing value of the filling-necessary field required by the target system is detected, acquiring a corresponding preset default value according to the filling-necessary field attribute query and filling the corresponding default value into a corresponding field, and if the missing value processing miss exists, supplementing a preset occupied value and delaying the corresponding record to the follow-up batch filling. If the fact that the code value is missing due to the fact that the main object on which the external key depends is not migrated is detected, the history mapping knowledge base or the rule base is called to inquire the matched corresponding code value to fill, if the matched code value cannot be obtained, the oc