1 Purpose
This configuration guide provides the information you need to set up the
configuration of this building block manually.
2 Preparation
Before you start installing this building
block, you must install prerequisite building blocks. For more information, see
the Building Block Prerequisite Matrix for HCM. The matrix (an Excel file) is
linked on the solution's DVD/website in one of the following two locations:
·
Content
Library
·
Site
Map
3 Organizational Management
Organizational
Management (OM) is delivered through this SAP Best Practices package with a
model that companies can use as an example for designing their Organizational
Structure and to drive approvals. The model contains an Organizational
functional and reporting view, a quantity of jobs and with positions connected
to a job family and functional area. By focusing this SAP Best Practices
package on the main functional areas of an Organization such as
Finance/Administration, Human Resources, Information Technology, and
Sales/Distribution, a cross-Industry HR template approach is realized within
OM.
3.1 Benefits to Users
This SAP Best Practices package provides an out-of-the-box
environment whereby the customer can become familiar with such business
simulations as 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 Organizational Management
This SAP Best Practices Package is delivered with both
customizing data relating to Organizational Management as well as its Master
Data. The Master Data component is delivered and installed via a sequential
file using the standard report RHALTD00. The data includes all PD object types
used in this SAP Best Practices package Global, along with all the related
Infotypes for those objects. All PD objects delivered in this SAP Best
Practices package Global were created using external number range assignment,
so in addition to the data, the RP_PLOG number range is also delivered to
reflect the next available number in the range. If the master data is not kept
for production use, the delivered objects and their Infotypes may be deleted
with the SAP standard program RHRHDL00, which allows deletion of all or
specific PD objects. 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 proper
object id sequencing.
4 Basic Settings
4.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 intervals per plan version (and possibly also per
object type).
Procedure
1. Access
the activity using one of the following navigation options:
IMG
Path
|
Personnel
Management ®
Organizational Management ® Basic
Settings ® Maintain
Number Ranges ® Set Up
Number Assignment for All Plan Versions
|
Transaction
Code
|
O0NC
|
2.
On the Change View “No Assignment for
All Plan Versions””: Overview screen, make the following
entries:
Group
|
Sem.Abbr.
|
Value
|
Description
|
NUMRG
|
COMP
|
X
|
Number
assignment for all plan versions
|
4.2 Maintain Number Ranges
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 organizational object, that is,
Organizational Units, Jobs and Positions.
By defining a unique number range to each object type, you can easily
identify the type of object and it 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 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:
IMG Path
|
Personnel Management ® Organizational
Management ® Basic
Settings ® Maintain
Number Ranges ® Maintain
Number Ranges
|
Transaction Code
|
OONR
|
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 Internal Assignment
|
$$C
|
|
|
$$O
|
|
|
$$S
|
|
|
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.
7. The
following number ranges are delivered with this SAP Best Practices package. Enter the values below for the
corresponding Subgroup
$$$$.
Sub object
|
No.
|
From Number
|
To Number
|
Current Number
|
External
|
$$$$
|
EX
|
00000001
|
19999999
|
0
|
Select
|
$$$$
|
IN
|
20000000
|
29999999
|
0
|
|
$$C
|
EX
|
00000001
|
19999999
|
0
|
Select
|
$$C
|
IN
|
30000000
|
39999999
|
0
|
|
$$O
|
EX
|
00000001
|
19999999
|
0
|
Select
|
$$O
|
IN
|
20000000
|
29999999
|
0
|
|
$$S
|
EX
|
00000001
|
19999999
|
0
|
Select
|
$$S
|
IN
|
40000000
|
49999999
|
0
|
|
8. Choose
Save.
9. Repeat
this process, starting at step 5, until all of the remaining Subgroups ($$C,$$O,$$S)
have been assigned the corresponding number ranges.
4.3 Activate Inheritance of Account Assignment Features
Use
In this step, you can determine that account
assignment features (controlling area, company code, and business area) of
organizational units are to be inherited by subordinate positions.
Procedure
1. Access
the activity using one of the following navigation options:
IMG Path
|
Personnel
Management ®
Organizational Management ® Basic
Settings ® Activate
Inheritance of Account Assignment Features
|
Transaction Code
|
OOCINH
|
2. On
the Change
View “Inheritance of Contr. Area in Pos.”: Overview screen, make
the following entries:
Group
|
Semantic abbreviation
|
Value abbr.
|
Description
|
PP0M
|
INHS
|
X
|
Inheritance of Account Assignment. features
by positions
|
3. Choose
Save.
4.4 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.
Procedure
1. Access
the activity using one of the following navigation options:
IMG
Path
|
Personnel
Management ®
Organizational Management ® Transport ® Set Up
Transport Connection
|
Transaction
Code
|
O0CR
|
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.
Choose Save.
5 Integration Settings
This SAP Best Practices package is delivered with
integration activated between Personnel Administration (PA) and Organizational
Management (OM). Changes made to the OM objects that are relevant to
integration are not transferred to PA automatically.

In the standard system, the switch &PLOGI is set to X.
This SAP Best Practices package keeps this setting.
5.1.1 Set Up Integration with Personnel Administration
Use
This
SAP Best Practices package is delivered with integration activated between
Personnel Administration (PA) and Organization Management (OM). This ensures
that the contents of the OM solution are consistent with the configuration in
the PA solution. Changes made to the OM objects that are relevant to
integration are transferred to PA automatically.
Procedure
1. Access
the activity using one of the following navigation options:
IMG
Path
|
Personnel
Management ®
Organizational Management ®
Integration ® Integration
with Personnel Administration ® Set up
Integration with Personnel Administration (or SM30 à Maintain
Table T77S0)
|
Transaction
Code
|
SPRO
|
2.
On the Choose Activity
dialog box, double-click Basic Settings and enter the following values:
Group
|
Sem.Abbr.
|
Value
|
Description
|
PLOGI
|
EVCCC
|
02
|
Master
Data Action: Company Code change
|
PLOGI
|
EVCRE
|
X
|
Generate
event with entry T77INT (action designate)
|
PLOGI
|
EVEGC
|
02
|
Master
Data Action: Employee subgroup change
|
PLOGI
|
EVENB
|
|
Enhanced
integration (X=on, Space=off)
|
PLOGI
|
EVPAC
|
02
|
Master
Data Action: Country reassignment
|
PLOGI
|
ORGA
|
X
|
Integration
Switch: Organizational Assignment
|
PLOGI
|
PLOGI
|
01
|
Integration
plan version / Active Plan Version
|
PLOGI
|
PRELI
|
99999999
|
Integration:
default position
|
PLOGI
|
PRELU
|
|
Integration:
PA update online or batch
|
PLOGI
|
TEXTC
|
|
Integration:
transfer short text of job
|
PLOGI
|
TEXTO
|
|
Integration:
transfer short text of org.unit
|
PLOGI
|
TEXTS
|
|
Integration:
transfer short text of position
|
PPABT
|
PPABT
|
0
|
Switch:
department
|
PPINT
|
BTRTL
|
|
Default
value for personnel subarea
|
PPINT
|
PERSA
|
|
Default
value for personnel area
|
5.1.2 Feature PLOGI: Integration of Personnel Planning and Master Data
Use
This feature controls whether a person
participates in integration between personnel planning and master data. The standard setting for this feature sets
integration for all employee groups.
This needs to be modified for Retirees as they will not have default
values populate from a position.
Procedure
1. Access
the activity using one of the following navigation options:
IMG Path
|
Personnel Management ® Organizational
Management ® Integration
® Integration
with Personnel Management ® Set Up
Integration with Personnel Administration
|
Transaction Code
|
PE03
|
2. On
the Choose
Activity dialog box, double-click Participate in Integration.
3. On
the “Process
feature PLOGI: decision tree” screen, you will see the following
values:
D PERSG
2
&PLOGI=,
* &PLOGI=X,
5.1.3 Activate Feature: PLOGI
Use
Although SAP Best Practices package is
delivered with integration activated between Personnel Administration (PA) and
Organization Management (OM), the Feature PLOGI must be activated manually.
Procedure
4.
Access the activity using one of the following
navigation options:
IMG Path
|
Personnel Management ®
Organizational Management ®
Integration ®
Integration with Personnel Administration ® Set up
Integration with Personnel Administration (or PE03 à PLOGI)
|
Transaction Code
|
SPRO
|
5. On
the Choose
Activity dialog box, double-click Participate in Integration. The value set for PLOGI should
be an “X”.
6. If
the display is not in a Decision Tree format, click on PView à
Tree Maintenance.
7. Choose
Save.
8. Choose
Activate.
5.1.4 Set Up Integration with Cost Accounting/Distribution
Use
The
default controlling area has not been set in this SAP Best Practices package.
This is necessary if you create relationships between cost centers and
positions or organizational units, the system asks you to assign the cost center
to a controlling area. In such cases, the value you define in this step is used
as the default.
Procedure
1. Access
the activity using one of the following navigation options:
IMG
Path
|
Personnel
Management ®
Organizational Management ®
Integration ® Set up
Integration for Cost Accounting
|
Transaction
Code
|
O0CDIST
|
2.
On the Change View “Integration with
Cost Distribution”: Overview screen, make the following entries:
Group
|
Sem.Abbr.
|
Value
|
Description
|
PPINT
|
PPINT
|
1000
|
Default
value for controlling area
|
4.
Access the activity using one of the following
navigation options:
IMG Path
|
Personnel Management ®
Organizational Management ®
Integration ® Set up
Integration for Cost Distribution
|
Transaction Code
|
OOCDIST
|
5. On
the Change
View “Integration with Cost Distribution”: Overview screen, make
the following entries:
Group
|
Sem.Abbr.
|
Value
|
Description
|
PLOGI
|
COSTD
|
X
|
Integration of Cost Distribution
PersAdm/Org Management
|
6. Choose
Save.
6 Infotype Settings
6.1 Vacancy Infotype
Use
To
facilitate the integration to ‘Recruitment’ the following entries are delivered
with this SAP Best Practices package.
Procedure
1. Access
the activity using one of the following navigation options:
IMG
Path
|
Personnel
Management ®
Organizational Management ® Infotype
Settings ® Activate/Deactivate
“Vacancy” Infotype
|
Transaction
Code
|
OOVB
|
2. On
the Change
View “Vacancy Editing”: Overview screen, enter the following values:
Group
|
Sem.Abbr.
|
Value
|
Description
|
PPVAC
|
PPVAC
|
1
|
Switch
for defining a vacancy
|
PPVAC
|
PREF
|
|
‘X’
dialog for personnel officer
|
PPVAC
|
VACWF
|
|
Vacancy
workflow on = ‘X’, Vacancy
|
3. Choose
Save.
6.2 Working Time
6.2.1 Maintain Working Time Groups
Use
When the job is occupied, this working time is compared to
the working time agreed with the position holder. In this way, you can avoid
positions being more than 100% occupied. In this SAP Best Practices package the
following entries are delivered:
Procedure
1.
Access the activity using one of the following
navigation options:
IMG Path
|
Personnel
Management ®
Organizational Management ® Infotype
Settings ® Working
Time ® Maintain
Working Time Groups
|
Transaction Code
|
O0GP
|
2.
On the Change View “Employee
Group/Subgroup Assignment to Work Schedule Group screen, choose
the New
Entries button and make the following entries:
EEGrp
|
Emp.Group
|
ESgrp
|
Emp.Subgroup
|
W/S
|
Work Schedule
Group
|
1
|
Employee
|
Y0
|
Hourly Full Time
|
0002
|
Hourly Paid Employees
|
|
|
|
|
||
Y4
|
Hourly Part Time
|
0002
|
Hourly Paid
|
||
Y1
|
Salaried FT-Exempt
|
0001
|
Salaried Employees
|
||
Y8
|
Salaried PT-Exempt
|
0001
|
Salaried Employees
|
||
Y9
|
Salaried FT-Non Ex
|
0001
|
Salaried Employees
|
||
Y3
|
Executive
|
0001
|
Salaried Employees
|
||
|
|
|
|
||
4
|
Intern
|
Y1
|
Salaried FT-Exempt
|
0001
|
Salaried Employees
|
Y8
|
Salaried PT-Exempt
|
0001
|
Salaried Employees
|
||
Y9
|
Salaried FT-Non Ex
|
0001
|
Salaried Employees
|
||
7
|
Temp/Seasonal
|
Y0
|
Hourly Full Time
|
0002
|
Hourly Paid Employees
|
Y4
|
Hourly Part Time
|
0002
|
Hourly Paid Employees
|
||
8
|
Expatriate
|
Y1
|
Salaried FT-Exempt
|
0001
|
Salaried Employees
|
Y3
|
Executive
|
0001
|
Salaried Employees
|
||
YA
|
Non-Payroll w/Ben
|
0001
|
Salaried Employees
|
||
9
|
External
|
Y2
|
Contractor
|
0002
|
Hourly Paid Employees
|
YB
|
Service Provider
|
0002
|
Hourly Paid Employees
|
||
U
|
Inpatriate
|
Y1
|
Salaried FT-Exempt
|
0001
|
Salaried Employees
|
Y3
|
Executive
|
0001
|
Salaried Employees
|
6.2.2 Maintain Rule Values
Use
The working time values that are
determined by an overall rule value in infotype 1011 for an organizational unit
are used as the basis for the working time check. A working time check takes
place, if you fill a position with a person. The working time for the position
(from infotype 1011) is compared to the person's working time (from infotype
0007 of Personnel Administration). If these times differ, a warning appears.

This entry is an SAP
standard entry.
Procedure
1.
Access the activity
using one of the following navigation options:
IMG Path
|
Personnel Management ® Organizational
Management ®
Infotype Settings ®
Working Time ®
Maintain Rule Values
|
Transaction Code
|
O0RW
|
2.
On the Change View
“Work Schedule: Rule Values”: Overview screen, make the following
entries:
Group
|
Sem.Abbr.
|
Value
|
Description
|
WORKT
|
DAILY
|
800
|
Average working time per day
|
WORKT
|
DAYMT
|
2170
|
Average number of working days
per month
|
WORKT
|
DAYWK
|
500
|
Average number of working days
per week
|
WORKT
|
DAYYR
|
26000
|
Average number of working days
per year
|
WORKT
|
DECNO
|
2
|
Number of decimal places for
default working time
|
WORKT
|
FTEP
|
|
Calculation of values for FTE
|
WORKT
|
FTEQ
|
|
Quota planning in FTE’s
|
WORKT
|
MAXHR
|
2400
|
Maximum values for working
hours per day
|
WORKT
|
MINHR
|
100
|
Minimum values for working
hours per day
|
WORKT
|
PATHA
|
WRKT_AO
|
Evaluation path: work centre /
organizational unit
|
WORKT
|
PATHO
|
WRKT_O
|
Evaluation path: org.unit /
org.unit
|
WORKT
|
PATHS
|
WRKT_SO
|
Evaluation path: position /
organizational unit
|
WORKT
|
PERCK
|
M
|
Type of working hours check
|
3. Choose Save.
6.2.3 Set Up Check Values for Authorities/Resources
Use
The OM Infotype 1010 (Authorities/Resources) is divided into
two subtypes. Authorities are the authorities, which describe a position
regardless of the holder. Resources are assigned to work centers and positions,
which require particular technical features.
Procedure
1.
Access the activity using one of the following
navigation options:
IMG Path
|
Personnel
Management ®
Organizational Management ® Infotype
Settings ® Set up
Check Values for Authorities/Resources
|
Transaction Code
|
O0K0
|
2.
On the Change View “Authorities/Resources”:
Overview screen, make the following entries:

In addition to the standard model entries the following
have been created for this SAP Best Practices package.
Subtype
|
Subtype Text
|
Resources
|
Resource Name
|
0001
|
Authority/pwr of attorney
|
YK1
|
Purchases up to
$50,000
|
0002
|
Technical resources
|
YK2
|
Protective goggles
|
0002
|
Technical resources
|
YK3
|
Protective mask
|
0002
|
Technical resources
|
YK4
|
Protective Clothing
|
6.2.4 Set Up Check Values for Health Examinations
Use
The OM Infotype 1009 (Health Examinations) is divided into
two subtypes. Health Exclusions can be used to flag work centers that may not
be filled by persons with previous illnesses. Whereas, Health Examinations can
be used to flag work centers, which require examinations to be carried out at
regular intervals.
Procedure
1.
Access the activity using one of the following
navigation options:
IMG Path
|
Personnel
Management ®
Organizational Management ® Infotype
Settings ® Set Up
Check Values for Health Examinations
|
Transaction Code
|
O0GV
|
2.
On the Change View “Health Examinations”:
Overview screen, choose the New Entries button
and make the following entries:

In addition to the standard model entries the following
have been created for this SAP Best
Practices package:
Subtype
|
Subtype Text
|
Exam
Type
|
Health Examination
Name
|
Exam
Recurr.
|
Time Unit
|
0002
|
Health examinations
|
YK03
|
Preventive Medical
|
12
|
Months
|
0002
|
Health examinations
|
YK04
|
Lead Level Test
|
03
|
Months
|
0002
|
Health examinations
|
YK05
|
Audiometric Test
|
12
|
Months
|
6.2.5 Set Up Check Values for Restrictions
Use
The OM Infotype 1006 (Restrictions) can be used to flag work
centers that are unsuitable for particular groups of persons, due to the
working time or the type of activities involved.
Procedure
1.
Access the activity using one of the following
navigation options:
IMG Path
|
Personnel
Management ®
Organizational Management ® Infotype
Settings ® Set Up
Check Values for Restrictions
|
Transaction Code
|
SPRO
|
2.
On the Change View “Health Examinations”:
Overview screen, choose the New Entries button
and make the following entries:

In addition to the standard model entries the following
have been created for this SAP Best
Practices package:
Restriction
|
Restriction Name
|
YK01
|
Not suitable for Hearing impaired
|
YK02
|
Not suitable for Sight impaired
|
YK03
|
Not suitable for Pregnant Women
|
6.2.6 Set Up Check Values for Reasons
Use
Reasons are used in combination with the OM Infotype 1006
(Restrictions). These reasons can be combined with all the restriction in
infotype 1006. Infotype 1006 must be created first to allocate the reasons.
Procedure
1.
Access the activity using one of the following
navigation options:
IMG Path
|
Personnel
Management ®
Organizational Management ® Infotype
Settings ® Set Up Check Values for Reasons
|
Transaction Code
|
SPRO
|
2.
On the Change View “Health Examinations”:
Overview screen, choose the New Entries button
and make the following entries:

In addition to the standard model entries the following
have been created for this SAP Best
Practices package:
Reason
|
Reason Name
|
YK01
|
Harmful solvent fumes
|
YK02
|
Exposure to Lead
|
7 Organizational Structure

This
section describes and lists the Organizational Units that have been defined for
use with Public Sector. The actual
loading of these organizational objects is accomplished in the HCM Master Data
BPD (558).
Use
The
Organizational Structure forms the basis of the entire Personnel Planning and
Development application. An organizational unit represents a grouping of
employees (in the form of departments). This
SAP Best Practices package is delivered with 11 organizational units.
To
view the Organizational Units provided in the system, follow the SAP menu
path:
Menu
Path
|
Human Resources ® Organizational Management ® Info System ® Organizational Unit ® Organizational Structure ® Organizational Structure
|
Transaction
Code
|
S_AHR_61016493
|
Following
is the graphical representation of the Organizational Structure that is
presented:

Cost
Centers have been assigned to each of the organizational units above with
validity period January 1, 2007 through December 31, 9999. These cost centers are
delivered as part of the Baseline configuration. The cost center assignment
needs to be modified to correspond to the cost centers defined for your
organization. These organizational units are tied to Company Code 1000. As part
of the configuration to support cost center integration, the following table
entry is completed to provide the Cost Accounting default controlling area for
the company:
Group
|
Semi Abbr.
|
Value
|
Description
|
PPINT
|
PPINT
|
1000
|
Default
value for controlling area
|

Company
Code and Controlling Area ‘1000’ are delivered with the SAP Best Practices
Baseline for Global. If you have chosen not to install the baseline
configuration, then this value should be modified to the controlling area used
in your organization
8 Jobs

This section describes and lists the Jobs that have been
defined for use with Public Sector. The
actual loading of these organizational objects is accomplished in the HCM
Master Data BPD (558).
A Job is used to classify information basic to the human
resource planning process. It identifies the relevant duties/tasks, skills, and
requirements of each job within an Organization. This SAP Best Practices package is delivered with approximately 30
jobs. These may either be used as is, changed by the customer for production,
or simply provide guidelines as to how to organize and create jobs in SAP.
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
package, follow the SAP menu path:
SAP Path
|
Human
Resources ®
Organizational Management ® Info
System ® Job ® Existing
Jobs
|
Transaction Code
|
S_AHR_61016497
|
Following is a sampling of the jobs (C objects) that are
provided in this SAP Best Practices
package Org. structure:
Object ID
|
Name
|
Validity period
|
10002000
|
Executive (Headquarters)
|
01/01/1900 - 12/31/9999
|
10002001
|
Accountant
|
01/01/1900 - 12/31/9999
|
10002002
|
Administrative
|
01/01/1900 - 12/31/9999
|
10002003
|
Supervisor
|
01/01/1900 - 12/31/9999
|
10002004
|
Manager
|
01/01/1900 - 12/31/9999
|
10002005
|
Chief Executive Officer
|
01/01/1900 - 12/31/9999
|
10002006
|
Chief Financial Officer
|
01/01/1900 - 12/31/9999
|
10002007
|
Customer Service Representative
|
01/01/1900 - 12/31/9999
|
10002008
|
HR Generalist (Headquarters)
|
01/01/1900 - 12/31/9999
|
10002009
|
Sales (East)
|
01/01/1900 - 12/31/9999
|
10002010
|
Director
|
01/01/1900 - 12/31/9999
|
10002011
|
Financial Analyst
|
01/01/1900 - 12/31/9999
|
10002012
|
Business Analyst
|
01/01/1900 - 12/31/9999
|
10002013
|
Line Foreman Product ‘A’
|
01/01/1900 - 12/31/9999
|
10002014
|
Assembly Worker Product ‘A’
|
01/01/1900 - 12/31/9999
|
10002015
|
IT-Technical
|
01/01/1900 - 12/31/9999
|
10002016
|
Programmer I
|
01/01/1900 - 12/31/9999
|
10002017
|
Programmer II
|
01/01/1900 - 12/31/9999
|
10002018
|
Clerk
|
01/01/1900 - 12/31/9999
|
10002019
|
Forklift Driver
|
01/01/1900 - 12/31/9999
|
10002020
|
Quality Assurance Analyst
|
01/01/1900 - 12/31/9999
|
10002021
|
Controller
|
01/01/1900 - 12/31/9999
|
10002022
|
Training Coordinator
|
01/01/1900 - 12/31/9999
|
10002023
|
Maintenance
|
01/01/1900 - 12/31/9999
|
10002024
|
Transportation Product ‘A’
|
01/01/1900 - 12/31/9999
|
10002025
|
Marketing
|
01/01/1900 - 12/31/9999
|
10002026
|
Communications
|
01/01/1900 - 12/31/9999
|
10002027
|
Chief Information Officer
|
01/01/1900 - 12/31/9999
|
10002028
|
Janitorial
|
01/01/1900 - 12/31/9999
|
10002029
|
Course Instructor
|
01/01/1900 - 12/31/9999
|
10002030
|
Assembly Worker Product ‘B’
|
01/01/1900 - 12/31/9999
|
10002031
|
HR Generalist (East)
|
01/01/1900 - 12/31/9999
|
10002032
|
HR Generalist (West)
|
01/01/1900 - 12/31/9999
|
10002033
|
HR Generalist (Central)
|
01/01/1900 - 12/31/9999
|
10002034
|
Sales (West)
|
01/01/1900 - 12/31/9999
|
10002035
|
Sales (Central)
|
01/01/1900 - 12/31/9999
|
10002036
|
Transportation Product 'B'
|
01/01/1900 - 12/31/9999
|
10002037
|
Line Foreman Product 'B'
|
01/01/1900 - 12/31/9999
|
10002038
|
Vice President
|
01/01/1900 - 12/31/9999
|
10002039
|
Executive (East)
|
01/01/1900 - 12/31/9999
|
10002040
|
Executive (West)
|
01/01/1900 - 12/31/9999
|
In addition to the object definition and relationships to
positions, jobs in this
SAP Best Practices package are also delivered with additional
information attached. By creating infotype 1610 EEO/AAP category, the EEO, AAP,
and FLSA designations for each job are stored. This information is associated
with any employees assigned to a position that is related to the job. In this
way, EEO and AAP reports may be run, and overtime calculations may be made
based on FLSA status. The FLSA status indicator is reflected on the employee’s
Organizational Assignment infotype 0001.
Worker’s Compensation information can also
be maintained via IT1641. This infotype can be viewed via the standard
transaction PO03 and selecting the object titled WC Attributes for JOB.
The Planned Compensation infotype (1005) has
also been defined for salaried (exempt and non-exempt) jobs this includes the
pay grade type, area, grade, and level. If integration is activated this
information defaults in personnel administration, Basic Pay (IT0008)

The use of the country specific infotypes is
typically handled via Expert Mode maintenance. To access these infotypes, choose
the menu path Settings ’ Country-specific
infotypes from the Expert Mode main screen. At the dialog box, enter the
appropriate country code for the country, and change the radio button to select
“For the following countries”. Upon
returning to the main processing screen, the additional infotypes appear.
9 Positions

This section describes and lists the Organizational
Units, Jobs and Positions that have been defined for use with Public
Sector. The actual loading of these
organizational objects is accomplished in the HCM Master Data BPD (558).
A Position is an organizational grouping of activities that
can be performed by a person. This SAP
Best Practices package is delivered with over 20 positions available for
use and linked to a Job Classification.
To view the positions provided in the system, follow the SAP
menu path:
SAP Path
|
Human
Resources ®
Organizational Management ® Info
System ® Position ® Existing
Positions
|
Transaction Code
|
S_AHR_61016502
|
Following is a sampling of the positions (S objects) that
are provided in this SAP Best
Practices package Org. structure:
Object ID
|
Name
|
Validity period
|
10003000
|
Sales
|
01/01/1900 - 12/31/9999
|
10003001
|
Vice President – Human Resources
|
01/01/1900 - 12/31/9999
|
10003002
|
Vice President – Marketing
|
01/01/1900 - 12/31/9999
|
10003003
|
Sales
|
01/01/1900 - 12/31/9999
|
10003004
|
Sales
|
01/01/1900 - 12/31/9999
|
10003005
|
Manager -_Finance
|
01/01/1900 - 12/31/9999
|
10003006
|
Manager – Manufacturing
|
01/01/1900 - 12/31/9999
|
10003007
|
Manager – R&D
|
01/01/1900 - 12/31/9999
|
10003008
|
Maintenance Supervisor
|
01/01/1900 - 12/31/9999
|
10003009
|
Director - HR
|
01/01/1900 - 12/31/9999
|
10003010
|
Janitorial
|
01/01/1900 - 12/31/9999
|
10003011
|
Manager - Marketing
|
01/01/1900 - 12/31/9999
|
10003012
|
Director – Regional Sales
|
01/01/1900 - 12/31/9999
|
10003013
|
Sales Manager
|
01/01/1900 - 12/31/9999
|
10003014
|
HR Analyst
|
01/01/1900 - 12/31/9999
|
10003015
|
Financial Analyst
|
01/01/1900 - 12/31/9999
|
10003016
|
Line Foreman
|
01/01/1900 - 12/31/9999
|
10003017
|
HR Generalist
|
01/01/1900 - 12/31/9999
|
10003018
|
Business Analyst
|
01/01/1900 - 12/31/9999
|
10003019
|
Plant Maintenance
|
01/01/1900 - 12/31/9999
|
10003020
|
Machinist
|
01/01/1900 - 12/31/9999
|
10003021
|
Customer Service
|
01/01/1900 - 12/31/9999
|
10003022
|
Course Instructor
|
01/01/1900 - 12/31/9999
|
10003023
|
Customer Service
|
01/01/1900 - 12/31/9999
|
10003024
|
Customer Service
|
01/01/1900 - 12/31/9999
|
10003025
|
Sales QA Analyst
|
01/01/1900 - 12/31/9999
|
10003026
|
Manufacturing QA Analyst
|
01/01/1900 - 12/31/9999
|
10003027
|
Operations QA Analyst
|
01/01/1900 - 12/31/9999
|
10002028
|
Assembly Worker
|
01/01/1900 - 12/31/9999
|
10002029
|
IT Manager
|
01/01/1900 - 12/31/9999
|
10002030
|
Operations Manager
|
01/01/1900 - 12/31/9999
|
All of the positions in this SAP Best Practices package are delivered with infotype
settings that provide default assignment to an Employee Group and Subgroup combination
via infotype 1013. Thus, when a Person is assigned to a Position, the system
automatically determines the default Employee Group and Subgroup values in
infotypes 0000 (Actions) and 0001 (Organizational Assignment). Before adding
new Positions to the system, be aware of the effect of Employee Group/Subgroup
settings that result when Employees are assigned to a Position.
In addition, all positions are delivered with infotype
settings that provide default assignment to a Company Code, Personnel Area, and
Personnel Subarea combination via infotype 1008. These values also default in
infotypes 0000 (Actions) and 0001 (Organizational Assignment) when the position
is selected.
To facilitate position control in Organizational Management,
Positions are also assigned Vacancies, via Infotype 1007. Each time a Person is
assigned to a position, an existing Vacancy record is delimited. Extensive
reporting capabilities in Recruitment and Personnel Development are available
in the system as a result of the management of position vacancies or your human
resources inventory.
10 Create Personnel Actions
Use
These Personnel Actions are different from those within the
Personnel Administration guides. Although these are titled as Personnel
Actions, they are the actions used to create organizational objects. These actions are a collection of
several logically connected infotypes in the system, which, in an exact
sequence, is used for processing and is used for a particular system activity
(see "Create Organizational Unit", for example).
Procedure
1.
Access the activity using one of the following
navigation options:
IMG Path
|
Personnel
Management ® Personnel Development ® Basic
Settings à Maintain Personnel Actions
|
Transaction Code
|
SPRO
|
2.
On the Change View “Actions (Overview)”:
Overview screen, select the Specific Object Type and choose Action
(Individual Maintenance).
3.
Maintain the following entries. The table below
illustrates the actions for creating Organizational Units, Jobs and Positions.
Action
|
Action
Text |
Seq#
|
Plan Version
|
Obj. Type
|
Infotype
|
Subtype
|
Plan Status
|
Var. Field
|
Func. Code
|
FC Scr Var
|
YO
|
Create organizational unit
|
1
|
**
|
O
|
1000
|
|
|
|
INSE
|
MASS
|
YO
|
Create organizational unit
|
20
|
**
|
O
|
1002
|
0001
|
|
|
INSE
|
MASS
|
YO
|
Create organizational unit
|
40
|
**
|
O
|
1001
|
A011
|
|
K
|
INSE
|
|
YO
|
Create organizational unit
|
45
|
**
|
O
|
1612
|
|
|
|
INSE
|
|
YC
|
Create job
|
1
|
**
|
C
|
1000
|
|
|
|
INSE
|
MASS
|
YC
|
Create job
|
20
|
**
|
C
|
1005
|
|
|
|
INSE
|
|
YC
|
Create job
|
25
|
**
|
C
|
1610
|
|
|
|
INSE
|
|
YS
|
Create position
|
1
|
**
|
S
|
1000
|
|
|
|
INSE
|
MASS
|
YS
|
Create position
|
10
|
**
|
S
|
1002
|
0001
|
|
|
INSE
|
MASS
|
YS
|
Create position
|
30
|
**
|
S
|
1001
|
B007
|
|
C
|
INSE
|
|
YS
|
Create position
|
40
|
**
|
S
|
1008
|
|
|
|
INSE
|
MASS
|
YS
|
Create position
|
50
|
**
|
S
|
1013
|
|
|
|
INSE
|
MASS
|
4.
Choose Save.