SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 1

PA OM Integration

Applies to:

Enter SAP technology or product release (release number, SP, etc.) to which this article or code sample applies. For more information, visit the Enterprise Resource Planning homepage.

Summary

Personnel Administration (PA) and Organizational Management (OM) module form the base for entire SAP HR system. All other sub-modules in SAP HR are dependant / integrated with both PA and OM.

In PA we maintain all personnel related data in what is called as Infotypes (Information Types).

Organization Management module is used to capture and maintain the organization structure. And it uses various SAP system objects like Organization Unit (O), Position (S), and Job (C).

We need to have both PA and OM in place before we can implement any other SAP HR sub module. SAP is integrated ERP system where all cross functional module are integrated with each other as well as all sub-modules within a function are also integrated with each other.

The objective of this white paper is to use explain how exactly does the integration between PA and OM module work in SAP HR. The target audience would be end users and SAP consultants.

Author: Vishal Dusad

Company: Deloitte Consulting LLP

Created on: 3 November 2010

Author Bio

Vishal has been in the field of SAP HR consulting for over 8 years now. He has worked on both global as well as domestic India implementations. The areas that he had handled include Personnel Administration, Organizational Management, Concurrent Employment, Management of Global Employees, ESS, MSS, Benefits, Training and Event Management. In addition to this he has also done support for Payroll and Time modules.

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 2

Table of Contents

Basic Concept ..................................................................................................................................................... 3

Example: Organization Management .............................................................................................................. 3

Example: Personnel Administration ................................................................................................................ 6

How does PA-OM Integration work? .................................................................................................................. 8

Standard SAP Reports for PA-OM Integration ................................................................................................. 10

Related Content ................................................................................................................................................ 11

Disclaimer and Liability Notice .......................................................................................................................... 12

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 3

Basic Concept

In the SAP system the integration is controlled using switches. All the integration switches are stored in table T77S0. PA OM integration is defined by PLOGI ORGA in this table.

If the value of PLOGI-ORGA is set to X that means integration is switched ON between PA and OM module. There are other switches as well for PLOGI group, but for time being we will only focus on this one.

Example: Organization Management

Let us look at how Organizational Management data is stored in the SAP HR system. We will consider only Organization Unit (O), Position (S) and Job (C). See a sample Organizational Structure in SAP below (Fig 1.1) (Transaction Code PPOM_OLD).

Fig 1.1

Each object has a unique object ID, start date, end date, short text and description.

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 4

All this data is stored in HRP1000 table. See below HRP1000 table screen (Fig 1.2).

Fig 1.2

All Organizational Unit, Position and Job objects created in Organizational Management are also stored in Personnel Administration in tables T527X, T528B and T513S respectively.

As you can see in the organizational structure, all objects are related to each other. All relationship data is stored in HRP1001 table. There are standard SAP pre-define relationships available in the system. Customers can create additional relationship as required in the system.

Following are few examples of available relationships.

Org Unit Belongs To (A003) Org Unit

Position Reports To (A002) Position

Job Describes (A007) Position

In the SAP system, there are two types to relationships i.e. Top Down (A***) and Bottom Up (B***).

User created only one of the two relationships, and the system created the other relationship (reverse relationship) automatically. So each of the above examples, we will have the following as well.

Org Unit Incorporate (B003) Org Unit

Position Is Line Supervisor Of (B002) Position

Position Is Described By (B007) Job

The following screen (Fig 1.3) shows how the relationship data is stored in HRP1001 table.

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 5

Fig 1.3

In the above screen (Fig 1.3),

Org Unit 1000076 Reports To (A002) Org Unit 1000075

Org Unit 1000076 Incorporates (B0003) Position 3000026, 3000027, 3000034, 3000035, 3000036 and 3000037.

Position 3000035 Reports To (A002) Position 3000026

Position 3000035 Belongs To (A003) Org Unit 1000076

Position 3000035 Is Described By (B007) Job 50012673

Now let us see reverse relationship for each of the above is stored in the system.

In the screen (Fig 1.4) below we see Org Unit 1000075 Is Line Supervisor of (B002) Org Unit 1000076

Fig 1.4

In the following screen (Fig 1.5) we see Position 3000026, 3000027, 3000034, 3000035, 3000036 and 3000037 Belong To (A003) Org Unit 1000076.

Fig 1.5

In the following screen (Fig 1.6) we see Position 3000026 Is Line Supervisor Of (B002) Position 3000035

Fig 1.6

In the following screen (Fig 1.7) we see Org Unit 1000076 Incorporates (B003) Position 3000035

Fig 1.7

In the following screen (Fig 1.8) we see Job 50012673 Describes (A007) Position 3000035

Fig 1.8

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 6

Example: Personnel Administration

We will hire one employee in Personnel Administration Module now using transaction PA40. We will use position 3000035 Assistant. Refer Fig 1.9

Fig 1.9

When performing hiring action in the system, we select/enter position ID on infotype 0000-Action screen. See the screen above. Once Infotype 0000 screen is saved, we get Infotype 0001-Organizational Assignment screen (Fig 1.10).

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 7

Fig 1.10

As we can see, in this screen Job Key and Organizational Unit are already populated. This is exactly what PA-OM Integration does. Let me explain how this happens in the next section.

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 8

How does PA-OM Integration work?

Based on the position selected on infotype 0000 screen, the system finds out which Organizational unit does the position belong to and what is Job that describes this position. Both these values are fetched and populated on IT0001 screen.

In case we do not have the relationships maintained appropriately in the Organizational Management side, we will not get these fields pre-populated.

Infotype 0001-Organizational Assignment is stored in table PA0001. See following screen (Fig 1.11) for PA0001 table.

Fig 1.11

Here we can see Organization Unit (ORGEH), Position (PLANS) and Job (STELL) being captured for employee number 33.

Employee number 33 is also visible in the Organizational structure now. Refer Fig 1.12

Fig 1.12

Position to Person and Person to Position relationships are created in HRP1001.

In the following screen (Fig 1.13) we see Person 33 is Holder (A008) of position 3000035

Fig 1.13

In the following screen (Fig 1.14) we see position 3000035 is Holder (B008) of person 33

Fig 1.14

SAP system uses position 99999999 as default integration position. In cases where user does not know the position on which employee needs to be hired, we use default integration position 9999999.

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 9

When we terminate the employee in SAP system i.e. the action which makes the employment status = 0 (Withdrawn) in infotype 0000 (Fig 1.15), the position assignment of the employee in infotype 0001 get changed to Integration Default Position-99999999. Note that at this point in time the Organizational Unit and Job stored against the employee in infotype 0001 remain unchanged. Refer to Fig 1.16 below.

Let us terminate above employee 33 and see this in SAP system.

Fig 1.15

Fig 1.16

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 10

Standard SAP Reports for PA-OM Integration

Following standard SAP reports are available for PA-OM integration.

RHINTECHECK This check report checks objects involved in integration for inconsistencies, in other words it looks for differences in the data status between PA and OM tables.

RHINTE10 - This report allows you to create object types in Personnel Administration (HR-PA) which have already been set up in Organizational Management (HR-OM) and which are needed for integration.

RHINTE20 - This report can be used to check whether the relevant object types for integration have been created in both Personnel Administration (HR-PA) and Organizational Management (HR-OM).Objects that are missing either in PA or OM can be created immediately.

RHINTE30 - This report creates a batch input session for specified personnel numbers. The session updates infotype 0001 "Organizational Assignment" (PA) for the persons concerned.

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 11

Related Content

SAP ERP Human Capital Management - Solution Overview

Personnel Administration (PA-PA)

For more information, visit the Enterprise Resource Planning homepage

PA OM Integration

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2010 SAP AG 12

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.