FPDS Query Library
About Us
Contact Us

Contracting Office Id Name

Human-readable name of the contracting office associated with the Other Transaction IDV record. This is the label counterpart to the contracting office ID code and identifies the office that issued or managed the instrument.

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__contractingOfficeID__name
Title
Contracting Office Id Name
FPDS Path
OtherTransactionIDV/contractDetail/purchaserInformation/contractingOfficeID/name
Description
Human-readable name of the contracting office associated with the Other Transaction IDV record. This is the label counterpart to the contracting office ID code and identifies the office that issued or managed the instrument.
Business Meaning
This field helps analysts attribute awards to the correct contracting organization for workload, oversight, and organizational trend analysis. It is useful for grouping activity by office name when evaluating buying patterns, portfolio concentration, or office-level performance.
Example Value
W6QK ACC-PICA
Observed Non-Null Count
13,417

FPDS Compare

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

Use Cases

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

Common Usage

  • Group awards by contracting office for reporting
  • Display office labels in dashboards and exports
  • Validate or reconcile office IDs to readable names

Common Mistakes

  • Using the name as a unique key instead of the office ID
  • Assuming abbreviated text always matches a standardized organization name

Query Guidance

Use this field for presentation, filtering, or aggregate labels, but join and deduplicate on the contracting office ID when possible. In SQL, normalize case and trim whitespace if comparing names, and prefer selecting the ID plus name together to preserve both the code and its readable label.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__contractDetail__purchaserInformation__contractingOfficeID__name AS contracting_office_id_name
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__purchaserInformation__contractingOfficeID__name IS NOT NULL
LIMIT 25

Top values

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