Professional Documents
Culture Documents
ASAP Accelerated SAP Phase 1 and 2 PDF
ASAP Accelerated SAP Phase 1 and 2 PDF
Dr. Andijani
Handout
ASAP: Accelerated SAP Phase 1 and 2
Identify the Project Preparation purpose, main deliverables and work packages
Identify the Business Blueprint purpose, main deliverables and work packages
Developed from the perspective of the company as a whole rather than any
one of its departments
Features:
On-line system with no batch interfaces
One database for all data (minimal redundancy)
Clear definition of data items in data dictionary
Modular application (independent, but integrated modules)
Software functionality configurable to customers requirements
(parameterized modules)
Client-oriented data structure
Definition data reflects the relevance of the business
SAP R/3 Coverage
Financial Accounting
FI: external accounting
CO: internal accounting
AM: asset management
Human Resources
Manufacturing and Logistics
MM: materials management
PL: plant management
QM: quality management
PP: production planning
PS: project system
SM: service management
Sales and Distribution
ASAP, why?
The largest drawback to SAP R/3 (and other ERP) has been that it takes too long
to implement
ASAP was designed specifically to refine and produce a standard implementation
approach to cut the implementation time to less than 2 years and reduce costs,
making it an acceptable solution for smaller businesses
so Benefits
Quicker SAP R/3 implementation and improved business results
Offers a standard approach to SAP R/3 implementation
Results in more effective use of available resources, resources that can be
used in future implementation stages to decrease your overall
implementation costs
What is ValueSAP?
We will focus on implementation, that is, on how ValueSAP helps us implement ERP
solutions, in particular, SAP R/3 solutions. To do this we will use Accelerated SAP
(ASAP).
ASAP Phases
Phase 1, Project Preparation: Initiates with a retrieval of information and
resources. The purpose of this phase is to provide initial planning and preparation
for your SAP project. Decisions, decisions start planning
Phase 4, Final Preparation: Testing, user training, system management and cut
over activities, to finalize your readiness to go live. This final preparation phase
also serves to resolve all crucial open issues. On successful completion of this
phase, you are ready to run your business in your productive R/3 system. Just
checking Everything all right?
The ASAP Roadmap covers the different aspects and phases of an implementation. In
the Roadmap, a detailed project plan is included for the five phases. The Roadmap
provides a standard procedure (methodology) for implementing the SAP R/3 System,
including project management, configuration of business processes, technical, testing and
training aspects
Some Project Roles
Steering Committee
Project Sponsors
Project Management
Change Management
Consultant
Security
Training
Technical
The Implementation Roadmap is the main structuring mechanism for tools within the
Implementation Assistant. It is divided into four levels (PWAT):
Phase: main organisational step
Work package: A group of activities to complete a major portion of Phase. A
project team would be assigned a work package
Activity: A group of tasks. An activity can produce a deliverable, and would be
assigned to one or more project team members
Task: A specific event to be performed by a project team member
Accelerators can be documents, templates, tips or tricks or whatever, which can be used
to accelerate task completion
The purpose of this phase is to provide initial planning and preparation for
your SAP project. Although each SAP project has its own unique objectives,
scope, and priorities, the steps in Phase1 help identify and plan the primary focus
areas to be considered
As you prepare your SAP implementation, there are important issues you must
address at the beginning of the project, including
Defining your project goals and objectives
Clarifying the scope of your implementation
Defining your implementation strategy
Defining the overall project schedule and implementation sequence
Establishing the project organization and committees
Assigning resources
By addressing these issues early in your implementation, you help ensure that the
project proceeds efficiently, and that you have established a solid foundation for a
successful SAP implementation
Project charter: Represents an agreement on, and commitment to, the deliverables of the
project, as well as the time constraints, resources, standards, and budget of the project
Project plan: This is the first cut, focuses on milestones and Work packages
Project team organization: Sets the who of the project. This decides who will be
involved and what their goal is
Standards and procedures: Sets the why and how of the project. Standardizing how
meetings are run, documents are handled; etc means that everyone understands what is
going on
Outputs from Discovery & Evaluation phase of ValueSAP are fed into ASAP
Main aims of Phase 1: Project Preparation are to
review scope and strategy documents
collect together the project team and set up standards
start training
The BB document! It lays the foundations for your implementation project. The BB
documents the business process requirements of the company (gathered during
requirements workshops). On this basis, you achieve a common understanding of how the
company intends to run its business within the SAP R/3 system
The requirements are reviewed for each SAP Reference Structure item in the Q&Adb,
and the answers to the Questions and CI (Customer Input) Templates are input to the
Q&Adb. The Business Blueprint document is the output of the Q&Adb
The Q&Adb is the tool that helps you determine the company requirements with respect
to SAP business processes. It uses CI templates (general) and business processes
questions (specific).
There are 4 Master Lists: Business Process Master List (BPML), Organizational
Structure List (OSL), Development List (DL), and Authorization List (AL).
Business Process Master List (BPML): An Excel worksheet containing a representation
of the R/3 business processes and transactions defined in the project scope in order to
carry out the configuration and testing of R/3 in iterative cycles: the Baseline scope
(defined in the BPML), up to four configuration cycles (C1 to C4), and two integration
cycles for testing.