FPDS Query Library
About Us
Contact Us

Cost or Pricing Data

Boolean or coded flag indicating whether cost or pricing data was used for the IDV record. It reflects the presence of a yes/no determination in the contract data section rather than a monetary amount or narrative explanation.

Family: IDV
Category: Contract Data
Data Type: boolean_or_code_flag
Semantic Type: flag
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__contractData__costOrPricingData
Title
Cost or Pricing Data
FPDS Path
IDV/contractData/costOrPricingData
Description
Boolean or coded flag indicating whether cost or pricing data was used for the IDV record. It reflects the presence of a yes/no determination in the contract data section rather than a monetary amount or narrative explanation.
Business Meaning
This field is useful for assessing pricing basis and compliance patterns in negotiated procurements, especially where Truthful Cost or Pricing Data requirements may apply. Analysts use it to segment awards by whether cost or pricing data was obtained, which can support oversight, audit review, and market pricing analysis.
Example Value
N
Observed Non-Null Count
1,977,095

FPDS Compare

FPDS Query Variable
content__IDV__contractData__costOrPricingData
FPDS XML Path
IDV/contractData/costOrPricingData
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/contractData/costOrPricingData' into the SQL-ready variable 'content__IDV__contractData__costOrPricingData'.

Use Cases

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

Common Usage

  • Identify awards where cost or pricing data was used
  • Segment procurements for compliance or audit review
  • Compare pricing basis across acquisition categories

Common Mistakes

  • Reading the flag as evidence that certified cost or pricing data was required
  • Treating non-affirmative values and missing values as equivalent without checking the extract

Query Guidance

Use equality filters against the affirmative code in the local extract, for example WHERE content__IDV__contractData__costOrPricingData = 'Y' or the equivalent coded value. If the column is stored as mixed text, normalize values first and validate against the dataset's observed code set before aggregating.

SQL Examples

Preview values

SELECT
    content__IDV__contractData__costOrPricingData AS cost_or_pricing_data
FROM fpds.data
WHERE content__IDV__contractData__costOrPricingData IS NOT NULL
LIMIT 25

Flag distribution

SELECT
    content__IDV__contractData__costOrPricingData AS flag_value,
    count() AS record_count
FROM fpds.data
WHERE content__IDV__contractData__costOrPricingData IS NOT NULL
GROUP BY flag_value
ORDER BY record_count DESC

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