Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

call sub screen

prasanth_kasturi
Active Contributor
0 Likes
1,007

'Call subscreen' is written in flow logic but not in the actual program like 'call screen' why??

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
811

Hi,

Generally, operations on screens are dealt in dynpro's or what we traditionally call module pool. So we could call a subscreen inside any screen and is not possible anywhere else. A subscreen could be called only in a designated Subscreen area and that too could be dealt in Module pool.

Hence you generally do not get an oppurtunity to call subscreens in normal programs.

Hope this clarifies ur doubt... else plz revert back.

Reward points if this helps,

Kiran Kumar S

5 REPLIES 5
Read only

Former Member
0 Likes
811

No it is to create sub screen.

Report programming is done in ABAP language. 'Call screen' is a ABAP language element to call a screen from report.

Dialog programming is done in a language similar to ABAP but not exact to ABAP. It is called screen language. CALL SUBSCREEN is a element of screen language like CHAIN, FILED, TABLE CONTROL etc.

Ex:


PROCESS BEFORE OUTPUT.
  MODULE STATUS_100.
  CALL SUBSCREEN: AREA1 INCLUDING SY-REPID NUMBER1,
                  AREA2 INCLUDING SY-REPID NUMBER2.

PROCESS AFTER INPUT.
  MODULE CANCEL AT EXIT-COMMAND.
  MODULE SAVE_OK.
  CALL SUBSCREEN: AREA1,
                  AREA2.
  MODULE USER_COMMAND_100.

Subscreen is similar to include in ABAP programming language.

There are three steps to define sub-screen:

1. Define the subscreen area on a screen.

2. Define suitable sub screen screen.

3. Include the subscreen in the subscreen area.

Edited by: Abhishek Sarkar on Feb 7, 2008 11:21 AM

Read only

Former Member
0 Likes
811

Hi,

Usually used for pop up screens. Many times, there is a need for user to enter additional information or secondary information on another screen or pop up screen. Once the user enters the data, he should be able to go back to main screen or to the screen where he started. This is not possible by using SET SCREEN. CALL SCREEN achieves this functionality.

Syntax

Call Screen 200.

Will simply call a screen number 200 from a main screen. Once the screen is displayed the user can enter all the data and return to the main screen by clicking BACK button.

To call screen as pop up screen the syntax is

Call screen starting at <col.no.> <line no>

Ending at <col no> <line no>.

In this case window will be popped as window and user can close it by using BACK button.

Regards,

Bhaskar

Read only

Former Member
0 Likes
812

Hi,

Generally, operations on screens are dealt in dynpro's or what we traditionally call module pool. So we could call a subscreen inside any screen and is not possible anywhere else. A subscreen could be called only in a designated Subscreen area and that too could be dealt in Module pool.

Hence you generally do not get an oppurtunity to call subscreens in normal programs.

Hope this clarifies ur doubt... else plz revert back.

Reward points if this helps,

Kiran Kumar S

Read only

0 Likes
811

Hii

Kiran plz be a bit more clear plz....

Read only

Vijay
Active Contributor
0 Likes
811

HI

you can call sub screen like this

process before output.

module status_0101.

call subscreen : headerdetails including 'ZPURCR_71945' '1010',

lineitems including 'ZPURCR_71945' '1011',

schedulelines including 'ZPURCR_71945' '1012'.

process after input.

module exit_0101 at exit-command.

call subscreen: headerdetails ,

lineitems,

schedulelines.

module user_command_0101.

regards

vijay

reward points if helpful