$(function () { pageContext.i18n.modTalk = 'moderation talk'; pageContext.i18n.replyToComment = 'Reply'; pageContext.i18n.modTalkEmpty = 'moderation talk is empty'; pageContext.url.getModTalk = "/comments/%25ID%25/listModTalk.json"; pageContext.url.possibleCommentRecipients = "/comments/%ID%/possibleRecipients.json"; pageContext.url.commentEdit = '/comments/%25ID%25/edit.html'; pageContext.url.commentView = '/comments/%ID%/view.html'; pageContext.i18n.commentVisibility = { 'full': 'Viewable by all users', 'op': 'Viewable by the original poster', 'mod': 'Viewable by moderators', 'opAndMod': 'Viewable by moderators and the original poster', 'other': 'Advanced visibility', 'dialogTitle': 'Comment visibility', 'selectGroups': 'Visible to groups', 'selectOther': 'Other recipients', 'selectOriginalPoster': 'Original poster', 'selectModerators': 'Moderators', 'selectAssignees': 'Asked to answer users' }; pageContext.i18n.commentMenuLabels = { 'comment-edit': 'comments.menu.edit', 'comment-delete': 'comments.menu.delete', 'comment-convert': 'comments.menu.convert' };pageContext.i18n.answer= { bestAnswer: 'Best Answer', controlBar : { accept: 'Accept', unaccept: 'Unaccept', acceptCommand: 'Accept this answer as correct', cancelAcceptedCommand: 'Remove this answers accepted status' } }; window.croles = { u: false, op: false, m: false, og: false, as: false, ag: false, dc: false, doc: false, eo: false, ea: false }; tools.init({ q: { e: false, ew: false, eo: false, r: false, ro: false, d: false, dow: false, fv: false, c: false, co: false, p: false, tm: false , ms: false, mos: false }, n: { f: false, vf: false, vfo: false, vr: false, vro: false, c: false, co: false, vu: false, vd: false, w: false, wo: false, l: false }, c: { e: false, eo: false, d: false, dow: false, ta: false, tao: false, l: false }, a: { e: false, ew: false, eo: false, d: false, dow: false, a: false, aoq: false, ao: false, tc: false, tco: false, p: false, tm: false }, pc: croles }, { tc: true, nsc: true }); commandUtils.initializeLabels(); }); Skip to Content

Onedx search: enforce 'exact' search with special characters

May 11, 2017 at 09:40 AM


avatar image

I am trying to search via onedx.find.sap.com with the following criteria:

"include <object>"

and I get these results:


In my case < and > are not treated as a part of the search criteria.

What additional parameters do I need to pass and what formatting should I use to enforce exact search with such characters?

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Mynyna Chau
May 12, 2017 at 03:28 PM

I now learned that this is covered in this documentation.The syntax asked about is not supported.

Are there any characters I cannot search on? The full text index ignores all of the following characters .'\/;,:-_()[]<>!?*@+{}="&#$~|‚ (token separators). This usually leads to good search results but in some special situations does restrict search capabilities. If you want to search on file endings such as '*.txt' - the system interprets with as search for 'txt' - and only occasionally returning results as expected. The closest result is using API with 'like' operator - not giving back any ranking, having rather poor performance and not available via UI. In case you want to search for a particular file name such as 'error_101.txt' the normal query can be improved using an exact search query "error 101 txt" (which is synonym to "error_101.txt"). In this case typos are certainly not taken care of.

In case you are seeking for a product version '4.1', this query handled the same as searching for '1 or 4'. Similar to the above it is recommended to combine this with a product name and using exact search - such as "netweaver 4.1"

Thanks to Jason Lax who provided this answer.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Thank you both, for taking the time to explain. I was hoping, that there was some escape character, which I did not think of, that could do the trick.

Unfortunately, both links are not accessible for non-SAP employees, but I think, that I understood the case by the provided explanation.

If, at some point, part of this documentation could be published for public use, this would be really great, because if people understand how SAP search functions, they can take better advantage of its capabilities.