Complex Cutover Strategy

Hi all,
I would like to seek your help on the issues that I am currently facing.
Company A is currently running SAP ECC6.0. They are about to take over several warehouses Company B, which is also using SAP. I would need to know how to advice them accordingly to ensure a smooth cutover in transitioning these warehouses into Company A's SAP system.
Apart from that, they mentioned that upon go-live/cutover, Company A and Company B will be running SAP in parallel where, PM Activities such as maintenance order will be created in company B's SAP system, but the inventory management which is now owned by Company A, will be performed in Company A's SAP system.
Any Idea how to go about this?
Im thinking that an interface has to be created between both systems to ensure that both systems are updated with the necessary data. Example, PM work order created in Company B, and then the data will be pushed to Company A's SAP system. Then when Inventory management activities are done in Company A, data will be pushed back to company B's SAP system.
Is there another way to go about this?
Any ideas would be much appreciated.

Nazrin,
This scenario we have in our firm up and running. 2 landscapes are integrated through interfaces. and the interfaces are activated through batch jobs which run in specified time.
I docs are exchanged between the system. It is not possible for me to explain deeply here.
but i feel this will be a worst solution because this adds more pressure on support activities.
Best way is to have minimal activity in Company B's SAP System. slowly in a time phased manner, bringing SAP of company B in to Company A and merging both the licenses.
Raghavan

Similar Messages

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 .

Cutover strategy for Cash Management

Hi Gurus,
Please tell me about the cutover strategy for Cash Management??
We are implementing Cash Management in mid year, so how can we take the data in effect which is already posted in the system??
Please revert asap.
Thank You

dear Simmi,
for delta queue check this
https://websmp104.sap-ag.de/~sapidb/011000358700001584392004#17
I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into SAP NetWeaver BI and that no delta is pending. After the client copy, an inconsistency might occur between SAP NetWeaver BI delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name which are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the SAP NetWeaver BI system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in SAP NetWeaver BI when editing or creating an InfoPackage, you should expect that the delta has to be initialized after the copy.

Cutover strategy for BW

BW Gurus,
What is the best cutover strategy for BW. We are planning to do a system copy for go live.
1)What are the points/instructions that need to be completed on the original system before doing a System copy?
2)What are the steps for the Basis?
3)What should be the status of outbound queues on r3/other source systems in the original system?
If the answer is put in points, will be apprecited.
Thanks
Simmi

dear Simmi,
for delta queue check this
https://websmp104.sap-ag.de/~sapidb/011000358700001584392004#17
I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into SAP NetWeaver BI and that no delta is pending. After the client copy, an inconsistency might occur between SAP NetWeaver BI delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name which are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the SAP NetWeaver BI system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in SAP NetWeaver BI when editing or creating an InfoPackage, you should expect that the delta has to be initialized after the copy.

What is ' WORKBENCH' and CUTOVER STRATEGY

hi Gurus
Can any one plese tel me
1 . what is ' WORKBENCH'
Why we use it and when?
2. what is CUTOVER STRATEGY
when we use it and why?
Thanks and Regards
babi

Dear Mr Babisap,
The term 'Workbenc' generally refers to any kind of changes to the standard programmes (objects), beyond the scope of customisation.
To appreciate the full impact, on the SAP Easy Access screen of say R/3 kindly open the menu 'Tools'. The first sub-menu would help in an introduction its scope.
In most companies or organisations implementing or planning to implement any other software system, especially at enterprise wide level, there would be a transition, from the prevalent system to the intended system. Broadly, this process of transition is referred to as 'cutover'.
We could have different possibilities for this transition, normally adopted by a 'steering commitee' establishing (mapping) the equivalence between the two systems.
The preferred mode of change(strategy) would normally qualify to be called a 'Cutover Srrategy'.
Trust I clarify.
Regards,
K Gopidas.

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

Cutover Strategy for CO

Dear All,
Can anyone explain about what are the things need to care in cutover strategy for CO, each compoenent wise, CCA.,PCA, IO.COPC and COPA.
Our client using 4.6 and they aer not using COPC. From ECC 6 COPC is there.
Valuable inputs always highly appriciated.
Thanks and regards.
Sriram.
Moderator: Please, search SDN

dear Simmi,
for delta queue check this
https://websmp104.sap-ag.de/~sapidb/011000358700001584392004#17
I intend to copy the source system, i.e. make a client copy. What will happen with may delta? Should I initialize again after that?
Before you copy a source client or source system, make sure that your deltas have been fetched from the DeltaQueue into SAP NetWeaver BI and that no delta is pending. After the client copy, an inconsistency might occur between SAP NetWeaver BI delta tables and the OLTP delta tables as described in Note 405943. After the client copy, Table ROOSPRMSC will probably be empty in the OLTP since this table is client-independent. After the system copy, the table will contain the entries with the old logical system name which are no longer useful for further delta loading from the new logical system. The delta must be initialized in any case since delta depends on both the SAP NetWeaver BI system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs in SAP NetWeaver BI when editing or creating an InfoPackage, you should expect that the delta has to be initialized after the copy.

Cutover strategy and dates

Hi Friends
Please explain the cutover strategy and dates.
How it will work sin implementation.I have pending 3 planned orders after go live. how can i move these orders to sap system after go live.
Before go live i want 4 planned orders to move to sap system . whati s settings.
Please explain
Thanks
Venkat

Hi ,
Could you please explain more about your production strategies Is it drive through Order or Make to stock ?
You said you have 3 planned orders after Go-live ;
You have all the master data gets Uploaded in the SAP system . So you can create directly Production Order in CO01 / or
or planned order in MD11 , if the requirements are confirmed .
Before Go-live :
You said 4 planned orders to move , here you can also create manual Planned order Using MD11 in sap system
If the requirements are through SO & MTO Production strategies and the sales order drives Production after MRP run
creates planned order automatically.
JayaVimal

CUTOVER STRATEGY (CUTOVER DATA)

HI
When working in the project there is an stage where u have to deside CUTOVER STARTEGY (CUTOVER DATA)
before go live phase can any one expalin what
CUTOVER STARTEGY means in project point of view.
Maximum (Releted Project)..
Manoj.

Hi,
As per my uinderstanding you need to running project to switch in new version. If this is then you consult with customer because the end user is going to use in two phases new & old.
If this is not your query, pls explain in details.
Anil

Cutover Strategy : Customer Service

Dear All,
Am facing problem of deciding data migration strategy from legacy system to SAP for customer service module.
Here am explaining the situation at my project.
My client is manufactures of water purifier systems.It sells and provides services to the customers. It offers to customers Warranty for one year and also AMCs of 1- 5 years.It offers two free service to customers for one year warranty and two free service per one year AMC.They maintain serial numbers for their products. For every service call from customer am using a service notification in SAP, for AMC i am using Service contract.
They have so many active warranties (the warranties given for the past one year ) and active AMCs (the AMCs given for the past five years) and the serial numbers given to those customers in their legacy. So how to collect the data in this case? how would be the data migration strategy?do i have to take all the past active data into the system?if i don't take past data there will not be any reference to create service notifications.Data volume is around 30000 AMCs, 19000 warranties are active at this point of time.
Pls guide me how to proceed in this case.
Thanks in advance,
Kartheek.

http://help.sap.com/saphelp_46c/helpdata/en/3c/abae15413911d1893d0000e8323c4f/frameset.htm
http://www.sap.com/solutions/sam/pdf/BWP_Service_Management.pdf
http://www50.sap.com/businessmaps/3714BAEB0F324C8696F1212B6693F660.htm

PO conversion during cutover (retaining legacy no.)

Hello !
We are planning on manually entering all open POs into SAP at the time of cutover.
One idea that has been floated is to create a special number range that matches the legacy PO numbers... and ensure that the legacy PO number is retained in SAP for POs that are brought over. This would help with communication/receiving etc.
Does anyone see any problems we could encounter with this approach? Is this a common PO cutover strategy?
It seems like a good idea to us, but I am not sure if there is anything we need to be concerned about.
Any insights appreciated.
Thanks,
Anisha.

Hi,
I agree with the approach, i have also use similar one in a project,,
create a new doc type for legacy POs (ensuring that legacy PO no. range doesn't conflicts with normal POs), it works well as it is easy to by pass PO release strategy also..
one extra precaution is to unassign the number range to this doc type once all cutover activity is signed off to avoid accedental usage of this doc type (becuase one can use this to avoid release strategy)
reg
dheeraj

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

Cutover Activities for Upgrade Project

Experts
What are the cutover support activities for the administration of the ECC 6.0 (SAP) upgrade project. Also please do let me know how to prepare cutover strategy , and how do we develp cutover plans.
Regards,
Mahesh

Hi,
Check this thread.
CutOver activities in BI7.0 while doing production upgrade BI7.0 FromBW3.x
Regards.

Cutover activities and cutover data

Hi ,
Can anybody pl. tell me what is cutover strategy or cutover activities? What are cutover data is there?Is there any specific activity in pp
Regards

Strategy:
The cutover strategy in SAP project means the introspection of the data and business scenario while transferring the data from the non SAP to SAP system.The process involves the process of checking the redundencies involved while going Live.This ensures proper functioning of the R/3 system.And if there is any complications is involved is taken care of bveforehand so that ther is not problem while going live.
Activities:
Create a material master for the work in process and set the standard price as the cost incurred for that product (ie. Work in process)
Create a bill of material (which will be used only for this production order) including this material and other materials still to be consumed.
Create Routing for rest of the production process.
Bring the work in process material into inventory as of the cut off date.
Create the production orders in SAP for the Work in process and issue materials to production order

CUTOVER STARTEGY

HI
When working in the project there is an stage where u have to deside CUTOVER STARTEGY
before go live phase can any one expalin what
CUTOVER STARTEGY means in project point of view.
Manoj Yadav

Hi Manoj,
The cutover strategy in SAP project means the introspection of the data and business scenario while transferring the data from the non SAP to SAP system.The process involves the process of checking the redundencies involved while going Live.This ensures proper functioning of the R/3 system.And if there is any complications is involved is taken care of bveforehand so that ther is not problem while going live.I hope your query resolves soon.
Have a best day ahead.

Complex Cutover Strategy

Similar Messages

Maybe you are looking for