Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Abap Objects

Former Member
0 Likes
633

Which are the common uses of the abap objects in abap reports ?

the use of abap object only is limited to generated classes with atributes that use table's fields, and methods that use post and get to the atributes?

Message was edited by: Jose Roberto Milan

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
592

Hi Jose,

Generally the abap objects are mostly used in ALV reporting.

But that is not only limited for ALV reporting. You can use abap objects very similar to your normal programming. Even a simple report could be written in ABAP OBJECTS and very compelex reporting could also be done in ABAP OBJECTS.

Cheers

VJ

3 REPLIES 3
Read only

Former Member
0 Likes
593

Hi Jose,

Generally the abap objects are mostly used in ALV reporting.

But that is not only limited for ALV reporting. You can use abap objects very similar to your normal programming. Even a simple report could be written in ABAP OBJECTS and very compelex reporting could also be done in ABAP OBJECTS.

Cheers

VJ

Read only

anversha_s
Active Contributor
0 Likes
592

hi jose,

Before saying the common use,

I have to mention why OOPs is used.

1. reusability.

2. performance improvement.

3. less coding.

4. very similar to real world scenarios.

its common use in ABAP are,

one ex is , ALV reports.

like that, if we feel if the scenario matches with the real world go with OOPS.

rgds

anver.

if hlped mark points

Read only

uwe_schieferstein
Active Contributor
0 Likes
592

Hello Jose

I do not program reports anymore. If a report is required for batch programming then I would use the report for having a selection screen but nothing more.

My credo is: Use ABAP Objects always and everywhere!

My dialog programs (including reports) are designed according to the MVC architecture (model view control). The controller class corresponds to the "classical" report and is responsible for any user interaction. The entire business logic is encapsulated in the model class (which is usually composed of several other classes). Finally, the view class is responsible for representing the data to the user.

The advantages of such a design will become obvious as soon as you have to maintain or enhance your programs. A clear architecture of the application makes it quite obvious where changes have to be placed.

Regards

Uwe