Description
This report reads the infotype records of the OrganizationalAssignment infotype (0001) created in PA.
The system then checks whether all or some of these records existin PD.
If all these records exist in PD, that is for the entire validity periodof the PA record, a log is output. The log indicates that no changesare required in PD and no batch input session is created.
If changes are required, the system creates the following records inPD according to the Create Object(s) and CreateRelationship(s) parameters.

• Objects (infotype 1000):

Work center
Job
Organizational unit
Position

• Relationships (infotype 1001) between the following objects:

Person and position (or work center)
Position and job
Position and organizational unit
Cost center and organizational unit or position (depending on theRelate Cost Center with parameter).
The system only creates objects and relationships with objects that areused in HR Master Data. The objects are created in the validity periodthey have in the relevant check tables for master data.
If the validity periods of the PA and PD records border each other oroverlap, a continuous record is created in PD or the existing recordis extended (thereby avoiding splits in the validity period).

• Example of bordering records:

The following example illustrates how a PA record and a PD recordthat border each other are merged into one record in PD after reportRHINTE00 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 thatoverlap each other are merged into one record in PD after reportRHINTE00 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 TEXTSdictate which texts are copied to the Object
Abbreviation (SHORT/Length=12)field of the PD object for organizational units, jobs, and positions.
You can find these switches in the Implementation Guide (IMG) forPersonnel 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 thePA object is transferred (and if necessary reduced to 12 characters)to the Object Abbreviation field of the PD object whenreport RHINTE00 is run.
If these switches are not activated (value = ' '), the system transfersthe object ID of the PD object to the ID field when reportRHINTE00 is run.
&EXAMPLE&:
The object ID of the PD object is '00001000'.
Text for organizational unit in PA:
Department 1
Text in PD after RHINTE00, if PLOGI TEXTO='X':
Department 1
Text in PD after RHINTE00, if PLOGI TEXTO=' ':
00001000
In both cases, the text of the PA object is transferred to theObject Name (STEXT) field of the PD object.
Employees who have already left the company at the time the report isrun, obtain a position relationship in HR-PD only up to the leavingdate.
If the leaving is to be transferred to HR-PD for employees who havealready been transferred, you must select the parameterTransfer Leavings Only. In this case, only the relationshipsthat still exist in HR-PD of employees who have already left aredelimited. No records are created.
&NOTE&:
This report does not allow you to transfer an employee's leaving andsubsequent reentry simultaneously. However, you can do this by runningthe program twice (once for the leaving, and once for the reentry).
After this report has been run, a batch input session (BTCI) must beprocessed (exception: if it is a test run or no changes are required inPD).
You can start the batch input session from the menu under System-> Services -> Batch Input -> Process. Thesession contains the name of the user who started report RHINTE00.
The report uses the standard relationships listed in Customizingunder Maintain Relationships to create relationships betweensaid objects.

Selection
You make the entries according to standard selection for file PAnnnn.You must enter a start and end date for the time interval to beprocessed (default values: 01/01/1800 to 12/31/9999; ensures completeconsistency between PA and PD).

Report-Specific Settings
The 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 setup 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). Recordsare 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 individualparameters:

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 followingrelationships 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 Dataare created.

Delimit Old Holder Relationships
This parameter provides you with the following options:


• None (Presetting)

If you select this option, the system response is the same asbefore the functional enhancement, see SAP Note 637221. No holderrelationships (infotype 1001, subtype A008/B008) for this personare 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, therebyimplicit delimitations occur. In this case, you must check allthe holder relationships of this person and, if necessary, delimitthem manually.
SAP recommends you use this option, which is selected as standard. Foran explanation, see SAP Note 554412.

• Only positions from IT 0001

If you select this option, the report delimits previous, individualholder relationships in PD if the following conditions apply:
A previous record with a different position has been found for each ofthe infotype 0001 records selected.
Corresponding holder relationships with a validity identical to thatof thetransfer date have been found in infotype 0001 for these previousrecords.
In this case, the corresponding records are delimited as of thetransfer date.
Exception:
If the corresponding holder relationship starts on the same date as thetransfer in infotype 0001, this relationship is only delimited (or,in this case, deleted) if the staffing percentage of a previous recordin infotype 1001 for the same position has not changed. If it haschanged, it is assumed that the relationship was created intentionallyin PD and it is therefore not delimited.
Caution:
In the case of multiple assignments (one person occupies severalpositions), a maximum of one holder relationship is delimited in PD foreach selected infotype 0001 record. The relationship that is savedin infotype 0001 is delimited.
&EXAMPLE&:
The following example illustrates what RHINTE00 does if theOnly Positions from IT 0001 option is selected.
The following abbreviations are used: S = position, I = start and endselection 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 intersectthe selected records are delimited as of the start date of the firstselected infotype (or deleted if the holder relationship startslater than the first selected infotype 0001 record).
Caution:
SAP recommends you use this option only if you can ensure that personsin the selection period cannot occupy several positions at the sametime meaning that no multiple assignments could exist.
If multiple assignments do exist, this may result in required holderrelationships being deleted unintentionally if, contrary to expectation,multiple assignments are intended for some persons.
Example:
The following example illustrates what RHINTE00 does if the Alloption is selected.
The following abbreviations are used: S = position, I = start and endselection 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 forinfotype 0001 records found in the selection period are created againin PD according to the defined time constraint logic.
Records listed in the list output of the report under Delimitedor Deleted Relationships, can also appear under the records to beadded. In this way, a technical delimitation is described.
Provided they are available in the release you use, you can then runrun report RHINTECHECK or RHINTE20 to find any remaininginconsistencies.
For more details and information about the technical background, seeSAP Note 637221.

Session Name
This parameter enables you to enter a name for the batch input sessionthat is created by this report.

Test
This parameter enables you to specify whether a batch input session isto be created. If you select this parameter, a test run is executedwithout creating a batch input session.

Output
The report outputs a batch input session or a list of objects foundfor the session. It also outputs a list of personnel numbers for whichno relationship with a position exists.