Professional Documents
Culture Documents
Sap BPML
Sap BPML
Management Guide
Version 1.0 • December 2003
Document Information
About this Document
Abstract The Business Process Master List (BPML) is a key tool for use in
implementations to capture the scope of the project, drive the planning and
managing of configuration and testing. This document is an overview of
what a BPML is and how to use and manage it in an implementation. The
following pages were provided by a large COTS user and reflect their process
for using the BPML.
See also the sample BPML included in the EI Toolkit.
File Name bpml_mgmt_guise.ppt
Document Name Business Process Master List (BPML) Management Guide
Version 1.0 December 2003
Date Last Validated September 2004
Use Policy
This document was created to be used as a reference, sample or template. Contents of the EI Toolkit should not be
repurposed for publication in copyrighted material. This policy applies to all contents unless otherwise specified in a
particular document.
2
Business Process Master List (BPML) Management Guide
Version 1.0 December 2003
Table of Contents
Overview
Objectives
Utilization
File Explanation
Organization, Roles and Responsibilities
Updates Management
The BPML was originally created in the ASAP tool through the utilization
of the Project Scooping module, and adapted to Colgate business
practices by the Jaguar team
Support other Key Project Activities, such as, Change Management and
Security
And the OK Word in TESTING DATE / Column ACTUAL
The Core Team delivers subsidiary configuration in a specific dates along the
implementation calendar, these dates are identified as Configuration Cycles in the
High Level Plan
The MASTER LIST sheet has a FINAL CONFIGURATION CYCLES section with Four C
columns that represents Configuration Cycles
Core Team Leaders marks with an X the configuration / variants that will be
delivered in each configuration cycle
Once the Configuration available for each cycle is identified the implementation
team documents the corresponding business variants
During GAP Analysis implementation team develops the necessaries business
conditions to replicate their business processes in SAP R/3, AND
Evaluate the FIT of the Latin America Application Framework in their business
After GAP Analysis, there will be several integration test, each of them with
specific objectives
IT-Agendas will be based in functionality / business variants available for a
giving cycle
BPML will be used to keep teams focus to achieve test objectives
Area:
This column is used
to identify the Functional
Area of the Business
Processes
Example: Finance
Scenario:
This column is used to identify
the Scenario in which The
Business Processes are
Involved.
Example: Contract
Manufacturing
Group:
This column is a sublevel
Of the scenario, used to
Classify several process with the
Same objective.
Process:
This column is a sublevel
Of the Group, used to identify
Business processes.
Code:
This column, used to document
the T-Codes of SAP for their own
BPP
Consultant:
This column, used to assign a
Consultant that is responsible
For the specific Business process
Owner:
This column, used to assign a
CP Person that is responsible
For the specific Business process
C1:
This column, used by the core
teamto mark which business
processes are in scope to be
tested on the specific cycle
C”n”.
This will be used to generate the
Cycle “n” Worksheet.
C1 worksheet:
After identifying the scope of
The testing cycle and you
Generate the worksheet, here
Is were you find the worksheet
C1 Worksheet:
This is how the testing scope
Worksheet looks like, you have
the same process structure
(area, scenario group, process,
BPP & T-Codes this are to be
generated Automatically.
C1 Worksheet:
The Tester column is the
Person responsible to test
the specific Process
This is updated by the
Implementation team
Business Variants tested OK
Will be Marked “OK”in
TESTING DATES /
Column ACTUAL
in Section C1 of the BPML
Variants with error will
remain in RED in both
Master List and C1
Core Team
Leader Organisation
BPML
Coordinator
Subsidiary
Team Leaders
Subsidiary
Team
Functional Technical & Change Team
Teams Security
Project
Managers
Core Team
Leader Project
Managers
Core Team
BPML
Coordinator
Core Team
1.- CT Identifies or Leaders
Modifies a T-Code 6.- Updates BPML
According to form
2.- CT fills up an
Update form 7.- Emails notification Subsidiary
of New BPML Teams
3.- CT sends form version on DB
to BPML coordinator
with copy to
CT Leader Consultants
Project
Managers
BPML
Coordinator
Core Team
1.- Subsidiary Identifies Leaders
or 4.- Updates Official
Modifies a T-Code BPML
2.- Subsidiary fills up a 5.- Emails notification Subsidiary
BPML of updated BPML Teams
3.- Subsidiary sends version on DB
File to BPML
manager with copy
to Sub Leader Consultants
BPML
Coordinator
1.- After IT, results of
BVariants test will be in the Core Team
Leaders
BPML colored accordingly.
4.- Updates Official
BPML
2.- Subsidiary sends 5.- Emails notification Subsidiary
file, to BPML of updated BPML Teams
Manager with copy to version on DB
IT coordinator
Consultants