PCD Index Error in Trex Search

Dear all
I have tried to configure as mentioned in the URL
Configuring the Search for Portal Pages and iViews
http://help.sap.com/saphelp_nw04/helpdata/en/b2/d59a4271c80a31e10000000a1550b0/frameset.htm .
I am getting the following error.
Search Failure
Error during search occurred com.sapportals.wcm.WcmException
An unexpected severe error occurred during the search call. If the situation persists, inform your system administrator.
When I remove the index which is created for the PCD and created dummy index for any of the KM folder then its work fine.This scenario is working fine for the administrator and it is not working for the anonymous users.
Can anybody help in this...
Regards
Geogi

Hi Robert,
Thanks for your reply.I have done the same way U mentioned in the last reply.
I have changed the https host name to http,then restarted servlet engine and trex server.After that i have done re-indexing on my particular repository.
Now it is showing the below status:
return code :8005
Time out reached
To be preprocessed: 780
Document status: To be preprocessed and preparation failed
indexed : 175
Errors :315(preparation failed).its taking too much time to re-index and now errors are going on increasing.
shall I remove the full alternate host name and delete the old index and create new index.will it work?
what is the solution for the above condition?
Waiting for your reply.
Thanks in Advance
Amit kumar koyal

Similar Messages

Portal Roles Search & TREX Search

Hello,
We need to search some pages and documents. The search results should be based on the permissions set for that user on the pages and documents. We created Portal Roles Search. It works fine for pcd objects. But it doesn't work for documents.
When we create an index with TREX Search service, it works for documents. But it doesn't consider the permissions.
When there are 2 search indexes, one with TREX Search and the other with Portal Roles Search, the TREX Search throws WcmException.
Any ideas?
Regards,
Rukmani

Hi Sudha,
Portal Roles Search
The objects found using the portalRolesSearch index service in the PCD cache are converted to KM objects and can be displayed in the search results list.
http://help.sap.com/saphelp_nw2004s/helpdata/en/b2/d59a4271c80a31e10000000a1550b0/content.htm
TREX Search
Enables the retrieval of information
http://help.sap.com/saphelp_nw70/helpdata/EN/42/60adaa032c1422e10000000a114cbd/content.htm
TREX Classification
Helps in the classification of documents.Classification causes documents to be assigned to one or more categories of an existing taxonomy
http://help.sap.com/saphelp_nw04s/helpdata/en/bf/a17a05d15211d6b2c700508b6b8a93/content.htm
It depends on the kind of search you want to enable for your project.
Hope this helps.
Cheers,
Sandeep Tudumu

TREX search error

We are getting an intermittent problem when we do a search from our KM iview. When we put in a search string it for the most part comes back with the appropriate data, but every once in a while we get the following error either as an informational text at the top of the iview or as stack dump error.
Error during search occurred - com.sapportals.wcm.WcmException: Index does not exist;index=ourindex (Errorcode 2007)
Does anybody have any information on a fix for this?

Hi Aaron
Indexes are created in ECC or any other SAP for trex search and sometimes indexes may be have to be rebuild, have you checked this particular index shown in the error message 'ourindex'
Bhudev

TREX - Search Failure - HTTP Server error: 503 - Queue Server down

Hello,
I've got a problem with TREX, the following tasks results in erros:
Default Search
Search Failure
Error during search occurred - com.sapportals.wcm.WcmException: HTTP server error: 503 (Errorcode 7266)
An unexpected severe error occurred during the search call. If the situation persists, inform your system administrator.
Creating Index
Error 503
- On Index Administration: indexes status are green
- On TREX Monitor: Takes long time to loa. HTTP Server and Name Server are green. There is no entry for Queue Server
- On TREX Monitor > Display Queues: Takes a long time and then no queues are displayed
- On Portal Monitor > Request Overview: Requests for TREX takes pretty long time
Starting Time: 9:16:23 AM
Starting Date: May 19, 2010
Request Name: NW:J2E:SRV:HTTP
User ID: <my user>
Outbound Data: n/a
Duration: 395671
CPU Time: 5812
Component Entries: 26
Component with Largest Net Time: EP:KM:TREX:HTTP:<host>:30205
Largest Net Time: 38867
Component with Largest Net CPU Time: EP:PRT_render:.../com.sap.km.TrexMonitor
Net CPU Time: 5674
Could you help me with procedures or guides on how to solve the problem and start the queue server?
kind regards,
Rafael

BASIS team reseted TREX and it's working again

TREX search engine error

Hi,
I am new to KM.I installed TREX server in separate Host.I am accessing the TREX server into our portal.I created the Web Respository and craeted Crawler and Index.When i check the TREX monitor and Crawler monitor everything running fine.But when i am Searching the content throough search engine i am getting the following error.
Search Failure
com.sapportals.wcm.WcmException: Index does not exist; indexId = "test_index" (Errorcode 7)
An unexpected severe error occurred during the search call. If the situation persists, inform your system administrator.

Can anyone suggest me where exactly i am getting the problem and need solution.
Regards
Usman

Hi Usman,
you probably deleted an index on TREX site, without deleteing the index in KM Index Administration.
This is simply not supported, because KM has no chance to register it.
You have to choices:
Either 'Reindex' this index in the index administration.
The other option is to delete it.
Regards Matthias Röbig-Landau

CCM TREX indexing error

To CCM gurus,
Once in a while, I'd get indexing errors while trying to publish a procurement catalog. The errors would say something like:
1. Error when deleting TREX metadata for catalog ABC...
2. Error when creating the index for catalog XYZ...
3. Error in search index update; discarding existing changes
And then the catalog update is terminated. What we normally do is restarting the TREX server and then we can publish again.
My question is...can we resolve this without having to restart TREX each time? Is there a way to re-index TREX without restarting it?
Regards,
SN

Hi SN,
You can check the 'health' of the TREX indexes specific to CCM by use of report /CCM/CHECK_TREX (you need at least CCM 2.0 SP4 for this). In this report, if the index is either orange or red, it is not usable, if it is green it is fine. If the index is coloured red or orange, drill into this index and there will be some short text indicating what the problem with the index is. Once inside this index it can be deleted using the delete (trashcan) icon - in this case, a full publication is required to regenerate the index from fresh.
It may also be possible to use report /CCM/RECREATE_INDEX providing the index is still valid on the trex server.
Regards,
Jason

Search indexing error in CRS 10.0.2

Hi All,
I have setup the CRS with Search and i have done full deployment and started doing search full indexing. i am getting the following error.
Please suggest if you have any.
Error Message In Search Indexing status monitor
atg.searchadmin.core.IndexLoaderException: Exception while processing customization item atg.search.adapter.customization.CustomizationItemProxy@6476d0: Customization atg.search.adapter.customization.CustomizationItemProxy@6476d0 failed.
     at atg.searchadmin.core.IndexLoader.executeCustomizationList(IndexLoader.java:1008)
     at atg.searchadmin.core.IndexLoader.executeCustomizationType(IndexLoader.java:926)
     at atg.searchadmin.core.IndexLoader.executeCustomizationType(IndexLoader.java:876)
     at atg.searchadmin.core.IndexLoader.executeCustomizations(IndexLoader.java:847)
     at atg.searchadmin.core.IndexLoader.completeIndex(IndexLoader.java:1489)
     at atg.searchadmin.core.IndexLoader.executeSession(IndexLoader.java:1991)
     at atg.searchadmin.core.IndexLoader$IndexingThread.run(IndexLoader.java:2423)
Caused by :atg.searchadmin.core.IndexLoaderException: Customization atg.search.adapter.customization.CustomizationItemProxy@6476d0 failed.
     at atg.searchadmin.core.IndexLoader.executeCustomizationList(IndexLoader.java:1004)
     at atg.searchadmin.core.IndexLoader.executeCustomizationType(IndexLoader.java:926)
     at atg.searchadmin.core.IndexLoader.executeCustomizationType(IndexLoader.java:876)
     at atg.searchadmin.core.IndexLoader.executeCustomizations(IndexLoader.java:847)
     at atg.searchadmin.core.IndexLoader.completeIndex(IndexLoader.java:1489)
     at atg.searchadmin.core.IndexLoader.executeSession(IndexLoader.java:1991)
     at atg.searchadmin.core.IndexLoader$IndexingThread.run(IndexLoader.java:2423)
Error message In BCC Server console:
17:33:17,977 ERROR [IndexLoader] Error occurred in step post_index_customization_step for sync task 400004 of type complete. Error:
atg.searchadmin.core.IndexLoaderException: Exception while processing customization item atg.search.adapter.customization.CustomizationItemProxy@6476d0: Customization atg.search.ad
apter.customization.CustomizationItemProxy@6476d0 failed.
atg.searchadmin.core.IndexLoaderException: Exception while processing customization item atg.search.adapter.customization.CustomizationItemProxy@6476d0: Customization atg.search.ad
apter.customization.CustomizationItemProxy@6476d0 failed.
at atg.searchadmin.core.IndexLoader.executeCustomizationList(IndexLoader.java:1008)
at atg.searchadmin.core.IndexLoader.executeCustomizationType(IndexLoader.java:926)
at atg.searchadmin.core.IndexLoader.executeCustomizationType(IndexLoader.java:876)
at atg.searchadmin.core.IndexLoader.executeCustomizations(IndexLoader.java:847)
at atg.searchadmin.core.IndexLoader.completeIndex(IndexLoader.java:1489)
at atg.searchadmin.core.IndexLoader.executeSession(IndexLoader.java:1991)
at atg.searchadmin.core.IndexLoader$IndexingThread.run(IndexLoader.java:2423)
Caused by: atg.searchadmin.core.IndexLoaderException: Customization atg.search.adapter.customization.CustomizationItemProxy@6476d0 failed.
at atg.searchadmin.core.IndexLoader.executeCustomizationList(IndexLoader.java:1004)
... 6 more

You have two options, if your cartridge is like MediaBanner, and at least has media and link objects, you just need to use OOTB MediaBanner handler in the properties file.
Otherwise, you first have to define the class you will use for MediaBanner handler, and in that class you will need to convert linkBuilder to linkaction like this:
- your class needs to extend from NavigationCartridgeHandler
- in the process method, you will need to get linkBuilder object
- and then get linkAction object like this:
linkBuilder.createAction(this.navigationStateBuilder, this.contentSource, getActionPathProvider())
Does it make sense?
Regards,
Naresh

TREX Indexation errors

Hi!
We use SAP NetWeawer Portal 7.0 SP18 and Sap Trex 7.10.23. When I start indexation for documents in repository in the Portal i get errors in Trex trace like this ...
TrexApiContent.cpp(00575): doc type != analyzed, can't resore content for doc...
almost for all documents in the repository.
What does this erorrs mean? and how to fix this problems?

TrexIndexServerAlert.trc:
[1159735616] 2010-05-19 17:47:49.859 e SERVER_TRACE TRexApiContent.cpp(00575) : doc type!=analysed, can't restore content for doc '/repository/filename.txt'
[1091729728] 2010-05-19 17:47:49.935 e SERVER_TRACE TRexApiContent.cpp(00575) : doc type!=analysed, can't restore content for doc '/repository/filename.txt'
[1193306432] 2010-05-19 17:47:49.941 e SERVER_TRACE TRexApiContent.cpp(00575) : doc type!=analysed, can't restore content for doc '/repository/filename.txt'
[1210091840] 2010-05-19 17:47:49.944 e SERVER_TRACE TRexApiContent.cpp(00575) : doc type!=analysed, can't restore content for doc '/repository/filename.txt'
[1184913728] 2010-05-19 17:47:49.946 e SERVER_TRACE TRexApiContent.cpp(00575) : doc type!=analysed, can't restore content for doc '/repository/filename.txt'
[1201699136] 2010-05-19 17:47:49.955 e SERVER_TRACE TRexApiContent.cpp(00575) : doc type!=analysed, can't restore content for doc '/repository/filename.txt'
In other trace files i cann't find any errors with this documents.

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

Error occurred during search

Hello,
I'm getting the following error when I use the search in the Portal:
Error occurred during search: com.sapportals.wcm.WcmException: error: communication with preprocessor failed;index=teste,location=cdphl815:30203 (Errorcode 42)
That's probably an indexing error:
Indexing document failed. Preprocessor: failed (Errorcode 6800)
But I don't know what to do to fix this.
Please... help me!!
Thanks
Luisa

Hi Luisa,
It might help:
Trex Administration Tool:
http://help.sap.com/saphelp_erp2004/helpdata/en/23/92bd4016c0cc38e10000000a155106/frameset.htm
General TREX Configuration :
http://help.sap.com/saphelp_erp2004/helpdata/en/c2/d81e40777cdd5fe10000000a155106/frameset.htm
Post-Installation Activities :
http://help.sap.com/saphelp_erp2004/helpdata/en/8b/1cc83edf72e16be10000000a114084/frameset.htm
Hope it helps,
Yoav

TREX search failure for some pdf documents

Hi,
TREX search is not getting correct result for some pdf documents. It's not able read the content of some pdf documents. When we search with file name the search result is correct but we are getting "No document excerpt available" message in search result for this file name.
Let me know where might be the problem for those pdf docs.
Thanks

Hi Tatayya Marni,
1. Can you tell me whether the pdf documents are opening when you are selecting them?
2. This error comes mostly when you havent included this .extn file (.pdf in your case) to the portal.
3. Check whether this extn is their in your portal if not make it inclueded and then try making a new index and one new data source where your pdf is residing. Try for one Test.
You have to include the file extns in System Confi....UI Interface...
Hope this will resolve your issue.
Regards
Piyush Bhurangi

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

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

TREX7 - Following error occurred in search: 2029

Hi,
We have done an upgrade of E-Recruitment 2.0 to 6.0.With respect to that we have installed TREX 7.0 on AIX platform.We have created the indexes on the new TREX
Version info for RFC server : SERVER Version TREX 7.0
Version info for search engine: DrFuzzy 6.1
When i do a TEST Search from TCode SKPR07 i am getting "Following error occurred in search: 2029" also i can see many entries under the "Problem Case" with Error Code 8002.
When i do a search from the application i doesn't return any values.
What could be the reason.
Regards,
Sam

Hi Sam,
the error 2029 could have too many different reasons like: incompartibility between ABAP and TREX versions, corrupted index, wrong query e.t.c .
Please open new OOS ticket regarding this issue.
Regards,
Mikhail

TREX Search with URL Parameters

Hi all,
is there still a (supported) way to query TREX via a URL with parameters in 2004s?
Thanks,
Reinhard

Reinhard,
This should help you out a little bit
Standard Portal call for html event: https://<servername>/irj/servlet/prt/portal/prteventname/HtmlbEvent/prtroot/
PCD Object Location to your search iview: pcd!3aportal_content!2fcom.sap.sen.search!2fcom.sap.sen.search.iViews!2fcom.sap.sen.search.value_engineering_search?
Type of Search: SearchType=quick
Predefined Properties (Metadata): &SelectedPredefinedProps=<namespace>:<metadata unique id>(value=<value searching for>/operator=EQ)
Query String: &QueryString=*
Put it all together!
https://<servername>/irj/servlet/prt/portal/prteventname/HtmlbEvent/prtroot/pcd!3aportal_content!2fcom.sap.sen.search!2fcom.sap.sen.search.iViews!2fcom.sap.sen.search.value_engineering_search?SearchType=quick&SelectedPredefinedProps=<namespace>:<metadata unique id>(value=<value searching for>/operator=EQ)&QueryString=*
Thanks
Trevor

PCD Index Error in Trex Search

Similar Messages

Maybe you are looking for