Why SAP is not fully Object Oriented

[Former Member]

Hi,

Can any one tell me why SAP is not fully Object oriented, I guess there is some problem with screens,,,?

Thanks and Regards

Narendra

[matt]

Why do you think it isn't?

matt

[GrahamRobbo]

Hi Narendra,

SAP have a strategy of making ABAP upwardly compatible. This means ABAP code written for on an earlier release will compile and execute on later releases.

I am told there is still old R/2 ABAP code running inside the latest SAP ERP release.

Cheers

Graham Robbo

[Former Member]

Hello Naren,,

If you switch on debugging mode, you may find the code that is written in standard programs, are written using classess and objects.

eg: the function module reuse_alv_first_display, internally written sing classes and objects.

But there are ways that a user could straightlly write an alv program using classes, objects and methods!!

But simply to make the language simple and understandable, SAP has come out with simple commands!!

But inturn, it is written using ABAP objects!

[Former Member]

Hi Naveena,

Thanks for ur comment, But i still had a doubt ,If every thing in ABAP is object why don't a method of a class accept CALL statement.

[matt]

CALL what? CALL FUNCTION MODULE? CALL TRANSACTION?

What are you wanting to achieve?

matt

[Former Member]

Hi

Any CALL statement to a Screen is not supported.Why

[matt]

Ah, now I see what you are concerned about.

No, you can't call screens directly from ABAP Objects. The way I've seen this overcome is to use Function Groups to do all the screen handling, and call the relevant function module of the group from the class method. Any logic beyond screen handling you should write using Objects.

Effectively, you can use the MVC pattern - but with the VC part in partly non-OO code.

The whole screen handling has long been flawed from a software design perspective, but I guess it's too embedded now to change. Despite its flaws, it's still pretty good. But, alas, not object oriented.

matt