EHP7 for SAP ERP 6.0
February 2014
English
Global Base
Organization
Management (F46)
Building Block Configuration Guide
SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
Copyright
© 2014 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.
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. Please see
http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and
notices.
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 SE or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP SE 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, which speak only as of their dates, and they should not be relied upon in making purchasing
decisions.
© SAP SE
Page 2 of 14
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
Icons
Icon
Meaning
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style Description
Example text Words or characters that appear on the screen. These include field names,
screen titles, buttons as well as menu names, paths, and options.
Cross-references to other documentation.
Example
text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE
TEXT
Names of elements in the system. These include report names, program
names, transaction codes, table names, and individual key words of a
programming language, when surrounded by body text, for example, SELECT
and INCLUDE.
Example
text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as names
of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the ENTER
key.
Example
text
Exact user entry. These are words or characters that you enter in the system
exactly as they appear in the documentation.
<Example
text>
Variable user entry. Pointed brackets indicate that you replace these words
and characters with appropriate entries.
Example text This text denotes entries that are SAP standard settings. These entries are not
configured by the SAP Best Practices for HCM package (EhP7) and are
included for informational purposes.
© SAP SE
Page 3 of 14
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
Contents
1
2
3
4
5
6
7
Purpose ......................................................................................................................................... 5
Preparation .................................................................................................................................... 5
Organization Management ............................................................................................................ 5
3.1
Benefits to Users ................................................................................................................. 5
3.2
Delivery and Handling of Organization Management ......................................................... 5
Personnel Management ................................................................................................................ 6
4.1
Global Settings in Personnel Management......................................................................... 6
4.1.1
Set Active Plan Version .................................................................................................. 6
4.2
Organizational Management/Basic Settings ....................................................................... 6
4.2.1
Set up Number Assignment for all Plan Versions ........................................................... 6
4.2.2
Maintain Number Ranges ............................................................................................... 7
4.2.2.1 Number Range Maintenance...................................................................................... 7
4.2.3
Data Model Enhancement / Maintain Relationships ....................................................... 8
4.3
Transport/Set Up Transport Connection ............................................................................. 9
Organizational Structure .............................................................................................................. 10
5.1
Relations in the Organizational Structure ......................................................................... 11
Jobs ............................................................................................................................................. 11
Positions ...................................................................................................................................... 13
7.1
Relations Organizational Units, Positions, Jobs ............................................................... 14
© SAP SE
Page 4 of 14
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
Global Base Organization Management:
Configuration Guide
1
Purpose
This configuration guide provides the information you need to configure this building block manually.
2
Preparation
Before you start installing this scenario, you must install the prerequisite building blocks. For more
information, see the Building Block Prerequisites Matrix for the SAP Personnel Administration and
Organization Management rapid-deployment solution. You will find this document in the content
library attached to the Step-by-Step Guide.
3
Organization Management
The organizational structure is created by defining organizational units and positions. An
organizational structure is a comprehensive and dynamic model of the structural and personnel
environment in your company, which you can evaluate at any time. Since an organizational structure
is company-specific, we deliver a basic, sample organizational structure with the common jobs,
positions and organizational units that can be used or renamed; additional objects can be easily built
to meet the client’s requirements.
This configuration guide contains the basic configuration required for the setup of a global
organization structure. The first hierarchies are created within this Building Block and will be
enhanced with application specific objects within the RDS packages.
3.1 Benefits to Users
This SAP Best Practices for HCM package provides an out-of-the-box environment with which the
customer can become familiar with business simulations such as those for reorganizing
organizational structures, forecasting staff counts, and studying the impact of introducing new jobs,
planning for contingencies, and realigning responsibilities. Different configuration scenarios can be
created easily and tested from this solid base.
3.2 Delivery and Handling of Organization Management
This SAP Best Practices for HCM package is delivered with both customizing data relating to
Organization Management as well as the associated master data. The data includes all PD object
types used in this SAP Best Practices for HCM package, along with all the related infotypes for these
objects. If the master data is not required for use in the production system, the delivered objects and
their infotypes may be deleted with the SAP standard program RHRHDL00, which allows all or
specific PD objects to be deleted. See the report documentation for further details.
If objects are deleted, the number range should also be updated to reflect the status of
the next current number. This ensures that the object IDs are properly sequenced.
© SAP SE
Page 5 of 14
SAP Best Practices for HCM Package
4
Global Base OM (F46): Configuration Guide
Personnel Management
4.1 Global Settings in Personnel Management
4.1.1 Set Active Plan Version
Use
In this step, you specify which plan version is to be the active plan version, that is, the plan version in
which you maintain current valid information on your enterprise.
The following should be taken into consideration before you determine your active plan version:

If integration is active, the plan version you specify here is the integration plan version for all
Personnel Planning and Development components (Organizational Management, Shift
Planning, Personnel Development, Personnel Cost Planning, as well as Training and Event
Management). You do not, therefore, have to enter a new plan version for each component
you install.

If you have several Personnel Planning and Development components installed,
retrospective changes to the active or integration plan version can lead to data
inconsistencies.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
OOAP
SAP Customizing Implementation Guide Personnel
Management  Global Settings in Personnel Management 
Plan Version Maintenance  Set Active Plan Version
IMG Path
2. On the Change View “Set Active Plan Version”: Overview screen, make the following entries:
Group
Sem.Abbr.
Value
Description
PLOGI
PLOGI
01
Integration Plan Version / Active Plan Version
3. Save your entries.
4.2 Organizational Management/Basic Settings
4.2.1 Set up Number Assignment for all Plan Versions
Use
The cross-plan version number assignment switch is not set in this SAP Best Practices package.
Once the installation is complete, the following entry should be set to ensure that number
assignments across plans are consistent.
If you decide not to work with number assignment valid for all plan versions, you must create
individual number ranges for each plan version (and possibly also for each object type).
© SAP SE
Page 6 of 14
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
Procedure
1. Access the activity using one of the following navigation options:
Transaction
Code
OONC
SAP Customizing Implementation Guide  Personnel Management 
Organizational Management  Basic Settings  Maintain Number Ranges
 Set Up Number Assignment for All Plan Versions
IMG Path
2. On the Change View “No Assignment for All Plan Versions””: Overview
following entries:
screen, make the
Group
Sem.Abbr.
Value
Description
NUMRG
COMP
X
Number assignment for all plan versions
3. Save your entries.
4.2.2 Maintain Number Ranges
4.2.2.1
Number Range Maintenance
Use
The system is delivered with subgroup $$$$ that defines the number range to be used for all objects.
A different range of numbers can be defined for each type of organization object, that is,
organizational units, jobs, and positions. By defining a unique number range for each object type,
you can easily identify the type of object, which can also be a benefit for reporting purposes. These
new subgroups/number ranges override the $$$$ number ranges. Both external and internal number
ranges have been configured in this SAP Best Practices for HCM package to allow a user to assign
a specific number to the object or to allow the system to automatically assign the number when the
object is being created.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
OONR
IMG Path
SAP Customizing Implementation Guide  Personnel
Management  Organizational Management  Basic Settings 
Maintain Number Ranges  Maintain Number Ranges
2. On the Change View “Number Assignment””: Overview screen, choose the New Entries button.
3. Enter the values from the table below:
Subgroup
Number Range Internal
Assignment
Number Range External Assignment
$$C
IN
EX
$$O
IN
EX
$$S
IN
EX
4. Choose Save.
5. On the Change View “Number Assignment”: Overview screen, select the row with subgroup
$$$$ and choose the Number Range Maintenance button.
6. Choose the Change Intervals button.
© SAP SE
Page 7 of 14
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
7. The following number ranges are delivered with this SAP Best Practices for HCM package.
Check or enter the values below for the corresponding subgroup $$$$.
Sub object
No.
From Number
To Number
Current Number
External
$$$$
EX
00000001
49999999
0
Select
$$$$
IN
50000000
59999999
0
$$C
EX
00000001
49999999
0
$$C
IN
60000000
69999999
0
$$O
EX
00000001
49999999
0
$$O
IN
80000000
89999999
0
$$S
EX
00000001
49999999
0
$$S
IN
70000000
79999999
0
Select
Select
Select
8. Save your entries.
9. Repeat this process, starting at step 5, until all of the remaining subgroups ($$C,$$O,$$S) have
been assigned the corresponding number ranges.
OM Object
Description
External
Internal
$$$$
All other OM objects
00000001-49999999
50000000-59999999
$$C
Jobs
00000001-49999999
60000000-69999999
$$S
Positions
00000001-49999999
70000000-79999999
$$O
Organizational units
00000001-49999999
80000000-89999999
4.2.3 Data Model Enhancement / Maintain Relationships
Use
In this step, you make the settings that are required for creating relationships.
By creating relationships between objects, you can display all the structures that exist in Personnel
Management.
Relationships are special subtypes of infotype 1001. Each relationship has two relationship types,
indicated by A and B. The corresponding inverse relationship is automatically set up for each
relationship created (A or B) and is delivered as part of the standard system.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
SAP Customizing Implementation Guide  Personnel Management
 Organizational Management  Basic Settings  Data Model
Enhancement  Relationship Maintenance  Maintain
Relationships
2. On the Change View “Links”: Overview screen, select relationship 008 and double-click
Relationship Characteristics. Modify any existing entries or choose the New Entries button.
© SAP SE
Page 8 of 14
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
3. Enter the values from the table below:
A/B
Relationship
Relationship
Name
100% Check
Check Work
Schedule
Check
Obsolete
A
008
Holder
W
E
B
008
Holder
W
E
4. Choose Save.
4.3 Transport/Set Up Transport Connection
Use
In this step, you specify which type of transport connection you wish to use to transport personnel
planning objects from the Customizing client. The standard setting is to not transport organizational
objects or infotypes as these are considered to be master data.
Procedure
1. Access the activity using one of the following navigation options:
IMG Path
Transaction Code
OOCR
IMG Path
SAP Customizing Implementation Guide  Personnel Management
 Organizational Management  Transport  Set Up Transport
Connection
2. On the Change View “Set Up PD Transport Connection”: Overview screen, make the following
entries:
Group
Sem.Abbr.
Value
Description
TRSP
CORR
X
Transport switch (X = No Transport)
TRSP
STOBJ
Redefinition: Standard Transport Object
TRSP
WFOBJ
Redefinition: Workflow Transport Object
3. Save your entries.
© SAP SE
Page 9 of 14
SAP Best Practices for HCM Package
5
Global Base OM (F46): Configuration Guide
Organizational Structure
Texts are kept simple and generic so that they can be easily overwritten by the customer. A skeleton
structure is built, comprising a root org. unit and below this a hierarchical structure containing sample
sub-org. units. Such a structure could be applied to both single and multi-country customers alike. A
sample number of divisions are created below the root structure, together with sample departments,
along functional lines (for example, Finance, Human Resources, and so on). The assignment of org.
units to company codes, controlling areas, cost centers, and so on, is not part of the delivered values
as these settings would need to be reset for each customer. An illustration of what the org. structure
looks like is included below.
Use
Organization Management is the basis for additional Human Resources components and functions
as well as for SAP Business Workflow, CRM, and SRM, for example. The fact that these
components can be integrated should be taken into account when you are building the
organizational structure.
To view the organization units provided in the system, use one of the following navigation options:
Transaction Code
PPOME
Menu Path
SAP Menu  Human Resources  Organizational Management 
Organizational Plan  Organization and Staffing  Change
Below is a sample of the organizational units (O objects) that are provided in this SAP Best Practices
for HCM package org. structure:
Object ID
Short Text
Long Text
Validity Period
10001001
Global Compa
Global Company
01/01/1900 - 12/31/9999
10001002
Headquarters
Headquarters
01/01/1900 - 12/31/9999
10001003
Adm Services
Administrative Services
01/01/1900 - 12/31/9999
10001004
Human Res
Human Resources
01/01/1900 - 12/31/9999
10001005
Finance
Finance
01/01/1900 - 12/31/9999
10001006
Marketing
Marketing
01/01/1900 - 12/31/9999
10001007
Sales
Sales
01/01/1900 - 12/31/9999
10001008
Operations
Operations
01/01/1900 - 12/31/9999
10001009
Manfacturing
Manfacturing
01/01/1900 - 12/31/9999
10001010
Services
Services
01/01/1900 - 12/31/9999
10001011
Purchasing
Purchasing
01/01/1900 - 12/31/9999
The object ID shown in the table might differ in your manual configuration due to the customer’s own
number ranges.
© SAP SE
Page 10 of 14
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
5.1 Relations in the Organizational Structure
Below is a sample of the hierarchy relation within the organization structure.
Organizational Unit
Hierarchy Level
Related below Org Unit
Global Company
0
Headquarters
1
Global Company
Administrative Services
2
Headquarters
Human Resources
2
Headquarters
Finance
2
Headquarters
Marketing
2
Headquarters
Sales
2
Headquarters
Operations
2
Headquarters
Manufacturing
2
Headquarters
Services
2
Headquarters
Purchasing
2
Headquarters
Creating historical HR org. structure master data is not in scope. Nevertheless, validity dates for the
org. units, jobs and positions delivered is set to 01/01/1900, to provide flexibility, in case a client has
implemented an alternative organizational structure relating to CRM or other applications. Texts are
kept simple and generic so that they can be easily overwritten by the customer. A skeleton structure
is built, comprising a root org. unit and below this a hierarchical structure containing sample sub-org.
units. Such a structure could be applied to both single and multi-country customers alike. A sample
number of divisions are created below the root structure, together with sample departments, along
functional lines (for example, Finance, HR, and so on).
The assignment of org. units to company codes, controlling areas, cost centers, and so on, is not
part of the delivered values as these settings would need to be reset for each customer.
6
Jobs
Jobs are classifications of functions in an enterprise (administrator, for example), which are defined
by the assignment of characteristics. Jobs serve as descriptions which apply to several positions
with similar tasks or characteristics.
Note the validity period used (January 1st, 1900 through December 31st, 9999). We recommend a
similar approach to date validity as you build your organizational structures.
To view the jobs provided in this SAP Best Practices for HCM package , use one of the following
navigation options:
Transaction Code
SAP Menu Path
© SAP SE
PPOME
SAP Menu  Human Resources  Organizational Management 
Organizational Plan  Organization and Staffing  Change
Page 11 of 14
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
Below is a sample of the jobs (C objects) that are provided in this SAP Best Practices for HCM
package (EhP7) org. structure:
Object ID
Short Text
Long Text
Validity period
10002001
CEO
Chief Executive Officer
01/01/1900 - 12/31/9999
10002002
VP
Vice President
01/01/1900 - 12/31/9999
10002003
Director
Director
01/01/1900 - 12/31/9999
10002004
Manager
Manager
01/01/1900 - 12/31/9999
10002005
Supervisor
Supervisor
01/01/1900 - 12/31/9999
10002006
Controller
Controller
01/01/1900 - 12/31/9999
10002007
Specialist
Specialist
01/01/1900 - 12/31/9999
10002008
Maintenance
Maintenance
01/01/1900 - 12/31/9999
10002009
Security
Security
01/01/1900 - 12/31/9999
10002010
Auditor
Auditor
01/01/1900 - 12/31/9999
10002011
Trainer
Trainer
01/01/1900 - 12/31/9999
10002012
Recruiter
Recruiter
01/01/1900 - 12/31/9999
10002013
Acc Exec
Account Executive
01/01/1900 - 12/31/9999
10002014
Admin Assist
Administrative Assistant
01/01/1900 - 12/31/9999
The object ID shown in the table might differ in your manual configuration due to the
customer’s own number ranges.
© SAP SE
Page 12 of 14
SAP Best Practices for HCM Package
7
Global Base OM (F46): Configuration Guide
Positions
A position represents a post that can be occupied by a person (employee) in the staff assignments
of an organization unit, purchasing administrator, for example.
The assignment of positions to company codes, controlling areas, cost centers, personnel areas,
personnel subareas, employee groups and subgroups, and so on, is not part of the delivered values
as these settings would need to be reset for each customer. Where it is not possible to assign an
employee to a position, the system is set to default to position 99999999. The position vacancy
switch is not activated in the global template. The system is set up to generate a warning not to
exceed 100% occupancy, to minimize the risk of more than one employee being assigned to a
position inadvertently.
To view the positions provided in the system, use one of the following navigation options:
Transaction Code
PPOME
SAP Menu Path
SAP Menu  Human Resources  Organizational Management 
Organizational Plan  Organization and Staffing  Change
Below is a sample of the positions (S objects) that are provided in this SAP Best Practices for HCM
package org. structure:
Object ID
Short Text
Long Text
Validity period
10003001
CEO
CEO
01/01/1900 - 12/31/9999
10003002
ExecAssist
Executive Assistant CEO
01/01/1900 - 12/31/9999
10003003
VP Corp Serv
VP Corporate Services
01/01/1900 - 12/31/9999
10003004
ExecAssist
Executive Assistant VP
01/01/1900 - 12/31/9999
10003005
Dir Adm Serv
Director of Admintrative
Services
01/01/1900 - 12/31/9999
10003006
Admin Assist
Administrative Assistant AS
01/01/1900 - 12/31/9999
10003007
VP Finance
VP of Finance
01/01/1900 - 12/31/9999
10003008
Admin Assist
Administrative Assistant FIN
01/01/1900 - 12/31/9999
10003009
VP HR
VP Human Resources
01/01/1900 - 12/31/9999
10003010
Admin Assist
Administrative Assistant HR
01/01/1900 - 12/31/9999
The object ID shown in the table might differ in your manual configuration due to the
customer’s own number ranges.
© SAP SE
Page 13 of 14
SAP Best Practices for HCM Package
Global Base OM (F46): Configuration Guide
7.1 Relations Organizational Units, Positions, Jobs
Below is a sample of the relation between Organizational Units and Positions as well as their related
jobs.
Organizational Unit
Position
Head
Jobs
Global Company
CEO
Head of
Organizational
Unit
Chief Executive Officer
Executive Assistant
CEO
Headquarters
VP Corporate
Services
Administrative Assistant
Head of
Organizational
Unit
Executive Assistant
VP
Administrative
Services
Director of
Administrative
Services
Administrative Assistant
Head of
Organizational
Unit
Administrative
Assistant AS
Finance
VP of Finance
VP Human
Resouces
Administrative
Assistant HR
© SAP SE
Director
Administrative Assistant
Head of
Organizational
Unit
Administrative
Assistant FIN
Human Resources
Vice President
Vice President
Administrative Assistant
Head of
Organizational
Unit
Vice President
Administrative Assistant
Page 14 of 14