cutover activity

7/30/2019 Cutover Activity

1/11

Cutover Activity:

1.You could have replied like this, As cutover activity is done in the final preparation stage of the ASAPmethodology,while migrating the data from the legacy system to the sap systems,Billing will be stopped for that pointof time for time being.YOU could have told that , I have assisted in finding out the data relating to the OpenOrders,Contracts,Pricing activities and Billing Documents,for the same time data relating to the Material master ofBook stock,physical stock.etc.You should reply in such a way that he should be convinced that you really worked on

that.Answer slowly no problem. Actually the cut over plan anyway will be provided by the Implementation partner.

All the other activities at this point of time will be stopped,what ever you want to modify will be done before or afterthis activity only.I am telling this for your Idea.

Basically the following will be the roles & responsibilities of an SD consultant:

1. Creating the business blue print (BBP). The business blue print contains 2 parts - ASIS = This part contains the

explanation of the current organizational structure, master data & processes, the *requirements* are mentioned belowin the ASIS section.TOBE = This part contains the information as to how the organizational structure, master data & processes would bemapped in SAP. The solution for the requirements mentioned will be clearly specified in the TOBE section. GAPS ifany will be mentioned in the TOBE section, GAP is the bridge between the ASIS & TOBE, like if requirement can be

mapped in standard SAP, then GAP will be "A" and if requirement is to be fulfilled through some development , then

GAP will be "C". To discuss about the ASIS part, you have to be thorough with the sales domain & ask the key usersrelevant questions so as to capture all the processes & masters. You have to give them a presentation of what SAP SDis all about so that at the time of actual discussion they have some idea about the offerings in SAP. The ASIS part isdiscussed with the key users & the TOBE part is prepared purely by the functional consultant. The BBP has to be indetail so that everyone in the project always has an idea as to what will the system look like after configuration. TheBBP is signed off by the stakeholders involved in the project & after this the configuration will start.

A BBP comprises of the following structure elements in a hierarchy:Organizational Units, Master data, Business Process, Business Scenarios, Process Steps

2.Realization - As an SD consultant you have to configure the system as per the BBP, then provide the Functional

specifications to the ABAP developers for development of reports & layouts. 3. Testing - UAT & integration testing

with the client. You have to issue the templates for the master data & open items data. Master data - Customer master,finished goods material master, pricing master, customer material information record, customer credit limit. Openitems - open sales orders, open contracts. Get the sign off on all UATS & integration testing.

4. If any fine tuning is required after testing this will be done in the Final Preparation phase. In case you come acrossany new requirements which was not mentioned in the BBP, then such new requirements have to be addressed throughthe *Change Request Form*. The change request forms requires the approval from the steering committee members.Provide the request numbers in proper sequence to the Basis consultant so that the configuration can be moved in PRDserver. Upload the master data & open items data in the PRD server through LSMW or BDC.

5. Go-Live = Running an entire sales cycle = sales order - delivery - invoice (accounting document has to begenerated) will be go-live. Also the invoice print out has to be generated through SAP.Note: 1.Whatever meetings & discussions are there with the key users should be properly documented. These were some ofthe roles & responsibilities of an SD consultant

Gap Analysis

Let me share with you a requirement from one of our client. While we procure asset through requisition, the client

requirement is that the system should propose the asset number by default. If we procure 100 assets then system need

to give the asset number accordingly without users creation. But in standard we donot have such facility. User have to

manually input the asset number while raising PR or he need to create the assets at that time. So this is a gap. To

overcome this we need to do analysis for achieving the above. This is called Gap analysis. Hope the example gave u a

fair idea

In standard SAP there will be no Availability check done at Quotation Level. But client requests that


2/11

Availability check be done at Quotation level also so that that will give him an idea roughly when the delivery couldme made (remember that doesnot transfer requirements). Accordingly his customer can proceed with placing an orderor not as per his requirement.

Once the functional guys collect the business requirements from the clients, for whatever development requirementsidentified they prepare a functional specification.

It contains who the business process owners are, the developers, the functional guys involved, the proj managernames, version of the specification. Then what is the task, a pseudo logic for it, then how the desired result should belike and on what parameters the results are validated. Also the client needs approve the functional document thusprepared.

Apart from these basic details there are some more details in a functional specification document. Now based on thefunctional spec, the technical guys prepare a technical specification which contains further explanation of how that

particular is gonna be executed and how the logic is going to be validated, a code walk through. After the technicalspecification is okayed by the functional guy, they go throught with the actual development work. After it is done thefucntional guy tests it and asks for the clinet to check if it is as per his requirement.

If some more modifications or minor changes are required, then the same specification can be used with a different

version number. Like if they beginned it with ' 1 ' , this time it will be 1.1 for a minor change.


3/11

Functional Spec with Example

XYZ LTD (Client Name) ABC (Consulting Firm)

Development Request Form

Functional Specification Details

Dev Req. RefNo

To Be FilledBy FunctionalLead

Product /

ModuleFI CO MM SD CS CRM BW EP BPS

Requested By XXXXXXXXXXXXX

Requested Date 12.06.2006

Reqd. By Date

Business Case Sales / Purchase Report at Work-Shop.

Requirement

Priority Critical Important Desirable

Functional

Specs

Selection ParameterSales Organization: From (Mandatory)

Plant From to (Mandatory)Period: From date, To date (Mandatory) WRT

Service orderOutput Parameters:Header:Dealer's NamePlant :Address:Sales/Purchase ReportFrom To DateLogic for Plant Address:Go to Table T001w & get NAME2, TRAS,PSTLZ, ORT01Item Level:Sr.No

Material Code (MATNR)Material Description (ARKTX)Sale QuantityGroup Wise(Acessories/Oil/M&M,Local)Sale Value

Vat AmountUnit CostCost ValueDifference

Logic for the report:Based on the combination of Sale Organization(VKORG), Plant(Werks),

Data to be extracted from CAUFV(ServiceOrder)- Data to be Extracted are as follows:GiveInput as Erdat From To Get AUFNR(Serviceorder No).Pass This Value(AUFNR) into Table RKPF
http://wiki.sdn.sap.com/wiki/display/ERPLO/Fuctional+Spec+with+Examplehttp://wiki.sdn.sap.com/wiki/display/ERPLO/Fuctional+Spec+with+Example


4/11

With input ERDAT to get all Service ordersdone with Movement Type 261(BWART).Passthis Value (AUFNR) into VBAK to getVBELN(Sales Order No's.).Pass this values ofVBELN into Table VBAP to getMATNR,ARKTX,MATKL,ZMENG.To get Sale Amount:Go to Table VBAK give

Value VBELN, get KNUMV.Pass this KNUMV

as input in KONV table & get KBETR &KAWRTLogic for Vat Amount: Based on the region ofdelivering plant and region of the customer

A911. Hard code the values for Customer TaxClassification as '1'(Go to VBAP with in putVBELN & get TAXM1) and Material TaxClassification as '1'. Then pass the values ofRegion of delivering plant and region of

customer along with the hard coded values forCustomer Tax Classification and Material tax

classification in table A911. Obtain the value for

KNUMH for the period or duration provided asinput.Pass the A911-KNUMH into KONV-KNUMHto obtain the values of KONV-KBETR. Convert

the value in KBETR to tax rate in percentage bydividing it by a divisor of '10000'. This value is

the percentage of Tax. Add the percentage tax tothe amount obtained for the basic amount. Toobtain the price after tax.If the condition not met,. Based on the region of delivering plant and

region of the customer A909. Hard code thevalues for Customer Tax Classification as '1' andMaterial Tax Classification as '1'. Then pass thevalues of Region of delivering plant and regionof customer along with the hard coded values forCustomer Tax Classification and Material taxclassification in table A909. Obtain the value forKNUMH for the period or duration provided asinput. Pass the A909-KNUMH into KONV-KNUMH to obtain the values of KONV-KBETR. Convert the value in KBETR to taxrate in percentage by dividing it by a divisor of

'10000'. This value is the percentage of Tax.Add the percentage tax to the amount obtainedfor the basic amount. To obtain the price aftertax.Then pass this value into A920-KNUMH intoKONV-KNUMH KONV-KNUMH to obtain the

values of KONV-KBETR. Convert the value inKBETR to tax rate in percentage by dividing it

by a divisor of '10000'. This value is thepercentage of Tax. Add the percentage tax to theamount obtained for the basic amount. To obtainthe price after tax.

The validity of records from and to date toappear in the last two columns of the report.Logic for Unit Cost:Go to Table MBEW withinput MATNR & get VERPR.Logic for Cost Value:Unit Cost * Sale Quantity.


5/11

Logic for Difference:Sale Amount(NETWR-KONV) - Cost Value(MBEW-VERPR * SaleQuantity

UsageFrequency

High

Authorizations

Performance

ConsiderationsTest Cases &

Desired Output

Formats forInput / Output /Forms etc.

Input

Parameter

SalesOrganization(mandatory)

From

Period(mandatory)

From Date To date

Output

Format:ExcelSheetAttached

To Be Filled

By ProjectManager

Req. Accepted YES NO

Date

Remarks

Signature

Impact Analysis Detail s

To Be Filled By Technical Team Lead

Dev Req. Ref No

Impact Analysis

Disposition Accepted On Hold Rejected

Est. End Date

Assigned To

Remarks

Signature

Techni cal Specif ications Detail s

Dev Req. Ref NoTech Specialist

Start Date

Technical Specs


6/11

End Date

To Be Filled By Technical Team Lead

Specs ApprovedYES NO

Date

Remarks

Signature

Testing Report

Development Detail s

Dev Req. Ref No

Tech Developer

Start Date

Object Name

Request NoUnit Test Report

End Date

Remarks

Signature

Transportation Details

Dev Req. Ref No

Trans. Req. No

Trans. Req. Desc

To QA Server

To Prod Server

Signature

Are you sure yo Click to toggle the

Dev Req. Ref No


7/11

Test script - Sample for basic procurement process

view

SCENARIO: Standard Procurement involving MM processes OWNER:

BUSINESS CASE:STATUS:

To be

tested

DESCRIPTION:RUN NO.: 1

EXPECTED

RESULTS:Generation of RFQ, Price comparison, creation of standard PO,Intercompany PO, Sub-contracting PO

RUNDATE:

16-03-2007

SETUP DATA

DATA OBJECT VALUE/CODE DESCRIPTION COMMENTS AND NOTES

Input parameters

Purchase Organization

Purchase Group

Customer

Plant

TRANSACTIONAL STEPS

Link No.BUSINESS PROCESSSTEPS /

TRANS. CODEINPUT DATA /SPECIALINFORMATION

OUTPUTDATA /RESULT

TESTEDBY

STATUS

1 Login to BQA-300

A Sourcing

1 Generate RFQ ME41

2 Maintain Quotation ME47

3 Compare Quotation ME49

4 Maintain Source List ME01

BProcurement - LocalProcurement
http://wiki.sdn.sap.com/wiki/display/BPX/Test+script+-+Sample+for+basic+procurement+processhttp://wiki.sdn.sap.com/wiki/display/BPX/Test+script+-+Sample+for+basic+procurement+process


8/11

1 Purchase Requisitionassignment

ME57

Link No.BUSINESS PROCESSSTEPS /

TRANS. CODEINPUT DATA /SPECIALINFORMATION

OUTPUTDATA /RESULT

TESTEDBY

STATUS

2 Print PO ME9F alsoME22N print

preview / FAX

3Update Orderacknowledgement

ME22N

4Display of Info recordcreated for the above PO

ME13

CProcurement - Sub

Contracting

1Display Material Master forviewing special

procurement key

MM03

2Display PurchaseRequisition

ME53N

3Purchase Requisitionassignment

ME57

4Update Orderacknowledgement

ME22N

5Display of the info recordcreated for the above PO

ME13

Are you sure yo Click to toggle the

Building good test cases is very important to ensure that SAP is properly tested before go-live. Test cases include testconditions, test data and also the expected results to check the design and functionality of SAP. Test cases should be

comprehensive enough to take into account all business scenarios. SAP test scenarios contains a number of test caseswhereas a SAP test script lists down the steps that are needed to execute a test case. Tools are available in the marketto develop test scenarios. SAP tests can be designed in spreadsheets or even text editors. So what makes up a good testcase. SAP best practice test cases have the following characteristics:

1. Test cases should be reusable so that a test case once designed can be used in different testing.2. Test cases should use theSAP role profilethat will be used to test the condition. This will take care of accesscontrol testing as well.

3. Test cases should include a description of what exactly is being tested and how it will be tested. It is good to have anarrative in place for tests.

4. Tests should have valid data (transaction andmaster data) which can be related to the business process and

technical and functional requirments.5. Test cases should be reviewed and signed off once testing is complete.

SAP's Transport management system represents the centralized change and transport system CTS for all R/3 systems.

SAP introduced transport management systems TMS from version 4.0 onwards. One of the main
http://big4guy.com/index.php/2007/07/06/creating_implementing_user_roles_in_saphttp://big4guy.com/index.php/2007/07/06/creating_implementing_user_roles_in_saphttp://big4guy.com/index.php/2007/07/06/creating_implementing_user_roles_in_saphttp://big4guy.com/index.php/2007/05/15/sap_bw_master_data_manager_mdmhttp://big4guy.com/index.php/2007/05/15/sap_bw_master_data_manager_mdmhttp://big4guy.com/index.php/2007/05/15/sap_bw_master_data_manager_mdmhttp://big4guy.com/index.php/2007/05/15/sap_bw_master_data_manager_mdmhttp://big4guy.com/index.php/2007/07/06/creating_implementing_user_roles_in_sap


9/11

benefits of the new transport management system is that it enables the SAP administrator to manage all SAP R/3change requests fromone single SAP client. Centralization of change request results in streamlined changemanagement.

Earlier the transport of objects was done through transaction code SE06. With the introduction of transportmanagement system, the movement of objects is now controlled through transaction code STMS. SAP TMS allowsSAP administrators to define transport routes before hand. This minimizes human intervention in handling transportrequests. As asegregation of duties best practice, access to transport management system transactions should only

be restricted to the Basis team. Below, I have listed some of the important SAP transactions related to transportmanagement.

Important Transport Management TCodes

SCC1, SCC4 - These are Client Administration transactions which enable user to create a new client SCC1 and copydata from an existing client to a target client.

SE10 - SE10 represents the transport organizer. It is used to manage and verify transport requests.

SE11 - SE11 is theABAPdictionaryand is used to manage and release transport requests.

STMS - The transaction for transport management system, controls the movement of objects between various SAPsystems.

Landscape is like a server system or like a layout of the servers or some may even call it the architecture ofthe serversviz. SAP is divided into three different lanscape DEV, QAS and PROD.

- DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.- QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training.

- PROD may have something like a 200 Production.

These names and numbers are the implementer's discreet on how they want it or they have been using in their previousimplementations or how is the client's business scenario.

Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfiedwith your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember,this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you hadthought was important and usable, you get a transport request pop up upon saving everytime. You save it under atransport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 inthis example).

You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is aconfiguration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in theTesting client, just as it is in the Golden client. The configuration remains in sync between these two clients.

But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where youperform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). Theincorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior toGolden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config issatisfactory.

The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference

client for all the good, complete and final configuration that is being used in the implementation.

In summary:Landscape : is the arrangement for the servers

IDES : is purely for education purpose and is NOT INCLUDED in the landscape.
http://big4guy.com/index.php/2006/03/23/clients_in_sap_r3_concept_of_client_in_s_3http://big4guy.com/index.php/2006/03/23/clients_in_sap_r3_concept_of_client_in_s_3http://big4guy.com/index.php/2006/03/23/clients_in_sap_r3_concept_of_client_in_s_3http://big4guy.com/index.php/2006/04/08/segregation_of_duties_in_sap_r_3_environhttp://big4guy.com/index.php/2006/04/08/segregation_of_duties_in_sap_r_3_environhttp://big4guy.com/index.php/2006/04/08/segregation_of_duties_in_sap_r_3_environhttp://big4guy.com/index.php/2005/11/14/abap_dictionaryhttp://big4guy.com/index.php/2005/11/14/abap_dictionaryhttp://big4guy.com/index.php/2005/11/14/abap_dictionaryhttp://big4guy.com/index.php/2005/11/14/abap_dictionaryhttp://big4guy.com/index.php/2005/11/14/abap_dictionaryhttp://big4guy.com/index.php/2005/11/14/abap_dictionaryhttp://big4guy.com/index.php/2006/04/08/segregation_of_duties_in_sap_r_3_environhttp://big4guy.com/index.php/2006/03/23/clients_in_sap_r3_concept_of_client_in_s_3


10/11

DEVELOPMENT ---> QUALITY ----> PRODUCTION

DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.

QUALITY : is where the core team members and other members test the customization.

PRODUCTION : is where the live data of the company is recorded.

A request will flow from Dev->Qual->Prod and not backwards.

1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you doall the configuration/customization as per the companies business process.

2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved inworkbench requests, to be transported to Production server.

3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any

changes/ new develpoment is done is development client and the request is transported to production.

These three are landscape of any Company. They organised their office in these three way. Developer develop theirprogram in Development server and then transport it to test server. In testing server tester check/test the program andthen transport it to Production Server. Later it will deploy to client from production server.

Presentaion Server- Where SAP GUI have.Application Server - Where SAP Installed.Database Server - Where Database installed.

What is the meaning of "R" in R/3 systems?

R/3 stands for realtime three tier architecture. This is the kind of architrecture SAP R/3 system has.

R/3 means three layers are installed in Different system/server and they are connected with each other.

1) Presentation2) Application3) Database

Why do we call client 000 as golden client?

Golden client contains all the configuration data and master data so some extent. All the configuration settings aredone in golden clients and then moved to other clients. Hence this client acts as a master record for all transaction

settings, hence the name "Golden Client".


11/11

Unit Test Script

TestCaseID

Test Case Test to excute the test cases Expected Results Actual Results

1 Display of reportheader

Verify that report name ispresent at centre of reportheader.

Report should beopened in infoview. As perr the Funtionaldesign section- page no.7

2 Display of logo Verify that displayed in thetop left corner of the report.

Logo should be seen inthe top left corner of thereport.

As per the Funtional design

section-page no.7

3 Display Of "Page

N of M"

Verify that "Page N of M" isdisplayed at left corner of thereport footer

"Page N of M" should bedisplayed at rightcorner of the reportfooter


section 2-page no.7

4 Display of text "Confidential"

Verify that Confidential isdisplayed at the middle of thereport footer

Confidential should bedisplayed at middle ofthe report footer


section 1-page no.7

5 Report

Creator/Owner

Verify that Report Createrdisplay on report

The Report outputshould be as per thedesign document


section 1-page no.7

6 Parameter Verify that report parameterdisplay in report

The Report outputshould be as per the

design document


Report Parameter section-

page no.3

7 Report SQL Verify that report sql is as perthe sql given in DDD.Refer theSQL given in the attachedobject.

The Report outputshould be as per the SQLquery output


section

8 Sorting Verify that Report is sorted inasc or desc order

The Report output

should be as per the

design document


Major Report Features

section-page no.4

9 Report Output Verify that Report output is asper the mockup in detaildesign document.

Output of the reportshould be as per themockup given in detaildesign document


Major Report Features

section