FPDS Query Library
About Us
Contact Us

Effective Date

Date on which the Other Transaction award becomes effective and the agreement’s terms take effect. In FPDS, this is the contractual effective date recorded in the contract detail date set.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__contractDetail__relevantContractDates__effectiveDate
Title
Effective Date
FPDS Path
OtherTransactionAward/contractDetail/relevantContractDates/effectiveDate
Description
Date on which the Other Transaction award becomes effective and the agreement’s terms take effect. In FPDS, this is the contractual effective date recorded in the contract detail date set.
Business Meaning
Analysts use this date to anchor award timing, compare execution timing across awards, and establish the correct start point for period-based reporting. It is important for lifecycle analysis, obligation timing, and sequencing events such as award, modification, and performance windows.
Example Value
2022-07-08 00:00:00
Observed Non-Null Count
38,893

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__relevantContractDates__effectiveDate
FPDS XML Path
OtherTransactionAward/contractDetail/relevantContractDates/effectiveDate
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/relevantContractDates/effectiveDate' into the SQL-ready variable 'content__OtherTransactionAward__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

  • calendar or fiscal period grouping of awards
  • sequencing award dates against modification and completion dates
  • filtering records for effective-date-based analysis

Common Mistakes

  • assuming it is the same as the signed date or obligated date
  • grouping raw timestamp strings without normalizing the date component

Query Guidance

Convert the string to a DATE or TIMESTAMP type before filtering or aggregating. Use it in WHERE clauses for effective-date windows and in DATE_TRUNC or EXTRACT logic for monthly, quarterly, or fiscal reporting; if the source stores midnight timestamps, strip the time portion when day-level precision is sufficient.

SQL Examples

Preview values

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

Top values

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