BW Go-live cutover plan

Hi All,
Our BW system is supposed to golive along with the SAP R/3 golive date. We have to do cutover plan for this. Is there any standard template or documents on this? Please help me out.
Thanks & regards,
Vaskar

Dear Sujan,
check the below link for GO live strategy.
http://www.saptechies.com/sap-pdf-books-download/SAP_Go_live_strategy11248141773.pdf
Search the Google for BBP Document quastions.
Regards,
Kishore K
Edited by: kishore babu on Dec 22, 2009 8:21 AM

Similar Messages

  • Cutover plan on Project systems

    Hi Friends
    Can any one help me to prepare Project systems cutover plan, if you have any cutover plan on Project systems could you please pass me to
    harikrishna underscore sd at yahoo dot com
    Our requirement is we are going to stop the existing client and we are creating a new client and will continue with the same. So how we should update the projects of various stages in the new client and how to close in the existing client.
    Regards,
    Hari

    Hi,
    Plz refer this links it may help u.
    http://sapdocs.info/2008/09/22/sap-go-live-strategy/
    CUTOVER
    http://www.sap-img.com/sap-implementation.htm
    Cutovers
    Different types of testing in a SAP Implementation project
    Regards
    Chandra

  • PI cutover plan

    Hello sdn
    What activities need to be part of PI cutover plan ?
    Please advise.
    Thank you.

    Hi,
    It completely depends on the project you are working on.
    But roughly, it should have to have all the activities including sender and receiver application systems & PI would be carrying out before Go-Live.
    It should have all the steps in correct sequence with the correct date and time that would be taking place by Sender/Receiver applications and PI.
    Example: Master data upload activity in case of Idoc scenarios.
    -Supriya.

  • Cutover planning strategy doc

    Does anybody have Cutover Planning/Strategy document for PI/XI? I do have the ASAP standard.. but I feel there must be one with lot of good information.. please send it to my  gsvas81at gmail dot com

    Hi,
    We restricted from NEUPL................
    When i have gone thru entire process my findings for this problem is as follows
    1) When A planning strategy is changed in a plant?plants the existing/Pending PIRs need to closed or deleted. If there are any PIRs pending the system can not select new req Type automatically.
    2) All the Depending requirements schedule lines and purchase orders for existing PIRs need to be closed before going to new Planning Strategy
    If the user follows this procedure then the system will automatically uses  "Control of Requirements Type Determination " and a required "Req Type" populates in user parameters. otherwise there will be planning inconsistency
    Please correct me if i am wrong
    Pavan

  • Cutover Plan SAP GRC AC

    Hi all,
    I´m interested in getting some templates for planning and describe a detailed Cutover Plan for SAP GRC Access Control, which includes all activities for performing in each one of the modules for SAP GRC (RAR, ERM, CUP and SPM).
    Anybody has some template or related information for prepare cutover plan for SAP GRC AC?
    Thanks in advance,
    Santiago

    Hi Santiago,
    here you could find a AC5.3 Project Plan:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b00a372f-ddb7-2b10-88aa-d6eaae69a756
    And this is the Pre-Installation Checklist:
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50692df1-67da-2b10-2995-84a0d0c82193
    Best,
    Frank

  • Data migration cutover plan

    Hi please help on how to create cutover plan for data migration, and what are the tasks and what are the activeites , if any one having please send the cutover plan.

    Hi,
    In most of the cases the templates required to upload master/operative data are provided by the client. However if your requirement is such that you need to create new templates please refer SDN Wiki as mentioned in the previous post or you can also search Google. You will find a lot of inputs that may help you.
    Regards,
    Gokul

  • Cutover plan

    We have few sales orders with future delivery dates in production system. We are implementing customer collaboration with SNC5.1.
    There are few OPEN SALE  orders in R/3. We want to plan for cutover so how we should plan this.
    Details approach will be appreciated.
    Regards,
    Vaibhav

    you can recreate the orders in SNC, once you have your production system setup with all masterdata and customizing, and PI is up and running, you can send all orders to SNC, and they will be re-created by the Replenishment order confirmation XML interface.

  • Implementatiion cutover plan

    Hi guys,
    Please tell me, what is the implementation cutover pan, creating training plans and deliver training.

    Now my question is if i move development into the production what happens to the delta that is being loaded since the extractor is enhanced ?
    when you moved to BWQ what happend to the data , did it got over write or it stayed in the cube? my recommendation to be on the safe side create new cubes, keep the same values and you can copy the queries as well, transport it to bwp and have dtp load n to new cube frld cube.
    if i want to load the data into global cubes only last 3 years data how can i do that ?
    you can filter in infopcakge to load only last 3 years if you have a field for fiscal or calender year.
    Can i do a repair full load into new cube . will that work.Will it fetch the data required without disturbing the deltas.
    no you cannot

  • What are the front to backend steps for redeploying a live EPMA Planning ap

    Hello All,
    Can anyone outline considerations/steps for redeploying an EPMA Planning application in a live environment? Do users have to be logged off of the system? Does the Planning app have to be put into Administration mode? Does the Planning Essbase DB have to be put into standby mode or users logged out of it first? Do I have to restart Planning afterward? Thank you in advance for any information that you can provide.

    Hello John,
    Thank you very much for your quick response. We currently try to do this after hours but it seems invariably that there were some users still in or had some processes running that seemingly hang when we try to redeploy EPMA/Planning (the users are not able to log back in after the EPMA Planning re-deployment). Is there a sure fire way to ensure that users are out of the system before redeploying so that this doesn't happen? Please advise, thank you sir.
    Edited by: 859885 on May 18, 2011 2:51 PM

  • Cutover plan for BI 7 security upgrade

    We  are in the process of cutting over to prod.. Is there a specific list of things which needs to be done during cutover..Any inputs will be appreciated!

    Cut Over Activity
    https://forums.sdn.sap.com/click.jspa?searchID=13649826&messageID=1240557

  • Cutover stratergy

    Hi all
    let me know what is the CUTOVER STRATEGY?
    Which strategy used for PP module?
    Thanks in advance
    Sriram

    dear sriram,
            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. 
    Hope this helps...Reward your points if it is useful
                                                                              -gide

  • Regarding cutover strategy!!!!

    what are the steps involved in the cut over stratey? please explain

    2.What is 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.
    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.
    The final phase before going live with SAP is often referred to as the cutover phase, which is the process of transitioning from one system to a new one. The organization needs to plan, prepare and execute the cutover, by creating a cutover plan that describes all cutover tasks that have to be performed before the actual go-live. Examples of cutover tasks are:
    Review and update all systems-related operations procedures like backup policies and system monitoring
    Assign ownership of SAP’s functional processes to individuals
    Let SAP AG do a Going Live check, to get their blessing to go live with the system
    Lock down the system, i.e. do not make any more changes to the SAP system
    Cut-Over Activities:
    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.
    Open Client activity:
    The activity or configuration to be done in production server, by opening an client should be ensured that it is done before go-live.
    Cutover Activities
    At the end of Phase 4, it is necessary to refine and validate the 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.

  • Live Scenario Please Reply ASAP

    Dear Gurus
    There is a live scenario. As you all must be knowing that the exchange rate changes every day.
    I will explain the whole scenario.
    The sales order was prepared on an exchange rate of Rs 46 for one Dollar. But when i am billling the exchage rate has changed to Rs 48 for one Dollar. How can it be changed automatically with out updation in the T Code 0B08 i.e. T Curr
    Please guide and any further clarifications please revert back
    Satish Kullu

    Five Phases of ASAP methodlogy.
    Phase 1: Project Preparation - The purpose of this phase is to provide initial planning and preparation for your SAP project.
    Phase 2: Business Blueprint - The purpose of this phase is to achieve a common understanding of how the company intends to run its business within the SAP System. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops. The Business Blueprint document represents the business process requirements of the company. It is the agreed statement of how the company intends to run its business within the SAP System.
    Phase 3: Realization - The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: Baseline (major scope); and Final configuration (remaining scope).
    Phase 4: Final Preparation - The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.
    Phase 5: Go Live & Support - The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation.
    Additionally:
    Some additional Infomation on ASAP methodology:
    Phase 1 - Project Preparation
    Change Charter - Goals and objectives of Organizational Change Management
    Project Plan - This is a first cut focusing on milestones and Work Packages; details to come.
    Scope - Sets the initial definition of the project; input from sales cycle.
    Project Team Organization - Sets the who of the project: Standards & Procedures - Sets the why and how of the project.
    Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb and is the key document for Phase 3.
    Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing & documentation. Planning - Defines how the configuration will be done and how it will be tested. Development Programs - Provides details of the external programming requirements. EU Training Material - End User training material and process documentation.
    Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s capabilities
    Cutover Plan - The details of how to move to the production environment and go live
    Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going live
    Phase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.
    Reward points if helpful.
    Regards,
    Rajesh Banka

  • Cutover phase - various activities

    Hi Gurus,
    I want to know in details about the various activities in cutover phase, terms like War Rooms, Dress Rehearsal, Ground Support, etc. A detailed explaination will be very helpful.
    Thanks,
    Kumar

    Here are a few:
    A War Room is the room that the Cutover/Mogration team reside in and use for meetings. This is also where you will hang your schedule, plan and any other relevant burndown type charts.
    Dress Rehersal is a trial run of the migration and usually takes place on an environment that is being released first. Usually Dev, QA, SI, Pre-Prod and then Prod (before it becomes the live Prod)
    Ground Support will be the Basis team and all the rest like Super Users, Data Migration team, CoE, and any third party support team like Logica offshore, Accenture or Wipro. These will no doubt have some sort of support role. They will more than likely be taking over the live/BAU support of your system.
    Go/No Go usually a few days before the weekend, after the Dress Rehersals, to decide whether or not the system is ready for the actual Live cutover.
    Contingency Plan - The Cutover Plan must include a contingency plan for delays. The contingency plan must address how long (in hours or days) the new production system cutover can progress but be stopped, and legacy systems restored. It is standard practice to have a point of no return for making the new system operative. After a few hours or days, it may not be possible to convert the business operations back to the legacy system. However, it is important to consider this option.

  • Cutover Strategy

    Hello all,
    Can any body explain me about cutover strategy,
    the scenario is my client is paying full advance payment against PO  and but recived half material so PO is open . How we can expalin to client to prepare cutover plan startegy to prepare cutover data.
    Suggest.

    Hi ,
    Cutover strategy in SAP implementation or any other implementation is client specific . It depends on organisation data load strategies .
    as example , in simple words for MDM 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 .
    Hope this clarfies your Query .
    -Annika .

Maybe you are looking for