Refine Accruals with Benefit Mappings

To create a benefit mapping, Salesforce recommends that the admin first creates similar custom fields on the Program Rebate Type Benefit and Transaction Journal objects.

In the Advanced engine, the system uses anchors within Data Cloud to group transactions for accrual calculations. You configure grouping by adding Program Rebate Type Aggregation Field records to the rebate type, each record specifies one aggregate field.

By default, the engine aggregates by Member only, using a single Aggregation Field record with the aggregate field set to Member. To aggregate by Member and Product, complete both of these steps:

• Add a second Aggregation Field record with the aggregate field set to Product.
• Customize the Pre-Processing DPE so that the Product anchor is set.

For steps to customize the Pre-Processing DPE to set the Product anchor or a custom anchor, see Extend Accrual Aggregation with Custom Anchors.

The engine supports up to five aggregation anchors in total — Account and Product as built-in dimensions, and three custom anchors (Anchor1, Anchor2, Anchor3).

To track accruals by additional dimensions such as Region, Territory, or Channel, use the custom anchors (Anchor 1, Anchor 2, Anchor 3) to create custom aggregation criteria. The admin must ensure these custom fields are mapped to the corresponding Data Lake Objects (DLOs) during setup.

Note Unlike Rebate and Accrual Management Advanced, the Advanced engine does not require the Rebate Member Product Aggregate object. Instead, the mapping ensures the Rule Processing DPE correctly identifies the criteria within Data Cloud.

Example

A company wants to differentiate the benefits of a volume-based rebate type by Product Category. The admin must ensure the Product Category information is available on the Transaction Journal and the Program Rebate Type Benefit record.

Object	Field	Data Type	Objective
Program Rebate Type Benefit	Product Category	Lookup	Enables the program manager to define distinct benefit values and accrual rates for specific product segments within the same benefit tier.
Transaction Journal	Product Category	Lookup	Provides the source data for the engine to match against the benefit criteria.

The program manager then maps these fields in the Program Rebate Type Benefit Mapping object. The engine uses this mapping to "Anchor" the calculation to the specific product category during the high-volume processing in Data Cloud.

Note When the engine matches transaction data to benefit mapping criteria, only exact matching is supported. For example, if a benefit is mapped to Product Category "Compactors", only transactions where the Product Category field exactly equals "Compactors" are matched to that benefit. If no exact match is found, benefit isn't applied to the transaction.

To capture product category information, the program manager can define benefit tiers as shown here. The program manager maps the fields in the Rebate Type Benefit Mapping object by defining these fields:

• Transaction Field: The field on the Transaction Journal that serves as the source criteria.
• Benefit Field: The field on the Program Rebate Type Benefit that defines the qualifying criteria.

Benefit Tier	Minimum Value	Maximum Value	Benefit Value	Product Category
Tier 1	101	500	$3 per unit	Hammers
Tier 2	501	Leave it blank	$8 per unit	Hammers
Tier 3	101	500	$5 per unit	Compactors
Tier 4	501	Leave it blank	$10 per unit	Compactors