Coordinating with external transactions

The application provides the capability to run external code either by raising an event, calling a user exit, or invoking a custom API or service. During these invocations, the external systems can begin a transaction.

Since the external transaction is not part of the Sterling Order Management transaction it could lead to data inconsistencies if the Sterling Order Management transaction is rolled back but the external transaction is not.

External transaction coordination lets the external systems register their transactions with the Sterling Order Management. When the Sterling Order Management is ready to commit its transaction, the YFSTxnCoordinatorUE user exit is invoked, which lets the application handle the commits and rollbacks on the external transactions.