INTEGRATIONEXPLAIN THE PROGRAMS TO CHECK THE CONSISTENCY BETWEEN OM AND PA:

1. RHINTE00 –   PA to OM : The client may not implement OM.  After some time they may need OM.  At that time we have to this program.  When we run this program, whatever positions existing in PA will go to OM from PA – the program reads form IT 0001 and enter in OM.  However, reporting structure should be maintained manually.  A/0008 – Holder.  Whenever we hire a person, the system will create relationship A/0008.  When we upload OM and Employee Master Data separately, this relationship is not loaded.  Hence we have to run program RHINTE00.  Whenever we upload, we must compulsorily run RHINTE00 to create relationship.

RHINTE00 - Standard report to Transfer Organizational Assignment (PA -> PD)

RHINTE00.

Short textTransfer Organizational Assignment (PA -> PD)DescriptionThis report reads the infotype records of the Organizational Assignment infotype (0001) created in PA.The system then checks whether all or some of these records exist in PD.If all these records exist in PD, that is for the entire validity period of the PA record, a log is output. The log indicates that no changes are required in PD and no batch input session is created.If changes are required, the system creates the following records in PD according to the Create Object(s) and Create Relationship(s) parameters. Objects (infotype 1000):

Work center Job Organizational unit Position

 Relationships (infotype 1001) between the following objects: o Person and position (or work center)o Position and jobo Position and organizational unit

o Cost center and organizational unit or position (depending on the Relate Cost Center with parameter).

The system only creates objects and relationships with objects that are used in HR Master Data. The objects are created in the validity period they have in the relevant check tables for master data.If the validity periods of the PA and PD records border each other or overlap, a continuous record is created in PD or the existing record is extended (thereby avoiding splits in the validity period).

Example of bordering records: The following example illustrates how a PA record and a PD record that border each other are merged into one record in PD after report RHINTE00 has been run.

Record in PA:|<---PA RECORD--->|Record in PD:                 |<--PD-RECORD-->|Record in PD after RHINTE00 has been run:|<---------PD RECORD----------->|

Example of overlapping records:The following example illustrates how a PA record and a PD record that overlap each other are merged into one record in PD after report RHINTE00 has been run. 

                        Record in PA:|<-----------PA RECORD--------->|Record in PD:            |<----PD RECORD----->|Record in PD after RHINTE00 has been run:|<---------PD RECORD----------->|The settings of the switches PLOGI TEXTO, PLOGI TEXTC, and PLOGI TEXTS dictate which texts are copied to the ObjectAbbreviation (SHORT/Length=12) field of the PD object for organizational units, jobs, and positions.You can find these switches in the Implementation Guide (IMG) for Personnel Management under Organizational Management -> Integration -> Integration with Personnel Administration -> Set Up Integration with Personnel Administration.If these switches are activated, (value ='X'), the text of the PA object is transferred (and if necessary reduced to 12 characters) to the Object Abbreviation field of the PD object when report RHINTE00 is run.If these switches are not activated (value = ' '), the system transfers the object ID of the PD object to the ID field when report RHINTE00 is run.Example:The object ID of the PD object is '00001000'.Text for organizational unit in PA:Department 1Text in PD after RHINTE00, if PLOGI TEXTO='X':Department 1

Text in PD after RHINTE00, if PLOGI TEXTO=' ':00001000In both cases, the text of the PA object is transferred to the Object Name (STEXT) field of the PD object.Employees who have already left the company at the time the report is run, obtain a position relationship in HR-PD only up to the leaving date.If the leaving is to be transferred to HR-PD for employees who have already been transferred, you must select the parameter Transfer Leavings Only. In this case, only the relationships that still exist in HR-PD of employees who have already left are delimited. No records are created.Note:This report does not allow you to transfer an employee's leaving and subsequent reentry simultaneously. However, you can do this by running the program twice (once for the leaving, and once for the reentry).After this report has been run, a batch input session (BTCI) must be processed (exception: if it is a test run or no changes are required in PD).You can start the batch input session from the menu under System -> Services -> Batch Input -> Process. The session contains the name of the user who started report RHINTE00.The report uses the standard relationships listed in Customizing under Maintain Relationships to create relationships between said objects.SelectionYou make the entries according to standard selection for file PAnnnn. You must enter a start and end date for the time interval to be processed (default values: 01/01/1800 to 12/31/9999; ensures complete consistency between PA and PD).Report-Specific SettingsThe parameters of this report allow you to define the following:

The target plan version for the relevant objects and relationships (the standard target plan version is the integration plan version set up in Customizing under Set Active Plan Version).

Whether records are to be created in PD (transfer of organizational assignment) or delimited (transfer of employees' leaving). Records are created in the standard system.

Status to be used for relationships and objects (active or planned; only active for integration plan version).

Percentage to be used in the relationship (standard is 100%)

Whether objects and relationships are to be created. In the standard system, this option is selected = yes.

Object type with which relationships with cost centers are created (standard is O = organizational unit).

Whether old holder relationships are to be delimited (if can be decided technically).

If and under which name a batch input session is to be created.

For more information, see the documentation for the individual parameters:Create Object(s)This parameter enables you to specify whether integration objects (positions, jobs, and organizational units) are to be created.Only objects that are used in HR Master Data are created.Create Relationship(s)This parameter enables you to specify which of the following relationships are to be created:

Position - person Position - job Position - organizational unit Position or organizational unit - cost center

Only relationships between objects that are used in HR Master Data are created.Delimit Old Holder RelationshipsThis parameter provides you with the following options:

None (Presetting) : If you select this option, the system response is the same as before the functional enhancement, see SAP Note 637221. No holder relationships (infotype 1001, subtype A008/B008) for this person are delimited in PD.

Exception:If the Customizing setting of the time constraint for IT 1001/B008 < = '2', a person can only occupy one position at a time, thereby implicit delimitations occur. In this case, you must check all the holder relationships of this person and, if necessary, delimit them manually.SAP recommends you use this option, which is selected as standard. For an explanation, see SAP Note 554412.

Only positions from IT 0001

If you select this option, the report delimits previous, individual holder relationships in PD if the following conditions apply:

o A previous record with a different position has been found for each of the infotype 0001 records selected.

o Corresponding holder relationships with a validity identical to that of the transfer date have been found in infotype 0001 for these previous records.

In this case, the corresponding records are delimited as of the transfer date.Exception:If the corresponding holder relationship starts on the same date as the transfer in infotype 0001, this relationship is only delimited (or, in this case, deleted) if the staffing

percentage of a previous record in infotype 1001 for the same position has not changed. If it has changed, it is assumed that the relationship was created intentionally in PD and it is therefore not delimited.Caution:In the case of multiple assignments (one person occupies several positions), a maximum of one holder relationship is delimited in PD for each selected infotype 0001 record. The relationship that is saved in infotype 0001 is delimited.Example:The following example illustrates what RHINTE00 does if the Only Positions from IT 0001 option is selected.The following abbreviations are used: S = position, I = start and end selection of infotypes.Before RHINTE00 has been run:

Selection period:                         I------------------------Infotype 0001 I---S1-----I-S2--I--S2-I---S3------Infotype 1001/AB008 I---S1----------------------------------  " I---S4--I-------S4------------I--S4--

After RHINTE00 has been run:

Infotype 1001/AB008 I---S1-----I  "                  I-S2---------I  "                                     I---S3--------  " I---S4--I-------S4------------I--S4--

All

If you select this option, all holder relationships in PD that intersect the selected records are delimited as of the start date of the first selected infotype (or deleted if the holder relationship starts later than the first selected infotype 0001 record).Caution:SAP recommends you use this option only if you can ensure that persons in the selection period cannot occupy several positions at the same time meaning that no multiple assignments could exist.If multiple assignments do exist, this may result in required holder relationships being deleted unintentionally if, contrary to expectation, multiple assignments are intended for some persons.Example:The following example illustrates what RHINTE00 does if the All option is selected.The following abbreviations are used: S = position, I = start and end selection of infotypes.Before RHINTE00 has been run:

Selection period:                         I------------------------Infotype 0001 I---S1-----I-S2--I--S2-I---S3------Infotype 1001/AB008 I---S1----------------------------------

  " I---S4--I-------S4------------I--S4--

After RHINTE00 has been run:

Infotype 1001/AB008 I---S1-----I  "                  I-S2---------I  "                                     I---S3--------  " I---S4--I--I

Note:Irrespective of the option you select here, all the relevant data for infotype 0001 records found in the selection period are created again in PD according to the defined time constraint logic.Records listed in the list output of the report under Delimited or Deleted Relationships, can also appear under the records to be added. In this way, a technical delimitation is described.Provided they are available in the release you use, you can then run run report RHINTECHECK or RHINTE20 to find any remaining inconsistencies.For more details and information about the technical background, see SAP Note 637221.Session NameThis parameter enables you to enter a name for the batch input session that is created by this report.TestThis parameter enables you to specify whether a batch input session is to be created. If you select this parameter, a test run is executed without creating a batch input session.OutputThe report outputs a batch input session or a list of objects found for the session. It also outputs a list of personnel numbers for which no relationship with a position exists.

RHINTE10 – OM to PA: Suppose we created all in OM.  We can hire only through PA Module.  When we hire, we should get data from OM. RHINTE10 - Standard program to Prepare Integration (OM with PA)

RHINTE10

Short text

Prepare Integration (OM with PA)

Description

     This program allows you to create object types in Personnel Administration (HR-PA) which have already been set up in Personnel Planning and Development (HR-PD) and which are needed for integration.

The following object types are relevant to integration:PD PA

Work center(object type A)

Tables T528B, T528T

Job(Object type C)

Tables T513, T513S

Position(Object type S)

Tables T528B, T528T

Organizational unit

(Object type O)

Table T527X

    Only objects which exist in status 1 (active) in the integration plan version are included (see in PD Customizing under Set active plan version, entry PLOGI PLOGI).

     The integration object types are required for infotype 0001 "Organizational Assignment".A program run can take place for one or all object types.

Parameter

Creating ObjectsControls whether objects should be created in the tables for Personnel Administration. These objects are created, that is transferred to the existing objects in Personnel Planning and Development (HR-PD).

Deleting Non-Existent ObjectsControls whether objects in Personnel Administration tables (HR-PA) that only exist in these tables and not in Personnel Planning and Development ( HR-PD) should be deleted.

Only Objects with Original in OMRestricts the objects to be deleted to objects whose original is maintained in Organizational Management. In relation to the "Delete non-existent objects" parameter, only objects of the PA tables whose original was previously created in OM are taken into account. Objects which were created with their original in OM from the beginning and therefore have never existed in OM are not deleted.

Test

This parameter controls whether the program is to be run in test mode without table changes or in update mode with table changes.

Output

You obtain a list containing the number of records for each operation performed and for each object type. To display the individual records, double-click on a line.

RHINTE20 – Consistency Check.  Compares data in OM and PA.  This program will show the missing objects.  Comparison will be done with object IDs, the eight digit code. RHINTE20 - Standard report to Create missing objects (OM or PA)

RHINTE20

Short text

Create missing objects (OM or PA)

Description

This program can be used to check whether the relevant object types for integration have been created in both Personnel Administration (HR-PA) and Personnel Planning and Development (HR-PD).The entries in the HR tables T513/T513S (job), T528B/T528T (position, work center) and T527X (organizational unit) are compared with the corresponding objects that have been created in the HRPnnnn file for PD in the integration plan version.Objects that are missing either in PA or PD can be created immediately.

"Object ID" Parameter

For normal use of this report, do not enter an object ID. If you do, the system cannot return the expected results. An exception to this is the special case described below:

Special Case:If you only want to update or create certain Organizational Management (HR-PD) objects from Personnel Administration (HR-PA),

you can specify the HR-PD objects you do not want to update by making a multiple selection under the object ID.These objects do not appear in the results list 'Objects not in OM' and are therefore excluded from the update.

However, note that if you use the report in this way, the results list 'Objects not in OM' can differ from the title of the list in that it can include existing objects on the HR-PD side, but also objects that do not exist there.

"Integration Objects Only (PA)" Parameter

Selection parameter for reading PA table entriesInput value

performed action

Space All entries are selected.

'X'Only integration entries are selected.(indicator'P' in field RPPLAN)

RHINTE30 – After learning PA, we will study this. RHINTE30 - Standard report for Transfer org. assignment in batch input folder for infotype 0001

RHINTE30

Short text

Transfer org. assignment in batch input folder for infotype 0001

Description

This report creates a batch input session for specified personnel numbers. The session updates infotype 0001 "Organizational Assignment" (PA) for the persons concerned.The organizational assignment which was created by previous actions in Personnel Planning and Development is transferred to infotype 0001.You can find further information about integration and about using this report in Customizing in the description of the activity Set Up Integration with Personnel Administration and in the documentation of the form pool SAPFHPIN.

We recommend that you start the report in test mode initially.

Requirements

In order to start the report, integration between Personnel Planning and Development (PD) and Personnel Administration (PD) must be activated.In addition to this, a check of all personnel numbers is carried out to see whether they meet the integration conditions laid down in the feature PLOGI.

Parameters

Parameter "Personnel numbers"

Enter the personnel numbers or a range of personnel numbers for which you want to update infotype 0001.When the report is executed, a batch input session is created for personnel numbers that are related with positions in Personnel Planning and Development and that were changed.No input is interpreted as "All personnel numbers".

Parameter "Only open personnel numbers"

In this case, of the personnel numbers specified only those that are also stored in table 'HRINTE30" are edited.This table contains personnel numbers if you selected the setting BTCI (=PA update per batch) when you maintained the basic settings for integration with Personnel Administration in PLOGI PRELU (Integration: PA-Update Online or Batch). In this case, changes to personnel numbers are not recorded immediately in PA, but are collected in the table HRINTE30.You can find further information on the interdependencies of the settings in the entry PLOGI PRELU and this report in the documentation of the formpool SAPFHPIN.

Parameter "Start date"

Enter the date as of when the changes to infotype 0001 records are effective.Please note the following points regarding the start date of the infotype record update and the validity period of the record from the Personnel Planning perspective.Case 1:Start and end date of the validity period are after the date entered. In

this case, a record is created in PA with the same validity period. There are no changes made on the Personnel Planning side.Case 2:The start date of the validity period lies before the start date entered, and the end date is after it.In this case, a record is created in PA with a start date the same as the start date entered. The end date of the record is taken over.On the PD side, the original record is split at the start date entered.Case 3:Both the start and end date of the validity period are before the start date entered.In this case, no editing is carried out by the report.

Parameter "TEST"

Before you start program RHINTE30, you should ensure that your PD authorization profile allows you to change the position - person relationships concerned. You can check this by doing a test run for program RHINTE30. Should it turn out that you have authorization fornone of the personnel numbers, an empty batch input session would run. You can prevent this happening by doing a test run.

RHINTECHECK - Consistency Check OM-PA

RHINTECHECK

Short text

RHINTECHECK

Title

Consistency Check OM-PA

Purpose

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

Features

The report carries out a complete check for inconsistencies between PD and PA tables. It then returns inconsistencies in the following objects or assignments:

- Position- Job- Organizational unit- Cost center- Business area- Account assignment cost center PA- Account assignment cost center OM

The report only finds inconsistencies. To remove them, use the following tool reports:

Transfer Organizational Assignment (PA->OM)

Transfer org. assignment for infotype 0001 in a batch input session

Independently of the specific situation, you can also use the other integration tool reports to remove inconsistencies:

Prepare Integration (OM->PA)

Create Missing Objects

Selection

In the selection area, use the usual HR parameters to select the objects to be checked.For more selection parameters, select the "Further Selections" pushbutton.

    

TIME CONSTRAINTS:Time constraints are for deciding as to how many records we can have at a given period of time.  The length of time constraint is 1.A Time Constraint indicates whether more than one info type record may be available at one time.  The following Time Constraint Indicators are permissible:

Time Constraint 1:  An Info Type record must be available at all times.  This record may have no gaps.  We may not delete the record last stored on the database because all records of this Info Type would otherwise be deleted.Time Constraint 2:  Only one record must be available at one time, but time gaps are permitted.Time Constraint 3:  Any number of records may be valid at one time, and time gaps are

permitted.Time Constraint A:  Only one record may ever exist for this Info Type.  This record is valid from 01.01.800 to 31.12.9999.  Splitting is not possible.Time Constraint B: Only one record may ever exist for this Info Type.  It is valid from 01.01.800 to 31.12.9999.  Splitting is not possible, but can be deleted.Time Constraint T: The time constraint values depend on subtype.Time Constraint Z: This refers to or points to Time Management Info Types.  The time constraint for these Info Types depends on the time constraint class defined in view V_554Y_B               1 – Without gap.  No deletion.  Example: Org objects.  Bank Account               2 – W/o gaps. Can be deleted.  Most info types have this time constraint.               3 – There can be multiple valid active records, with gaps.  Deletion is possible. Examples: Children.  Cell    phone numbers.                4 - A – Example: IT 0003.  There is no other info type with this TC. Cannot be deleted.               5 -  B – Like A.  Can be deleted.