When you join data from the same source, use the Transaction transformation scope to preserve incoming transaction boundaries for a single pipeline. Use the Transaction transformation scope when the Joiner transformation joins data from the same source, either two branches of the same pipeline or two output groups of one transaction generator. Use this transformation scope with sorted data and any join type.

When you use the Transaction transformation scope, verify that master and detail pipelines originate from the same transaction control point and that you use sorted input. For example, in Preserving Transaction Boundaries for a Single Pipeline the Sorter transformation is the transaction control point. You cannot place another transaction control point between the Sorter transformation and the Joiner transformation. In the mapping, the master and detail pipeline branches originate from the same transaction control point, and the Integration Service joins the pipeline branches with the Joiner transformation, preserving transaction boundaries.

The following figure shows a mapping that joins two branches of a pipeline and preserves transaction boundaries: