FPDS Query Library
About Us
Contact Us

Department Id

Code identifying the department of the funding or requesting agency associated with the award. It is a reference identifier, not a narrative name, and typically represents the top-level federal department tied to the funding source. Example values are numeric codes such as 8000.

Family: Award
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__award__purchaserInformation__fundingRequestingAgencyID__departmentID
Title
Department Id
FPDS Path
award/purchaserInformation/fundingRequestingAgencyID/departmentID
Description
Code identifying the department of the funding or requesting agency associated with the award. It is a reference identifier, not a narrative name, and typically represents the top-level federal department tied to the funding source. Example values are numeric codes such as 8000.
Business Meaning
This field helps analysts attribute an award to the federal department that supplied or requested the funds, which is important for budget tracking, interagency reporting, and spend analysis by department. It supports rollups of obligation and award activity across programs that may be executed by one agency but funded by another.
Example Value
8000
Observed Non-Null Count
102,422,036

FPDS Compare

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

Use Cases

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

Common Usage

  • Department-level spend rollups
  • Cross-agency funding source analysis
  • Filtering awards by funding or requesting department

Common Mistakes

  • Assuming the code is the same as the awarding agency
  • Treating the numeric value as a human-readable department name

Query Guidance

Use exact equality or IN filters on the code value, and join to a department reference table or decoded lookup if you need the department name. If analyzing trends over time, standardize codes to a consistent reference set and check for nulls, legacy codes, or records where the funding department differs from the procuring agency.

SQL Examples

Preview values

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

Top values

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