Final delivery disposition for transactional sends using Sendable Reconcilable Data Extension template. Requires transactional reconciliation configuration.
Schema last reviewed 2026-06-17
Opens _ReconcilableDispositionView in the interactive canvas with SQL Sandbox.
| Field | Type | Flags | Relations | Description |
|---|---|---|---|---|
JobId |
Number | PK, FK | _Job.JobID _Sent.JobID |
Email or SMS job ID. |
Channel |
Number | — | — | Channel identifier (Email or SMS). |
Disposition |
Number | — | — | Final delivery disposition status. |
MessageKey |
Text(255) | PK | — | Unique transactional message key. |
SubscriberKey |
Text(254) | FK | _Subscribers.SubscriberKey _Sent.SubscriberKey _Open.SubscriberKey _Click.SubscriberKey _Bounce.SubscriberKey _Complaint.SubscriberKey _Unsubscribe.SubscriberKey |
Subscriber key. |
SubscriberID |
Number | FK, NULL | _Sent.SubscriberID _Open.SubscriberID _Click.SubscriberID _Bounce.SubscriberID _Complaint.SubscriberID _Unsubscribe.SubscriberID |
Subscriber record ID. |
ErrorCodeID |
Number | NULL | — | Error code ID when not delivered. |
ErrorName |
Text(255) | NULL | — | Error name. |
ErrorDescription |
Text(500) | NULL | — | Error description. |
StartTime |
Date | — | — | Transactional message trigger datetime. |
SELECT TOP 100
SubscriberKey, SubscriberID, JobId, Channel, Disposition, MessageKey
FROM _ReconcilableDispositionViewValid in Query Studio and Automation Studio Query Activities. GROUP BY is only needed for aggregates; ORDER BY is optional but recommended with TOP so rows are meaningful. Narrow date ranges on large tracking views to avoid timeouts.