Implementing DAO Pattern in ABAP

[Former Member]

This discussion asked the question of how to develop a DAO pattern in ABAP but i'd like to go a little deeper.

The only answer given suggested the following design pattern:

I don't have an coded example here, but isn't it sufficient for this pattern  to build an interface with some get- and set-methods? This interface can be implemented by several classes with different data retrieval logic. Then a static factory-method could do the job to decide during runtime which actual class is instantiated, returning the interface.

Can anyone give an abstract description of this implementation relative to an SAP module (How would one approach this implementation in MM, PM, FICO, HR)

Can anyone see any issues in this design?

Can anyone provide an alternate design?

Are we missing any steps?

Together we can build a solid abap DAO everyone can use.

[Former Member]

I started to read about DAO pattern some days ago and found this great blog post:

I am starting to implement unit test in my developments and DAO pattern seems to be a clever choice.

Regards,

Felipe