cutover

[Former Member]

Hi,

In my last interview i was asked how data was uploaded and was update till date to go live.. and when cutover strategy was implemented. Is it during realization phase.

Thanks

[Former Member · Accepted solution]

hi

the cut over plans will be taken into consideration in the business blue print process

AS IS: here the client requirement are taken

TO BE : the client requirement or process can be designed with help of a flow chart.

here if we cannot map the process in SAP then we redetermine the process with different functionalities.

the upload of the data will be done in the final preparation

thanks and regrds

K.GopalKrsihna

[Former Member]

Hi Hemant,

<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.

Check these links for few more important and Frequently asked SD Interview Questions and I hope these may help you a lot to shape yourself for an Interview

http://www.sap-img.com/sap-sd/short-sap-sd-questions-1.htm

http://www.sap-img.com/sap-sd/short-sap-sd-questions-2.htm

http://www.sap-img.com/sap-sd/short-sap-sd-questions-3.htm

ALL THE BEST

Thanks,

Vinay

[Former Member]

thanks for the replies sadhu and vinay. so cutover strategy primarily deals loading of data into sap. I have one more question then, where is the data loaded to, is it to a dev server and to quality and to production.

Thanks all .

Hemant

[Former Member]

Hi hemant,

yes, cutover strategy is used to make sure all the required is in the production when we go live. Because of this it i done just before go live date. The businees is freezed or the data is all managed in a differnet file and that is also finally included into the sap system. But somewhere a line has to be drawn to say, this dat am puting in sap. The data is loaded into production server.

Hope it helps. Please reward if useful.

Thanks & Regards

Sadhu Kishore

[Former Member]

Hi,

I have a question while on this topic. Kishore, you mentioned that:

<i>The stock data as on the date of going live should be correctly entered.</i>

You also mentioned:

<i>The stock data as on the date of going live should be correctly entered.</i>

Can you elaborate on what exactly happens on the first day of g-live with respect to data loading.

My assumption was: Both Master and Transaction-data will be loaded into the Production System before the go-live date. From the go-live date onwards, users come and enter all sorts of SOs and POs in the system.

Do you mean to say that Master data is loaded in production before go-live date while Transaction-sdata is loaded into productionfrom the date of going-live.

Thanks

[Former Member]

Hi,

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.

Hope it helps. Please reward if useful.

Thanks & Regards

Sadhu Kishore