The events captured for replication from an SAP replication system are referred to as transactions, even if they do not directly correspond to an actual transaction in the primary database. For example, if a transaction affects both marked tables and unmarked tables, only the operations that affect the marked tables are captured for replication. Operations on unmarked tables are ignored.
All data-change operations captured for replication exist within a transaction context, that is, only committed transaction operations are replicated; transactions that are rolled back are not replicated.
Even if the data-change events replicated through an SAP replication system are really operations, those operations are grouped in an atomic collection, and they represent the results of a committed transaction in the primary database.