FPDS Query Library
About Us
Contact Us

Funding Requesting Office Id

Identifier for the office that is requesting or originating the funding associated with the award. It is a coded value, not a narrative office name, and may reflect an internal agency office key or abbreviated organizational code.

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__fundingRequestingOfficeID
Title
Funding Requesting Office Id
FPDS Path
award/purchaserInformation/fundingRequestingOfficeID
Description
Identifier for the office that is requesting or originating the funding associated with the award. It is a coded value, not a narrative office name, and may reflect an internal agency office key or abbreviated organizational code.
Business Meaning
This field helps analysts trace which funding or requesting office supported the procurement, enabling spend attribution, organizational accountability, and analysis of buying patterns by office. It is useful for identifying decentralized purchasing activity, funding responsibility, and cross-office award relationships.
Example Value
C8711
Observed Non-Null Count
89,433,447

FPDS Compare

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

Use Cases

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

Common Usage

  • Group awards by requesting office
  • Join to an office reference table for human-readable names
  • Filter awards tied to a specific funding organization

Common Mistakes

  • Assuming the value is a full office name rather than a code
  • Using the field for reporting without normalizing or validating against reference data

Query Guidance

Use this field in WHERE, GROUP BY, and JOIN clauses as a coded organizational key. In SQL, compare against exact code values or join to a lookup table; do not rely on partial text matching unless you have confirmed the code format.

SQL Examples

Preview values

SELECT
    content__award__purchaserInformation__fundingRequestingOfficeID AS funding_requesting_office_id
FROM fpds.data
WHERE content__award__purchaserInformation__fundingRequestingOfficeID IS NOT NULL
LIMIT 25

Top values

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