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 | DDAUTOSUGGEST |
| Short Description | Proposal Search for Input Fields |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DDAUTOSUGGEST | |
| 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 | 10 | Word Supp. |
| Medium | 20 | Autom.Word Supplem. |
| Long | 30 | Automatic Word Supplementation |
| Heading | 0 |
Documentation
Definition
The proposal search enables you to display the input help in a dropdown box already at the time when you enter one or several search terms in the input field, without your having to explicitly call the search help dialog - for example, using the F4 key. In this way, the requested value can be selected directly from the dropdown box. The values are displayed in the same way as a list generated on the basis of the modeled LPos parameters - in the respective order and in tabular form. Exception: The values of the parameter that belongs to the input field on which you performed the search function are always displayed in the first column of the dropdown box, irrespective of the LPos value. All the other parameters follow then in accordance with their LPos value.
If only this field is set, or if the option "Full Text Fuzzy Search" is not supported by the database used by the system, the full text search is executed solely on the column of the database that belongs to the field or the assigned search help parameter. In addition, additional selection conditions for other columns of the table(s) or view will only be taken into consideration if these are modeled as additional IMPORT parameters in the search help and if values are stored for them in the user interface or stored as default values in the search help.
Use
In many cases, a search help can be used without further modifications for the proposal search. However, as a rule, the parameter for the field where the proposal seach is to function correctly should be modeled as an IMPORT parameter of the search help.
Furthermore, this setting should only be activated if the search help is modeled in such a way that 10 search results (default setting for the proposal search) can always be determined within a maximum of one second. If complex selection conditions (for example, many IMPORT and/or SPos parameters) are modeled or long-running operations are implemented in search help exits, this search help should first be tested for its runtime behanvior before this functionality is activated.
Dependencies
This functionality must be supported by the corresponding user interface technology (for example, Dynpro, Web Dynpro, and so on). If necessary, further adaptations will need to be performed on the respective user interface in order that the proposal search is activated on the input field where this search help is used. You will find details on this in the documentation for the respective user interface technology and in Note 1861491.
Example
A search help determines the IATA codes of airports on the basis of the values stored in Table SAIRPORT. If the proposal search is activated for the corresponding search help, immediately after you have entered the letter 'F' all the available IATA codes in the system that begin with 'F' will be displayed in the dropdown box, as in this example:
FCO Rome Leonardo Da Vinci, I
FRA Frankfurt/Main, FRG
History
| Last changed by/on | SAP | 20140117 |
| SAP Release Created in | 740 |
