Hi,
As you know standard way of development of exit variables is to isert ABAP code directy in main include of the exit.
However with a big number of exits and serveral teams working in parallel, this is not a good practice. I've herad about projects using ABAP OO to encapsulate and isolate code of every exit.
Do you have an experience with usiage of ABAP OO to code exits? Could you provide structure you use (e.g. one class for all exits with different mentods, one class for every exit etc.) with some code samples?
BTW - yes, I have read the blog /people/ed.herrmann/blog/2007/01/16/simplify-your-bw-enhancements-for-global-reporting-variables and appreciate work of its author, but this is not enough for me - I cannot import in the system custom code that I do not know what is exactly doing. I preffer to undestand better whole concept. Especially when it requires download and installation of some SAPlink plugins
Thanks in advance,
Marcin