Type 1 & Type M

Former Member — Wed, 18 Oct 2006 06:34:52 GMT

If I create a screen in Type 1 program by using Call screen 100; and use events PBO, PAI etc & design the screen in SE51. Is it ok to still say that it is a module pool program because of use of the events or it is a report & not a module pool?

Re: Type 1 & Type M

gopi_narendra — Wed, 18 Oct 2006 06:36:48 GMT

Its a executable report program not a module pool program. for reference see this program DEMO_DYNPRO_TABCONT_LOOP

<b>PLEASE CLOSE THIS THREAD IF PURPOSE DONE</b>

Regards

- Gopi

Message was edited by: Gopi Narendra

Re: Type 1 & Type M

Former Member — Wed, 18 Oct 2006 06:40:29 GMT

Hi Vishal,

It will remain executable program only.

You can not call it as a module pool

Re: Type 1 & Type M

shishupalreddy — Wed, 18 Oct 2006 08:30:46 GMT

Hi,

It z a report program only

regards,

Re: Type 1 & Type M

Former Member — Wed, 18 Oct 2006 09:03:00 GMT

good

Type 1->

You can start a type 1 program by entering its program name. For this reason, they are also known as executable programs. When you start a type 1 program, processors are started in the runtime environment that call a series of processing blocks (event blocks) in a predefined sequence. The sequence is oriented towards reporting tasks. This is why executable programs are also known as reports. For further information, refer to Running Programs Directly - Reports.

A special type of type 1 program is a logical database. You can start logical databases together with reports. A logical database contains subroutines that are called by an invisible system program in a prescribed sequence for type 1 programs. The subroutines make certain reporting functions reusable.Users can run executable programs either in the foreground, by entering the program name in Transaction SA38 (System ® Services ® Reporting), or as a background job. You can only run a program in the background if there is no dialog-controlled execution. You do not need to assign a transaction code to an executable program, although you may if you wish, and you do not have to use the Screen Painter to create any screens for it.

TYPE M PROGRAM->

Type M programs can only be started using a transaction code. A transaction code starts a screen, which consists of the screen itself and its flow logic. Screen flow logic can call special processing blocks (dialog modules) in the corresponding ABAP program. Since type M programs contain mostly dialog modules, they are known as module pools. For further information about running module pools, refer to Dialog-controlled Program Execution - Transactions.

here i given some hints about the TYPE 1 and TYPE M pgoram, so what you have developed is a type 1 program so it cant not be a module pool or TYPE M program.

thanks

mrutyun^

topic Re: Type 1 & Type M in Application Development and Automation Discussions

Type 1 & Type M

Re: Type 1 & Type M

Re: Type 1 & Type M

Re: Type 1 & Type M

Re: Type 1 & Type M