It is a well accepted fact that today the speed of doing business has increased by many folds. Every day with the inclusion of new stakeholder, new node or dimension is being added to the supply chain activities of an organization. Therefore there is a requirement of digitally transformed IT landscape, which can help absorb the load of information, with every added business process.
This should be well backed up by analytical and transactional software capabilities along with high end hardware. Amidst all these, migrating a SAP based database and its associated sub programs, can be of utmost challenging in nature. It is in the scope of the technology partner to choose the right migration methodology, which can address the challenges of big data and the complex SCM processes. It has to be noted here that, during the migration there is “ZERO “data loss.
SAP HANA is specifically made to cater the needs of organizations dealing with huge volume of data generated every second from their supply chain activities. Therefore, it is imperative to follow the following basic steps to ensure a successful data migration program.
Setting the stage
This phase is marked by the team formation activities, which are crucial for the direction of the project. Any successful project kick off is only possible with the declaration of a dedicated technical team, from the organizational side, with a non technical person holding the chair position. This will ensure non biasness towards any department, while formulating departmental process map. It is now for the technology partner to nominate a functional consultant, who would be working in tandem with the organizational chair person, for further development of the project. The role of the functional consultant is to conduct a successful SRS (system requirement study), session with the respective department team.
A good SRS session is the foundation for a successful system design, as the same captures all the nitty gritty of the departmental process flow. It is in this stage, that the system authorizations in the form of locks and user rights are defined. This is also the stage for determining the hardware requirements, for the project, like system RAM, version, proper cable and terminal availability, according to the completed SRS activity. It is also to be noted here, that the addition of various custom built procedures and licensing needs shoots up the cost. This is where SAP HANA is class apart from other system, as the same consolidates various IT resources, and reduces cost.
The beginning of Data Migration
Now there are two way to address this step, one is “on premise implementation”, other being “cloud based”. There are two basic sequences which have to be followed, during the migration procedure. First, the up-gradation of the target system to support SAP HANA and second is the actual process of migration. During the process of migration, to prevent data loss, the storage systems are reconfigured to optimize system performance. It is a standard practice in IT industry, to well complement every step, with proper documentation to avoid any human error. Documentation is useful; as the same helps refer back to the work carried out in past and stage wise payment disbursement to the technology partner.
The migration of the source data base on to the target database is initiated by the locking of the source database. This ensures zero data loss during the transfers, and also allows for the day to day work, to be carried out. To cope up with the data generation speed, it is advisable to use R3load command option, during the import/export procedure. This ensures speed enhancement of the total process, while the work is being carried out in a structured process. However, as per the best practices manual goes, it is always advisable to carry out the migration procedure, in a structured format, which will help in the segregation of the data according to its characteristics based on technical and functional nature. SAP HANA migration provides with the DMO (data base migration option), which is the latest methodology, allowing for system upgrade and migration of database at the same time. To meet the regulatory requirement, it is better to consider the datacenter expansion, which also demands for the system configuration of 1.0 SP9. After the general migration procedure is completed, it is necessary to validate the entire process, for any loop holes. In this process, the locks and the standard procedures are tested with a dummy database for any possible faults.