Você está na página 1de 5
 
Hi, Guest <a href=Log On Join Us Search the Community " id="pdf-obj-0-8" src="pdf-obj-0-8.jpg">

Hi, Guest

Search the Community

 
 
 

Products

Services & Support

About SCN

Industries

Training & Education

Partnership

Lines of Business

Events & Webinars

 

Innovation

<a href=Share " id="pdf-obj-0-79" src="pdf-obj-0-79.jpg">
<a href=Share " id="pdf-obj-0-81" src="pdf-obj-0-81.jpg">
Average User Rating (0 ratings) cutover activities. This question is Assumed Answered. Hi All, What are
Average User Rating
(0 ratings)
cutover activities.
This question is Assumed Answered.
Hi All,
What are the "cutover activities" maintained in SD in the Phase GO LIVE & SUPPORT.
regards,
vas.
3035 Views
 

hi 6. 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. 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&#8217;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

Like (0)

prashanth gaddam Jul 18, 2007 2:04 PM (in response to jyothi v)

Govind A Jul 18, 2007 2:06 PM (in response to jyothi v)

  • 0 Tweet 0

Jul 18, 2007 2:02 PM

jyothi v

Like

0

Cut over plan is the plan to migrate the dat ain Final prparation phase we Plan the data migration from legacy to SAP system,This plan is cut over plan,

Hi Vas,

<a href=Share Average User Rating (0 ratings) cutover activities. This question is Assumed Answered. Hi All, What are the "cutover activities" maintained in SD in the Phase GO LIVE & SUPPORT. regards, vas. 3035 Views Re: cutover activities. hi 6. 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. 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&#8217;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 Like ( 0 ) prashanth gaddam Jul 18, 2007 2:04 PM (in response to jyothi v) Govind A Jul 18, 2007 2:06 PM (in response to jyothi v) 0 Tweet 0 Jul 18, 2007 2:02 PM Like 0 Cut over plan is the plan to migrate the dat ain Final prparation phase we Plan the data migration from legacy to SAP system,This plan is cut over plan, Re: cutover activities. Hi Vas, THIS DISCUSSION IS LOCKED 5 Replies Latest reply : Oct 24, 2007 6:56 AM by VijayaSateeshKumar Kandula " id="pdf-obj-0-131" src="pdf-obj-0-131.jpg">
<a href=Share Average User Rating (0 ratings) cutover activities. This question is Assumed Answered. Hi All, What are the "cutover activities" maintained in SD in the Phase GO LIVE & SUPPORT. regards, vas. 3035 Views Re: cutover activities. hi 6. 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. 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&#8217;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 Like ( 0 ) prashanth gaddam Jul 18, 2007 2:04 PM (in response to jyothi v) Govind A Jul 18, 2007 2:06 PM (in response to jyothi v) 0 Tweet 0 Jul 18, 2007 2:02 PM Like 0 Cut over plan is the plan to migrate the dat ain Final prparation phase we Plan the data migration from legacy to SAP system,This plan is cut over plan, Re: cutover activities. Hi Vas, THIS DISCUSSION IS LOCKED 5 Replies Latest reply : Oct 24, 2007 6:56 AM by VijayaSateeshKumar Kandula " id="pdf-obj-0-133" src="pdf-obj-0-133.jpg">

THIS DISCUSSION IS LOCKED

5 Replies Latest reply: Oct 24, 2007 6:56 AM by VijayaSateeshKumar Kandula

THIS DISCUSSION IS LOCKED 5 Replies Latest reply : Oct 24, 2007 6:56 AM by VijayaSateeshKumar
Like (0) So for transfering the data it takes some item, so we plan in cutRe: cutover activities. 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. Cut Over activities, Gap Analysis, Open Client activity Message was edited by: SHESAGIRI GEDILA Like ( 0 ) Guest Jul 18, 2007 2:22 PM (in response to jyothi v) " id="pdf-obj-1-4" src="pdf-obj-1-4.jpg">
Like (0) So for transfering the data it takes some item, so we plan in cut
Like (0)
So for transfering the data it takes some item, so we plan in cut over plan
Maily for MDM,Master data migration we use LSMW
Reward points if u helpful
Cheers,
Govind.
Mainly in cut over plan the end user is trained on SAP system & when the end user is equipped with
SAP system then we transfer the data,
We transfer the data using tools like LSMW,BDC,SECATT,
 

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.

Message was edited by:

SHESAGIRI GEDILA

Like (0)

Guest Jul 18, 2007 2:22 PM (in response to jyothi v)

Like (0) So for transfering the data it takes some item, so we plan in cutRe: cutover activities. 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. Cut Over activities, Gap Analysis, Open Client activity Message was edited by: SHESAGIRI GEDILA Like ( 0 ) Guest Jul 18, 2007 2:22 PM (in response to jyothi v) " id="pdf-obj-1-61" src="pdf-obj-1-61.jpg">
Like (0) So for transfering the data it takes some item, so we plan in cutRe: cutover activities. 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. Cut Over activities, Gap Analysis, Open Client activity Message was edited by: SHESAGIRI GEDILA Like ( 0 ) Guest Jul 18, 2007 2:22 PM (in response to jyothi v) " id="pdf-obj-1-63" src="pdf-obj-1-63.jpg">
<a href=VijayaSateeshKumar Kandula Oct 24, 2007 6:56 AM (in response to jyothi v) MANOJ MAHAJAN Oct 24 2007 6:51 AM (in response to jyothi v) Re: cutover activities. VAS, 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. reward IF THIS HELPS.. Regds MM Like ( 0 ) Train Users Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There Cut Over Plans Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens. Hi Vas, Re: cutover activities. " id="pdf-obj-2-3" src="pdf-obj-2-3.jpg">
<a href=VijayaSateeshKumar Kandula Oct 24, 2007 6:56 AM (in response to jyothi v) MANOJ MAHAJAN Oct 24 2007 6:51 AM (in response to jyothi v) Re: cutover activities. VAS, 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. reward IF THIS HELPS.. Regds MM Like ( 0 ) Train Users Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There Cut Over Plans Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens. Hi Vas, Re: cutover activities. " id="pdf-obj-2-5" src="pdf-obj-2-5.jpg">

VijayaSateeshKumar Kandula Oct 24, 2007 6:56 AM (in response to jyothi v)

MANOJ MAHAJAN Oct 24 2007 6:51 AM (in response to jyothi v)

 

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

reward IF THIS HELPS.. Regds

MM

Like (0)

Train Users Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There

Cut Over Plans Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.

Hi Vas,

<a href=VijayaSateeshKumar Kandula Oct 24, 2007 6:56 AM (in response to jyothi v) MANOJ MAHAJAN Oct 24 2007 6:51 AM (in response to jyothi v) Re: cutover activities. VAS, 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. reward IF THIS HELPS.. Regds MM Like ( 0 ) Train Users Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There Cut Over Plans Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens. Hi Vas, Re: cutover activities. " id="pdf-obj-2-69" src="pdf-obj-2-69.jpg">
<a href=VijayaSateeshKumar Kandula Oct 24, 2007 6:56 AM (in response to jyothi v) MANOJ MAHAJAN Oct 24 2007 6:51 AM (in response to jyothi v) Re: cutover activities. VAS, 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. reward IF THIS HELPS.. Regds MM Like ( 0 ) Train Users Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better. Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP. There Cut Over Plans Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens. Hi Vas, Re: cutover activities. " id="pdf-obj-2-71" src="pdf-obj-2-71.jpg">
 

should be a gap. So by filling this gap, we make configuration with the help of these documents. This is called as fit gap analysis. Cut over activities are mainly in final preparation before go live

i). Legacy system shutdown and ii). All finished goods uploaded from legacy system to sap iii). And linking old number ranges to new number ranges iv). Uploading all transport requests v). End user training 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.

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

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

Please Reward If Really Helpful,

Thanks and Regards, Sateesh.Kandula Like (0) Share 0 Tweet 0 Like 0 Site Index Contact Us
Thanks and Regards,
Sateesh.Kandula
Like (0)
Share
0
Tweet 0
Like
0
Site Index
Contact Us
SAP Help Portal
Follow SCN
Privacy
Terms of Use
Legal Disclosure
Copyright