I am looking for the warm and fuzzy that I've yet to experience while being convinced about this one particular advantage of OO. Particulary involving multiple creation of objects, or instances occurring at one time.
I know the syntax of local and global classes, have done quite a bit of reading, and am familiar with OO coding, but seem to be missing the real-world implications of its use and its superiority to Function Modules in Function Groups.
My understanding is that with data in Function Modules within a Function Group, unlike attributes in a class, a single value in a field has one existence (and value) at runtime for the Function Group. However, for attributes, or objects, in a class, multiple instances may occur at one time. While even as I say this it confuses me, because I do not think I've seen an example of a convincing custom application in SAP in my experience only. Not that I do not doubt SAP's intent, I just am not getting it.
Can any experienced, and already convinced, ABAP OO programmer try to explain an application (in its simplest terms, if possible) where I would create multiple objects where this principle can be seen. And then tell me why I wouldn't be able to accomplish the same thing with Function Modules within Function Groups. Especially, if you have experienced a real-world implementation of this claim using OO.
What I would really like is to have some code that uses Function Modules, then some classes, that both accomplish the same results, that would prove to me that OO, and its classes are superior to Function Modules in Function Groups.I suppose what I really need is an application where multiple instances of the same object is being used, and its advantages.
I will listen to any, or all explanantions. I will accept any code, links, etc. Anything, please to settle my thinking and convince me once and for all.
Edited by: TMM on Jun 17, 2009 4:36 PM
Edited by: TMM on Jun 17, 2009 4:37 PM