FPDS Query Library
About Us
Contact Us

Vendor Name

Human-readable name of the vendor associated with the Other Transaction award record. This is the label shown for the vendor entity in the contract detail section, rather than a numeric identifier or classification code.

Family: Other Transaction Award
Category: Vendor Header
Data Type: string
Semantic Type: label
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__contractDetail__vendor__vendorHeader__vendorName
Title
Vendor Name
FPDS Path
OtherTransactionAward/contractDetail/vendor/vendorHeader/vendorName
Description
Human-readable name of the vendor associated with the Other Transaction award record. This is the label shown for the vendor entity in the contract detail section, rather than a numeric identifier or classification code.
Business Meaning
This field identifies the counterparty receiving the award and is essential for vendor-level analysis, such as supplier concentration, award history, market participation, and organizational reporting. It helps analysts connect the transaction to a specific entity when reviewing award activity across agencies or time periods.
Example Value
UNIVERSITY OF ILLINOIS
Observed Non-Null Count
38,894

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__vendor__vendorHeader__vendorName
FPDS XML Path
OtherTransactionAward/contractDetail/vendor/vendorHeader/vendorName
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/vendor/vendorHeader/vendorName' into the SQL-ready variable 'content__OtherTransactionAward__contractDetail__vendor__vendorHeader__vendorName'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • Contractor profiling and competitor analysis

Common Usage

  • Vendor-level spend and award rollups
  • Matching awards to known suppliers or parent organizations
  • Searching and filtering transaction records by recipient name

Common Mistakes

  • Treating the name string as a unique vendor identifier
  • Assuming different spellings or abbreviations represent different entities

Query Guidance

Select and group by this field for display or descriptive reporting, but join and deduplicate using vendor IDs or other persistent identifiers where possible. In SQL, normalize case and punctuation if performing name-based matching, and avoid using exact string equality as the only vendor matching rule.

SQL Examples

Preview values

SELECT
    content__OtherTransactionAward__contractDetail__vendor__vendorHeader__vendorName AS vendor_name
FROM fpds.data
WHERE content__OtherTransactionAward__contractDetail__vendor__vendorHeader__vendorName IS NOT NULL
LIMIT 25

Top values

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