Ansicht
Dokumentation

ERC_BADI_DYNAMIC - BAdI: Dynamic Determination of Jump Destinations at Runtime

PERFORM Short Reference   General Material Data  
This documentation is copyright by SAP AG.

In this Customizing activity, you can use the BAdI Dynamic Determination of Jump Destinations at Runtime (RS_BBS_BADI_DYNAMIC) to enhance dynamically the context menu for the jump destinations from queries.

In the standard system, we deliver the implementation Dynamic Determination of Jump Destinations in SAP E-Recruiting at Runtime (HRRCF_RS_BBS_BADI_DYNAMIC).

The implementation of the BAdI enables the user to navigate from the context menu of the query to the candidate profile, the requisition maintenance, and the data overview of the requisition. The system calls the BAdI implementation from the query. If the query does not contain a candidate (0CANDIDATE) or requisition (0REQUI), calling the implementation has no effect.

The implementation uses the following methods:

• GET_TARGETS

The method checks the information of the selected rows of a query and provides the suitable jump destinations. The candidate ID is saved in a class variable.

If the field 0CANDIDATE exists, the method adds the jump destination Candidate Profile.

If the field 0REQUI exists, the method checks whether the user is allowed to display the data overview for the requisition (value REQ_DOVR in the field RCF_VIEW of the authorization object P_RCF_VIEW). If the authorization exists, the following steps are executed:

• The requisition ID is saved in a class variable.

• The method adds the jump destination Requisition Overview.

• The method checks whether the user is the lead recruiter for the requisition. In this case, the method also adds the jump destination Requisition Maintenance.

• CALL_URL

The method creates the URL to be called and fills the parameters of the jump destination if the user calls the corresponding jump destination in the context menu.

• Jump destination Candidate Profile

Depending on whether the user is authorized to maintain the candidate profile (authorization object P_RCF_POOL, field RCF_POOL, value CAND_MAIN), the method creates a URL to either edit the candidate profile (application ERC_A_CAND_OVERVIEW) or just display the candidate profile (application ERC_A_CAND_OVERVIEW_DISPLAY).

• Jump destination Requisition Maintenance

The method creates the URL for application ERC_A_REQ_MGNT in change mode.

• Jump destination Requisition Overview

The method creates the URL for application ERC_A_DATAOVERVIEW.

To include customer-defined Web Dynpro application configurations, you have to store the configurations in the following parameters in the method IF_RS_BBS_BADI_HANDLER_DYNAMIC~CALL_URL: lc_cand_profile_conf, lc_cand_profile_dis_conf, lc_data_overview_conf, lc_req_maintenance_conf.

For information about the BAdI, see the documentation for the RS_BBS_BADI_DYNAMIC BAdI.

In the standard system, we deliver the implementation HRRCF_RS_BBS_BADI_DYNAMIC as inactive.

Activate the implementation HRRCF_RS_BBS_BADI_DYNAMIC or create and activate your own implementation.

PERFORM Short Reference   General Material Data  
This documentation is copyright by SAP AG.

Length: 4040 Date: 20240523 Time: 221354     sap01-206 ( 64 ms )