S.P.O.C.K – These are the most important objects in OM
S – Position
P – Person
O – Organizational Unit
C – Job
K – Cost Center
Organizational units can any type of organizational entity. Eg. programs, regions, districts, divisions, departments, teams, etc. Seperate Organizational units are needed when:
- Reporting for each is required seperately
- Units can have Managers/Leaders
- Units that have distinct tasks/activities
Jobs are general classification of tasks that are preformed together. Eg. Human Resources Director, Administrative Specialist, Equipment Operator, etc.
Positions are organization specific. A number of positions can be based on the same job. As a general rule, each position represents only one employee.
Persons hold positions – more information on persons are stored in PA (Personnel Administration)
Position belongs to org unit <-> org unit incorporates position
Job describes a position <-> position is described by a job
A postion reports to another position <-> A position is the line supervisor of another position
A person is the holder of a position <-> Position is assigned to a person as a holder
– Each object can have a number of attributes. These attributes are stored in infotypes. These attributes are inherited based on the relationships. Eg. If a job has a salary range, the position related to it inherits it and thus the person that holds that position. Org Units and postions will inherit cost center of the parent org units. Positions can inherit tasks of the jobs that describe them (and can also have tasks directly assigned to them). The important attributes of the OM objects are listed below.
- Org Unit – Org title, description, address, head of Org Unit, cost center, account assignment features
- Position – Position title, description, Vacancy, Address, Work Schedule, Cost Distribution, Worker’s Comp codes, Account assignement features, Cost Center override
- Job – Class title, Description, Salary band/Scale, FLSA Status, EEO/AAP codes