I’m involved in a project writing Smartforms and reports and other stuff within QM, a module I’ve never worked in before.  Being a conscientous object oriented programmer, I started by writing some classes for, what I think are called, Data Access Objects (DAOs). 

STOP!!!

Just becaucse I used a three letter acroynm, doesn’t mean this is going to be dull and technical.  Now, have another sip of coffee and pay attention.

In QM, there are these things called Notifications.  I’m writing reports that gather information about different kinds of notifications, and analyse that information publish it in a particular way.  So my first DAO class was for notifications.

Once I’d written it, I found I was using it in all subsequent programs I was tasked to write.

And, one night, having come back from the pub, having imbided a few very fine English ales, I thought.

Why am I writing this stuff?

( I mean the ABAP, not this blog).

You see – I can’t be the only developer on the planet who’s needed this data.  Someone else must have needed it before.  So why am I knee deep in debugger and SQL traces, working out where the sampling locations are to be garnered for a maintenance plan. ( That’s for my maintenance plan DAO, not my notification DAO ).

So, on the road to Damascus my home town I had this germ of an idea.  Hopefully it’ll be more infectious than swine ‘flu.

A project. (not called Torchwood), to write reasonably comprehensive DAO classes for all the different Business objects within R/3, ECC.

or whatever it’s called now.

A collaborative, community project.  We could have a motto –

One screen field – one getter.