IMG–> PA–> OM–> Basic settings –> integration–>set up integration with PA

Table T77S0 is the major table for OM – PA integration
Set the integration switch PLOGI ORGA to X

Users often get confused about the way in which Personnel Administration is linked to Organization Management. There is no ‘link’ as one would imagine. When the integration is switched on any new position created in Organization Management is created in the database HRP1000 – where all the objects are created. In addition, the position is copied into table T528B which is used by Personnel Administration. When an employee is assigned a position, the system does a check to see whether the position ID exists within table T525B.

The integration switches are held in table T77S0. The key entry is “plogi orga” entry. If this is set to “X” then the integration is turned “on”. If there is a blank entry in this field, then integration is turned “off”. Don’t take for granted that your integration will always be spot on. Check different aspects of the integration in terms of the data synchronisation between PA and OM with the integration programs outlined below.

Reports in relation to PA – OM

RHINTE00 is used to transfer data from PA to OM
RHINTE10 is to transfer OM data to PA tables
RHINTE20 is to determine whether the data relevant for integration is available in PA and OM
RHINTE30 is to update IT0001 (org assignment) for the person you have selected
Overview

It is important to realize that in PA, there are tables that contain objects from OM, i.e. for those items displayed on infotype 0001 Organizational Assignment. Sometimes the tables can get ‘out of step’ with those in PD – table HRP1000.

The tables are:

T513, T513S Object type C (Job)

T528B, T528T Object types S (Position) and A (Work center)

T527X Object type O (Organizational unit)

RHINTE00
This loops through all employees in PA by looking at positions on infotype 0001. It checks thecorresponding person to position relationship exists in PD (A008). If not it is created.

This program transfers the PD objects from Personnel Administration to Organization Management. The system creates a batch input session (SM35) which you have to execute for the changes to be effective.

RHINTE10
Generally, the program RHINTE20 will be used instead of this one. This program loops through the PD table HRP1000. For each job, position, cost centre and organization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update cost centers also. The main difference with this program as opposed to RHINTE20 is that this one has the option to delete items from the PA tables, which no longer exist in PD.

This program is generally run if you have created any objects in Organization Management, before integration has been turned on. If you turn on integration before you create any objects, then you should not have to run this report. This report copies the objects into the Personnel Administration tables for jobs (T513, T513S), positions (T528B, T528T), org units (T527X) etc.

RHINTE20
This program loops through the PD table HRP1000. For each job, position, work centre andorganization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update work centers also.

This program is run to check the consistency between the objects in Personnel Administration and Organization Management. If any inconsistencies are found, you are able to correct these by double-clicking on a particular object type.

RHINTE30
This program updates Personnel Administration with any new data that has been entered in Organization Management. It creates a batch input session for the employees selected. Leave the selection blank to choose all available employees. Take the tick off the checkbox “Open Personnel Numbers Only”. If this check-box is on, the system looks in table RHINTE30 to see whether the employee exists in this table. If they do, then they will be processed.