Vendor Alternate Name

Human-readable alternate name associated with the vendor recorded on an Other Transaction IDV award. It captures the label used for the vendor when the record stores an alternate or alias name rather than, or in addition to, the primary vendor name.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__vendor__vendorHeader__vendorAlternateName
Title
Vendor Alternate Name
FPDS Path
OtherTransactionIDV/contractDetail/vendor/vendorHeader/vendorAlternateName
Description
Human-readable alternate name associated with the vendor recorded on an Other Transaction IDV award. It captures the label used for the vendor when the record stores an alternate or alias name rather than, or in addition to, the primary vendor name.
Business Meaning
This field helps analysts identify entity aliases, legacy names, trade names, or parent/subsidiary naming variations that can affect vendor-level rollups and deconfliction. It is useful for matching awards to the correct business entity when the same vendor appears under multiple names across FPDS records.
Example Value
PARENTHETIC LLC
Observed Non-Null Count
4,458

FPDS Compare

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

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 normalization and alias matching
  • Entity resolution across award records
  • Reviewing alternate trade or legal names on IDVs

Common Mistakes

  • Using it as a unique vendor key
  • Assuming it always differs from the primary vendor name

Query Guidance

Select and compare this field with vendor identifiers and the primary vendor name when deduplicating or grouping vendors. In SQL, use it for display or alias matching logic, but join and aggregate on stable IDs rather than on the text value alone.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__contractDetail__vendor__vendorHeader__vendorAlternateName AS vendor_alternate_name
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__vendor__vendorHeader__vendorAlternateName IS NOT NULL
LIMIT 25

Top values

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