CN113239019A

CN113239019A - Data migration method and system between ERP systems, electronic device and medium

Info

Publication number: CN113239019A
Application number: CN202110618728.0A
Authority: CN
Inventors: 任洪青; 赵强; 雷新洪
Original assignee: Fengjing China Building Materials Group Corp
Current assignee: Fengjing China Building Materials Group Corp
Priority date: 2021-06-03
Filing date: 2021-06-03
Publication date: 2021-08-10

Abstract

The invention provides a data migration method and a system among ERP systems, electronic equipment and a storage medium, wherein the data migration method comprises the following steps: setting data fields for exporting the ERP system and importing the ERP system; setting a logical relation between data fields of the exported ERP system and the imported ERP system and forming an imported attribute library; extracting table data exported from the ERP system, and migrating the table data to the imported ERP system according to the imported attribute library; and checking the data migrated to the ERP system. According to the invention, the field relation of the ERP system database is set to form the database field attribute library of each functional module, and the matching verification of all fields is carried out during data migration, so that the data migration between a new system and an old system is efficiently and quickly realized, the manpower and logistics are saved, the working efficiency is improved, and the use cost of software is reduced.

Description

Data migration method and system between ERP systems, electronic device and medium

Technical Field

The invention belongs to a data processing technology in the field of computers, and particularly relates to a method and a system for data migration between ERP systems.

Background

At present, with the rapid development of the domestic software industry, the application of the ERP system is more and more extensive, the ERP system providers are more and more, and the functions of the ERP system also range from simple purchase, sale and inventory to quality management, laboratory management, project management, cooperative management, electronic commerce and the like. The trend of a large number of ERP development enterprises at home and abroad, the market competition globalization, the deviation of the demands of customers, the continuous shortening of the development period, the technical application of micro-service, SARS mode platform and the like, and more ERP users face the problem of system replacement for meeting the future development demands. Before the system is replaced, the original ERP data is imported into the new system, and the important influence is brought to the switching of the ERP system and the normal operation of the new system. If the data is migrated with a little carelessness, the new system cannot be operated as expected, and the migrated data cannot be used.

For the traditional data migration or database replacement problem, for different ERP products of the same manufacturer, as the system is developed on the basis of the same database and the storage logic or method is basically the same, the data utilization rate in the old system is very high and can reach 70%; for the replacement of the ERP products among different manufacturers, the utilization rate of old data is not more than 10%, although modules of the ERP products provided by the ERP manufacturers selected by users may be the same, the corresponding implementation methods, the table structures of database records and the ERP workflow are quite different, a large amount of work needs to be completed manually during data migration, and the time consumption is long.

At present, when ERP data is migrated, an enterprise determines effective data to be migrated according to the requirements of a new ERP system and usually needs to be completed cooperatively by a plurality of departments, and in the ERP data migration process, especially the switching of the ERP systems of different manufacturers, the technical means is complex, the development cost is high, many operations need to be completed manually or even input manually, the time and the labor are consumed, and the efficiency is low.

Disclosure of Invention

The invention provides a method and a system for data migration between ERP systems aiming at the current situation that the efficiency of data migration between ERP systems is low,

in a first aspect, an embodiment of the present application provides a method for data migration between ERP systems, including:

setting data fields for exporting the ERP system and importing the ERP system;

setting a logical relation between the data fields of the export ERP system and the import ERP system and forming an import attribute library;

and extracting the table data exported from the ERP system, and migrating the table data to the imported ERP system according to the imported attribute library.

In some embodiments, the data migration method further comprises: and checking the data migrated to the imported ERP system.

In some of these embodiments, the logical relationship includes an equal relationship, and/or a merge relationship.

In some embodiments, when the logical relationship is an equal relationship, the import attribute library is constructed according to data fields of the export ERP system.

In some embodiments, when the logical relationship is a merge relationship, the data fields of the exported ERP system are merged to construct the imported attribute library.

In some embodiments, the step of checking the data migrated to the ERP system includes: checking whether all data fields are successfully matched, and if so, successfully importing; if not, the import fails, and the import attribute library is modified and set.

In a second aspect, an embodiment of the present application provides a data migration system between ERP systems, which is suitable for any one of the above data migration methods between ERP systems, and includes:

the data field setting unit is used for setting data fields exported from the ERP system and imported into the ERP system;

an import attribute library obtaining unit, which sets the logical relationship between the data fields of the export ERP system and the import ERP system and forms an import attribute library;

and the data migration unit extracts the table data exported from the ERP system and migrates the table data to the imported ERP system according to the imported attribute library.

In some of these embodiments, the data migration system further comprises: and the checking unit is used for checking the data migrated to the imported ERP system.

In a third aspect, an embodiment of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor, when executing the computer program, implements the method for data migration between ERP systems according to the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for data migration between ERP systems as described in the first aspect above.

Compared with the prior art, the invention has the advantages and positive effects that:

1. according to the invention, the import attribute library of each functional module is formed by setting the field relation of the ERP system database, and the import of the table data is directly carried out according to the setting of the attribute library without manual operation, so that the data migration between the new system and the old system is efficiently and quickly realized.

2. Different data field relations are set according to needs, different import attribute libraries are created for different functional modules, and flexibility and variability in data migration operation are improved.

3. And (4) checking the data transferred to the imported ERP system, and checking whether all the fields are successfully matched, so that the accuracy of data transfer is ensured by carrying out complete matching check.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a flowchart of a method for data migration between ERP systems according to an embodiment of the present application;

FIG. 2 is a block diagram of a system for data migration between ERP systems according to an embodiment of the present application;

FIG. 3 is a block diagram of a computer device according to an embodiment of the present application.

Wherein the reference numerals are:

81. a processor; 82. a memory; 83. a communication interface; 80. a bus.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments provided in the present application without any inventive step are within the scope of protection of the present application.

It is obvious that the drawings in the following description are only examples or embodiments of the present application, and that it is also possible for a person skilled in the art to apply the present application to other similar contexts on the basis of these drawings without inventive effort. Moreover, it should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of ordinary skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.

Unless defined otherwise, technical or scientific terms referred to herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this application belongs. Reference to "a," "an," "the," and similar words throughout this application are not to be construed as limiting in number, and may refer to the singular or the plural. The present application is directed to the use of the terms "including," "comprising," "having," and any variations thereof, which are intended to cover non-exclusive inclusions; for example, a process, method, system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to the listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Reference to "connected," "coupled," and the like in this application is not intended to be limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as referred to herein means two or more. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, for example, "A and/or B" may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Reference herein to the terms "first," "second," "third," and the like, are merely to distinguish similar objects and do not denote a particular ordering for the objects.

The present invention is described in detail with reference to the embodiments shown in the drawings, but it should be understood that these embodiments are not intended to limit the present invention, and those skilled in the art should understand that functional, methodological, or structural equivalents or substitutions made by these embodiments are within the scope of the present invention.

Before describing in detail the various embodiments of the present invention, the core inventive concepts of the present invention are summarized and described in detail by the following several embodiments.

The technical scheme is used for data migration between ERP systems, and comprises the steps of setting data fields of the systems and logic relations among the data fields, forming an import attribute library, and performing data migration according to the import attribute library. The problems of complex technical means, high cost and low efficiency in the ERP data migration process are solved, manpower and material resources are saved, and the working efficiency is improved.

The first embodiment is as follows:

referring to fig. 1, this example discloses a specific implementation of a data migration method (hereinafter referred to as "method") between ERP systems.

Specifically, the method disclosed in this embodiment mainly includes the following steps:

and step S1, setting data fields of the export ERP system and the import ERP system.

Specifically, the fields for importing the ERP system function modules include x1, x2, x3 and x4... xn, and the fields for exporting the database of the ERP system include y1, y2, y3 and y4... yn.

Then, step S2 is executed to set the logical relationship between the data fields of the exported ERP system and the imported ERP system and form an imported attribute library.

Specifically, the logical relationship includes an equal relationship and/or a merge relationship, when the logical relationship is the equal relationship, that is, x1 is x2, an import attribute library is constructed according to the data fields of the exported ERP system, and when the logical relationship is the merge relationship, that is, x1 is y1+ y2 or x1+ x2 is y1, the data fields of the exported ERP system are merged to construct the import attribute library.

Then, step S3 is executed to extract tabular data of the export ERP system, and migrate the tabular data to the import ERP system according to the import attribute library.

Specifically, the corresponding function module of the imported ERP system is clicked for importing, and the table data exported from the ERP system is imported into the corresponding function module according to the import attribute library.

Finally, step S4 is executed to check the data migrated to the ERP system.

Specifically, complete matching verification is carried out on all data fields of the function module of the exported ERP system, whether all the data fields are successfully matched or not is checked, and if yes, all the fields are successfully matched, the importing is successful; if not, the import fails, and the unmatched fields are modified and imported again.

Example two:

with reference to the data migration method between ERP systems disclosed in the first embodiment, this embodiment discloses a specific implementation example of a data migration system (hereinafter referred to as "system") between ERP systems.

Referring to fig. 2, the system includes:

the import attribute library obtaining unit is used for setting a logical relation between data fields of an export ERP system and an import ERP system and forming an import attribute library;

And the checking unit is used for checking the data migrated to the ERP system.

In some embodiments, the data field setting unit selects the corresponding function module to set the field of the imported ERP system module, and also sets the field of the data exported from the ERP system, for example, the field of the imported ERP system function module may be x1, x2, x3, x4... xn, and the field of the database exported from the ERP system may be y1, y2, y3, y4... yn.

In some embodiments, the import attribute library obtaining unit completes setting of a logical relationship and building of an import attribute library, where the logical relationship includes an equal relationship and/or a merge relationship, when the logical relationship is the equal relationship, that is, x 1-x 2, the import attribute library is built according to data fields of the export ERP system, and when the logical relationship is the merge relationship, that is, x 1-y 1+ y2 or x1+ x 2-y 1, the data fields of the export ERP system are merged to build the import attribute library.

In some embodiments, after the data migration unit performs the import operation, the table data exported from the ERP system is imported into the corresponding functional module according to the import attribute library.

In some embodiments, the checking unit performs complete matching check on all data fields of the function module of the exported ERP system, checks whether all the data fields are successfully matched, and if yes, successfully matches all the fields, then successfully imports the data fields; if not, the import fails, and the unmatched fields are modified and imported again.

Please refer to the description of the first embodiment, which will not be repeated herein.

Example three:

referring to FIG. 3, the embodiment discloses an embodiment of a computer device. The computer device may comprise a processor 81 and a memory 82 in which computer program instructions are stored.

Specifically, the processor 81 may include a Central Processing Unit (CPU), or A Specific Integrated Circuit (ASIC), or may be configured to implement one or more Integrated circuits of the embodiments of the present Application.

Memory 82 may include, among other things, mass storage for data or instructions. By way of example, and not limitation, memory 82 may include a Hard Disk Drive (Hard Disk Drive, abbreviated to HDD), a floppy Disk Drive, a Solid State Drive (SSD), flash memory, an optical Disk, a magneto-optical Disk, tape, or a Universal Serial Bus (USB) Drive or a combination of two or more of these. Memory 82 may include removable or non-removable (or fixed) media, where appropriate. The memory 82 may be internal or external to the data processing apparatus, where appropriate. In a particular embodiment, the memory 82 is a Non-Volatile (Non-Volatile) memory. In particular embodiments, Memory 82 includes Read-Only Memory (ROM) and Random Access Memory (RAM). The ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically Erasable PROM (EEPROM), Electrically rewritable ROM (EAROM), or FLASH Memory (FLASH), or a combination of two or more of these, where appropriate. The RAM may be a Static Random-Access Memory (SRAM) or a Dynamic Random-Access Memory (DRAM), where the DRAM may be a Fast Page Mode Dynamic Random-Access Memory (FPMDRAM), an Extended data output Dynamic Random-Access Memory (EDODRAM), a Synchronous Dynamic Random-Access Memory (SDRAM), and the like.

The memory 82 may be used to store or cache various data files for processing and/or communication use, as well as possible computer program instructions executed by the processor 81.

The processor 81 reads and executes the computer program instructions stored in the memory 82 to implement any one of the ERP inter-system data migration methods in the above embodiments.

In some of these embodiments, the computer device may also include a communication interface 83 and a bus 80. As shown in fig. 3, the processor 81, the memory 82, and the communication interface 83 are connected via the bus 80 to complete communication therebetween.

The communication interface 83 is used for implementing communication between modules, devices, units and/or equipment in the embodiment of the present application. The communication port 83 may also be implemented with other components such as: the data communication is carried out among external equipment, image/data acquisition equipment, a database, external storage, an image/data processing workstation and the like.

Bus 80 includes hardware, software, or both to couple the components of the computer device to each other. Bus 80 includes, but is not limited to, at least one of the following: data Bus (Data Bus), Address Bus (Address Bus), Control Bus (Control Bus), Expansion Bus (Expansion Bus), and Local Bus (Local Bus). By way of example, and not limitation, Bus 80 may include an Accelerated Graphics Port (AGP) or other Graphics Bus, an Enhanced Industry Standard Architecture (EISA) Bus, a Front-Side Bus (FSB), a Hyper Transport (HT) Interconnect, an ISA (ISA) Bus, an InfiniBand (InfiniBand) Interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a microchannel Architecture (MCA) Bus, a PCI (Peripheral Component Interconnect) Bus, a PCI-Express (PCI-X) Bus, a Serial Advanced Technology Attachment (SATA) Bus, a Video Electronics Bus (audio Electronics Association), abbreviated VLB) bus or other suitable bus or a combination of two or more of these. Bus 80 may include one or more buses, where appropriate. Although specific buses are described and shown in the embodiments of the application, any suitable buses or interconnects are contemplated by the application.

In addition, in combination with the inter-ERP system data migration method in the foregoing embodiment, an embodiment of the present application may provide a computer-readable storage medium to implement. The computer readable storage medium having stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement any of the above-described embodiments of the inter-ERP system data migration methods.

The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method for data migration between ERP systems is characterized by comprising the following steps:

setting data fields for exporting the ERP system and importing the ERP system;

2. The data migration method of claim 1, comprising:

and checking the data migrated to the imported ERP system.

3. The data migration method of claim 1, wherein the logical relationship comprises an equal relationship, and/or a merge relationship.

4. The data migration method of claim 3, wherein when the logical relationship is an equal relationship, the import attribute library is built according to data fields of the export ERP system.

5. The data migration method according to claim 3 or 4, wherein when the logical relationship is a merge relationship, the data fields of the exported ERP system are merged to construct the imported attribute library.

6. The data migration method according to claim 2, wherein the step of checking the data migrated to the imported ERP system includes: checking whether all data fields are successfully matched, and if so, successfully importing; if not, the import fails, and the import attribute library is modified and set.

7. A system for data migration between ERP systems, comprising:

8. The data migration system of claim 7, comprising:

and the checking unit is used for checking the data migrated to the imported ERP system.

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the data migration method of any one of claims 1 to 6 when executing the computer program.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the data migration method according to any one of claims 1 to 6.