report s

[Former Member]

hi,

1.what is the difference between "initialization" and "at selection output" events. can you explain in detail with example.

2.what is the use of end-of-selection event . where we have to specify. eventhough end-of-selection is not given ther is no problem.

what condition we have to mention. can u expleain in detail.

the importance of end-of-selection.

3.what is screen level validation differed from field level validation.

[Former Member]

Hi srisaihari,

1. what is the difference between "initialization" and "at selection output" events. can you explain in detail with example.

Initialisation event is fired ONLY ONCE.

AT SELECTION SCREEN OUTPUT

will be fired

a)whenever we press ENTER KEY

b) click a radio button having some okcode

c) tick a check having some ok code

d) any other fcode

ie., it can be fired multiple times.

regards,

amit m.

[naimesh_patel]

Hello,

1.

initialization

You can set the initial values in this.. this calles only once, when you execute the report.

at selection screen output

This is every time when you press enter or any event

2. end-of-selection.

to get the the contents at end of page of every page.

If you use line-count in the report

like report ztest_np line-count 25(2). so you can print 2 lines in the end-of-page

Regards,

Naimesh

[Former Member]

At-Selection screen output

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

Initialization is the section where the initialization of internal tables, variables, select-option fields, parameters etc takes place.

True, that you can default the values too for parameters/select-option fields in selection-screen.

This event is invoked directly after LOAD-OF-PROGRAM and before the selection screen processing of any existing standard selection screen.

This gives you the one-time opportunity to initialize the input fields of the selection screen, including those defined in the logical database linked with the program.

When run in background, values initialized in initialization event are considered.

For eg: if you want to initialize like this:

carrid-sign = 'I'.

carrid-option = 'EQ'.

carrid-low = 'AA'.

carrid-high = 'LH'.

APPEND carrid TO carrid.

You cannot achieve this by giving 'default' or 'value' at selection-screen.

[Former Member]

1.what is the difference between "initialization" and "at selection output" events. can you explain in detail with example.

Initization event is used to initialize the values on a selection-screen. Also, note that it is triggered only in case of online runs and not batch jobs. So example would be to initialising a date range to start and end days of the month.

At Selection output is used to validate the values entered on the selection screen...example you need a filename to be entered only if the user selects the download radio button etc.

Obivously we can use default and obligatory etc to reduce the coding in the above events.

Regards

Anurag