SAP Transactions -1

29. Can we state the next screen number with a variable (*Yes/No)?

- Yes

30. The field SY-DYNR refers to--------------

Number of the current screen.

31. What is dialog Module?
- A dialog Module is a callable sequence of screens that does not belong to a particular transaction. Dialog modules have their module pools, and can be called by any transaction.

32. The Syntax used to call a screen as dialog box (pop up)is---------

CALL SCREEN
STARTING AT
ENDING AT

33. What is “call mode”?
- In the ABAP/4 WORLD each stackable series of screens is a “call mode”, This is IMP because of the way u return from the given sequence .To finish a call mode and return to a suspended chain set the “next screen” to 0 and leave to it:
LEAVE TO SCREEN 0 or (SET SCREEN 0 and LEAVE SCREEN) .When u return to the suspended chain execution resumes with the statement directly following the original CALL SCREEN statement.The original sequence of screens in a transaction (that is , without having stacked any additional call modes),you returned from the transaction altogether.


34. The max number of calling modes stacked at one time is?
- NINE

35. What is LUW or Data base Transaction?

- A “LUW”(logical unit of work) is the span of time during which any database updates must be carry out in an “all or nothing” manner .Moreover they are all performed (committed),or they are all thrown away (rolled back).In the ABAP/4 world , LUWs and
- Transactions can have several meanings:

LUW (or “database LUW” or “database transaction”)

This is the set of updates finished by a database commit. A LUW lasts, at most, from one screen change to the next (because the SAP system triggers database commits automatically at every screen change).

36. What is SAP LUW or Update Transaction?
Update transaction (or “SAP LUW”)
This is a set of updates terminated by an ABAP/4 commit. A SAP LUW may last much longer than a database LUW, since most update processing extends over multiple transaction screens. The programmer terminates an update transaction by issuing a COMMIT WORK statement.

37. What occur if only one of the commands SET SCREEN and LEAVE SCREEN is used with no using the other?
If we use SET SCREEN without LEAVE SCREEN, the program finishes processing for the present screen before branching to. 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.

38. What is the meaning of the screen number ‘0’?
In “calling mode”, the special screen number 0 (LEAVE TO SCREEN 0) root the system to jump back to the preceding call level. That is, if you have called a screen sequence with CALL SCREEN leaving to screen 0 ends the sequence and returns to the calling screen. If you have not called a screen sequence, LEAVE TO SCREEN 0 ends the transaction.

39. What does the ‘SUPPRESS DIALOG’ do?
Suppressing of whole screens is feasible with this command. This command permits us to carry out screen processing “in the background”. Suppressing screens is helpful when we are branching to list-mode from a transaction dialog step.

40. What is the significance of the memory table ‘SCREEN’?
At runtime, characteristic for each screen field are stored in the memory table called ‘SCREEN’. We need not speak out this table in our program. The system keeps the table for us internally and updates it with every screen change.