TAW_10_2 chapter 14, screen error handling

Question 1

What are the field checks that occur before PAI

Answer 1

Mandatory fields all filled
Field format
Fixed values
Foreign key

Question 2

When an ‘e’ level error is raised from a field statement the PBO is reprocessed?

Answer 2

False

Question 3

If a field is changed in PAI but has not been part of a Field chain, have its value changes been transported?

Answer 3

No, which is why you must be careful about the order of the field statements and make sure all values relevant to the check module are included in the chain

Question 4

When a user corrects input after an e level error, where does processing resume

Answer 4

At the first field or chain that a changed field is used

Question 5

What is the sequence of field transport from screen t program

Answer 5

1) all fields that are not part of a field or chain

2) all remaining fields are transported after the field statements

Question 6

What is the difference between ON INPUT and ON REQUEST

Answer 6

ON INPUT means the field is not equal to it’s initial value

ON REQUEST means the field has been changed when new input is entered

Question 7

How can automatic checks be avoided if the user wishes to leave the screen?

Answer 7

AT EXIT-COMMAND

Question 8

Can a FIELD or CHAIN statement be combined with a switch

Answer 8

Nope

Question 9

From the initial screen of a program, the BACK, CANCEL, and EXIT buttons all drive back to the calling program

Answer 9

True

Question 10

How can the program check if a user entered data so a “save data” prompt can be given?

Answer 10

Check system field SY-DATAR. If the user entered data this field will be X. When an exit function is selected the user can be prompted with a popup