Kontakt

Ansicht
Dokumentation

ERC_ECC_INTEGRATION - Software Runs on One Instance

ERC_ECC_INTEGRATION - Software Runs on One Instance

Vendor Master (General Section)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

As of Release 300, SAP E-Recruiting is an add-on for SAP ERP Central Component (SAP ECC). This enables you to run SAP E-Recruiting and the SAP ECC components on the same instance. In this way, some of the candidate's data in E-Recruiting can be reconciled with the employee's data in the HR system.

The HR system is the main system for the following employee data. The data of an employee is processed using Personnel Management (personnel actions, master data). Changes to the data in the following infotypes are then reconciled with SAP E-Recruiting.

  • Actions (0000)
  • Organizational Assignment (0001)
  • Personal Data (0002)
  • Addresses (0006)
  • Communication (0105)
  • Qualifications (1001, subtype 032) (Note: Available as of Release 600)

Synchronous Reconciliation of Data between HR Master Data and E-Recruiting Data

As of Release 600, the data reconciliation between HR master data and SAP E-Recruiting in the standard system has changed from asynchronous to synchronous.

The data is reconciled synchronously using the BAdI implementation (BAdI = HRSYNC_P, BAdI implementation = CONV_HR_DATA_TO_EREC (Conversion of Employee's HR Data in E-Recruiting)). The BAdI implementation is delivered as inactive in the standard system. Activate the BAdI implementation using the transaction SE18 (BAdI Builder).

The Qualifications data is reconciled synchronously using the BAdI implementation (BAdI = HRBAS00INFTY, BAdI implementation = HRRCF00_STORE_HRQUAL, (Updating of HR Qualifications in E-Recruiting Infotype 5105)). The BAdI implementation is delivered as active in the standard system.

With the synchronization, the data is written automatically to SAP E-Recruiting after changes have been made using HR standard transactions (for example, PA30, PA40, maintaining the qualification profile).

Note

If you use the detached IT framework (for example, Employee Self-Service or HR Administrative Services), you must activate the BAdI implementation HRRCF00_HR2EREC_NEW_IFRMWK of the BAdI definition HRPAD00INFTYBL (Enhancement of Business Logic of Standard Infotypes). In the Customizing for Personnel Administration, choose Customizing Procedures -> Infotypes -> Infotypes in Detached Infotype Framework -> Enhancements to Business Logic and Updating -> BAdI: Enhancement of Business Logic of Standard Infotypes for the Customizing activity with which you can activate the BAdI implementation.

You also have to activate the implementation HR_INTEGAT_TO_EREC of the BAdI HRPAD00INFTY.

For more information, see SAP Note 997181.

Note

Ensure that you no longer have the obselete service ERP_EE_TO_INT_CAND (reconciling of employee's HR data with candidate data for E-Recruiting) set up as a periodic service (see Define Periodic Services).
Instead, set up the reconciliation of data in each case as described above.

Repair Scenario: Asynchronous Reconciliation of Data between HR Master Data and E-Recruiting Data

The relevant HR master data is reconciled using the HR_SYNC_PERSON report (as of Release 300) or the HRALXSYNC report (as of Release 600). These reports are used for repair scenarios, for example, if there have been problems with the synchronous reconciliation (personnel number locked) or if you have just installed E-Recruiting and want to reconcile the data.

Note

The report RCF_CREATE_USER (Create Internal Users and Candidates for SAP E-Recruiting) may not be used in the integrated scenario.

There is no point in using this report as the users are created using standard transactions (SU01) and the required E-Recruiting-specific data (such as Candidate) is added with the HR_SYNC_PERSON or HRALXSYNC report.

Instead, use the HR standard transactions PA30 and PA40.

For information about the prerequisites for using SAP E-Recruiting and SAP ECC on one instance, see SAP Note 830591.

Sample scenario 1: Hiring of external candidate

The registration of an external candidate (object type NA) results in the following objects being created in E-Recruiting and linked to each other (infotype 1001):

  • Candidate, object type NA, object ID 4711
  • Central person, object type CP, object ID 4711
  • Business partner, object type BP, object ID 4711

When the external candidate is hired using transaction PA48, the relevant hiring action is performed. The following objects are created using the hiring action:

  • Person, object type P, object ID 0815
  • Central person, object type CP, object ID 0815
  • Business partner, object type BP, object ID 0815

The candidate object in E-Recruiting must be assigned to the personnel number using synchronization. This is done using the aforementioned BAdI implementation, whereby NA 4711 is linked with the central person CP 0815 and the link to the object CP4711 is obsolete.

Sample scenario 2: Hiring a new employee without prior reference to E-Recruiting

When the external candidate is hired using transaction PA48, the relevant hiring action is performed. The following objects are created using the hiring action:

  • Person, object type P, object ID 0815
  • Central person, object type CP, object ID 0815
  • Business partner, object type BP, object ID 0815

The relevant candidate object in E-Recruiting must be created and assigned to the personnel number through synchronization. This is done using the aforementioned BAdI implementation, whereby a new candidate object NA 4711 is linked with the central person CP 0815.






CL_GUI_FRONTEND_SERVICES - Frontend Services   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 7208 Date: 20240523 Time: 184443     sap01-206 ( 134 ms )