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

Similar Messages

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

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.

Put Together A Data Archiving Strategy And Execute It Before Embarking On Sap Upgrade

A significant amount is invested by organizations in a SAP upgrade project. However few really know that data archiving before embarking on SAP upgrade yields significant benefits not only from a cost standpoint but also due to reduction in complexity during an upgrade. This article not only describes why this is a best practice but also details what benefits accrue to organizations as a result of data archiving before SAP upgrade. Avaali is a specialist in the area of Enterprise Information Management. Our consultants come with significant global experience implementing projects for the worlds largest corporations.
Archiving before Upgrade
It is recommended to undertake archiving before upgrading your SAP system in order to reduce the volume of transaction data that is migrated to the new system. This results in shorter upgrade projects and therefore less upgrade effort and costs. More importantly production downtime and the risks associated with the upgrade will be significantly reduced. Storage cost is another important consideration: database size typically increases by 5% to 10% with each new SAP software release – and by as much as 30% if a Unicode conversion is required. Archiving reduces the overall database size, so typically no additional storage costs are incurred when upgrading.
It is also important to ensure that data in the SAP system is cleaned before your embark on an upgrade. Most organizations tend to accumulate messy and unwanted data such as old material codes, technical data and subsequent posting data. Cleaning your data beforehand smoothens the upgrade process, ensure you only have what you need in the new version and helps reduce project duration. Consider archiving or even purging if needed to achieve this. Make full use of the upgrade and enjoy a new, more powerful and leaner system with enhanced functionality that can take your business to the next level.
Archiving also yields Long-term Cost Savings
By implementing SAP Data Archiving before your upgrade project you will also put in place a long term Archiving Strategy and Policy that will help you generate on-going cost savings for your organization. In addition to moving data from the production SAP database to less costly storage devices, archived data is also compressed by a factor of five relative to the space it would take up in the production database. Compression dramatically reduces space consumption on the archive storage media and based on average customer experience, can reduce hardware requirements by as much as 80% or 90%. In addition, backup time, administration time and associated costs are cut in half. Storing data on less costly long-term storage media reduces total cost of ownership while providing users with full, transparent access to archived information.

Maybe this article can help; it uses XML for structural change flexiblity: http://www.oracle.com/technetwork/oramag/2006/06-jul/o46xml-097640.html

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.

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

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.

Vertical tables and date tracked fields

We are in process of remodeling our database. We will have true 3rd normal form tables with vertical structure and date tracked fields among many other changes. I'm interested in Toplink's support capability.
We are evaluating using stored procedures to do CRUD operations and use toplink to do only reads. Has anyone used toplink in this type of database model and how is it implemented?
Thanks

Sure. Having your database in 3rd normal form will only make your object model more consistent and more efficient to modify.
TopLink has great stored procedure support and also performs very favourably on reads, so it serves this kind of model quite well. The caveat is that TopLink tends to cache fairly agressively be default. If you are doing writes outside of TopLink then you will need to determine a strategy for refreshing cached objects that may have changed in the db. TopLink does provide a number of ways that you can use to do that, including cache eviction policies, implicit and explicit refreshing, and cache hit disabling when necessary.

DSO - What key fields and data fields in dso

Hi experts,
I need to create a dso in between the cube and 2 data sources(2lis_11_vaitm, 2lis_12_vcscl) to stage the data. My question is: what key fields and data fields to choose for the dso? is there a standard dso to copy? please explain in detail the model to set up, whether to connect both the ds's to dso and then to cube or one ds to dso and the other to the cube. more details will help.

Check this for standard DSO:
http://help.sap.com/saphelp_nw04/helpdata/en/43/fcdc387f34384f94c3227baf3837a8/content.htm
Thanks...
Shambhu

Reading MS Project column names and data on the fly from a selected View

Hi guys,
I have several views on my project file (MSPROJECT 2010) and I want to build a macro so that;
1. User can select any view ( Views can have diffrent columns and the user may add new columns as well)
2. User runs the Macro and all the coulmns along with the tasks displayed in the view will be written to a excel file. ( I don't want to build several macro's for each view, I'm thinking of a common method which would work for any selected view)
The problem I'm facing is that how will i read the column names and data for a particular view on the fly without hard coding them inside the vba code ?
The solution needs to work on a master schedule as well.
Appreciate your feedback.

Just to get you started the following code writes the field name and data for the active task to the Immediate window.
Sub CopyData()
Dim fld As TableField
For Each fld In ActiveProject.TaskTables(ActiveProject.CurrentTable).TableFields
If fld.Field >= 0 Then
Debug.Print Application.FieldConstantToFieldName(fld.Field), ActiveCell.Task.GetField(fld.Field)
End If
Next fld
End Sub
Rod Gill
Author of the one and only Project VBA Book
www.project-systems.co.nz

Pdf portfolio source file name and date in file details

Is it possible to import the source file name and extension as well as the source file created date in the portfolio file details? Need to document source to portfolio in working with 3rd parties that will only have the original source. Need to document what was converted into pdf as not all files in a directory will successfully convert to pdf. Sometimes need to convert 100's of files. Manual entry is inefficient. the file names and modified dates are displayed on the Combine Files dialog. is there a way to capture the detail on that page?

I don't need the detail of when the pdf was added to the portfolio. I
need know which dwg or jpg or word file was converted and the original
created date of that file for control of information.
That is impossible; sorry. For some *very specific* types of conversion to PDF the pdfx:SourceModified XMP tag will be set to show the last-modification date of the source file (for example DOCX files converted using MS Word), but there will never be a human-readable record of the source filename or its creation date unless you have manually added them as document XMP properties after conversion (this is what the "Custom Properties" dialog is for). To embed source data automatically would raise no end of privacy and security problems for customers, who most certainly do NOT want their recipients seeing details of internal documents.
Without writing a plugin there's no access to the internal workflow of the Combine Files dialog, so you cannot use a script to read the names and dates of the files *before* conversion and store them automatically in the new PDF Portfolio's Fields array.

Who worked with ICS' Model 4896 GPIB? I can not count the data from the module. Can prompt as it to make. It is desirable with examples (data read-out from the module and data transmission between channels. It is in advance grateful.

I can not count the data from the module. Can prompt as it to make. It is desirable with examples (data read-out from the module and data transmission between channels. It is in advance grateful.

Hello. Most of the engineers in developer exchange are more familiar
with NI products. Contacting ICS for technical support is a better
course of action.

How can we get Dynamic columns and data with RTF Templates in BI Publisher

How can we get Dynamic columns and data with RTf Templates.
My requirement is :
create table xxinv_item_pei_taginfo(item_id number,
Organization_id number,
item varchar2(4000),
record_type varchar2(4000),
record_value CLOB,
State varchar2(4000));
insert into xxinv_item_pei_taginfo values( 493991 ,224, '1265-D30', 'USES','fever','TX');
insert into xxinv_item_pei_taginfo values( 493991 ,224, '1265-D30', 'HOW TO USE','one tablet daily','TX');
insert into xxinv_item_pei_taginfo values( 493991 ,224, '1265-D30', 'SIDE EFFECTS','XYZ','TX');
insert into xxinv_item_pei_taginfo values( 493991 ,224, '1265-D30', 'DRUG INTERACTION','ABC','TX');
insert into xxinv_item_pei_taginfo values( 493991 ,224, '1265-D30', 'OVERDOSE','Go and see doctor','TX');
insert into xxinv_item_pei_taginfo values( 493991 ,224, '1265-D30', 'NOTES','Take after meal','TX');
select * from xxinv_item_pei_taginfo;
Item id Org Id Item Record_type Record_value State
493991     224     1265-D30     USES     fever     TX
493991     224     1265-D30     HOW TO USE     one tablet daily     TX
493991     224     1265-D30     SIDE EFFECTS     XYZ     TX
493991     224     1265-D30     DRUG INTERACTION     ABC     TX
493991     224     1265-D30     OVERDOSE      Go and see doctor     TX
493991     224     1265-D30     NOTES     Take after meal     TX
Above is my data
I have to fetch the record_type from a lookup where I can have any of the record type, sometime USES, HOW TO USE, SIDE EFFECTS and sometimes some other set of record types
In my report I have to get these record typpes as field name dynamically whichever is available in that lookup and record values against them.
its a BI Publisher report.
please suggest

if you have data in db then you can create xml with needed structure
and so you can create bip report
do you have errors or .... ?

Cutover strategy and dates

Similar Messages

Maybe you are looking for