Organizational Unit

Represents a functional unit in the enterprise, for example, the marketing department. Depending on how the task structure is organized in an enterprise, this can be a department, a group, or a project team, for example.

Other enterprise units such as personnel areas, company codes, business areas, and so on are to be differentiated from organizational units. They are defined and used in the relevant components to represent structures, for example, Personnel Administration or Accounting.

From a technical and business perspective, the organizational unit of the component Personnel & Organization corresponds to the organizational unit of the component Organizational Management.

You use organizational units to represent the functional units of your enterprise. By assigning organizational units to each other in a hierarchy, you create an organizational structure. You can define properties for each organizational unit. You use organizational units and the organizational structure for the following purposes, for example:

You use the organizational structure that results from the organizational units to obtain an overview of the current functional distribution of tasks and hierarchy (for example, departments, reporting paths) in your organization.
By assigning positions to organizational units, you describe your personnel resource requirements for each area of your organization.
With the organizational structure, you can use organizational criteria to search for employee master data.
You can control business processes along the functional hierarchy described using organizational units.
You can use organizational units and organizational structures in the Business Workflow to determine the agent.

Processing

For information about processing organizational units, see Processes and Organizational Data (Infotypes).

Structure

Basic Data

The system stores the properties of the organizational units in the infotypes of the component Organizational Management. The basic data (and thereby the existence of an object) is determined by a corresponding entry in the infotype Object (1000):

Object type/data storage
From a technical perspective, organizational units are represented in the system as instances of the object type O.
Object ID
An object of the type organizational unit is uniquely identified using an object ID in the infotype Object (1000). The assignment of all other object properties is made using this object ID. When an object is created, it receives this ID that cannot be changed. In Customizing, you can determine which number range intervals are to be available and whether the number assignment is to be made automatically by the system or through a user decision.
Validity period
When an object is created, it receives a validity period in addition to the object ID. The system also uses the infotype Object (1000) to represent the validity period. Since it possible for more than one infotype record to exist for an object (due to changes to the object name), the system automatically ensures that there is always a chain of records for this infotype that is without time gaps. The start date of the first infotype record of an object and the end of the last infotype record determine the entire validity of the object. The validity period of an object also determines which validity period all other properties of the object that are stored in infotype records may have. These properties must be within the object validity.

The validity period of the object can be changed according to certain rules.

Short Profile

By default, the short profile of an organizational unit displays the following data and key figures for the specified date:

Field	Description	Data source/method
<Without Field Label>	Long description of the organizational unit	Infotype Object (1000), see also Name and Description (Infotype 1000 and 1002)
ID	Unique ID of organizational unit
Valid From/To	Validity period of the organizational unit (start date of the first infotype record, end date of the last infotype record)
Managed By	Employee who staffs the position that is assigned to the organizational unit as the managing position (if no employee is assigned to the managing position, the system does not display any value)	Infotype Relationships (1001), relationship 012 (assigned managing position) and relationship 008 (assigned employee), see also Relationships (Infotype 1001)
Reports To	Direct higher-level organizational unit	Infotype Relationships (1001), relationship 002, see also Relationships (Infotype 1001)
Master Cost Center	Assigned master cost center	Infotype Relationships (1001), relationship 011, see also Master Cost Center
No. of Employees	Calculated key figure: Number of employees that are directly assigned to the positions of the organizational unit	Infotype Relationships (1001), relationship 003 (assigned positions) and relationship 003 (assigned employees), see also Relationships (Infotype 1001) The system uses the class CL_HRBAS_OM_KEYFIGURES (method GET_NUM_EMPL_OF_ORG) to determine this key figure.
FTE	Calculated key figure: Number of full-time equivalents (FTE) in positions that are staffed by directly assigned employees	Summation of the employment percentages of employees that are stored in the infotype Planned Working Time (0007). The system uses the class CL_HRBAS_OM_KEYFIGURES (method GET_FTE_EMPL_PERC_OF_ORG) to determine this key figure. Note Alternatively, you can also use the summation of the capacity utilization levels that are stored in the infotype Basic Pay (0008 ) to determine this key figure (method GET_FTE_CAP_UTIL_OF_ORG). You make this change in Customizing for the short profile. End of the note.
Directly subordinate positions.	Calculated key figure: Number of positions assigned to the organizational unit directly	Infotype Relationships (1001), relationship 003, see also Relationships (Infotype 1001) The system uses the class CL_HRBAS_OM_KEYFIGURES (method GET_NUM_POS_OF_ORG) to determine this key figure.
Vacant Positions	Calculated key figure: Number of vacant positions assigned to the organizational unit directly	Infotype Vacancy (1007) and infotype Obsolete (1014) of the assigned positions; see also Staffing Status (Infotypes 1007 and 1014) The system uses the class CL_HRBAS_OM_KEYFIGURES (methods GET_NUM_POS_VACANT_OF_ORG and GET_NUM_POS_OBSOLETE_OF_ORG) to determine these key figures.
Obsolete Positions	Calculated key figure: Number of obsolete positions assigned to the organizational unit directly

Note Note

Note that the key figures do not have their own authorization check. The user sees the calculate key figures even if he or she does not have authorization for the underlying infotypes.

End of the note.

For more information about configuring the short profile, see Customizing for the component Personnel & Organization and choose Start of the navigation path Master Data Application Next navigation step Object Profile Page Short Profiles End of the navigation path .

Other Object Characteristics

Organizational units can also have characteristics in the following data areas: