Common TREX issues

Here are some common TREX issues and their resolutions.

I get no search results but TREX is setup properly

If your user does not have a 741 relationship between it’s position (your user must be linked to a person with an organizational assignment) and an organization unit – your Area of Responsibility (AOR) – then you will get no search results in TREX.  It is also recommended that you have the Talent Management Specialist role (SAP_TMC_TALENT_MANA_SPECIALIST), or equivalent authorizations.

An Area of Responsibility (AOR) has been assigned but I get no hits in the search and I definitely have an organizational assignment

Change pointers for authorizations are not generated in real-time like with standard indexes and require the report RPTMC_CREATE_CHANGEPOINT_AUTH to be run.  Even if scheduled in SM36, the minimum interval at which the report can run is 1 hour.  Therefore, when a new assignment has been made it is recommended to run this report for that user account.

I get results, but the names are blank

This issue occurs when Business Partner objects (object type BP) do not exist or are not synchronized for each Central Person object (object type CP).  See this blog on Business Partner objects in SAP HCM Talent Management.

TREX has been indexed, but there is missing data in the indexes

When indexing TREX it uses the authorizations of the user that triggered the indexing.  Therefore the user that triggers the indexing should have adequate authorization to access all data required in the TREX searches.

I’m a Talent Management Specialist and I can find myself in the search

Implement SAP Note 1604592.

Is TREX required for SAP Talent Visualization by Nakisa (STVN)?

STVN is integrated with Talent Management and Talent Development and leverages the same data model, authorization concept, and search.  The search in Talent Management and Talent Development uses TREX and so, indirectly, STVN does require TREX for searching.

I have made changes to the Talent Management customizing, but the new values are not considered in the search

Search connectors for customizing tables (Technical Objects) do not have change pointers created and must be re-indexed when customizing tables are updated.  See SAP Note 1437946 for details of the Technical Objects that require indexing on demand.

Delta indexing does not work for authorizations

By default BAdI implementation HRTMC_AUTHORITY_VIEW is enabled, but the BAdI for delta indexing (HRTMC_AUTHORITY_VIEW_DELTA) is disabled.  Often enabling the HRTMC_AUTHORITY_VIEW_DELTA implementation requires a manual activity.  To enable it, see Enabling BadI HRTMC_AUTHORITY_VIEW_DELTA .

The indexing of HRTMC_CENTRALPERSON runs endlessly

Implement SAP Note 1653152.