Thursday, August 7, 2014

Module Pool Programming Interview Questions in SAP ABAP

Interview Questions on Module Pool Programming in SAP ABAP
Welcome to SAP ABAP Interview Questions and Answers. Module Pool Programming Interview Questions and Answers. 

Dialog programming interview questions, Interview questions on module pool programming in SAP ABAP, Real Time Interview Questions Part-2. 

This post consist of Dialog Programming Real Time Questions for the all levels of interviews on SAP-ABAP Programming. Dialog Programming is a special type of programming in SAP ABAP. Dialog programming (Module pool) is used to create custom SAP screens as per business requirement. Dialog programs are executed using T-codes. Click on read more to read the questions.




Module Pool Programming Interview Questions


Dialog Programming is a special type of programming in SAP ABAP. Dialog programming (Module pool) is used to create custom SAP screens as per business requirement. Dialog programs are executed using T-codes.


Interview questions on module pool programming



1)What is "at exit-command"?


The flow logic Keyword at EXIT-COMMAND is a special addition to the MODULE statement in the Flow Logic .AT EXIT-COMMAND lets you call a module before the system executes the automatic fields checks.




2)Which Function type has to be used for using “at exit-command” ?


To Use AT EXIT – COMMAND, We must assign a function Type “E” to the relevant function in the MENU Painter OR Screen Painter.




3)Of the two “ next screen “ attributes the attributes that has more priority is ---. 


Dynamic. 




4)Navigation to a subsequent screen can be specified statically / dynamically.  (TRUE/FALSE).

  
TRUE. 



5)Dynamic screen sequence  for a  screen can be set using ------------- and ----------------- commands

          
Set Screen, Call screen.



6)The commands through Which an ABAP/4 Module can “branch to “ or “call” the next screen are


a).------------,b)--------------,c)---------------,d) ------------.



a. Set screen<scr no>,


b. Call screen<scr no> ,


c. Leave screen, 


d. Leave to screen <scr no>.




7)What is difference between SET SCREEN and CALL SCREEN?


This statement sets the screen with the screen number specified in dynnr, as the next screen for processing of the current screen...If we want to branch  to the next  screen without finishing  the current one ,use LEAVE SCREEN. 

With CALL SCREEN , the current (calling) chain is suspended , and a next screen (screen chain) is called .The called can then return to the suspended chain with the statement LEAVE SCREEN TO SCREEN 0.



8) Can we specify the next screen number with a variable (*Yes/No)?


a. Yes




9) The field SY-DYNNR refers to-------------- 


Number of the current screen.




10) The Syntex used to call a screen as dialog box (pop up)is---------


       CALL SCREEN <screen number.>


       STARTING AT <start column><start line> 


        ENDING AT <end column> <end line>.




11) What is “call mode”?


In the ABAP/4  WORLD each stackable sequence of screens is a “call mode”, This is IMP because of the way u return from the given  sequence .To terminate a call mode and return to a suspended chain set the “next screen” to 0 and leave to it:




12) The max number of  calling modes stacked at one time is?


a.NINE




13) What happens if only one of the commands SET SCREEN and LEAVE SCREEN is used without using the other?


If we use SET SCREEN without LEAVE SCREEN, the program finishes processing for the current screen before branching to <scr no>.  


If we use LEAVE SCREEN without a SET SCREEN before it, the current screen process will be terminated and branch directly to the screen specified as the default next-screen in the screen attributes.




14) What is the significance of the screen number ‘0’?


In “calling mode”, the special screen number 0 (LEAVE TO SCREEN 0) causes the system to jump back to the previous call level.  


That is, if you have called a screen sequence with CALL SCREEN leaving to screen 0 terminates the sequence and returns to the calling screen.  If you have not called a screen sequence, LEAVE TO SCREEN 0 terminates the transaction.




15) What is the significance of the memory table ‘SCREEN’?


At runtime, attributes for each screen field are stored in the memory table called ‘SCREEN’.  We need not declare this table in our program.  The system maintains the table for us internally and updates it with every screen change.




16) Why grouping of fields is required? What is the max no of modification groups for each field?


If the same attribute need to be changed for several fields at the same time these fields can be grouped together.  We can specify up to four modification groups for each field.




17) What is a screen group? How it is useful?


Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. 


This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.




18) What is a Sub screen? How can we use a Sub screen?


A subscreen is an independent screen that is displayed in an area of another (“main”) screen.  To use a subscreen we must call it in the flow logic (both PBO and PAI) of the main screen.  


The CALL SUBSCREEN statement tells the system to execute the PBO and PAI events for the sub screen as part of the PBO or PAI events of the main screen.  The flow logic of your main program should look as follows:


PROCESS BEFORE OUTPUT.


CALL SUBSCREEN <area> INCLUDING ‘<program>’ ’<screen>’.


PROCESS AFTER INPUT.


CALL SUBSCREEN <area>.




19) What are the restrictions on Subscreens?


• Set their own GUI status


• Have a named OK code


• Call another screen


• Contain an AT EXIT-COMMAND module


• Support positioning of the cursor.




20) How can we use / display table in a screen?

    
TABLE CONTROLS and STEP LOOPS.



21) What are the differences between TABLE CONTROLS and STEP LOOPS?


1) TABLE CONTROLS are simply enhanced STEP LOOPS that display data,but from a  programming accepts, TABLE CONTROLS and STEP LOOPS are almost the same.



2) One major difference between STEP LOOPS and TABLE CONTROLS is , in STEP LOOPS their table rows can span more than one line on the screen.  In TABLE CONTROLS the rows are always single lines, but can be very long and they are scrollable. 



3) The structure of table controls is different from step loops.  A step loop, as a screen object, is simply a series of field rows that appear as a repeating block.  A table control, as a screen object consists of :  

 i )  table fields ( displayed in the screen )   


 ii )  a control structure that governs the table display and what the user can do with it.




22) What are the dynpro keywords?

    
FIELD, MODULE, SELECT, VALUES and CHAIN are the dynpro keywords.



23) Why do we need to code a LOOP statement in both the PBO and PAI events for each table in the screen?


We need to code a LOOP statement in both PBO and PAI events for each table in the screen.  


This is because the LOOP statement causes the screen fields to be copied back and forth between the ABAP/4 program and the screen field.  For this reason, at least an empty LOOP….ENDLOOP must be there.




24) How can we declare a table control in the ABAP/4 program?

    
  Using the syntax controls

 <table control name> type tableview using screen <scr no>.




25) Differentiate between static and dynamic step loops.


   Static step loops have a fixed size that cannot be changed at Run time.  Dynamic step loops are variable in size.  


If the user re-sizes the window the system automatically increases or decreases the number of step loops blocks displayed.




Click Here For : 



"You found the information helpful and want to say thanks? Your donation is enough to inspire us to do more. Thanks a bunch!"

0 comments:

Post a Comment

Note: Only a member of this blog may post a comment.

Categories

ABAP (1) ABAP Interview Questions (112) ABAP Open SQL Statements (1) ABAP Syntax Rules (6) ABAP WORKBENCH (2) ABAP-Interview-Questions (52) ALE IDOC (6) ALE IDOC Interview Questions (6) ale-idoc (6) ALE-IDOC-Interview-Questions (19) ALV Interview Questions (5) ALV-Interview-Questions (22) BADI (2) BAPI (1) BAPI Interview Questions (1) BAPI-Interview-Questions (14) BDC (6) BDC Interview Questions (6) BDC-Interview-Questions (9) Classical Reports Interview Question (3) Classical-Reports-Interview-Questions (22) Conditional Statements (1) Cross Applications (3) Cross-Applications (14) Data Dictionary (22) Data Type Questins (1) Data types (1) Data-Dictionary (48) Data-Type-Questins (6) Dialog programming (5) Dialog Programming Interview Questions (4) Dialog-Programming (30) DOMAIN Interview Questions (1) Domain-Interview-Questions (8) Function Module (2) IDoc Tutorials (6) Interactive Report Interview Questions (4) Interactive-Reports-Interview-Questions (22) Internal Tables (1) Lock Object Interview Questions (1) Lock-Objects-Interview-Questions (10) Logical Database (1) Modularization Interview Questions (4) Modularization-Interview-Questions (25) Module Pool Programming (5) Module-Pool-Programming (39) Object Oriented ABAP (19) Object Oriented ABAP Interview Questions (15) object-oriented-abap (2) Object-Oriented-ABAP-Interview-Questions (34) OOABAP (9) Reports (14) Reports Interview Questions (9) Reports-Interview-Questions (19) RFC (1) RFC Interview Questions (1) RFC-Interview-Questions (14) RICEF (1) RICEF Objects (1) SAP (2) SAP ABAP (2) SAP ABAP Interview Questions (42) SAP ABAP Introduction (46) SAP ABAP Message Types (2) SAP BADI Interview Questions (2) SAP Basics (71) SAP Books (2) SAP Certification (1) SAP CONSULTANTS (5) SAP CRM (1) SAP ENHANCEMENTS (3) SAP EXITS (2) SAP EXITS ( SAP ENHANCEMENTS ) Interview Questions (1) SAP Free Books (1) SAP HR (2) SAP Lock Object (1) SAP Open SQL Statements (1) SAP R/3 Architecture (4) SAP Search help (1) SAP Smartforms (1) SAP Smartforms Interview Questions (2) SAP Tables (5) SAP Tcodes (10) SAP Views (1) SAP Webdynpro ABAP (12) SAP Work Processors (2) SAP Workflow (3) SAP-BADI-Interview-Questions (11) SAP-Enhancements (39) SAP-Exits (39) SAP-Exits-Enhancements-Interview Questions (3) SAP-HANA (1) SAP-HANA-Interview-Questions (1) SAP-Smartforms-Interview-Questions (2) SAP-Workflow (3) Scripts (3) Scripts Interview Questions (2) Scripts-Interview-Questions (32) Search Help Interview Questions (1) Search-Help-Interview-Questions (9) Smartforms (1) Table Maintenance Generator (1) Table-Maintenance-Generator (4) Tables in SAP (2) Tables Interview Questions (3) Tables-Interview-Questions (3) Type Group Interview Questions (1) Type-Group-Interview-Questions (7) Variable Declaration (1) Views Interview Questions (1) Views-Interview-Questions (5) Webdynpro (12)

Protected Blog

 
This blog is not affiliated to SAP AG |SAP is trademark of SAP AG |The information collected from various sources use information with your own risk.