Abap 7.4 - chapter 12 - classical screens

INFO
STADISTICS
RECORDS
Title of test:
Abap 7.4 - chapter 12 - classical screens

Description:
ABAP 7.4 - Chapter 12 - Classical Screens

Author:
ONKIDONKI
(Other tests from this author)

Creation Date:
18/04/2017

Category:
Others
Click 'LIKE' to follow the bests test of daypo at facebook
Last comments:
No comments about this test.
Make a comment?
Login at daypo to comment the test.
Content:
The ... event is triggered before the screen is displayed, so generally you populate screen fields with default values and set the GUI status and screen title in the ... event block PBO PAI POH POV.
The ... event is triggered when the user performs some action on the screen such as clicking on a button, selecting a menu entry, pressing (Enter), or selecting a function on the screen PBO PAI POH POV.
The ... evens is triggered when the user selects (F1) help for a screen element PBO PAI POH POV.
The ... evens is triggered when the user selects (F1) help for a screen element PBO PAI POH POV.
The ... evens is triggered when the user selects (F4) help for a screen element PBO PAI POH POV.
What is correct to say about Screen Design: (There are three correct answers) The screens for dialog programming are created with the Screen Design Selection screens are created for an executable ABAP program with ABAP declarative statements (i.e., PARAMETERS and SELECT-OPTIONS) to obtain user input for the program You have to define the screen flow logic for selection screens You have to define the screen flow logic for dialog screens Screens in module pools can only be addressed using dialog transactions.
What is correct to say about Screens: (There are three correct answers) You can create screens to be used in any program of type 1 (executable program), M (module pools), and F (function groups) A default next screen is defined in the Screen Painter for all dialog screens, but you can override this dynamically within the program, specifically in the PAI flow logic for the screen The screen flow logic consists of Process Before Output (PBO), Process After Input (PAI), Process on Help-Request (POH), and Process on Value-Request (POV) The screen flow logic must contain at least one PBO event block or one PAI event block POH and POV event blocks are mandatory.
The following are some of the screen attributes required to create a screen: (There are six correct answers) Program.The program type can be 1, M, or F. Short Description Screen number. It can be up to four digits long and must be a unique number within the container program Screen type. (normal screen, subscreen, or dialog box) Next Screen Cursor position Long Description Screen exit conditions.
Selection screen numbers and Screen Painter screen numbers belong to the same namespace, so your dialog screen number cannot be 1000 if your program has a selection screen as well True False.
The next screen number can be dynamically changed within the program to override the statically defined screen number. At runtime the screen number is stored in the system variable. The next screen number can be changed dynamically in the PAI flow logic by the ABAP statement SET SCREEN <screen_no> True False.
Every screen has the 20-character OK field, which is not displayed on the screen and which you must name. The name we usually give it is... The OK field is also referred to as the function code. You need to assign a name to the OK field to use it in the program. You also need to declare a data variable with exactly the same name, of type SY-UCOMM. This way the contents are automatically transported from the screen to the ABAP program OK_CODE OK_DATA OK_RESULT OK_SUBRC.
What is correct to say about the Screen Flow Logic: (There are four correct answers) The screen flow logic is created before the screen attributes and the layout of the screen have been defined Screen flow logic is created in the flow logic editor of the Screen Painter, and you can use ABAP statements directly here Screens have their own set of keywords for use in the PBO, PAI, POH, and POV event blocks You create special module calls in screen flow logic, and it is these modules that contain the ABAP statements Modules are like subroutines for the screens The screen flow logic must contain at least the two statements PROCESS BEFORE OUTPUT and PROCESS AFTER INPUT, and these are created automatically when you create the screen itself.
What is correct to say about Screen Processing: (There are two correct answers) For a screen and its ABAP program to be able to communicate, you have to maintain an internal table, which controls the relation between them You should use ABAP Dictionary structures or program fields to define the screen elements and input/output fields and declare the ABAP Dictionary structure as a work area in the program by using the TABLES statement. The system copies the contents of the screen fields to the corresponding fields in the ABAP work area before the first module in the PAI processing block is executed, unless this transport has been delayed by the use of the FIELD statement.
What is correct to say about the statement FIELD: (There are three correct answers) Used in PAI, PBO, POH, and POV event blocks It must be used in PBO event blocks It can be used with PAI modules for input checks on the screen field The input field against the FIELD keyword will be ready for re-input if the module defined for the FIELD statement issues an error or warning message You can also call the ABAP dialog modules conditionally by using the addition ON INPUT or ON REQUEST with the FIELD statement.
What is correct to say about CHAIN...ENDCHAIN: (There are three correct answers) Can be used to validate user input on a set of fields on a dialog screen You can send an error or warning message from the module that is called using the FIELD statement All of the fields that belong to the processing chain within the CHAIN and ENDCHAIN statement are locked, only the field that has triggered the error is ready for input if an error or a warning message is sent from the module If you use the FIELD statement outside a CHAIN statement, only a single field is made ready for input when a warning or error message is displayed.
What is correct to say about ON INPUT addition for the FIELD statement: (There are two correct answers) Calls the ABAP dialog when the screen field contains a value other than the initial value for that screen field The initial value for the screen field is determined by the data type of the screen field. The initial value is a space ( ) for character fields and 0 (zero) for numeric fields Calls the ABAP dialog module only if the user has entered something in the screen field.
What is correct to say about ON REQUEST addition for the FIELD statement: (There are two correct answers) Calls the ABAP dialog module only if the user has entered something in the screen field The module is executed even if the user enters the initial value for the data type of the screen field or overwrites an existing value with the same value Calls the ABAP dialog when the screen field contains a value other than the initial value for that screen field.
The ON CHAIN-INPUT and ON CHAIN-REQUEST additions work the same way as ON INPUT and ON REQUEST except that the ABAP dialog module is called if at least one field listed in the FIELD statement within the CHAIN statement meets the condition True False.
The AT CURSOR-SELECTION addition calls the ABAP dialog module if the cursor is positioned on a particular screen element True False.
What is correct to say about Screen Processing: (There are five correct answers) Automatic input checks are performed in the PAI event after the data is transferred to the ABAP program The automatic checks are performed based on the screen element attributes If a screen field is mandatory, then the user must enter data before the PAI event block can start If the screen input field refers to an ABAP Dictionary field, then the field-level validation defined in the ABAP Dictionary, such as checks against the check table or domain fixed values, is performed before the PAI processing can start For the menu item of function type E, you have to code the exit logic within the dialog module defined with the addition AT EXIT-COMMAND in PAI You can validate the user input with the screen flow logic by the addition VALUES with the FIELD statement or by checking against a database table.
What is correct to say about field help and value help functions for screen fields: You can use ABAP Dictionary fields for the screen element definition, in which case (F1) help automatically displays the data element documentation You can display data element supplementary documentation for (F1) help if the data element documentation is not sufficient for your application. You can display data element supplementary documentation for (F1) help if the data element documentation is not sufficient for your application You can display (F1) help from the dialog modules by writing your own code. Generally, you can use the function module HELP_ OBJECT_SHOW_FOR_FIELD or HELP_OBJECT_SHOW to display help You use the Functions F4IF_FIELD_VALUE_REQUEST for value help.
What is correct to say about GUI Status and Title Design: (There are five correct answers) The GUI status for a screen consists of the menu bar, a standard toolbar, the application toolbar, and the function key settings and is designed using the Menu Painter tool The GUI title is used to define the title for the screen Each screen should have a GUI status and GUI title A menu bar is made up of individual menus and can have up to eight menus including the System and Help menus The System and Help menus are always present for every screen and have identical functions that can also be modified Each menu can have up 15 entries or functions.
Functions within the menu or toolbars are identified by function codes.The attribute Function Type determines the intended purpose of the function. The function type is also sometimes referred to as a functional type. Connect the Type with the meaning: Blank E T S P.
What is correct to say about Function Codes: (There are two correct answers) A function must be created with dynamic texts For dynamic texts, you have to assign a field to the function, and the contents of the field are displayed as the menu text at runtime The application toolbar can contain up to 20 buttons, or separators You should always define function code type E for your dialog screen and code for those functions in the dialog module that are called within the PAI event block with the addition AT EXIT-COMMAND. This allows users to exit the screen by selecting the function code of type E, without entering the value on mandatory input fields on the screen.
What is correct to say about the GUI status and title: (There are three correct answers) GUI status name can be up to 20 characters long The title text itself can be up to 60 alphanumeric characters long The title appears as the screen heading and can have up to five variables that can be dynamically populated in the program. SET TITLEBAR XXX WITH <&1>...<&5> At runtime the value of the screen title is stored in the system variable SYST-DESC The functions can be deactivated by using the EXCLUDING <fcode> addition with the statement SET PF-STATUS.
What is correct to say about Table Control Programming: (There are three correct answers) A table control has a table header and column headers To define a table control, you have to define the table control area, the table control elements, and the table title for the table control You also need to declare the table control in the program The syntax for the table control in the program is as follows: CONTROLS flights TYPE TABLEVIEW USING SCREEN 100 The table control name is flights, and it is created on screen number 100. The table control name in an ABAP program should be identical to the table control created on the screen.
What is correct to say about Screen Flow Logic for Table Control: (There are three correct answers) You must use the LOOP ... ENDLOOP statement in the PBO event block in the screen flow logic, you must implement in the PAI just for programs that allow changes in the table lines. This statement is required for each table control on your screen It is required to copy the data back and forth from the ABAP program to the table control fields and vice-versa The table control must be declared in the ABAP program for each table control defined on the screen The ability to scroll using a scroll bar is manually implemented and managed by the program.
What is correct to say about Modifying Screens Dynamically: (There are two correct answers) SCREEN is an internal table with the header line, and you do not need to declare this in the program You can see this table in the Debugger, and you can only access it through its header line You can modify the attribute of the screen element in an ABAP program during the PBO event block.
Which of the following is correct? The screen attributes can be modified in the PROCESS AFTER INPUT event block. The screen attributes can be modified in the PROCESS BEFORE OUTPUT event block The screen attributes can be modified in the PROCESS BEFORE OUTPUT and PROCESS AFTER INPUT event blocks None of the above.
The static sequence of the default next screen can be established by the value in the screen attribute Next Screen True False.
If you enter the value “0” or blank (“ ”) as the next screen, then the system resumes processing from the point at which the screen was initiated, assuming the Next Screen attribute is overridden dynamically in the program True False.
The Next Screen attribute can be temporarily overwritten by the set screen statement (that is, SET SCREEN 200) True False.
The FIELD statement does not have any effect in the PBO event block, and it should not be used in the PBO event block True False.
The FIELD statement with the ON INPUT addition is used to conditionally call the ABAP dialog module. The ABAP dialog module is called if the value of the screen field is other than the initial value True False.
The FIELD statement with the ON REQUEST addition calls the ABAP dialog module if any value is entered in the screen field True False.
You can call a module for the FIELD statement to validate user entry on the input field. You can validate the entry on the input field and send an error or a warning message from an ABAP dialog module True False.
If an error or warning message is sent from the ABAP dialog module for the FIELD statement within the CHAIN and ENDCHAIN statements, then all of the fields within CHAIN and ENDCHAIN are ready for user input again True False.
The user interface consists of the GUI status and GUI title: True False.
At most, a menu bar can have 10 menus: True False.
At most, how many buttons can the application toolbar have on the screen? 20 30 10 35 None of the above.
At most, how many menu items (including functions, separators and sub-menus) can a menu have on the screen? 15 10 20 None of the above.
The data is transferred and displayed on the screen after the processing of the PBO: True False.
Which statement will interrupt the processing of the current screen and branch to new screen? CALL SCREEN <NNNN> LEAVE TO SCREEN <NNNN> SET SCREEN <NNNN> None of the above.
Report abuse Terms of use