ABAP Keyword Documentation → ABAP − Reference → SAP GUI User Dialogs → General Dynpros → Input Checks
Automatic Input Checks
In the PAI event, the dynpro makes a series of automatic input checks. These checks take place before data transports to the ABAP program and before the dynpro flow logic is processed. Before these automatic input checks, a single dialog module can be called using an unconditional module call and with a special function type. This dialog module is usually used to bypass the checks and exit the dynpro 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 input and trigger PAI again. The actual PAI processing does not start until there are no more errors.
The automatic input checks run in the following order:
- Mandatory input
- Input format
- Checks defined in ABAP Dictionary
- Does the entered value match any foreign key relationship with a different database table? This means the check table is checked to verify whether the input value exists as a foreign key in the check table. This check only takes place, however, if the foreign key attribute is set for the input field in Screen Painter. This input check is not necessarily identical with the input help. The developers in question must ensure that the input help represents a subset of the content of the check table.
- Does the entered value exist as a fixed value of the domain of the field? This means that the definition of the domain of the field in ABAP Dictionary is checked. The fixed values of the domain can also be used as an input help. The value table of a domain, however, is not checked. It is only used as a default value for the check tables of the fields that reference the domain.
Other versions:
7.31 | 7.40 | 7.54