In the PAI event, the screen makes a series of automatic input checks. These are carried out before any data is transferred to the ABAP program, and before the screen flow logic is processed. Before the automatic input checks, you can call a single dialog module unconditionally using a special function type. You normally use this dialog module to bypass the checks and leave the screen directly.
If the automatic input checks find an error, a message appears in the status bar of the screen, and the corresponding fields remain ready for input. The user must correct the entries and trigger the PAI again. The actual PAI processing does not start until there are no more errors.
The automatic input checks run in the following order:
If a field is defined as a mandatory field in the Screen Painter, the user must enter a value for it before the PAI processing can start.
The values entered in the input fields on the screen must correspond to the data format of the corresponding screen field. For example, the format of a date field (type DATS) is eight characters and has the format YYYYMMDD. All of the characters must be numeric. MM must be 12 or less, and DD must be 31 or less. The system also checks that the specified day is valid for the month.
If you create an input field in the Screen Painter by copying an ABAP Dictionary field, the screen checks whether:
· The value satisfies any foreign key relationship to another database table, that is, the system checks whether the value is contained in the check table as a foreign key. This is only checked if the Foreign key attribute is set in the Screen Painter for the input field. The input check is not necessarily identical with the input help. The programmer is responsible for ensuring that the input help presents values that will all pass any foreign key check.
· That the value is one of the fixed values of the domain of the fields, that is, the system checks the definition of the underlying domain in the ABAP Dictionary. The fixed values of the domain can also be used as input help. However, the value table of a domain is not checked. It is only used as a default value for the check tables of the fields that refer to the domain.
Automatic input checks
DATA: ok_code TYPE
date TYPE d.
CALL SCREEN 100.
SET PF-STATUS 'STATUS_100'.
MODULE cancel INPUT.
MODULE pai INPUT.
MESSAGE i888(sabapdocu) WITH text-001.
The next screen (statically defined) for screen 100 is 100. It has the following layout:
The date field date from the program is assigned to the input field Date. The other input fields are the CARRID; CONNID, and MARK components of the ABAP Dictionary structure DEMO_CONN. All of the fields are mandatory. The function code of the pushbutton is EXECUTE.
In the GUI status STATUS_100, the icon (F12) is active with function code CANCEL and function type E. Furthermore, the function key F8 is assigned to the function code EXECUTE.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE cancel AT EXIT-COMMAND.
The user must fill all of the input fields with valid values before the PAI module can be called:
· All of the input fields must contain values
· The date entry must have the correct format
· The airline must be in the check table SCARR
· The flight number must exist for the corresponding airline in the check table SPFLI
· The selection MARK must be one of the fixed values of the domain S_FLAG.
The user can leave the screen using Cancel (, F12) without entering all values correctly, since the module call is programmed using AT EXIT-COMMAND.