---
schema_version: "1"
id: e4a5508f6ab64ee4fac0713e60fb9725ff7ca0f4114e70cc3dd73bd5bff5dfad
title: Simple Scenario-Based Data Processing Engine Edits for Rebates
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/admin_rebates_easy_dpe_edit_capabilities.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.admin_rebates_easy_dpe_edit_capabilities.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 09fbf81a8414ea9022892db48f51eed163146e95b038ed4e9ecb5a7326505c81
description: Use the Data Processing Engine Edits for Rebates prebuilt app to easily group and aggregate Rebate Member Product Aggregate records. You don’t need to edit a Data Processing Engine (DPE) definition and modify multiple nodes to add custom grouping and aggregation logic.
products:
  - Partner Cloud
  - Cross Cloud
  - Manufacturing
release: "264"
---
# Simple Scenario-Based Data Processing Engine Edits for Rebates

Use the Data Processing Engine Edits for Rebates prebuilt app to easily group and aggregate Rebate Member Product Aggregate records. You don’t need to edit a Data Processing Engine (DPE) definition and modify multiple nodes to add custom grouping and aggregation logic.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer </strong>Editions that have Rebate Management enabled.</td></tr></tbody></table>

Data Processing Engine definitions filter and process member transactions for a single payout period for a specific rebate type. The results are written back to the Rebate Member Product Aggregate object using flows. The Rebate Member Product Aggregate object stores the aggregated values of all eligible transactions that qualify for payout. These records are then used as the basis of payout calculations for a member for each payout period. Rebate program managers can view the aggregate records to track total transaction quantity, total transaction amount, and other data for members.

Typically, rebate managers have these two common custom requirements:

- Sum up the values of fields such as Invoice Amount, Total Discounts Offered, or Order Quantity to view the aggregated values on a Rebate Member Product Aggregate record.
- Group the aggregated rebate data by fields such as Product Category, Member Priority, or Ship-To Location, to segment Rebate Member Product Aggregate records logically.

To meet these requirements, admins create custom fields on the Transaction Journal and Rebate Member Product Aggregate objects. Then, they edit the required DPE definition to include these custom fields across multiple data source, filter, formula, group and aggregate, join, and writeback nodes. Editing a DPE definition can be complex, especially if you must include multiple custom fields to the grouping and aggregation logic.

Use the Data Processing Engine Edits for Rebates to map up to three custom fields for grouping data, and up to three custom fields for aggregating data. You can also specify whether the aggregation must consider eligibility criteria and product filters in its calculations. Then, download the modified JSON file where the mappings are automatically applied. You don’t need to manually edit the DPE definition. Upload the modified JSON file in the DPE builder to apply the mappings and node changes. You can use the updated definition in your rebate program types.