Organizational Structure Specification

INTERNAL
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>
How to use the Template

Blue text is always intended as instructions, guidelines, explanations, hints, and tips. It has to be removed when the
document is finalized. To provide a consistent representation of this document to the customer, chapters should not be
deleted or inserted. Required additions should be made as sub-chapters to existing chapters.
Chapters that are not relevant should be marked as such (that is, add “not relevant” or “not applicable”).

Be sure to delete these instructions when you have finished!

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 January 03, 2018 <Text here>

2
REVIEW AND APPROVAL
Delete Review and Approval section below if not applicable for the document!

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
REQUIREMENTS & EXPECTATIONS 5
GLOBAL DESIGN DECISIONS5
NAMING CONVENTION 5
ASSIGNMENT OF SAP ORGANIZATIONAL UNITS 5
CHANGES TO ENTERPRISE STRUCTURE 5
IMPACT OF FUTURE STATE ORGANIZATION ON SAP ORGANIZATION ELEMENTS 5
CONFIGURATION CONSIDERATIONS 5
AUTHORIZATION/SECURITY CONSIDERATIONS 5
Control Requirements 5

4
REQUIREMENTS & EXPECTATIONS
Create a bulleted list of your requirements for a specific SAP organizational structure. Using an organizational structure
diagram describe in detail each element within the structure.
These are the minimum requirements for this section.

GLOBAL DESIGN DECISIONS

Provide an overview of the system design approach to be taken for this organization structure. List the key design
decisions that impact this SAP organization structure. Make note of the requirements that are being met by this design,
and those to be left out of the design.

NAMING CONVENTION
Describe the naming and numbering conventions that the company will use for this structure item. Identify changes that
must be made in order to accommodate SAP requirements and/or best practices. (Final design decisions not required at
this time)

ASSIGNMENT OF SAP ORGANIZATIONAL UNITS

Describe the assignment of organizational unit(s) in the SAP System that is relevant to the company’s enterprise.
Include how the SAP organization structures inter-relate. Include any reasons for deviations from organizational
structure guidelines.

CHANGES TO ENTERPRISE STRUCTURE

Describe the effect of this structure item on the customer’s enterprise structure. For example:
 Will the credit collection procedure be moved to customer service?
 Will the plant be able to process more orders per day?
 Will there be an impact on head count?

IMPACT OF FUTURE STATE ORGANIZATION ON SAP ORGANIZATION ELEMENTS

Identify the impacts on this SAP organization element resulting from the future state organization. If there is no change
from what was entered in Requirements, indicate it.

CONFIGURATION CONSIDERATIONS
Describe issues of importance to the company in relation to system configuration. Capture decisions on how specific
fields will be used in ways that are not standard SAP (i.e., using storage location for material valuation). The information
captured here should be sufficient for an SAP Application Specialist to complete configuration in Realization Phase.

AUTHORIZATION/SECURITY CONSIDERATIONS
Describe the company’s security requirements in this area. Don't cover the creation of authorizations in too much detail.
Sensitize the team to the system functions and get the process owners to think about access to the system and its data.

CONTROL REQUIREMENTS
Enter control requirements with their respective rankings.

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