Just posted a new Tip over on sumneva.com that deals with quickly creating a package that can manage all DML transactions against a table or tables.
I came across this feature in the days of APEX 4.0 EA1. I immediately thought that it was a new APEX 4.0 feature - until I checked 3.2, and it was there too. Basically, this allows you to easily create a table API which can be used to replace the built-in APEX DML processes.
Why would you do this?
If you wanted to create a more secure architecture, you may want to have a tableless schema - thus, the built in processes will do you little good. This API can live in a separate schema, and facilitate all DML calls used to manage your data.
Since it's in a PL/SQL package, you can easily add additional security or data integrity checks before performing any of the DML transactions - another major reason to consider this approach.