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

Sharing Screen in Module Pool

Former Member
0 Likes
529

My Requirement is an application to be developed in Module Pool where one screen will be responsible for create,change and display.Let's talk abt an application to create sales order using module pool,this application will have 1 screen where user will input all the required data to create sales order and same screen will be used for displaying and changing sales order . Help is appreciated.

4 REPLIES 4
Read only

Former Member
0 Likes
504

The same screen will be used.

But in Background what is happening...?

If it is create they open the Fields for Input.

if it is change they open the fields for edit/input

if is display then it will be in Display mode.

We can achieve that using LOOP AT SCREEN and modify the screen fields.

If you take the same example

T180-TRTYP contents 'H', "Creation

T180-TRTYP contents 'A', "Display

T180-TRTYP contents 'V', Change

in sales order creation based on the parameter TRTYP , the screens will be changed from Display to Change etc.

According to the Parameter value the coding is done in side sales order application.

Read only

Former Member
0 Likes
504

Hi Manish,

You can't totally get that functionality with only 1 screen.

You can make use of tabstrips in your main screen.. but for that you need to create subscreens for each tab.

regards

padma

Read only

0 Likes
504

Hi ,

You use the same screen for Create , Change and Display. I have worked on a similar requirement .

All you have to do is create three different transaction code with same program name .

Use the system variable sy-tcode , Do the necessary moidifcations .

If you want further help let me know.

Thanks.

Read only

Former Member
0 Likes
504

hi,

You can use a single screen for all operations.

You need to structure down your operations, like under PAI do your operations like this,

Case sy-tcode.

when 'ZCREATE'

<do these operations>

when 'ZCHANGE'

<do these operations>

when 'ZDISPLAY'

< do these operations>

endcase.

For display, where you do not need any input, just make a group which includes all your input fields and disale them so that user can not enter value but only view them.