cancel
Showing results for 
Search instead for 
Did you mean: 

cutover streatagy

Former Member
0 Kudos

hi gurus,

I am working in implementation, what is the cutoverstreatagy and plans. pls tell something about.

Regards,

koti

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi rao,

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.

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.

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.

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 August 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 August 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 August 1st to back dates) and chalk out a plan of action for updating all the necessay information into the SAP system so that by August 1st Golive is done.

Award points if it adds information.

Thanks

Mohan

Answers (1)

Answers (1)

former_member227476
Active Contributor
0 Kudos

dear rao

cutover

Cutover Activities

Communication to Vendor, Customer and Excise etc

User Training by Core Team

Cost Roll ups and Validations – Test

Upload of Master Data in Sequence on Test

Start entry of Open Sales Orders, Quotation, Enquiries, Purchase Orders in Prod

Stock Taking Activity at Plant

Stock Upload with SAP Material Code, Qty, Value and Storage Location as on xx.xx.xxxx on Prod

Enter Cash Balances as of xx.xx.xxxx

Enter Excise balances as of xx.xx.xxx with monthly duty payment for March

Configure Cut off Excise Number Range (Excise Invoice, RG registers) as on xx.xx.xxxx

Back up of Loaded Production Server

Go Live

Availability of all balances

FI Balance uploads (For both ledgers/ subledgers/ assets/ customers/ vendors)

If Sales Order is Open, we require to foreclose the Sales Order & also ensure that there is no open deliveries. Incase if there is any open deliveries, they should either comple the process upto Billing & creating accounting Document or the Deliveries should be cancelled. Similarly if there are any Billing document not passed to accounting, it should be ensured that they are passed to accounting.

In the New System, if transaction are small in number then sales sales order should be created manually & if the volume is high through LSMW.

The Duration of Cut-Over is arounf 15 - 20 days ideally

rewards if it helps

siva

Former Member
0 Kudos

Cut over strategy means,at the end of implementing project,the time takes to replace the existing system with SAP is called Cut over strategy.

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.

as example , in simple words for MDM(master data maintenance) it means that after cutover - all data will be used of MDM and not legacy systems . for central master data scnerio ; Data before cutover date will be maintained in all systems and after cutover date , it will be maintained in MDM only .

Data can be uploaded using BDC programs, LSMW for master data and CATT is also being used.

-Prashant