FPDS Query Library
About Us
Contact Us

Created Date

Timestamp indicating when the Other Transaction award transaction record was created in FPDS. It represents the system-created date and time for the transaction entry, not necessarily the award action date or the date the underlying procurement occurred.

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__createdDate
Title
Created Date
FPDS Path
OtherTransactionAward/contractDetail/transactionInformation/createdDate
Description
Timestamp indicating when the Other Transaction award transaction record was created in FPDS. It represents the system-created date and time for the transaction entry, not necessarily the award action date or the date the underlying procurement occurred.
Business Meaning
This field helps analysts track record timing, ingestion order, and reporting lag in FPDS workflows. It is useful for understanding when transaction data entered the system, supporting audit trails, refresh monitoring, and time-based analysis of transaction capture.
Example Value
2023-04-13 15:32:47
Observed Non-Null Count
38,894

FPDS Compare

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

Use Cases

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

Common Usage

  • incremental ETL and refresh filters
  • data latency and audit trail analysis
  • ordering transactions within a reporting window

Common Mistakes

  • using it as the award effective date or obligation date
  • grouping procurement outcomes by creation timestamp without accounting for time zone or load timing

Query Guidance

Store and compare as a timestamp/datetime. In SQL, use it for range filters, ordering, and change detection (for example, WHERE createdDate >= :start_ts AND createdDate < :end_ts), but do not substitute it for procurement action dates in obligation or award analyses.

SQL Examples

Preview values

SELECT
    content__OtherTransactionAward__contractDetail__transactionInformation__createdDate AS created_date
FROM fpds.data
WHERE content__OtherTransactionAward__contractDetail__transactionInformation__createdDate IS NOT NULL
LIMIT 25

Top values

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