Skip to main content

YCLASSICAL_JOINING

*&---------------------------------------------------------------------* *& Report  YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT   yclassical_joining  NO   STANDARD   PAGE  HEADING                               LINE - SIZE   110                               LINE - COUNT   255                               MESSAGE - ID  zsan. ** T Y P E    D E C L A R A T I O N ** TYPES  :  BEGIN   OF  ty_mara,          matnr  TYPE  matnr,          ernam  TYPE  ernam,          pstat  TYPE  pstat_d,          END   OF  ty_mara,          BEGIN   OF  ty_makt,          matnr  TYPE  matnr,          spras  TYPE  spras,          maktx  TYPE  maktx,          END   OF  ty_makt,          BEGIN   OF  ty_final,          matnr  TYPE  matnr,          ernam  TYPE  ernam,          pstat  TYPE  pstat_d,          maktx  TY

What are The Events in Module Pool Programming

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)
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

Popular posts from this blog

ALV Field Catalog in SAP ABAP

ALV Field Catalog in SAP ABAP Field Catalog Field catalog is an internal table which is used to pass a list of fields to display in ALV report, we can set different properties to fields that will be display in ALV output. Type Group It is a data dictionary object which contains all the reusable user-defined types. Example for a type group is SLIS, which contains all the user-defined types for developing ALV reports. TYPE-POOLS is a keyword which is used to assign the type-group to a ALV report . Syntax : TYPE-POOLS SLIS . DATA : <IT_FCAT> TYPE SLIS_T_FIELDCAT_ALV . "INTERNAL TABLE FOR FIELD CATALOG DATA : <WA_FCAT> TYPE SLIS_FIELDCAT_ALV . " WORK AREA FOR FIELD CATLOG Field catalog types Field catalog: Field catalog is a format description of the display area. There are three procedures to build a FIELD CATALOG. 1. Automatic field catalog. 2. Semi-automatic field catalog. 3. Manual field catalog. Automatic field catalog. If the list structure has