Cutover Activities

Hi Experts,
Can you please let us know what are the cutover activites during MM Impletation Phase?
Thanks in Advance,
Laxmi.

Cutover activies for MM Module
1) take physical inventory for initial stock upload ( with 561)
2) Closure of old 57f4 challans and open new57 f4challans( reconcile quanties at supplier end)
3) upload excise balances
4) upload master data ( Material master,vendor master, info records,excise master etc)
5) upload open purchase orders and open purchase requisitions
6) Maintain number ranges for excise documents ( from last numbers, previous number to be taken from client)
hope it helps

Similar Messages

Details on Data cutover activities during merger of 2 company codes

Hi all,
Basically we have 2 companies which will be merged to one. what would be
the data cutover activities (MM perspective) during merger?
May I know more details (particularly transaction details) on
Inventory upload,
physical inventories and value adjustments,
other open items/ balances in financial accounting,
Open PO and PR
Thanks in advance
Regards
JJ

Hi
There are lot of issues that you need to take care of:
1. is there any relation bwteeen the two company codes before merger. have they done any transactions between them? If yes, what wewould be the accounting treatment for the same. Would it be transferred at cost or Cost+Price (Transfer Price)
2. If you are in India, there would be effects of taxation like excise and vat calculations
3. One of the most important issue, is that of the new fiscal year. What strategy would you follow for the merged entity? In Sap, changing a fiscal year is a critical issue. Request you to refer SAP Help for the same. There are notes available for the same
4. What would be the strategy for Asset valuations? Are there different asset valuation procedures followed in the two company codes?
Thanks & regards
Sanil K Bhandari

Cutover Activities for Upgrade Project

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

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

Cutover activities and cutover data

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

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

Regarding cutover activities

hello SAP guys,
      i am confused regarding activities takes place in CUTOVER.I have read that in cutover you have to upload the master data,u have to upload the stock,within cutover period your client can't create any new orders,and whatever the open orders are there you have to close it.
   My question is that in one of the thread in sdn i have come to know that even the open orders you have to upload in SAP.Is it right?Does the uploading of open orders come under cutover activities?or within cutover period u have to close all the open orders so that u can work from start.
      Apart from these if u could tell me other activities which takes place in cutover than i would be very greatful.
                 Thanking u guys in advance.

Hi,
On Cut Over date:- all data regarding stocks should be ready in uploadable format as on cut over date, there should not be any issues of material.
All Open PO ie material which will be arriving after the cut over date, such PO's should be created manually. No Material GR from such PO should be made before cutover date.
All sales order whose delivery will be before Cut over date, such material should be delivered, all Open Sales Order whose delivery is expected to be after cut over date, such Sales orders to be created and delivery should be done after Cutover date only.
All Prod orders for material, whose prod will start after cut over date to be created manually, all material whose prod is continuing after Cut over date, these orders balance quantity prod orders only needs to be created.
Navin

Some Cutover Activities

Hi please brief me some of the important cutover activities such as 1. Master data upload
2. Initial stock upload
How do we upload/maintain the initial stock in the system?
Whats the t code for the same also what are the steps in that?
Best Regards,
Deepika

Hi,
SAP Data Migration with LSMW
http://www.sap-img.com/sap-data-migration.htm
http://www.sap123.com/showthread.php?t=98
LSMW - Step by Step

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

Examples for cutover activities

hi
can any me tell me what are the cutover activities and example for this
kumar

Cutover Activities or Master Data Uploading Strategies Depending upon the when we are going live. As per that, you have to give the information to your core team. If you goling live at the middle you have to upload the all P&L Account items and B/S Items. If you going live at the financial year start, you have to only Upload the B/S Items. Activities for Golive:
1.   G/L Master Upload Thru BDC or LSMW (TC-Fs00 and extended one co code to another company code Fs01)
2.   Vendor Master Upload Thru BDC Or LSMW (Will be Taken Care By MM)
3.   Customer Master Upload Thru BDC or LSMW (Will be Taken Care By SD)
4.   Asset Master Upload(Thru As90)
5.   Cost Element Master Upload
6.   Cost Center Master Upload
7.   Profit Center Master Upload
8.   G/L Balances Thru F-02
10. Vendor Balances thru F-43
11. Customer Balances thru F-22
12. Customer Advances thru f-29
13. Vendor Advances thryu F-48

FI Cutover Activities

Hello Experts,
Can someone give me the steps/sequence of FI cutover activities. We will be going live soon. I just want to be prepared for the turnaround.I know its a big topic but just outline should be helpful.
Thanks,
Reena.

Hello Reena,
Cutover activities the name itself tells you cut the business data ex: legacy transactions are stopped from today onwards means today is cut date and will take all balances as on todays date and upload into sap system by using LSMW, BDC, Ecatt etc., It is part of final preparation at 4th phase in the ASAP methodology. That includes upload the balances, sign off from end user, user acceptance test etc.,
Financial Accounting:
The following account numbers will be used for the takeover of the opening data:
Open balance assets <No.>
Initial stock uploads <No.>
Open balance GL <No.>
Open balance of Receivables <No.>
Open balance of Payables <No.>
Trial Balance:-
1.The certified trial balance as on <date> will be taken over in the SAP system.
2.It may be noted that this trial balance needs to be broken down profit center wise for the balance sheet accounts and cost center & profit center wise for the revenue accounts (Profit & Loss Accounts)
3.The Balance sheet items excluding AR/AP/FA will be taken as the closing balance, whereas, open line item will be taken for AR/AP/FA u2013 respective sub-ledger wise. AR/AP line items will compulsory have payment terms. CWIP will be uploaded asset wise. So CWIP accounts will be broken up accordingly.
Accounting Entries while data upload:
1.Inventory Takeover:
When inventory will be uploaded, following entry will be generated by the system depending upon the valuation class specified in the material master.
Inventory Accountu2026u2026u2026u2026.Dr
To Initial stock upload account
2.Receivable Takeover:
Account Receivables will be uploaded customer wise and only the open items will be taken over to new system. At the time of upload following entry will be generated.
Customer Account (with actual reconciliation account Dr
To Opening balance u2013 account receivables
3.Payable Takeover:
Account Payables will be uploaded vendor wise and only the open items will be taken over to new system. At the time of upload following entry will be generated.
Vendor Account Dr
To Open Balance u2013 Account payables
4.Asset Takeover:
The asset balances will be uploaded asset wise. This will not create any accounting entries initially and asset balances will be loaded.
In case of Accounts Receivable, Accounts Payable, and Assets, it should be ensured that the sub ledger balances are tallying with the general ledger.
5.Other GL Takeover:
All the GL Accounts (other than above) will be taken over by debiting / crediting to the account code <No.> (open balance GL)
The closing balance of balance sheet accounts will be taken over and the profit and loss accounts will be taken cost center wise.
At the end of the data takeover exercise, all takeover accounts together shall show a u2018zerou2019 balance. These accounts shall be blocked for posting after the data take on activity.
GR/IR account:
It would be ideal to ensure that all invoices relating to goods received be booked in the legacy system before the cut off date. Alternatively, all provisions made in the legacy system relating to goods received but invoices not received will have to be adjusted against corresponding vendor invoices received after the go-live date. In case of invoices relating to goods that have been received before the go-live date, the following entry shall be passed in the production system:
Corresponding Provision Accountu2026u2026u2026u2026u2026u2026..Dr
To Vendor Account
The invoice for such receipts shall be passed using the FI invoice booking transaction and not through Materials Management. The verification of the invoice shall be manual.
Apart from the above-mentioned data, the budget data for Cost center and Profit center also needs to be uploaded into the SAP system.
Thanks
Para

How to Upload WIP Production orders in production during Cutover.

How to Upload the Open Production orders in production system during cutover activities.
my client is having 1000 open production order(WIP), during cutover activies how to upload this in production.
Please guide me
Regards
Sunil Patil.

Hi,
I somewhat agree with what Raj has to say. Something which is already in process how can that be uploaded, how can one compensate for the time which has been consumed in the production activity.
I hope Rupesh Brahamakar sir would throw light on this issue, as most of us are under the dillema at the time of Cut-Over activity.
Sir, hoping your valueable inputs.
Regards,
Harris

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.

MANUAL ENTRIES IN CUTOVER

HI,
CAN ANY BODY LET US KNOW IN DETAIL ABOUT 1) WHAT ARE THE MM CUTOVER ACTIVITIES AND
2) WHAT ARE THE MM MANUAL ENTRIES UPLOAD IN TO SAP SYSTEM IN CUTOVER STRATAGY, IN FINAL PREPARATION PHASE.
PLZ KINDLY REPLY ASAP
POINTS WILL BE GIVEN
THANKS
SUNNY

Hi,
It all depends on you whether you go Manual entries or through Program BDC or BAPI
The activities
1. Intial Stock Upload through MB1C ( Mov. type 561) may be by BAPI or BDC or manually.
2. Upload of Open PR/PO.
3. If any master data( Mainly Vendor Master / Material Masrter) missing cross verify and upload the same.
4. Check MB5l transaction to see the Material stock value is in accordance with fi G/L value entry.
Thanks & Regards
Sudhansu

CutOver

Hi,
Can we upload previous transactions ( Sales Order, Deliveries, Invoices etc...) during CutOver thru (LSMW,BDC....)?
For that I heard there should be no Open order, open delivery or open billing, is that right?
What is the standard duration for CutOver?
Thank You,
Shastri

Cutover Activities
Communication to Vendor, Customer and Excise etc
User Training by Core Team
Cost Roll ups and Validations Test
Upload of Master Data in Sequence on Test
Start entry of Open Sales Orders, Quotation, Enquiries, Purchase Orders in Prod
Stock Taking Activity at Plant
Stock Upload with SAP Material Code, Qty, Value and Storage Location as on xx.xx.xxxx on Prod
Enter Cash Balances as of xx.xx.xxxx
Enter Excise balances as of xx.xx.xxx with monthly duty payment for March
Configure Cut off Excise Number Range (Excise Invoice, RG registers) as on xx.xx.xxxx
Back up of Loaded Production Server
Go Live
Availability of all balances
FI Balance uploads (For both ledgers/ subledgers/ assets/ customers/ vendors)
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

What is the Tcodes for Uploading of data using BDC & CATT

PP members:
I was going through the cutover activities , and what I understood is we transfer all the legacy system data into SAP before going live
The data upload follows certain steps (depends on the organizational design load strategies)
First we upload all the master data ( material master, BOM, W/C's & Routings)
Then the transaction data ( Ideally speaking, there should no open orders i.e. WIP as on the day of cutoff )
If the WIP (Work in Process) is unavoidable then the materials consumed shall be treated as materials of the previous stage and necessary adjustments shall be made after cutover day
At this point, I could not able to understand what does the author mean materials of the previous stage
Now comming to the uploading of data into SAP from legacy system, we use tools like LSMW, CATT & BDC
Is it a must to use only LSMW tool to upload master data or any other upload tools are fine
Lastly,. I am not sure about the Tcode of CATT & BDC
Summary of the questions:
1.What does the author mean material of previous stage, for WIP materials during cutover activities
2. Is it mandatory to use only LSMW tool for uploading for master data
3. What are the Tcodes for upload tools CATT & BDC ?
Thanks for your time
Suren R

Dear,
1.What does the author mean material of previous stage, for WIP materials during cutover activities - as i understood, what is the stage of material..like it must have gone through 2 work centers and other 2 is left. i.e. you need to create Production order with only 2 operation as other 2 is already over. - usually it is done in such a way that we will create Production order and confirm till 2 operations and WIp is calculated so thatb FI will tally the books in SAP and lagacy.
2. Is it mandatory to use only LSMW tool for uploading for master data - no you can use any tool as required and suits yr requirement
3. What are the Tcodes for upload tools CATT & BDC- BDC through a prog in SE38. CATT through - SCEM.

* Information to All

hi all.
SAP Tickets - What Is That?
Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.
The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand,to analyse,to actuate and to give the right solution in right time.This is the job of the support consultant.
The issues or the tickets(problems) which are arised is taken care of on priority basis by the support team consultants.
The work process in support projects are given below for your reference.
1. The customer or the end user logs a call through any tool or by mail (RADIX).
2. Each one of the support team is a part of support group.
3. Whenever a customer logs a call he /she has to mention to which work group (by name).
4. Once the calls came to the work group the support consultant or the team need to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top,High,Med,Low,None)
5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR(Transport Request through the basis admin)
6. Then it is informed to the end user/customer/super user about the changes which have moved to the production server by CTS process.
These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client.
An example:
Tickets in SD can be considered as the problems which the end user or the employee in the company faces while working on R/3. Tickets usually occur during the implementation or after the implementation of the project. There can be numerous problems which can occur in the production support and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.
To begin with, we should give "TICKET" to you for not knowing it.
Here is an eg of a ticket raise:
End user is not able to
1. Create Sales order for a customer from a New plant, since shipping point determination is not happened . ( Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).
He raises a ticket and the priority is set in one of the below:
1. Low 2. Medium 3. High.
Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.
You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.
Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.
What Is Maintaining SLA - Service Level Agreement
What is maintaining SLA in production support?
SLA is an abbreviation for "Service Level Agreement". It means to have guaranteed reaction or resolving times for incidents (= trouble tickets).
For instance you could have defined the following SLA levels For example:
Gold: Reaction time = 30 minutes, resolving time = 4 hours
Silver: Reaction time = 4 hours, resolving time = 24 hours
SLAs normally are part of a contract between a customer and a service provider.
Or in details description:
SLA are Service Level Agreements to resolve the tickets by the market. SLA means Service Level agreement. It is the service agreement between a Company and a service provider. For example an IT Organization providing support of SAP / other software / hardware has a agreement. This can be for example categorized based on criticality of the incident. High priority incident has to be resolved on 10 hours. Medium priority incident has a 3 days time to resolve etc
SLA's are nothing but Service level agreements.
These are defined in project preparation phase and client would have made an agreement with the company for the level of service. The SLA's are applicable in Production as well as maintanence support projects. For example: if your company follows a ticketing process(a ticket is nothing but an environment contains complete description of the problem which contains Short description, problem, customer contact details, sreen shots of the error etxc.,) and for each ticket there will be a severity for example business critical issues or problems may be treated as high or top severitie's. In those case your company or your team has to deliver the solution to the customer in agreed time limit or otherwise you might end up missing SLA's.
SLA's has two important time specifications
1. IPRT --- initial problem response time --- this is nothing but time taken to respond to the problem.
2. PRT --- Problem response time -
this is nothing but time taken to solve the issue or problem.
Both IPRT and PRT will be different for different severitie's.
What Are Functional Specification in SAP?
To speak at macro level that is at projet manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.
The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
The functional specification translates the Software Requirements template into a technical description which
a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.
b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
Let me throw some light on documentation which is prepared before and in a project:
1) Templates
2) Heat Analysis -
3) Fit Gap or Gap Analysis
4) Business Process Design
5) Business Process Model
6) Business Change & Impact
7) Configuration Design, which is just 5 % of Total SAP- have different names -
8) Future Impact & Change Assessement
9) Functional Design (Module Wise)
10) Risk Assessement
11) Process Metrics and Many More-- Which has impact on Business and its work flow
Note * This documents are preapared in Vanilla SAP Standards -- Things differ from one implementation to another, and it always depends on the type of business which is opting for SAP
Role of a mySAP Functional Consultant
What are the differences between a functional and business consultant?
The difference between Functional consultant and Business consultant are as follows:
1) A funcitonal consultant is able to configure the system unlike business consultant.
2) Functional consultant know more about business process unlike Business consultant.
3) A business consultant will bring business process knowledge and provide it to functional consultant who in turn used this knowledge to configure the system.
4) Functional consultant has more configuration knolwledge then Business consultant. *-- Rocky
The responsibilities of a support consultant are:
- Primarily responsible for Handling tickets and application support to the endusers
- When an issue comes diagnose, analyse and solve the issue
- Responsible for any enhancements
- Writing functional specs and interacting with Abapers to develop any user exits
- Training the end users and preparing end user training material *-- Sistla
For those who wished to know the role of a functional consultant. Below is one view:
A functional consultant evaluates the demands in talking with the customer's representatives, transforms the essence into an abstract and algorithmic business model. Hence, he identifies the use cases and transforms them into logical and technical views.
Then the main task starts: customizing the respective business area and making sure the system reacts in the manner according to the constraints of the requested use case.
The consultant documents the settings and prepares proper guidelines that allow other consultants to do further changes or repairs with due efforts.
The consultant takes care that proper training is given to the users and that the system is usable, performing appropriately and the business flow is complete and correct.
During go live he assists the technical staff by testing the behaviour of the system.
After go live he guarantees that the procedures remain usable and consistent in real live situation and proposes enhancements.
The main duty of a consultant is to transfer external know-how to the client. It is not manpower that counts but intelligence, understanding of processes, a feeling for defects and general a common sense
Role of SAP Consultant In Testing
1. What is the role of SD Consultant in Testing while implementing the project?
2. What is Unit testing and Integration Testing?
Testing : the core team members along with endusers will test whether the postings done in SAP is resulting as per the requirements of the organisation. They will test whether the output documents such as purchase order, invoice document are printed in the required format and showing the correct data.
Unit testing is refer to the module which are going to implement. SD, MM, FICO etc. there will be test script based on that testing will be performed.
Integration testing will be cross the modules. MM-SD-FICO for example. Integration testing is also called SIT ( System integration testing)
Testing mathologies and types: there are 6 types of testings:
1. Unit Testing
2. System Testing
3. System Integration security Testing
4. Performance Testing
5. User Acceptance testing
6. Regression Testing
Unit testing is done in bit and pieces. Like e.g. in SD standard order cycle; we do have 1-create order, then 2-delivery, then 3-transfer order, then 4-PGI and then 5-Invoice. So we will be testing 1,2,3,4 and 5 seperately alone one by one using test cases and test data. We will not be looking and checking/testing any integration between order and delivery; delivery and TO; TO and PGI and then invoice.
Whrereas System testing you will be testing the full cycle with it's integration, and you will be testing using test cases which give a full cyclic test from order to invoice.
Security testing you will be testing different roles and functionalities and will check and signoff.
Performance testing is refered to as how much time / second will take to perform some actions, like e.g. PGI. If BPP defination says 5 seconds for PGI then it should be 5 and not 6 second. Usually it is done using software.
Regression testing is reffered to a test which verfies that some new configuration doesnot adversly impact existing functionality. This will be done on each phase of testing.
User Acceptance Testing: Refers to Customer testing. The UAT will be performed through the execution of predefined business scenarios, which combine various business processes. The user test model is comprised of a sub-set of system integration test cases.
We use different software during testing. Most commonly use are
Test Director: which is used to record requirement, preparing test plan and then recording the progress. We will be incorporating defects that are coming during these testings using different test cases.
Mercury Load Runner: is used for performance testing. This is an automatic tool.
What does the following terms means :
- Technical Unit Testing
- Functional Unit Testing
- IntegrationTesting
- Volume Testing
- Parallel Testing?
Technical Unit Testing= Test of some technical development such as a user exit, custom program, or interface. the test usually consists of a test data set that is processed according to the new program. A successful test only proves the developed code works and that it performed the process as as designed.
Functional Unit Testing= Test of configuration, system settings or a custom development (it may follow the technical unit testing) These usually use actual data or data that is masked but essentially the same as a real data set. A successful test shows that the development or configuration works as designed and the data is accurate as a result.
IntegrationTesting= Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrate . The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas.
Volume Testing= testing a full data set that is either actual or masked to insure that the entire volume does cause system problems such as network transmission problems, system resources issues, or any systemic problem, A successful test indicates that the processes will not slow or crash the system due to a full data set being utilized.
Parallel Testing= Testing the new system or processes with a complete data set while running the same processes in the legacy system. A successful test will show identical results when both the legacy system and new system results are compared.
I would also note that when a new implementation is being done you will want to conduct at least one cut over test from the old system to the new and you should probably do several.
What kind of testings that are carried out in testing server?
1. Individual Testing ( Individually which we've created)
2. Regressive Testing ( Entire Process)
3. Integration Testing ( Along with other integrated modules)
The 3 types of testing is as follows:-
1. Unit testing (where an individual process relevant to a SD or MM etc is tested)
2. Integration testing (where a process is tested that cuts across all areas of SAP).
3. Stress testing (where lots of transactions are run to see if the system can handle the data)
Roles and Responsibilities of End Users
What is the Difference between Consultant & End users?
SAP consultant role is to build the system, changes & modification/updation in currently installed SAP system for the end users.
SAP End user only use the SAP system just to fetch some info, or to create new thing. So a end user is just using the final product which it is meant for and consultnat design the product/updation and modification.
The roles and responsibilities of end users is working in easy access menu they will not have authorizations of using img settings if they get doubt they will send query to the implemented company and just entering day to day transactions.
Roles and Responsibilities of End User:
Using the software at the end or after the implementation is an End User.
In sap HR , we do come across entire Org Management creation by an end user after the Personnel strucutre is created. OM objects like creation of Org Unit means functional area or dpt , creation Job and Position and its occupancy is with in the limits of an enduser. Initiallly the OM is created by sap consultant . In course of time a new department has appeared in the company of the client .. this has to be created by the enduser rather than depending up on the implementor... similarly new job and position..like this small things are always done by the enduser.
The entire work of OM is purely depends upon the enduser.
After from this running periodical payroll and Ensuring of the Time schedules ( Work Schedules) of each employee is done from sap easy access by an enduser and the show run of payroll everymonth is by the enduser only. Like this lot of roles are there for an end user.
Whatever the problems come across during the enduser utilisation of sap ...that will reach as ticket to the support team
What Are SAP End User Manual
It is the same for every other modules although here I reference it mainly for SAP HR.
1) You should understand which targeted group for the end-user training is for. Do they have any computer background or not.
2) In what way they are going to make use of the manuals supplied to them during the course of training.
Let us focus on how to prepare manuals:
In the client side , End Users are not permanent. If they get any better job outside they will resign and go out. Even if you train them well, again the end-user team disappears after some time. That is why implementing company( Client ) expects SAP Consultants to prepare documents which are self explanatory (even to a layman in SAP) and study themselves and use the sap easy access very comfortably.
Hence we should prepare a document which explains the following things comfortably:
A) All the buttons and Screens we have in sap and its importance for an end-user.
B) All the transaction codes used by end user.
C) The STEP by STEP usage methodology with screen shots and explanatory foot notes for each Transaction code.
D) Prepare a book a table and columns which should have the following information:
- Sl.NO.
- Transaction Code
- Navigation path
- Use of the Code
- Expected Result
- Achieved Result
- Remarks/Any Comment
E) Highlight the common troubles during the usage of SAP by an end- user and give the solutions (ready to use)
These problems you can come across while giving the in house training for the end-users. You just place them at one place and publish it for their usage in future for any of their new joinees as an end-user.
F) Every consultant is aware that the entire Organsiational Management is with end user only. Means consultant should train the end user in entire OM.
G) We should inform the importance of info types and usage for our purposes at expert mode, PA30, PA40 etc.,
H) Each field in the international infotypes should be explained very clearly and ensure that they are comfortable with the fields of infotypes which have been configured for their company.
For example : info type 0001 Org Assignment insists about the three structures of the HR. We should explain each sub field like Emp Group, Emp Sub Group, Personnel Area and Sub Area and its importance and relevance to their company so as to understand while processing them from the end- user point of view .
When an employee is hired into the company , now the end-user in a position to understand which employee group and subgroup, Personnel Area And Sub Area etc., should allotted..
Like this whatever comes across in SAP Easy Access should be insisted through the training of end users.
I) Demo, exercises and solutions should be provided in the manuals.
J) Glossary of terms and expansion of Acronyms, Abbreviations should be given. Like this each consultant should focus on end user training and prepare the documents.
Mini SAP System Requirement and How to Get it
Mini SAP System Requirement
The system Requirements are :
General Requirements
Operating System:
Windows 2000 (Service Pack2 or higher);
Windows XP (Home or Professional);
Windows NT
Linux
Internet Explorer 5.01 or higher
At least 192 MB RAM (recommended to have 256 MB of RAM)
At least 512 MB paging file
At least 3.2 GB disk space (recommended to have 6 GB hard disk drive space)
(120 MB DB software, 2.9 GB SAP data, 100 MB SAP GUI + temporary free space for the installation)
The file C:\WINNT\system32\drivers\etc\services (Windows 2000) or
C:\Windows\system\32\drivers\etc\services (Windows XP) must not include an entry for port 3600.
A possible entry can be excluded by using the symbol '#'.
No SAPDB must be installed on your PC.
The hostname of the PC must not be longer than 13 characters.
The Network must be configured for installation and
the MS Loopback Adapter must be configured when you start the system without a network connection!
Special Requirements for Installations on Windows XP
In the file C:\Windows\system\32\drivers\etc\hosts the current IP address and the host name must be defined as
<IP address><Host name>
Open the network connectivity definition with start->control panel->network connections for defining the network connection. Select ->extended-> allow other users in network. Activate new configurations.
Select remote desktop within extended configuration menu.
Successfully Implementing SAP
Implementing a package can be a traumatic affair for both the customer and the vendor. Get it wrong and the vendor may get paid late or have to resort to lawyers to get paid and tarnish their reputation. For the company the new package may not work the way they expected, be late or cost a more than budgeted for and take management will take their eye off running their business.
Recently a client asked me what I would consider to be the five most important things one should consider before embarking on an implementation. This isn't a simple question, although there are many factors to think about after some consideration for me the top five are way ahead of the others.
My top five factors to consider would be:
1. Set up a Project Board,
2. Secure the resources,
3. Complete the GAP Analysis,
4. Have detailed Cut Over Plans,
5. Train the users.
Taking each one in turn:
The Project Board
The correct set up and operation of the Project Board in my view is major factor in the success failure of the project. The Project Board will consist of the stakeholders, key users and the vendor. The Project Board is part of the governance of the project. The Project Board will meet regularly to ensure that the project plans are created and being executed as planned, moves from stage to stage with all the deliverables being signed off is resourced properly.
The Resources
Three types of resources are absolutely necessary -- end users, change team and technicians.
Early involvement by the end users is absolutely necessary, as they will be the ones living with the system for hopefully many years to come. They will want to feel involved in its implementation. Buy in from the end users of the system is absolutely essential if the system is to have a long and stable life in any organisation.
The Change Team will identify the gaps between the package and the business requirements, re-engineer some of the businesses process to cope with the package, train the users to ensure implementations is smooth as possible into the business.
The Technical Team will prepare the systems environment for the package, apply any software fixes from the vendor, implement the software in the best way possible for the organisation set up and tune the software for the particular technical environment.
GAP Analysis
A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage.
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.
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.
Explain Cutover Activities/Strategies in SAP FI.
Cutover Activities or Master Data Uploading Strategies Depending upon the when we are going live. As per that, you have to give the information to your core team. If you goling live at the middle you have to upload the all P&L Account items and B/S Items. If you going live at the financial year start, you have to only Upload the B/S Items. Activities for Golive:
1. G/L Master Upload Thru BDC or LSMW (TC-Fs00 and extended one co code to another company code Fs01)
2. Vendor Master Upload Thru BDC Or LSMW (Will be Taken Care By MM)
3. Customer Master Upload Thru BDC or LSMW (Will be Taken Care By SD)
4. Asset Master Upload(Thru As90)
5. Cost Element Master Upload
6. Cost Center Master Upload
7. Profit Center Master Upload
8. G/L Balances Thru F-02
10. Vendor Balances thru F-43
11. Customer Balances thru F-22
12. Customer Advances thru f-29
13. Vendor Advances thryu F-48
Before uploading Vendor Balances you have to take care of WHT(TDS) Information.
Difference between the User Exit & Gap analysis.
Both are quiet a different and has a small relation.
User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench. its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
Gap analysis is start point of Realization and once blue print is finished we have to find the realization of sap system for client requirment and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system. *-- V. Sridhar
What is roll out of SAP Project?
As per dictionary, Rollout means Inauguration or initial exhibition of a new product.
As per SAP specific definition, rollout is the strategy for international SAP implementation. Rollout strategy normally include the following
- Whether to implement SAP simultaneously (also known as big-bang) in all the countries, or
- Go live in sequence of phased manner
- Or to go for the combination of both (phased manner implementation for some of the countries and big-bang for others).
Rollout strategy is the most important decision that a client can make during SAP implementation. Normally, steering committee decides the rollout strategy.
ALL THE BEST

Man, thanks a lot! I appreciate this.
You think you could do me a favor? I listen to a lot of DCI songs (for those of you who don't know what that is, don't worry about it), anyways, DCI shows are average 0-2 mins. Could you give me the formula that you use for this so I can calculate it's

Cutover Activities

Similar Messages

Maybe you are looking for