Each program is explained in detail so you can decide which ones you need to run. To set up/fix full integration between PA and PD, they should be run in this sequence:
1. RHINTE00 – Transfer PA records into PD positions –batch
2. RHINTE20 – Create OM objects in PA tables – Online
3. RHINTE30 – Bulk update of infotype 0001
4. RHINTECHECK – Program to check PA to PD
5. RHCHECKV - Checks all inverse relationships
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 the
corresponding person to position relationship exists in PD (A008), if not it is created.
RHINTE10
Generally, the program RHINTE20 will be used instead of this one. This program loops through the PD table HRP1000. For each job, position, work 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 work 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.
RHINTE20
This program loops through the PD table HRP1000. For each job, position, work 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 work centers also. An example output will show:
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 the
corresponding person to position relationship exists in PD (A008), if not it is created.
RHINTE10
Generally, the program RHINTE20 will be used instead of this one. This program loops through the PD table HRP1000. For each job, position, work 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 work 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.
RHINTE20
This program loops through the PD table HRP1000. For each job, position, work 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 work centers also. An example output will show:
Expand the tree items to display a list of objects that can be created:
RHINTECHECK
When the above programs have been run, use this check program, which looks through all employees and reports any inconsistencies found between PA and PD.
Tick each item that you wish to be created, or click on the text
and click ‘select subtree’ to select them all then click to perform multiple updates. This program can prove to be ‘problematic’. If difficulties arise with it, try using RHINTE10 instead.
RHINTE30
This will create an infotype 0001 record with correct entries for org unit, job, position and work centre by looking through the organization structure. It creates a batch job, which must be run via SM35.
More details to follow.
RHCHECKV
This will check inverse relationships and create missing ones.
No comments:
Post a Comment