FPDS Query Library
About Us
Contact Us

Department Id

Code identifying the department of the agency that requested or funded the IDV action. It is a coded reference value, not a narrative name, and typically represents the parent department within the federal reporting hierarchy.

Family: IDV
Category: Purchaser Information
Data Type: identifier_or_code
Semantic Type: identifier
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__purchaserInformation__fundingRequestingAgencyID__departmentID
Title
Department Id
FPDS Path
IDV/purchaserInformation/fundingRequestingAgencyID/departmentID
Description
Code identifying the department of the agency that requested or funded the IDV action. It is a coded reference value, not a narrative name, and typically represents the parent department within the federal reporting hierarchy.
Business Meaning
This field supports aggregation and comparison of obligations, awards, and ordering activity by department-level organization. It is useful for identifying which cabinet department is driving demand, comparing procurement activity across departments, and linking IDV records to broader federal organization structures.
Example Value
6900
Observed Non-Null Count
3,532,659

FPDS Compare

FPDS Query Variable
content__IDV__purchaserInformation__fundingRequestingAgencyID__departmentID
FPDS XML Path
IDV/purchaserInformation/fundingRequestingAgencyID/departmentID
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/purchaserInformation/fundingRequestingAgencyID/departmentID' into the SQL-ready variable 'content__IDV__purchaserInformation__fundingRequestingAgencyID__departmentID'.

Use Cases

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

Common Usage

  • Group IDVs by requesting department
  • Filter records for a specific department code
  • Join to agency or department lookup tables

Common Mistakes

  • Assuming the code is the human-readable department name
  • Using the field as a numeric measure rather than an identifier

Query Guidance

Use equality filters for department-specific analysis and JOIN to a reference table for labels. Example: WHERE departmentID = '6900' or GROUP BY departmentID; if the field is stored as text, preserve leading zeros and compare as a string.

SQL Examples

Preview values

SELECT
    content__IDV__purchaserInformation__fundingRequestingAgencyID__departmentID AS department_id
FROM fpds.data
WHERE content__IDV__purchaserInformation__fundingRequestingAgencyID__departmentID IS NOT NULL
LIMIT 25

Top values

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