FPDS Query Library
About Us
Contact Us

Funding Requesting Office Id

Code identifying the funding or requesting office associated with the IDV purchaser information. It is an internal organizational identifier, not a narrative office name, and may appear as an abbreviated code such as 47QSMS.

Family: 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__IDV__purchaserInformation__fundingRequestingOfficeID
Title
Funding Requesting Office Id
FPDS Path
IDV/purchaserInformation/fundingRequestingOfficeID
Description
Code identifying the funding or requesting office associated with the IDV purchaser information. It is an internal organizational identifier, not a narrative office name, and may appear as an abbreviated code such as 47QSMS.
Business Meaning
This field helps analysts attribute an IDV to the office responsible for initiating or funding the requirement. It supports organizational spend analysis, office-level workload review, and segmentation of contract actions by funding or requesting entity.
Example Value
47QSMS
Observed Non-Null Count
3,532,633

FPDS Compare

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

Use Cases

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

Common Usage

  • Group IDVs by funding or requesting office
  • Filter awards tied to a specific office code
  • Join to an office reference table or look up code descriptions

Common Mistakes

  • Assuming the value is a full office name
  • Using the code without checking whether blanks or legacy codes are present

Query Guidance

Use the field as a discrete identifier in WHERE, GROUP BY, and JOIN clauses. For analysis, normalize casing and trim whitespace if needed, and join to a validated office lookup to translate the code into a human-readable label.

SQL Examples

Preview values

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

Top values

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