Ansicht
Dokumentation

RH_SFI_TRIGGER_JOB_REQUISITION - Create and Update Job Requisitions in SuccessFactors

CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Purpose

In the SAP ERP system, this report creates new records of the infotype SFSF Job Requisition (1107) for positions that need to be staffed, or changes existing infotype records. Based on the information stored in this infotype, it transfers data from the SAP ERP system to SuccessFactors Business Execution (SuccessFactors BizX) so that job requisitions are created there for the positions. If the positions are staffed in the SAP ERP system, the report also transfers this information to SuccessFactors BizX so that the associated job requisitions are closed there.

Integration

Prerequisites

• You have activated the data transfer and the creation of job requisitions for positions to be staffed in SuccessFactors BizX. To do so, in Customizing for the integration add-on, under Integration Scenario for Recruiting Data -> Activate Additional Functions you have set the parameter JOB_REQUISITION_INTEGR_ACTIVE to X.

• You have defined the package size for the data transfer. To do so, in Customizing for the integration add-on, under Basic Settings -> Settings for Middleware -> Define Package Size for Transferring Recruiting Data, you have defined a corresponding value for the parameter REQUISITIONS_PACKAGE_SIZE.

Recommendation

We recommend that you do not choose too large a package size so that not too many positions are locked for changes at the same time (see the "Features" section).

• You have defined how the ID of the template for job requisitions from SuccessFactors BizX is to be determined for positions to be staffed. To do so, in Customizing for the integration add-on, under Integration Scenario for Recruiting Data -> Transfer of Job Requisition Data from SAP ERP to SuccessFactors BizX, you have performed the activity BAdI: Determination of Job Requisition Template from SFSF.

• You have defined how the SAP ERP fields are to be mapped to the SuccessFactors BizX fields. To do so, in Customizing for the integration add-on, under Integration Scenario for Recruiting Data, you have performed the following activities:

• Map SuccessFactors BizX Fields and SAP ERP Fields to Each Other

• Transfer of Job Requisition Data from SAP ERP to SuccessFactors BizX -> BAdI: Mapping of SAP ERP Infotype Fields to SFSF Fields

• Transfer of Job Requisition Data from SAP ERP to SuccessFactors BizX -> BAdI: Mapping of ERP Infotype Fields to SFSF Fields: Change of Mapping Result.

Features

In each run, the report proceeds as follows:

1. It evaluates the change pointer table for job requisitions (table HRSFI_D_RCT_REQ) to generate records of the infotype SFSF Job Requisition (1107).

Note

In the change pointer table, the SAP ERP system stores a change pointer if a position is to be staffed and therefore a job requisition needs to be created in SuccessFactors BizX.

If you use the infotype Vacancy (1007) in your SAP ERP system, the change pointers are triggered when this infotype is created or changed. In this case, the system reflects all changes to the infotype Vacancy in corresponding records of the infotype SFSF Job Requisition.

If you do not use the infotype Vacancy, the HR Administrator needs to create and edit the records of the infotype SFSF Job Requisitionmanually. To do so, in the Organization and Staffing applications (transactions PPOCE, PPOME, PPOSE), under Details for Position, he or she uses the SFSF Job Requisition tab.

When evaluating the change pointer, the report proceeds as follows:

1. It processes all change pointers for a position together in the order of their date of origin. As of the point at which the report processes the first change pointer, it locks the position so that it cannot be changed. If it cannot lock the position so that it cannot be changed while processing the first change pointer, it skips all other change pointers for this position. It reattempts to process the data for this position in the next run.
2. If new change pointers are added for a position when converting the change pointers to infotype records, the report processes these in the next run.
3. The report deletes all change pointers that it has evaluated successfully from the table HRSFI_D_RCT_REQ.
4. It saves the records of the infotype SFSF Job Requisition to the database.

The report determines the data that needs to be transferred to SuccessFactors BizX. The report proceeds as follows:

1. It reads all relevant data records from the database table for the infotype 1107 (table HRP1107) that have the subtype Open Job Requisition (0001).

For new infotype records, it also uses the Business Add-In (BAdI) Determination of Job Requisition Template from SFSF (HRSFI_B_TEMPLATE_DETERMINATION) to determine the ID of the associated template for job requisitions from SuccessFactors BizX.

It sorts the data records by the template for job requisitions and the relevant positions.

1. For each data record that it has determined in this way, it calculates a new image for the table HRP1107 and stores this in the buffer.
2. It checks whether the transfer status in the infotype SFSF Job Requisition is set to Error. If so, the report needs to transfer this data again.
3. It checks whether the transfer status in the infotype SFSF Job Requisition is set to Forced Transfer or Postponed Transfer. If so, the report needs to transfer this data.
4. It checks whether the status of the job requisition stored in the infotype SFSF Job Requisition as it was most recently successfully transferred from the SAP ERP system to SuccessFactors BizX (field STATUS) is different from the status that is transferred during the next data transfer from the SAP ERP system to SuccessFactors BizX (field TARGET_STATUS). If so and if the point at which data is transferred is within the validity period of the infotype record, the report needs to transfer this data.

Example

The status Open is stored in the STATUS field and the status Closed is stored in the TARGET_STATUS field. This means that the position has been staffed in the SAP ERP system. This information needs to be transferred to SuccessFactors BizX so that the job requisition is closed there.

1. It checks whether a delta data transfer is necessary. To do so, it compares the new image for the data record that is stored in the buffer with the existing image that is stored in the database table. If there are differences and the point at which data is transferred is within the validity period of the infotype record, the report needs to transfer this data.

The report transfers the data to SuccessFactors BizX in packages. The report proceeds as follows:

1. For each data record to be transferred, based on the ID of the template for job requisitions from Customizing, the report determines the fields and field contents to be transferred and bundles them in packages.

In doing so, it adds the data records to the same package until another ID is assigned for job requisitions or until the maximum package size has been reached.

1. As soon as a package has been completed, the report uses the Web service SFSFGenericUpsertRequestConfirmation_Out to transfer the package to SuccessFactors BizX, where it triggers the creation, change, or closing of job requisitions. For newly created job requisitions, the SuccessFactors BizX system sends the ID of the job requisition as a response.
2. If an exception is triggered during the data transfer, the report sets the status of the data transfer to Error for all data records of the package in the infotype SFSF Job Requisition and defines a handle for the application log. It also stores corresponding error messages temporarily in the report log and permanently in the application log.
3. It saves the image defined internally for all affected data records definitively in the table HRP1107 per package. In the new infotype records, the report stores the ID of the job requisition transferred from SuccessFactors BizX. It updates the status in all infotype records.
4. It removes the lock for all positions in the package.

When all packages have been transferred, the report generates statistics and saves them in the report log and in the application log. It also saves all temporarily stored error messages definitively to the report log.

Selection

Specify the language in which texts are to be transferred to SuccessFactors BizX. The report uses this language when determining the content for all text fields that are contained in the data transfer.

Standard Variants

Output

The system displays a log that informs you of the number of positions for which the data has been successfully transferred and the number for which the data transfer failed. If errors occurred, the positions in question are listed with relevant error messages. Additionally, all job requisitions that have been created and changed successfully are listed.

Activities

1. Schedule this report as a regular background job.
2. After each run, check the messages in the report log or in the application logs (see Evaluate Application Logs for Creating/Updating Job Requisitions in SFSF).

Example

Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 11857 Date: 20240601 Time: 195415     sap01-206 ( 220 ms )