Each form in its own include?

[jrgkraus]

Hi all,

since we upgraded to ERP 2005 (from 4.6C) the abap editor behaves in a different way when creating a new FORM (by doubleclicking on the first identifier of a PERFORM statement). The editor suggests to create a new include each time I perform this operation.

What benefits do I have by placing each form in its own include source? I do beleive that the developers of the ABAP environment did have their motivation to design it in this way? Can anybody tell me?

Greetings

Joerg

[jrgkraus]

Hi all,

since we upgraded to ERP 2005 (from 4.6C) the abap editor behaves in a different way when creating a new FORM (by doubleclicking on the first identifier of a PERFORM statement). The editor suggests to create a new include each time I perform this operation.

What benefits do I have by placing each form in its own include source? I do beleive that the developers of the ABAP environment did have their motivation to design it in this way? Can anybody tell me?

Greetings

Joerg

[Former Member]

Hi,

Its the modularity & traceability bcz of which only one include with several FORMS is better.

Best regards,

Prashant

[Former Member]

faccording to abap standards there should be 5 includes

1. top include- data declerations

2. for pbo

3. for pai

4. for subroutines

5. for events

this is easy to read, undstnd and for modularisation

sice this is accoding to abap stndard so it will automatically prompt to put in include.

[Former Member]

i dont know what motivation those "developers" had when iomplementing this, but even on our ABAP training at the SAP itself, the lecturers told us that this is more a bug than a feature.

Yeah it is good not to throw all your forms in one include, but rather group them logically (all PAI forms in one, all PBO forms in one, andf so on for example), than to have one include for every form.