Documente Academic
Documente Profesional
Documente Cultură
And
HCM Structures
2
Table of contents
ORGANIZATIONAL MANAGEMENT.................................................................................................3
Organizational Management
Introduction to Organizational Management
Organizational Management is the component that will provide you the basic mechanism to depict
your organization in SAP systems. The organization from an HR perspective is created and
managed, allowing organizational group differentiation to be represented in the other HR
processes. All organizational units form the basis of the structure, whether it’s a company,
division, function, department, or work unit. The level of detail or granularity is completely up to
you to define, so the system is very flexible. Jobs and positions are defined to represent the
various types of roles that exist within those organizations.
Through organizational hierarchies, we define employee relationships, then store and administer
employee data in the system. Every employee is included in the structure of the enterprise. Data
entry is restricted while the validity of all employee data is checked. The enterprise is subdivided
into organizational structures, based on an organizational plan, and administrative structures,
based on the enterprise.
An organizational plan provides you with a complete model of the structural and personnel
environment of your enterprise. The highest organizational unit in an organizational structure is
the root organizational unit. Hierarchies and report structures are clearly laid out. You assign
employees in info type 0001, Organizational Assignment. In doing this, you include employees
in the enterprise, personnel and organizational structure.
4
In the SAP System, the company’s structure is defined by the Enterprise Structure and the
Personnel Structure. When used together, these structures defined the legal entities of the
company, work locations for the company, and the Company’s various employee groups.
Because the enterprise and personnel structures help the company differentiates between the
various types of employee and work locations, the structures values are used extensively in
payroll, time and benefit processing rules.
The enterprise and personnel structures are also used extensively by the financial components of
SAP. For instance, the structure values are used in rules to appropriately posts payroll expenses
to the correct GL accounts. Additionally, the tracking of recurring base budgets by staff group
relies heavily on Enterprise and Personnel structure values. Enterprise and Personnel structures
are stored on positions. When positions are created by the HR compensation Analyst, the
appropriate structure values will be selected and stored for the position.
As employees are assigned to positions, the employee will inherit the structure values stored on
the position. If the values are not appropriate for the assignment, the values may be changed on
the employee assignment screen (Infotype 0001, Organizational Assignment). Especially with
concurrent employment, the enterprise and personnel structure values will require careful over
sight.
5
Although an organizational plan can consist of many object types, the five basic
object types are the building blocks.
Persons are the holders of a position Positions are defined and assigned to organizational
units and cost centers.
• Shift Planning
• Personnel Cost Planning
• Career and Succession Planning
8.1 RHINTE00
Transfer PA Records To PD Positions. In another world, it creates the HRP1001 between P to S
in the OM side of the world. When you view a record via IT0001, you see this person holds the
position, however via HRP1001, that relationship isn’t so.
8.2 RHINTE10
Generates the required relevant tables. (T513 - Jobs, T513S - Jobs, T528B - Positions, T528T
Work Center, T527X - Org Unit.
8.3 RHINTE20
Checks for all objects for integration between PA and OM. This is a big one and will take awhile
to run. What it does is look at table T513/T513T - Jobs, T528/T528T - Position, and T528X - Org
Unit. It will then compare it against the HRPxxxx table to find missing objects. If there are any
missing objects, it will create the record.
8.4 RHINTE30
Transfer OM to PA. This will create infotype 0001. If the conversion strategy is to have SAP
auto inherit factor to kick in for IT0001, often time jobs and org unit are missing via IT0001
during the initial conversion load. RHINTE30 will find the relationship and push it through
IT0001.
• Personnel Administration
• Recruitment
• Personnel Development
• Compensation Management
• Controlling
• Shift Planning
If integration is active a and a person is assigned to a position in HR Master Data, the objects
8
related with the position in H R M aster Data are written to the Organizational Assignment info
type. If integration is active, the Organizational Unit, Job, and Cost Center fields are not ready
for input. Instead, they are filled from Organizational Management o only. In addition, every
organizational change is stored in both the Organizational Assignment info type in HR Master
Data and in the Organizational plan in Organizational Management. This means If a change is
made in Organizational Management that affects the organizational assignment of a person, the
change is written to the person’s Organizational Assignment info type. Similarly, a change made
to a person’s organizational assignment (for example, as a result of a personnel action) in HR
Master Data is written to Organizational Management.
The recruitment process starts from a vacancy. Vacancies are positions which need to be filled
by persons. These positions can be created in Organizational Management component and if
integration between organizational Management component and Recruitment is active, the
vacant position can be triggered in recruitment. The applicant data can be transferred from
recruitment to personnel administration component.