Obligated Amount
Monetary amount obligated on the Other Transaction IDV record. It represents the dollars committed or reported for that instrument in the FPDS award detail.
FPDS Compare
Use Cases
- Dictionary lookup and field explanation
- SQL filtering and grouping
- Analytical reporting and reusable query building
- Spending aggregation and trend analysis
Common Usage
- Summing obligated dollars by agency, vendor, or fiscal year
- Ranking awards by financial magnitude
- Comparing obligation levels across other transaction instruments
Common Mistakes
- Assuming it is an estimated value, ceiling, or total contract value
- Mixing obligated amounts with deobligations or other dollar fields without confirming the transaction logic
Query Guidance
Use SUM(content__OtherTransactionIDV__contractDetail__dollarValues__obligatedAmount) for totals after filtering to the desired population and time period. Cast or coalesce the field to a numeric type, and handle nulls explicitly to avoid undercounting; if records can be revised, deduplicate on the award key and latest action when appropriate.
SQL Examples
Preview values
SELECT
content__OtherTransactionIDV__contractDetail__dollarValues__obligatedAmount AS obligated_amount
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__dollarValues__obligatedAmount IS NOT NULL
LIMIT 25
Aggregate total
SELECT
sum(content__OtherTransactionIDV__contractDetail__dollarValues__obligatedAmount) AS total_value
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__dollarValues__obligatedAmount IS NOT NULL
Distribution overview
SELECT
min(content__OtherTransactionIDV__contractDetail__dollarValues__obligatedAmount) AS min_value,
avg(content__OtherTransactionIDV__contractDetail__dollarValues__obligatedAmount) AS avg_value,
max(content__OtherTransactionIDV__contractDetail__dollarValues__obligatedAmount) AS max_value,
count() AS record_count
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__dollarValues__obligatedAmount IS NOT NULL
Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.