To create a parameter, proceed as follows:
Choose Selections in the InfoSet maintenance screen.
In the dialog box that appears, determine whether you are defining a parameter or a selection criterion and enter a name for the selection containing up to eight characters.
Define the parameter.
By specifying a sequence on the selection screen, you can determine the arrangement of the parameters. This is generally in ascending order. If two parameters have the same sequence specification, the order in which they appear on the selection screen is uncertain.
The sequence number applies equally to parameters and selection criteria.
The text you enter on the Description line serves as documentation and should describe the selection criterion as well as possible. It should describe the parameter. The Selection text appears on the selection screen of every query report within that InfoSet. If you do not enter a selection text, the system uses the description as the selection text.
When defining parameters, you have the same options as when you define additional fields.
If you want to assign attributes such as type and length specifications to the parameter, use the field Additns. There, you can specify all the additions allowed with the ABAP statement PARAMETERS. If required, you can use several additions, one after the other.
The system then performs a syntax check.
For every selection that is defined in the InfoSet or retrievd by the logical database, you can make a code for the time AT SELECTION-SCREEN to carry out checks. To do this, place the cursor on a selection in the overview screen for the existing selections and choose the function check code for element .
Coding at the AT SELECTION-SCREEN has to be decided upon separately for each selection. When a query report is generated, a check is made to ensure that the check coding for all selections is collected together in AT SELECTION-SCREEN and that only the selections that appear on the screen are referred to.
You should also evaluate parameters that you define. A typical example would be CHECK <parameter> to evaluate parameters in a GET event, in order to allow only certain table lines to be processed.