TREX - Search Talent Management

[Former Member]

Hi All,

I know that there are many threads on the TREX and have looked at all of them and tried some of the things but i still get the error search not available.

We have created all search connector in the admin cockpit and have indexed all of them with no errors. All 32 of them are active. I then ran report ESH_TEST_SEARCH to test the searches. All of the objects templates return results except the following:

HRTMC_AES_DOCUMENTS

HRTMC_AES_ELEMENTS

HRTMC_AES_TEMPLATES

HRTMC_AUTHORITY_VIEW

HRTMC_CENTRALPERSON

HRTMC_FUNC_AREA

HRTMC_JOB

HRTMC_JOB_FAMILY

HRTMC_ORG_UNIT

HRTMC_POSITION

HRTMC_QUALIFICATION

HRTMC_REL_CP_JF_744

HRTMC_REL_CP_Q_032

HRTMC_TALENT_GROUP

For most of these templates I get the following error:

Search Engine Error 29 for DHR310_{HRTMC_FUNC_AREA} : attribute not defined for physical index;index esh:dhr310_dhr310hrtmc_func_area~functional_areayy has no attribute 'objid'.

For the HRTMC_AUTHORITY_VIEW i get no results, it comes back no values and has a yellow traffic light in the Log viewer. In the Job Log in the Admin Cockpit i see the following

31.05.2011 21:54:23 Object connector DHR310_{HRTMC_AUTHORITY_VIEW}: New status: Indexing

31.05.2011 21:54:23 The implementing class does not support the iterator by time interface

31.05.2011 21:54:23 Implementation did not provide any data -> exit indexing

31.05.2011 21:54:23 Object connector DHR310_{HRTMC_AUTHORITY_VIEW}: New status: Active

31.05.2011 21:54:23 Job finished

I also activated BADI HRTMC_AUTHORITY_VIEW_DELTA in the IMG and ran report RPTMC_CREATE_CHANGEPOINT_AUTH. I then scheduled ESH_IX_PROCESS_CHANGE_POINTERS for the HRTMC_AUTHORITY_VIEW, hoping the I would be returned with some results.howver

I do have a TMS linked to several org units via relation 741 and this is returned in the test search HRTMC_REL_S_O_RESP. In addition if I go to a Talent Review Meeting in the portal and click on 'ADD' to select an org unit, the managers of the Org Units that I am related to appear on the list. However as soon as I select any of them, they are added to the participant list but non of the nominated talents appear, i get the following message:

'No nominations are displayed since the search is not available'

for all other searches i get the error 'Search is not available' or 'No Relevant Records Were Found for This Search'

I Also checked SLG1 logs after attempting the searches and got the following errors:

2007 for DHR310_{HRTMC_CENTRALPERSON} : NameServer error: no servers found; IndexId:esh:dhr310_dhr310hrtmc_centralperson~~sap_talent

Exception occurred in program CL_ESH_IF_SEARCH_RESPONSE=====CP, include CL_ESH_IF_SEARCH_RESPONSE=====CM006, row 4

An exception has occurred

29 for DHR310_{HRTMC_CENTRALPERSON} : attribute not defined for physical index;index esh:dhr310_dhr310hrtmc_centralperson~personal_datayy has no attribute 'objid'

Exception occurred in program CL_ESH_IF_SEARCH_RESPONSE=====CP, include CL_ESH_IF_SEARCH_RESPONSE=====CM006, row 4

I also tried creating my own serch request using one of the search templates returning results. In this case i used the HRTMC_REL_CP_TB_743 templates with talent group ID as search field and assigned it to one of the search configurations. I then however got the following error.

The following error text was processed in the system DHR : The ASSERT condition was violated. The error occurred on the application server sivrs106_DHR_00 and in the work process 0 . The termination type was: RABAX_STATE The ABAP call stack was:

Method: GET_AUTHORIZATION_QUERY of program CL_ESH_IF_SEARCH_REQUEST======CP

Method: SEARCH_ONE_CONNECTOR of program CL_ESH_IF_SEARCH_REQUEST======CP

Method: SEARCH of program CL_ESH_IF_SEARCH_REQUEST======CP

Method: CONSTRUCTOR of program CL_HRTMC_SEARCH_REQUEST=======CP

Method: GET_INSTANCE of program CL_HRTMC_SEARCH_REQUEST=======CP

Method: TRIGGER_SIMPLE_SEARCH of program CL_HRTMC_AC_SEARCH============CP

Method: ONACTIONSTART_SEARCH of program /1BCWDY/JUNQ9FJYULV16JASJHWU==CP

Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/JUNQ9FJYULV16JASJHWU==CP

Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP

Method: IF_WDR_ACTION~FIRE of program CL_WDR_ACTION=================

Anyone have any ideas on how i can resolve this.

Apologies for posting such a long thread, just trying to provide full picture.

Regards

Imraan

[lukemarson]

Hi Imraan,

You should be congratulated on a thorough post! What version and revision of TREX are you using? You should use TREX 7.1 revision 16 or higher. You should also review the PA-TM SAP notes for TREX. I would recommend reviewing some of the following (some you might need to come back to later):

u2022 1376055 - ESH_ADM_INDEX_ALL_SC: Exception in step 2: Create

u2022 1384953 - ESH: Error message 'A connection already exists' in cockpit

u2022 1437946 - TMC search: Frequently asked questions

u2022 1441190 - Error in model assignments to logical system

u2022 1457940 - Transporting software components: Error in after-import

u2022 1476894 - Transporting software components: Paths are lost

u2022 1483890 - Importing software components directly to target client

u2022 1492752 - Program to create a join index retroactively

u2022 1502296 - Too few ESH_OM_LOGSYSA entries after creating a connector

u2022 1538688 - Indexing Log: Warning "Object 'nw_esh_tst_auto' not ..."

u2022 1516237 - TMC search: Long runtime for indexing of HRTMC_REL_S_Q_031

u2022 1518396 - Indexes are not filled after TREX conversion

u2022 1520538 - TMC search: Performance for extraction of documents

u2022 1523648 - The search does not find any hits

u2022 1526710 - TMC search: Error during position switch by TMS

u2022 1529878 - Performance of authorization indexing

u2022 1534172 - TREX 7.10: Revision 42

u2022 1536663 - TMC search: Long runtime during indexing HRTMC_REL_SC_JF_FN

u2022 1536656 - Missing search attr for person search in Succession Planning

u2022 1540869 - TMC search authorization indexing with initial user ID

u2022 1541984 - Search connectors are not found

u2022 1542741 - Deleting connections

u2022 1550964 - TMC srch: Qualification srch criteria for CP-Q relationship

u2022 1551029 - TMC: Incorrect authorization check for PA infotypes

u2022 1554061 - TMC search: Error in search fields for job evaluation

u2022 1555950 - Indexing of HRTMC_AUTHORITY_VIEW: Data packages are too big

u2022 1558355 - TMC search: Empls. that have left company in search result

u2022 1560966 - TMC search: Error message when copying search configurations

u2022 1561070 - Termination when saving after deleting system assignments

u2022 1562742 - TMS / Search: Indexing fails with HRTMC_REL_S_MANAGER

u2022 1568563 - TMC search: Error when setting up authorization index

u2022 1567065 - TMC search: Simplifying the authorization indexing

u2022 1575454 - TMC search: Performance during CP indexing

u2022 1584309 - TMC search: Change pointer for newly created org. units

Also, did you follow these steps once TREX was connected?

[/people/luke.marson/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management]

Best regards,

Luke

[Former Member]

Hi Luke,

I've had a look at the notes and most of the notes have not been implemented. I am going to ask basis to implement the notes. Is it necessary to re-index the search connector after implementing the notes.

I have also noticed that non of the Talent Management Structural Authorization profiles have been copied to our dev client.

I have asked basis to copy these. Could this be a factor?

Is it necessary to implement structural authorizations i.e to assign users to authorization profiles. is this a requirement for TREX?

Yes i did follow steps after the connection of TREX.

Regards

Imraan

[lukemarson]

Hi Imraan,

Depending on the note, some manual alterations are required to TREX search connectors. In this case the note specifies if the search object connectors need re-indexing.

The Talent Management structural authorizations profiles are usually only in client 000 and have to be copied if required. This has no effect on the operation of the systems as these profiles are only used if assigned to a user. My understanding is that these aren't used that often during implementations.

There are no requirements for TREX other than the 741 relationship.

Please let us know how you get on with the SAP notes. Please also confirm your TREX version and revision number.

Best regards,

Luke

[Former Member]

Hi Luke,

We are on version 7.10.44.00

Regards

Imraan

[Former Member]

Hi,

We have resolved this issue by applying SAP Note 1526788.

Thanks for the responses.

Regards

Imraan

[lukemarson]

Hi Imraan,

Good news! That's an interesting note for the issue. Deactivate the index usage collector is the solution to this problem - so I'll have to remember that for later.

Best regards,

Luke