Status

Human-readable status of the Other Transaction Award transaction record. The example value "F" indicates this field may store a coded value rather than a free-text status description, so its exact meaning should be confirmed against observed FPDS code usage or paired descriptive fields if available.

Family: Other Transaction Award
Category: General
Data Type: string
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__contractDetail__transactionInformation__status
Title
Status
FPDS Path
OtherTransactionAward/contractDetail/transactionInformation/status
Description
Human-readable status of the Other Transaction Award transaction record. The example value "F" indicates this field may store a coded value rather than a free-text status description, so its exact meaning should be confirmed against observed FPDS code usage or paired descriptive fields if available.
Business Meaning
This field helps analysts identify where an award transaction sits in its lifecycle and separate finalized records from preliminary, amended, or otherwise nonfinal entries. It is useful for filtering award populations, tracking record completeness, and avoiding double counting in procurement performance and obligation analyses.
Example Value
F
Observed Non-Null Count
38,894

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__transactionInformation__status
FPDS XML Path
OtherTransactionAward/contractDetail/transactionInformation/status
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/transactionInformation/status' into the SQL-ready variable 'content__OtherTransactionAward__contractDetail__transactionInformation__status'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building

Common Usage

  • Filter to finalized or active transaction records
  • Group records by transaction lifecycle state
  • Exclude nonfinal entries from obligation or award counts

Common Mistakes

  • Assuming the value is always descriptive text rather than a code
  • Using status alone to infer award validity without checking related transaction fields

Query Guidance

Use this field in WHERE clauses to limit analysis to the relevant status values once the code set is confirmed, and in GROUP BY queries to summarize record states. When joining or aggregating, pair it with transaction identifiers and action/date fields so you do not count multiple statuses for the same award event as separate awards.

SQL Examples

Preview values

SELECT
    content__OtherTransactionAward__contractDetail__transactionInformation__status AS status
FROM fpds.data
WHERE content__OtherTransactionAward__contractDetail__transactionInformation__status IS NOT NULL
LIMIT 25

Top values

SELECT
    content__OtherTransactionAward__contractDetail__transactionInformation__status AS value,
    count() AS record_count
FROM fpds.data
WHERE content__OtherTransactionAward__contractDetail__transactionInformation__status IS NOT NULL
GROUP BY value
ORDER BY record_count DESC
LIMIT 25

Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.