FPDS Query Library
About Us
Contact Us

Funding Requesting Office Id

Identifier for the office that requested or funded the transaction within the purchaser information section of an Other Transaction Award record. It is a coded value, not a human-readable office name, and may represent an internal agency key, shorthand, or abbreviated reference.

Family: Other Transaction 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__OtherTransactionAward__contractDetail__purchaserInformation__fundingRequestingOfficeID
Title
Funding Requesting Office Id
FPDS Path
OtherTransactionAward/contractDetail/purchaserInformation/fundingRequestingOfficeID
Description
Identifier for the office that requested or funded the transaction within the purchaser information section of an Other Transaction Award record. It is a coded value, not a human-readable office name, and may represent an internal agency key, shorthand, or abbreviated reference.
Business Meaning
This field helps analysts attribute demand and funding responsibility to the originating office behind an Other Transaction Award. It supports organizational analysis, workload attribution, funding-source tracing, and identification of which offices are driving awards or modifications across agencies.
Example Value
F4FBGK
Observed Non-Null Count
38,062

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__purchaserInformation__fundingRequestingOfficeID
FPDS XML Path
OtherTransactionAward/contractDetail/purchaserInformation/fundingRequestingOfficeID
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/purchaserInformation/fundingRequestingOfficeID' into the SQL-ready variable 'content__OtherTransactionAward__contractDetail__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
  • Link transactions to internal funding or program offices
  • Filter records by office-specific responsibility

Common Mistakes

  • Interpreting the code as the full office name
  • Comparing values across agencies without normalizing or crosswalking the code set

Query Guidance

Use this field as a grouping, filtering, or join key rather than a display label. In SQL, pair it with a descriptive office field when available, and consider COUNT(DISTINCT ...) or GROUP BY to analyze office-level activity; if values vary by agency, build a mapping table before aggregating.

SQL Examples

Preview values

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

Top values

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