Classic Infotype Framework for HR Master Data Infotypes

The following prerequisites must be filled if you want to run SAP E-Recruiting and Personnel Management on an integrated system and you use the classic infotype framework:

In the system table T77S0, you must set the following parameters:

You must activate the following sample implementations of the BAdIs listed below or the corresponding third-party implementations:

Decoupled Infotype Framework for HR Master Data Infotypes

The following prerequisites must be filled if you want to run SAP E-Recruiting and Personnel Management on an integrated system and you use the decoupled infotype framework:

In the system table T77S0, you must set the following parameters:

You must activate the following sample implementations of the BAdIs listed below or the corresponding third-party implementations:

Initial Step After Installation

You are already using Personnel Management live in your system (HR system). You now install SAP E-Recruiting on the same system as well.

Since the HR system that you are using is a live system, Personnel Numbers (P) and Central Persons (CP) - and possibly also Business Partners (BP) - already exist there for all employees.

To create a Business Partner (BP) and a Candidate (NA) for each Personnel Number (P), you use the HRALXSYNC report (Object Synchronization and Repair).

You proceed as follows:

On the initial screen of the report, you select the Employee Areas affected and run the report.

In the Object Overview view, the system displays a table with the available personnel numbers and the existing business partners .

If a business partner exists for a personnel number , the system displays the Business Partner Number and Internal Candidate columns. In the latter column, a red icon means that there is no candidate assigned; a green icon indicates a candidate is assigned.

A green icon does not necessarily indicate that the SAP E-Recruiting data is synchronized with the Personnel Management data.

If no business partner exists for a personnel number , this is represented by a red icon in the Basic Data column and by the lack of an icon in the Internal Candidate column.

The columns in this table are dependent on the active implementations of the BAdI HRALX_HRALXSYNC_BADI

You select the personnel numbers for which no candidates were created yet and choose the Repair function.

The report first changes or creates the assigned business partners . The report then creates the missing candidates . To do this, the report calls the implementations of the BAdI HRSYNC_P . The following activities are executed within the DO_POST_PROCESSING method if no candidate has been created yet for the personnel number :

The method reads the user name and the e-mail address from the data in infotype 0105

The method uses the business partner number to create an Internal Candidate (NA) and links this with the Central Person (CP).

The method also creates a record in the infotype 5102 for the candidate and sets the IS_INACTIVE indicator ( FALSE if IT0000-STAT2 = 3 (employee is active in the company), otherwise TRUE ).

If records for infotype 0000 exist that lie in the future (BEGDA > SY-DATUM), the method writes the activity information in the indicator table T77RCF_P_STAT

For information about the table T77RCF_P_STAT, see also the Changes to the Activity Status in the Future section further down in this document.

If the user who is assigned to the personnel number in infotype 0105 does not exist, then the user is created. The user is assigned the reference user that corresponds to his or her role (internal candidate) according to table T77RCF_ROLE

If the user already exists (transaction SU01), the method assigns the reference user according to table T77RCF_ROLE . If a reference user is already assigned there, the method adds the roles that are assigned to the reference user according to table T77RCF_ROLE (internal candidate).

Only one reference user can be assigned at any one time.

If the infotype 0105 does not exist, no user is assigned to the candidate .

If the selected personnel number is no longer active, the system creates an external candidate for the internal candidate . In doing so, an alias is assigned to the associated user. If possible, the alias is the same as the user name .

If qualifications were assigned via infotype 1001 to the Personnel Number (P) (for example, through data entered via ESS scenarios or using the transaction PPPM), these qualifications are saved in infotype 5105 for the Candidate (NA).

Repairs in Live Operations

You want to synchronize the data for a candidate in SAP E-Recruiting with the data of the assigned personnel number for Personnel Management in a live system. You run the HRALXSYNC report to make any necessary repairs.

To do so, you proceed as follows:

On the initial screen of the report, you select the personnel number affected and run the report.

A green icon in the Internal Candidate column indicates that a Candidate (NA) exists for the Personnel Number (P).

The report reads the associated user and the e-mail address from the data in infotype 0105 . The report sets the IS_INACTIVE indicator of infotype 5102 according to infotype 0000 (FALSE if IT0000-STAT2 = 3, otherwise TRUE). If records for infotype 0000 exist that lie in the future (BEGDA > SY-DATUM), the report writes the activity information in the indicator table T77RCF_P_STAT

When the report is run for repair purposes, it does not process the infotypes 0001 and 0002 as this information was already adjusted for the Business Partner (BP) in the initial step by the same HRALXSYNC report.

The infotype 0006 (Addresses) is synchronized with the Business Partner (BP) outside the BAdI implementation CONVHR_DATA_TO_EREC for SAP E-Recruiting. To ensure that the addresses are still available in SAP E-Recruiting, the infotype 5110 (subtype 0000 ) must also be synchronized.

The report then adjusts the user according to the infotypes 0105 and 0000 . For internal candidates , the report writes the e-mail address from infotype 0105 to the address-independent part of the Business Partner (BP) and adjusts the data record in infotype 0105 (subtype 0003 ).

If qualifications were assigned via infotype 1001 to the Personnel Number (P) (for example, through data entered via ESS scenarios or using the transaction PPPM), these qualifications are saved in infotype 5105 for the Candidate (NA).

Hiring Without Referring to Candidates (PA40)

This case describes a hiring whereby a candidate did not already exist in SAP E-Recruiting .

The hiring date for a personnel number is in the future.

If you perform the procedure to hire a person although the hiring day lies in the future, the system creates the new Personnel Number (P) and the associated Central Person (CP) at the time when the data record is created.However, the system does not create a Business Partner (BP).For this reason, a candidate cannot be created in SAP E-Recruiting at this point in time.The system creates the candidate when you run the HRALXSYNC report for repair purposes on the hiring day (or later) and the report repairs the data for the personnel number .

In normal operations, you should schedule the HRALXSYNC report to run periodically (see the Changes to the Activity Status in the Future section).

The hiring date is in the past or is today.

The system creates the infotypes for a person within the framework of a hiring action (PA40). Each time these infotypes are changed, the system calls the implementations of the BAdI HRPAD00INFTY

As long as there is no candidate for the personnel number , the BAdI implementations have no effect.

Once the system has created the infotypes 0000 0001 , and 0002 , the system calls the BAdI implementation for the business partner integration and creates a Business Partner (BP).

The system then calls the implementations of the BAdI HRSYNC_P . The system uses the SAP E-Recruiting sample implementation to create an internal candidate using the business partner number and the personnel number .

In addition, the system creates the infotype 5102 and sets the IS_INACTIVE indicator according to the attribute of the STAT2 field for the current infotype record 0000 . For future infotype records 0000 , the system fills the table T77RCF_P_STAT accordingly.

If other infotypes relevant for SAP E-Recruiting ( 0000 0001 0002 0006 0105 ) are created within the framework of a hiring action, the system processes them using the BAdI implementation HR_INTEGRAT_TO_EREC

For changes to the infotype 0105 according to the criteria as described in the Initial Step After Installation section, the system creates a user and/or enhances the profile of an existing user .In addition, the system adjusts the e-mail address in the address-independent part of the Business Partner (BP) (including infotype 5110 (subtype 0003 )).

For changes to the infotype 0000 according to the criteria as described in the Initial Step After Installation section, the system sets the IS_INACTIVE indicator in infotype 5102 for a current infotype record. For a future infotype record, the system makes an entry in the indicator table T77RCF_P_STAT . The system also changes the profile of the user (SU01).

For changes to the infotype 0006 according to the criteria as described in the Initial Step After Installation section, the system synchronizes the infotype 5110 (subtype 0000 ).

The infotypes 0001 and 0002 influence only the Business Partner (BP) in SAP E-Recruiting .

SAP does not deliver any implementations for these infotypes as it is assumed that the synchronization with the business partner was already performed before the BAdI implementation HR_INTEGRAT_TO_EREC is executed.

If qualifications were assigned via the infotype 1001 to the Personnel Number (P) (for example, through data entered via ESS scenarios or using the transaction PPPM), these qualifications are saved in infotype 5105 for the Candidate (NA) (according to the setting of the RECFA HRQUA switch in table T77SO ).

Hiring with Reference to the Candidate (PA48)

This case describes the hiring of an external candidate using SAP E-Recruiting . The external candidate's information is transferred by Remote Function Call (RFC) to the transaction PA48 (module pool SAPMPRAP, table T752F) in the same system. The system starts a hiring action whereby the transferred data is used as default values. Once the hiring action has been performed, the system calls the HR_RCF_ASSIGN_EE_TO_CANDIDATE function module (via RFC to the same system). The function module informs SAP E-Recruiting that the external candidate has become a personnel number XYZ . For a hiring in the future, the system saves this information in the indicator table T77RCF_EMPL_CAND In all other cases, the system processes this information directly (see the Hiring in the Past section below).

The following graphic describes the object relationships at the point in time when the system calls the function module.

Object Relationships when Calling the Function Module

The hiring date of an external candidate is in the future

When hiring an external candidate as of a date in the future, the system does not create a Business Partner (BP) for the Personnel Number (P) and Central Person (CP). This means that an internal candidate is not created in SAP E-Recruiting . The system stores the information about the future assignment of the personnel number to the candidate ID in the table T77RCF_EMPL_CAND (function module HR_RCF_ASSIGN_EE_TO_CANDIDATE ). The system then creates the business partner on the hiring day or later using the HRALXSYNC report. The sample implementation of the BAdI HRSYNC_P recognizes that no candidates have existed up to now for the personnel number , but that the personnel number was created as the result of hiring an external candidate .

The system then deletes the Central Person object (CP 1) for the external candidate (NA 1) (with its relationships (infotype 1001)) and writes the relationship (infotype 1001) from the external candidate (NA 1) to the new Central Person (CP 2). The system then locks the user of the external candidate .

The following graphic displays the object relationships:

Object Relationships for a Hiring in the Future

The hiring date of an external candidate is not in the future

When an external candidate (NA 1) is hired on a date that is not in the future, the Personnel Number (P) and the Central Person (CP 2) exist. The system creates a Business Partner (BP 2) and a new candidate (NA 2) (see also the Hiring Without Referring to Candidates section). When a new candidate is created, the system ( hiring action ) does not recognize that an external candidate already exists.

The system then deletes the Central Person object (CP 1) for the external candidate (NA 1) and the new internal candidate (with all relationships in each case (infotype 1001)) and writes the relationship (infotype 1001) from the external candidate (NA 1) to the newly created Central Person (CP 2). The system locks the old User (US 1) of the external candidate . If a User (US 2) is assigned to the new Central Person (CP 2), the system uses the CHANGE_USER_ROLE method of the CL_HRRCF_CANDIDATE class to assign the reference user of the internal candidate to this user .

The following graphic displays the object relationships:

Object Relationships for a Hiring in the Past or Today

Hiring With Reference to Candidates (XI Interface)

You can integrate SAP E-Recruiting and HCM Processes and Forms using the XI Content for HCM Processes and Forms . In this way, you can transfer data from the SAP E-Recruiting system to the HR system using the XI interface and then trigger the hiring of a new employee in the HR system (XI scenario New Hire Request from E-Recruiting (NEWHIREREQUEST) ). Once the hiring process has been completed successfully and the HireConfirmation XI message has been received, the system calls the HR_RCF_ASSIGN_EE_TO_CANDIDATE function module. The function module informs SAP E-Recruiting that the external candidate has become a Personnel Number P . For a hiring in the future, the system saves this information in the indicator table T77RCF_EMPL_CAND In all other cases, the system processes this information directly (see also the Hiring with Reference to the Candidate (PA48) section).

Infotype Changes to an Active Personnel Number (PA30)

The system uses the HR_RCF_TRANSFER_HRPA30_CHANGES function module to perform changes (such as Create, Change, Delete) to the PA infotype 0000 0001 0002 0006 0105 of a Personnel Number (P) for which a candidate exists. The following changes are relevant:

Infotype 0000 : Indicator IS_EMPLOYEE , user profile

Infotype 0006 : Synchronization with Business Partner (BP) and infotype 5110 (subtype 0000 )

Infotype 0105 : E-mail address for Business Partner (BP) and in infotype 5110 (subtype 0003 ), user profile

We recommend that you do not change an existing user assignment to the personnel number.

The system uses the sample implementation HRRCF00_STORE_HRQUAL of the BAdI HRBAS00INFTY to make changes to PD infotypes (Qualifications). To do so, the system processes the records of the Qualification object type (Q) that are assigned to the personnel number via the relationship B032. If a Candidate (NA) exists, the system synchronizes the infotype 5105 for the candidate with the qualifications (according to the setting of the RECFA HRQUA switch in table T77SO ).

Changes to the Activity Status in the Future

You can use the HRALXSYNC report to transfer manually the associated Candidate (NA) for a specific Personnel Number (P) to an internal or external candidate. This depends on the attribute of the STAT2 field in the current record of the infotype 0000 The report updates the indicator table T77RCF_P_STAT . As part of the update, the report deletes obsolete data records and writes future data records.

You can use the PROCESS_CAND_STAT_CHANGE periodic service (class CL_HRRCF_UPDATE_P_STAT) to automate the changes to the activity status at the correct point in time. The periodic service must run on a daily basis and ensures that the Candidate becomes an internal or external candidate on the day of re-entry or leaving. To do this, the service uses the data from the indicator table T77RCF_P_STAT

Dismissal

In the case of a dismissal, the STAT2 attribute in infotype 0000 is given a value other than 3 . The system uses the sample implementation HR_INTEGRATE_TO_EREC of the BadI HRPAD00INFTY to set the IS_INACTIVE indicator directly in infotype 5102 to TRUE (dismissal not in the future), update the user profile, and create an alias if possible. For a dismissal in the future, the system makes a corresponding entry in the indicator table T77RCF_P_STAT (see also the Changes in the Activity Status in the Future section).

Rehire

In the case of a rehire, the STAT2 attribute in infotype 0000 is given the value 3 again.The sample implementation HR_INTEGAT_TO_EREC ensures that the system sets the IS_INACTIVE indicator in infotype 5102 to FALSE (rehire not in the future) or that the system makes a corresponding entry in the indicator table T77RCF_P_STAT (see the Changes in the Activity Status in the Future section). The system changes the profile of the assigned user according to the IS_INACTIVE indicator.