When a requesting application with an active transaction runs a remote procedure, the transaction is not propagated to the remote procedure. Rather, the remote procedure acts as if it is the first procedure of the application, and follows the normal SpeedScript rules for starting and terminating transactions. If a requesting application and a remote procedure connect to the same database, each database connection comprises a separate transaction.
For more information on remote procedures, see OpenEdge Application Server: Developing AppServer Applications.
