The Delta Calculation DPE compares the current run's Rule Ingest and Tier Ingest records against records stored from the previous run. Records unchanged since the last run are marked Unmodified and not reprocessed. This prevents double-counting when the engine runs multiple times in the same period.
Required Editions
Available in: Enterprise, Unlimited, and Developer Editions that have Rebate and Accrual Management Advanced enabled.
For each Rule Ingest record, the DPE creates a Rule Stage record. For each Tier Ingest record, it creates a Tier Stage record that adds the cumulative qualifying quantity and the date range of contributing transactions.
Tier Stage records for NovaTech, Revenue-Based — combined April quantity is 170 units (70 + 100), which crosses into Tier 2:
Member
Rebate Type
Tier
Cumulative Quantity
Rate
First Transaction
Last Transaction
NovaTech
Revenue-Based
Tier 1
100
2%
Apr 1
Apr 9
NovaTech
Revenue-Based
Tier 2
170
3%
Apr 9
Apr 9
The cumulative quantity of 170 in the Tier 2 row tells the Rule Processing DPE that NovaTech has crossed into Tier 2 for April.
Tier Stage records for Rayler, Volume-Based, Radius — 70 units, stays within Tier 1:
Member
Rebate Type
Product
Tier
Cumulative Quantity
Rate
First Transaction
Last Transaction
Rayler
Volume-Based
Radius
Tier 1
70
$2/unit
Apr 1
Apr 1
Note If a member has no qualifying transactions in a period, the First Transaction and Last Transaction fields in the Tier Stage record are blank. Blank date fields indicate no qualifying activity for that member in the period, not a DPE failure.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.