Extending the Selection Criteria 

On the Selections screen, you can choose the selection criteria you require when executing the query. If, for example, you select the field Flight connection code, you can specify in the program selections area that you only want to display flights with certain flight numbers.

If you want to make an additional selection for a field, you must select it on this screen. As a result, the selection screen is extended by one selection criterion for this field. You can also change the text for this selection criterion if you do not like the text proposed by the query.

Texts for selection criteria can only be changed after the appropriate field has been selected and Enter chosen.

You should use selection criteria of this type only if they cannot be implemented using dynamic selections. The advantage of dynamic selections is that the number of database accesses is reduced.

In our example (selection by Flight connection code), you should use dynamic selections since they are supported by the logical database.

If selection criteria are defined for InfoSet fields and local fields and these fields contain character strings (type C), then the ABAP Dictionary definition of this field determines whether case sensitivity is maintained when the selection criteria are input or if all input values are converted to capital letters (uppercase).

With additional fields and local fields whose data type definitions do not use a LIKE reference to a Dictionary field, that is with fields that have no Dictionary reference, all input values were previously capitalized by default. This meant that selections based upon case sensitivity, upon a mixture of upper and lowercase letters, could not be made in the past.

From Release 4.5A, the selection criteria for those character strings with no ABAP Dictionary reference are no longer automatically converted to capital letters. This means that when inserting selection criteria, you must now pay attention to the exact manner in which they have been written.