Stage 4 of 11

Decisive blocker

Inspect the exact production path, owner, and month-end contract that blocks retirement.

One decisive blocker

finance_revenue_close

Finance Analytics · PROD · Month-end close

Exact lineage path

urn:li:dataset:(urn:li:dataPlatform:postgres,payne.finance.legacy_revenue_rollup,PROD)
↓
urn:li:dataset:(urn:li:dataPlatform:postgres,payne.finance.finance_revenue_close,PROD)

Inspect lineage and context

Exact legacy lineage path: urn:li:dataset:(urn:li:dataPlatform:postgres,payne.finance.legacy_revenue_rollup,PROD) → urn:li:dataset:(urn:li:dataPlatform:postgres,payne.finance.finance_revenue_close,PROD); The decisive consumer remains downstream of the retiring dataset in the Day 1 analysis snapshot.
Accountable owner: Finance Analytics; urn:li:corpuser:finance-analytics
Operational context: Month-end close; The catalog description names net_revenue_adjusted, finance_revenue_close, and month-end close.
Required contract mapping: adjusted_net_revenue → net_revenue_adjusted; Numeric, non-null compatibility alias required by the known consumer.

Contract mismatch

Consumer expects: net_revenue_adjusted
Replacement provides: adjusted_net_revenue
Required action: Preserve the known output contract with a bounded alias, then validate and apply it through the official sandbox.