on 05-21-2007 2:25 PM
HI THIS IS SURESH
CAN ANYBODY EXPLAIN ME ABOUT CUTOVER STRATEGY?
ADVANCED THANKS FOR ALL SAP GURUS
WITH REGARDS
SURESH
Hi Suresh
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, you go-live 100% or partial again depending upon organizational setup and policies.
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.
Rewards if it helps....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suresh,
Cutover Strategy is the plan of action of updating all the process transactions into SAP before GOLIVE.
Let me explain you in this way... suppose the GOLIVE date of an SAP project is June 1st. And the Compnay might be using some legacy system prior to this implementation. So all the transactions, master datas, G/L accout information, material stock uploading etc should be updated into sap so that there will be smooth GOLIVE on JUNE 1st. And there is also a gap between the SAP implementation and stop using of Legacy system. So all the transactions done in this gap also should be updated into SAP system.
So they come in backward process (Like june 1st to back dates) and chalk out a plan of action for updating all the necessay information into the SAP system so that by June 1st Golive is done.
Hope this will give some idea about Cutover Strategy.
Reward if helpful.
Thanks,
praveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suresh,
<b>Cutover strategy:</b> 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, you go-live 100% or partial again depending upon organizational setup and policies.
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.
Thanks,
Vinay
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Cutover strategy is used for uploading the master data in the production system from the legacy system before Golive of the project.
Master data includes Customer master,Material master,Condition master.
Exsisting transaction which are present in the legacy system which needs to be processed in SAP system,those needs to be maintained in SAP.
Material stock needs to be uploaded.
Here we basicaly fixed the date upto which the data has to be uploaded.After cutover date no data will be updated in SAP till Golive.
Reward points if useful
Regards,
Amrish Purohit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.