topic Re: At-Selection screen output in Application Development and Automation Discussions

At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:21:15 GMT

Dear All,

Will you please let me know the difference between,

At-Selection screen output and

At-Selection screen on input ?

Thanks,

Ranjan

Re: At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:24:06 GMT

Hi,

At-Selection screen output Event is triggered before screen is diplayed to the user.

At-Selection screen input Event is triggered after user has made an entry on the screen and has initiated an action thereafter.

regards,

Sumeet Mishra

Re: At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:25:19 GMT

Hi,

AT SELECTION-SCREEN OUTPUT

event is triggered. This event block allows you to modify the selection screen directly before it is

displayed.

PARAMETERS: TEST1(10) MODIF ID SC1,

TEST2(10) MODIF ID SC2,

TEST3(10) MODIF ID SC1,

TEST4(10) MODIF ID SC2.

AT SELECTION-SCREEN OUTPUT.

LOOP AT SCREEN.

IF SCREEN-GROUP1 = 'SC1'.

SCREEN-INTENSIFIED = '1'.

MODIFY SCREEN.

CONTINUE.

ENDIF.

IF SCREEN-GROUP1 = 'SC2'.

SCREEN-INTENSIFIED = '0'.

MODIFY SCREEN.

ENDIF.

ENDLOOP.

2.AT SELECTION-SCREEN ON <field>

is triggered when the contents of each individual input field are passed from the selection screen

to the ABAP program. The input field <field> can be checked in the corresponding event block.

If an error message occurs within this event block, the corresponding field is made ready for input

again on the selection screen.

SELECTION-SCREEN BEGIN OF BLOCK PART1 WITH FRAME.

PARAMETERS: NUMBER1 TYPE I,

NUMBER2 TYPE I,

NUMBER3 TYPE I.

SELECTION-SCREEN END OF BLOCK PART1.

SELECTION-SCREEN BEGIN OF BLOCK PART2 WITH FRAME.

PARAMETERS: NUMBER4 TYPE I,

NUMBER5 TYPE I,

NUMBER6 TYPE I.

SELECTION-SCREEN END OF BLOCK PART2.

AT SELECTION-SCREEN ON BLOCK PART1.

IF NUMBER3 LT NUMBER2 OR

NUMBER3 LT NUMBER1 OR

NUMBER2 LT NUMBER1.

MESSAGE E020(HB).

ENDIF.

AT SELECTION-SCREEN ON BLOCK PART2.

IF NUMBER6 LT NUMBER5 OR

NUMBER6 LT NUMBER4 OR

NUMBER5 LT NUMBER4.

MESSAGE E030(HB).

ENDIF.

Re: At-Selection screen output

hymavathi_oruganti — Tue, 31 Jan 2006 11:25:37 GMT

at selection-screen output

event is used to validate screen table fields. it is triggred after selection screen is loaded.

there is no event "at selection-screen on input".

but there is

"at selection-screen on para/select-option"

Re: At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:25:44 GMT

<b>At-Selection screen output</b>

This event is executed at PBO of the selection screen every time the user presses ENTER - in contrast to INITIALIZATION. Therefore, this event is not suitable for setting selection screen default values. Also, since AT SELECTION-SCREEN OUTPUT is first executed after the variant is imported (if a variant is used) and after adopting any values specified under SUBMIT in the WITH clause, changing the report parameters or the selection options in AT SELECTION-SCREEN OUTPUT would destroy the specified values.

At-Selection screen

This is PAI--Process after Input...

Cheers:-)

Mithlesh

Re: At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:26:50 GMT

Hi,

They are like PBO and PAI sections of normal Module pool programming.

Generally Any Dynamic screen modifications like making fields disable/enable etc are done in at selection-screen output.

All the validations on the entered values are done in at selection screen on input.

Re: At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:27:02 GMT

Hi,

At-Selection screen output Event is used for changing the screen elements after the user presses ENTER.

At-Selection screen Event is triggered after user has made an entry on the screen and has initiated an action thereafter.

regards,

Nelson

Re: At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:27:57 GMT

Hi,

at slection-screen output is like PBO .

here you can modify the screen.

but i don't know what is this for

<b>at selection-screen on input.</b>

but at selection-screen on field is there,

you can validate a particular field.

regards

vijay

Re: At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:28:20 GMT

I think there is no SELECTION-SCREEN on INPUT

Possible types:

...

| { ON {para|selcrit} }

| { ON END OF selcrit }

| { ON BLOCK block }

| { ON RADIOBUTTON GROUP radi }

| { }

| { ON {HELP-REQUEST|VALUE-REQUEST}

| FOR {para|selcrit-low|selcrit-high} }

| { ON EXIT-COMMAND }.

At slection-screen output - Processing Before Output.

Re: At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:29:04 GMT

Hi ,

At-Selection screen output event is fired

before selection screen is displayed.

This event can be used to disable certain fields

on selection screen.It is similar to PBO of

module pool.

loop at screen.

if screen-name = 'MATNR'.

screen-enable = 1.

modify screen.

endif.

endloop.

At-Selection screen on input event is fired upon

user entering some values similar to PAI of module

pool.

This event can be used to validate data entered

by user is valid or not.

select single matnr into mara-matnr from mara

where matnr = p_matnr.

if sy-subrc eq 0.

message e000 with 'invalid data'.

endif.

Regards

Amole

Re: At-Selection screen output

Former Member — Tue, 31 Jan 2006 11:59:03 GMT

Hi,

Case 1:

=======

"At-Selection screen" output Event is triggered before screen is diplayed to the user.

Example:

========

You have two radio buttons and three input fields. Out of which one field is common to both the radio button and other button should be displayed depending up on the radio button selected, in this case you can make the 2nd and 3rd field visible/invisible depending up on the radio button selected. So when you click a radio button the event "At-Selection screen" will be triggered, so you can make the necessary field ( 2nd or 3rd) visible/invisible using this.

This is as similar to PBO(Process Before Output).

Case 2:

=======

"At-selection screen ON....."

Example:

=======

Suppose if you want to restrict a value that you are entering in the field on the screen then you can use this event,

At-selection screen <P_VAR>.

If the report starts an error dialog at this point, precisely these fields become ready for input again until you enter correct value.

Regs,

Venkat Ramanan