FPDS Query Library
About Us
Contact Us

Funding Requesting Office Id Name

Human-readable name of the office that submitted or requested funding for the award. This is the descriptive label paired with the underlying funding/requesting office identifier in the FPDS record.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__contractDetail__purchaserInformation__fundingRequestingOfficeID__name
Title
Funding Requesting Office Id Name
FPDS Path
OtherTransactionAward/contractDetail/purchaserInformation/fundingRequestingOfficeID/name
Description
Human-readable name of the office that submitted or requested funding for the award. This is the descriptive label paired with the underlying funding/requesting office identifier in the FPDS record.
Business Meaning
It identifies which organizational unit is associated with the funding request, supporting analysis of acquisition responsibility, workload distribution, and funding source patterns across offices. For Other Transaction Awards, it helps trace which office initiated or supported the transaction.
Example Value
W4MK CCDC ARMAMENTS CENTER
Observed Non-Null Count
37,979

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__purchaserInformation__fundingRequestingOfficeID__name
FPDS XML Path
OtherTransactionAward/contractDetail/purchaserInformation/fundingRequestingOfficeID/name
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/purchaserInformation/fundingRequestingOfficeID/name' into the SQL-ready variable 'content__OtherTransactionAward__contractDetail__purchaserInformation__fundingRequestingOfficeID__name'.

Use Cases

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

Common Usage

  • grouping awards by requesting office
  • cross-walking to the underlying office identifier
  • spotting office-level funding and acquisition patterns

Common Mistakes

  • using the name alone as a unique key
  • assuming abbreviations map cleanly across all records

Query Guidance

Use this field for display, filtering, and human-readable reporting, but aggregate on the paired office ID when available. In SQL, standardize text cautiously and avoid exact-match logic without checking observed variants such as abbreviations, punctuation, or casing.

SQL Examples

Preview values

SELECT
    content__OtherTransactionAward__contractDetail__purchaserInformation__fundingRequestingOfficeID__name AS funding_requesting_office_id_name
FROM fpds.data
WHERE content__OtherTransactionAward__contractDetail__purchaserInformation__fundingRequestingOfficeID__name IS NOT NULL
LIMIT 25

Top values

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