7137 TSCM 52 2 parte (24)

background image

E-MSG

MÁSTER EN SOFTWARE DE GESTIÓN DE EMPRESA
SAP R/3

2003-2004
Certificación MM (7137)
Xavier Rovira-Juan Carlos Sarrasi
TSCM 52-2ª parte (24-1)

background image

background image

© SAP AG

TSCM52

24-1

SAP AG 2002

Appendix

background image

© SAP AG

TSCM52

24-2

SAP AG 2001

Implementation Roadmap

z

Phase 1 - Project Preparation

z

Phase 2 - Business Blueprint

z

Phase 3 - Realization

z

Phase 4 - Final Preparation

z

Phase 5 - Go Live & Support

Content:

background image

© SAP AG

TSCM52

24-3

SAP AG 2001

Upon completion of this unit, you will be able to:

z

Outline the purpose and content of the work
packages in each phase of the ASAP Roadmap

z

Identify the main roles and responsibilities of
each phase of the ASAP Roadmap

z

Explain and demonstrate the major tools &
accelerators supporting each phase of the
ASAP Roadmap

Implementation Roadmap: Unit Objectives

background image

© SAP AG

TSCM52

24-4

SAP AG 1999

Unit

Unit

Unit

Topic

Topic

Topic

Legend:

Legend:

Legend:

Phase 1
Project Preparation

Phase 2

Business Blueprint

Phase 3
Realization

Implementation
Roadmap

Phase 4

Final Preparation

Phase 5
Go Live & Support

Overview Diagram: Implementation Roadmap (1)

background image

© SAP AG

TSCM52

24-5

SAP AG 2001

Phase 1: Project Preparation: Objectives

On completion of this topic, you will be able to:

z

Explain the activities and tasks that are
important in the Project Preparation phase of
your implementation project

z

Highlight the tasks essential from the project
team perspective

z

Identify the importance of the Sample Scope
Document for Phase 2: Business Blueprint

background image

© SAP AG

TSCM52

24-6

SAP AG 2001

The Purpose of Phase 1: Project Preparation

ASAP Roadmap

Project

Preparation

Realization

Final

Preparation Go Live &

Support

Business

Blueprint

„

The purpose of this phase is to provide initial planning and preparation for your SAP project.
Although each SAP implementation project has its own unique objectives, scope and priorities, the
steps in Phase 1 help identify and plan the primary focus areas to be considered. As you prepare for
your SAP implementation, there are important issues you must address at the beginning of the
project, including:

y

Defining your project goals and objectives

y

Clarifying the scope of your implementation

y

Defining your implementation strategy

y

Defining the overall project schedule and implementation sequence

y

Establishing the project organization and committees

y

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.

background image

© SAP AG

TSCM52

24-7

SAP AG 2001

Project Preparation - Roles & Key Focus

Sign-Off

Quality Check/

Sign-Off

Sign-Off

QC

QC

Tech.

Tech.

Req

Req

.

.

Planning

Planning

Project

Project

Kickoff

Kickoff

Training

Training

Plans

Plans

Project

Project

Procedures

Procedures

Initial

Initial

Proj

Proj

Planning

Planning

Steering

Steering

Sponsors

Sponsors

Proj

Proj

. Mgmt.

. Mgmt.

Consultant

Consultant

Customer

Customer

Technical

Technical

Training

Training

Change

Change

Security

Security

Role
Groupings

Phase

Content

******************

Proj. Charter

and

Implementation

Strategy

******************

Implementation

Strategy

Plan / Budget/

Resources

Organization /

Plan

Proj. Mgmt.

Standards &

Procedures

Deployment

Strategy

Change Mgmt.

Plan

Comm./ Doc.,

Issue Mgmt

Change Mgmt

Plan

System Authoriz.

Standards

Project Team
Training Plan

Project Team

Org. Change

Management

Training

Kickoff

Meeting

Kickoff

Meeting

Project Team

Standards

Kickoff

Meeting

******************

Kickoff

Meeting

Proj. Team

Standards

******************

ID Tech

Requirements/

Procure HrdWr

„

There are ten primary roles in an SAP implementation; details of each are in the Implementation
Assistant.
Steering Committee - members include Project Sponsors, the SAP Consulting Manager (and/or the
TeamSAP Coach), and project managers. The committee is also the primary source for the
company’s long-term goals and vision, sets priorities, approves scope, and resolves company-wide
issues.
Project Sponsors - Directly communicates the company's long-term goals and visions and are
members of the steering committee.
Project Management - TeamSAP Project Manager and Customer Project Manager
Consultant - TeamSAP Members, application, cross application, business process
Technical - Customer or consultants for System Administration and Technical, Help Desk Provider
Training - Training & Documentation, Project Manager/Lead, Training and Documentation
Developer/Instructor, Training Coordinator, Training Technology Administrator
Change -These are dedicated individuals assigned to manage the Organizational Change
Management processes: Risk Assessment, Communication, Sponsorship and Leadership, Skills
Development, Knowledge Transfer, or Business Optimization.
Security - Authorization, Administration, or Internal Auditor responsible for managing the system
security and authorization environment and may be combined with other (technical) administrative
roles.

„

Shared items are marked by the ************ brackets.

background image

© SAP AG

TSCM52

24-8

SAP AG 2001

Master Lists

Microsoft Excel
Spreadsheets for
Development, Organization,
Business Processes and
Authorizations

Project

Charter

BPP

Documents of an ASAP Project

Q&Adb

Substructures:

Business Strategy
Organization
General Settings
Master Data
Business Process
Cross Application
Development

Business

Blueprint

Project

Plan

Scope

Config.

Plan

Testing

Plan

Unit testing
Test scenario
Integration

4

3

2

1

5

Cutover

Plan

Volume

Test

Stress

Test

Conduct

End User

Training

System

Performance

Review

Project

Team

Org.

Stand. &

Proced.

Technical

Operations

Manual

Progr.

Develp.

EU

Training

Material

Microsoft Word

Documents

Phase 1 - Project Preparation

„

Change Charter - Goals and objectives of Organizational Change Management

„

Project Plan - This is a first cut focusing on milestones and Work Packages; details to come.

„

Scope - Sets the initial definition of the project; input from sales cycle.

„

Project Team Organization - Sets the who of the project: Standards & Procedures - Sets the why and
how of the project.

Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and

defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb
and is the key document for Phase 3.

Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in

the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing &
documentation. Planning - Defines how the configuration will be done and how it will be tested.
Development Programs - Provides details of the external programming requirements. EU Training
Material - End User training material and process documentation.

Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s

capabilities
Cutover Plan - The details of how to move to the production environment and go live
Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going
live

Phase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.

background image

© SAP AG

TSCM52

24-9

SAP AG 2001

Project

Project

Procedures

Procedures

QC

QC

Technical

Technical

Req

Req

.

.

Planning

Planning

Initial Project

Initial Project

Planning

Planning

Project Kickoff

Project Kickoff

Create

Create

Training Plans

Training Plans

Phase 1: Project Preparation - Work Packages (1)

„

The purpose of this work package is to allow you to start detailed planning for the project. There are
many basic issues to resolve at this early stage to ensure the project's success. You should start
planning as early as possible in Phase 1, and make key decisions now.

background image

© SAP AG

TSCM52

24-10

SAP AG 2001

Tasks

Create and Issue Project Charter

Project

Preparation

Project

Preparation

Load Documents into Roadmap

Check Documents from Discovery and Evaluation

Organize Workshop for Detailing Program Charter

Define Project Mission Statement

Create Initial Project Plans

Identify Project Objectives and Measurements

Develop the Change Strategy and Charter

Assemble and Approve Project Charter

„

Accelerators

:

„

Project Charter White Paper

„

Project Plan

„

Budget / Resource Plan (Sample)

„

The purpose of this activity is to define key elements that give overall strategic direction to the
project team for the SAP System implementation. These tasks provide a solid foundation for the
project, and as such, their results should be communicated to all project team members.

„

The input for this activity should be the documents created during the Discovery & Evaluation
phase.

„

Load Documents into Roadmap, Check Documents from Discovery and Evaluation, and Organize
Workshop for Detailing Program Charter
serve as synchronization and interfacing tasks between the
Customer Solution Strategy (CSS) of Discovery & Evaluation and the Implementation Roadmap.

background image

© SAP AG

TSCM52

24-11

SAP AG 2001

Review and Confirm Implementation Plan

Check Strategy for Corporate Rollout

Tasks

SAP

Pro

jec
t

Inputs

Implementation

proposals

Project charter

Data gathered from the

sales cycle

Global Implementation

Strategy

Output

SAP Implementation

Strategy

Review and Refine Implementation Strategy

Accelerators:

„

Verify the use of Preconfigured Systems (PCS) as Implementation

Accelerator

„

Sample Scope Document

Project

Preparation

Project

Preparation

„

The purpose of this activity is to review in detail the implementation strategy for the Project. One
must determine if any changes are needed in terms of Project objectives or methodology. The overall
implementation approach and methodology should now be finalized and confirmed. For some
Projects, it is necessary to also review the overall corporate SAP implementation strategy, especially
if there are multiple, simultaneuous SAP implementation Projects in process throughout the
company.

„

For local rollout projects as part of a global program, the objective of this activity is to understand
and review the global SAP product implementation strategy.

background image

© SAP AG

TSCM52

24-12

SAP AG 2001

Sample Scope Document

Level 1

Level 2

Level 3

Level 4

KEY

Structure

In Scope

BP Owner / Consult

KPI

mySAP.com

Master Data

Business Process

Procurement

Production

Sales and Distribution

Define Business Process Scope at:

Level 1 - SAP Reference Structure

Level 2 - Enterprise Area

Level 3 - Scenario

Level 4 - Process Group

Review and Confirm Implementation Plan

Project

Preparation

Project

Preparation

z

With specific focus on:

„

Company Business Objectives

„

Key Implementation Assumptions

„

Overall Scope - Use accelerator “Sample Scope Document”

„

The purpose of this task is to review the implementation proposal(s), with specific focus on company
business objectives, overall scope, and key implementation assumptions.

„

The sample scope document is used as a basis for outlining the scope of the Project (accelerator
Sample Scope Document). This document may have already been created as a result of pre-sales
activities.

background image

© SAP AG

TSCM52

24-13

SAP AG 2001

Plan and Set up Environment

Define Project Organization and Create Teams

Assign People to Core Change Team Roles

Conduct Project Team Transition Meeting

Create the Extended Change Team

Accelerators:

„

Project Room Requirements White Paper

„

IT Infrastructure Document

Tasks

Determine Project Organization

Project

Preparation

Project

Preparation

„

The purpose of this activity is to create the project organization structure and finalize roles and
responsibilities. Both company employees and consultants will need assignment. An important
aspect of this activity is the set up of a common working area for the project team. It is crucial for
team members to work in an open environment where they are in direct contact, so that they can
discuss the various integration issues and resolve them quickly. This common work area is generally
referred to as a project team room.

background image

© SAP AG

TSCM52

24-14

SAP AG 2001

Project

Project

Procedures

Procedures

QC

QC

Initial Project

Initial Project

Planning

Planning

Project Kickoff

Project Kickoff

Phase 1: Project Preparation - Work Packages (2)

Technical

Technical

Req

Req

.

.

Planning

Planning

Create

Create

Training Plans

Training Plans

„

The purpose of this work package is to establish the principal elements that determine how the SAP
implementation project is to be accomplished. These activities set the groundwork for project
kickoff, and provide a baseline of information to be referenced throughout the implementation. For
all project team members to operate in an effective manner, it is necessary that project standards and
procedures are established at the beginning of the project, and then communicated to all team
members.

„

In case of a local rollout project, reference should be made to the global implementation program.

„

By setting the standards, you:

y

Avoid redundant and unnecessary work

y

Maintain consistency

y

Facilitate communication

background image

© SAP AG

TSCM52

24-15

SAP AG 2001

z

Avoid redundancy and unnecessary work

z

Maintain consistency

z

Facilitate communication

z

Facilitate knowledge transfer to the customer

z

Ensure the entire team understands what is required
of them

z

Tasks build upon one another through the phases

z

Define Project Documentation

z

Create Issue Management Plan

Define Project Management Standards and Procedures

Project

Preparation

Project

Preparation

„

The purpose of this activity is to establish the basic standards and procedures for the project. Some
will apply throughout each phase of the project, while others will only apply at certain times and/or
specific phases. It is important to address these issues during Phase 1 and to establish clear
guidelines. Some of the key issues that ASAP recommends be defined are:

• Steering committee meeting schedule

• How change management is handled

• Project monitoring and status reporting

• Meeting schedules for core team and extended project team

• Overall project communication methods and processes

• Project documentation

„

In case of local rollout projects as part of a global program, two additional key issues to be defined
are:

• Interaction points between local and global teams

• Feedback process from local rollout team to global team

background image

© SAP AG

TSCM52

24-16

SAP AG 2001

Define Strategy for Using SAP Services

Post

Go Live

Post

Go Live

Implementation

Implementation

Sales

GoLive Check

EarlyWatch

5

Solution Review

SAP Review Program

1

2

3

4

ASAP Roadmap Quality Checks

Project

Preparation Business

Blueprint

Realization

Final

Preparation

Go Live &

Support

Project

Preparation

Project

Preparation

„

The purpose of this task is to define the strategy for using the SAP Services during the
implementation phases, as well as for Continuous Business Improvement during production
operation of the SAP System.

„

SAP provides services for certain tasks from the ASAP Roadmap. SAP Services can speed up these
tasks and help to reach a higher level of quality in the implementation project, as well as in
production operation.

„

These services, which are closely linked with the project phases, are tailored to meet your individual
needs.

background image

© SAP AG

TSCM52

24-17

SAP AG 2001

Define System Configuration Standards
Define Testing Strategies
Define Post-Implementation Service

and Support Strategy
Define System Authorization Standards

for Project Team
Define Change Request Management
Define System Enhancement and

Modification Approval Process
Define ABAP Development Standards
Define Support Package Strategy
Define Upgrade Strategy

Define Implementation Standards and Procedures

Project

Preparation

Project

Preparation

„

The purpose of this activity is to establish the overall implementation standards and procedures for
the project. Some of these elements should be established by the technical members of the project
team, and others by the business or functional members. All team members should have input in this
process, and should understand the basic procedures once these have been defined. As with project
management standards and procedures, it is important to address the implementation standards
during Phase 1 and to establish clear guidelines. Some of the key issues to be defined are:

• Overall configuration standards for the project

• Initial system authorization standards

• How system enhancements are handled

• How and when testing occurs

background image

© SAP AG

TSCM52

24-18

SAP AG 2001

Quality

Assurance

System

Production System

Development/Customizing System

Quality Assurance System

Production System

DEV

QAS

PRD

Copy

Transport

ation

DEV

SAP

Client

000

QAS

PRD

Development System

Project

Preparation

Project

Preparation

Data conversions

z

Three database infrastructure with
Development, Quality Assurance
and Production Systems

z

Complete testing of development
and upgrades possible

z

Suitable development environment

Define System Landscape Strategy

„

A three-system infrastructure is the ideal solution for most customers:

y

It affords you unlimited testing of your development.

y

You can implement system upgrades without disturbing your live system.

y

With a separate quality assurance system, you can integrate developments and run consistency

checks on objects for a transport before they are introduced to the production system.

„

This three-system solution supports the R/3 System Landscape (System and Client Deployment
Strategy)
which has the following aims:

y

Development, quality assurance and production should take place in separate environments.

y

In the event of data loss, you should be able to restore a client with consistent data.

y

Transport systems for setting up and maintaining the system infrasturcture are predefined.

y

The infrastructure supports the import of business data from an existing system.

background image

© SAP AG

TSCM52

24-19

SAP AG 2001

Project

Project

Procedures

Procedures

QC

QC

Initial Project

Initial Project

Planning

Planning

Project Kickoff

Project Kickoff

Phase 1: Project Preparation - Work Packages (3)

Technical

Technical

Req

Req

.

.

Planning

Planning

Create

Create

Training Plans

Training Plans

„

The purpose of this work package is to create a project team training plan including business
processes, SAP system functionality, and change management. During this phase, level one or
awareness training should be conducted for the project team.

„

This phase also includes defining an end user training and documentation strategy. This strategy
needs to be developed by reference to, and to support, the overall implementation strategy and
project plan.

background image

© SAP AG

TSCM52

24-20

SAP AG 2001

ASAP Roadmap

Project

Preparation

Business
Blueprint

Realization

Final

Preparation Go Live &

Support

Create Project Team Training Plan

SAP Training Courses:

comprise level 1 (awareness), level 2 (readiness) & level

3 (proficiency)

should ideally have been completed for levels 1 & 2

before starting the Business Process Workshops

address function and use of the SAP product

Note!

Management and project team may have training needs

in addition to SAP product. These should also be
addressed in the training plan

Accelerator:

Training Services for

the Project Team

Project

Preparation

Project

Preparation

„

The purpose of this activity is to create a training plan for the project team involved in the SAP
implementation. While training costs can be viewed as relatively expensive, it is critically important
that the project team be given this training. Once initial training is completed, the project team has a
much better understanding of basic SAP functions, how configuration works, and how to maximize
SAP’s impact to meet your business requirements. This initial training does not cover user training –
it will be addressed later in the implementation.

„

Key factors during this activity include:

y

Background of each team member

y

Specific area of business involvement of team member (application or technical)

y

Timing of team member participation during the implementation.

„

This key factor information can be used to determine the appropriate classes for each team member,
thereby avoiding redundancy, or time spent in classes that are not applicable, and to make sure the
course material is timed accordingly. When developing this plan, decide which courses are to be
conducted at an SAP training center, or at the company site. The project team training plan is
regularly updated throughout the life of the implementation.

background image

© SAP AG

TSCM52

24-21

SAP AG 2001

Tasks

End User Training and Documentation Strategy

Project

Preparation

Project

Preparation

Develop End User Needs Assessment

Develop End User Training and Documentation
Project Plan

Develop End User Proposal and Conduct
Project Proposal Meeting

„

Accelerators:

„

End User Training and Documentation Needs Assessment

„

End User Training and Documentation Methodology

„

The purpose of this activity is to develop an end user training and documentation strategy and to
develop a work plan. You will begin with an assessment of the needs of the end users, develop a
project work plan, and then create a project plan that will be the basis of your end user training and
documentation implementation.

background image

© SAP AG

TSCM52

24-22

SAP AG 2001

Project

Project

Procedures

Procedures

QC

QC

Initial Project

Initial Project

Planning

Planning

Project Kickoff

Project Kickoff

Phase 1: Project Preparation - Work Packages (4)

Technical

Technical

Req

Req

.

.

Planning

Planning

Create

Create

Training Plans

Training Plans

„

The objective of this work package is to identify the technical requirements needed to implement the
SAP technical environment, clarify the customer’s expectations, review hardware sizing, and procure
the required hardware.

„

During the planning, keep in mind that all required SAP systems are unlikely to be procured and
installed at the same time. The development system is the initial system and is needed at the start of
an SAP implementation project. Early on, this may be the only SAP system in the system landscape.
Other required SAP systems, such as the quality assurance and production systems, are not needed
until a later phase; therefore, part of the planning includes taking expected delivery lead-times into
consideration so that subsequent systems and hardware can be ordered in time.

background image

© SAP AG

TSCM52

24-23

SAP AG 1999

Identify Technical Requirement

Technical Requirements Planning for Local Projects

Procure Hardware

Project

Preparation

Project

Preparation

„

Identify technical requirements: The purpose of this activity is to identify the technical infrastructure
needed to implement R/3, and to clarify the customer's expectations.

„

Procure Hardware: The purpose of this activity is to procure the hardware needed for the SAP
environment and place the hardware order with the appropriate vendor(s). Carefully plan the
procurement of the subsequent systems (quality assurance and production systems, additional
application servers, storage devices, etc.) to avoid unexpected lead times that could impact the SAP
implementation schedule. Hardware procurement lead-times can vary from days, weeks, to even
months.

background image

© SAP AG

TSCM52

24-24

SAP AG 2001

Project

Project

Procedures

Procedures

QC

QC

Initial Project

Initial Project

Planning

Planning

Project Kickoff

Project Kickoff

Phase 1: Project Preparation - Work Packages (5)

Technical

Technical

Req

Req

.

.

Planning

Planning

Create

Create

Training Plans

Training Plans

„

The purpose of this work package is to formally announce the initiation of the SAP project to the
whole organization. This kickoff meeting should include the presentation of the overall goals,
detailed task plans, and processes. Consultants, steering committee, senior management, project
managers from the company, SAP and any other implementation partners must be involved. The
kickoff meeting is focused on the organization as a whole, while the project team standards meeting
is focused on the project team.

„

It is important that – as part of the Change Management – the kickoff meeting is followed by regular
communication to the rest of the organization about the progress, achievements, etc.

„

In case of a local rollout project as part of a global program, reference should be made to the global
implementation program; the global rollout manager and the global rollout core team must be
involved as well.

background image

© SAP AG

TSCM52

24-25

SAP AG 2001

Motivate the individuals involved and

bring them together as a team

Explain the implementation strategy,

timeline, and project goals and
objectives

Clarify team member roles,

responsibilities, and common objectives

Kickoff Meeting

Project Introduction to the Whole
Organization

Project

Preparation

Project

Preparation

„

The first purpose of this activity is to inform all staff members involved about the start of the project.
The goal here is to:
- Introduce the people involved in the project
- Present the functionality and benefits of the new solution
- Introduce SAP and the implementation partners and explain their roles in the process
- Explain the project plan and the different deliverables throughout the process
- Show commitment of the Executive Management to this project
- Generate some positive excitement amongst the end-user community

„

The second purpose of this activity is to arrange and conduct a meeting amongst all people directly
involved in the project to accomplish the following goals:
- Motivate the individuals involved and bring them together as a team
- Explain the implementation strategy, timeline, and project goals and objectives
- Clarify team member roles, responsibilities, and common objectives
- Outline Key Organizational Change Management goals and objectives

„

This milestone activity is a critical checkpoint that officially launches the SAP implementation
project to the entire organization.

„

Be sure to allow adequate time for questions and answers, as some issues could require clarification.

„

In case of a local rollout project as part of global program, reference should be made to the global
implementation program.

background image

© SAP AG

TSCM52

24-26

SAP AG 2001

Project

Project

Procedures

Procedures

QC

QC

Initial Project

Initial Project

Planning

Planning

Project Kickoff

Project Kickoff

Phase 1: Project Preparation - Work Packages (6)

Technical

Technical

Req

Req

.

.

Planning

Planning

Create

Create

Training Plans

Training Plans

„

The purpose of this work package is to provide final verification of all prior project planning and
deliverables from this phase. It is critical that regular quality checks be performed throughout the
phase, as tasks are completed. All issues regarding scope, project environment, and initial technical
setup must be addressed.

„

There are two types of quality reviews mentioned in this work package. The first is an internal
review conducted by the project leadership team. The second is an independent external review using
the SAP Review Program.

background image

© SAP AG

TSCM52

24-27

SAP AG 1999

QC

Perform Quality Check and Obtain Approval

Accelerators:

SAP Project Review Program

SAP Service

Perform Internal Quality Check

Project Preparation Review

Obtain Approval

„

Perform Internal Quality Check: The purpose of this activity is to collect all deliverables and to
review them together for completeness and accuracy. Quality checks are performed as specific tasks
are completed. However, it is also critical to review deliverables in total because individual results
from one task can have an adverse impact on another area of the project.

„

Project Preparation Review: The purpose of this activity is to recognize potential project risk areas
during the Project Review at an early stage. This reduces the possibility of an extended project
timeline. It leads to a faster implementation and increases the customer’s level of confidence.

„

Obtain Approval: The purpose of this activity is to obtain the approval from the customer. Upon
completion of this activity, signoff is obtained and the project proceeds to the next phase.

background image

© SAP AG

TSCM52

24-28

SAP AG 1999

Unit

Unit

Unit

Topic

Topic

Topic

Legend:

Legend:

Legend:

Phase 1
Project Preparation

Phase 2

Business Blueprint

Phase 3
Realization

Implementation
Roadmap

Phase 4

Final Preparation

Phase 5
Go Live & Support

Overview Diagram: Implementation Roadmap (2)

background image

© SAP AG

TSCM52

24-29

SAP AG 2001

Phase 2: Business Blueprint: Objectives

Upon completion of this topic, you will be able to:

z

Explain the activities and tasks that are
important in the Business Blueprint Phase
of the SAP implementation project

z

Explain the importance of the Question and
Answer Database (Q&Adb)

background image

© SAP AG

TSCM52

24-30

SAP AG 2001

The Purpose of Phase 2: Business Blueprint

Project

Preparation

Business

Blueprint

Realization

Final

Preparation

Go Live &

Support

ASAP Roadmap

„

The purpose of this phase is to create the Business Blueprint, which is a detailed documentation of
the results gathered during requirements workshops. The Business Blueprint details the agreed
business process requirements of the company. It documents the common understanding of how the
company intends to run its business within the SAP system.

„

During this phase, you also:

y

Refine the original project goals and objectives

y

Define the Baseline scope

y

Refine the overall project schedule and implementation sequence

background image

© SAP AG

TSCM52

24-31

SAP AG 2001

Business Blueprint - Roles & Key Focus

Project

Project

Mgmt.

Mgmt.

Refine Project

Plan

Comm./ Doc.,

Issue Mgmt.

Project

IMG/Master

Records

Team Bldg.

Activities

Tech Design/

Set up Dev

Env/ Install

h/w, printers,

networks

Steering

Meetings

Org. Impact/

Risk / Sponsor

Sign-Off

Quality Check/

Sign-Off

Attend PTT

Org.

Org.

Chg

Chg

.

.

Mgmt.

Mgmt.

Project Team

Project Team

Training

Training

Config

Config

Sys

Sys

Admn

Admn

Org.

Org.

Structure

Structure

Business

Business

Proc

Proc

.

.

Def

Def

.

.

QC

QC

Training

Effectiveness

EUT & Doc.

strategy/delvy.

Attend PTT

Attend PTT

Approve Tech

Design

Org Structure

Guidelines/

Workshops

Org. Structure

Guidelines/

Workshops

Determine

Enhancements

Assemble Bus

Blueprint

Org

Optimization

Analysis

Attend PTT

Sign-Off

Set up Proper

Authoriz.

Org. Impact/

Risk / Sponsor

Steering

Steering

Sponsors

Sponsors

Proj

Proj

. Mgmt.

. Mgmt.

Consultant

Consultant

Customer

Customer

Technical

Technical

Training

Training

Change

Change

Security

Security

***************

Review,

Status Meetings

& Steering

Meetings

**************

***************

Requirements

BP/ARICE

Deficient

Areas

**************

Role
Groupings

Phase

Content

„

These are the primary roles in an SAP implementation (all the roles are defined in the
Implementation Assistant).
Steering Committee - members include Project Sponsors, the SAP Consulting Manager (and/or the
TeamSAP Coach), and project managers. The committee is also the primary source for the
company’s long-term goals and vision, sets priorities, approves scope, and resolves company-wide
issues.
Project Sponsor - Directly communicates the company’s long-term goals and visions and are
members of the steering committee.
Project Management - TeamSAP Project Manager and Customer Project Manager
Consultant - TeamSAP Members, application, cross application, business process
Customer - Project Team Members (business process, power users)
Technical - Customer or consultants for System Administration and Technical, help desk provider
Training - Training & Documentation, Project Manager/Lead, Training and Documentation
Developer/Instructor, Training Coordinator, Training Technology Administrator
Change -These are dedicated individuals assigned to manage the organizational change management
processes: Risk Assessment, Communication, Sponsorship and Leadership, Skills Development,
Knowledge Transfer or Business Optimization.
Security - Authorization, Administration, or Internal Auditor responsible for managing the system
security and authorization environment and may be combined with other (technical) administrative
roles.

„

Shared items are marked by the ************ brackets.

background image

© SAP AG

TSCM52

24-32

SAP AG 2001

Master Lists

Microsoft Excel
Spreadsheets for
Development, Organization,
Business Processes and
Authorizations

Project

Charter

BPP

Documents of an ASAP Project

Q&Adb

Substructures:

Business Strategy
Organization
General Settings
Master Data
Business Process
Cross Application
Development

Business

Blueprint

Project

Plan

Scope

Config.

Plan

Testing

Plan

Unit testing
Test scenario
Integration

4

3

2

1

5

Cutover

Plan

Volume

Test

Stress

Test

Conduct

End User

Training

System

Performance

Review

Project

Team

Org.

Stand. &

Proced.

Technical

Operations

Manual

Progr.

Develp.

EU

Training

Material

Microsoft Word

Documents

Phase 1 - Project Preparation

„

Change Charter - Goals and objectives of Organizational Change Management

„

Project Plan - This is a first cut focusing on milestones and Work Packages; details to come.

„

Scope - Sets the initial definition of the project; input from sales cycle.

„

Project Team Organization - Sets the who of the project: Standards & Procedures - Sets the why and
how of the project.

Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and

defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb
and is the key document for Phase 3.

Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in

the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing &
documentation. Planning - Defines how the configuration will be done and how it will be tested.
Development Programs - Provides details of the external programming requirements. EU Training
Material - End User training material and process documentation.

Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s

capabilities
Cutover Plan - The details of how to move to the production environment and go live
Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going
live

Phase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.

background image

© SAP AG

TSCM52

24-33

SAP AG 2001

QM

QM

Phase 2: Business Blueprint - Work Packages (1)

Organizational

Organizational

Structure Definition

Structure Definition

Business Process

Business Process

Definition

Definition

Project Management

Project Management

Technical Design Planning

Technical Design Planning

Organizational Change Management

Organizational Change Management

Design Training Plans

Design Training Plans

Establish Development System Environment

Establish Development System Environment

background image

© SAP AG

TSCM52

24-34

SAP AG 2001

Project Management

Project Management

Checklist

Checklist

Prepare and attend

status meetings

Prepare and attend

steering committee
meeting

Correct project

variances

Refine project plan
Change Management
Team-building

activities

9

9

9
9
9

9

Configuration

D

o

cu

men

tat

io

n

Project Management

„

The purpose of this work package is to establish a proper cycle of project management activities,
which ensure that the implementation project is on target. It determines all project planning,
controlling and updating activities. It also identifies where changes in the relationship between
business processes and the organizational structure need to be managed, in consultation with
departmental management. The same work package is also in the subsequent phases.

„

The Project Review Program is provided as an SAP service. Reviews can be scheduled throughout
the duration of the project. A review provides an independent and objective management verification
of a company´s SAP product implementation project, identifies any risks to the project goals and
recommends appropriate corrective actions.

background image

© SAP AG

TSCM52

24-35

SAP AG 2001

Accelerators:

Activities

Organizational Change Management

Business

Blueprint

Business

Blueprint

n

OCM Implementation White Paper

n

Communications White Paper

n

Organizational Optimization White Paper

Initiate and Conduct OCM

Risk Assessment

Plan and Establish Sponsorship

and Leadership Process

Plan and Establish

Communication Process

Implement Business Optimization Process

Measure/evaluate effectivity of steps taken

Determine potential

risks

Set priorities,

bearing all possible

outcomes in mind

Establish and take

steps designed to

minimize risks

„

The purpose of the Organizational Change Management work package is to address the
organizational and human resource factors that have an impact on the SAP implementation.

„

The Organizational Change Management work package includes a series of change processes that
allow the change team to manage organizational risks.

„

These Organizational Change Management processes ensure that the change team understands and
manages the company’s perceptions of and responses to the changes that will occur after the
implementation of the SAP System.

„

During the Blueprint Phase the Organizational Change Management creates the foundation for a well
integrated Organizational Change Management program.

background image

© SAP AG

TSCM52

24-36

SAP AG 2001

Conduct Project Team Training

Analyze End User Training and

Documentation Strategy

Prototype End User Training and

Documentation Deliverables

Accelerators:

„

Project Team Training Template

„

Curriculum Planner

„

Training Environment Setup and Considerations

„

Knowledge Warehouse (Information)

Activities

Design Training Plans

Business

Blueprint

Business

Blueprint

„

The purpose of this work package is to finalize and conduct level 2 of the project team training.
During the training business blueprint phase, the end user training and documentation strategy is
carefully analyzed. The training team develops the training curriculum and selects the delivery tools.
End user training and documentation prototypes are demonstrated during this phase.

„

The purpose of the Conduct Project Team Training activity is to conduct Level 2 project team
training so that team members can obtain an overview of the business processes or technical features
in their area. This training is a prerequisite to the detailed business process courses and detailed
technical courses (Level 3 training), and enables the project team to start to match their company
requirements with SAP functions during the Business Blueprint phase.

„

The purpose of the Analyze End User Training and Documentation Strategy activity is to analyze the
end user training and documentation strategy, and finalize the plan for developing the training
content, training documentation, and training delivery.

„

The purpose of the Prototype End User Training and Documentation Deliverables activity is to
design and develop a training and documentation prototype, and analyze and determine the system
requirements necessary for conducting training. The tasks involved with this activity will occur at
times simultaneously with the tasks in Analyze End User Training and Documentation Strategy.

background image

© SAP AG

TSCM52

24-37

SAP AG 2001

Phase 2: Business Blueprint - Work Packages (2)

Project Management

Project Management

Organizational Change Management

Organizational Change Management

Training in the Business Blueprint Phase

Training in the Business Blueprint Phase

Business Process

Business Process

Definition

Definition

Technical Design Planning

Technical Design Planning

Establish Development System Environment

Establish Development System Environment

QM

QM

Organizational

Organizational

Structure Definition

Structure Definition

„

The purpose of the Technical Design Planning work package is to

• Further define the planning that was started in phase one.

• Document the technical design.

„

You should anticipate the future needs of additional SAP systems and hardware as the project
continues and begin the technical design planning for them as early as possible.

„

The purpose of the Establish Development System Environment work package is to install and set
up the development system for the start of implementation.

„

For local rollout projects, as part of a global implementation project, the Global Solution Package
will be used to set up this environment. Please refer to the task Getting Familiar with Global
Solution Package
in Phase one of the Rollout Roadmap.

background image

© SAP AG

TSCM52

24-38

SAP AG 2001

Technical Design Planning

Set up Development Environment

System Administration Procedures

Business

Blueprint

Business

Blueprint

Accelerators:

„

IT Infrastructure Document

„

SAP Web Installation Guides

„

SAP Software and License Keys

Activities

Activities

Establish Development Environment

Upgrad

e

Srateg

y

Create Technical Design

„

Create Technical Design: The purpose of this activity is to define and document your technical
design. It is recommended that you seek support from your hardware partner for this work.

„

Set Up Development Environment: The purpose of this activity is to install and configure the
technical environment for the development system. This activity includes installing the hardware,
verifying the technical environment, installing the SAP software and frontend components, and
configuring and securing the technical environment of the SAP System.

„

System Administration Procedures: The purpose of this activity is to define and verify the system
administration procedures for the development system. It is an ongoing process throughout the
Business Blueprint phase.

background image

© SAP AG

TSCM52

24-39

SAP AG 2001

Available now

http://service.sap.com

For customers

and Partners

K

E

Y CO

MP

O

N

EN

T

S

The SAP Service Marketplace is SAP´s one-stop Internet platform that provides

personalized access to all services necessary to design, build and maintain a

high quality solution

Benefits

„

Easy, one-stop access to

SAP services - anytime,

anywhere

„

A full range of services to

ensure solution

completeness

„

Information that is easy to

find and understand, as

you navigate easily

through well-organized

topics - and you can

personalize the site to suit

your needs

Support Services

„

Submit messages, access support packages and SAP
notes

„

Request remote service sessions like Early Watch

Consulting & Education Services

„

Request hardware sizing, consulting

„

Online booking of training sessions worldwide

Information Services

„

Detailed information around the SAP solutions

„

SAP related new offerings

„

Download best practices materials

SAP Service Marketplace

background image

© SAP AG

TSCM52

24-40

SAP AG 2001

Phase 2: Business Blueprint - Work Packages (3)

Project Management

Project Management

Organizational Change Management

Organizational Change Management

Training in the Business Blueprint Phase

Training in the Business Blueprint Phase

Business Process

Business Process

Definition

Definition

Technical Design Planning

Technical Design Planning

Establish Development System Environment

Establish Development System Environment

QM

QM

Organizational

Organizational

Structure Definition

Structure Definition

„

The purpose of this work package is to define the enterprise organizational structure using SAP
organizational units, such as company codes and sales organizations.

„

In conducting the organization structure workshop, topics such as the following need to be
addressed:

• What enterprise areas and business processes will be used in the system?

• Which organizational units within the company will be affected by the implementation?

„

For a rollout project, many of the organizational structure elements may already have been included
in the template. For the part remaining, documentation for the intended solution including naming
conventions will usually be provided by the global solution package from the Global Template
project. The organizational structure(s) will then have to be reviewed, validated and completed.

background image

© SAP AG

TSCM52

24-41

SAP AG 2001

Schedule and Prepare Organization

Structure Workshop

Conduct Organization

Structure Workshop

Recommend and Approve

Organization Structure

Accelerators:

Organization Structure Presentation
Enterprise Modeling - Consultant's Handbook
Sample Scope Document

Tasks

1

1

SAP Reference Model

Organization

Business Strategy

Define Business Organization Structure

Business

Blueprint

Business

Blueprint

„

The purpose of this activity is to prepare for business organization structure workshops to define the
organizational structure of the company within the system. The organizational structure is
established to give structure to the logistic and financial enterprise areas.

background image

© SAP AG

TSCM52

24-42

SAP AG 2001

QAdb

Documents

Q&Adb Structure

1

1

QAdb

QAdb

QAdb

User

Issues

Report

Development

Basis

SAP Reference Structure

1

User Roles

1

1

1

1

Training and Documentation

Cross-application

Business Processes

Master Data

1

General Settings

1

Organization

1

1

1

mySAP.com

KPI

Business Strategy

„

The section under Business Strategy sections contain items designed to collect information about the
general business strategy and the implementation.

„

The Key Performance Indicators (KPI) substructure is designed to assist you measure, analyze and
improve the value added process and business performance in your enterprise.

„

The mySAP.com substructure is there to assist you analyze and document how you might implement
the SAP Internet solution in your enterprise.

„

The Organization substructure contains items that describe the R/3 system organization structure.
This is the framework in which the R/3 System is configured.

„

The General Settings section contains elements of the R/3 Implementation Guide (IMG). This is of
overall importance for Business Blueprint phase to set up the R/3 system properly.

„

The Master Data section contains items that describe the master data structure that controls the
behavior and implementation of an R/3 System.

„

The Business Processes area of the Q&Adb contains the process structure items as represented in the
SAP Reference Structure.

„

The Cross-application section refers to all data objects (tables, entities or processes) that relate to
more than one business application.

„

The Training and Documentation section collects information about the planned training and
documentation standards in an SAP product implementation.

„

The User Role node provides all the SAP user roles (based on Release 4.6B of the R/3 System). The
project team can use these roles to analyze the project-specific requirements for user profiles.

„

The content of the Development area is created automatically by the application. It is designed to
hold all functional specification documentation data that you entered in the Associated Items box

„

The Documents substructure of the Q&Adb allows you to store and manage all documents related to
the entire life cycle of your SAP System. For example the Business Blueprint document and drafts
thereof would be stored here.

background image

© SAP AG

TSCM52

24-43

SAP AG 2001

QAdb

Documents

1

1

QAdb

QAdb

QAdb

User

Issues

Report

Development

Basis

SAP Reference Structure

1

User Roles

1

1

1

1

Training and Documentation

Cross-application

Business Processes

Master Data

1

General Settings

1

Organization

1

1

1

mySAP.com

KPI

Business Strategy

Associated Items 1

Business Analysis

Question

CI Template

BP Transaction

User Roles

Project Documentation

SAP Documentation

IDES Documentation

Associated Items

„

The Question(s) enable you to gather requirements on specific business scenarios and their
processes. A question may appear within several structures. The answer to a question on a specific
occurrence within any structure is visible on all other occurrences using that question. While answers
given to a question are visible at all occurrences, questions can only be answered and answers can
only be changed at the current structure level. These questions are open-ended and promote the flow
of information between you and the consultants who will configure your system. Using your answers
as a guide, consultants define your company’s requirements in detail and adapt process models to
reflect your company’s needs.

„

The User Roles enable consultants in the Blueprint phase to identify, adapt and describe SAP-
delivered user roles based on project-specific requirements.

„

The CI template sections form the heart of the Business Blueprint document. It is important to
provide as much information as possible when entering your answers in these sections. In some cases
the information may not be known at the Blueprint stage, if this occurs, it should be noted in the CI
template answers. For example, when you enter the Authorization Considerations question during
the Business Blueprint phase only high level information is available. As this changes, the Q&Adb
should be updated with detailed authorization requirements.

„

During the initial Q&Adb setup, you specified the path to SAP and IDES documentation. This
documentation is available for view only and cannot be changed. If an SAP or IDES document is
available for a selected function, the name of the document displays in the Associated Items box.
Click the document to view it.

„

You may add, view, or delete documentation to the Project Documentation folder in the Associated
Items box. It is recommended that all documents are put into the Project Documentation directory so
that they can then be found in the Q&Adb directory.

background image

© SAP AG

TSCM52

24-44

SAP AG 2001

SAP Reference Structure

Associated Items 2

Information

Note:

Availability of Associated

Items Objects depends on

Structure Level

Functions

Input / Output

Organizational Units

Project Documentation

Key Performance Indicator

Where used Enterprise Area

Where used Scenario

Associated Items

Not Yet Processed

In Process

On Hold

Completed

Predefined

Technical Analysis

Conversions

Interfaces

Reports

Forms

Other Development

Status

„

The Associated Items frame which appears on the right side of the Q&Adb application screen
represents a user interface work area and a display area for user-specific information. The range of
possible associated items are indicated above. However, note that the actual associated items
displayed at any one time in the Q&Adb will be those linked to the SAP reference structure item
currently selected.

„

The Technical Analysis tab allows you to specify development requirements for your project. This
information is used to draw up a technical specification from the Development List (DL) that forms
the basis of programming. There are specific functional and technical specification templates for
each of the areas on the Technical Analysis tab.

background image

© SAP AG

TSCM52

24-45

SAP AG 2001

Compose Project Structure

SAP Project Reference Structure

SAP Product Reference Structure

R/3

BBP

SAP Reference Structure

SAP Reference Structure

1

1

Development

Basis Components

SAP Reference Structure

1

Training and Documentation

1

1

1

1

User Roles

Cross-Application Components

Business Processes

Master Data

1

General Settings

1

Organization

1

1

1

mySAP.com

KPI

Business Strategy

1

1

Development

Basis Components

SAP Reference Structure

1

Training and Documentation

1

1

1

1

User Roles

Cross-Application Components

Business Processes

Master Data

1

General Settings

1

Organization

1

1

1

mySAP.com

KPI

Business Strategy

CRM

„

You can map SAP Reference Structures of various mySAP.com components in a Q&Adb. This
enables you to create a Business Blueprint for a mySAP.com solution that consists of more than one
mySAP.com component.

Compose Project Structure:

The project manager can group together SAP Reference

Structures of various variants, such as R/3, APO, and BW. This enables the project team to
process the entire implementation scope in one Q&Adb.

• Before the project reference structure is created, the SAP Reference Structure on the left of the
Q&Adb screen area only contains structure items from level 1; in other words, the structure still
has to be "filled." The project manager and business process team can define the project scope
under Administration -> Compose project structure. The Create Project Reference Structure
dialog box displays the SAP Reference Structures of all variants installed as indicated on the
right under “SAP Product Reference Structure”.

• The structure items selected as in scope can then be transferred from the SAP Product
Reference Structure to the SAP Project Reference Structure (from right to left) and processed in
the Q&Adb.

background image

© SAP AG

TSCM52

24-46

SAP AG 2001

Scoping

Edit

...
Project scope

...
Set in scope
...

3

Structure Item

D

2

Structure Item

B

2

Structure Item

C

SAP Reference Structure

1

Structure Item

A

3

Structure Item

E

SAP Reference Structure

1

Structure Item

A

2

Structure Item

C

3

Structure Item

E

View

Reports

„

Before you begin answering questions, decide which structure items are valid and appropriate for
your business. Setting these items In Scope delimits the information gathering of the Q&Adb to your
specific business.

„

Any one or all hierarchy items can be set in scope by right-clicking on that item in the tree view and
choosing Set in scope.

„

In Scope areas appear in yellow for easy identification.

„

In Scope status can be removed from individual hierarchy items as necessary by clicking the checked
Set in scope menu item.

„

If you would like to see only the items in scope, choose View-> Project scope.

background image

© SAP AG

TSCM52

24-47

SAP AG 2001

Set Owner

SAP Reference Structure

1

Structure Item

2

Structure Item

3

Structure Item

Business Owner

Select Owner

Consultant

„

An Owner is person who is responsible for one or many Structure items on different levels.

„

You can assign an owner from the customer’s project team and/or a consultant to each structure item.
You can:

• Generate View by Owner
This view displays only the structure items assigned to a particular owner. For example, you can
display structure items for which you are the owner or for which you have assigned a particular
team member as owner.

• Use the Owner report option
This means that only those structure items that are assigned to you or to one of your team
members are included in the report.

• Include the name of the owner for each structure item in your report

„

Setting ownership ensures that a warning message appears if a user changes a structure item which is
assigned to another owner.

background image

© SAP AG

TSCM52

24-48

SAP AG 1999

Issues Database

Details

Details

Priority

Priority

,

,

Status, Project phase,

Status, Project phase,

Responsible

Responsible

Action Item Prority, Resolution

Action Item Prority, Resolution

Effort Category, Planned, Actual,

Effort Category, Planned, Actual,

Remainung

Remainung

Documents MS-XL, MS-Word, MS-PP

Documents MS-XL, MS-Word, MS-PP

All

All

by Classification

by Classification

All by Project Phase

All by Project Phase

All

All

Issues

Issues

Closed Issues

Closed Issues

....

....

Issue Editor and Documentation

Issue Editor and Documentation

Open Issues

Open Issues

Unsolved

Unsolved

Problems

Problems

Edit View Reports

Administrative
Issues

All Issues
Current View

Listing

Listing

in

in

EXCEL

EXCEL

Table

Table

„

The Issues substructure helps the project management team to record, monitor, and manage open
questions or unforeseen problems that arise during implementation. Issues may hinder project
progress or even jeopardize its success if a solution is not found. They may have an impact on the
project scope, budget, timeline, and resources.

„

When you log on, the system informs you of any outstanding issues for which you are responsible.
You can choose to go directly to your open issues. The system will also display a message telling
you if you have been informed about an issue.

background image

© SAP AG

TSCM52

24-49

SAP AG 1999

Business Strategy

2

General Enterprise Strategy

2

Markets

2

Procurement Strategy

SAP Reference Structure

1

Business Strategy

Question

Project Documentation

Business Analysis

Status

Business

Blueprint

Business

Blueprint

„

In this substructure, you can gather information on your enterprise’s general business strategy. Using
questions and customer input templates, you are able to, for example, analyze your business strategy,
describe your corporate culture and give details of your competitive and market position. The
information you enter here is of strategic importance to your enterprise and essential for mapping
your enterprise specific requirements to the SAP System.

background image

© SAP AG

TSCM52

24-50

SAP AG 2001

mySAP.com

SAP Reference Structure

1

mySAP.com

2

Workplace

3

Buy Side

2

The Marketplace

3

Sell Side

Question

CI Template

Project Documentation

Business Analysis

Status

Business

Blueprint

Business

Blueprint

„

In the mySAP.com substructure, you can analyze and document how to implement your SAP
Internet solution in your enterprise. The questions and CI templates contained here focus on the
Workplace and the Marketplace. The project documentation stored in this substructure provide
guidelines for successfully implementing mySAP.com.

„

Customer Input (CI) templates exist for all structure items. Using these templates you can document
and analyze the main areas of the mySAP.com substructure. The information you enter here is
essential for drawing up your Business Blueprint.

background image

© SAP AG

TSCM52

24-51

SAP AG 2001

Organizational Structure

SAP Reference Structure

1

Organization

2

Procurement....

3

Company Code

2

Cross-application....

3

Controlling Area ...

Business Analysis

Question

CI Template

Project Documentation

SAP Documentation

IDES Documentation

Status

Information

Business

Blueprint

Business

Blueprint

„

The Organization structure level contains items that describe the system organization structure in
which framework the SAP system is configured. In the Q&Adb, questionnaires facilitate gathering
requirements on the company’s structure and processes that allow an initial mapping of the
company’s business to a proposed SAP organizational structure. The answers to the questions form
part of the Business Blueprint.

„

The second level contains the available enterprise areas (e.g. Sales and Distribution). It is not
recommended that you change or enhance this level of the organization structure.

„

A third level further defines the organization (e.g. Sales area data).

background image

© SAP AG

TSCM52

24-52

SAP AG 2001

Users

Users

Issues

Issues

Status

Status

Master lists

Master lists

BPML

BPML

OSL

OSL

DL

DL

AL

AL

Business Blueprint

Business Blueprint

-

-

-

mySAP

mySAP

.com

.com

-

Reports (Business Organization Structure)

Edit View Reports

Business strategy

Business strategy

Scope document

Scope document

Reports

Reports

-

Scope document

Business strategy
mySAP.com
Business Blueprint

All
KPI

Organizational structure

General settings
Master data
Business processes
Cross-application
components
User roles
Training and
documentation
Development

Master lists

Organizational Structure
List

Business Process Master
List
Development List
Authorization List

Status Report
Administrative
Issues

-

-

Business

Blueprint

Business

Blueprint

„

Reports allows you to display project documentation in different forms, and creates a report structure
in the Q&Adb.

background image

© SAP AG

TSCM52

24-53

SAP AG 2001

Phase 2: Business Blueprint - Work Packages (4)

Project Management

Project Management

Organizational Change Management

Organizational Change Management

Training in the Business Blueprint Phase

Training in the Business Blueprint Phase

Business Process

Business Process

Definition

Definition

Technical Design Planning

Technical Design Planning

Establish Development System Environment

Establish Development System Environment

QM

QM

Organizational

Organizational

Structure Definition

Structure Definition

„

Business Process Definition

The purpose of this work package is to determine the company requirements based on SAP business

processes, to provide the required functions. The business process definitions create your Business
Blueprint.

„

In the case of a local rollout (an implementation project itself part of an overall, global
implementation comprising a number of implementation projects), most of the company
requirements should already have been determined at the global, program level and mapped to the
corresponding SAP settings.

„

Note that you must have defined your organizational structure before proceeding to business
processes.
In case of a local rollout, the Global Solution Package must have been delivered. This is the
definition of the core requirement common across all implementations in a company’s multi site
and/or multi national implementation of SAP product.

background image

© SAP AG

TSCM52

24-54

SAP AG 2001

Business

Blueprint

Business Process

Questions

SAP Reference

Structure

INPUT

OUTPUT

Business Process

Definition

Technical Analysis

Functional

Specifications

Organizational

Structure

Master

Lists

Business Analysis

Questions

CI Template

BP Transactions

Business Process Definition

Business

Blueprint

Business

Blueprint

„

After the definition of the organizational structure, you define the business processes of the company
in terms of the R/3 System.

„

The Q&Adb is the tool supporting the definition of the business processes. You can use the CI
(Customer Input) template and the business process questions within the Q&Adb to support the
preparation and completion of the business process definition. For detailed analysis, you can access
external tools for modeling the business processes via the Q&Adb.

„

Generating the Business Blueprint gives you the company’s business process requirements in one
document.

„

Generating the Business Process Master List gives you the business processes which are in scope for
Customizing in the Realization Phase.

background image

© SAP AG

TSCM52

24-55

SAP AG 1999

Activities

Prepare for Business Process Workshops

Conduct General Requirements Workshops

Accelerators:

Business Consulting Approach to Improve KPIs

Sample Measure Driver Tree

Sample Business Blueprint

Sample

Sample

Scope Document

Scope Document

Input

Input

DE

DE

US

US

CH

CH

DM

DM

USD

USD

CHF

CHF

ISO

ISO

Norms

Norms

Numbering systems

Numbering systems

, Chart of

, Chart of

accounts

accounts

...

...

Business

Blueprint

Business

Blueprint

Business Process Definition

„

Prepare for Business Process Workshops: The purpose of this activity is to ensure efficient business
process workshops. This means determining who attends, which business processes are discussed,
and other applicable topics. To ensure effective meetings, you should send all relevant materials and
business process guidelines to the participants prior to the workshops.

„

Conduct General Requirements Workshops: The purpose of this activity is to analyze your
standardization aims (general settings) and the constraints to which they are subject. This activity
deals with determining whether standardization is, or ought to be, one of your objectives. Some of
the items which should be standardized include:

• Numbering systems for data records

• Charts of accounts

• Statistics

• Units and measurement

• Balance sheets and profitability analyses

• Handling of procedures, rules and standards for data transfer between application systems

background image

© SAP AG

TSCM52

24-56

SAP AG 2001

General Settings and Master Data

SAP Reference Structure

2

Countries

2

Currencies....

1

General Settings

1

Master Data

3

Material Master....

2

General Master Data....

3

Serial Numbers....

Technical
Analysis

Business Analysis

Question

CI Template

BP Transaction

Project Documentation

SAP Documentation

IDES Documentation

Information

Status

Business

Blueprint

Business

Blueprint

„

In the General Settings substructure, you can determine general settings in line with the
Implementation Guide (IMG), such as currencies, that apply across your entire SAP System. These
settings are required to set default parameters in the SAP System

„

In the Master Data substructure, you can see the structure of master data in the SAP System. It is
organized according to enterprise area. General master records, for example, Material Master, Work
Center
, Customer/Vendor Master Record are located below the enterprise-specific master data items
in the tree structure.

background image

© SAP AG

TSCM52

24-57

SAP AG 2001

Conduct Business Process Workshops (1)

Determine the Need for Extended Functions

Determine Forms Requirements

Determine Reporting Requirements

Determine Required Interfaces

Determine Conversion Requirements

Determine Required Enhancements

Clarify Deficient Areas

Analyze CRM Requirements for BW Integration

Business

Blueprint

Business

Blueprint

„

Conduct Business Process Workshops
The purpose of this activity is to conduct the business workshops to determine and complete all
requirements including:
Business

process

Reporting
Interfaces

Conversions

Enhancements
Authorizations

The business process workshops are a crucial part, as all the results gathered during the workshops
subsequently create the Business Blueprint. It is necessary to use the questions not yet answered in
the Q&Adb to determine business requirements, and to complete a Customer Input (CI) template for
each business process.

„

In case of a local rollout, the general company requirements regarding standardization aims have
usually been completed during template development. Nonetheless they should be kept in mind and
local detailed requirements coming up during this task should be fed back to the core team,
especially if deficient areas are detected.

background image

© SAP AG

TSCM52

24-58

SAP AG 1999

Conduct Business Process Workshops (2)

4

Process Groups

5

Processes

2

Enterprise Areas

3

Scenarios

SAP Reference Structure

1

Business Processes

Technical
Analysis

Business Analysis

Question

CI Template

BP Transaction

User Roles

Project Documentation

SAP Documentation

IDES Documentation

Information

Status

1

User Roles

Business

Blueprint

Business

Blueprint

„

The Q&Adb questions and the corresponding process models are used to facilitate and frame the
gathering of company input.

„

The questions concerning the business process are dependent for their content on the respective
business process. The answers can either be freely formulated or are given:

y

Yes, No, Unanswered

y

Answer list

„

The questions concerning the CI template are the same for all business processes and can be
answered freely.

background image

© SAP AG

TSCM52

24-59

SAP AG 2001

Diagram Explorer (Intellicorp)

- read only -

Aris for R/3 (IDS)

ERP Modeler (CASE wise)

Live Model (Intellicorp)

Determine coverage level

high
medium
low

Analyze Business Processes

External Modeling Tools

4

Process Groups

5

Processes

2

Enterprise Areas

3

Scenarios

SAP Reference Structure

1

Business Processes

Conduct Business Process Workshops - Modeling

Business

Blueprint

Business

Blueprint

„

You can use external modeling tools to compare enterprise process areas, scenarios, and processes
with the SAP Reference Structure.

„

In addition to installing the modeling tool you wish to use, you also need to choose the relevant
modeling tool in the field “Business Modeler“ in User Maintenance in the ASAP Administration
Tool.

„

The comparison with the SAP Reference Structure clarifies to what extent your own business
processes can be covered by the R/3 business processes.

„

The business fit can be high, medium, or low. The measures that need to be taken to achieve this
depend on the analysis:

y

High, through Customizing

y

Medium, through enhancement

y

Low, own transactions.

„

If an enhancement is necessary, it can be documented in the structure of the Q&Adb on each level by
adding customer-defined objects.

„

Copying of objects is supported on every level.

background image

© SAP AG

TSCM52

24-60

SAP AG 1999

Code Transaction DOC Scope BaseLine

C1-C4

MK01 Create Vendor Mstr Data

Item name Item count Answered In Scope

Business Process Transactions n N/A n

Business

Business

Process

Process

Transactions

Transactions

Run

Run

R/3

R/3

Transaction

Transaction

User

User

Profile

Profile

R/3 Information

R/3 Information

4

Process Groups

5

Processes

2

Enterprise Areas

3

Scenarios

SAP Reference Structure

1

Business Processes

Conduct Business Process Workshops - BP Ta.

Business

Blueprint

Business

Blueprint

„

The description of the business processes is completed by including the related Business process
transactions in the scope of the implementation project. The number of transactions related to the
business process will be displayed on the business process transaction matrix when you choose
Business process transactions.

„

The business process transaction matrix shows:
Code: Name of the business process transaction
Transaction: Long text of the business process transaction
DOC: Link to R/3 Documentation
SC (Scope): shows that the business process transaction is in scope
BL (Baseline): Indicates the business process transaction within the Baseline scope (the basic scope
of transactions that will be implemented
C1-C4: describe proposed cycles for configuration tests.

„

The business process transaction matrix contains the default values for the business process
suggested by SAP. You should not make changes in the business process transaction matrix, but in
the Business Process Master List, an MS-Excel file that is based on the business process transaction
matrix in the Q&Adb. You should only make changes with the support of consultants.

„

From the matrix, it is possible to call up the corresponding transaction in the R/3 System, providing
that the relevant settings in the Admin tool user profile have been maintained and the R/3 System is
available.

background image

© SAP AG

TSCM52

24-61

SAP AG 2001

User Roles

4

Process Groups

5

Processes

2

Enterprise Areas

3

Scenarios

SAP Reference Structure

1

Business Processes

Business Analysis

Questions

CI template

Transactions

Assigned user roles
User roles by
transaction
Transactions by
user role

Project documentation

SAP documentation

IDES documentation

1

User Roles

Business

Blueprint

Business

Blueprint

„

Once each process team has collected information about the different roles during business process
workshops, the Organizational Change Management (OCM) team is reponsible for bringing together
the various design documents and creating a master set of roles (see: Business Blueprint,
Organizational Change Management Blueprint, Implement Business Optimization Process, Create
Role Report).
The objective of this step is to develop a set of roles small enough to allow flexibility
in organizational design yet large enough to enable some degree of standardization throughout the
company.

„

Once the roles are confirmed, business process teams assign the roles to the transactions (manual and
SAP).

„

The best way to do this is to use the Q&Adb, if one is available and used. Finally a report needs to be
generated listing all business processes, transactions and roles. The report should then be distributed
to all teams for confirmation. Once the report has been confirmed, no changes should be undertaken
without formal change control.

„

The User Roles substructure is made up of user roles that have been defined by SAP. The project
team can use this substructure to determine the user profiles they require for their specific project. It
is possible to define, copy and rename user roles. You can also display the functions assigned by
SAP to user roles for each structure item.

background image

© SAP AG

TSCM52

24-62

SAP AG 2001

Assemble Business Blueprint

Identify Baseline Scope

Verify Business Blueprint Completeness

Tasks

Rep

orts

Rep

orts

Rep

orts

Rep

orts

Complete Business Blueprint

Accelerators:

„

Sample Business Blueprint

„

Sample Business Blueprint Summary Presentation

Business

Blueprint

Business

Blueprint

„

The purpose of this activity is to complete the Business Blueprint, which is the main deliverable of
Phase 2. The Business Blueprint serves as your conceptual master plan, and becomes a detailed
written document. This document shows you the business requirements in detail, and serves as the
basis for organization, configuration and, if necessary, development activities.

background image

© SAP AG

TSCM52

24-63

SAP AG 2001

Reports (Business Process Definition)

Users

Users

Issues

Issues

Status

Status

Master lists

Master lists

BPML

BPML

OSL

OSL

DL

DL

AL

AL

Business Blueprint

Business Blueprint

-

-

-

mySAP

mySAP

.com

.com

-

Edit View Reports

Business Strategy

Business Strategy

Scope document

Scope document

Reports

Reports

-

Scope document
Business strategy

mySAP.com
Business Blueprint

All

KPI
Organizational structure

General settings
Master data
Business processes
Cross-application
components
User roles
Training and
documentation
Development

Master Lists

Organizational Structure
List

Business Process Master
List
Development List
Authorization List
Status Report
Administrative
Issues

-

-

Business

Blueprint

Business

Blueprint

„

Reports allows you to display project documentation in different forms, and creates a report structure
in the Q&Adb.

background image

© SAP AG

TSCM52

24-64

SAP AG 2001

Tasks

Bu

sin

es

s

Bu

sin

es

s

Blu

ep

rin

t

Blu

ep

rin

t

Blueprint Document Review and Signoff

Business

Blueprint

Business

Blueprint

Prepare for Presentation of Blueprint Review

Conduct Review and Sign-Off

Accelerators:

Business Blueprint Quality Checklist
Project Signoff Form
Executive Summary of Business Blueprint

Powerpoint Presentation

„

Prepare for Presentation of Blueprint Review
The purpose of this task is to distribute the Business Blueprint to team members, and to organize the
Business Blueprint review and signoff meeting.

„

Conduct Review and Sign-Off
The purpose of this task is to review and sign off the Business Blueprint. This contains business
processes and scenarios, gaps between business processes and system functions, reports, models,
conversions and interfaces. Furthermore, the baseline scope needs to be reviewed at this time.

„

As a result of the Business Blueprint sign-off, you confirm the following:

• Process design

• Organizational structure

• Baseline scope

• Technical design

• System landscape

„

You have now completed your second project milestone.

background image

© SAP AG

TSCM52

24-65

SAP AG 2001

QM

QM

Phase 2: Business Blueprint - Work Packages (5)

Project Management

Project Management

Organizational Change Management

Organizational Change Management

Training in the Business Blueprint Phase

Training in the Business Blueprint Phase

Business Process Definition

Business Process Definition

Technical Design Planning

Technical Design Planning

Establish Development System Environment

Establish Development System Environment

Organizational

Organizational

Structure Definition

Structure Definition

„

The purpose of this work package is the final verification of all deliverables from this phase. It is
critical that quality checks be performed throughout the phase, as tasks are completed. The Business
Blueprint ensures that everybody has an accurate understanding of the final scope of the project
regarding business processes, organizational structure, and system environment.

„

In addition, this includes project team member training, project standards, and strategies in the
technical area. You must address issues regarding changes in scope, impact on budget, and resource
planning.

background image

© SAP AG

TSCM52

24-66

SAP AG 2001

Quality Check Checklist

Validate project team status

and steering committee
meeting

Verify teambuilding activities
Ensure user roles and

responsibilities

Confirm technical design
Verify development

environment/system
landscape

Sign off Business

Blueprint/Baseline Scope

9

9

9

9

9

Configuration

9

D

o

cu

m

en

tatio

n

Quality Management Business Blueprint Phase

„

The purpose of this activity is to collect all deliverables and to review them for completeness and
accuracy. Although quality checks are performed when specific tasks are completed, it is critical to
review them together because individual results from one task may have an adverse impact in
another area of the project. Upon completion of this quality check, signoff is obtained and the project
proceeds to the next phase.

„

This slide lists only the most important points of the checklists for project management or quality
assurance. You can find the complete checklists for the first and last Work Package of Phase 2:
Business Blueprint in the ASAP Roadmap documentation.

background image

© SAP AG

TSCM52

24-67

SAP AG 1999

Unit

Unit

Unit

Topic

Topic

Topic

Legend:

Legend:

Legend:

Phase 1
Project Preparation

Phase 2

Business Blueprint

Phase 3
Realization

Implementation
Roadmap

Phase 4

Final Preparation

Phase 5
Go Live & Support

Overview Diagram: Implementation Roadmap (3)

background image

© SAP AG

TSCM52

24-68

SAP AG 2001

Upon completion of this topic, you will be able to:

z

Explain the Realization Phase activities of the
ASAP Implementation

z

Explain and demonstrate how the ASAP tools
and accelerators support the Realization Phase
activities

Phase 3: Realization: Objectives

background image

© SAP AG

TSCM52

24-69

SAP AG 1999

The Purpose of Phase 3: Realization

Project

Preparation

Business
Blueprint

Realization

Final

Preparation

Go Live &

Support

ASAP Roadmap

„

The purpose of this phase is to implement business and process requirements based on the Business
Blueprint. The objectives are final implementation in the system, an overall test, and the release of
the system for production (live) operation. The project team needs to get the corresponding training
in these areas.

background image

© SAP AG

TSCM52

24-70

SAP AG 2001

Realization - Roles & Key Focus

Review, Status/

Cutover & Prod.

Support Plan

Steering

Meetings

Team Bldg

Activities

Analyse Org

Implement.

Risks

Refine Training

Sched/ Review

Proj Team Risk

Assmt

Attend PTT

Attend PTT

E.U. Training:

content & prep

Approve Config

Plans/Validate

Completion

Org Structure

System Test

Plans/QA &

Prod Enviro/

Prep for ABAP

Define

A-R-I-C-E

Create &

Register Dev

Create,Test,

Migrate

Programs &

Procedures

Test, Review, &

Approve

Review Strategy

Create Models

Authorize Design/

Job Functions

Define Scope &

Test Cases/

Approve

Signoff

Quality Check

Signoff

Signoff

Check for

Approvals

Review / FU on

Recommends

Attend PTT

Org Impact/

Risk / Sponsor

Steering

Steering

Sponsors

Sponsors

Project

Project

Mgt

Mgt

Consultant

Consultant

Customer

Customer

Technical

Technical

Training

Training

Change

Change

Security

Security

Proj Mgt

Proj Mgt

Org Chng

Org Chng

Mgt

Mgt

Proj

Proj

Team

Team

Training

Training

Config

Config

Sys Admn

Sys Admn

ARICE

ARICE

Arch

Arch

/Form

/Form

Integration

Integration

QC

QC

***************

Conduct

Test Cases

**************

***************

Check for

Approvals

**************

***************
Analyze Org

Implement.

Risks

**************

***************

Realization

Phase

Review

**************

***************

Refine Scope

Config/Define

Test Cases

**************

Role
Groupings

Phase

Content

„

These are the primary roles in an SAP implementation (all the roles are defined in the
Implementation Assistant).
Steering Committee - members include Project Sponsors, the SAP Consulting Manager (and/or the
TeamSAP Coach), and project managers. The committee is also the primary source for the
company’s long-term goals and vision, sets priorities, approves scope, and resolves company-wide
issues.
Project Sponsors - directly communicates the company’s long-term goals and visions and are
members of the steering committee.
Proj Mgt - TeamSAP Project Manager and Customer Project Manager
Consultant - TeamSAP Members, application, cross application, business process
Customer - Project Team Members (business process, power users)
Technical - Customer or consultants for System Administration and Technical, help desk provider
Training - Training & Documentation - project mgr/lead/ developer, Training Development
Instructor, Training Co-ordinator, Training Technology Administrator
Change -These are dedicated individuals assigned to manage the organizational change management
processes: Risk Assessment, Communications, Sponsorship, Skills Development, Knowledge
Transfer or Organizational Optimization.
Security - Authorisation, Administration or Internal Auditor responsible for managing the system
security and authorization environment and may be combined with other (technical) administrative
roles.

„

Shared items are marked by the ************ brackets.

background image

© SAP AG

TSCM52

24-71

SAP AG 2001

Master Lists

Microsoft Excel
Spreadsheets for
Development, Organization,
Business Processes and
Authorizations

Project

Charter

BPP

Documents of an ASAP Project

Q&Adb

Substructures:

Business Strategy
Organization
General Settings
Master Data
Business Process
Cross Application
Development

Business

Blueprint

Project

Plan

Scope

Config.

Plan

Testing

Plan

Unit testing
Test scenario
Integration

4

3

2

1

5

Cutover

Plan

Volume

Test

Stress

Test

Conduct

End User

Training

System

Performance

Review

Project

Team

Org.

Stand. &

Proced.

Technical

Operations

Manual

Progr.

Develp.

EU

Training

Material

Microsoft Word

Documents

Phase 1 - Project Preparation

„

Change Charter - Goals and objectives of Organizational Change Management

„

Project Plan - This is a first cut focusing on milestones and Work Packages; details to come.

„

Scope - Sets the initial definition of the project; input from sales cycle.

„

Project Team Organization - Sets the who of the project: Standards & Procedures - Sets the why and
how of the project.

Phase 2 - Business Blueprint - Requirements reviewed for each SAP Reference Structure item and

defined using CI Templates (in the Q&Adb). Business Blueprint - This is the output of the Q&Adb
and is the key document for Phase 3.

Phase 3 - Realization - Master Lists - Define business scenarios and R/3 transactions to be realized in

the system. BPP - Business Process Procedures representing R/3 transactions; used for unit testing &
documentation. Planning - Defines how the configuration will be done and how it will be tested.
Development Programs - Provides details of the external programming requirements. EU Training
Material - End User training material and process documentation.

Phase 4 - Final Preparation Stress & Volume Tests - Plans for confirming the production hardware’s

capabilities
Cutover Plan - The details of how to move to the production environment and go live
Conduct End User Training - Delivery of the necessary levels of R/3 End User training prior to going
live

Phase 5 - Go Live & Support: Ensuring system performance through SAP monitoring and feedback.

background image

© SAP AG

TSCM52

24-72

SAP AG 2001

Project Management

Project Management

QC

QC

Develop System Test Plans /

Develop System Test Plans /

Establish QA Environment

Establish QA Environment

Organizational Change Management

Organizational Change Management

Training in the Realization Phase

Training in the Realization Phase

Phase 3: Realization - Work Packages (1)

Baseline

Baseline

Configuration

Configuration

Final Configuration

Final Configuration

Integration

Integration

Workflow, ABAP,

Workflow, ABAP,

Conversions and Interface

Conversions and Interface

Prog

Prog

.

.

Enhancements, Reports, Forms,

Enhancements, Reports, Forms,

User Roles, Archiving

User Roles, Archiving

Establish Production

Establish Production

Environment

Environment

background image

© SAP AG

TSCM52

24-73

SAP AG 1999

Configuration

D

o

cu

men

tat

io

n

Project Management

Project Management

Checklist

Checklist

Prepare and attend

status meeting

Prepare and attend

steering committee
meeting

Determine project

variances

Refine project plan
Determine production

support plan

Determine cutover

plan

9

9

9

9

9

9

Project Management

„

Only the most important points of the checklists for project management and the quality check are
listed on this slide. The complete checklists can be found in the ASAP Roadmap documentation.

„

Note the Project Review Program which is provided as an SAP service. Reviews can be scheduled
throughout the duration of the project. A review provides an independent and objective management
review of the customer implementation project, identifies any risks to the project goals and
recommends appropriate corrective actions.

background image

© SAP AG

TSCM52

24-74

SAP AG 2001

Monitor / Update OCM Plan and Activities

Continue Business Optimization Process

Accelerators:

„

OCM Implementation White Paper

„

OCM Risks and Activities Guide

Activities

Organizational Change Management

Realization

Realization

„

The purpose of first of these work packages is to ensure that the Organizational Change
Managemente (OCM) activities take place as planned and are successful in mitigating OCM risks.

„

The second work package should ensure that there is an infrastructure, which supports the transition
to the new organizational business solution.

background image

© SAP AG

TSCM52

24-75

SAP AG 2001

Conduct Project Team Training

Define End User Training and Documentation Content

Develop End User Training and Documentation
Content

Prepare for End User Training and Documentation
Delivery

Activities

Accelerators:

n

Project Team Training Template

n

Training Services and Products

n

Sample Documentation Standards

Create Training Materials

Realization

Realization

„

The purpose of this work package is to finalize and conduct level three of the project team training.
Also during the realization phase, end user training and documentation is defined, developed, and
finalized.

„

The purpose of the Conduct Project Team Training activity is to conduct Level 3 project team
training so that team members can get insight of the business processes or technical features in their
area. This training shows the many business and technical options available to your company and
how to configure the system to meet your company needs.

„

The purpose of the Define End User Training and Documentation Content activity is to set the
standards and review process for training content and documentation development for the End User.
To define an evaluation and improvement process, communicate this information to the course
developers, and develop the course outlines are further tasks involved in this activity.

„

The purpose of the Develop End User Training and Documentation Content activity is to develop all
training content and documentation as defined in the end user training and documentation plan and
designed in the prototype.

„

The purpose of the Prepare for End User Training and Documentation Delivery activity is to prepare
for end user training delivery and distribution of documentation. In this activity, you will finalize the
training curriculum and job roles, develop a training logistics plan, test the training system, conduct a
train-the-trainer, and finalize end user training content and documentation materials.

background image

© SAP AG

TSCM52

24-76

SAP AG 2001

Team Training

Schedule

Team Training

Schedule

Refine Training Schedule

Baseline

Baseline

Configuration

Configuration

Final Configuration

Final Configuration

Project Team Training

Project Team Training

Level 2

Level 2

Phase

1

Phase

1

Phase

3

Phase

3

Complete training

Project Team Training

Level 3

Level 3

Level 2

Level 2

Level 3

Level 3

Realization

Realization

„

To prevent a delay in Realization and to have better control, re-evaluate the training schedule:

y

Are your employees receiving the right training?

y

Have there been new people added to the project that need to be added to the training schedule?

y

Have people been reassigned to a different area requiring the schedule to be adjusted?

y

Have all decisions been made on where training will take place and whether or not logistics will

need to be resolved?

„

Levels of courses in the SAP curriculum: Level 1, awareness - introductory to provide overview of
SAP product features & functions, SAP services & support, implementation framework (ASAP), and
SAP specific terminology; Level 2, readiness - core business process courses to enable individuals to
apply SAP to a company’s processes; & Level 3, proficiency - advanced courses for individuals to
acquire customizing & other detailed functional and technical SAP related expertise.

„

The project members must take all relevant level 2 and level 3 training by the end of the Baseline
Configuration. NOTE - ideally, Level 2 training is taken by the end of the Project Preparation Phase,
as part of the preparation for Business Blueprint Phase. The Level 2 preparation is also crucial to
obtaining the special configuration knowledge for the applications in the Level 3 training. Ideally,
the Level3 training should be completed prior to, or early in, the Baseline Configuration. In this way,
the project members should be able to go over the training again, and then be able to apply quickly
their newly gained knowledge in Final Configuration.

background image

© SAP AG

TSCM52

24-77

SAP AG 2001

Phase 3: Realization - Work Packages (2)

Project Management

Project Management

Organizational Change Management

Organizational Change Management

Training in the Realization Phase

Training in the Realization Phase

QC

QC

Develop System Test Plans /

Develop System Test Plans /

Establish QA Environment

Establish QA Environment

Baseline

Baseline

Configuration

Configuration

Final Configuration

Final Configuration

Integration

Integration

Workflow, ABAP,

Workflow, ABAP,

Conversions and Interface

Conversions and Interface

Prog

Prog

.

.

Enhancements, Reports, Forms,

Enhancements, Reports, Forms,

User Roles, Archiving

User Roles, Archiving

Establish Production

Establish Production

Environment

Environment

„

The purpose of the Develop System Test Plans work package is to define technical and performance
plans.

„

The system test plans defined here will be conducted during phase four on the actual production
system hardware, devices, and network. However, initial testing and verification of the test plans
should begin earlier in the development or quality assurance systems during phase three.

„

The purpose of the Establish Quality Assurance Environment work package is to install and set up
the quality assurance system for integration testing.

„

The purpose of the Establish Production Environment work package is to install and set up the
production system for productive operation.

„

For local rollout projects, as part of a global implementation project, the Global Solution Package
will be used to set up this environment. Please refer to the task Getting Familiar with Global
Solution Package
in phase one of the Rollout Roadmap.

background image

© SAP AG

TSCM52

24-78

SAP AG 2001

Define Production

System Design

Define Productive

System Management

Set Up Production

Environment

Develop System

Test Plans

Establish System

Administration

Functions

Set Up Production Environment

Establish Service Level Commitment

System QA and Production Work Packages

Verify data used in
the initial hardware
disk-sizing estimates
for the production
system

Phase 2

Business Blueprint

Realization

Realization

Set Up Quality Assurance Environment

„

The preparation from the Business Blueprint phase for developing the system environment can now
be put into practice.

„

System administration functions are, for example: client copy function, transport system, and
functions for backup and recovery.

„

Important tests are for example: failure tests, stress tests, and testing of fax and printing devices.

„

Useful accelerators for this topic can be found in the ASAP Roadmap documentation. Examples:

y

Volume Test Plan / Stress Test Plan

y

Ready-to-Run R/3 in SAPNet

y

SAP System Administration Made Easy Guidebook

background image

© SAP AG

TSCM52

24-79

SAP AG 2001

Phase 3: Realization - Work Packages (3)

Project Management

Project Management

Organizational Change Management

Organizational Change Management

Training in the Realization Phase

Training in the Realization Phase

QC

QC

Develop System Test Plans /

Develop System Test Plans /

Establish QA Environment

Establish QA Environment

Baseline

Baseline

Configuration

Configuration

Final Configuration

Final Configuration

Integration

Integration

Workflow, ABAP,

Workflow, ABAP,

Conversions and Interface

Conversions and Interface

Prog

Prog

.

.

Enhancements, Reports, Forms,

Enhancements, Reports, Forms,

User Roles, Archiving

User Roles, Archiving

Establish Production

Establish Production

Environment

Environment

„

The purpose of the Baseline Configuration work package is to configure and confirm settings from
the Baseline Scope for scenarios, processes, and functions.

„

During the Business Blueprint phase, the Identify Baseline Scope task divides relevant business and
process requirements into two main blocks. The Baseline block comprises the priority requirements
of the company, ensuring that they can be implemented quickly.

„

During baseline configuration, work on processes can be configured without programming or
enhancements. Requirements that need programming or enhancements to the SAP system are
addressed in separate work packages in the Realization Phase.

„

The Final configuration is an iterative process in which you set up your business requirements. You
confirm that all your business requirements are met in the R/3 System. To make configuration easier,
create two or more cycles. Each cycle, based on the value chains in the enterprise, includes the
functions and processes you need. Depending on the scope of implementation, create an appropriate
number of cycles (cycle 1, cycle 2 through to cycle n). Configure these cycles sequentially.

„

The Final configuration is a transformation process that expands the Baseline solution, defined
during the Business Blueprint and Baseline configuration, through cycles (1 to n) resulting in a
solution that satisfies all stated business requirements.

background image

© SAP AG

TSCM52

24-80

SAP AG 2001

Activities

Develop Plans for Baseline Configuration

Configure Initial Settings and Organizational Structure

Configure and Validate Baseline

Prepare Baseline Confirmation

Perform Baseline Confirmation

n

Directory Structure and Naming Conventions

n

Sample Configuration Plan for Baseline

n

Computer Aided Test Tool (CATT)

n

Testing Strategy White Paper

Baseline Configuration and Confirmation

Accelerators:

Realization

Realization

„

The purpose of the Baseline Configuration and Confirmation work package is to refine the
Baseline Scope from phase 2, to determine the baseline test cases, and create the Project IMG in the
R/3 System.

„

In baseline configuration one first needs to change general settings and organizational structures in
the System. Only once this is completed can you then configure the business processes in the
Baseline configuration and the Final configuration.

background image

© SAP AG

TSCM52

24-81

SAP AG 2001

Goal, Content, and Tools of Configuration

A fully configured, tested and signed off system

Tools/Accel-
erators

Content

Goal

Baseline

Baseline

Config

Config

.

.

and Confirmation

and Confirmation

Final Configuration

Final Configuration

and Confirmation

and Confirmation

ABAP, A-R-I-C-E, Forms and Archiving

ABAP, A-R-I-C-E, Forms and Archiving

Final

Final

Integration Test

Integration Test

Implementation Assistant

Implementation Assistant

Business Blueprint
Master Lists and associated Worksheets
Templates

Test Scenarios
BPPs - Unit Test

R/3

R/3

IMG
Documentation
Transportation

Optional: Case Procedures

Final Integration Test Procedures

Realization

Realization

„

The objective of Realization Phase is the implementation of the system as specified by the Business
Blueprint, its overall test, release and documentation.

„

The configuration is realized in two Work Packages:

y

Baseline Configuration and Confirmation (planning, implementation, test, and release)

y

Final Configuration and Confirmation (planning, implementation, test, and release).

„

In order to do the Final Integration Test, you must also plan, realize, and test all relevant interfaces,
system enhancements, and so on. The Business Process Master List (BPML) is the central tool to
properly plan and document Realization. Supporting documents, which provide the additional detail
to actually carry out configuration and testing, are produced using templates (accelerators) designed
for this purpose. The BPML is generated from the Q&Adb.

background image

© SAP AG

TSCM52

24-82

SAP AG 2001

Tasks

SAP

Reference

IMG

Generate Project IMG

Accelerators:

Sample Scope Document

Working with Project IMGs

ASAP IMG-Link

Data

Scope

Views

Member

Status

Country

Define Project

Name

Cross-Reference

Doc. type

Transportation

Keywords

Don't Generate Project IMG

IMG Link

Manually

IMG Link

Develop Plans for Baseline Configuration

Business

Blueprint

Business

Blueprint

„

The purpose of this task is to generate the Project Implementation Guide (IMG). You should use the
Project Implementation Guides to plan and organize the necessary Customizing activities for your
project. When you set up your Project IMGs or Release projects, keep to the standards for using
status indicators, for scheduling, and for documentation, which you defined in the task Define
Project Documentation
under the work package Project Procedures (project Preparation phase).

„

There are two methods of generating the Project IMG:

y

The Project IMG is created manually. This is the more common method, whereby consultants

manually identify the components of the IMG that must be configured according to the project
scope.

y

The Project IMG is automatically generated from the ASAP Question & Answer database

(Q&Adb). This is a new function that uses the scope settings within the ASAP Q&Adb and
transfers them automatically into the R/3 Project IMG. Refer to the accelerator ASAP IMG-Link
for more information.

background image

© SAP AG

TSCM52

24-83

SAP AG 2001

ASAP - IMG Link

SAP Reference Structure

1

Structure Item

A

2

Structure Item

C

3

Structure Item

E

Adminstration

Transfer Scope to R/3 System
...

User

User

Maint

Maint

.

.

R3 Info

R/3

R/3

Project

IMG

Project

Documentation

Project

Management

Transfer

Scope

„

In order to create a direct link from the BPML to the R/3 IMG, proceed as follows:

1. Set the scope in the Q&Adb

During the Business Blueprint phase of the project, the project team undertakes a number of General
Requirements and Business process workshops to define both the high-level scope and detailed
scope. This scope is entered into the Q&Adb.

2. Create Project IMG header in R/3

In order to transfer the Q&Adb scope to the R/3 System, it is first necessary to create a Project IMG
through Project Administration in R/3. Specify a project name and description, select the countries
and save the Project IMG.

3. Verify R/3 Login information in the Q&Adb

Before initiating the transfer to R/3, make sure that the user parameters are set correctly to log on to
the corresponding R/3 System. If you maintained this information in the Admin Tool, you only need
to confirm it here.

4. Generate Project IMG based on the scope set in the Q&Adb

The generation of the Project IMG will be derived from ASAP, based on the agreed scope.
In order to transfer the Q&Adb scope to the R/3 System, select the menu item Administration ->
Transfer Scope to R/3 System.
Only the project manager is authorized to transfer the Q&Adb scope
to R/3.

5. You can now branch directly to the IMG Customizing activities from the Business Process Master

List, for a specific transaction scoped in the Q&Adb.

background image

© SAP AG

TSCM52

24-84

SAP AG 2001

Baseline Scope

Level 1

Level 2

Level 3

Linking the Blueprint to the Realization Phase

Business

Blueprint

Cycle Scope

Level 1

Level 2

Level 3

The Business Blueprint is Always the Source Document

Re

fere

nc

e

Reference

Development Master List

Level 1

Level 2

Level 3

Authorization Master List

Level 1

Level 2

Level 3

Organization Master List

Level 1

Level 2

Level 3

Business Process Master List

Level 1

Level 2

Level 3

Integration Test

Level 1

Level 2

Level 3

Generate
Worksheets

„

In Phase 2, the business requirements were defined in the Q&Adb along with the project scope. The
Master Lists reflect the definitions defined in the Business Blueprint document. The various
worksheets used to control and drive the configuration and confirmation process are derived from
those Master Lists.

„

In all cases where there is disagreement about business process definition, the resolution is found in
the Business Blueprint Document. The Blueprint is the reference source for answering all questions
about requirements definition in Phase 3, Realization. As such, if there are changes, the Blueprint
Document must be updated.

background image

© SAP AG

TSCM52

24-85

SAP AG 1999

Business Process Master List

Integration

Cycles

Baseline

Business Process Master List

Check columns







Ba

se

lin

e

Cy

cl

es

In

te

g

ra

ti

o

n





Level 2 - Enterprise Process Area A

Level 3 - Scenario Process AA

Level 4 - Process Group AA00

Level 5 - Business Process AA10

Level 6 - BPP AA11

Level 5 - Business Process BB10

Level 1 - Business Process

  

… to create
associated
worksheet

… to create
associated
worksheet

Select
process,
...

Select
process,
...

„

The BPML, which is generated in the Q&Adb, is the central data repository. It contains all R/3
business processes and transactions that represent the scope of the project. The project scope was
determined in the Business Blueprint Phase. The BPML is also generated then, prior to the
commencement of the Realization Phase.

„

As the central data repository, the BPML is used to feed required business process information to the
working documents (worksheets) used to specify, manage, monitor and control the work packages
of:

y

Baseline Configuration and Confirmation

y

Final Configuration and Confirmation (cycles)

y

Final Integration Testing

„

During project scope definition in the Business Blueprint Phase, adjustments (Process variants) to
R/3 business processes may have been made to meet customer needs e.g. a distinction between a
goods receipt with and without bar code recognition might be required, in which case a process
variant would have been created. In addition, business process owners will probably have been
identified. Applications consulting will also have defined, with the customer, the order of realization.
All these events of the Business Blueprint Phase will have been reflected in the Master List
illustrated in this slide. They will now be reflected in subsequent BPML worksheets derived from
this Master List in the Realization Phase.

background image

© SAP AG

TSCM52

24-86

SAP AG 1999

Worksheets within the BPML

Cycles

Baseline

Integration

Baseline Scope

Cycle 1 Scope
Cycle 2 Scope
Cycle 3 Scope
Cycle 4 Scope

Integration Test 1
Integration Test 2

Worksheets specify, sequence,
schedule and assign responsibility
for the work

„

The relevant worksheet is generated from the BPML:

y

Baseline - Baseline Scope Document or BSD

y

Cycles (Final Configuration and Confirmation) - a Configuration Plan Worksheet for each of the

cycles (1 - n)

y

Integration - an Integration Test Plan Worksheet for each cycle (1 & 2).

„

Worksheets are used to specify, sequence, schedule and assign responsibility for the work involved.

background image

© SAP AG

TSCM52

24-87

SAP AG 2001

Baseline & Cycle Worksheets

Cycles

Baseline

Baseline/Cycle Scope

Documentation Links

R/3 Links

Responsibilities

Configuration Dates

Testing Dates

Level 1, Level 2, Level 3, Level 4, Level 5, Level 6

CI, BPP, Case Proced, Test Scenario, Related Files

Transaction Code, IMG

Config, Writer, Tester

Plan, Actual

Plan, Actual

Status

Doc’d, Config’d, Tested, Retest, Approved, Hold

„

Baseline / Cycle Scope
Level 1 - Structure item from Q&Adb
Level 2 - Corresponds to Enterprise area level for business process
Level 3 - Corresponds to Scenario level for business process
Level 4 - Corresponds to Process Group level for business process
Level 5 - Corresponds to Business Process level for business process
Level 6 - Corresponds to Business Process Procedure level for business process

„

Status - The current status of the particular level in the scope

„

Responsibilities
Config - Person responsible for configuring the system
Writer - Person responsible for writing the documentation
Tester - Person responsible for testing

„

Configuration Dates
Plan - Planned completion dates for the configuration of the defined level
Actual - Actual completion dates of the configuration

„

Testing Dates
Plan - Planned completion date for testing the defined level
Actual - Actual completion date of the testing

„

The BPML worksheet also includes a Comments column for notes and additional information
documentation

background image

© SAP AG

TSCM52

24-88

SAP AG 1999

The ASAP Processes in the Work Packages

Conduct

Scenarios

Prepare

Scenarios

Refine

Configure

Test

Create

Test Plan

Create

Config.

Plan

Define

Test Cases

For Baseline / Final Configuration & Confirmation

„

This process for configuration and confirmation is used in both of the Work Packages of Baseline
Configuration & Confirmation and Final Configuration & Confirmation.

„

While the process defines the flow of work through the Work Packages, the Implementation
Assistant defines all the tasks necessary to complete the configuration and confirmation work.

background image

© SAP AG

TSCM52

24-89

SAP AG 2001

Activities

Develop Plans for Final Scope Configuration

Conduct Configuration Workshops (Cycle 1-n)

Configure and Validate Final Scope (Cycle 1-n)

Prepare Final Confirmation

Perform Final Confirmation

n

Cycle Concept and Group Definition

n

Test Scenario

n

Test Scenario Instructions

n

List of Predefined Test Scenarios

Final Configuration and Confirmation

R/3 System

IMG for R/3 Customizing

Keywords

Note Types

General

Memo

Employee

Status

Activity

Project Name

Organizational
Structure List

IMG

- Activity

Documentation

Status Information

Accelerators

Realization

Realization

Business
Process
Master List

„

The cycles in the Final configuration represent an iterative process that coordinates the configuration
with your business processes and business requirements. This is normally carried out at the same
time as the development activities.

„

The application consultants assume the initial responsibility. As the end user retention increases
during the knowledge transfer, this responsibility is gradually passed over to members of the project
team.

„

The result of the Final configuration using cycles is a completely configured system that is based on
the business requirements, the trained project team, the planned user procedures, the documented
issues, and the system prepared for the integration test.

background image

© SAP AG

TSCM52

24-90

SAP AG 2001

Testing in the Realization Phase

Final Configuration

Baseline Configuration

Integration Test

IT 1

IT2

Development of Conversions, Interfaces, Forms, etc.

Scenario Test - Test Scenario Template

Development Unit Test - Functional Specification Test

Unit Test - BPP with Test Conditions

Integrated

Test Scenario

IT Scenario

with Develp

Realization Phase

START

END

C1

C2

C3

C4

„

Note: the number of cycles for Final Configuration (4) and Integration Test (2) is a recommendation
only.

„

Unit Testing - This is the lowest level of testing where the program or transaction is tested and
evaluated for errors. Unit testing is normally the first test that is completed during the configuration
effort, and is focused towards the program’s inner functions, rather than towards the integration.
Testing focus: Master data & Business processes.

„

Scenario Testing - During the configuration there is a need to test chains of transactions that flow
together and which reflect important business processes and scenarios. Testing focus: Multiple
transactions within one enterprise area; Workflow and Business processes which cross enterprise
areas. During subsequent integration testing these small scenarios can be used to build larger end-to-
end scenarios.

„

Integration Testing - Final integration testing is accomplished through the execution of predefined
business flows, or scenarios, that emulate how the system will run your business. These business
flows, using migrated data from the pre-existing systems, will be performed in a multifaceted
computing environment comprised of R/3, third-party software, system interfaces and various
hardware and software components. It is this environment that builds the necessary level of
confidence that the solution is complete and will perform in your business. Final integration tests
need to be an evolutionary process that is driven from your previous testing efforts. The test cases
and scenarios that were used for Baseline and Final Configuration need to be reviewed and enhanced
for the integration testing.


Wyszukiwarka

Podobne podstrony:

więcej podobnych podstron