Skip to Content
0
Former Member
Jul 04, 2009 at 11:55 PM

OO Design--do ABAP Persistent Classes make sense for ALV reports in NW2004?

131 Views

Hello experts,

At our company, we started using ABAP OO in the last year.

I am on NW-2004 . We just acquired a business that is on 4.6C.

We have a lot of customization to bring into our system. There are a lot of reports with common queries that span multiple tables.

I would like to follow the best practice for OO design and create global classes for the data access layer the business logic layer and the UI layer. For the UI layer, I will be utilizing the SALV class, since NW2004 doesn't have ABAP WebDynpro (we don't have a java stack available for development and software change management).

For the data access layer, I would like to use the persistent classes, but without the query manager, it just doesn't make sense.

Thomas Jung said in a blog that he sometimes used SQL to get the keys and then used persistent classes to retrieve the remaining data. But for straight ALV reporting, that just seems inefficient. But it could be that I am just not familiar enough with the technology.

I am looking for suggestions on how to design the data access layer for these intense and commonly used queries.

(Ironically, we will upgrade to NW2004s after this migration -- ouch!)

All ideas are appreciated.

Thanks.