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

Similar Messages

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

Error while creating the Connector in PRD - Trex in Talent Management

Dear Luke,
Greetings.
We are in ECC 6, Eph4.
While setting up the TREX in Production we are encountring an error as below. But we dont have any issue in Development and Quality system. TREX related to Talent Management is working fine.
Would be great if you share your inputs.
Kind regards
Sathya

Dear Luke,
Thank you for response. We have posted an OSS message. SAP is suspecting this to a support pack level kind of issue. So we are waiting for a solution from SAP.
Appreciate your support.
Kind regards
Sathya

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

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

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

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 - 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

New SDN blog post: Setting up TREX for SAP EhP4/5 Talent Management

Hi all,
I have written a new SDN Blog on Setting up NetWeaver Embedded Search (TREX) for SAP EhP4 Talent Management:
http://scn.sap.com/community/erp/hcm/blog/2010/09/20/setting-up-netweaver-embedded-search-trex-for-sap-ehp4-talent-management
Enjoy!
Luke

Hi Luke
I'm looking for a copy of the SDN Blog, but having trouble trying to find it.
All pages lead to "Page not Found".
Is it possible for you to post this again or email me a copy of the Article ?
Thanks in Advance
Min

Searching for dashboard Talent Management in OBI APPS

Hi All,
I have question to the Gurus that I am searching for Talent Management in OBI Apps Human resource , is it available in 7.9.6 version because we have 7.9.5 and it is not there in that ?
Thanks for quick response,
Amol

Hi Amol,
We have downloaded and setup the BI Apps to see what they are all about. I personally exported a report of all the requests in the latest version, 7.9.6, and there is nothing affiliated with "talent".
Hope this helps. Please award points if you find my research helpful.
Best regards,
-Joe

Talent Management Enhancement pack 4 Business Function HCM_TCM_CI-1

This business function contains some new job architecture functionality that we would like to utilize. These new object types are functional name (FN) and job family (JF). We do not plan to configure any of the talent management functionality because we will not be using it at this time. Activating this business function also activates a functionality called Embedded Search which requires TREX 7.1. We do not plan to do any of the configuration for the embedded search functionality either at this time as we don't think we will need it.
My question is, is anyone aware of any issues that might arise or what other SAP functionality that might be impacted by moving this business function into our Production environment without doing any of the configuration. We have implemented SAP Payroll, Benefits, Org management, Personnel Administration, eRecruiting and Learning.
Thanks in advance for any advise you can provide.

Hi Kathy:
In a nutshell, you shouldn't run into any issue. You're just going to get a host of new web dynpro apps, OM data, and infotypes for the Central Person (the 74XX infotypes). If you don't use them, then that's fine, it won't hurt anything.
You should be just fine using the HRP1001 450 relationships from JF to FN and C to help drive your job architecture. You would potentially need to use transaction HRTMC_PPOM to manage your job family/functional area relationships, but you won't negatively impact anything you have already implemented.
If you're not going to use any of the Talent Mgmt functionality, you also don't need to worry about enterprise search or TREX. I'm assuming you aren't using Succession Planning in eRecruiting, right? If you do ever consider using the Talent Management functionality you've now implemented, you will have to migrate data over from the old eRecruiting version of Succession Planning. Other than that, you should be good to go.
Hope that helps!
Thanks,
Chris

Regarding Talent Management Infotypes !!!

Hi Seniors,
As,I am assigned to work on career and succession planning module... I would like to know about the info types 7400, 7410, 7402, 7403 .... etc.
When to maintain these info types ?
Where to maintain info types?
How to see these info types?
Pls suggest
Regards,
Ritu

Hi Ritu,
The Portal is for the following applications:
Talent Profile for Employees
Talent Profile for Managers and Talent Management Specialists
Talent Review Meetings
Talent Groups
Corporate Goals and Values
Talent Assessment
None of these processes can be managed in the SAP R/3 system. Therefore it is not possible to have a holistic end-to-end succession management process, since you can only manage succession planning of positions.
For your search issue, have you installed and configured TREX? See this blog for information:
Setting up NetWeaver Embedded Search (TREX) for SAP HCM Talent Management EhP4, 5 and 6
Best regards,
Luke

Indexing Trex Search

Hello!
I have a question to the indexing of the connectors. I have setup the trex search in our talentmanagement with the very good tutorial from Luke Marson. When I see the Connectors in the ESH_Cockpit there were some Connectors set with real time indexing and some not. What is necessary that all the different connectors are indexing every 2 hours. Our SAP Netweaver is in Version 7.1 and we have EHP6.
Please could you help me.
Best regards
Jürgen

Hello Luke,
thanks for your reply. I understand that the technical templates cannot be index in real time.
Is it necessary to index technical templates in connection with the trex search in talent management?
If yes, how can this be accomplished?
If i understand it correctly connectors with real time indexing update the index automatically. There is no need to schedule any indexing procedures.
TIA,
Jürgen

Issue in creating dev plan in talent management specialist role

Hi ,
I am facing issue in creating development plan through talent management specialist role . Actually in one system I have 2 location one is india & another one is USA . its working for india but when I search india employee its show no employee found . can you please guide me
Tarun

Hi Luke ,
According to one of your article , I run HRALXSYNC in r/3 , in that all indian employee are green but USA employee in RED . I found following error , can you please guide me that what is mean by that ?
The error occurred in program CL_HRRCF_INFOTYPE=============CM003 line 117
Qualification 90007487 does not exist
The incorrect HR object has the key 01NA90011026
The incorrect infotype record is 40601NA900110265105 1 1900010199991231
The error occurred in program CL_HRRCF_QUALIFICATION========CM001 line 69
Serious error; see log
The error occurred in program CL_HRRCF_CANDIDATE_INFOTYPE_BLCM00B line 99
Serious error; see log
The error occurred in program CL_HRRCF_INFOTYPE=============CM003 line 117
Qualification 90007487 does not exist
The incorrect HR object has the key 01NA90011026
The incorrect infotype record is 40601NA900110265105 1 1900010199991231
The error occurred in program CL_HRRCF_QUALIFICATION========CM001 line 69
Serious error; see log
The error occurred in program CL_HRRCF_CANDIDATE_INFOTYPE_BLCM00B line 99
Thanks
Tarun

TREX search KM BI Repository

TREx 7.1
Portal 7.0
I have created and been using a KM BI Repository. This repository contains txt documents that are currently being accessed thru a KM Document IVIEW. I have recently implmented TREX 7.1 and I am having trouble finding anything in my repository using the search UI.
I have added indexes and taxonomies that point to the data source /bi_documents.
The search UI is available but finds nothing.
The TREX search can find Portal Documents.
I have also added to the Index Management Service the "Repository Manager" that is for my BI Repository.
Component Monitor is good and all green
TREX Monitor good.
My searchs still return nothing from my KM BI Repository.
I have researched and followed numerous documentation on repositories.
Any help or configuration document on KM BI Repositories would be appreciated.
Thank you,
sarah

Thanks for the input Frank,
I am using the standar crawler and it appears that the indexes are not being built due to a crawler error.
Preprocessor.cpp(01165) :     HTTPHEAD failed for URL https://sbserver.sap.state.edu:50001/irj/go/km/docs/bi_documents/InfoProviderData/%23BP_M001/1413120000%202010%20AM.txt :
Errorcode -8001 , Message   Reader::connect failed, url=https://sbserver.sap.state.edu:50001/irj/go/km/docs/bi_documents/InfoProviderData/%23BP_M001/1413120000%202010%20AM.txt
Preprocessor.cpp(03980) :     HANDLE: DISPATCH - Processing Document with key 'https://sbserver.sap.state.edu:50001/irj/go/km/docs/bi_documents/InfoProviderData/%23BP_M001/1413120000%202010%20AM.txt' failed, returning PREPROCESSOR_ACTIVITY_ERROR (Code 16001)
Any help on this would be appreciated.
thank you,
sarah

TREX - Search Talent Management

Similar Messages

Maybe you are looking for