Case Analysis of search problem in SAP Fiori Application

This article mainly introduces "case analysis of search problems of SAP Fiori application". In daily operation, I believe that many people have doubts about the case analysis of search problems of SAP Fiori application. The editor has consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "case analysis of search problems of SAP Fiori application". Next, please follow the editor to study!

Contact search on Fiori ui looks like google like search, but in fact the technical implementation (which refers to the DB query part) is the same as search on Webclient ui.

Of course, it also supports enterprise search.

The title Dr of BP is stored in field TITLE_ACA1 in the form of key 0001, and Dr is only 0001 of the translatable description, so you can't get the desired results through Dr search.

There is a bug in BP's code (although the latest SAP code has been fixed), and they want the longer strings to be executed first when performing multiple rounds of scans:

Before Sort: 2, 5, 7

After Sort: 5, 5, 2, 7-wrong.

Only if you explicitly add by length: SORT lt_search_f by length DESCENDING.

Be careful when you write code, and try to avoid similar problems by using the guideline defined in follow ABAP help:

At this point, the study of "case analysis of search problems in SAP Fiori applications" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!