integration en

Integration of SAP E-Recruiting / SAP ERP You can run SAP E-Recruiting as a standalone scenario on one instance or in an integrated scenario on different instances.

In the integrated scenario, SAP E-Recruiting runs on the same system and client as SAP ERP Central Component (SAP ECC). (Software runs on one instance.)

In the standalone scenario, only SAP E-Recruiting is active in the system; other active ERP components are installed on another system, separate from the SAP E-Recruiting system. This scenario also includes the case where SAP E-Recruiting runs on the same system as the ERP components, but in a different client. (Software runs on different instances.)

The following documents describe the integration of SAP E-Recruiting and SAP ERP for these installation options:

ERP Integration (Software Runs on One Instance)

ERP Integration (Software Runs on Different Instances)

ERP Integration (Software Runs on One Instance) This document describes the integration between SAP E-Recruiting and SAP ERP for the situation whereby both run on the same system.

SAP E-Recruiting and SAP ERP in the Integrated System For each Personnel Number (P) in Personnel Management in an integrated system, a corresponding Candidate (NA) must exist in SAP E-Recruiting.

For each employee, the Personnel Number (P) and Central Person (CP) objects must exist in Personnel Management. In addition, a Business Partner (BP) must exist for each Central Person (CP) if the (first) hiring date of the associated personnel number has been achieved.

SAP E-Recruiting creates a Candidate (NA) for each Personnel Number (P) for which a Business Partner (BP) also exists.

If Concurrent Employment (CE) is active, SAP E-Recruiting creates a Candidate (NA) for each Central Person (CP). Several Personnel Numbers can be assigned to a Central Person.

The following graphic shows the object relationships between the relevant Personnel Management objects and SAP E-Recruiting objects.

Object Relationships

B208 (2) (Relationship can be simulated via IT0105)

-

Central Person

(CP)

Business Partner

(BP)

User (US)

Person(P)

Candidate(NA)

B207 (2)

B209 (3)

A209 (2)

B650 (2) A650 (2)

The HR master data for the personnel numbers is saved in PA infotypes. The data can be accessed using the classic or the decoupled infotype framework.

For decoupled infotypes, there is a strict distinction made between the business logic and the user interface-relevant elements.

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:

Parameter in Table T77S0

Group Semantic Abbreviation Value

HRALX HRAC X

RECFA DTCBA Logical system (self-referring), not required when using XI technology for the data transfer

RECFA HRRFC Logical system (self-referring), not required when using XI technology for the data transfer but definitely required for integration in Organizational Management

RECFA RECCE Specifies whether Concurrent Employment is active in the E-Recruiting system.

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

BAdI Implementations

BAdI Sample Implementation

HRSYNC_P CONV_HR_DATA_TO_EREC

HRALX_HRALXSYNC_BADI CHECK_INTER_NA_EXIST

HRPAD00INFTY HR_INTEGRATION_TO_B

HRPAD00INFTY HR_INTEGRAT_TO_EREC

HRBAS00INFTY HRRCF00_STORE_HRQUAL

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:


Group Semantic Abbreviation Value

HRALX HRAC X

RECFA DTCBA Logical system (self-referring), not required when using XI technology for the data transfer

RECFA HRRCF Logical system (self-referring), not required when using XI technology for the data transfer but definitely required for integration in Organizational Management

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



HRSYNC_P CONV_HR_DATA_TO_EREC

HRALX_HRALXSYNC_BADI CHECK_INTER_NA_EXIST

HRPAD00INFTY HR_INTEGRATION_TO_BP

HRPAD00INFTYBL HRRCF00_HR2EREC_NEW_IFRMWK

HRBAS00INFTY HRRCF00_STORE_HRQUAL

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 Central Person (CP), you use the HRALXSYNC report (Object Synchronization and Repair).

For information about the report and the integration of Personnel Administration with SAP Business Partner, see SAP Library and choose Integration with SAP Business Partner [Extern].

If you use the HRALXSYNC report, 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 you use Concurrent Employment (CE), at least one of the personnel assignments must be active in order for SAP E-Recruiting to be able to recognize the employee as an active employee.

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 5110 (subtype 0003).

If you use Concurrent Employment (CE), different users and e-mail addresses can be stored for different personnel assignments. In this case, the system uses the e-mail address and the user of the oldest active personnel assignment.

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 (Transaction 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 indicator IS_INACTIVE according to the attribute of the field STAT2 of the current infotype record 0000.


In the case of 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 (Transaction 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

NA1

CP1

US1

BP1

CP2

US2

P

External Candidate

Personnel Number(Hiring in the future)

NA2

CP2

US2

BP2P

Personnel Number(Hiring in the past)

A

B

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 (CP1) for the external candidate (NA1) (with its relationships (infotype 1001)) and writes the relationship (infotype 1001) from the external candidate (NA1) to the new Central Person (CP2). 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

NA1

CP1

US1

BP1

CP2

US2

P BP2

The system performs the following steps:

• No changes when calling the function module

• Entry in the indicator table T77RCF_EMPL_CAND

• The HRALXSYNC report makes the following changes on the hiring date

• Creation of BP2, assignment to CP2

• Reassignment of NA1

• Deletion of CP1 and the relationships from CP1 to BP1

and US1

The hiring date of an external candidate is not in the future When an external candidate (NA1) is hired on a date that is not in the future, the Personnel Number (P) and the Central Person (CP2) exist. The system creates a Business Partner (BP2) and a new candidate (NA2) (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 (CP1) for the external candidate (NA1) and the new internal candidate (with all relationships in each case (infotype 1001)) and writes the relationship from the external candidate (NA1) to the newly created Central Person (CP2). The system locks the old User (US1) of the external candidate. If a User (US2) is assigned to the new Central Person (CP2), 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

NA1

CP1

US1

BP1

NA2

CP2

US2

BP2P

The system performs the following steps:• Changes when calling the function module• No entry in the indicator table T77RCF_EMPL_CAND• Reassignment of NA1, deletion of NA2• Deletion of CP1 and the relationships from CP1 to BP1 and US1• Deactivation of US1

Hiring With Reference to Candidates (XI Interface) You can integrate SAP E-Recruiting and HCM Processes and Forms [Extern] using the XI Content for HCM Processes and Forms [Extern]. 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) [Extern]). 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 (Transaction 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.

ERP Integration (Software on Different Instances) This document describes the integration between SAP E-Recruiting and SAP ERP for the situation whereby they run on different systems or where they run on the same system but in different clients. This document focuses on the inbound processing of the IDocs of Application Link Enabling (ALE) that are sent from the connected SAP ERP system on which Personnel Management (PA) is installed.

There are different scenarios, as follows:

In scenario I2-A, only SAP E-Recruiting runs on one system. Personnel Management runs on another system, independent of the SAP E-Recruiting system.

SAP E-Recruiting Scenario I2-A

SAP NetWeaver SAP NetWeaver

SAP E-Recruiting SAP ERP HCM

SAP ERP

SAP NetWeaver

SAP ERP HCM

SAP NetWeaverSAP NetWeaverSAP NetWeaverSAP NetWeaverSAP NetWeaverSAP NetWeaver

In scenario I2-B, SAP E-Recruiting runs on one system (client) integrated in an SAP ERP system in which only SAP E-Recruiting is active. Personnel Management is active on another ERP system or client, independent of the SAP E-Recruiting system.

SAP E-Recruiting Scenario I2-B

SAP NetWeaver SAP NetWeaver

SAP E-Recruiting SAP ERP HCM

SAP ERP

SAP NetWeaver

SAP ERP HCM

SAP NetWeaverSAP NetWeaverSAP NetWeaverSAP NetWeaverSAP NetWeaverSAP NetWeaver

SAP ERP

SAP ERP HCM

SAP E-Recruiting and SAP ERP in the I2-A Scenario The program RHALEINI (transaction PFAL) distributes the employees (personnel numbers) in the SAP E-Recruiting system. Once the Personnel Management objects are distributed in SAP E-Recruiting, a corresponding object Candidate (NA) must exist in the SAP E-Recruiting system for each Personnel Number (P) in the Personnel Management system.

For each employee, the Personnel Number (P) and Central Person (CP) objects must exist in Personnel Management. In addition, a Business Partner (BP) must exist for each Central Person (CP) if the (first) hiring date of the associated personnel number has been achieved.

SAP E-Recruiting then creates a Candidate (NA) for each Personnel Number (P) for which a Business Partner (BP) also exists.

If Concurrent Employment (CE) is in use, SAP E-Recruiting creates a Candidate (NA) for each Central Person (CP). Several Personnel Numbers can be assigned to a Central Person.

The following graphic shows the object relationships between the relevant Personnel Management objects and SAP E-Recruiting objects.

Object Relationships

PersonnelNumber (P) User (US)

Central Person

(CP)

Position (S)

Candidate (NA)

Business Partner (BP)

0..n

0..n

The HR master data for the personnel numbers is saved in PA infotypes.

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


Group Semantic Abbreviation

Value Description

HRALX HRAC X Activates HR integration

HRALX PBPHR ON Distributes employees from connected HR system

HRALX USRAC X Creates relationship to user

RECFA HRRFC Logical system, not required when using XI technology for the data transfer but definitely required for integration in Organizational Management

Logical system of the coupled HR system

RECFA RECCE Specifies whether Concurrent Employment (CE) is active in the SAP E-Recruiting system.

Concurrent Employment is active in the SAP E-Recruiting system (parameter is relevant as of Release 604)

RECFA DTCBA Logical system (required on the HR system side) , not required when using XI technology for the data transfer

RFC connection to the SAP E-Recruiting system

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



HRSYNC_P CONV_HR_DATA_TO_EREC (active as of Release 604)

HRALX_HRALXSYNC_BADI CHECK_INTER_NA_EXIST (inactive)

HRALE00INBOUND_IDOC HRRCF00_INBD_NEWMOD (active as of Release 604)

HRALE00SPLIT_INBOUND HR_INB_PROCESS_IDOC (inactive as of Release 604)

HRALE00INBOUND_IDOC HRRCF00_DELETE_SPREL (inactive as of Release 604)

HRALE00SPLIT_INBOUND HR_INB_PROCESS_IDOC (active up to Release 603)

HRALE00INBOUND_IDOC HRRCF00_DELETE_SPREL (active up to Release 603)

Best Practices After Installation of SAP E-Recruiting (ALE Distribution) up to Release 603

This section is relevant only for releases up to 603 and describes the initial distribution of the Personnel Number (P) und Position (S) objects.

Prerequisites You already use Personnel Management in your HR system.

You have installed SAP E-Recruiting as described in the I2 scenarios.

You want to perform an initial distribution of HR master data (object type P) and of the organizational structure (object types O, S) or of other object types.

Procedure

You use the program RHALEINI to create all initial candidate objects (NA objects) in SAP E-Recruiting.

In an I2 scenario, SAP E-Recruiting exchanges the P S relationship for a CP S relationship in infotype 1001.

If you perform the initial distribution of the objects P and S in Insert Mode (an IDoc with two segments, one for the object P and another for the object S), it can occur that the relationship CP S is created first during the inbound process for the segment of the object P. However, this relationship is then deleted again by the Insert Mode when the second IDoc segment with the object S is processed.

For this reason, we recommend the following initial distribution strategy:

This is just a recommendation; other procedures are also possible.

Distribute all objects of the type Organizational Unit (O) using the program RHALEINI. Make sure that all objects of the type O are created in the SAP E-Recruiting system by using the Update Mode as Transfer Mode and specifying the infotype 1000.

Repeat the previous step for the object type S.

Redistribute all objects of the object type O again using the program RHALEINI. Make sure that all objects of the type O and the relationships between the objects are created in the SAP E-Recruiting system by using the Insert Mode as Transfer Mode.

The infotype 1000 is not redistributed again in this case.

Repeat the previous step for the object type S.

Distribute all objects of the object type P using the program RHALEINI. Make sure that all objects of the type P and the relationships between the objects are created in SAP E-Recruiting by using the Insert Mode as Transfer Mode. In addition, the system creates the objects of the type Candidate (NA).

ALE Inbound Processing in SAP E-Recruiting The ALE inbound processing creates candidates or updates them in SAP E-Recruiting for the installation as an I2 scenario.

Note that the inbound processing was changed as of Release 604 (due to CE functionality) and the ALE inbound processing workflow is therefore different in SAP E-Recruiting.

Inbound Process up to Release 603

SAP E-Recruiting Inbound Processing in I2-A (I2-B) Scenario up to Release 603

SAP NetWeaver

SAP E-RecruitingSAP ERP HCM

PA

PersonnelAdministration

CP BP NA

ALE

BAdIHRALE00SPLIT_INBOUND

SAP E-Recruiting Inbound Processing

process_selected_data

The inbound process calls the implementation of the BAdI HRALE00SPLIT_INBOUND. The system performs the following activities using the method HRRCF_CAND_FROM_EE_ALE of the class CL_HRRCF_EMPLOYEE_INBOUND.

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

The method creates a Business Partner (BP) and a Central Person (CP), which are required to create an internal candidate. The method then links this candidate (infotype 1001) with the Central Person.

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

If the user who is assigned to the personnel number in infotype 0105 does not exist in the IDoc, the method creates the user by using the template EEXXXXXXXX (where XXXXXXXX is the eight characters from his or her personnel number). The system then assigns to the user the reference user that corresponds to his or her role (internal candidate) according to table T77RCF_ROLE.

If qualifications are distributed via the IDoc from infotype 1001 to Personnel Number (P), the system saves these qualifications in infotype 5105 of the Candidate (NA).

The relationship P S of the original IDoc changes to a relationship of the type CP S.

Hiring Without Referring to Candidates (Transaction PA40) up to Release 603 This case describes a hiring whereby a candidate did not already exist in SAP E-Recruiting.

If the hiring date for a Personnel Number lies in the future, the inbound process creates an entry in the table T77RCF_P_STAT with the hiring date on which the periodic service PROCESS_CAND_STATUS_CHANGE reclassifies the candidate from an external candidate to an internal candidate. The integration then occurs as described in the Inbound Process up to Release 603 section (BP, NA, and so on are created).

Inbound Process as of Release 604 SAP E-Recruiting Inbound Processing in I2-A (I2-B) Scenario as of Release 604

SAP NetWeaver

SAP E-RecruitingSAP ERP HCM

PA

PersonnelAdministration

CP BP NA

ALE

BAdIHRALE00INBOUND_IDOC

process_idoc

Standard ALE Inbound Processingfor HR Master Data

SAP E-Recruiting Inbound Processing

post_process_idoc

The inbound process calls the implementation of the BAdI HRALE00INBOUND_IDOC. This enables the execution of the standard ALE inbound processing for HR master data. The infotype framework used for this (IT5580 to IT5588) lies in the basis layer (SAP_ABA).

As of Release 604, SAP E-Recruiting uses the standard ALE inbound processing for HR master data and creates only the SAP E-Recruiting objects. The standard ALE inbound processing for HR master data creates all other objects, such as BP, CP, and so on, and links the HR master data with the infotype framework.

The SAP E-Recruiting-specific part of the inbound processing lies in the method POST_PROCESS_IDOC of the implementation of the BAdI. The method DO_ALE_POST_PROCESSING of the class CL_HRRCF_ALE_EE_INBOUND performs the following activities:

Concurrent Employment (CE) supports only this implementation for the inbound processing.

The method reads the e-mail address from the data of the Business Partner (BP).

The standard ALE inbound processing for HR master data links the IDoc data of the infotype 0105 with that of the infotype 5585. The infotype 5585 then contains the user for SAP E-Recruiting.

The method uses the Business Partner (BP) and the Central Person (CP) (that were created by the standard ALE inbound processing for HR master data) to create an internal Candidate (NA). The method then links the Candidate with the Central Person.

The method also creates an entry in infotype 5102 for the candidate and sets the indicator IS_INACTIVE to FALSE if the IDoc data from IT0000-STAT2 = 3 (employee is active employee), otherwise to TRUE. If Concurrent Employment (CE) is in use, at least one staff assignment must be an active assignment so that SAP E-Recruiting can recognize the employee as an active employee.

If the user who is assigned to the personnel number in infotype 5585 does not exist in the IDoc, the method creates the user by using the template EEXXXXXXXX (where XXXXXXXX is the eight characters from his or her personnel number). The system then assigns to the user the reference user that corresponds to his or her role (internal candidate) according to table T77RCF_ROLE.

If qualifications are distributed via the IDoc from infotype 1001 to Personnel Number (P), these qualifications are saved in infotype 5586 by the standard ALE inbound processing for HR master data. SAP E-Recruiting then copies them from there to the infotype 5105 of the Candidate (NA).

SAP E-Recruiting copies the address of the candidate from the Business Partner.

Note that the standard ALE inbound processing for HR master data saves the relationship S as a CP S relationship in infotype 5586 and in infotype 1001. SAP E-Recruiting

does not make any changes to the assignments.

Hiring Without Referring to the Candidate (Transaction PA40) as of Release 604 This case describes a hiring whereby a candidate was not already created in SAP E-Recruiting.

If the hiring date of a person lies in the future, the ALE inbound processing only creates a new Personnel Number (P) and the assigned Central Person (CP) in the infotypes 5580 to 5588. No entry is created in infotype 1001 at this point in time. As the system does not create a Business Partner (BP), SAP E-Recruiting cannot create a Candidate (NA) at this point in time.

The system does not create the candidate until you run the report HRALESYNC in repair mode on the hiring day or later. The report repairs the data by creating the corresponding Business Partner (BP) and the entries in the infotype 1001. The BAdI implementation CONV_HR_DATA_TO_EREC of the BAdI HRSYC_P then calls the SAP E-Recruiting inbound processing DO_ALE_POST_PROCESSING and the integration proceeds as described in the section Inbound Process as of Release 604.

In normal operations, you should schedule the HRALESYNC report to run periodically.

Hiring with Reference to the Candidate (Transaction PA48) This case describes the hiring of an external candidate using SAP E-Recruiting. In this case, the data of the external candidate is transferred by Remote Function Call (RFC) to the transaction PA48 (module pool SAPMPRAP, table T752F) of the HR system. The system starts a hiring action whereby the transferred data is used as default values. After executing the hiring action, the system calls the function module HR_RCF_ASSIGN_EE_TO_CANDIDATE. This function module informs SAP E-Recruiting that a personnel number was created for the external candidate and creates the CP P relationship in infotype 1001.

Only the Personnel Number (P) was assigned to the Candidate (NA). The candidate remains an external candidate until the ALE inbound processing is performed.

Hiring With Reference to the Candidate (XI Interface) You can integrate SAP E-Recruiting and HCM Processes and Forms [Extern] using the XI Content for HCM Processes and Forms [Extern]. 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) [Extern]). Once the employee is hired successfully and the XI message HireConfirmation is received, the system calls the function module HR_RCF_ASSIGN_EE_TO_CANDIDATE and behaves as if the HireConfirmation message had been sent via an RFC call (see Hiring with Reference to the Candidate (Transaction PA48)).

Changes to the Activity Status in the Future If you made changes to the activity status in the master data of an employee (changes that affect the attribute of the field STAT2 in the infotype 0000) and you distribute these changes via ALE in SAP E-Recruiting, SAP E-Recruiting must declare the associated candidate as an internal or external candidate. The inbound processing in SAP E-Recruiting writes an indicator in the indicator table T77RCF_P_STAT that changes are to take place in the future.

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 inbound processing sets the indicator IS_INACTIVE in infotype 5102 to TRUE (dismissal not in the future) and updates the user profile. For a dismissal in the future, the

system makes a corresponding entry in the indicator table T77RCF_P_STAT (see also the Changes to the Activity Status in the Future section).

If you use Concurrent Employment (CE), all of the personnel assignments of an employee must be inactive in order for SAP E-Recruiting to be able to recognize the employee as an inactive employee.

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

SAP E-Recruiting and SAP ERP in an I2-B Scenario In scenario I2-B, SAP E-Recruiting runs on one system integrated in an SAP ERP system in which only SAP E-Recruiting is active. Personnel Management is active on another ERP system, independent of the SAP E-Recruiting system.

This integration scenario is identical to the previous I2-A scenario. As SAP ERP HCM exists in the system but is not in use, you must inform SAP E-Recruiting manually that SAP E-Recruiting is to run in an I2-B scenario and not in an I1 scenario.

You do this by creating in the Class Constructor of the class CL_HRRCF_SYSTEM_CHECK an enhancement that sets the attribute IS_STANDALONE to TRUE.

For more information about this, see SAP Note 1147882.

An I1 scenario describes the case where SAP E-Recruiting and HCM are live and integrated on the same system.

integration en

Documents