FPDS Query Library
About Us
Contact Us

Contracting Office Id

Identifier for the contracting office responsible for the transaction in the FPDS record. It is a coded value, not a free-text name, and may use agency-specific abbreviations or routing codes.

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__contractingOfficeID
Title
Contracting Office Id
FPDS Path
OtherTransactionIDV/contractDetail/purchaserInformation/contractingOfficeID
Description
Identifier for the contracting office responsible for the transaction in the FPDS record. It is a coded value, not a free-text name, and may use agency-specific abbreviations or routing codes.
Business Meaning
This field lets analysts attribute awards and other transactions to the buying office that executed or managed them. It is essential for office-level workload analysis, obligation rollups, accountability reviews, and comparing procurement activity across organizational units.
Example Value
W50RAJ
Observed Non-Null Count
13,417

FPDS Compare

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

Use Cases

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

Common Usage

  • Group obligations or counts by contracting office
  • Filter awards for a specific office or command
  • Compare procurement volume across offices

Common Mistakes

  • Assuming the code is a human-readable office name
  • Using the field without validating office-code mappings over time

Query Guidance

Use this field in WHERE clauses for office-specific pulls and in GROUP BY for office-level analytics. When presenting results, join to an office lookup table or reference mapping to display the office name alongside the code.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__contractDetail__purchaserInformation__contractingOfficeID AS contracting_office_id
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__purchaserInformation__contractingOfficeID IS NOT NULL
LIMIT 25

Top values

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