topic Re: Initialization event flow in Application Development and Automation Discussions

Initialization event flow

Former Member — Fri, 28 Jun 2013 07:03:05 GMT

Hi Experts,

I was just practicing and came to know that:

PARAMETERS P_MATNR TYPE MATNR DEFAULT 'A112233'.

INITIALIZATION.
WRITE 'INITIALIZATION'.

START-OF-SELECTION.
WRITE 'START OF SELECTION'.

END-OF-SELECTION.
WRITE: 'END OF SELECTION'.

does not write INITIALIZATION.

But without PARAMETERS statement it writes.

can anyone explain me why it is so.

Thanks,

Vibhor

Re: Initialization event flow

matt — Fri, 28 Jun 2013 07:43:24 GMT

The parameters statement puts a screen in the way, so when you get the "start-of-selection", you've got a new screen.

If you want to see the sequence of events, try using the MESSAGE statement instead of write.

Re: Initialization event flow

Former Member — Fri, 28 Jun 2013 07:55:02 GMT

Beside the question, Can you imagine a need in reallife to use a write statement before the Start-of-Selection Block?

Re: Initialization event flow

Former Member — Fri, 28 Jun 2013 08:36:07 GMT

Thanks a lot Matthew.

Re: Initialization event flow

Former Member — Fri, 28 Jun 2013 08:39:41 GMT

Hi Nikolaus,

It is not required to have a write statement before the start of selection because only after selection is executed you can have write statement.

Re: Initialization event flow

Former Member — Fri, 28 Jun 2013 08:56:45 GMT

he he he,

Initialization is the event before screen is getting callled.

it executes the write statement, but where it should write???

Put messages of type I then you will get the exact result what you want.

Regards,

Re: Initialization event flow

Former Member — Fri, 28 Jun 2013 09:38:28 GMT

Hi Vijay,

If you remove the PARAMETERS statement then it is writing it anyway.

Matthew is right, because the selection screen comes the a way.

Re: Initialization event flow

Former Member — Sat, 29 Jun 2013 05:34:07 GMT

Dear Matthew,

It is a very basic question. it should be rejected actually. Any one can find answer very easily for these type of questions.

Re: Initialization event flow

matt — Sat, 29 Jun 2013 14:43:49 GMT

I thought that at first, but then thought - if someone asked me what would happen in this situation, I wouldn't have known without writing the code. So I decided the question, while basic, was sufficiently interesting to let pass.

Moderation is always a subjective judgement call. I've no objection to newbies asking reasonable basic questions. It's the ones that are answered easily be searching or having had done BC400 that will get rejected.

Re: Initialization event flow

Former Member — Sun, 30 Jun 2013 10:50:23 GMT

Hi Vibhor,

The initialization will gets printed without selection screen because it is the first event that gets trigger. So if there is a selection screen, then after the initialization event the screen will be displayed then after user action other events will gets trigger and the previous list will be refreshed.

To know the correct execution just put a break point at report statement and in the debugging mode just see the display list which will be under Miscellaneous. There you can find in detail

Re: Initialization event flow

Former Member — Mon, 01 Jul 2013 05:07:33 GMT

Thanks Shravan.

This "Display under miscellaneous" thing was new to me.

It really helped thanks a lot.

-Vibhor