Skip to Content
avatar image
Former Member

cut over stratgey

plz tell me what is the cut over stratgey ....and systm land scap

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    Jan 09, 2008 at 07:28 AM

    Cutover strategy.

    Cutover strategy or Cutover plan is the activity done in ASAP methodology, while transfering the data from the lagacy system to the sap system.At this point of time the billing will be stopped,all the open orders, contracts, pricing data will be transfered as per the cutover plan which is provided by the implementation partner. what ever you want to do on the system u need to do before or after this activity.

    System Land Scape

    http://help.sap.com/saphelp_nw04/helpdata/en/fe/39ae3d47afd652e10000000a114084/content.htm

    http://http://blogs.ittoolbox.com/sap/kehinde/archives/understanding-the-sap-system-landscape-14030

    Reward Points if useful.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 09, 2008 at 07:45 AM

    Following are the activities taken during cutover. I think you know that cutover is the period before Go live. During this period the system will be disabled for use by anybody.

    Cut over activities

    1. Business will be stopped during the cutover period

    2. Before starting migration, the org structures and baseline configuration in the system will be checked once. Also the loader sheets will be checked once for the consistency of data and mapping of organisational structure with the loader sheet org structures.

    2. Migration of the transactions which happened in the legacy/old system will happen as per the migration strategy

    3. Any Ztables, Ztcodes created/already available in the system will be checked for the consistency.

    4. Once migration is over, the quality of migrated orders, invoices etc will be checked.

    5. After all these activities, the system will be left open for some users to execute some new transactions in the systems.

    6. On confirmation, the system will be Rolled out to the users

    A holistic strategy will be put for executing these cutover activities by the combined efforts of Consultants, Core team members from the client, some core users etc.

    System landscape refers to the interfaces, the architecture of transport movement etc which can impact your system. It is represented diagrammatically.

    Hope this helps.

    Reward if this helps.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 09, 2008 at 07:52 AM

    Hi Gaurav,

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

    Cut over 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 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 atleast managable position to work on production server. Preparation of user manual. All go-live preparatory activities.

    cut-over-activities

    cut-over-planning

    cut-over-strategy

    Follow the Links For More Info..

    Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD.

    DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.

    QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training.

    PROD may have something like a 200 Production.

    These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.

    Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).

    You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.

    But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.

    The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.

    In summary:

    Landscape : is the arrangement for the servers

    IDES : is purely for education purpose and is NOT INCLUDED in the landscape.

    DEVELOPMENT ---> QUALITY -


    > PRODUCTION

    DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.

    QUALITY : is where the core team members and other members test the customization.

    PRODUCTION : is where the live data of the company is recorded.

    A request will flow from Dev->Qual->Prod and not backwards.

    1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process.

    2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.

    3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new develpoment is done is development client and the request is transported to production.

    These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.

    Presentaion Server- Where SAP GUI have.

    Application Server - Where SAP Installed.

    Database Server - Where Database installed.

    Reward If Helpful..

    Regards..

    Praveen Kumar.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 09, 2008 at 08:02 AM

    hi,

    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.

    Here you can also refer to the Data Transfer Made Easy Guidebook created especially for this purpose. It is located in the Knowledge Corner of the ASAP CD.

    The help desk is particularly important in the first weeks after going live, but you will require help desk support throughout the productive life of your R/3 System. An internal help desk should be staffed and supported mainly by employees of the enterprise. Setting up a help desk involves, among other things, installing office and technical equipment and defining OSS users. Problems which cannot be solved by this internal help desk are forwarded to SAP via the OSS system.

    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.

    regards,

    Arun prasad

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 10, 2008 at 05:31 PM

    thanks

    Add comment
    10|10000 characters needed characters exceeded