Analysis of historical data migration between SAP and erpv1.0

* After the launch of erpv2.0, you are faced with an urgent problem-migrate data from the original SAP system and erpv1.0 to erpv2.0 for full-text search. The data storage and display modes of erpv1.0 are the same as those of erpv2.0. The difference lies in the data storage location. Therefore, the migration of this part of data focuses on the two parts of data (1.0 and 2.0) full-text retrieval is integrated, while SAP application data is scattered in dB instead of filenet, and the field information displayed is also significantly different from erpv1.0 and 2.0, therefore, the migration of this part of data focuses on the analysis of migration data and data import.

Priority

Customers have priorities for different needs. The SAP system is many years earlier than the erp1.0 system. Therefore, when data in erp1.0 is used in 2.0, the customer must at least complete the full-text search. Therefore, the priority of 1.0 is higher than that of SAP.

Ease the customer's demand for multiple parties on the premise that the priority can be determined

Data migration seems to be one thing. There are two to three things, and the customer wants the data of the two systems to be migrated to 2.0 as soon as possible. However, due to the pressure on the project team resources, developers cannot complete multiple tasks within the workload of one task. The key to the problem is to understand what the customer needs and understand how to do these things. The result of this operation is to migrate 1.0 of the data first, but at the same time, an SAP system migration statement is provided, it is used to guide customers in what they can do for SAP system data migration during the 1.0 data migration period, that is, to guide customers to prepare basic data in the format required for 2.0.

Analyze the relationship between sub-tasks of one thing

Before proposing the above solution with the customer, the project team needs to analyze the feasibility of this (or multiple) solution: Is it really helpful to solve the problem and will it bring additional work, can a series of problems produced by decomposition be solved by each other (or unilaterally. Although these three projects were not developed by the Team, the problem was basically a technical and time problem. After some logic analysis and code debugging and tracking, it was concluded that, in fact, the data of the SAP system and the erp1.0 system can be integrated in disguise, that is, as long as 1.0 of the data can be searched in the full text in 2.0, then the data of the SAP system can be searched in full text in 2.0 through this disguised operation, so that only the historical data of SAP is transferred to the 2.0 Environment. This analysis can meet the above-mentioned solutions and provide customers with SAP data migration basic data export instructions to achieve the goal of disguised matching of 1.0 data.

In this way, a more difficult problem can be easily explained to the customer. The subsequent task is to compile the data format specification according to the above analysis and analyze 2.0 of the logic in parallel to achieve full-text retrieval of 1.0 of data in 2.0 applications.