FPDS Query Library
About Us
Contact Us

Funding Requesting Office Id

Identifier for the office that requested or funded the order under the Other Transaction IDV record. It is typically a coded office value, such as an agency bureau or component identifier, rather than a free-text name.

Family: Other Transaction 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__OtherTransactionIDV__contractDetail__purchaserInformation__fundingRequestingOfficeID
Title
Funding Requesting Office Id
FPDS Path
OtherTransactionIDV/contractDetail/purchaserInformation/fundingRequestingOfficeID
Description
Identifier for the office that requested or funded the order under the Other Transaction IDV record. It is typically a coded office value, such as an agency bureau or component identifier, rather than a free-text name.
Business Meaning
This field links the procurement action to the responsible funding or requesting office, which is useful for organizational accountability, workload distribution, and spending analysis by office. It helps analysts trace which component initiated or supported the requirement within an Other Transaction vehicle.
Example Value
N66604
Observed Non-Null Count
12,134

FPDS Compare

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

Use Cases

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

Common Usage

  • grouping obligations or awards by requesting office
  • joining to an office reference table for organization names
  • identifying which component sponsored an Other Transaction action

Common Mistakes

  • treating the code as a human-readable office name
  • assuming codes are comparable across agencies without normalization

Query Guidance

Use exact-match filters or joins on this code when analyzing office-level activity. If you need reporting labels, join to a reference table or related descriptive field; avoid substring logic unless you are explicitly handling agency-specific code patterns.

SQL Examples

Preview values

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

Top values

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