Cutover strategy is a planing ,How data load will be perform in production client before Go Live !
Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data load
Cutover strategy depends upon how the organizations design their data load strategies
There are several way to perform cut over activity.
Go-live 100% or partial again depending upon organizational setup, policies & data volume.
Lets look in to this ...
Cut-Over Activities:
Cutover Plan - The details of how to move to the production environment and go live. Ensuring that all master data to be loaded to production server is ready & in correct format. User training is conducted & user is in a comfort or at least manageable position to work on production server. Preparation of user manual. All go-live preparatory activities.
Open Client activity: The activity or configuration to be done in production server, by opening an client should be ensured that it is done before go-live. We must request to Basis team for opening production client for certain periods once .On that time all user will block by basis team & system will not accessable .Cutover activity finished Basis will be close production client
Cutover Activities At the end of Phase 4, it is necessary to refine and validate the cutover plans generated in the Realization phase. Among other things, this includes tasks such as the reviewing of the runtime of test runs to estimate runtime for the complete data size. A conversion checklist for transporting all changes into the productive system is provided for all the configuration settings to be imported. At this stage, it is important to verify that required tasks have been successfully completed, for example, that the technical environment is in place, the cutover programs are ready and the application data is verified. Approval is now sought from project management and company senior management to start the cutover process.
Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data load
Cutover strategy depends upon how the organizations design their data load strategies
There are several way to perform cut over activity.
Go-live 100% or partial again depending upon organizational setup, policies & data volume.
Lets look in to this ...
Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads,
Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds. The final phase before going live with SAP is often referred to as the cutover phase, which is the process of transitioning from one system to a new one. The organization needs to plan, prepare and execute the cutover, by creating a cutover plan that describes all cutover tasks that have to be performed before the actual go-live. Examples of cutover tasks are: Review and update all systems-related operations procedures like backup policies and system monitoring Assign ownership of SAP’s functional processes to individuals Let SAP AG do a Going Live check, to get their blessing to go live with the system Lock down the system, i.e. do not make any more changes to the SAP system
Cut-Over Activities:
Cutover Plan - The details of how to move to the production environment and go live. Ensuring that all master data to be loaded to production server is ready & in correct format. User training is conducted & user is in a comfort or at least manageable position to work on production server. Preparation of user manual. All go-live preparatory activities.
Open Client activity: The activity or configuration to be done in production server, by opening an client should be ensured that it is done before go-live. We must request to Basis team for opening production client for certain periods once .On that time all user will block by basis team & system will not accessable .Cutover activity finished Basis will be close production client
Cutover Activities At the end of Phase 4, it is necessary to refine and validate the cutover plans generated in the Realization phase. Among other things, this includes tasks such as the reviewing of the runtime of test runs to estimate runtime for the complete data size. A conversion checklist for transporting all changes into the productive system is provided for all the configuration settings to be imported. At this stage, it is important to verify that required tasks have been successfully completed, for example, that the technical environment is in place, the cutover programs are ready and the application data is verified. Approval is now sought from project management and company senior management to start the cutover process.
