Restriction using OABAP

[Former Member]

Hi there!

Are there any restricitions, where OABAP should not be used? (Speed etc.)

Bye Markus

[former_member69765]

One word answer for you ... NONE

[Former Member]

OOALV's programs will give you dump when you run it in background you have to start using docking container to avoid that.

[Former Member]

I think the OP was referring to OOABAP in general not specifically the ALV.

Cheers

jimbo

[Former Member]

hi,

Refer to the link.

http://www.allinterview.com/showanswers/36463.html

Regards

Sumit Agarwal

[Former Member]

I think your reference here is MISLEADING.

There is NO FUNDAMENTAL REASON WHATSOEVER why OO should be complicated or difficult. The only reason it might seem that way is that you are probably very used to "classical" non OO ABAP.

There's alwways a learning curve but once you get the hang of it you can develop applications MUCH MORE SIMPLY AND QUICKLY and what's more with the MINIMUM of errors. Code is also much more maintainable as well.

Cheers

-K

[Former Member]

HI,

Advantage:

ABAP OOP:

You can customize the Objects

Already more Objects are predefined

JAVA:

Easy to use

Disadvantage:

ABAP:

Very Complicated

Java:

Fully Program

you should write code to create every objects, class

everything

Regards,

manju

[Former Member]

Actually you should restrict the use of NON OO ABAP. Ideally you should also try (where practicable) to replace function modules either by classes or attributes.

You can't obviously re-write the whole of the SAP system especially the older finiancial and HR bits (such has PROVIDE / GET on infotypes) but there is no reason in general why you can't use classes where you would use a "Z" or "Y" function module.

cheers

jimbo