If your application requires database transactions to span called forms, you need to understand the difference between posting and committing.
During a default commit operation, Oracle Forms issues the SQL statements necessary to update, delete, or insert records that have been marked in the form as changed, deleted, or inserted. Oracle Forms then issues the COMMIT statement to commit these transactions in the database.
Posting consists of writing updates, deletions, and insertions in the form to the database, but not committing these transactions to the database. You can explicitly cause Oracle Forms to post without committing by executing the POST Built-in procedure.
When an application executes the POST procedure, Oracle Forms does all of the default validation and commit processing, but does not issue the COMMIT statement to finalize these transactions.
Since posted transactions have been written to the database, Oracle Forms does not have to maintain the status of the affected records across called forms. More importantly, because these transactions have not been committed, they can be rolled back programmatically. You can take advantage of this functionality to manage transactions across called forms.