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.

Similar Messages

What is Workbench and Cut over stratrgy

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

Hi
we have different Workbench like ABAP Work bench and LSMW
ABAP Workbench is used to develop the Program
Legacy System Migration Workbench (LSMW) is used to Upload the Legacy system Data (All Master data, Transaction data, Stock balance, Account balance ) to Production Server
This process is called Cut over
This is tack place before GO-Live and After Change management

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

We are trying to do a Quick payment from payment workbench and getting 'FRM-41830: List of values contains no entries' error for payment document column/field. Payment document setup looks good. Not sure what the issue is.

We are trying to do a Quick payment from payment workbench and getting 'FRM-41830: List of values contains no entries' error for payment document column/field. Payment document setup looks good. Not sure what the issue is.

Already gone through following three notes but didn't found resolution.
APXPAWKB: FRM-41830 When Clicking on Payment Document LOV (Doc ID 1081305.1)
R12: APXPAWKB: Payment Document Lov Is Empty When Entering A Payment (Doc ID 857587.1)
R12: Payment Workbench Error: FRM-41830 List Of Values Contains No Entries (APXPAWKB.FMB) (Doc ID 1323875.1)

What procedures in BRF+ workbench and what in ABAP via coding

Hello Gurus ,
I am new in BRF+ development. I have a query -what procedures should be done in BRF+ workbench and what in ABAP via coding.
If we create all object in BRF+ workbench and use ABAP for only invoking the function , passing parameters and displaying result .
Is there be any limitation/ issues for extending BRF+ functionalities later using this approach.
Thanks in advance.
Best Regards,
PS

Moderator message -
When closing old threads, there is no need to add a comment. Adding a pasted answer like "thanks a lot" only brings old threads to the top of the forum list and pushes current ones down. If you do add a comment, please indicate just how the problem was resolved.

What is Cutover Date and Cutover Activities

Dear All,
What is Cutover Date And Cutover activities, if nay one know kindly help me
Regards
Reddy.

at the final preparation stage we have list of activitiesl ike
1.all transport request moved to production?
2.check all number ranges are there i production?
3.check all user profile are working ?
4.if problems will occure in production system , how we will deal /
5.all master data uploaded in production server?
like that only
chandra

What's the difference between the LRU and NRU strategy for stateful session bean?

Hi,
Does anybody know the difference between the LRU and NRU strategy for
stateful session bean?
Thanks,
Levi

LRU makes the assumption that the bean that has been used a lot recently is
likely to be used again.
NRU simply removes the beans that have not been used for a stipulated amount
of time.
The algorithm for the LRU is much more complicated than the NRU. I think BEA
recommends LRU for better performance and NRU when you have memory
constraints.
"levi" <[email protected]> wrote in message
news:[email protected]..
Hi,
Does anybody know the difference between the LRU and NRU strategy for
stateful session bean?
Thanks,
Levi

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

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.

Dunning by dunning procedure and collection strategy

Hi All,
Have some questions around dunning.
1. Can dunning by dunning procedure and collection strategy coexist in the same company code - if this cannot be achieved by config can it be achieved by development - can we have something like account determination IDs of X to use dunning procedure, account determination IDs of Y to use collection strategy?
2. If the answer to 1. is no, can one company code use dunning procedure and another company code use collection strategy?
3. What is SAP's (or any other proven) recommended approach to migrate a production system utilising dunning by dunning procedure to dunning by collection strategy?
Cheers.

Have a look
SAP-ISU will be used to carry out initial collection activities. Initial 1 or 2 reminder letters (based on the customer type, Live or Closed) will generated from SAP-ISU. Thereafter, the account will be managed in Tallyman. Thus, all the subsequent activities, such as sending further reminder letters, sending debt to collection agencies, carry out warrant activities and taking customers to court will be carried out in Tallyman system. During the time, the account is in Tallyman, no dunning activities will be carried out in SAP.
There will be daily interfaces from SAP-ISU to Tallyman to update Tallyman of Accounts that have passed a certain dunning level in SAP-ISU and any changes to the account that are currently being managed in Tallyman. Similarly there will be interfaces from Tallyman to SAP to update SAP of Accounts, that have been marked for write off in Tallyman. Fees and Charges that have been applied in Tallyman, for example court fees, warrant fees etc.
Regards
Shashi
Edited by: shashi jha on Mar 31, 2010 8:10 AM

PMW (Payment Medium Workbench) and needs to send Payment Advises to Vendor

Hi SAP Gurus,
We are using PMW (Payment Medium Workbench) and our client needs to send Payment Advises through mail. After running F110 system should trigger mail to vendor for payment advise.
We have created one DME format and it's working fine. DME file is getting generated when we assign DME format to our payment method.
we have also made the change for payment advice sending through email. Copy FM SAMPLE_PROCESS_00002040 to ZSAMPLE_PROCESS_00002040
Go to transaction FIBF
Settingsprocess modules of an SAP application
Add a new entry for 00002040 FI-FI ZSAMPLE_PROCESS_00002040
Make use of FM ZSAMPLE_PROCESS_00002040 for adding vendor email address and make the payment medium.
Now the problem is, we can not do this in one go, if we need to create DME file than we have to assign DME format to our payment method and if we have to send payment advice to our vendor than we need to use Payment Medium Program RFFOGB_T (standard program). It's radio button and we can not choose both the program and Payment Medium Workbench.
I need your valuable advice what need to be done in order to get DME file and payment advice send to vendor in one go.
many thanks for your reply.
regards,
SATVIR SINGH

Hi Stavir,
Do you recall how were you able to resolve this issue?
Thanks
M

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 .

What is ' WORKBENCH' and CUTOVER STRATEGY

Similar Messages

Maybe you are looking for