Status Description

Human-readable label for the transaction status associated with an Other Transaction IDV record. It is the descriptive companion to the coded Status field and explains the status value in plain language.

Family: Other Transaction IDV
Category: General
Data Type: string
Semantic Type: description
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__transactionInformation__status__description
Title
Status Description
FPDS Path
OtherTransactionIDV/contractDetail/transactionInformation/status/description
Description
Human-readable label for the transaction status associated with an Other Transaction IDV record. It is the descriptive companion to the coded Status field and explains the status value in plain language.
Business Meaning
This field helps analysts interpret lifecycle state in procurement records without relying only on abbreviated or coded status values. It is useful for separating active, final, or otherwise resolved transactions when evaluating award portfolios, obligation timing, and contract administration outcomes.
Example Value
FINAL
Observed Non-Null Count
13,417

FPDS Compare

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

Paired Field

Relationship
description_of
Variable

Use Cases

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

Common Usage

  • Interpreting the coded Status field
  • Filtering records by lifecycle state such as final or active
  • Validating or grouping transaction records in status-based analyses

Common Mistakes

  • Using the description instead of the Status code as the primary filter when exact logic is required
  • Assuming the description is standardized across all records or agencies

Query Guidance

Join or filter on the paired Status code when possible, then use this field for display, validation, or CASE-based mapping of codes to readable labels. In SQL, group by the code and use the description as a label, and review distinct values to confirm how source systems populate the text.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__contractDetail__transactionInformation__status__description AS status_description
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__transactionInformation__status__description IS NOT NULL
LIMIT 25

Top values

SELECT
    content__OtherTransactionIDV__contractDetail__transactionInformation__status__description AS value,
    count() AS record_count
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__transactionInformation__status__description 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.