TAW12 - Week 2

1 of 133

format Check Obligatory Field Check Fixed Values Foreign Key Check Parameter Id Validation

2 of 133

OK_CODE is a system reserved variable and cannot be accessed directly Because the OK_CODE gets reset at the beginning of each execution of PAI processing To prevent accidental setting of the OK_CODE in a different screen So the OK_CODE is freed up for subscreens

3 of 133

(More than one answer is correct) To improve user response time your updates need to run together as a logical unit Immediate updates to the Database are required your program need the updates completed in order to continue processing

4 of 133

NUMBER_GET_INFO NUMBER_RANGE_INTERVAL_LIST NUMBER_CHECK . NUMBER_RANGE_EXTERNAL_CHECK NUMBER_GET_NEXT 5 of 133

0 2 Unlimited 1 6 of 133

(More than one answer is correct) Update table.. .. PERFORM.. .. ON COMMIT and WAIT COMMIT WORK AND WAIT CALL FUNCTION in Update Task 7 of 133

SAP memory ABAP/4 memory Shared Memory

8 of 133

V2 Local V1 Transactional 9 of 133

an update-task function module triggered with COMMIT WORK AND WAIT an update-task function module triggered with COMMIT WORK Batch Input Programs PERFORM.. .. ON COMMIT 10 of 133

After these events are processed the screen is redisplayed but the PBO is not processed After these events are processed the PAI is processed then the PBO and then the screen is displayed After these events are processed the PBO module is processed and the screen is redisplayed None of the answers are correct

11 of 133 Ensure the prefix name of the radio buttons is the same Encompass them in a Radio Button Group Define a Group box Make sure each one has the same Screen Group Name

TAW12 - Week 2

12 of 133 10 20 30 40 50 60 70 PROCESS BEFORE OUTPUT. MODULE SET_STATUS_0100. Set Titlebar 'ABC'. CALL SUBSCREEN SUB INCLUDING 'SAPMZABC' '110'. LOOP. MODULE CHECK_LOOP. ENDLOOP.

80 PROCESS AFTER INPUT. 90 MODULE USER_COMMAND_0100. 100 FIELD FLIGHT MODULE CHECK_FLIGHT ON-REQUIRED. (More than one answer is correct) 30 100 20 40 50

TAW12 - Week 2

13 of 133 (More than one answer is correct) ROLLBACK WORK CALL Transaction MESSAGE S101 COMMIT WORK

14 of 133

To where the transaction was called To the initial screen of the transaction To the previous screen To the Cancel area

TAW12 - Week 2

15 of 133

I type MESSAGE statement A type MESSAGE statement E type MESSAGE statement W type MESSAGE statement S type MESSAGE statement 16 of 133

LEAVE TO BASIC LIST LEAVE TO LIST-PROCESSING CALL REPORT report_name GENERATE list 17 of 133

An error in one V2 function module cause all other V2 functions to be rolled back Each V2 function module for a given COMMIT WORK always runs in its own (separate) DB LUW

V2 errors cause V1 updates to be rolled back They are usually time critical updates

TAW12 - Week 2

18 of 133 (More than one answer is correct) Set Screen Use the Next Screen Option on the Screen Attributes Loop at Screen Submit Screen 19 of 133

(More than one answer is correct) The function module forms its own Database LUW The remote function will continue to execute even if the caller is no longer active All parameters must have a dictionary reference They are executed on another R/3 database server

TAW12 - Week 2

20 of 133 (More than one answer is correct) The flow logic is contained in Modules Dialog Programs do not require a transaction to execute the module pool

Screens are optional in a dialog program. Transactions are a vehicle to execute dialog programs update and enqueue techniques are important.

TAW12 - Week 2

21 of 133 contains screen field values contains function codes determines successful user action

TAW12 - Week 2

22 of 133 (More than one answer is correct) Multiple subscreens are possible in a single screen. You can also specify the subscreens dynamically at runtime. Can set their own titlebar Can set their own GUI status have their own OK_CODE

TAW12 - Week 2

23 of 133 (More than one answer is correct)

Duplicate numbers will never be encountered in the system perceived improved performance can be achieved a programmer can choose to ignore buffering on request The numbering sequence is contiguous

TAW12 - Week 2

24 of 133

Case OK_CODE PAI Module User_command PBO

TAW12 - Week 2

25 of 133 (More than one answer is correct) Leave to transaction Call Transaction Submit.. .. and Return Submit

TAW12 - Week 2

26 of 133

On the same screen On the next screen After the AT-EXIT Module In the System Log

TAW12 - Week 2

27 of 133

process after input. 10 module exit at exit-command. module back. 20 30 field a module check_field_a. field b module check_field_b.

40 chain. field: a, b, c. module check_field_abc. endchain. 50 chain. field: c, d. module check_field_cd. endchain. c a, b, c c, d b, d

<== ERROR

TAW12 - Week 2

28 of 133

CALL report AND RETURN SUBMIT report LEAVE TO LIST-PROCESSING SUBMIT ZPGMA and Return SUBMIT ZPGMA with selection-set.. ..

TAW12 - Week 2

29 of 133

At Line-Selection Start-of-Selection Top-of-Page At Selection-Screen

TAW12 - Week 2

30 of 133

3 2 0 1

TAW12 - Week 2

31 of 133 In the module that perform OKCODE processing

In the PAI when Process on Value-Request dialog event is triggered In the PBO when Process on Value-Request dialog event is triggered In the PAI when Process on Help-Request dialog event is tgriggered

TAW12 - Week 2

32 of 133

SNR3 SNR1 SNR2 SNR4

TAW12 - Week 2

33 of 133 There is no difference Call Screen is used only for external screens. Set screen is only for screens in the same module pool Call screen executes and returns to the point of call. Set Screen does not Set screen executes and returns to the point of call. Call Screen does not

TAW12 - Week 2

34 of 133 (More than one answer is correct) DYNP_VALUES_UPDATE DYNP_VALUES_READ DYNPREAD F4IF_FIELD_VALUE_REQUEST

TAW12 - Week 2

35 of 133 (More than one answer is correct) ENQUEUE_EZMARA DEQUEUE_EZMARA ENQUEUE_EZ_MARA DEQUEUE_EZ_MARA

TAW12 - Week 2

36 of 133

P T Blank F E

TAW12 - Week 2

37 of 133 (More than one answer is correct) A subordinate output field in a table control inherits the context menu of the table control They are a special GUI Status A subordinate input field in a subscreen causes the subscreen to inherit the context menu of the subordinate field Context Menus are assigned to input fields

TAW12 - Week 2

38 of 133

PROCESS BEFORE OUTPUT. * MODULE SET_STATUS_0100. PROCESS AFTER INPUT MODULE USER_COMMAND_0100. (More than one answer is correct)

MZABCTOP USER_COMMAND_0100 MZABCO01 MZABCI01

TAW12 - Week 2

39 of 133 A loop .. endloop statement for the table control only in the PAI A loop .. endloop statement for the table control in both the PBO and the PAI A loop .. endloop statement for the table control only in the USER_COMMAND module A loop .. endloop statement for the table control only in the PBO

TAW12 - Week 2

40 of 133

Field Module Check Case

TAW12 - Week 2

41 of 133 (More than one answer is correct) The screen will be displayed with the report that was built, but the gui-status will be the one from the previous screen The report will be displayed on the screen only after the user presses the enter key The previous screen (calling screen) will be redisplayed The screen will be displayed, and will be empty

TAW12 - Week 2

42 of 133

Call Subscreen in the PAI and PBO The Call Subscreen statement is not required Call Subscreen in the PAI only Call Subscreen in the PBO only

TAW12 - Week 2

43 of 133 Use the Data Browser

Through a Function Call Create it as an object in the dictionary

TAW12 - Week 2

44 of 133 A Commit Work is executed System passes a Database commit to the database system The application gathers data for update processing The SAP LUW is concluded

TAW12 - Week 2

45 of 133

Using the SET GROUP statement Do you really care In the Dynpro In the screen painter

TAW12 - Week 2

46 of 133 Parameter passing is allowed Multiple calls to a FORM result in single execution of

the FORM Commit Work is allowed in the form RollBack Work is allowed in the FORM

TAW12 - Week 2

47 of 133

Call Function Enqueue_ESMYLOCK Exporting Field1 = Field2 = Field3 = It is not possible in this case Field1 = Generic, Field2 = Generic, Field3 = Space Field 1 = AA, FIELD2 = 111, Field3 = Initial Field 1 = AA, FIELD2 = 111, Field3 = Space

TAW12 - Week 2

48 of 133 Batch Asynchronous Synchronous Direct

TAW12 - Week 2

49 of 133

4 1 3 Unlimited 2

TAW12 - Week 2

50 of 133

TOP_LINE w/selcolumn LINE_SEL_MODE Function code

TAW12 - Week 2

51 of 133 An RFC Function Call that terminates normally A program that issues a MESSAGE type 'A'. A user cancels the transaction A program that issues a Commit Work statement

TAW12 - Week 2

52 of 133

read data,lock data, update database, release locks lock data, read data, release locks, update database lock data, read data, update database, release locks

TAW12 - Week 2

53 of 133

R D 1 M

TAW12 - Week 2

54 of 133

Until the Next screen change Until the next Set TitleBar statement Until the next DB Luw

TAW12 - Week 2

55 of 133

Screen fields followed by table control fields All fields regardless of table control definition are transported at the beginning of PBO Table control fields followed by the remaining screen fields Dictonary Fields followed by Program Fields

TAW12 - Week 2

56 of 133 SM13 CCMS SM12 SE80

TAW12 - Week 2

57 of 133 _mytext !mytext ?mytext

TAW12 - Week 2

58 of 133 tstc txncodes tstct txn

TAW12 - Week 2

59 of 133 (More than one answer is correct) SAP LUW is concluded User is notified of updates Update requests are processed Database commit is triggered

TAW12 - Week 2

60 of 133 (More than one answer is correct) When Users need the ability to navigate freely between components When Navigation between components is predetermined in a fixed manner When several components of an application need to be displayed on one screen

TAW12 - Week 2

61 of 133

Asynchronous RFC Synchronous RFC Transactional RFC

TAW12 - Week 2

62 of 133

03 - Already_Locked 08 - General_Failure 01 - Foreign_Lock 02 - System Failure

TAW12 - Week 2

63 of 133

(More than one answer is correct) Update task functions are logged in the SM12 log tables Requests are not passed directly to the DB You can combine update requests from consecutive dialog steps COMMIT concludes the SAP LUW All updates are performed or none at all

TAW12 - Week 2

64 of 133 (More than one answer is correct) You must release the locks programatically Locks generated in the dialog program are passed on to the update program An update termination error holds the locks The locks are automatically released when the updates complete

TAW12 - Week 2

65 of 133 In a PBO module In a PAI Module PAI screen event in Flow logic

PBO screen event in Flow logic

TAW12 - Week 2

66 of 133

Screen Pushbuttons menu functions Container tool-bar pushbuttons

TAW12 - Week 2

67 of 133 (More than one answer is correct) End the Transaction Reset Command CALL FUNCTION DEQUEUE_ALL Commit Work Program ends abnormally

TAW12 - Week 2

68 of 133

a)The corresponding check table will be referenced and displayed b)Process on Value-Request is executed c)A search help is referenced and displayed d)The corresponding domain values will be displayed b, c, a, d a, b, c, d b, d, a, c d, a, c, b

TAW12 - Week 2

69 of 133

Subscreen Sy-Table Screen Screen_ITAB

TAW12 - Week 2

70 of 133 Program Transaction Text Screen Number Authorization Object

TAW12 - Week 2

71 of 133 Before PBO Processing Begins After the User has pressed enter and before the PAI modules are processed After PAI Processing is complete After the User has pressed enter and before the PBO modules are processed

TAW12 - Week 2

72 of 133

All fields except table control and field statements, Table control fields, Field statement fields Field statement fields, Table control fields, remaining fields Dictionary Fields followed by Program Fields Table control fields, Field statement fields, All remaining fields

TAW12 - Week 2

73 of 133 1. Dialogtask FORM routines logged with PERFORM. ON COMMIT. 2. High-priority (V1) update-task function modules. 3. Low-priority (V2) update-task function modules. 1, 2, 3 3, 2, 1 2, 3, 1

TAW12 - Week 2

74 of 133

(More than one answer is correct) To the next screen defined in the screen attributes of screen 100 There is no return if the statement LEAVE TO LISTPROCESSING is used To the beginning of the transaction If LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN xxx is used, return will go to screen xxx To the next screen defined in the screen attributes of screen 200

TAW12 - Week 2

75 of 133

CXTAB TableView TableControl Table

TAW12 - Week 2

76 of 133 All PBO and PAI modules in the Module pool One sequence of a PBO followed by a PAI One sequence of a PAI followed by a PBO All ABAP Modules of a screen

TAW12 - Week 2

77 of 133 The system will display the documentation of the field to which a screen field refers The system will display the documentation of the data element to which a screen field refers The system will display the documentation of the domain to which a screen field refers

The system will display the technical information of the field to which a screen field refers

TAW12 - Week 2

78 of 133

Function Type Application Processing type Function Group

TAW12 - Week 2

79 of 133 The database breaks The update task removes them at the end of the SAP LUW The update task removes them at the beginning of the SAP LUW Commit Work statement is issued

TAW12 - Week 2

80 of 133 (More than one answer is correct) Update requests do not use the VBLOG table Cluster tables are used to processing the update request Update requests use shared memory A new dialog work process is used for the update process

TAW12 - Week 2

81 of 133 Titles/Headers Parameter Texts Selection Texts Text Symbols

TAW12 - Week 2

82 of 133

NUMBER_GET_INFO NUMBER_GET_NEXT NUMBER_RANGE_INTERVAL_LIST NUMBER_RANGE_EXTERNAL_CHECK

TAW12 - Week 2

83 of 133 (More than one answer is correct) CALL SUBSCREEN At User-Command Message I001. Exit the Transaction CALL TRANSACTION

TAW12 - Week 2

84 of 133 (More than one answer is correct) CLEAR MEMORY ID 'MYID' FREE MEMORY ID 'MYID' IMPORT ABC TO MEMORY ID 'MYID' EXPORT ABC TO MEMORY ID 'MYID'

85 of 133 (More than one answer is correct)

Set the screen painter attribute GET Parameter and fill in the Parameter ID field with CAR Use the GET Parameter in the PBO of the DYNPRO Use the SET Parameter in the PBO of the DYNPRO Use the GET Parameter in the PAI of the DYNPRO

TAW12 - Week 2

86 of 133 (More than one answer is correct) subroutines called using on commit have no interface subroutines called using on commit pass parameters by reference only subroutines called using on commit pass parameters by value only subroutines called using on commit use global data only

TAW12 - Week 2

87 of 133 (More than one answer is correct) Tab Title Function Keys Tabstrip Menu Bar Subscreens

Subscreen Area

TAW12 - Week 2

88 of 133 Module Pool Flow logic Screen attributes Element List Screen layout

TAW12 - Week 2

89 of 133 F1, Technical Info on the screen field Check users default Check table TPARA Check the Value statement in the Top Include

TAW12 - Week 2

90 of 133 (More than one answer is correct)

OK_CODE Checking is performed in the Screen Flow Logic The last field of the element list of the screen has the name OK_CODE OK_CODE is Defined in the TOP Include Define a GUI Status

TAW12 - Week 2

91 of 133

F2 F3 F1 F4

TAW12 - Week 2

92 of 133 Prevents a single user with read-write access from attaining further locks to the same set of table rows. This is useful when you are using recursive routines to make updates. Gives a single user read and write access to the specified table rows. No other users may access the rows. allows multiple users to access the specified table rows, but with read-access only. No write-accesses are allowed at any time.

TAW12 - Week 2

93 of 133

Event Program Type Module Transaction

TAW12 - Week 2

94 of 133

Field MYTAB-RESERVATION Module Validate_Reservation. The field is ready for input again PBO is reprocessed The system places the cursor in the error field Screen is Redisplayed The Message is displayed

TAW12 - Week 2

95 of 133

Export the screen fields to memory The mandatory fields must be filled in with "Get Parameter" statement or default values in Transaction ZABC The mandatory fields must be filled in with "Set Parameter" statement or default values in Transaction ZABC The first screen in transaction ZABC can indicate that mandatory fields do not need to be filled in if called by another transaction

TAW12 - Week 2

96 of 133

SUBMIT TRANSACTION tcod LEAVE PROGRAM LEAVE TO TRANSACTION tcod CALL TRANSACTION tcod

TAW12 - Week 2

97 of 133

SUBMIT RSPGM101 WITH BOOKING = T_BOOKING. SET PARAMETER ID BOK FIELD T_BOOKING. SUBMIT RSPGM101. IMPORT T_BOOKING TO MEMORY ID MYID. SUBMIT RSPGM101. EXPORT T_BOOKING TO MEMORY ID MYID. SUBMIT RSPGM101.

TAW12 - Week 2

98 of 133

TC_FLIGHT-LINES SY-DYNNR SY-STEPL TC_FLIGHT-TOTAL_LINES

TAW12 - Week 2

99 of 133 A number range can be character only The range consists only of numerics A number range can be defined as both internal and external. A number range is used only for transactional documents

TAW12 - Week 2

100 of 133

SUBMIT ABC WITH CARRID = W_CARRID CALL ABC WITH CARRID = W_CARRID SUBMIT ABC AND SKIP FIRST SCREEN. SUBMIT ABC VIA SELECTION-SCREEN.

TAW12 - Week 2

101 of 133 (More than one answer is correct) Leave Program Leave to Screen 0 Set Screen 0 Set Screen 0. Leave Screen

TAW12 - Week 2

102 of 133

LOOP AT BOOKING_TC.ENDLOOP. "In the PBO. controls: booking_tc type tableview using screen 200. "IN THE TOP INCLUDE LOOP AT BOOKING_TAB WITH CONTROL BOOKING_TC CURSOR BOOKING_TC-CURRENTLINE. ENDLOOP. "IN THE PAI controls: booking_tc using screen 200. " IN THE TOP INCLUDE

TAW12 - Week 2

103 of 133 CHAIN. Field: Flight, Carrid. Module Validate on Chain-Input ENDCHAIN. The Module Validate is processed if both FLIGHT and CARRID are other than the initial value

The Module Validate is processed if at least one of the fields FLIGHT or CARRID are other than the initial value The Module Validate is processed only if both FLIGHT and CARRID are initial values The Module Validate is never processed

TAW12 - Week 2

104 of 133 You should declare a corresponding one character variable in your TOP include You should declare a corresponding one character variable in the Screen Flow Ensure the radio button is selected in the screen Nothing else is required

TAW12 - Week 2

105 of 133 (More than one answer is correct) The Column heading The width of a column , The horizontal grid can be set off/on The order of the columns

TAW12 - Week 2

106 of 133

At the end of the transaction Only when the program encounters more code to modify the field attributes At PAI execution At PBO execution

TAW12 - Week 2

107 of 133 (More than one answer is correct) Enables execution of interactive reporting events Data available in the dialog program must be passed to the list Enables processing of ok_code functions The CALL SCREEN xxx statement is possible The invoking module pool still retains control of execution

TAW12 - Week 2

108 of 133 Leave to Transaction Leave Screen Call Screen 100 Set Screen 100

TAW12 - Week 2

109 of 133 (More than one answer is correct) ABAP memory is local to each external session Each external session has its own ABAP memory SAP Memory can be accessed by all external sessions ABAP memory can be accessed by SAP memory ABAP memory is used to pass data between the external sessions of an internal session

TAW12 - Week 2

110 of 133 Shortcuts for frequently used functions Functions that are relevant for the current Screen Group Context Sensitive Pushbuttons A special menu for subscreens

TAW12 - Week 2

111 of 133

(More than one answer is correct) Issue a COMMIT WORK statement Issue a ROLLBACK WORK statement in the program End the dialog program Issue a termination message (type A)

TAW12 - Week 2

112 of 133

Extended memory SAP memory ABAP/4 memory

TAW12 - Week 2

113 of 133

Function Modules Generic Lock Keys A Dictionary Table

TAW12 - Week 2

114 of 133 UPDATE CALL FUNCTION .. .. IN UPDATE TASK PERFORM ASYNCHRONOUS

PERFORM .. .. ON COMMIT

TAW12 - Week 2

115 of 133 (More than one answer is correct) Place a tabstrip object on your screen using Screen Painter Define Pushbuttons on the subscreen area Name your tabstrip object Declare a Tabstrip control in your global top include

TAW12 - Week 2

116 of 133

Any Primary Key Fields Any Primary Key Fields and Any Secondary Key Fields The Primary Key Fields The Foreign Key Dependancies

TAW12 - Week 2

117 of 133

process after input. 10 module exit at exit-command. module back. 20 30 field a module check_field_a. field b module check_field_b.

40 chain. field: a, b, c. module check_field_abc. endchain. 50 chain. field: c, d. module check_field_cd. endchain. 30 20 40 10 50

<== ERROR

118 of 133 (More than one answer is correct) Dictionary Objects Txn Code Function Modules GUI User Dialogs ABAP Program

119 of 133

Assign Function Type = Space Assign Function Code = P Assign Function Code = Space Assign Function Type = P

TAW12 - Week 2

120 of 133

Leave to Transaction Exit. Leave Program Stop Program

TAW12 - Week 2

121 of 133

Number of table control lines Loop Counter Number of filled lines

TAW12 - Week 2

122 of 133

Do 5 times. x = sy-tabix. perform calculate_sales on commit. enddo. COMMIT WORK. Infinitely 1 Not at all 5

TAW12 - Week 2

123 of 133 (More than one answer is correct) A screen can be called from within a function module Screens should be called from PBO modules Screens can be called from PAI modules A screen can be called from a report program.

TAW12 - Week 2

124 of 133

Process After Input Module Exit at exit-command Field ABC Module Validate_ABC. 10 All fields not defined in FIELD statements

20 System performs Auto Field Checking 30 Fields in FIELD Statements 20, 30, 10 10, 20, 30 20, 10, 30

TAW12 - Week 2

125 of 133

Application Screens Top Include Logical Database

TAW12 - Week 2

126 of 133 (More than one answer is correct) Message A101 ROLLBACK WORK UPDATE Call Function in Update Task

TAW12 - Week 2

127 of 133 (More than one answer is correct) Define a change document object Mark the change document flag on the domain of the field where logging is required Call the generated change doc function (i.e. obj_write_document) in an ABAP program Create a function to update tables CDHDR and CDPOS

TAW12 - Week 2

128 of 133

cl_context_clas cl_ctmenu cl_menu menu_class

TAW12 - Week 2

129 of 133 Tab strip ACTIVETAB Function Code

OK_Code

TAW12 - Week 2

130 of 133

COMMIT MODIFY SET ACTIVATE

TAW12 - Week 2

131 of 133 After all V1's are complete After each related V1 Before V1's are started Parallel to relative V1's

TAW12 - Week 2

132 of 133

Run Time Error Status 'BASE' is displayed Standard List Status

Screen 200 is displayed without a status.

TAW12 - Week 2

133 of 133 (More than one answer is correct) Page scrolling using the standard toolbar is automatic and can be controlled by the user Column sizing is adjustable and can be controlled by the user The sort option is automatic and can be controlled by the user Table control rows are scrollable