FPDS Query Library
About Us
Contact Us

Contracting Office Id

Identifier for the contracting office associated with the Other Transaction Award purchaser information. It is a coded office key, not a free-text name, and identifies the specific contracting office that issued or managed the transaction.

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__contractingOfficeID
Title
Contracting Office Id
FPDS Path
OtherTransactionAward/contractDetail/purchaserInformation/contractingOfficeID
Description
Identifier for the contracting office associated with the Other Transaction Award purchaser information. It is a coded office key, not a free-text name, and identifies the specific contracting office that issued or managed the transaction.
Business Meaning
This field is important for attributing awards to the correct contracting office, supporting workload analysis, organizational reporting, and office-level spend or obligation reviews. It also helps analysts compare activity across bureaus, regions, or offices when names may vary or be duplicated.
Example Value
N00164
Observed Non-Null Count
38,894

FPDS Compare

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

Use Cases

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

Common Usage

  • Group awards by contracting office
  • Filter transactions for a specific office code
  • Join to office lookup tables for descriptive reporting

Common Mistakes

  • Assuming the field contains the office name instead of a code
  • Aggregating across offices without normalizing codes or handling missing values

Query Guidance

Use this field in WHERE, GROUP BY, and JOIN clauses as an office key. If you need a readable label, join to a contracting office reference table; when comparing across periods, verify the code remains consistent and account for null or placeholder values.

SQL Examples

Preview values

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

Top values

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