Tuesday, March 11, 2008

TRANSACTIONS

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

- Yes

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


Number of the current screen.


32.. 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.


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


CALL SCREEN
STARTING AT ENDING AT

34. 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:


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.



35. The max number of calling modes stacked at one time is?


- NINE


36. 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 performed in an “all or nothing” manner .Either 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 terminated 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).



37. 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.



38. 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 . 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.



39. 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.



40.. What does the ‘SUPPRESS DIALOG’ do?


Suppressing of entire screens is possible with this command. This command allows us to perform screen processing “in the background”. Suppresing screens is useful when we are branching to list-mode from a transaction dialog step.



41. 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.



42. What are the fields in the memory table ‘SCREEN’?




Name

Length

Description

NAME

30

Name of the screen field

GROUP1

3

Field belongs to field group 1

GROUP2

3

Field belongs to field group 2

GROUP3

3

Field belongs to field group 3

GROUP4

3

Field belongs to field group4

ACTIVE

1

Field is visible and ready for input.

REQUIRED

1

Field input is mandatory.

INPUT

1

Field is ready for input.

OUTPUT

1

Field is display only.

INTENSIFIED

1

Field is highlighted

INVISIBLE

1

Field is suppressed.

LENGTH

1

Field output length is reduced.

DISPLAY_3D

1

Field is displayed with 3D frames.

VALUE_HELP

1

Field is displayed with value help.




43. 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.44. What are the attributes of a field that can be activated or deactivated during runtime?

Input, Output, Mandatory, Active, Highlighted, Invisible.



45. What is a screen group? How it is useful?


Screen group is a field in the Screen Attributes of a screen. Here we can define a string of up to four characters which is available at the screen runtime in the SY-DNGR field. Rather than maintaining field selection separately for each screen of a program, we can combine logically associated screens together in a screen group.



46. What is a Subscreen? How can we use a Subscreen?


A subscreen is an independent screen that is displayed in a n 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 stratement tells the system to execute the PBO and PAI events for the subscreen 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 INCLUDING ‘’ ’’.



PROCESS AFTER INPUT.


CALL SUBSCREEN .



A
rea is the name of the subscreen area you defined in your main screen. This name can have up to ten characters. Program is the name of the program to which the subscreen belongs and screen is the subscreen’s number.



47. What are the restrictions on Subscreens?

Subscreens have several restrictions. They cannot:


- Set their own GUI status


- Have a named OK code


- Call another screen


- Contain an AT EXIT-COMMAND module


- Support positioning of the cursor.



48. How can we use / display table in a screen?


ABAP/4 offers two mechanisms for displaying and using table data in a screen. These mechanisms are TABLE CONTROLS and STEP LOOPS.



49. What are the differences between TABLE CONTROLS and STEP LOOPS?


TABLE CONTROLS are simply enhanced STEP LOOPS that display with the look and feel of a table widget in a desktop application. But from a programming standpoint, TABLE CONTROLS and STEP LOOPS are almost exactly the same. One major difference between STEP LOOPS and TABLE CONTROLS is in STEP LOOPS their table rows can span more than one time on the screen. By contrast the rows in a TABLE CONTROLS are always single lines, but can be very long. (Table control rows are scrollable). The structure of table control 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.



50. What are the dynapro keywords?


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



51. 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.



52. The field SY-STEPL refers to the index of the screen table row that is currently being processed. The system variable SY-stepl only has a meaning within the confines of LOOP….ENDLOOP processing. Outside the loop, it has no valid value.



53. How can we declare a table control in the ABAP/4 program?

Using the syntax controls type tableview using screen .


54. Differentiate between static and dynamic step loops.


Step loops fall into two classes: Static and Dynamic. Static step loops have a fixed size that cannot be changed at runtime. Dynamic step loops are variable in size. If the user re-sizes the window the system automatically increases or decreases the number of step loop blocks displayed. In any given screen you can define any number of static step loops but only a single dynamic one.



55. What are the two ways of producing a list within a transaction?


By submitting a separate report.


By using leave to list-processing.



56. What is the use of the statement Leave to List-processing?


Leave to List-processing statement is used to produce a list from a module pool. Leave to list processing statement allows to switch from dialog-mode to list-mode within a dialog program.



57. When will the current screen processing terminates?


A current screen processing terminates when control reaches either a Leave-screen or the end of PAI.



58. How is the command Suppress-Dialog useful?


Suppressing entire screens is possible using this command. This command allows us to perform screen processing “in the background”. The system carries out all PBO and PAI logic, but does not display the screen to the user. Suppressing screens is useful when we are branching to list-mode from a transaction dialog step.



59. What happens if we use Leave to list-processing without using Suppress-Dialog?


If we don’t use Suppress-Dialog to next screen will be displayed but as empty, when the user presses ENTER, the standard list output is displayed.



60. How the transaction that are programmed by the user can be protected?


By implementing an authority check.

No comments:

Tutorials on SAP-ABAP

Adobe Interactive Forms Tutorials

Business Server Pages (BSP)

Userexits/BADIs

Web Dynpro for ABAP (Step by step procedure for web dynpro,Tutorials on Web Dynpro,)

ALV Tutorials

Blog Archive

goodsites