BUSINESS SCENARIO/END-TO-END PROCESS

PUBLIC
PROJECT IDENTIFICATION
Delete Project Identification table if not applicable for the document!
Project Name CPI Project Number
<Project Name>
Customer Name Customer Number
<Customer Name>
SAP Project Manager Customer Project Manager
<SAP Project Manager> <Customer Project Manager>

DOCUMENT IDENTIFICATION
Document Identification Instruction:
 Update document location
Location could be Solution Manager or other relevant project repository
 Update Version, Status, and Date
Possible statuses are Draft, Ready for internal review, Released for customer, Final. You can for example
number the appropriate versions as follows:
o Draft
o Ready for internal review
o Ready for internal review (in case of major changes)
o Released for customer
o Final
 Update classification:
Internal means the document is restricted to SAP internal use only. Confidential means that only a defined
group of people (such as a CDP team and their customer) have access to the document.

Be sure to delete these instructions when you have finished!

Author Document Location (repository/path/name)
<Author> <Document location>
Version Status Date (YYYY-MM-DD) Document Classification
0.1 Final <Date> Confidential

REVISION HISTORY
Delete Revision History section below if not applicable for the document!

Version Date Description

0.1 <Text here>
0.2

REVIEW AND APPROVAL

Delete Review and Approval section below if not applicable for the document!

2
Name Date (YYYY-MM-DD)
Customer Project Manager

Name Date (YYYY-MM-DD)

SAP Project Manager

Name Date (YYYY-MM-DD)

Key Stakeholder

Name Date (YYYY-MM-DD)

Key Stakeholder

3
TABLE OF CONTENTS
BUSINESS SCENARIO/END-TO-END PROCESS DESCRIPTION................................................................5
VALUE REALIZATION.................................................................................................................................... 6
Business Objectives and Expected Benefits............................................................................................... 6
Major Business Pain Points (to achieve business objective).....................................................................6
Key Business Requirement (to achieve business objective).....................................................................6
Key Financial Performance Indicators (KPIs)..............................................................................................6
ORGANIZATIONAL CHANGE IMPACT.......................................................................................................... 8
FUNCTIONAL AND PROCESS DESIGN (IN SAP)......................................................................................... 8
Organizational Structure (in SAP)................................................................................................................. 8
Master Data Elements.................................................................................................................................... 8
Business Scenario/End-to-End Process Scope...........................................................................................9
Business Scenario/End-to-End Process Model...........................................................................................9
Business Scenario/End-to-End Process Diagrams...................................................................................10
Legacy Systems Being Replaced and/or Interface To...............................................................................10
Initial List of Major Identified Gaps............................................................................................................. 10
Initial List of Major Integration and Policy/SOX Considerations..............................................................10
Initial List of Major Data Sources for Conversion......................................................................................11

4
BUSINESS SCENARIO/END-TO-END PROCESS DESCRIPTION
Provide a description of the business scenario/end-to-end process. At this point a high level enterprise view from
Process Area (e.g. Sales) or Process Group (Channel Sales) will be provided.

Sample for a process map, to be replaced with actual map, highlight the scenario entry point in the process map:

5
VALUE REALIZATION

Business Objectives and Expected Benefits

Describe the business objective and expected benefits. These are the measurable improvements that result in achieving
their business requirements.

Business Objectives and Expected Benefits

Process
Business Change Biz Case KPI
Value Owner Target Benefit
Objectives (Key Business (financial)
Requirement)

Major Business Pain Points (to achieve business objective)

Provide a high-level list of requirements and expectations.-link to the Value Dependency document.

Major Pain Points from weaknesses analysis

Pain Point Impact on
Pain Point ID Contact
Description Business

Key Business Requirement (to achieve business objective)

Provide a high-level list of requirements and expectations.-link to the Value Dependency document and to be leveraged
for Business Process Requirement Gathering sessions.

Business Requirement (High level)

Req. Standard/
Requirement Description Priority Contact
ID Gap

Key Financial Performance Indicators (KPIs)

List the KPIs

6
Key Performance indicators
KPI Name
Owner
Definition
Calculation
Drill Down
Capabilities
Supporting SAP
Solution
Components
Planned Data
Source
Reporting Method
Frequency
Used by

7
ORGANIZATIONAL CHANGE IMPACT
Identify organizational entities in scope – groups, divisions, plants, departments. Note roles/jobs in the current
organization and potential change to those groups.

Process Step Description

ID Organization Entity Role Potential Change

FUNCTIONAL AND PROCESS DESIGN (IN SAP)

Organizational Structure (in SAP)

List organization structure items required to support his business scenario/end-to-end process. For each item, note the
customer requirements and describe the SAP solution to meet the requirements

Organizational Structure
Corresponding Explanation if
Relevant Organizational
ID organization necessary
Unit SAP
(e.g. Customer) (e.g. Mandatory)
Company code Company Code (Initialized from Plant Code)

Physical site where Maintenance

Maintenance Plant
Maintenance Planning Plant
Mill
activities will be done
Plant which will Provide
Mill
Maintenance Work (=Mill)

Planner Group Supervisor and Work Planner

Work Center Work Group

Cost Center Cost Center Copied from Technical Object

Profit Center

Sales Organization

Distribution Channel

Division

Insert Org. Structure diagrams as necessary.

Master Data Elements

List master data elements needed to support his business scenario/end-to-end process. Note all unique customer
requirements and how they will be met in SAP.

8
Business Scenario/End-to-End Process Scope
List the business processes. Indicate whether they are in or out of scope of this business scenario/end-to-end process.
Identify the proposed SAP Solution(s) i.e., SD, WM.

Business Scenario/End-to-End Process Scope

SAP
ID Process Name Description In Scope
Solution
Production planning activities
Production Planning generates all the production plans in Yes PP
support of business requirements
Manufacturing execution will create
and release production orders, assign
serial numbers to the upper
Manufacturing Execution Yes PP, WM, MM
assemblies, confirm operational steps
once complete, receive assemblies
into warehouse stock.

Business Scenario/End-to-End Process Model

Characteristics
Trigger
Input
Output
Owner
Volumes
Frequencies

9
Business Scenario/End-to-End Process Diagrams
Where applicable, provide links to process maps, refer to ARIS/ Visio diagrams, see example given below.

Legacy Systems Being Replaced and/or Interface To

List the system(s) currently used to enable this business scenario/end-to-end process. Indicate which ones will be
decommissioned and which ones will have interfaces. For example:
 Oracle ERP System – replaced with SAP
 Legacy Serial Tracking System – replaced with SAP
 Quality system – replaced with SAP

Initial List of Major Identified Gaps

List any known or perceived gaps in the SAP solution(s). For example:
 Sequential system generated Serial number assignment with number that contains alpha numeric characters.

Initial List of Major Integration and Policy/SOX Considerations

Note known integration topics/issues with other teams. List company policies and SOX considerations impacted by this
business scenario/end-to-end process. For example:
 Integration Considerations:
 Inventory control
 Product costing settlement

10
Initial List of Major Data Sources for Conversion
List the data conversion requirements and the source systems. For example:
 Existing in-process production orders from Oracle
 Bills of materials from Oracle
 Routings from Oracle

11
www.sap.com/contactsap

© 2017 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.