topic Re: general in Application Development and Automation Discussions

general

Former Member — Wed, 02 May 2007 10:28:34 GMT

what is the exact diff between set screen,call screen.

Re: general

Former Member — Wed, 02 May 2007 10:30:05 GMT

Hi,

1) Call Screen: Calling a single screen can be used for embedding a screen sequence. If you want to prevent the called screen from covering the current screen completely (say u want 2 display both screen) you can use the CALL SCREEN statement with the STARTING AT and ENDING AT

CALL SCREEN 200

If we write this statement in screen 100 ,it will goto screen 200 and it will retain screen 100(ie u can come back)

and moreover u have options using this

CALL SCREEN 200 STARTING AT x1 y1 ENDING AT x2 y2

2) If we use set screen first the processing blocks in the present screen will be executed and control goes to the screen which is called.

in this control remains in that calling screen only, it doesnt come back to our screen.

3)In screen 100,we call screen 200.The PBO and PAI of screen 200 is processed.Now in screen 200,if we use leave to screen 100,the processing starts from screen 100 after the call screen 200 statement.The PBO and the PAI of screen 100 need not be processed again from the beginning in this case.

4) That is if we use leave to screen,the control goes back to the screen from which the present screen was called and continues with the processing.

SET SCREEN 200

1) With the above statement , it will goto screen 200 and screen 100 no more remains

2) Screen No 0 : This special screen number causes the screen to jump back to the calling screen.

set screen 0 used to go back to the previous screen.

Reward points if useful..

Regards

Nilesh

Re: general

Former Member — Wed, 02 May 2007 10:30:58 GMT

Hello,


SET SCREEN scr. 


Effect 
In ABAP dialogs: Sets the number of the next screen. 
Screen number scr is then processed when the current screen has finished. 



Example
SET SCREEN 200. 



Notes 
To leave a CALL SCREEN chain or return to the application menu, use one of the following statements: 

SET SCREEN 0. or LEAVE TO SCREEN 0. 



Please consult Data Area and Modularization Unit Organization documentation as well. 

CALL SCREEN - Call a screen 


Basic form 
CALL SCREEN scr. 


Addition: 
... STARTING AT x1 y1 ... ENDING AT x2 y2 



Effect 
Calls the screen scr; scr is the number of a screen of the main program. You use SET SCREEN 0. or LEAVE SCREEN. to define the return from the CALL screen. 



Addition 
... STARTING AT x1 y1  ENDING AT x2 y2 


Effect 
The coordinates x1, y1 (start column and start line in the window) and x2, y2 (end column and end line in the window) define the size and position of the CALL screen ("top left - bottom right"). Besides these coordinates, you can also see the contents of the primary window, but cannot perform any action there. 



Note 
If "ENDING AT ..." is not specified, suitable values are substituted for x2 and y2, taking into account the size of the called screen. 



Note 
Runtime errors: 



DYNP_TOO_MANY_CALL_SCREENS: No further screen level (call screen); the maximum number of nested screen levels is restricted to 50 at present. 


Additional help 
Calling Screen Sequences

If useful reward.

Vasanth

Re: general

former_member198270 — Wed, 02 May 2007 10:32:13 GMT

Hi Naga,

1. CALL SCREEN and SET SCREEN

The difference lies in the NEXT Statement...

When Call Screen, the new screen comes, and after that new screen is exited, the control COMES BACK TO THE ORIGNAL SCREEN.

Whereas in SET SCREEN,

The PAI is FIRST COMPLETED, and then, independetly,

the another screen comes, and proceeds further independently.

2. LEAVE SCREEN and LEAVE TO SCREEN

Leave Screen - Simply leaves the current screen,

and goes back from where it came

Leave to screen - Branches to a particular screen

Reward Points if helpful.

Regards,

Amber Soni

Re: general

Former Member — Wed, 02 May 2007 10:32:55 GMT

For Set Screen:

This statement sets thescreen with the screen number specified in dynnr, as the next screen for processing of the current screen. For dynnr, a data object of type n and length 4 is expected. It must contain either the screen number of a screen in the main program of the current program group or the value 0, otherwise a non-catchable exception will be triggered. The specified next screen overwrites the previously-set next screen.

The next screen is automatically called when the system finishes the PAI processing of the current screen. If the screen number of the next screen is 0, the current next screen is ended.

One next screen is always set during the processing of a screen. After you call a screen, the next screen whose characteristics are defined statically, applies; this next screen can be overwritten with the SET SCREEN statement for the duration of the actual next screen processing.

Call screen:

This statement calls the dynpro with the dynpro number specified in dynnr. For dynnr, a data object of type n and length 4 is expected. The call starts a new dynpro sequence, which is embedded into the current dynpro sequence. The dynpro with dynpro number dynnr is the initial dynpro of the dynpro sequence. In a dynpro sequence started by a transaction code, you can nest up to 50 other dynpro sequences.

difference between SET SCREEN and CALL SCREEN :

With SET SCREEN, the current screen simply specifies the next screen in the chain. control branches to this next screen as soon as the current screen has been processed. Return from next screen to current screen is not automatic. It does not

interrupt processing of the current screen. If we want to branch to the next screen without finishing the current one, use LEAVE SCREEN.

With CALL SCREEN, the current (calling) chain is suspended, and a next screen (or screen chain) is called in. The called screen can then return to the suspended chain with the statement LEAVE SCREEN TO SCREEN 0. Sometimes we might want to let an user call a popup screen from the main application screen to let them enter secondary information. After they have completed their entries, the users should be able to close the popup and return directly to the place where they left off in the main screen. Here comes CALL SCREEN into picture. This statement lets us insert such a sequence into the current one.

Regards,

Jayant

Please award if helpful.

Re: general

Former Member — Wed, 02 May 2007 10:33:22 GMT

Hi,

If u Call screen 200 from screen 100 it will take u to screen 200 without killing 100.

with set screen 200 from screen 100 it will kill 100(u cant come back) it will go to 200

Call Screen

Calls the screen scr; scr is the number of a screen of the main program. You use SET SCREEN 0. or LEAVE SCREEN. to define the return from the CALL screen.

SET SCREEN

Calls the screen scr; scr is the number of a screen of the main program. You use SET SCREEN 0. or LEAVE SCREEN. to define the return from the CALL screen

Reward if it helpful

Thanks

Vana

Re: general

Former Member — Wed, 02 May 2007 10:33:41 GMT

Hi Mrudula,

call screen scr.

Calls the screen scr; scr is the number of a screen of the main program. You use SET SCREEN 0. or LEAVE SCREEN. to define the return from the CALL screen.

Call Screen is used to define a screen and then call it.

Regards,

Ravi G

Re: general

Former Member — Wed, 02 May 2007 10:34:37 GMT

Hi Naga,

check this link

https://www.sdn.sap.com/irj/sdn/forums

regards,

Pavan

Re: general

Former Member — Wed, 02 May 2007 10:35:20 GMT

Starting Lists from Screen Processing

This section describes how to switch from screen processing to list processing. It contains a short technical introduction, followed by a recommended procedure.

Switching Between Screen and List Processing

Screen processing always involves a screen sequence that you start either using CALL SCREEN or a transaction code. During screen processing, the ABAP program is controlled by the dialog processor. In the ABAP program, the PBO and PAI modules are executed as they are called from the screen flow logic.

To pass control from the dialog processor to the list processor, you must include the following statement in one of the dialog modules:

LEAVE TO LIST-PROCESSING [AND RETURN TO SCREEN <nnnn>].

You can include this statement in either the PBO or the PAI event. Its effect is to start the list processor and display the basic list after the PAI processing of the current screen. The basic list contains any list output from all PBO and PAI modules that have been executed up to that point.

If detail lists are defined in the corresponding event blocks of the ABAP program (AT LINE-SELECTION, AT USER-COMMAND), user actions on the basic list will lead to the detail list, and further interaction will lead to further list levels.

You can leave list processing in two ways:

By leaving the basic list using the Back, Exit, or Cancel function.

By using the following statement during list processing:

LEAVE LIST-PROCESSING.

In both cases, control returns from the list processor to the dialog processor. Each time this occurs, the entire list system is initialized. Any subsequent list output statements in PBO and PAI modules apply to an empty basic list.

By default, the dialog processor returns to the PBO processing of the screen from which the list processor was called. The optional addition AND RETURN TO SCREEN allows you to specify a different screen in the current screen sequence at whose PBO event you want to resume processing. In particular, the statement

LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.

can be used to end the current screen sequence and return to the point from which it had originally been called.

Recommended Procedure

If you want to display lists during screen processing, you should create a separate screen for each list system that you want to call. This screen encapsulates the creation and display of the basic list. It can then be called from anywhere in the program using CALL SCREEN.

The actual screen mask of this screen can remain empty. You do not need any PAI modules, and only a single PBO module. In the PBO module, you define the basic list of the list system and call the list processor.

First, use the

LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.

statement to call the list display at the end of the screen, and to ensure that, after leaving the list, you return to the point from which the screen was called.

Next, set a GUI status for the list; for example, the default list status SPACE or a list status of your own.

Use one of the following statements to ensure that the empty screen is not displayed:

SUPPRESS DIALOG.

LEAVE SCREEN. Instead, the list is displayed immediately at the end of the screen.

Now define the entire basic list, and place any necessary data in the HIDE area.

If you want to process user actions on the list, you need to define the relevant event blocks in your ABAP program. If you want to call more than one independent list system in the program, you must ensure that you can tell them apart in the list event processing. You cannot do this using SY-DYNNR, since the container screen for a list is always number 120. Instead, you could assign a different GUI status to each list, and distinguish between the list systems using the value of SY-PFKEY, or you could place some unique information in the HIDE area of each list system.

Example

REPORT demo_leave_to_list_processing .

TABLES sdyn_conn.

DATA: wa_spfli TYPE spfli,

flightdate TYPE sflight-fldate.

CALL SCREEN 100.

MODULE status_0100 OUTPUT.

SET PF-STATUS 'SCREEN_100'.

ENDMODULE.

MODULE cancel INPUT.

LEAVE PROGRAM.

ENDMODULE.

MODULE user_command_0100.

CALL SCREEN 500.

SET SCREEN 100.

ENDMODULE.

MODULE call_list_500 OUTPUT.

LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0.

SET PF-STATUS space.

SUPPRESS DIALOG.

SELECT carrid connid cityfrom cityto

FROM spfli

INTO CORRESPONDING FIELDS OF wa_spfli

WHERE carrid = sdyn_conn-carrid.

WRITE: / wa_spfli-carrid, wa_spfli-connid,

wa_spfli-cityfrom, wa_spfli-cityto.

HIDE: wa_spfli-carrid, wa_spfli-connid.

ENDSELECT.

CLEAR: wa_spfli-carrid.

ENDMODULE.

TOP-OF-PAGE.

WRITE text-001 COLOR COL_HEADING.

ULINE.

TOP-OF-PAGE DURING LINE-SELECTION.

WRITE sy-lisel COLOR COL_HEADING.

ULINE.

AT LINE-SELECTION.

CHECK not wa_spfli-carrid is initial.

SELECT fldate

FROM sflight

INTO flightdate

WHERE carrid = wa_spfli-carrid AND

connid = wa_spfli-connid.

WRITE / flightdate.

ENDSELECT.

CLEAR: wa_spfli-carrid.

This example switches to list processing during the screen processing for screen 100. Screen 100 has a single input field - the component CARRID from the ABAP Dictionary structure SDYN_CONN.

It has the following flow logic:

PROCESS BEFORE OUTPUT.

MODULE STATUS_0100.

PROCESS AFTER INPUT.

MODULE CANCEL AT EXIT-COMMAND.

MODULE USER_COMMAND_0100.

The PAI module USER_COMMAND_100 calls screen 500 using the CALL SCREEN statement. This screen encapsulates a basic list. It has the following flow logic:

PROCESS BEFORE OUTPUT.

MODULE CALL_LIST_500.

PROCESS AFTER INPUT.

The module CALL_LIST_500 defines the basic list and switches to list processing. Since the next screen after list processing is screen 0, screen 500 is a one-screen screen chain. After list processing, control returns to the position in USER_COMMAND_100 from which screen 500 was called.

If the user selects a line on the basic list, a detail list appears. This is achieved through the event block AT LINE-SELECTION. The program also contains event blocks for TOP-OF-PAGE and TOP-OF-PAGE DURING LINE-SELECTION, which define page headers for both the basic list and detail list.

Since there is only one list system in this program, there is no need for case distinctions within the list events.

Also, check....

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9d2f35c111d1829f0000e829fbfe/content.htm