FPDS Query Library
About Us
Contact Us

Funding Requesting Office Id Name

Human-readable name associated with the funding/requesting office identifier in the Other Transaction IDV purchaser information. It is the label version of a coded office ID, used to identify the office that requested or funds the action.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__purchaserInformation__fundingRequestingOfficeID__name
Title
Funding Requesting Office Id Name
FPDS Path
OtherTransactionIDV/contractDetail/purchaserInformation/fundingRequestingOfficeID/name
Description
Human-readable name associated with the funding/requesting office identifier in the Other Transaction IDV purchaser information. It is the label version of a coded office ID, used to identify the office that requested or funds the action.
Business Meaning
This field helps analysts attribute obligations and awards to the office driving the requirement, enabling oversight by organization, bureau, or program owner. It is useful for tracing buying activity back to the responsible office when analyzing spend patterns, portfolio ownership, or inter-office procurement support.
Example Value
DEF ADVANCED RESEARCH PROJECTS AGCY
Observed Non-Null Count
12,133

FPDS Compare

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

Use Cases

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

Common Usage

  • Grouping transactions by requesting office name
  • Supporting drill-down from office ID to readable office label
  • Validating bureau- or program-level procurement reporting

Common Mistakes

  • Using the name as a join key instead of the underlying office ID
  • Assuming the text is standardized across all records or time periods

Query Guidance

Use this field for display, grouping, and filtering only when exact label matching is acceptable. For reliable joins and de-duplication, prefer the corresponding funding/requesting office ID and select this field for presentation in the result set.

SQL Examples

Preview values

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

Top values

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