You are here:
Output Layer
The Source Generation DPE writes final calculated results to this DLO and syncs them back to Salesforce Core as Program Rebate Type Accrual Source records.
Required Editions
| Available in: Enterprise, Unlimited, and Developer Editions that have Rebate and Accrual Management Advanced enabled. |
AccrualAndPayoutOutput_dll
| Label | API Name | Type | Description |
|---|---|---|---|
| ID | Id__c | Text | Unique identifier for the output record |
| Accrual And Payout Output Meta | AccrualAndPayoutOutputMeta__c | Text | Links to the output metadata definition |
| Accrual And Payout Rule | AccrualAndPayoutRule__c | Text | Links to the rule used for calculation |
| Accrual And Payout Input | AccrualAndPayoutInput__c | Text | Links to the input record used |
| Account | Account__c | Text | Member account identifier |
| Source1 | Source1__c | Text | Primary source system identifier |
| Source2 | Source2__c | Text | Secondary source system identifier |
| Anchor1 | Anchor1__c | Text | Custom aggregation dimension 1 |
| Anchor2 | Anchor2__c | Text | Custom aggregation dimension 2 |
| Anchor3 | Anchor3__c | Text | Custom aggregation dimension 3 |
| Reason | Reason__c | Text | Reason code for the calculated output |
| Status | Status__c | Text | Processing status |
| Value | Value__c | Number | Final calculated accrual amount |
| Active | Active__c | Boolean | Indicates whether the record is active |
| Created Date Time | CreatedDateTime__c | DateTime | Timestamp when the record was created |
| Effective Date | EffectiveDate__c | Date | Effective date of the output |
| Input Date | InputDate__c | Date | Activity date from the source transaction |
| Usage Tag | UsageTag__c | Text | Partitions records by business module |
| Sfdc Organization ID | SfdcOrganizationId__c | Text | Org identifier for multi-tenant isolation |
| Code | Code__c | Text | Output type code |
| Accrual And Payout Tier | AccrualAndPayoutTier__c | Text | Links to the tier applied for this calculation |
If transactions are missing from your accruals, the AccrualAndPayoutTierStage_dll is the primary diagnostic DLO. Check these fields:
| Field | What to Look For |
|---|---|
| NewStartDate__c / NewEndDate__c | If null, the engine found no qualifying transactions for that member in the period for the given tier. |
| NewFromValue__c / NewToValue__c | Use these to verify if the cumulative quantity is actually crossing the expected tier boundary |
| RowStatus__c | Confirms whether the record was reprocessed or bypassed as Unmodified. A status of Unmodified is expected on re-runs where nothing changed — it's a problem only when you expect new or updated data. |
| CumulativeQualifierValue__c | Compare against NewFromValue__c / NewToValue__c to confirm whether the cumulative quantity is crossing the expected tier boundary. |
| NewInputStart__c / NewInputEnd__c | Use these to trace the first and last input transactions the engine counted in the tier. |
| NewInputStartOffset__c / NewInputEndOffset__c | Use these to confirm the engine isn't double-counting or skipping input across tier boundaries. The offset accounts for the input measure value already counted in the previous tier. |
Did this article solve your issue?
Let us know so we can improve!
