Get Example source ABAP code based on a different SAP table
ID DYNPRO% • SET PF-STATUS - dynpro ABAP Statement
SET PF-STATUS>, Dynpro Short Reference >
ABAP_SYNTAX SET PF-STATUS status $[OF PROGRAM prog$] $[EXCLUDING fcode$].>
ABAP Addition 1 ... OF PROGRAM prog> 2 ... EXCLUDING fcode>
What does it do? In dynpro> processing, this statement defines the GUI status> specified in status> for the subsequent screen layouts>. The components of the set status are active in the user interface from the next time a screen layout is sent and remain active until the end of the program or until the next SET PF-STATUS> statement. The name of the current GUI status can be read from the system field sy-pfkey >. status> expects a character-like data object that contains either the name of the GUI status of the main program> of the current program group> , or the program specified in uppercase or only blanks in prog>. If the status is not available, an empty status is displayed in which no control elements are active except for the predefined system functions. Of these functions, only the Enter> key, to which an empty function code is assigned in this case, raises the event PAI>. If the data object status> contains only blanks, the standard list status> is set and the additions have no effect.
Latest notes:
The GUI status of a dynpro must be set at the latest during the event PBO>. If no GUI status is set for a dynpro, the empty status described above is used.
If the set GUI status contains dynamic function texts, the function texts are read from the assigned global data objects of the program in which the GUI status is defined. If these do not exist, question marks (?) are displayed. For dynamic function texts, an explicitly specified program prog> is loaded into the current program group> if it does not already exist in the ABAP_ISESS >. This enables access to its global data objects.
The statement SET PF-STATUS> has a variant for the GUI status of lists>.
There is no guarantee that the statement SET PF-STATUS> will work at PBO> for the selection screen>. This statement should no longer be used for selection screens.