Fuzzy search is not working

[Former Member]

Hi ,

We had intergrated the SCM system with TREX and indexing the long descriptions and description into TREX system by using TREX function modules.But while search with any word in TREXADMIN, it will search with "exact" word. But customer requested to support the "Fuzzy" search also.

Could any one will help to activate the fuzzy search in this scenario? we are using TREX search function module to get the result data by passing the attributes as input to  TREX Search function module.

Thanks in advance,

Surendra.

[former_member217429]

Hi Surendra,

from the ta. TREXADMIN you can execute only the exact search. However this is not the way how the applications search in TREX (I mean the TREXADMIN is used for monitoring TREX and in special cases you can change the TREX settings there, but the search in TREXADMIN is just for the testing).
What's the application you use ? ESH ?

Best regards,
Mikhail

[Former Member]

Hi Mikhail,

Thanks for your reply.

Actually we have SCM TM system where commodity gets creating along with long description. We are trying to indexing the commodity long description into TREX system using TREX function module. As of now Long description and commodity code has indexing into TREX system.

We have search help exit for commodity field , when we are trying to search with any text in description field of commodity search help pop up, it will try to searching the long description along with commodity from TREX system by using 'TREX_EXT_SEARCH_DOCUMENTS' function module by passing the  index table, RFC destination, query entries, requested attributes .

Exact search is working properly. But customer has requested for fuzzy search. We already passing the TERM-ACTION query parameter as 'F' in query internal table. Even though FM does n't returns any results.

Kindly help me there was any extra parameters need to be required in query internal table or any other way to activate?

Thanks,

Surendra.

[former_member217429]

Hi Surendra,

it's very difficult to find out what#s missing or what's wrong in the query. May I ask you to create an OSS incident for this issue and put this on BC-TRX component.

Thanks and best regards,
Mikhail