cutover activities

[Former Member]

what r cutover activities

what cutover activities we do before going to go live step wise

[Former Member · Accepted solution]

Hiii Mahesh cutover strategy is nothing but the last step before shifting from legacy system to SAP. The following activities are carried out in cutover strategy.r

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.

As soon as you know when you will go live with the R/3 System or with new R/3 applications you should inform SAP. Thus you can ensure that SAP can provide optimal support throughout your going-live phase. For the last weeks before and first weeks after the go-live date, SAP offers the R/3 GoingLive Customer Care Service, accessible via SAPNet and OSS.

[Former Member · Accepted solution]

hi jay

for every question that i posted u r giving me appropriate answers. thanks for that.

and i think i know u. can u please reply to mail id kumar.configured@gmail.com

[Former Member]

Generally Cutover strategies r using before golive

that is we upload the data from non R/3 to SAP

in this we use the cutoverstrategies

just we divide(cut) the data depends on the modules

like main imp data is HR and FI

first we upload these related data

then we upload the other modules related data likeMM SD PP

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