FPDS Query Library
About Us
Contact Us

Department Id

Code identifying the department of the funding or requesting agency associated with the purchaser information on an Other Transaction IDV record. It is an internal reference value, not a free-text agency name, and typically appears as a numeric or abbreviated code such as 9700.

Family: Other Transaction 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__OtherTransactionIDV__contractDetail__purchaserInformation__fundingRequestingAgencyID__departmentID
Title
Department Id
FPDS Path
OtherTransactionIDV/contractDetail/purchaserInformation/fundingRequestingAgencyID/departmentID
Description
Code identifying the department of the funding or requesting agency associated with the purchaser information on an Other Transaction IDV record. It is an internal reference value, not a free-text agency name, and typically appears as a numeric or abbreviated code such as 9700.
Business Meaning
This field helps analysts attribute funding or requesting responsibility to the correct federal department when evaluating Other Transaction IDVs. It supports agency-level rollups, cross-agency comparisons, and identification of which department is tied to the demand signal behind the transaction.
Example Value
9700
Observed Non-Null Count
12,136

FPDS Compare

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

Use Cases

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

Common Usage

  • Agency-level aggregation of Other Transaction IDV activity
  • Join key to reference tables for department names
  • Filtering records by funding/requesting department

Common Mistakes

  • Interpreting the code as a department name rather than an identifier
  • Grouping on the code without checking for missing, reused, or dataset-specific values

Query Guidance

Use this field as a join and filter key, typically with DISTINCT, GROUP BY, or WHERE clauses. If a description field or reference table exists, join to it for readable output; if not, retain the code and confirm its meaning against observed values and FPDS reference data.

SQL Examples

Preview values

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

Top values

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