Talent Management TREX and Enterprise Search

Hi All,
in the area of talent management I try to use the TREX search functionality. I have two problems:
1) For Connector HRTMC_AES_DOCUMETS no indexes are available although I started indexing many times. Other Connectors have active indexes. Appraisal documents exist in the system. The indexing and search for hrtmc_aes_templates are successful.
2) How does the connector hrtmc structural authority work. If I do a search for my username on this connector I get a result. If I do a search for a colleagues username on the same connector I get no result. If this colleague wants to search for e.g. a central person he gets no result. How can I fill up the index for struct authorization with the colleagues username?
many thanks for answers and have a nice day
Martin

Hi RD,
the TREX you will need for this will be specific to HCM and called via HCM's own strategy in ECC 6.0. This - for all I know - should be through AS ABAP for indexing and AS Java for searching.
This should have nothing to do with the Portal's access to TREX, as the functionality is HCM's, even if provided to Portal in an iView. For the specifics, please check your HCM Master Guide and other documentation and/or discuss with your technical consultant for ECC 6.0.
Best, Karsten

Similar Messages

Talent Management - Talent Search and Enterprise Search

Hi All,
We are on ECC 6, Portal 7 SP3.
We are using Talent Management Business Package. Under Talent Management-> Talent Information, there is an iView called Talent Search(which is based on the Webdynpro ABAP "hrtmc_search").
For this Search functionality I have read that SAP Netweaver Enterprise Search is needed.
My question is:
1. Is TREX required for Talent Search. I've read that it can be integrated with Enterprise Search. Please note that we are not using KM and Collaboration.
2. Is it necessary to integrate AS Java with Enterprise Search since it will only be used for Talent Search iView which is in any case a webdynpro abap application.
So in this case Enterprise Search will only be integrated with AS ABAP / ERP system - Is this assumption correct.
Your input and help is much appreciated..
RD

Hi RD,
the TREX you will need for this will be specific to HCM and called via HCM's own strategy in ECC 6.0. This - for all I know - should be through AS ABAP for indexing and AS Java for searching.
This should have nothing to do with the Portal's access to TREX, as the functionality is HCM's, even if provided to Portal in an iView. For the specifics, please check your HCM Master Guide and other documentation and/or discuss with your technical consultant for ECC 6.0.
Best, Karsten

Integration of Oracle RDF and Enterprise Search

Hi,
Has anyone tried integrating Enterprise Search with the new RDF feature to enable true semantic search?

It would be interesting to hear from people who have tried this in an application.
As an FYI, using RDF query capabilities in Oracle, simple PL/SQL code can be written to do this. Consider search based on a query term X. SDO_RDF_MATCH can be used to find all terms related to X in a given ontology/RDF data set. All these terms can then be used in the 'Contains' operator that is part of Oracle Text, to find all documents in a table that contain any of those terms. We have some sample code to do this, if you are interested write to me at melliyal <dot> annamalai <at> oracle <dot> com. Tighter integration is being planned in a future release as well.
RDF queries can be also combined with other relational queries. An example in Oracle of simple SQL to combine querying RDF with a relational query is as follows:
SELECT emp1.name, emp1.salary
FROM emp1, TABLE(SDO_RDF_MATCH(
'(?name :fatherOf :Matt)',
SDO_RDF_Models('family'),
null,
SDO_RDF_Aliases(SDO_RDF_Alias('','http://www.example.org/family/')),
null)) t where emp1.name=t.name;
The father of Matt is found by querying the family model (represented using RDF) using SDO_RDF_MATCH, and his salary is found out by doing a join with the table emp. Since the output of SDO_RDF_MATCH is a table, it can be easily joined with other relational data.

E-Recruiting TREX and fuzzy search

Hello,
is fuzzy search available for the e-Recruiting module. We are using TREX 7.0 and e-Recruiting 6.0.
If that functionality is available, how does it exactly work and is it customizable?
thanks
Koen

Hi Guys
Sorry to jump on this thread with nothing to add except my problem.
We are currently in the process of implementing E-Recruitment 3.0 as an extension to ECC 5. I have configured the system and have been doing some unit testing, and have found that when I
- try to "Apply Directly" in tab "Career and Job". If I enter the reference details of the specific job it finds the specific. Or if I leave the input field blank and hit the search button, it returns all jobs posted. However, if I try using a the "Search for Jobs" link option, I get a consistent error "An internal error occurred. Please try again later"
When I check transaction SLG1.....and the error log says the termination occured in a program called CL_HRRCF_ABDTRACT_CONTROLLER==CM001 line 56 and CL_HRRCF_SEARCH_MASK_GROUP====CM00M line 15
Same thing happens when searching for candidates to assign requisitions to.
Has anyone come across this prolem before? Any help will be greatly appreciated, as we have a tight deadline.
Cheers

Is TREX mandatory for Talent Management?

Dear Experts,
Is TREX a mandatory component for Talent Management? It's because I am having issue when I click "Search" in Talent Management Specialist Launchpad, telling me "Error occurred during the search; contact your system administrator".
And it seems to me that TREX supports only LINUX and MaxDB, which is totally out of our company's landscape.
Thanks,
Steven

Hi Steven,
TREX is the search engine itself. That means Talent management is using enterprise search and enterprise search uses TREX to perform searches and store data.
Enterprise Search is part of SAP Netweaver ABAP ( also called embedded search ). Enterprise search is responsible to index data from HR to TREX and is responsible to redirect search requests from Talent management to TREX and put back the results back to the UI. It also provides tools to maintain and administer the data models.
So Enterprise Search is available on your Netweaver ABAP system. But ES uses TREX. That means if you want to get ES up and running you need TREX. (normaly installed on a different box and connexted by RFC to the Netweaver System)
hope that helps.
Martin Hastik

TREX vs Enetrprise Search - Talent Management

Hi,
We are implementing Talent Management and would like to find out what do we require for the enabling search functionality.
Do we require TREX or Enterprise search?
We currently have TREX version 7.0 installed and not Enterprise search. What is the difference between Enterprise search and TREX?
Please can someone advise?
Regards
Imraan

Hi Imraan,
TREX is the engine that runs the Enterprise Search that you will use in Talent Management. You need to install TREX on a dedicated server and connect it via RFC to SAP. Then you need to enable the business function ENTERPRISE_SEARCH in SFW5 and activate the ESH cockpit service in SICF. Then you need to create and index your search object connectors. You can use this guide for that:
[/people/luke.marson/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management|/people/luke.marson/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management]
Good luck!
Luke

PLM 7 and Netweaver Enterprise Search

We installed PLM 7.0. We also had an existing TREX server and we set that up to do indexing in ABAP. Now we have a requirement to use PLM UI on the portal and we need the search results to display there. All the docs I have read are basically saying we have to use Netweaver Entrprise Search for any search to work within the portal. Can anyone confirm this? Or maybe does anyone know if its possible to display search results in the portal just using TREX and embedded search.
Any suggestions are greatly appreciated. Thanks for your help in advance.

HI Storm,
We are in the same decision making for moving from TREX 7.0 to 7.1 with Enterprise Search Functionality as we are planning to go for SAP PLM 7.0.
We have gone thru no of documents & presentation which suggest to go for TREX 7.1 for SAP PLM 7.0 (which is access able thru EP or using the NWBC) to take advantage of the Enterprise search functionality.
you can reffer to following notes
SAP Note 1164979
SAP Note 1266024
SAP Note 1249465
thanks
john
Edited by: johnpp on Feb 12, 2011 10:43 AM

TREX documentation - Embedded Search

Hi everyone,
We are implemeting TREX on SAP CRM 7.
I am looking for some customizing documents on SAP sites but cannot really understand what the difference between TREX, Embedded Search and Enterprise Search. Are those different functionnalities? Are they dependant of TREX implementation?
Any tips about TREX/CRM will be appreciated,
Regards,
Anaïs

Hi Anais,
SAP Enterprise Search provides unified, comprehensive, and secure real-time access to enterprise data and information from within and outside of a company.
the Enterprise Search enables a centralized search access to all sources, i.e. users can enter their search requests and receive the search results through a single browser-based user interface (Search UI).
In TREX search, each source has a separate user interface.
To configure TREX in SAP CRM or Solman please find below link.
Full-Text Search with TREX - SAP IT Service Management on SAP Solution Manager - SCN Wiki
If any concern in configuring Software Agent Framework (SAF), please let me know.
You can also refer below document:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80d3c626-b9f0-2d10-b3a5-e2e7582f3449?overridelayout=true&quicklink=index
Thanks,
Vikas.

Talent Management Grid

Hello Experts,
We are currently implementing Talent Managment Ehp6 and Nakisa 4.0. I have a couple of questions
1) I've researched several SCN posts and blogs about how the Performance/Potential grid has to be a 5,6,9 or 15 box grid and that the values (scales) used in performance must also be used in the talent mgmt grid. When we implemented Performance Management (Ehp4) we used a 20 value scale (1-5 with .25 gradients in between). I would just like to clarify that with everything I have read the Grid in Talent Mgmt and Nakisa will not support this large of a scale. That there isn't any BADI or Enhancement that we can use? It seems like we will have to reduce our scale in Performance to be able to use it in Talent Management/Nakisa. Is that correct?
2) I'm a bit confused about the Writeback functionality with Talent Management and Nakisa. I understand that the Talent Mgmt has their own infotypes (i.e. Potential and Performance) and a Manager or TMS can change the potential/performance in the grid during a Talent Meeting. I'm trying to understand how Talent Mgmt updates Nakisa when these ratings get changed? Or does the TMS and Manager have to change the ratings in both places since Nakisa also uses a grid? Also what happens when you move from a performance template in one year to a performance tempalte in the next year? Does the data save or does it get replaced?
Any assistance or clarification would be much appreciated
Sarah

Luke,
Thank you for taking the time to reply to my questions, I appreciate it.
In regards to the peformance scale we didn't go the PMP route, we went with the Flexible. When I go to the template in the appraisal catalog and try to add the Follow-up BAdI under the enhancement tab it gives me the information below :
"Note
Do not use the BAdI implementation for appraisal templates that you created using the transaction Appraisal Template Catalog (PHAP_CATALOG).
After you have completed an appraisal, the system copies the potential value and performance value to the Potential (7408) and Performance (7409) infotypes that are relevant for the talent review meeting.
The BAdI implementation can only be implemented with an appraisal template of type Performance Management that was created in the Customizing activity Configure Form for Performance Management Process since the appraisal values of the potential assessment and performance assessment are expected to be in certain places in the appraisal template or appraisal document."
Reading this I took this note to mean that if we created a Flexible Appraisal Template that I create via PHAP_CATALOG_PA that I could not use these follow-up BAdIs. That you can only use this follow-up BAdI if you created a form/template using the PMP process.
Am I understanding this correctly? Can you not use the Calibration Grid if you created a template in the catalog using the Flexible templates? In our performance appraisal we don't use the "Final Appraisal" column for our final performance rating. We created a custom column that stores the final rating.
Thanks again
Sarah

JSF managed beans Vs Enterprise beans

Hi friends,
what are the advantages/disadvantages of using enterprise beans/ JSF managed beans over JSF managed beans/Enterprise beans
regards
san

The primary difference between managed bean and enterprise bean is : enterprise bean will avail all the services provided by EJB container. where as managed bean cant avail all these.

TREX - Search Talent Management

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 DHR310HRTMC_FUNC_AREA : attribute not defined for physical index;index esh:dhr310dhr310hrtmc_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 DHR310HRTMC_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 DHR310HRTMC_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 DHR310HRTMC_CENTRALPERSON : NameServer error: no servers found; IndexId:esh:dhr310dhr310hrtmc_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 DHR310HRTMC_CENTRALPERSON : attribute not defined for physical index;index esh:dhr310dhr310hrtmc_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

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

Talent Management - TM - Trex 7.1 - Delta Indexing

luke.....are you out there??
congrats on your blog being featured right on the SDN homepage... very nice...
http://scn.sap.com/community/erp/hcm/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management
and congrats to Chris on his first two excellent blogs....
http://scn.sap.com/people/chris.mcnarney/blog/2010/08/26/whats-included-with-the-predefined-performance-management-process
http://scn.sap.com/people/chris.mcnarney/blog/2010/09/09/whats-included-with-the-predefined-performance-management-process--part-2
all 3 blogs are very helpful since there is little information available out there on these topics...
so we've been testing the delta indexing program very heavily - ESH_IX_PROCESS_CHANGE_POINTERS
we have found that it does not appear to be able to index new hires (new central_person index does not pick up the new CP). The only way this data can be indexed is by running a full re-index. That is problematic for us, b/c we were hoping to only do full re-indexing 1 a week or even 1 a month. our indexes take 2-3 hrs to complete and trex searching is pretty much inoperable during that time.
Have you tested new hires with delta indexing? it seems as a gap in the change_pointers program. We opened up OSS message to SAP.
some additional thoughts working with the program, relative to your blog. I would highly recommend that anyone testing this makes sure the following notes are implemented in your system. The first one is the most recent and we ourselves did not have that implemented.
1. 0.350 BC-EIM-ESH 1441190 Error in model assignments to logical system 24.02.2010
2. 0.230 BC-EIM-ESH 1408655 Alerts in syntax check due to unused indexes 18.11.2009
3. 0.260 PA-TM 1395703 Positions and termination are missing for indexing 30.10.2009
4. 0.330 BC-EIM-ESH 1249482 Functional corrections for Enterprise Search 7.01 SP03 26.01.2009
Another area which we found from testing: SAP by default does not delta index structural authority view. What this means is that if a new talent specialist is added with 741 relationship there access to see that structure will not be available in TREX search by default delta indexing. This would also impact existing organizations and positions shifted under existing 741 relationships.
The information in spro is actually quite helpful, you can find it in: talent management and talent development > basic settings > search > BAdI: Activate Delta Indexing for Authorization Data
Activtate the BADI, than the program to "create the change pointers" must run periodically in your system. This is done with RPTMC_CREATE_CHANGEPOINT_AUTH. Once that program creates the change pointers the next time your scheduled delta program runs (ESH_IX_PROCESS_CHANGE_POINTERS) all of the structural auths will be created and indexed correctly.
If we can just now get new hires to work with ESH_IX_PROCESS_CHANGE_POINTERS we will probably only run the full re-index once a week or once a month.
Let me know your thoughts,
Michael
Message was edited by: Luke Marson
Message was edited by: Luke Marson

so if anyone is interested, from my previous post I mentioned that new hires were not getting picked up by the change pointers program.
after further testing though, we found that when the authorization recon program identifies the new hires and appropriately creates a change pointer.
conclusion: to avoid full re-indexing of trex indexes, perform the following steps:
1. implement / activate the BADI - HRTMC_AUTHORITY_VIEW - talent management -> basic settings -> search
2. Schedule program RPTMC_CREATE_CHANGEPOINT_AUTH - every 30 mins, or 1 or 2 hr. This program will capture whenever anything changes from an authorization data perspective. This would include identifiying new central persons (new hires) or new TMC specialist being setup with 741 relationship. This program "creates change pointers" which than feeds the main delta program - ESH_IX_PROCESS_CHANGE_POINTERS.
3. Use Luke's blog on the instructions for the delta program - ESH_IX_PROCESS_CHANGE_POINTERS - this program you can have run every 5 mins, 10 mins, 15 mins, based on your needs. this processes all delta changes, the first time the program runs after the RPTMC_CREATE_CHANGEPOINT_AUTH program finishes it will also processes the data authorization changes, otherwise every other time the program is running it will catch non-data authorization for all the other indexes (employee name change, new performance rating, new potential, position name change, new profiiciency scale, new career profile data, etc).
hope this helps somebody!
michael
Edited by: Michael L Pappis on Oct 7, 2010 12:05 AM

SAP-DMS and NetWeaver Enterprise Search 7.2

Good day Experts,
I will be thankful to you if anyone can help me with the following query.
In SAP-DMS, we have got a reporting transaction CV04n which has got a facility to search for 'Text Search Within Original'. There is neat procedure if one wants to configure this feature for SAP-DMS. The procedure is as under
(Re: Document text search in cv04n with TREX)
1) Transaction: SRMO
Install TREX search engine, and create RFC destination to connect to
TREX.
2) Transaction: SKPR06
Check the flag to Document Area "DMS" to utilize this document area for
document search.
3) Transaction: SE38
Run the report program "RSTIRIDX_REINDEX" to create Index.
Also, run the report program "RSTIRIDX" to create Index as well.
4) SPRO IMG customizing; (Create MIME Types)
Cross-Application Components > Document Management System > General
Data > Settings for Storage Systems > Create MIME types for full
text search, Enter MIME type such as "application/msword",
"application/pdf".
5) Then, test retrieval document search using
Transaction: SKPR07.
Enter Document Class "DMS_PCD1", Language "EN", Document Class "DMS",
and try "TEST search".
We know from Karsten's SDN post (What is really 'SAP Netweaver Enterprise Search' ) that this feature is possible with NW Enterprise Search 7.2
u201CWith SAP NW Enterprise Search 7.2 having collected the Embedded Search indexes, the local search functionalities stay active and at the same time SAP NW Enterprise Search enables central search access to all Embedded Search systems in the landscape.u201D
Our query is as under
Does SAP NW Enterprise Search 7.2 ; which has got its own integrated TREX engine needs assistance from TREX engine from our landscape to make this feature work. This is important becuase then we have to have two different set ups.
A set up for SAP NW Enterprise Search 7.2 which is a separately licensed product.
A set up for TREX engine which is part of NetWeaver licence.
Regards,
Sham Bapat

Good day Sham!
The answer is:
No, you will not need the local PLM TREX anymore, as soon as you have installed SAP NWES 7.2 and pointed your PLM there instead of the local TREX.
And, I repeat, your local search functionality inside PLM will still work anyway.
Best, Karsten

Integration of TREX/Enterprise Search

Hi,
is it possible to integrate TREX/Enterprise Search into a web dypro application? That means the user can put a search string into an input field in a web dynpro application, the request goes to the TREX and the result will be shown in a web dynpro table.
Are there any documentations? How to handle this? I couldn't find anything to manage this.
Thanks.
Regards, Susanne

The ABAP Dictionary F4 Search Helps (transaction se11) are supported by Web Dynpro ABAP in the same way as with SAP GUI.
Note that the function module TREX_EXT_SEARCH_DOCUMENTS is an SAP internal interface.
It is not released for customer use, i.e. you cannot claim SAP support for your implementation.
Instead you should use a released search framework, that resides on TREX.
For details read SAP note 1254901 - SES for customer projects on TREX search
If you need a cookbook, how to include your specific search help into a standard F4 search help, you can refer to SAP note 1345777 (FAQ SES), chapter 8.
Cheers, Klaus

Configuring TREX for HCM Talent management functionality using Nakisa

Hi,
We are configuring the Talent Management functionality in ECC-HR system.We have installed TREX 7.1 patch number 36 and Nakisa.
We are using the 'embedded search' functionality.
Now, also and are trying to create indexes using the Administration cockpit (tcode ESH_COCKPIT).
However we are getting the error 'System DHS, client 100: A connection already exists' while creating a 'search connector' in the cockpit.
Also, we are getting the below log error in the system in SM21:
''TREX_ICM - Send_Error; return code = 112, return text =HTTPIO_PLG_ICM_CONNECT_FAILED-Fehle''
Kindly let us know what should be done.
Thanks & Regards,
Kunal.

Hi,
Now the initial error we were getting is resolved by applying one note suggested by SAP OSS.
However, now we have another issue, while creating indexes using tcode ESH_COCKPIT in the backend system.
We get error when we try to go to tcode TREXADMIN --> TREX
ABAP Customizing --> 'Net Performance'.
It gives the error below:
ERROR
Remote communication failure with partner http://:33003/ICMConnectTest
HTTP Status 507: Kernel error:ICM_HTTP_CONNECTION_FAILED (400 )
Kindly let us know why we get the error because even while recreating
the indexes we get similar error i.e. Remote communication failure with
partner http://cca1cs0872:33003/asxml/multiIndexCellTable
The icm timeout parameter is sufficiently large i.e. around 30 minutes.
Also, the RFC (TREX_DHS) from ECC-HR system to the TREX is working fine.
Thanks & Regards,
Kunal.

Talent Management TREX and Enterprise Search

Similar Messages

Maybe you are looking for