You are on page 1of 11

Business Scenario Design Document

INTERNAL
TABLE OF CONTENTS
1 BUSINESS SCENARIO/BUSINESS AREA DESCRIPTION............................................................3
2 BUSINESS CONTEXT..................................................................................................................... 4
2.1 Business Objectives and Expected Benefits................................................................................4
2.2 Major Business Pain Points (to achieve business objective).....................................................4
2.3 High Level Business Requirements (to achieve business objective)........................................4
2.4 Key Financial Performance Indicators (KPIs)...............................................................................4
2.5 Organizational Change Impact...................................................................................................... 5
3 FUNCTIONAL AND PROCESS DESIGN......................................................................................... 5
3.1 Organizational Structure................................................................................................................ 5
3.2 Roles................................................................................................................................................ 6
3.3 Master Data...................................................................................................................................... 6
3.4 Related Systems (being replaced or Interfaced with)..................................................................6
3.5 Major Data Sources for Conversion..............................................................................................6
3.6 Policy and Compliance................................................................................................................... 7
3.7 Process Scope................................................................................................................................ 7
3.7.1 Sales Quotation.............................................................................................................................. 7
3.7.2 Credit Memo Processing................................................................................................................ 9

2
1 BUSINESS SCENARIO/BUSINESS AREA DESCRIPTION
Provide an overall description of the business scenario/business area.
At this point a high-level enterprise view is provided highlighting the business scenario/business area.

3
2 BUSINESS CONTEXT

2.1 Business Objectives and Expected Benefits


Describe the business objective and expected benefits. These are the measurable improvements that will be
delivered by business requirements. These are drawn from the value case produced in the Discover phase.

Business Objectives and Expected Benefits


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

2.2 Major Business Pain Points (to achieve business objective)


Provide a high-level list of pain points based on business scenario and solution mapping in Discover phase.

Major Pain Points from weaknesses analysis


Pain Point ID Pain Point Description Impact on Business Contact

2.3 High Level Business Requirements (to achieve business objective)


Provide a list of high-level business requirements and expectations. These are refined in the Fit-to-Standard
process.

Business Requirement (High level)


Req. ID Requirement Description Standard/ Gap Priority Contact

2.4 Key Financial Performance Indicators (KPIs)


List the KPIs

Key Performance indicators


KPI Name

4
Owner

Definition

Calculation

Drill Down Capabilities

Supporting SAP Solution


Components

Planned Data Source

Reporting Method

Frequency

Used by

2.5 Organizational Change Impact


Identify organizational entities in scope: groups, divisions, plants, departments. Note roles/jobs in the current
organization. Identify potential changes.

Process Step Description


ID Organization Entity Role Potential Change

3 FUNCTIONAL AND PROCESS DESIGN

3.1 Organizational Structure


List SAP organization structure items required to support his business scenario/business area.

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

Cost Center Cost Center Copied from Technical Object

Profit Center

Sales Organization

Distribution Channel

Division

For each item, note any customer requirements and describe the SAP solution to meet the requirements.
Insert organization structure diagrams as necessary.

5
3.2 Roles
List business roles needed to support his business scenario/business area. Note any unique customer
authorization requirements.

Roles

Role Description SAP Role(s) Authorization Requirements


Internal Sales
Tele-sales
Representative

3.3 Master Data


List master data elements needed to support his business scenario/business area. Note any unique
customer requirements.

Master Data

Data Object Description SAP Object Unique Requirements

Customers SAP Business Partner

3.4 Related Systems (being replaced or Interfaced with)


List the system(s) currently used to enable this business scenario/business area. Indicate which ones will be
decommissioned and which ones will have interfaces.

Related Systems

System Role Impact Interfaces

Oracle ERP System End to end ERP Replaced by SAP None

Serial Tracking System Serial number tracking Replaced by SAP None

Payroll Interface with SAP

3.5 Major Data Sources for Conversion


List the data conversion requirements and the source systems.

Data Sources

System Source Data Object Volume Approach

Oracle ERP System Sales Order S/4HANA Migration Cockpit

Oracle ERP System Sales Bills of Material S/4HANA Migration Cockpit

Oracle ERP System Customers S/4HANA Migration Cockpit

6
3.6 Policy and Compliance
List company policies and compliance requirements. For example, SOX, GDPR and Segregation of Duty
considerations.

3.7 Process Scope


List the business processes or scope items. Indicate whether they are in or out of scope of this business
scenario/business area. Identify the proposed SAP Solution(s). Reference SAP Best Practices and SAP
Model Company.

Process Scope
ID Process Name Description In Scope SAP Solution
Creation of a standard sales quotation with
BDG Sales Quotation Yes S/4HANA Sales
conversion to a sales order.
You can apply a credit to a customer
account once you determine if a customer
1EZ Credit Memo Processing Yes S/4HANA Sales
has been overcharged because of a pricing
or sales tax rate error.

Provide more detail for processes that require additional design where the SAP Best Practice or Model
Company process must be extended.

3.7.1 Sales Quotation


Include or reference the relevant process flows.

7
Document key process characteristics including volumes.

Process Characteristics

Trigger

Input

Output

Business Process Owner

Volumes

Frequencies

Summarize configuration approach and reference configuration requirements.


List delta requirements or provide a reference to a central repository.

Delta Requirements
ID Delta Requirement Description Type Outline Solution

8
3.7.2 Credit Memo Processing
Include or reference the relevant process flows.

Document key process characteristics including volumes.

Process Characteristics

Trigger

Input

Output

9
Business Process Owner

Volumes

Frequencies

Summarize configuration approach and reference configuration requirements.


List delta requirements or provide a reference to a central repository.

Delta Requirements
ID Delta Requirement Description Type Outline Solution

10
www.sap.com/contactsap

© 2018 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.

You might also like