Track Contract Commitment Burn-Down Over Time
Inspect the result, its parameters and the SQL behind it.
- Source
- FOCUS use-case library
- Data
- FOCUS 1.0 sample
- Status
- Not in v1.0 sample
- Mode
- Read-only
- Library snapshot (UTC)
- 2026-10-08
- Source
- FOCUS use-case SQL
- Status
- Not in v1.0 sample
- Results
- Not run
- Mode
- Read-only
- Library snapshot (UTC)
- 2026-10-08
ContractApplied and its ContractCommitmentID / ContractCommitmentAppliedCost elements are absent from the v1.0 sample, so contract-commitment burn-down cannot be tracked.
Original FOCUS SQL
SELECT CU.BillingPeriodStart, CU.ServiceProviderName, CU.BillingAccountId, JSON_VALUE(CA, '$.ContractCommitmentID') AS ContractCommitmentId, SUM(CAST(JSON_VALUE(CA, '$.ContractCommitmentAppliedCost') AS FLOAT64)) AS AppliedCost, SUM(CU.EffectiveCost) AS TotalEffectiveCost FROM focus_data_table CU CROSS JOIN UNNEST(JSON_EXTRACT_ARRAY(CU.ContractApplied, '$.Elements')) AS CA WHERE JSON_VALUE(CA, '$.ContractCommitmentID') IS NOT NULL AND BillingPeriodStart >= ? AND BillingPeriodStart < ? GROUP BY CU.BillingPeriodStart, CU.ServiceProviderName, CU.BillingAccountId, JSON_VALUE(CA, '$.ContractCommitmentID') ORDER BY BillingPeriodStart, ContractCommitmentId