Module Pool/Dialog Programming - SAP ABAP

-

Dialog programs

  • are also known as transactions.
  • allows us to create and update the data.
  • are accessed through the SAP GUI and Web also.
  • Users can navigate between screens to interact with the SAP ERP system.
  • The screens will be created by using Abap workbench tool Screen Painter (SE51) OR we can create screens using transaction SE80 also.

A dialog program must always have

  • A user friendly interface
  • Various checks or validations to ensure valid data entry
  • Proper messages as warnings, information or errors
  • Help while entering data in the form of matchcodes, parameter ids, F4 help.
  • Database access for displaying and storing data

Components of screen

The various objects of a dialog program include the following

  • Screens
  • Screen flow logic
  • GUI Status
  • ABAP Program
  • Transaction code
  • Dynpro
  • Dialog step

         Module pool events (All events are available in Flow logic of screen) 
  • The following four screen events that are triggered when a screen is processed:  
    1.Process before output (PBO)
    A PBO event is triggered before showing the screen to the user. We use this event to prepare the screen, such as by assigning default values or dynamically displaying/hiding certain fields on the screen.  
    2.Process after input (PAI)
    A PAI event is triggered after showing the screen to the user, when the user performs any action on the screen. This event allows you to respond to user actions on the screen.  
    3.Process on help request (POH)
    A POH event is triggered when the user selects (F1) (or field) help for the screen field. We use this event to provide field help for the screen field.  
    4.Process on value request (POV)
    The POV event is triggered when the user selects (F4) (or input) help for the screen field. We use this event to provide input help for the screen field.

  • All four screen events listed are maintained with their respective event statements.
  • Dialog modules are called from within the event block using the MODULE statement.
  • The dialog modules that are called from the screen flow logic should be maintained between the MODULE...ENDMODULE statements in the main program to which the screen belongs.

Comments

Post a Comment

Popular posts from this blog

SAP ABAP-Internal Table Operations and Example Program

-
Image
Internal Table Operations: Below are the Operations of Internal Table Append Insert Delete Modify Describe Sort Refresh Clear Free Loop … Endloop Read Table   1.Append   - to append the workarea record at the last position of internal table. we can append:   a. single record   b. multiple records a. single record (one -> Many / Workarea-> Internal table) Syntax:   APPEND <WORKAREA NAME> TO <INTERNAL TABLE NAME>. Example:    wa_data-PATIENTID               = 9999.    wa_data-PATIENTNAME    = 'Addition1'.    wa_data-HOSPITALNAME = 'Alpha Hospital'.      APPEND wa_data to IT_DATA.    CLEAR wa_data.     b. Multiple records (Many->Many / Internal table1 to internal table2) Syntax: APPEND LINES OF <Internal table name1> to <Internal table name2>. Note: While appending 1 internal table data with another interna
Read more

HR ABAP Interview Questions and Answers

-
1)        Difference Between ABAP & HR-ABAP ? ABAP and HR-ABAP are almost similar but HR-ABAP has some different approach to program like logical      database (like PNP & PCH) are extensively used in HR-ABAP. Infotypes and Infotypes related tables are used in HR-ABAP. Some specific comments like provide ...endprovide are used in HR-ABAP but not generally in ABAP. 2)        Infotype ? The data fields of HR master data, time management and recruitment are grouped logically into information types or infotypes for short. Examples of infotypes are "Family/Related Person", "Organizational Assignment, "Basic Pay". Infotype Category’s: o     Infotypes 0000 - 0999 - HR master data   and sometimes for applicant data o     Infotypes 1000 - 1999 - organizational management o     Infotypes 2000 - 2999 - time data o     Infotypes 4000 - 4999 - applicant data o     Infotypes 9000 - 9999 - customers 3)        Subtype ?   Subtypes are
Read more

BDC (Batch Data Communication) - SAP ABAP

-
Image
BDC (Batch Data Communication) Batch input is a standard technique used to transfer large volumes of data into an SAP system. The advantage of batch input is that all the transaction-level checks can be performed on the data and then the data is updated through the transactions (Via Screens). Data transfer project involves the following steps:  1. Identifying the data that needs to be transferred to the SAP. 2.Record the screen fields using transaction: SHDB & generate a program from it. 3. Write the BDC program separately by making use of Recoding code (Step no:2) 4. If required, Convert the data while passing from Non-SAP to SAP (External to Internal). 5. Handle various errors/messages in program as per requirement. 6.Validate the data while processing. 7 . Process the program and verify the transferred data in SAP. 8. Set the data transfer frequency as per business requirement. Note: Batch input programs allow us to capture all t
Read more