Department Name

Human-readable name of the funding/requesting agency department associated with the purchaser information on the Other Transaction IDV record. This is the descriptive label for the agency department, not the coded identifier itself.

Family: Other Transaction IDV
Category: Purchaser Information
Data Type: string
Semantic Type: label
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__purchaserInformation__fundingRequestingAgencyID__departmentName
Title
Department Name
FPDS Path
OtherTransactionIDV/contractDetail/purchaserInformation/fundingRequestingAgencyID/departmentName
Description
Human-readable name of the funding/requesting agency department associated with the purchaser information on the Other Transaction IDV record. This is the descriptive label for the agency department, not the coded identifier itself.
Business Meaning
This field identifies which federal department is acting as the funding or requesting entity, which is important for spend attribution, organizational reporting, interagency analysis, and understanding who originates demand for an Other Transaction IDV.
Example Value
DEPT OF DEFENSE
Observed Non-Null Count
12,136

FPDS Compare

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

Use Cases

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

Common Usage

  • Group Other Transaction IDVs by funding/requesting department
  • Validate the agency name associated with the coded purchaser/funding field
  • Create readable labels in procurement dashboards and reports

Common Mistakes

  • Using the label as a join key instead of the underlying code
  • Assuming every textual variant represents a distinct agency

Query Guidance

Use this field in SELECT and GROUP BY clauses for human-readable reporting, but join or filter on the paired department code when available to avoid issues from text variation, punctuation, or abbreviations.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__contractDetail__purchaserInformation__fundingRequestingAgencyID__departmentName AS department_name
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__purchaserInformation__fundingRequestingAgencyID__departmentName IS NOT NULL
LIMIT 25

Top values

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