Attribute Types of Select Options
The attribute type specifies how the value assignment of an attribute is rendered and which operators are used for this type. Method GET_DEFAULT_OPERATOR of class CL_WD_SELOPT_UTIL_20 returns the operators defined for an attribute type.
The constants for the attribute types are defined in IF_WD_SELECT_OPTIONS_20=>E_ATTRIBUTE_TYPES.
The table below lists the default operators that are used in a specific field type, and describes the format of the attributes:
|
Attribute or Field Type |
Default Operators |
Output |
|---|---|---|
| FREE_TEXT (free text search) |
|
An attribute of type if_wd_select_options_20=>e_attribute_types-free_text is always output as the first line, with a label and without a dropdown menu. The text for the label (type: String) can be specified in the TEXT attribute. If no text table is entered, a standard text is used. If you have defined is as the only operator, the operator dropdown menu is not displayed. This attribute cannot be removed from the user interface, which means that no minus sign appears at the end of the line. The user can assign only one value. |
| TEXT (text field) |
|
Output as an input field |
| ID (ID field (alphanumeric field, contains numbers) |
|
Output as an input field for alphanumeric values Possible for alphanumberic fields that use number strings |
| NUMBER (numeric field) |
|
Output as an input field for numeric values Use operators is_not_between, top_number, top_percent, top_sum, bottom_number, bottom_percent, bottom_sum for applications that use the Business Warehouse systems. You define the explicit use of these operators in interface IF_WD_SELECT_OPTIONS_20 with component INCLUDE_OPERATORS / EXCLUDE_OPERATORS of structure WDR_SO_S_ATTRIBUTES. |
| DATE_TIME (date or time field) |
|
Used as an input field for dates or times. |
| VAR_DATE (variable date) |
|
Rendered as a dropdown. The type includes the option of the operator-dependent value set. The operators and the corresponding value sets must be specified in table VAR_DATE_ATTRIBUTES. |
| REL_DATE (relative date) |
|
Rendered as an input field In addition to inputting a direct date, relative dates like “today” or “current calendar year” can be used. Input help for the attribute type contains relative dates in a dropdown and the date navigator. The possible relative data must be made available in the substructure REL_DATE in the attribute definition. |
| DROPDOWN (field with dropdown menu) |
|
Rendered as a dropdown. The dropdown is always rendered as NULLABLE, which means that an additional empty line is created in the value set. The value set may contain the initial value as the key. The user evaluation can then be read as follows: If the user has selected the empty entry, the evaluation is:
If the user has selected the key with the initial value, the evaluation is:
The operator is_between is not valid in this scenario. |
| CHECK and TRISTATE (checkbox and tristate) |
|
Output as a checkbox with two or more statuses (Tristate). These types should be avoided since the rendered lines are always regarded as evaluated. |
| CURR_QUAN (amounts or quantities) |
|
The DDIC types QUAN and CURR are output in one line with their respective unit specifications. Other types are not supported. |
| CUKY_UNIT (currrency or unit) |
|
Not output as a separate attribute, but together with the associated quantity or amount field. |
| MULTI_VALUE (multi-value field) |
|
Output as an editable input field (TextEdit), and is write-protected in accordance with the guidelines (READ_ONLY). You can edit the field using an application-specific popup, which is opened from the edit button. For more information about multi-value fields, see Defining Multi-Value Fields. |
| TOKEN |
|
User input is the same as with an input field (including F4 help). The value entered is validated by the application, and together with the description text displayed as a token. For more information about token fields, see Defining Tokens. |
More Information
Some field types have complex properties or require special handling. For more information, see Properties and Handling of Specific Attribute and Field Types.