Get Example source ABAP code based on a different SAP table
General Dynpros Dynpro is an abbreviation for Dynamic Program. A dynpro is a repository object and is always a component of an ABAP program (a function pool, executable program, or module pool). It consists of a screen layout with its screen elements and the dynpro flow logic. Dynpro fields are assigned to the screen elements. The flow logic contains processing blocks for events that are raised before a screen layout is sent, and after user actions on the displayed screen layout. General dynpros are edited using the Screen Painter tool. Special dynpros, such as selection screens and lists, are generated from ABAP statements. The dynpros in a single ABAP program can be combined to form dynpro sequences. Individual dynpros or dynpro sequences can be called either using a transaction code from outside the ABAP program or by using the statement CALL SCREEN in the associated ABAP program. Once a dynpro or dynpro sequence is called, the control of the execution of the ABAP program is passed to the flow logic of the dynpro. Dynpro sequences can be defined dynamically by setting the next dynpro attribute for a dynpro dynamically in the ABAP program. The screen flow logic is divided into the Process Before Output ( PBO) event, which is processed before the screen is displayed, and the Process After Input (PAI) event, which is processed after a user action on the screen. The following diagram shows the position of dynpros between the GUI status and the ABAP program: IMAGE DYNPRO_POSITION.png 678 543 The dynpro flow logic calls dialog modules in the ABAP program, either to prepare the screens for display (PBO event) or to process the user's entries (PAI event). Dynpros are dynamic programs and have their own data objects, called dynpro fields. These are associated with the input/output fields that appear on the screen itself. When the screen is displayed and exited, data is passed between dynpros and ABAP programs on the basis of the matching names of dynpro fields and data objects in the ABAP program. Each screen has a GUI status, containing a menu bar, standard toolbar, and an application toolbar. Like dynpros, GUI statuses are independent components of the ABAP program. They are created in the Menu Painter. GUI statuses are assigned to dynpros dynamically in ABAP programs. Each dynpro is associated with the current GUI status using a special dynpro field to which the corresponding function code is passed whenever user actions are performed on the GUI status. The dynpro passes the function code to the ABAP program where it can then be evaluated, just like any other dynpro field. The following subtopics are covered in this section:
User Interface
Screen and Screen Elements
Dynpro Fields
Dynpro Flow and Dynpro Sequences
Input Checks
Field Help, Input Help, and Dropdown List Boxes
Statements in the Dynpro Flow Logic
ABAP Statements for Dynpros
Latest notes: The classic dynpros described here are considered obsolete by SAP for application programs. For new developments, only SAPUI5 or Web Dynpro should be used. ABAP_HINT_END
