Transportation request:

Transportation request: It is a 12 digit alphanumeric number
 SE01 to transport the request for business user
 SE10 to transport the request to the server
 Click on create button
© Select customizing request
Give the short description
 Save it
Select/Place the cursor on the request number
 Then click on add user icon
Specify your user name and press ENTER
 Click on release directly
Basis people maintain connections between Development server and Quality Assurance server. In weekend all the
requests are send to the production server.
NOTE: Once the customization has been transported to the server that cannot be changed.

ASAP Methodology

Accelerated SAP [ASAP] is SAP’s standard implementation methodology. It contains the roadmap, a step-by-step guide that incorporates experience from many years of implementing R/3. The road map defines control points/milestones and also specifies the major deliverables within each milestone. In road map we follo0w the identities the activities within each phase and assign dates to these milestones. At the end of the each phase we come up with deliverables/work packages. At the end of the each phase we perform quality check.

5 phases in ASAP Road Map:

1. Project preparation
2. Blue print
3. Realization
4. Final preparation
5. Go live and support

Phase 1: Project preparation: In this phase of the ASAP roadmap, decision makers define clear project objectives and an efficient decision making process. We define our project goals and identify scope of project Scope of the project: Identifying the business process that we want to map into SAP, which modules we are going to use and what functionality we are going to use for each modules. Then we decide whether we are going to go live by big bang implementation or phased implementation, which can be described in EASD [Enterprise Area Scope Development].

* We develop the structure of the project organization and identify the members to be included in the steering committee for the project.
* Assigning the resources to work on the project.
* Identify the proper hardware to be able to support development work on SAP R/3.
* Preparing the development server.
* Planni9ng for giving training for project people.
* Identifying the business and project measurements.
* Establishing standards [For proper documentation, reporting frequency and hierarchy, communication between team members].
* Identifying the persons to give authorization to access OSS note, early watch and going live check.
* Having a assistance from independent party to conduct Audit/Quality checks.
 Developing landscape, that is defining client instance strategy.
 Defining our system upgrade strategy.
 Defining procedures to manage transport requests.
 Organizing kick off meetings in which we declare the structure, roles and responsibilities.
 Perform quality checks and sign off.
 Concept check tool can be used in theses project.
Phase 2: Blue print: It’s a document that specifies all requirements of our company within identified scope of the ASAP project.
 Conceptual design phase of the project in which project team defines current business process or the AS – IS process first.
 Based on this AS – IS business processes, project team develops SHOULD – BE processes by using business re – engineering techniques.
 Mainly in this phase where we identify the requirements, perform re – engineering and record what our SAP system to deliver.
 In this phase we identify the BASELINE scope.
 In order to determine business requirements we integrate with end users. We use SAP tool that is Q & A database that is generated from the EASD. Q & A database includes issue database where issues relating project can be logged and get the resolutions from project management. By Q & A database we can generate reports.
 When answering the Q & A database we also identify the base line scope [80% of requirements].
 The entire realization phase can be divided baseline scope period, one to four unit test cycles and two integration test cycles.
 We could use two of the four unit test cycles to complete our 20% configurations.
 Based on the transactions that we identify in scope, we can specify which transactions are applicable to which cycle. This input is trigger point for generation of the business process master list .
 Based on the questions that we entered, team SAP members enter answers in the form of analysis of requirements, and then we can generate business blue print itself.
 Implementing the initial stages of the system landscape and development environment.
 System administration work starts here. So that development environment is ready with necessary logins.
 Finalize the technical design of hardware archi8techture.
 Establishing transport request management and release strategy.
 Remote connection to SAP, installing SAP GUI’s.
 Deciding the two/three tire architecture and setting up database and application layers accordingly.
 Establishing SAP clients and their purposes.
 Develop and finalize the training strategy.

Phase 3: Realization: Purpose of this phase is to implement all documented requirements in the business blue print.
 Performing integration testing.
 Getting ready of SAP system to productive operation.
 This phase is subdivided into:
(A) Base line phase [Configuration]
(B) Final configuration and
(C) Integration test
Base line phase [Configuration]: By considering business process transactions identified in the business process master prints, team SAP members perform configuration. While they doing the system configuration, developing necessary programs and interfaces, we can send project members to get the training. In this configuration minor critical processes are implemented in R/3. They demonstrate the functionality of system to team.
Final configuration: In this step team SAP will go back a little bit and allow the project team to complete 20% project.
 The work that is done at base line configuration can be refined in this phase.
 Unit/Cycle tests are developed processes.
 Problems are fixed if they found any errors, before moving to realization phase.
 The business master list contains the lists of transactions that need to be tested and that serve as a guideline for unit tests.
 These two phases can be used to develop customer-designed reports and transactions, test interfaces, test and develop all forms and data conversion programs.
 Developing quality assurance system where all integration tests would be performed.
Integration test: Performing tests on cross module processes or phase processes that involve more than one module of SAP to complete.

Integration test phase 1 constraints on transactions, which involve a data flow from one module to another module.

Integration test phase 2 is to execute back-to-back processes as if the entire process was entirely within one module.
 If any error finds that should be fixed and documented.
 Technical team defines authorizations for end users.
 Functional team creates user specific menus
 Technical team procure/plan for productive environment and archiving strategy also should be defined.
 Identifying the end users and impart training.

SAP Implementation Project STEP-BY-STEP

SAP Implementation Project STEP-BY-STEP

1.0 Project Monitoring
2.0 Project Preparation
3.1 Sap Blue Print
4.0 Realization
5.0 Final Preparation5
6.0 Go-Live & Post Go-live Support
7.0 Reference Documents
8.0 other
9.0 Process Audit Checklists
                     
    















       














     














  
       

SAP Project Monitoring (1.0.0)

1.0 Project Monitoring

1.0.1 Guidelines

1.0.2 Report

1.0.3 Project info

1.0.4 Customer Satisfaction index

1.0.5 Quality Goal

1.0.6 Resource

1.0.7 Risk

1.0.8 Problem, issues & open point

1.0.9 Traceability Matrix

1.0.10 Change control log

1.0.11 Test review report

1.0.12 Review report

1.0.13 Reuse

1.0.14 Best Practices

1.0.15 ABAP Modification

1.0.16 MIS




                                   






















           

Guidelines for project Monitoring (1.0.1 )

1. Flow of PR

PM -> PQM -> SM & TC -> PSR -> Updated PR to be circulated to all stakeholders by PM

This report has to be prepared initially as annexure to Project Plan & subsequently to be updated every month by PM , reviewed & and forwarded by PQM to SM & TC for review with their remarks / comments / suggested action points.

PM has to prepare the report and provide the reasoning for variations w.r.t planned activities & document the action plan.

PM has to forward the report to PQM for review.

PQM has to verify the complete report for correctness & completion, analyze the report for deviations from goals, carry out the configuration audit, check the project for QMS / Project Plan adherence & provide recommendations.

PQM has to verify the QMS adherence in the project and fill in the Process Audit checklist as applicable (during phase end). This will be an input to the PQM recommendations.

2. Guidelines given in each cell needs to be referred before filling the information.

3. Reporting should be as on 20th of every month. Data provided should be cumulative.

4. A review meeting to be held (Project Status Review) to discuss the status of the project & review comments. Minimum participants may be PM, PQM, SM & TC.

SBU Regional Quality Coordinators are also suggested to participate in the meeting

Team members and support teams can join the meeting as per the requirement as decided by the PM.

Meeting can be conducted offline also (Offline recommendations).

5. Final review comments / actions to be filled in the Report. Previous month's review recommendations to be retained in the report with status update while sending it for review.

6. Updated PR after the PSR to be uploaded in the Livelink & notification shall be given to all participants / stakeholders.

Alternately the same shall be sent through e-mail.

Worksheets

Note: Worksheets / rows / columns not applicable may be hidden. Project Specific additional worksheets may be added as per requirement.

Note: PM : Project Manager

PQM: Project Quality Manager

SM: System Manager

TC :Technical Controller

PSR:Project status report

Report for Project Monitoring (1.0.2)

This will provide the summary information of the subsequent worksheets, where in the progress of the project & quality of the project till the reporting date is available in brief.

This will also provide information on the actual & planned dates / effort of each phase / milestone. Also calculate the Schedule Slippage, Effort Accuracy & Effort Ratio for the projects.

Name of the reporting month needs to be changed in the Report.

Note: - Following worksheets have to be filled in during the project plan preparation. Subsequently status should be updated as & when there is a change and should be uploaded in Livelink with status as 20th of every month.

Project info for Project Monitoring (1.0.3)

This will provide the information of the project. General characteristics of the project can be identified from this information.

This also provide information on the planned resource distribution /effort estimation of the project.

Customer Satisfaction index (1.0.4 )

Customer Feedback shall be taken every six months / end of the project before End PES Meeting.

For projects of duration less than 6 months, it can be taken at the end of the project before the End PES meeting.

Quality Goals ( 1.0.5)

This will provide information on the trend of the Quality Goals set for the project. PQM should analyze the trend & provide improvement suggestions.

Resource ( 1.0.6 )

This will provide the information on the human resource of the project in terms of skill sets, contact information, training requirements etc.

Also the hardware / software / infrastructural resource requirement in the project.

Problem, issues & open point (1.0.8 )

This will provide information on the internal & external problems, Issues & it will list down all the action / open points from all meetings, audits etc. and acts as a means to track it to closure.

Customer Complaints if any also to be added as an issue in the report with classification as Customer Complaints.

Traceability Matrix (1.0.9)

This will provide the traceability from FS to the final Transport Number & vice-versa. This has to be updated only for change requests if tracked manually or if the tool does not provide the traceability.

Configuration Audit to be conducted using the Configuration Audit checklist & Basis checklist as applicable and the action points to be updated in the Problem, Issues & Open points. Audit dates to be updated in the Traceability Matrix

Change control log ( 1.0.10)

This provide information on the Change requests received in the project. This has to be updated only if tool is not used.

Test review report ( 1.0.11 )

This will provide information on the review & test summary of the deliverables.

Review report (1.0.12)

This will provide information on the review details of the deliverables. This should get updated as & when a review is conducted. It can be maintained as separate Excel Sheet if required.

NOTE: Following worksheets have to be filled in before the End PES meeting.

Reuse (1.0.13 )

This will provide information on the extent of Reuse in the project. This has to be filled in only at the end of the project

Best Practices(1.0.14 )

This will provide information on the best practices if any followed in the project. This has to be filled in only at the end of the project

ABAP Modification (1.0.15 )

This is the Metrics captured for ABAP modifications for Upgrade Projects. This sheet can be hiden for Implementation projects where upgrade is not under scope.

MIS ( 1.0.16 )

This report indicates monthly health of the project as per PM's judgment

1.0.16 MIS:

SAP Minutes of Meeting(1.1.1)

MOM Template

To			Minutes of Meeting				Received
			Organizer :
			Chairman: Phone:
			Minutes by: Phone:
Day: from-till location/building/room		Date:			From-Till:		Location / Building / Room:
Subject:
Participants:						Distribution:
Name Department Location	Department			Location		Name Department Location

Sr. No.	Minutes	Action By	Target date	Status (Closed/Open/Action Deferred)

1.
Pending Issues:
Date:		Signatures: (organizer)

SAP Project Preparation (2.0)

2.0 Project Preparation

2.1 Start PES Documents

2.2 SAP Project Briefing kit

2.3 SAP Project Charter

2.4 SAP Implementation Project Plan

2.5 Documents to be embedded in Project Plan

2.6 SAP Minutes of Meeting

Start PES Documents (2.1.0 )

2.1.0 Start PES Documents
Start PES Meeting  
Presented By:
Date:

Why New Systems Fail: An Insider's Guide to Successful IT Projects


A. ERP: The Implementation Cycle (Computer Weekly Professional)

Customer Name: - - - - - - - - - - - - - - - -
Location: - - - - - - - - - - - - - - - -
Customer Profile: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Project Manager: - - - - - - - - - - - - - - - - - -
Presented By: - - - - - - - - - - - - - - - - - -
Review Period: - - - - - - - - - - - - - - - - - -

B. Overview
 Total Effort M. Months: - - - - - - -
 Start Date: - - - - - - - - -
 Planned End Date : - - - - - - - - -
 Projected End Date: - - - - - - - - -
 Project Description
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
 Project Status Summary
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C. Technical Project Platform
 Hardware
 System Software
 Application Software
D. Project Methodology
1. Requirements / Scope / Determination of Project Size
2. Effort Estimation
3. Tracking and Measurements of work done, costs and schedule
4. Testing, Deliverables, Release
5. Acceptance and Completion Criteria
6. Escalation, Progress Reports etc.
7. Change Control / Contract Management / Claim Management
8. Resources - Manpower, Training, Infrastructure etc.
E. Project Organization   Staffing
1. Project Organization Structure



2. Project Staffing

Short Name	Role	Name
SBU Head	SBU Head
SM	Systems Manager
AM	Account Manager
QM	Quality Manager
FC	Financial Controller
PM	Project Manager
PQM	Project Quality Manger
OC	On-Site Co-ordinator
TC	Technical Controller
TL	Team Lead
PT	Project Team Member

F. Project Schedule Status Summary

Project Risks
No.	R I S K	Mitigation Plans
1
2

G. Project Goals

H. Project Standards

Defect Prevention Activities

Customer Issues

•          Customer Perception

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  Customer Feedback

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  Our Concerns

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

Why New Systems Fail: An Insider's Guide to Successful IT Projects