Regarding some concepts

[Former Member]

hi guys,

can any one help me out to answer these 4 questions

1) What is the exact difference between set screen and call screen.

2) what is SAP memory and ABAP memory

3) when you schedule a job in back ground, it will store in SPOOL list so what is the transaction code for checking spool list.

how do u check contents of spool list - that if i run a bdc in back ground and due to some error back ground process is stopped and only few records are updated to sap system and i need to process the error with the help of spool number generated for that particular job so, how do i do that with the help of spool no, how can i check the contents of spool number.

4) is there any possibility to mount push buttons on selection screen (not on output list) if so how do u do that and how many push buttons are allowed

it wud be great if any one could help me with this.

thanks very much

pavan

[RichHeilman]

1) http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbab2935c111d1829f0000e829fbfe/frameset.htm

SET SCREEN sets the next screen in the sequence flow, CALL SCREEN calls the screen directly.

2)

http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm

3) SP01

4) Yes, as many as you want.

report zrich_0001.


selection-screen begin of block b1 with frame title text-001.
selection-screen pushbutton 5(20) pb1 user-command pb1.
selection-screen skip 1.
selection-screen pushbutton 5(20) pb2 user-command pb2.
selection-screen skip 1.
selection-screen pushbutton 5(20) pb3 user-command pb3.
selection-screen skip 1.
selection-screen pushbutton 5(20) pb4 user-command pb4.
selection-screen skip 1.
selection-screen pushbutton 5(20) pb5 user-command pb5.
selection-screen skip 1.
selection-screen pushbutton 5(20) pb6 user-command pb6.
selection-screen skip 1.
selection-screen pushbutton 5(20) pb7 user-command pb7.
selection-screen skip 1.
selection-screen pushbutton 5(20) pb8 user-command pb8.
selection-screen skip 1.
selection-screen pushbutton 5(20) pb9 user-command pb9.
selection-screen skip 1.
selection-screen pushbutton 5(20) pb10 user-command pb10.
selection-screen end of block b1.



at selection-screen output.

pb1 = 'PushButton 1 Text'.
pb2 = 'PushButton 2 Text'.
pb3 = 'PushButton 3 Text'.
pb4 = 'PushButton 4 Text'.
pb5 = 'PushButton 5 Text'.
pb6 = 'PushButton 6 Text'.
pb7 = 'PushButton 7 Text'.
pb8 = 'PushButton 8 Text'.
pb9 = 'PushButton 9 Text'.
pb10 = 'PushButton 10 Text'.

Regards,

Rich Heilman

[Former Member]

2.

ABAP Memmory & SAP Memmory

http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm

3. SP01

4. Yes

Regards,

Santosh

[Former Member]

Hi pavan,

sap memory and abap memory:

SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens

ABAP/4 Memory

ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data

to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse

chk the links:

http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm

http://www.sap-img.com/abap/answers-to-some-abap-interview-questions.htm

http://www.tutorialdownloads.com/FAQ/sap-interview-questions.html

set screen:

Every screen has a static next screen that specifies the next screen to be called after the current one, as long as it is not overwritten dynamically. In the processing logic, that is, a dialog module called by the screen, you can use the SET SCREENstatement to overwrite the statically-defined next screen dynamically:

SET SCREEN Folgedynpro.

This statement defines a new next screen for the current program run. You can also specify the number of the next screen as a field containing a screen number. The statically-defined next screen is ignored. However, this only overrides the static screen sequence temporarily. The static value for the next screen, as defined in the Screen Painter, is always retained.

If you specify the value 0 for next screen, the current screen becomes the last in the screen chain. After the screen has been processed, control returns to the point from which the screen sequence was called. If the screen sequence was embedded, the system returns to the previous screen sequence containing the relevant CALL SCREEN statement. If the screen sequence was not embedded, the application program terminates.

The SET SCREEN does not interrupt the current screen processing. To leave a screen, use the ABAP statement LEAVE

call screen:

CALL SCREEN <dynnr>.

statement to call a screen and its subsequent sequence within that program. The flow logic of each screen calls dialog modules in the program that called the screen.

When the screen sequence ends, control returns to the statement after the original CALL SCREEN statement

regards,

keerthi.

[Former Member]

Hi,

Set Screen will will update the sy-dynnr to the said Screen no and will not go to the screen. But the call scren will call the screen by setting the sy-dynnr.

Transaction to check spool list SP01.

To read the contents of the SPool, use the below FM.

CALL FUNCTION 'RSPO_RETURN_ABAP_SPOOLJOB_RAW'

EXPORTING

rqident = <spoolid>

• FIRST_LINE = 1

• LAST_LINE =

TABLES

buffer = <i_rdidata>

EXCEPTIONS

no_such_job = 1

not_abap_list = 2

job_contains_no_data = 3

selection_empty = 4

no_permission = 5

can_not_access = 6

read_error = 7

OTHERS = 8.

Regards,

Prakash.

[Former Member]

hi pavan.

1)If u use Call screen...

2nd screen from 1st screen then 2nd screen is called without killing the 1st screen i.e u can come back to 1st screen.

set screen

if u use set screen 2nd is called killing the first screen i.e. u cannot come back to the 1st screen.

2)check this

3) SP01