E-Recruiting 600: Problems with TREX

[Former Member]

Hi everybody, i have two problems with TREX and E-Recruiting.

First one is about delta indexing of E-Recruit documents. I know how to schedule a complete indexing for E-Recruiting docs and also i know how to schedule a delta indexing on the Enterprise Portal. How can I schedule a delta index for E-Recruiting docs?

Second one is about Candidate indexing. On TRM there are candidates than doesn't appear on searchs. View them on the TREX index they have status blocked, where can i change that status?

Last one is also about candidate indexing. I executed a complete index manually and some candidates disappear from the inde on TREX admin.

Thank you in advance, Michael

[Former Member · Accepted solution]

At last, everything worked. We wrote a message to SAP, but suddenly everything worked like a charm without modifying anything on the TREX/ECC indexing configuration. I don't know if something changed on the HR side, but definitely it's been working ok for a month so our configuration was ok.

Anyway, thank you very much for your help.

Michael

Edited by: Michael Jones on Aug 5, 2009 11:03 AM

[Former Member]

Hello Michael,

Came across the below two notes.Please check if they can help.

1467411 - Missing candidates in search and dashboard query

1808871 - Common Errors and Troubleshooting guide for SES search
function - E-Recruiting

Please see the section below:

• Section
       A : Search returns no data or incorrect results:

1. 
   First of all, verify which search scenarios are working and check whether
   search is correct for unregistered job search, candidate search,etc, for
   example if there is a problem with the unregistered job search, does the search
   work with a different criteria, e.g if * search does not work, is the job
   posting found with a keyword search?
   
   The search scenarios are as
   follows:
   

   Search with *	SES
   Search without criteria	SES
   Search with criteria	SES
   Search with words	SES
   Search with reference code (Recruiter)	SES
   Search with reference code (Candidate)	Data based (KPRO Search)

   
   
   
   
2. If the search is working in some scenarios but not in others, then please
   check the solution from following wiki page: "No search results
   in a particular service"
3. If a Job posting is not found, check that it has the "X" flag in the
   published field for table T77RCF_INT_PUB (if internal posting) and
   T77RCF_EXT_PUB (external posting).
4. Next, in transaction SLG1, check the error logs to see if there is an error
   when executing the search -  common errors include;
   
   
   • Search masks and templates incorrectly customized.
   • Missing information categories in the search profile.
   • If errors can be seen in SLG1 of this nature then check the report RCF_CHECK_SEARCH_SETTINGS (this provides an overview of the
     search settings and will indicate if there any customizing errors detected for
     the SES search setup)
5. If you see errors in SLG1 when executing the search relating to incorrect
   or missing roles - then please verify the roles in transaction PFCG if
   they relate to the service user and services in SICF, the wiki page Role Assignment
   has more information.
6. For errors when executing registered job search or candidate search in SLG1
   relating to incorrect HR object  - please verify the candidate object is valid
   in table HRP5102 and check if these can be corrected by running HRALXSYNC using
   transaction SE38.
7. The report COM_SE_SEARCH_IIF_TEST can be used to check if the candidate or
   object can be found in the Internal Interface (IIF) in the E-Recruiting backend.
   The following wiki page will give you more information on how  this report works
   and what parameters to set in transaction SE38: COM_SE_SEARCH_IIF_TEST.
8. Finally: if you make any changes to the search profile customizing, then the
   indexes need to be updated, Starting with the IMG step "UPDATE SEARCH PROFILES"
   this job triggers COM_SE_DISPATCHER for a full indexing. This needs to be done
   when assigning any additional fields to a search profile type.  
9. Depending on which business functions you have activated, please also refer
   to the reference section which lists all of the essential notes for SES Search
   relative to the business function and TREX version.
   
   

Regards,

Vidyanand

[jasper_mallinson]

Hi Roman,

We have a similar problem with TREX. We are getting an internal error while doing a search in TRM or Job Search

SLG1 Log

Serious error; see log

The error occurred in program CL_HRRCF_ABSTRACT_CONTROLLER==CM001 line 56

Serious error; see log

The error occurred in program CL_HRRCF_SMG_CONTROLLER=======CM008 line 113

Serious error; see log

The error occurred in program CL_HRRCF_SEARCH_MASK_GROUP====CM009 line 40

Serious error; see log

The error occurred in program CL_HRRCF_SEARCH===============CM00P line 286

Index ID is not defined in table COM_SE_BUSOBJTY

The error occurred in program CL_HRRCF_SEARCH===============CM01C line 47

Could you pls throw some light on this..

[romanweise]

Hi,

could you tell me which release you use? And do you use the old TREX indexing via XML documents and python extentions or are you using SES search? This would help much.

Many Thanks

Roman

[jasper_mallinson]

Hi Roman,

We have a similar problem with TREX. We are getting an internal error while doing a search in TRM or Job Search

SLG1 Log

Serious error; see log

The error occurred in program CL_HRRCF_ABSTRACT_CONTROLLER==CM001 line 56

Serious error; see log

The error occurred in program CL_HRRCF_SMG_CONTROLLER=======CM008 line 113

Serious error; see log

The error occurred in program CL_HRRCF_SEARCH_MASK_GROUP====CM009 line 40

Serious error; see log

The error occurred in program CL_HRRCF_SEARCH===============CM00P line 286

Index ID is not defined in table COM_SE_BUSOBJTY

The error occurred in program CL_HRRCF_SEARCH===============CM01C line 47

Could you pls throw some light on this..

[romanweise]

Hello Michael,

I am not completely sure what you mean with delta indexing for E-recruiting. In general the periodical services get the change pointers for all objects changed since the last run and take care of getting them indexed on TREX. This keeps the index up to date. If for any technical, metaphysical or voodoo reason the index is corrupeted you only can rebuild it by using a complete indexing as long as you use the old TREX interface using xml documents an the python extention on the TREX server. If you already use the SES search interface to TREX which is available since EhP3 there should be a posibility to freeze certain index snapshots to start from when rebuilding the index. As far as I know E-Recruiting saves all change pointers anywhere to reroll the index but I have to admit that I never used this option so far.

TRM search for candidates only finds candidates with relesed profile. This infomation is implemented as the status of the candidate found in IT5102. The profile release inicates that a candidate is willing to be considered for positions he did not apply directly.

There are differen ways to change this information. The candidate has a checkbox on the send container sequnce item (BSP) or send roadmap step (WebDynpro) in the application wizard. Furthermore there is an application on the standard startpage (BSP or WebDynpro) which allows the candidate the user to change this status. To allow recruiters to change the status of certain candidates you can define activities of category statuschange on the candidate object to st relesed and locked status. The recruiter then can chang the status by creating one of the activities on the TRM tab of the candidate overview.

Updating an index can of course result in disappearing of some candidates .If a candidate deregisters for example he is no longer indexed.

I hope this anwsers you questions

Best Regards

Roman Weise

[Former Member]

Thank you for you reply

I meant for keeping the indexes up to date; is it enough to schedule a job incluiding the execution of RFC_PERIODICAL_SERVICES?

The point is our TREX is not indexing all the candidates with their profile released. Besides, we've seen in the IT5102 (table HRP5102) there is more than 1 valid line for each candidate! Is this possible? There's people with the 'Status' value blank, too. It should be 0 (locked),1 or 2 (released), but it's blank...

The situation is a bit strange; we're thinking more about a problem with the E-Recruiting data than a TREX problem.

Thank you in advance,

Michael Jones

[romanweise]

Hello Michael,

the periodical services are e central part of the e-recruiting application. They take care of a lot of stuff. They are needed for processing change pointers to get objects like candidates, requsitions, .. indexed in the TREX, thy take care of publishing publications at their publication date and they have an important role combined with ALE distribution. In addition we often build own periodical services for distributing task or status lists to process participants e.g. a report to managers once a week containing the number of questinairs to fill and a list of positions running out.

A periodical service is technical a class implementing an interface. In IMG under the node SAP E-Recruiting -> Technical Settings -> Periodic Services you find the definition and activation of services. To run them you have to plan the programm RCF_PERIODICAL_SERVICES periodically (evry 5 to 30 minutes).

If you have not run this job yet you should run it once as it will have to process lot of change pointers and only after this initial run is done start planning it regularly.

Assuming the TREX configuration, set up and linking to the e-recruiting system is fine this is all needed to have the TREX up to date. If this is not working check TREX logs and as always when having trouble with e-recruiting the logs in TCode SLG1.

In HRP5102 there can be several lines for each candidate but there should only be one which is valid today. This shoud be the dataset with enddat = Dec, 31st 9999. In the other candidate tables HRP5103,4,5 there can be of course several as a candidate can have more than one education etc.

Having lines with blank status is quite strange as the field is NUMC so a blanc could only be added with hard line updates violating the data consistencies of SAP. This would need additional investigation as it implies someone writing hard on the tables. Are you already productive with the system or are u still in rollout?

Regards

Roman

[Former Member]

Hi Roman,

We knew the program RFC_PERIODICAL_SERVICES was relevant; in fact we were executing it manually; but we didn't know it had such importance and a specific customizing. Thank you

We misunderstood the HRP5102, taking the 'modified by' column as the name of the candidate. Of course, candidates were ok. However, the status column still has no data or '2'. It's strange, because if you try to edit the table manually, it doesn't let you write a '0' but leaves the column with no data. I suppose it's representing data that way, even if it's different than the 'F4' help

We still don't have our candidates when searching@TRM, but it seems it can be solved by customizing the Talent Warehouse Search Profiles...

Of course, we're still in rollout.

Thank you very much,

Michael Jones

[romanweise]

Hello Michael,

please also check SLG1 if it shows any error.

Furthermore ensure that the disk share on the TREX which stores the index has always at least 2GB of free disk space. If this is n0ot fullfilled the TREX is not updating the Index anymore. So you still get a result but only old information.

The 0 or space issue might be an effect of a convert exit. I see the 0 as real 0 in my system but I am not sure if there might be differences depending on the used display technology or the system setting for unicode or non unicode. But I tend to the position that is very difficult to get this broken so it's probably ok ;o).

Keep us updated on your progress it is always interesting to get to know new ways the TREX can mess e-recruiting up.

Kind Regards

Roman

[Former Member]

Hi,

We've followed this blog /people/divya.jain6/blog/2008/07/22/setup-of-search-enginetrex-for-e-recruiting but we still have problems. Our TREX is indexing properly, but when we use TRM to search candidates, we find nothing.

We also found this link http://help.sap.com/erp2005_ehp_04/helpdata/EN/47/139deec7f53125e10000000a1553f7/frameset.htm, which talk about SES Business Objects. It seems it's needed to use this objects so the TREX can index everything. We're trying with the ERC_CAND object. It doesn't have a search interface, so we are developing one. Is this the right path?

We have no errors @ SLG1.

EDIT: We've finished the developing of the interface. TREX is indexing ok the ERC_CAND Business Object, but TRM still finds nothing. We're disappointed, because we thought this could be the solution. It's like TRM didn't know it has to use SES search. Is there any place to configure it? We've found nothing @ customizing

Thank you in advance,

Michael

Edited by: Michael Jones on Jun 17, 2009 5:02 PM

[romanweise]

Hello Michael,

as far as I understood you are trying to use the SES Interface to the TREX.

As I could not find above while flying over your former posts, could you please tell me which E-Recruiting Version with which EhP and on which Support Package you are on? Which Business Functions have been activated? Furthermore do you use standalone or integrated installation?

As the different combinations tend to different errors this would help much.

Kind Regards

Roman

[Former Member]

Hi,

I'd say I'm trying to use E-Recruiting & TREX with or without SES, but it's painful!

We're using SAP ECC 6.0 with SAP_ABA & BASIS SP17, SAP_HR SP43, ERECRUIT 600 SP13, TREX 7.1. No enterprise business functions activated. My installation is integrated.

EDIT: Search@SKPR07 works properly. SES search (using COM_SE_SEARCH_TEST) works too. But searching at TRM returns 0 results.

Thank you very much,

Michael

Edited by: Michael Jones on Jun 18, 2009 6:59 PM

[romanweise]

Hello Michael,

according to your installation the SES search interface to the TREX engine is no option for you. E-recruiting is not supporting this before a business function delivered with EhP3 for E-Recruiting.

So you need to stay with the python extension and the XML indexing documents. The configuration for that is described in 815866 and related notes. Unfortunately this interface is not the most stable thing sap ever developed which is one of the main reasons sap changes to the SES interface.

So first of all you should try to get your configuration clear. Deactivate everything related to SES and do the settings described within the notes. Also search SAPNET for troubleshooting + TREX in component PA-ER.

Be aware that the python extensions do not work together with other indexing stuff. So you need a standalone TREX for E-Recruiting. Using the same TREX engine for indexing on other applications can lead to any result.

Be sure to rebuild the indexes once you finished configuration.

A step away fron direct TREX problems. In general I do not recomment to use SAP E-Recruiting in an integrated installation up to release 600 EhP3. I have no Idea if it will be better with EhP4 but I will not trust any documentation I will judge on my own.

One of the central issues of this position is the structural authorization topic. Internal candidates are linked to an employee Id. If you do not have the overall structural autorization you won't see all candidates. This could be a reason why you do not see the results. This is a realy nasty issue on the rollout. If you have structural authorizations implemented a manager usually sees his department. But when someone applies on an internal vacancy this person is usually not a member of his department so he has no autorization to see the candidate. I think you get the point.

I hope this helps you with your investigations.

Kind regards

Roman

[former_member566286]

Hi Michael,

I have the same error your, wanted to know what was the solution.

I'm using:

ERECRUIT 600 SP19 (SAPK-60019INERECRUIT)

Thanks for your support

Regards,

[Former Member]

Hi All,

For sizing purpose of TREX we are consider below specifications so that client can confirm us. Please provide ur inputs for items or considerations for sizing I might have missed as I am first timer.

- No. Of hits per one min. (peak time)

Ans: A) approx. >99999 B) <99999

- No. Of fields on the basis of which search would provide output.

Ans: A) 10 B) 15

- Type of Searches

Ans: A) Structured B) Unstructured

Thanks in advance!

Regards