Store Aggregated Transactions in an Object

Track payouts effectively by aggregating members’ transaction records for a specific payout period in a single cumulative record. Store this aggregated data either in the default aggregate object, Rebate Member Product Aggregate, or in a custom object. You can aggregate transactions by using an appropriate data processing engine definition.

Required Editions

Available in: Enterprise, Unlimited, and Developer Editions that have Rebate Management enabled.

The Rebate Member Product Aggregate object is available in the Rebate Management data model, and can work for different levels of aggregation such as member, product, or any other custom logic.

If you create a custom aggregate object, ensure that you add these fields.

  • Program Rebate Type
  • Rebate Program Member
  • Rebate Program Payout Period
Note
Note Mark the fields as Required.

You can also add custom fields either to the default Rebate Member Product Aggregate object or to the custom object. For example, if you want to aggregate payout values for a member by country, region, or industry segment, add the required custom fields.

All records in the aggregate object are regularly updated via scheduled flow runs. Rebate program managers can view aggregated records to track total transaction quantity, total transaction amount, and other items.