project implementation of sap

7/26/2019 Project Implementation of Sap

1/92

E-MSGMSTER EN SOFTWARE DE GESTIN DE EMPRESASAP R/3

2003-2004Certificacin MM (7137)Xavier Rovira-Juan Carlos SarrasiTSCM 52-2 parte (24-1)


2/92


3/92

SAP AG TSCM52 24-1

SAP AG 2002

Appendix


4/92

SAP AG TSCM52 24-2

SAP AG 2001

Implementation Roadmap

Phase 1 - Project Preparation

Phase 2 - Business Blueprint

Phase 3 - Realization

Phase 4 - Final Preparation

Phase 5 - Go Live & Support

Content:


5/92

SAP AG TSCM52 24-3

SAP AG 2001

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

Outline the purpose and content of the work

packages in each phase of the ASAP Roadmap

Identify the main roles and responsibilities of

each phase of the ASAP Roadmap

Explain and demonstrate the major tools &

accelerators supporting each phase of the

ASAP Roadmap

Implementation Roadmap: Unit Objectives


6/92

SAP AG TSCM52 24-4

SAP AG 1999

UnitUnitUnit

TopicTopicTopic

Legend:Legend:Legend:

Phase 1Project Preparation

Phase 2

Business Blueprint

Phase 3

Realization

ImplementationRoadmap

Phase 4

Final Preparation

Phase 5

Go Live & Support

Overview Diagram: Implementation Roadmap (1)


7/92

SAP AG TSCM52 24-5

SAP AG 2001

Phase 1: Project Preparation: Objectives

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

Explain the activities and tasks that are

important in the Project Preparation phase of

your implementation project

Highlight the tasks essential from the project

team perspective

Identify the importance of the Sample Scope

Document for Phase 2: Business Blueprint


8/92

SAP AG TSCM52 24-6

SAP AG 2001

The Purpose of Phase 1: Project Preparation

ASAP Roadmap

ProjectPreparation

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:

Defining your project goals and objectives

Clarifying the scope of your implementation

Defining your implementation strategy

Defining the overall project schedule and implementation sequence

Establishing the project organization and committees

Assigning resources.

By addressing these issues early in your implementation, you help ensure that the project proceeds

efficiently, and that you have established a solid foundation for a successful SAP implementation.


9/92

SAP AG TSCM52 24-7

SAP AG 2001

Project Preparation - Roles & Key Focus

Sign-Off

Quality Check/

Sign-Off

Sign-Off

QCQCTech.Tech.ReqReq..

PlanningPlanningProjectProject

KickoffKickoffTrainingTraining

PlansPlansProjectProject

ProceduresProceduresInitialInitialProjProj

PlanningPlanning

SteeringSteering

SponsorsSponsors

ProjProj. Mgmt.. Mgmt.

ConsultantConsultant

CustomerCustomer

TechnicalTechnical

TrainingTraining

ChangeChange

SecuritySecurity

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

companys 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 ProviderTraining - 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.


10/92

SAP AG TSCM52 24-8

SAP AG 2001

Master ListsMicrosoft Excel

Spreadsheets for

Development, Organization,

Business Processes and

Authorizations

ProjectCharter

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 scenarioIntegration

4321 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


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 hardwares

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.


11/92

SAP AG TSCM52 24-9

SAP AG 2001

ProjectProject

ProceduresProcedures

QCQC

TechnicalTechnicalReqReq..PlanningPlanning

Initial ProjectInitial ProjectPlanningPlanning Project KickoffProject Kickoff

CreateCreateTraining PlansTraining 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.


12/92

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.


13/92

SAP AG TSCM52 24-11

SAP AG 2001

Review and Confirm Implementation Plan

Check Strategy for Corporate Rollout

Tasks

SAPProject

InputsImplementation

proposals

Project charter

Data gathered from the

sales cycle

Global Implementation

Strategy

OutputSAP Implementation

Strategy

Review and Refine Implementation Strategy

Accelerators:

Verify the use of Preconfigured Systems (PCS) as ImplementationAccelerator

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.


14/92

SAP AG TSCM52 24-12

SAP AG 2001


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

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.


15/92

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.


16/92

SAP AG TSCM52 24-14

SAP AG 2001

ProjectProjectProceduresProcedures

QCQC

Initial ProjectInitial Project

PlanningPlanningProject KickoffProject Kickoff




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:

Avoid redundant and unnecessary work

Maintain consistency

Facilitate communication


17/92

SAP AG TSCM52 24-15

SAP AG 2001

Avoid redundancy and unnecessary work

Maintain consistency

Facilitate communication

Facilitate knowledge transfer to the customer

Ensure the entire team understands what is requiredof them

Tasks build upon one another through the phases

Define Project Documentation

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


18/92

SAP AG TSCM52 24-16

SAP AG 2001

Define Strategy for Using SAP Services

Post

Go Live

Post

Go LiveImplementationImplementationSales

GoLive Check EarlyWatch

5

Solution Review

SAP Review Program

1 2 3 4

ASAP Roadmap Quality Checks

Project

Preparation Business

BlueprintRealization

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.


19/92

SAP AG TSCM52 24-17

SAP AG 2001

Define System Configuration Standards

Define Testing Strategies

Define Post-Implementation Serviceand Support Strategy

Define System Authorization Standardsfor Project Team

Define Change Request Management

Define System Enhancement and

Modification Approval ProcessDefine 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


20/92

SAP AG TSCM52 24-18

SAP AG 2001

QualityAssurance

SystemProduction System

Development/Customizing System

Quality Assurance System

Production System

DEV

QAS

PRD

CopyTransport

ation

DEV

SAPClient

000QAS PRD

Development System

Project

Preparation

Project

Preparation

Data conversions

Three database infrastructure with

Development, Quality Assurance

and Production Systems

Complete testing of development

and upgrades possible

Suitable development environment

Define System Landscape Strategy

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

It affords you unlimited testing of your development.

You can implement system upgrades without disturbing your live system.

With a separate quality assurance system, you can integrate developments and run consistencychecks 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:

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

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

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

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


21/92

SAP AG TSCM52 24-19

SAP AG 2001

ProjectProject


QCQC





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.


22/92

SAP AG TSCM52 24-20

SAP AG 2001

ASAP Roadmap

Project

PreparationBusiness

Blueprint

Realization

Final


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 & 2before 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 forthe 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

SAPs 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:

Background of each team member

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

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.


23/92

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.


24/92

SAP AG TSCM52 24-22

SAP AG 2001

ProjectProject


QCQC





The objective of this work package is to identify the technical requirements needed to implement the

SAP technical environment, clarify the customers 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.


25/92

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.


26/92

SAP AG TSCM52 24-24

SAP AG 2001

ProjectProject


QCQC

Initial ProjectInitial ProjectPlanningPlanning

Project KickoffProject Kickoff




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.


27/92

SAP AG TSCM52 24-25

SAP AG 2001

Motivate the individuals involved andbring 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.


28/92

SAP AG TSCM52 24-26

SAP AG 2001

ProjectProject


QCQC





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.


29/92

SAP AG TSCM52 24-27

SAP AG 1999

QCPerform 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 customers 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.


30/92

SAP AG TSCM52 24-28

SAP AG 1999

UnitUnitUnit

TopicTopicTopic

Legend:Legend:Legend:

Phase 1Project Preparation

Phase 2

Business Blueprint

Phase 3

Realization

ImplementationRoadmap

Phase 4

Final Preparation

Phase 5

Go Live & Support

Overview Diagram: Implementation Roadmap (2)


31/92

SAP AG TSCM52 24-29

SAP AG 2001

Phase 2: Business Blueprint: Objectives

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

Explain the activities and tasks that are

important in the Business Blueprint Phase

of the SAP implementation project

Explain the importance of the Question and

Answer Database (Q&Adb)


32/92

SAP AG TSCM52 24-30

SAP AG 2001

The Purpose of Phase 2: Business Blueprint

Project

Preparation

BusinessBlueprint

Realization

Final


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:

Refine the original project goals and objectives

Define the Baseline scope

Refine the overall project schedule and implementation sequence


33/92

SAP AG TSCM52 24-31

SAP AG 2001

Business Blueprint - Roles & Key Focus

ProjectProject

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.ChgChg..

Mgmt.Mgmt.Project TeamProject Team

TrainingTrainingConfigConfig

SysSysAdmnAdmnOrg.Org.

StructureStructureBusinessBusiness

ProcProc..DefDef..QCQC

Training

Effectiveness

EUT & Doc.

strategy/delvy.

Attend PTT

Attend PTT

Approve Tech

Design

Org Structure

Guidelines/

Workshops

Org. Structure

Guidelines/

Workshops

DetermineEnhancements

Assemble Bus

Blueprint

Org

Optimization

Analysis

Attend PTT Sign-Off

Set up Proper

Authoriz.

Org. Impact/

Risk / Sponsor

SteeringSteering

SponsorsSponsors

ProjProj. Mgmt.. Mgmt.

ConsultantConsultant

CustomerCustomer

TechnicalTechnical

TrainingTraining

ChangeChange

SecuritySecurity

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

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

companys long-term goals and vision, sets priorities, approves scope, and resolves company-wide

issues.

Project Sponsor - Directly communicates the companys 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.


34/92

SAP AG TSCM52 24-32

SAP AG 2001

Master ListsMicrosoft Excel

Spreadsheets for

Development, Organization,

Business Processes and

Authorizations

ProjectCharter

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 scenarioIntegration

4321 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


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 hardwares

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.


35/92

SAP AG TSCM52 24-33

SAP AG 2001

QMQM

Phase 2: Business Blueprint - Work Packages (1)

OrganizationalOrganizationalStructure DefinitionStructure Definition

Business ProcessBusiness ProcessDefinitionDefinition

Project ManagementProject Management

Technical Design PlanningTechnical Design Planning

Organizational Change ManagementOrganizational Change Management

Design Training PlansDesign Training Plans

Establish Development System EnvironmentEstablish Development System Environment


36/92

SAP AG TSCM52 24-34

SAP AG 2001

Project ManagementProject Management ChecklistChecklist

Prepare and attendstatus meetings

Prepare and attendsteering committeemeeting

Correct projectvariances

Refine project plan

Change Management

Team-buildingactivities

ConfigurationDocumentation

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 companys SAP product implementation project, identifies any risks to the project goals and

recommends appropriate corrective actions.


37/92

SAP AG TSCM52 24-35

SAP AG 2001

Accelerators:

Activities

Organizational Change Management

Business

BlueprintBusiness

Blueprint

nOCM Implementation White Paper

nCommunications White Paper

nOrganizational 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 companys 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.


38/92

SAP AG TSCM52 24-36

SAP AG 2001

Conduct Project Team Training

Analyze End User Training andDocumentation 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

BlueprintBusiness

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 theBusiness Blueprintphase.

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 inAnalyze End User Training and Documentation Strategy.


39/92

SAP AG TSCM52 24-37

SAP AG 2001




Training in the Business Blueprint PhaseTraining in the Business Blueprint Phase




QMQM


The purpose of the Technical Design Planningwork 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.


40/92

SAP AG TSCM52 24-38

SAP AG 2001

Technical Design Planning

Set up Development Environment

System Administration Procedures

Business

BlueprintBusiness

Blueprint

Accelerators:

IT Infrastructure Document

SAP Web Installation Guides

SAP Software and License Keys

Activities

Activities

Establish Development EnvironmentUpgradeSrategy

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.


41/92

SAP AG TSCM52 24-39

SAP AG 2001

Available nowhttp://service.sap.comFor customersand Partners

K

Y

O

M

P

O

N

The SAP Service Marketplace is SAPs one-stop Internet platform that providespersonalized access to all services necessary to design, build and maintain ahigh quality solution

Benefits

Easy, one-stop access toSAP services - anytime,anywhere

A full range of services toensure solutioncompleteness

Information that is easy tofind and understand, asyou navigate easilythrough well-organizedtopics - and you canpersonalize the site to suityour 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


42/92

SAP AG TSCM52 24-40

SAP AG 2001








QMQM


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 namingconventions 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.


43/92

SAP AG TSCM52 24-41

SAP AG 2001

Schedule and Prepare OrganizationStructure Workshop

Conduct OrganizationStructure Workshop

Recommend and ApproveOrganization Structure

Accelerators:

Organization Structure Presentation

Enterprise Modeling - Consultant's Handbook


Tasks

1

1

SAP Reference Model

Organization

Business Strategy

Define Business Organization Structure

BusinessBlueprintBusinessBlueprint

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.


44/92

SAP AG TSCM52 24-42

SAP AG 2001QAdb 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

11

mySAP.com

KPIBusiness 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 theSAP 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 draftsthereof would be stored here.


45/92

SAP AG TSCM52 24-43

SAP AG 2001

QAdb Documents

1

1

QAdb

QAdb

QAdb

User

Issues

Report

Development

Basis


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 companys requirements in detail and adapt process models to

reflect your companys 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 AssociatedItems 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.


46/92

SAP AG TSCM52 24-44

SAP AG 2001


Associated Items 2

Information

Note:Availability of Associated

Items Objects depends on

Structure Level

Functions

Input / Output

Organizational Units


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.


47/92

SAP AG TSCM52 24-45

SAP AG 2001

Compose Project Structure

SAP Project Reference Structure SAP Product Reference Structure

R/3BBP

SAP Reference StructureSAP Reference Structure

1

1

Development

Basis Components


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


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 ReferenceStructures 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 theQ&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

underAdministration -> 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 ProductReference Structure to the SAP Project Reference Structure (from right to left) and processed in

the Q&Adb.


48/92

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


1 Structure Item A

3 Structure Item E


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 scopemenu item.

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


49/92

SAP AG TSCM52 24-47

SAP AG 2001

Set Owner


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 customers 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 Ownerreport option

This means that only those structure items that are assigned to you or to one of your teammembers 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.


50/92

SAP AG TSCM52 24-48

SAP AG 1999

Issues Database

DetailsDetails PriorityPriority,, Status, Project phase,Status, Project phase,

Responsible Responsible

Action Item Prority, ResolutionAction Item Prority, Resolution

Effort Category, Planned, Actual,Effort Category, Planned, Actual,

Remainung Remainung

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

AllAll by Classificationby Classification

All by Project PhaseAll by Project Phase

AllAllIssuesIssues

Closed IssuesClosed Issues

........

Issue Editor and DocumentationIssue Editor and DocumentationOpen IssuesOpen Issues

UnsolvedUnsolved

ProblemsProblems

Edit View Reports

Administrative

Issues

All Issues

Current View

ListingListinginin

EXCELEXCEL TableTable

TheIssuessubstructure 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.


51/92

SAP AG TSCM52 24-49

SAP AG 1999

Business Strategy

2 General Enterprise Strategy

2 Markets

2 Procurement Strategy


1 Business Strategy Question


Business Analysis Status

Business

BlueprintBusiness

Blueprint

In this substructure, you can gather information on your enterprises 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.


52/92

SAP AG TSCM52 24-50

SAP AG 2001

mySAP.com


1 mySAP.com

2 Workplace

3 Buy Side

2 The Marketplace

3 Sell Side

Question

CI Template


Business Analysis Status

Business

BlueprintBusiness

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.


53/92

SAP AG TSCM52 24-51

SAP AG 2001

Organizational Structure


1 Organization

2 Procurement....

3 Company Code

2 Cross-application....

3 Controlling Area ...

Business Analysis

Question

CI Template


SAP Documentation

IDES Documentation

Status

Information

Business

BlueprintBusiness

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 companys structure and processes that allow an initial mapping of the

companys 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).


54/92

SAP AG TSCM52 24-52

SAP AG 2001

UsersUsers

IssuesIssues

StatusStatus

Master listsMaster lists

BPMLBPML

OSLOSLDLDL

ALAL

Business BlueprintBusiness Blueprint-

-

-

mySAPmySAP.com.com-

Reports (Business Organization Structure)

Edit View Reports

Business strategyBusiness strategy

Scope documentScope document

ReportsReports

-

Scope document

Business strategymySAP.com

Business Blueprint

All

KPI

Organizational structure

General settings

Master data

Business processes

Cross-application

components

User roles

Training and

documentation

DevelopmentMaster lists


List

Business Process Master

List

Development List

Authorization List

Status Report

Administrative

Issues

-

-

Business

BlueprintBusiness

Blueprint

Reportsallows you to display project documentation in different forms, and creates a report structure

in the Q&Adb.


55/92

SAP AG TSCM52 24-53

SAP AG 2001








QMQM


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 businessprocesses.

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 companys multi site

and/or multi national implementation of SAP product.


56/92

SAP AG TSCM52 24-54

SAP AG 2001

BusinessBlueprint

Business ProcessQuestions

SAP Reference

Structure

INPUT OUTPUTBusiness Process

Definition

Technical AnalysisFunctionalSpecifications

OrganizationalStructure

MasterLists

Business AnalysisQuestionsCI TemplateBP Transactions


Business

BlueprintBusiness

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 companys 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.


57/92

SAP AG TSCM52 24-55

SAP AG 1999

ActivitiesPrepare for Business Process Workshops

Conduct General Requirements Workshops

Accelerators:

Business Consulting Approach to Improve KPIs

Sample Measure Driver Tree

Sample Business Blueprint

SampleSample

Scope DocumentScope Document

InputInput

DEDE

USUS

CHCH

DMDM

USDUSD

CHFCHF

ISOISO NormsNorms

Numbering systemsNumbering systems, Chart of, Chart of accountsaccounts......

Business

BlueprintBusiness

Blueprint


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


58/92

SAP AG TSCM52 24-56

SAP AG 2001

General Settings and Master Data


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


SAP Documentation

IDES Documentation

Information

Status

Business

BlueprintBusiness

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.


59/92

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

BlueprintBusiness

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.


60/92

SAP AG TSCM52 24-58

SAP AG 1999

Conduct Business Process Workshops (2)

4 Process Groups

5 Processes

2 Enterprise Areas

3 Scenarios


1 Business Processes Technical

Analysis

Business Analysis

Question

CI Template

BP Transaction

User Roles


SAP Documentation

IDES Documentation

Information

Status

1 User Roles

Business

BlueprintBusiness

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:

Yes, No, Unanswered

Answer list

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

answered freely.


61/92

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


1 Business Processes

Conduct Business Process Workshops - Modeling

Business

BlueprintBusiness

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:

High, through Customizing

Medium, through enhancement

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.


62/92

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

BusinessBusiness ProcessProcess TransactionsTransactions

RunRun

R/3R/3 TransactionTransaction

UserUserProfileProfile

R/3 InformationR/3 Information

4 Process Groups

5 Processes

2 Enterprise Areas

3 Scenarios



Conduct Business Process Workshops - BP Ta.

Business

BlueprintBusiness

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 implementedC1-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.


63/92

SAP AG TSCM52 24-61

SAP AG 2001

User Roles

4 Process Groups

5 Processes

2 Enterprise Areas

3 Scenarios



Business Analysis

Questions

CI template

Transactions

Assigned user roles

User roles by

transactionTransactions by

user role

Project documentation

SAP documentation

IDES documentation

1 User Roles

Business

BlueprintBusiness

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.


64/92

SAP AG TSCM52 24-62

SAP AG 2001

Assemble Business Blueprint

Identify Baseline Scope

Verify Business Blueprint Completeness

Tasks

Reports

ReportsReports

Reports

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.


65/92

SAP AG TSCM52 24-63

SAP AG 2001

Reports (Business Process Definition)

UsersUsers

IssuesIssues

StatusStatus

Master listsMaster lists

BPMLBPML

OSLOSL

DLDL

ALAL

Business BlueprintBusiness Blueprint-

-

-

mySAPmySAP.com.com-

Edit View Reports

Business StrategyBusiness Strategy

Scope documentScope document

ReportsReports

-

Scope document

Business strategy

mySAP.com

Business Blueprint

All

KPI


General settings

Master data

Business processes

Cross-application

components

User roles

Training and

documentation

Development

Master Lists


List

Business Process Master

List

Development List

Authorization List

Status Report

Administrative

Issues

-

-

BusinessBlueprintBusinessBlueprint

Reports allows you to display project documentation in different forms, and creates a report structure

in the Q&Adb.


66/92

SAP AG TSCM52 24-64

SAP AG 2001

Tasks

Busin

ess

Busin

ess

Blue

print

Blue

print

Blueprint Document Review and Signoff

Business

BlueprintBusiness

Blueprint

Prepare for Presentation of Blueprint Review

Conduct Review and Sign-Off

Accelerators:

Business Blueprint Quality Checklist

Project Signoff Form

Executive Summary of Business BlueprintPowerpoint 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


Baseline scope

Technical design

System landscape

You have now completed your second project milestone.


67/92

SAP AG TSCM52 24-65

SAP AG 2001

QMQM





Business Process DefinitionBusiness Process 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

r