FPDS Query Library
About Us
Contact Us

Funding Requesting Office Id Name

Human-readable name of the office that is requesting or funding the procurement action within the IDV purchaser information section. It is the label associated with the underlying funding requesting office identifier, not the identifier itself.

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

Variable Overview

FPDS Query Variable
content__IDV__purchaserInformation__fundingRequestingOfficeID__name
Title
Funding Requesting Office Id Name
FPDS Path
IDV/purchaserInformation/fundingRequestingOfficeID/name
Description
Human-readable name of the office that is requesting or funding the procurement action within the IDV purchaser information section. It is the label associated with the underlying funding requesting office identifier, not the identifier itself.
Business Meaning
This field helps analysts attribute procurement activity to the specific office responsible for initiating or funding the requirement. It is useful for organizational reporting, spend attribution, workload analysis, and comparing activity across operating units or field offices.
Example Value
OREGON STATE OFFICE
Observed Non-Null Count
3,526,896

FPDS Compare

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

Use Cases

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

Common Usage

  • Display the funding requesting office name in reports and dashboards
  • Group procurement actions by requesting office for organizational analysis
  • Validate office-level coding against observed labels in the data

Common Mistakes

  • Using the name as a stable key instead of the office ID
  • Assuming the label is unique when multiple records may share similar or changing office names

Query Guidance

Use this field primarily in SELECT clauses for labeling and in joins only with caution; prefer the associated office ID for grouping, filtering, and deduplication. If you need office-level rollups, aggregate by the coded office field and include this name as a display attribute, using DISTINCT or MAX only when the label is consistently one-to-one with the ID.

SQL Examples

Preview values

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

Top values

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