The Transaction Pipeline is a mechanism that reads a data set from a Data Store and produces an output based on a set of business rules. You would typically run a Transaction Pipeline process if you need to periodize or distribute data from one or more columns, spawn transactions based on a set of business rules or just assign values to rows when exporting data to a target.
A Transaction Pipeline process consists of a Cell Adapter, Distributer, and Spawner component, which all produce output by evaluating business rules. The business rules (Ruleset) are configured in the Feature section of Setting tables, using one Setting table pr feature configuration. (For example, you cannot use the same Setting table to configure business rules for both Cell Adapter and Distributer components).
All Transaction Pipeline target Data Stores must have Tracing Columns.
Also, unless you intend for the entire source transaction data set to be (re)processed every time the pipeline is executed, you need to ensure that the Data Context for both the Transaction Pipeline source and target Data Stores have been properly defined. If a Data Store does not have relationship Dimension bindings that can be used for fully resolving the Data Context, you need to specify the Data Context configuration for the Data Store as part of the Global Data Context.