[kevinsky]

Yes, looking backwards PL/SQL code looks and acts like an API to the data. At Oracle conferences they will tell you that keeping your business logic in stored procedures means you don't have to duplicate it if a second application wants access to your data.

It all seems quaint now but the last time I built a web app with Entity framework and Oracle the EF part worked fine for simple CRUD operations but for complicated reporting and analysis stored procedures and views worked extremely well.

It is all about where you want your business logic. You can put it in the front end or the database or anywhere inbetween but the real test is whether it is documented, commented and easy to understand.