applies to trex configuration

8/13/2019 Applies to Trex Configuration

1/9

Applies to:

SAP E-Recruiting Enhancement pack 4 Service Pack 7 onwards

TREX Version 7.10.18.0 ( = TREX 7.1 with revision 18)

Activated Business Function HCM_ERC_CI_3

Introduction:This document explains the new search functionality available in the SAP E-Recruiting module (Ehp4) subject to

the system requirements stated above and all the necessary steps to upgrade the search functionality from older

versions already using the SES search. If you are implementing SAP E-Recruiting fresh, please look for my other

blog (coming soon). Clients used to ask me why SAP makes it so complex even to configure a simple

functionality and I used to tell them thats what you get when you buy packagedsoftware. They have to think of

several scenarios that their customers may use it. I should say they made it easier with Enhancement packages.

But the downside is unless you had experience with all the enhancement packs particularly the changes that

search had gone through, you may miss some important information hidden in the release notes. So I thought I

will write a blog to explain this new feature available after you activate the enhancement switch.

Background:

In enhancement pack 3 using SES search, all the structured data ( infotypes) were indexed through SES and theunstructured data (attachments) were indexed through KPro. I have to tell that there were lots of issues in

configuring the KPro indexes and to make the full text search on attachments work. Also you have to maintain the

indexes separately apart from the ses indexes.

Current: (Ehp4 +)

Now the structured and unstructured data is no longer separated and hence the KPro index is obsolete. You

dont need to maintain the indexes in SKPR07. Also the performance of the search applications has increased

greatly because of this comprehensive search. I havent done any benchmark study on this, just what I observed.

Steps:

1. Stop the periodical services background job. Go to transaction SM37 and using extended search, search for

batch job with program name RCF_PERIODICAL_SERVICES. Then change the status of the batch job from

released to scheduled via the menu path Job->Released to Scheduled2. Deactivate KPRO Indexing. Go to transaction SPRO and uncheck the indexing for Document Area HR_KW.

Please make sure you add this to the cutover plan as you have to perform this task in each environment ( Dev,

QA, and Production)
http://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72883/sessearch1.jpg


2/9

3. Delete the entry INDEX_DOCUMENTS from the table via the IMG activity as shown below,
http://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72885/sessearch3.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72884/sessearch2.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72885/sessearch3.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72884/sessearch2.jpg


3/9

4. Delete all marked documents via the transaction SKPR07.


4/9

5. Change the logon procedure for the content server ICF service via the transaction SICF to Logon Data

Required


5/9

6. Delete Indexes of existing SES Business Objects via transaction SES_ADMIN.

7. Restart the TREX server.

8. Create the indexes of SES business objects via transaction SES_ADMIN. Please make sure you log on to the

system in English before you create indexes. Create the following indexes via the menu path Index-

>Create/Activate Indexes:


6/9

9. Execute the program RCF_SES_JOIN_INDEX_CREATE. Please make sure you logged in English before you

execute this program.

10. Trigger full indexing of all SES business objects.
http://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72893/sessearch11.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72894/sessearch12.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72893/sessearch11.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72892/sessearch10.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72894/sessearch12.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72893/sessearch11.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72892/sessearch10.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72894/sessearch12.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72893/sessearch11.jpghttp://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72892/sessearch10.jpg


7/9

11. Delete the index category via transaction SRMO.

12. Clear all table entries related to KPRO indexes via transaction SKPR07.


8/9

If you get any errors, please delete all the inactive index categories manually.

13. Release the rcf_periodical_services batch job which was scheduled in step 1.
http://scn.sap.com/servlet/JiveServlet/showImage/38-58053-72897/sessearch16.jpg


9/9

1. Depends if you use WD or BSP but usually you generate it:

1. WD: hrrcf_a_startpage_ext_cand -> SE80 -> WD application -> you see the generated URL

2. BSP: hrrcf_start_ext -> report RCF_GENERATE_URL to generate the URLs

2. You have to make sure all SICF services are configured correctly. For WD you'll find the settings described in the

documentation ofIMG step -> Technical Settings -> User Interfaces -> Candidate -> Front-End Candidate -> Specify E-

Recruiting Services (Web Dynpro ABAP).

3. If a candidate registers, he/she sets the userid and password ... so they should know that already. If you want to add that in

the confirmation letter which is sent automatically you can copy the functionality from the 'password forgotten' smartform

(HRRCF_CS_IT_EXA_NEW_PASSWORD).

applies to trex configuration

Documents