Department Id

Code identifying the department-level agency for the contracting office associated with the Other Transaction IDV. It is an organizational identifier, not a narrative description, 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__contractingOfficeAgencyID__departmentID
Title
Department Id
FPDS Path
OtherTransactionIDV/contractDetail/purchaserInformation/contractingOfficeAgencyID/departmentID
Description
Code identifying the department-level agency for the contracting office associated with the Other Transaction IDV. It is an organizational identifier, not a narrative description, and typically appears as a numeric or abbreviated code such as 9700.
Business Meaning
This field supports agency-level attribution of contracting activity, allowing analysts to group obligations, awards, and vendor relationships by department. It is useful for routing accountability, comparing activity across departments, and linking procurement records to organizational structures or agency reporting hierarchies.
Example Value
9700
Observed Non-Null Count
13,417

FPDS Compare

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

Use Cases

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

Common Usage

  • Group awards by department-level contracting office
  • Join to agency reference tables or hierarchy maps
  • Filter transactions for a specific department code

Common Mistakes

  • Assuming the code is a department name or description
  • Casting the value to numeric when leading zeros may be meaningful

Query Guidance

Use this field as a join and filter key in WHERE, GROUP BY, and JOIN clauses. If you need human-readable output, pair it with a department name or agency description field; do not aggregate by the code unless you intend to analyze at the department-code level.

SQL Examples

Preview values

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

Top values

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