FPDS Query Library
About Us
Contact Us

Vendor Doing as Business Name

Human-readable Doing Business As (DBA) name reported for the vendor in an Other Transaction IDV record. It identifies the operating name used by the vendor and serves as the descriptive label associated with the vendor entity in the FPDS entry.

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__vendorDoingAsBusinessName
Title
Vendor Doing as Business Name
FPDS Path
OtherTransactionIDV/contractDetail/vendor/vendorHeader/vendorDoingAsBusinessName
Description
Human-readable Doing Business As (DBA) name reported for the vendor in an Other Transaction IDV record. It identifies the operating name used by the vendor and serves as the descriptive label associated with the vendor entity in the FPDS entry.
Business Meaning
This field helps analysts recognize the commercial name under which an awardee operates, which is useful when consolidating vendor activity across legal entities, subsidiaries, and branding variations. It supports vendor normalization, market research, and identification of awards that may be tied to a trade name rather than the registered legal name.
Example Value
IMMERVISION
Observed Non-Null Count
5

FPDS Compare

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

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 name normalization and entity matching
  • Display of vendor trade or operating name in reports
  • Cross-checking award records against legal entity names

Common Mistakes

  • Assuming the DBA name uniquely identifies the vendor
  • Using the field alone to aggregate awards across related entities

Query Guidance

Select this field for descriptive reporting or manual review, but join and aggregate on stable vendor identifiers when possible. In SQL, use it as a label column, apply TRIM/UPPER for display standardization if needed, and do not rely on it for de-duplication or exact vendor matching without additional identifier logic.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__contractDetail__vendor__vendorHeader__vendorDoingAsBusinessName AS vendor_doing_as_business_name
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__vendor__vendorHeader__vendorDoingAsBusinessName IS NOT NULL
LIMIT 25

Top values

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