FPDS Query Library
About Us
Contact Us

Effective Date

The date on which the Other Transaction IDV becomes effective under the contract detail's relevant contract dates. It marks when the instrument’s terms begin to apply for the record represented in FPDS.

Family: Other Transaction IDV
Category: Dates
Data Type: string
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__relevantContractDates__effectiveDate
Title
Effective Date
FPDS Path
OtherTransactionIDV/contractDetail/relevantContractDates/effectiveDate
Description
The date on which the Other Transaction IDV becomes effective under the contract detail's relevant contract dates. It marks when the instrument’s terms begin to apply for the record represented in FPDS.
Business Meaning
This date is important for establishing the start of procurement activity, aligning obligations to the correct fiscal period, and sequencing awards, modifications, and downstream actions. Analysts use it to measure award timing, compare pipeline vs. execution dates, and support time-based reporting on Other Transaction agreements.
Example Value
2021-08-11 00:00:00
Observed Non-Null Count
13,417

FPDS Compare

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__relevantContractDates__effectiveDate
FPDS XML Path
OtherTransactionIDV/contractDetail/relevantContractDates/effectiveDate
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionIDV/contractDetail/relevantContractDates/effectiveDate' into the SQL-ready variable 'content__OtherTransactionIDV__contractDetail__relevantContractDates__effectiveDate'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • Timeline, cohort, and period analysis

Common Usage

  • filtering awards by start date or reporting period
  • grouping obligations by fiscal year or quarter
  • ordering events in contract lifecycle analyses

Common Mistakes

  • using the raw string without converting it to a date type
  • confusing effective date with obligation, action, or modification dates

Query Guidance

Cast or parse the value to a DATE/DATETIME field in SQL, then use it in WHERE clauses, date ranges, and fiscal-period logic. Prefer inclusive start and exclusive end filters for period analysis, and do not assume the string includes meaningful time-of-day information unless observed in the source data.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__contractDetail__relevantContractDates__effectiveDate AS effective_date
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__relevantContractDates__effectiveDate IS NOT NULL
LIMIT 25

Top values

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