Selection screen

[madan_ullasa]

Hi frnds,

i have a selection screen. And in the at selection-screen event before the value is passed to the PAI i want to get the input value of that field dynamically...

can any1 tell me the function module to use ?

i alwaya assure points :)-

madan......

[Former Member]

Hi madan,

you can populate values in <b>at selection screen out put</b> events. this is some thing like PBO.

or if you want default values then

you can populate the values in <b>Initialization</b> event.

Vijay

[madan_ullasa]

hey vij,

its not like that...

lets say i have 2 parameters a and b in the selection screen...

i enter the value for the field a and this value i want to capture dynamically before i enter the value for b.

[athavanraja]

<i>its not like that...

lets say i have 2 parameters a and b in the selection screen...

i enter the value for the field a and this value i want to capture dynamically before i enter the value for b.</i>

after entering values in field a , there has to be a user command, so that you can capture field a value and do processing for field b value.

without that you wont be able to do it.

REgards

Raja

[Former Member]

Hi Madan,

You can use DYNP_VALUES_READ fm for this.

Some thing like the following,

DATA: lt_dynpfields TYPE STANDARD TABLE OF dynpread.

****fill P_PARAM or S_SELOP-HIGH depending on whether it ****is a parameter or select-option.

lt_dynpfields-fieldname = <your parameter name>.

APPEND lt_dynpfields.

CALL FUNCTION 'DYNP_VALUES_READ'

EXPORTING

dyname = '<your report name>'

dynumb = sy-dynnr

TABLES

dynpfields = lt_dynpfields

EXCEPTIONS

invalid_abapworkarea = 1

invalid_dynprofield = 2

invalid_dynproname = 3

invalid_dynpronummer = 4

invalid_request = 5

no_fielddescription = 6

invalid_parameter = 7

undefind_error = 8

double_conversion = 9

stepl_not_found = 10

OTHERS = 11.

Hope this helps..

Sri

[madan_ullasa]

hi sri,

which at sel-screen event i use for this ?

[Former Member]

Hi Madan,

You did not tell us what you want to do once you find out the value of a before b is entered..

If you want to influence the F4 help for the second parameter then write the code for DYNP_VALUES_READ in the following event,

<b> AT SELECTION-SCREEN ON VALUE-REQUEST FOR b.</b>

Hope this helps..

Sri

[jayanthi_jayaraman]

Hi,

Here is the another sample code.

REPORT ZANAND_TEST.

parameters: p_1 type n,

p_2 type i.

data: field_value type DYNFIELDVALUE.

at selection-screen on value-request for p_2.

perform read_field using 'P_1' changing field_value.

message i398(00) with FIELD_VALUE .

Form read_field changing p_field_value.

data: dyname like d020s-prog value 'ZANAND_TEST',

dynumb like d020s-dnum value '1000'.

data: begin of dynpfields occurs 3.

include structure dynpread.

data: end of dynpfields.

move p_fieldname to dynpfields-fieldname.

append dynpfields.

call function 'DYNP_VALUES_READ'

exporting

dyname = dyname

dynumb = dynumb

translate_to_upper = 'X'

tables

dynpfields = dynpfields

exceptions

invalid_abapworkarea = 01

invalid_dynprofield = 02

invalid_dynproname = 03

invalid_dynpronummer = 04

invalid_request = 05

no_fielddescription = 06

undefind_error = 07.

read table dynpfields index 1.

move dynpfields-fieldvalue to p_field_value.

endform. " read_field

Message was edited by: Jayanthi Jayaraman

[Former Member]

Hi Madan,

Use AT SELECTION-SCREEN OUTPUT.

for more of selection screen events read below:

- selscreen_event

Syntax

...

| { 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 }.

Alternatives:

1. ... OUTPUT

2. ... ON {para|selcrit}

3. ... ON END OF selcrit

4. ... ON BLOCK block

5. ... ON RADIOBUTTON GROUP radi

6. ... { }

7. ... { ON {HELP-REQUEST|VALUE-REQUEST} FOR

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

8. ... ON EXIT-COMMAND

Effect

These additions allow individual evaluation of specific elements of the selection screens of the program. The information as to which selection has triggered the event is contained in the system field sy-dynnr.

Alternative 1

... OUTPUT

Effect

This event is triggered at the screen event PBO of a selection screen. In the event block, the selection screen can be prepared through assignments to the data objects of parameters and selection criteria and through dynamic screen modifications.

Note

The assignments to input fields in the event block AT SELECTION-SCREEN OUTPUT always affect the selection screen and overwrite the user inputs from previous displays of the same selection screen. Assignments in the event blocks LOAD-OF-PROGRAM oder INITIALIZATION, on the other hand, only have an effect at first program start.

Alternative 2

... ON {para|selcrit}

Effect

This event is triggered at the screen event PAI of a selection screen if the content of the input field of a parameter para or a line of a selection criterion selcrit was passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or an error message in the event block makes the fields para and selcrit ready for input again.

No parameter that is defined as a radio button can be specified. For this purpose, the addition ON RADIOBUTTON GROUP is provided.

Note

If a user action takes place in the dialog box for the multiple selection of a selection criterion selcrit, the entries of the selection table are passed to the program, line by line. For each line, the event AT SELECTION-SCREEN ON selcrit is triggered.

Alternative 3

... ON END OF selcrit

Effect

This event is triggered after the selection table selcrit has been fully passed to the program after a user action in the dialog box for the multiple selection has taken place. In the event block, the entire selection table can be checked.

Alternative 4

... ON BLOCK block

Effect

This event is triggered at the screen event PAI of a selection screen if all the input fields of a block block of the selection screen were passed to the ABAP program. In the event block, the user inputs can be checked. Sending a warning or an error message in the event block makes all the fields of the block block ready for input again.

Alternative 5

... ON RADIOBUTTON GROUP radi

Effect

This event is triggered at the screen event PAI of a selection screen if all the fields of a radio button group radi of the selection screen were passed to the ABAP program. In the event block, the user input can be checked. Sending a warning or error message in the event block makes all the radion buttons of the block radi ready for input again.

Note

The individual fields of a radio button group are not passed individually and do not trigger the event AT SELECTION-SCREEN ON par.

Alternative 6

... { }

Effect

The event AT SELECTION-SCREEN itself is triggered as the last event of selection screen processing if all the input values were passed to the program. In this event block, all the user inputs can be checked. Sending a warning or an error message in the event block makes all the screen fields ready for input once again.

Alternative 7

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

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

Effect

The two events ON HELP-REQUEST and ON VALUE-REQUEST are triggered at the screen events POH and POV of a selection screen if - for the input field of a parameter para or one of the input fields of a selection criterion selcrit - the field help F1 or the input help F4 was called. Other selection events are not triggered.

In the event blocks, a self-defined field or input field can be programmed, which overrides any helps possibly defined in the ABAP Dictionary.

Notes

These event blocks can only be implemented for fields of the selection screen that are defined in the same ABAP program and not in a possibly linked logical database.

With the events for the field and input help, no data is transported between the selection screen and the ABAP program. As with general screens, suitable function modules must be used for these. The parameters and selection criteria changed for the input help are transported to the selection screen.

Alternative 8

... ON EXIT-COMMAND

Effect

This event is triggered if the user has called one of the functions Back, Exit or Cancel. In the event block, possible clean-up actions can be executed.

Example

In these executable programs, a standard selection screen and a further selection screen are defined. In the event blocks AT SELECTION-SCREEN, the inputs in the selection screens can be specially handled using the name p_carrid and the screen number in sy-dynnr.

REPORT demo_at_selection_screen.

• Global data

DATA: sflight_tab TYPE TABLE OF sflight,

sflight_wa LIKE LINE OF sflight_tab.

• Selection screens

PARAMETERS p_carrid TYPE spfli-carrid.

SELECTION-SCREEN BEGIN OF SCREEN 500.

SELECT-OPTIONS s_conn FOR sflight_wa-connid.

DATA s_conn_wa LIKE LINE OF s_conn.

SELECTION-SCREEN END OF SCREEN 500.

• Handling selection screen events

AT SELECTION-SCREEN ON p_carrid.

IF p_carrid IS INITIAL.

MESSAGE 'Please enter a value' TYPE 'E'.

ENDIF.

AUTHORITY-CHECK OBJECT 'S_CARRID'

ID 'CARRID' FIELD p_carrid

ID 'ACTVT' FIELD '03'.

IF sy-subrc = 4.

MESSAGE 'No authorization for carrier' TYPE 'E'.

ELSEIF sy-subrc <> 0.

MESSAGE 'Error in authority check' TYPE 'A'.

ELSE.

IF sy-ucomm = 'ONLI'.

CALL SELECTION-SCREEN '0500'.

ENDIF.

ENDIF.

AT SELECTION-SCREEN.

IF sy-dynnr = '0500'.

IF s_conn IS INITIAL.

MESSAGE 'Please enter values' TYPE 'W'.

ELSE.

SELECT *

FROM sflight

INTO TABLE sflight_tab

WHERE carrid = p_carrid AND

connid IN s_conn.

IF sy-subrc <> 0.

MESSAGE 'No flights found' TYPE 'E'.

ENDIF.

ENDIF.

ENDIF.

• Main program

START-OF-SELECTION.

...

Hope it helps...

Lokesh

Pls. reward appropriate points

[Former Member]

Hi u can achieve this with the help of the function module 'DYNP_VALUES_READ'.

Satish