*&---------------------------------------------------------------------* *& Report YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT yclassical_joining NO STANDARD PAGE HEADING LINE - SIZE 110 LINE - COUNT 255 MESSAGE - ID z...
What are The Events in Module Pool Programming
Dialog(Dynpro) programming Controls the multiple screens which are integrated hierarchically to the main program(Transaction) and they are executed in a sequence. The main elements of the module pool Programming are
Screens
Module pools
Subroutines
Menus
Transactions
Events in Module Pool Programming(Dialog programming)
Module pools
Subroutines
Menus
Transactions
Events in Module Pool Programming(Dialog programming)
In the PAI event, all of the Data from the screen is transported to the ABAP program when the automated input checks and before the primary PAI module is termed.
At the top of the last PBO module, and before the screen is displayed, all of the Data is transported from the ABAP program to any identically-named fields within the screen.
Data is transported between the screen and therefore the ABAP program at the start and finish of every dialog tread the appliance server.
There are four event blocks, each of which is introduced with the screen keyword PROCESS:
PROCESS BEFORE OUTPUT (PBO) is automatically triggered after the PAI processing of the previous screen and before the current screen is displayed. You can write source code in this block.
PROCESS AFTER INPUT (PAI) is triggered when the user chooses a function on the screen. You can write source code program the PAI processing of the screen in this block.
PROCESS ON HELP-REQUEST (POH) is triggered when the user requests field help (F1) or possible values help (F4) respectively.
PROCESS ON VALUE-REQUEST (POV) is triggered when the user requests field help (F1) or possible values help (F4) respectively
Comments
Post a Comment