Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-DIC-F4 (Application Component) F4 Help⤷
SDSH (Package) ABAP Dictionary internal: Poss.entries (F4)
Basic Data
| Data Element | DDFUZZY_SEARCH |
| Short Description | Full Text Fuzzy Search |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DDFUZZY_SEARCH | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 0 | |
| Medium | 20 | Error-Toler. Search |
| Long | 30 | Error-Tolerant Search |
| Heading | 0 |
Documentation
Definition
Certain databases (for example, SAP HANA) support a full text fuzzy search for the content of one or several tables or views. This kind of full text search across several columns is of particular advantage whenever users do not have exact knowledge of the value to be entered - for example, in the case of a complex customer number - but would be able to identify it by means of other attributes of the data record, such as the name or the location of the customer. If the other attributes are stored in other columns of the chosen selection method, the proposal search can supply the respective values for the input field through the input of these other attributes.
Use
This functionality is currently supported solely together with the proposal search for input fields. This means that the full text fuzzy search is not available through the standard input help that can be called using F4, for example. So that the input help includes the corresponding columns for this search, these must be marked as IMPORT or SPos parameters.
In certain circumstances, this setting can lead to a longer execution time for the proposal search, in particular if several search terms were entered and/or many columns of the selection method were selected for the full-text search. In this case, before you release the search help for this feature, it should be tested extensively for its runtime behavior.
Dependencies
This functionality can, as a rule, always be selected during modeling if the proposal search for input fields is activated and if tables or a view were selected as selection method. These are tables or views that are available on the database and a full text search is possible for them. This currently aplies to all database tables whose storage method is column-based. It also applies to database and projection views. If, for example, a help view or no selection method (data acquisition through a search help exit) is modeled, this functionality cannot be activated.
At runtime, the functionality is only activated by the system if it is also supported by the installed database. In the case of non-supported databases, the search help - during the proposal search on input fields - always behaves as if this functionality were not activated. For more details on this, refer to the help for the proposal search on input fields.
Example
A database table is modeled as selection method. It provides both the customer numbers as well as the corresponding attributes, such as the name and the address of the customers. The customer number is to be entered on the user interface; the users should also be able to enter the name and the address in the proposal search, in addition to the customer number itself. If a user is searching for customer number 19800417IBW, for example, where only the name (SAP) and the location of the customer (Walldorf) is known to him/her, the parameter name and address of the customer should be modeled as IMPORT or as SPos parameter. On the user interface then, the users can enter 'SAP Walldorf' as a search query, and the proposal search - for example,
19800417IBW SAP AG, Dietmar-Hopp-Allee 16, 69190 Walldorf
is proposed. After the selection of the proposal, the customer number 19800417IBW is automatically adopted into the input field.
History
| Last changed by/on | SAP | 20140117 |
| SAP Release Created in | 740 |
