INTEGRATION EXPLAIN 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 text Transfer Organizational Assignment (PA -> PD) Description This 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 o o
Position and job Position and organizational unit 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: || Record in PD: || Record in PD after RHINTE00 has been run: ||
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: || Record in PD: || Record in PD after RHINTE00 has been run: || 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 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 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. 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 be processed (default values: 01/01/1800 to 12/31/9999; ensures complete consistency 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 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 Relationships This 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 o
A previous record with a different position has been found for each of the infotype 0001 records selected. 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--
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 f