topic Re: ABAP Objects Design/Organization Issues in Application Development and Automation Discussions

ABAP Objects Design/Organization Issues

Former Member — Wed, 12 Apr 2006 03:29:09 GMT

Hi,

I'm trying to design and implement reusable components using ABAP Objects. I'm familliar with OO concepts and have developed a few applications using C++ and Java.

I'm trying to organize my classes into separate source files (include program in ABAP).

ie.

include program a

CLASS a DEFINITION.

ENDCLASS.

include program b

INCLUDE a.
CLASS b DEFINITION.
 data x TYPE REF TO a.
ENDCLASS.

Lets say I want to write a report that uses both objects a and b. That means I have to include both programs. but since program b includes program a. including both programs a and b in my report would produce redeclarations of class a.

executable program c

REPORT c.

INCLUDE a.
INCLUDE b.   " error: redeclaration of class a

DATA: x TYPE REF TO a.
      y TYPE REF TO b.

This bothers me. Although it would be possible to just include program b, it would be a bit awkward since, i dont care if class a was used in the implementation of class b. Implementation should be abstracted from the user. Besides, everything should be explicit.

Is there a way to organize things as such? Would importing these classes globally would solve the problem.

Thanks.

Re: ABAP Objects Design/Organization Issues

Former Member — Wed, 12 Apr 2006 03:53:38 GMT

Emir,

The way we do OO Programming in ABAP and other languages differ.

In your case, it might be a better option to create these classes as global classes, so that you will not have this issue. You can SE24 to do the same.

Regards,

Ravi

Re: ABAP Objects Design/Organization Issues

Former Member — Wed, 12 Apr 2006 06:15:16 GMT

do i need to keep the source code after i import?

and can you point me to any abap-oo design/organization articles.

I'm pretty much adept with the concepts and syntaxes. My company doesnt do OO architecture to their ABAP programs so I'm trying to cram years of experience for this implementation. Thanks!