EREC: Filtering out locked candidate profiles in the quick search fn

[Former Member]

Hi,

When a candidate registers in SAP e-Recruiting application, they have two option to set their profile status

i.e. 'Locked' and 'Released'.

Locked - Applicant is inactive or not looking for change. So when recruiter does a search, they won't see 'Locked' profiles.

The requirement is that for the quicksearch option the the locked profiles need to be filtered out.

I have tried implementing the BADI - HRRCF00_SEARCH_HIDDEN_INFO method RETRIEVE_HIDDEN_INFORMATION( )

by populating et_hidden_info table for iv_search_task EQ 'quicksearch'. It gives a syntax error "The syntax of your entries in the full text search is incorrect ".

Is there a way for the locked profiles to be filtered out inorder that recruiters don't see the locked candidate profiles?

Thanks for your help!

[former_member131723 · Accepted solution]

I know for quick search there is a recent correction with version 2 of this note 1586770 if using the BADI HRRCF00_SEARCH_HIDDEN_INFO

You can also add the released/locked status TREX attribute (hidden_info.candidate_status.key) for the TREX attributes for the candidate search

[Former Member · Accepted solution]

Hi Sally,

Thanks for your reply.

I have verfied if the correction mentioned in the sap note you've mentioned has been incorporated in the system, and I observe that it has been modified per the note.

I have already added the TREX attributes as below:

ls_hidden_info-ses_attr_name = me->gc_hidden_info_cand_status. ('hidden_info.candidate_status.key')

ls_hidden_info-ses_attr_value = me->gc_cand_status_released. ('RELEASED')

for the iv_search_task EQ 'quicksearch' and appended it to the exp. internal table et_hidden_info.

After this am getting the error message 'The syntax of your entries in the full text search is incorrect'.

Many Thanks,

Wincy

[former_member131723 · Accepted solution]

It was version 2 of this note that has been implemented?

is there any error in SLG1?

[Former Member · Accepted solution]

Hi Sally,

The version 2 of the note has been implemented. I've been informed that there is a bug in the search code in BADI and to hold on until SAP provides a fix to this.

Many thanks,

Wincy