Transaction Processing and Business Functions
An application or batch process establishes the primary transaction boundary. If an application calls a business function in Event Rules, the database operations in the business function are grouped within the boundaries of their parent application.
Master business functions should not define their own boundaries.
If your application calls several business functions, and you need to include the business functions in the transaction boundary, you must enable transaction processing for the application. Should a failure occur and you need to roll back database operations for the business function, you must designate Include in Transaction on the business function call.
Note: When you use business functions
within a transaction, you must be careful not to cause a deadlock. If two functions
modify the same table, you might cause a deadlock if you include one function in the
transaction but not the other. On the other hand, if a business function that
selects records for information also updates or inserts data in other tables, you
might want to split the business function.