Vendor Doing as Business Name

Text field that stores the vendor’s doing-business-as (DBA) name, i.e., the name under which the vendor is operating in the award record. It is a human-readable vendor label, not a code, and may differ from the legal entity name.

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__vendorDoingAsBusinessName
Title
Vendor Doing as Business Name
FPDS Path
OtherTransactionAward/contractDetail/vendor/vendorHeader/vendorDoingAsBusinessName
Description
Text field that stores the vendor’s doing-business-as (DBA) name, i.e., the name under which the vendor is operating in the award record. It is a human-readable vendor label, not a code, and may differ from the legal entity name.
Business Meaning
This field helps analysts identify the organization actually presenting itself in the transaction, especially when the legal name and operating name differ. It supports vendor normalization, spend attribution, and cross-walking awards to public-facing business names in procurement reviews.
Example Value
OFFICE OF RESEARCH
Observed Non-Null Count
12

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__vendor__vendorHeader__vendorDoingAsBusinessName
FPDS XML Path
OtherTransactionAward/contractDetail/vendor/vendorHeader/vendorDoingAsBusinessName
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/vendor/vendorHeader/vendorDoingAsBusinessName' into the SQL-ready variable 'content__OtherTransactionAward__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

  • Display vendor DBA name in award extracts and reports
  • Match awards to a vendor’s public operating name
  • Normalize vendor names across records for spend analysis

Common Mistakes

  • Treating the DBA name as the vendor’s legal entity name
  • Using it alone as a unique key for vendor deduplication

Query Guidance

Select it as a descriptive attribute and use it with vendor identifiers for joins or grouping. In SQL, trim and standardize case for matching, and prefer grouping by stable identifiers while using this field for presentation or secondary reconciliation.

SQL Examples

Preview values

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

Top values

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