SAP PROJECTS

1. Implementation projects
2. Support projects
3. Rollouts
4. Upgrades
5. Archiving
6. Developments / Enhancements

Implementation

Software implementation methodologies

SDLC

SAP Implementation methodology

ASAP methodology – Accelerated SAP

- What is ASAP Methodology?

 ASAP stands for Accelerated SAP.

 Its purpose is to help design SAP implementation in the most efficient manner possible.
 Its goal is to effectively optimize time, people, quality and other resources, using a proven
methodology to implementation.

 Phase of ASAP Methodology

 ASAP focuses on tools and training, wrapped up in a five-phase process oriented road
map for guiding implementation.

The road map is composed of five well-known consecutive phases
 • Phase 1 Project Preparation
• Phase 2 Business Blueprint
• Phase 3 Realization
 • Phase 4 Final Preparation
• Phase 5 Go-Live and support

ASAP Methodology –

Phase 1 : Project Preparation

 Phase-1 initiates with a retrieval of information and resources. It is an important time to

assemble the necessary components for the implementation. Some important
milestones that need to be accomplished for phase 1 include

• Obtaining senior-level management/stakeholder support

• Identifying clear project objectives
• Architect an efficient decision-making process
• Creating an environment suitable for change and re-engineering
• Building a qualified and capable project team.

Deliverables in Project preparation PHASE

1. Project Planning
2. Project Chart
3. Preparation of Scope document (SOW- Scope of work)
4. Project Team Skill Development, Recruitment of Consultants
5. Formation of Steering committee.
6. Implementation or defining the Project standards

Phase 2- Business Blueprint

SAP has defined a business blueprint phase to help extract pertinent information about your
company that is necessary for implementation. These blueprints are in the form of
questionnaires that are designed to probe for information that uncovers how your company
does business. As such, they also serve to document the implementation.

Each business blueprint document essentially outlines your future business processes and
business requirements. The kinds of questions asked subjected to the particular business
function

Deliverables in Business Blue print phase

1. Preparation of QADB – Questions and Answers Data base

2. Business Blue print Workshops – Requirements gathering workshops.
3. AS IS document – Business processes done in Legacy (before SAP)
4. TO BE DOCUMENT – Mapping all existing Business processes in SAP
 5. GAP – gap between standard sap processes and legacy process –

If a process is not defined in standard SAP , it is called a GAP. –

Gap fit analysis is done and gap is fixed by RICEFW –

R- reports

I – Interfaces

C – Conversions

E- Enhancements , user exits,

F – Forms

W – Workflow

6. BUSINESS BLUE PRINT – Prepared and Signoff.

7. Level 1 Training

8. Readiness with Development Server.

Phase- 3 – Realization

With the completion of the business BLUE PRINT in phase 2, “functional” experts are now ready
to begin configuring SAP.

The Realization phase is broken in to two parts.

1) 1) Your SAP consulting team helps you configure your baseline system, called the baseline
configuration.

1) 2) Your implementation project team fine-tunes that system to meet all your business and
process requirements as part of the fine tuning configuration.

The initial configuration completed during the base line configuration is based on the
information that you provided in your blueprint document. The remaining approximately 20%
of your configuration that was not tackled during the baseline configuration is completed
during the fine tuning configuration.
Fine tuning usually deals with the exceptions that are not covered in baseline configuration.
This final bit of tweaking represents the work necessary to fit your special needs.

Configuration Testing-
With the help of your SAP consulting team, you segregate your business processes into cycles of
related business flows. The cycles serve as independent units that enable you to test specific
parts of the business process. You can also work through configuring the SAP implementation
guide (IMG). A tool used to assist you in configuring your SAP system in a step by step manner.

Knowledge Transfer-
As the configuration phase comes to a close, it becomes necessary for the Project team to be
self-sufficient in their knowledge of the configuration of your SAP system.

Knowledge transfer to the configuration team tasked with system maintenance (that is,
maintenance of the business processes after Go-live) needs to be completed at this time. In
addition, the end users tasked with actually using the system for day-to-day business purposes
must be trained.

Deliverables in Realization phase

1. Baseline configuration
2. Unit testing
3. Preparing Configuration documents
4. Integration testing scripts
5. Integration Testing
6. Preparation of User manuals
7. Level 2 training
8. Preparation of UAT scripts ( UAT – User acceptance test)
9. RICEFW developments and testing
10. Readiness with Quality server for Final preparation
11. Transport the TR’s to Quality
12. Upload Sample data in Quality
13. User acceptance test in Quality server by users and signoff
14. Readiness of PRODUCTION Server

Phase 4 – Final Preparation

As phase 3 merges into phase 4, you should find yourselves not only in the midst of SAP
training, but also in the midst of rigorous functional and stress testing.
Phase 4 also concentrates on the fine tuning of your configuration before Go-live and more
importantly, the migration of data from your old system or systems to SAP.

Workload testing (including peak volume, daily load, and other forms of stress testing), and
integration or functional testing are conducted to ensure the accuracy of your data and the
stability of your SAP system. Because you should have begun testing back in phase 2, you do
not have too far to go until Go-live.

Now is an important time to perform preventative maintenance checks to ensure optimal

performance at your SAP system. At the conclusion of phase 4, take time to plan and document
a Go-live strategy. Preparation for Go-live means preparing for your end-user’s questions as
they start actively working on the new SAP system.

Deliverables in Final preparation phase

1. Transporting TR’s to Production – BY Basis / Security consultants

2. Upload of Master data into production
3. Cutover Strategy – All transactional data like Open PO’s, Stocks
GO live is on 01 april, We will give a cutoff date like 29 March ( we say to give the complete
Clist of POs and Stocks as on closing of 29 March). Then we will guide them to key all the
transactons ( PO’s created , GR done, stocks issued on 30 and 31) manually on 1 st april to
match with the Live transactions.

4. Preparation and updating of Authorization Matrix.

Phase 5 – Go-live and Hyper care Support

The Go-live milestone is itself is easy to achieve; a smooth and uneventful Go-live is another
matter altogether. Preparation is the key, including attention to what-if scenarios related not
only to the individual business processes deployed but also to the functioning of technology
underpinning these business processes and preparation for ongoing support, including
maintenance contracts and documented processes and procedures are essential.

Deliverables in GO LIVE & support

1.Live transactions monitoring
2. Cutover data entry
3. Fixing the system issues.