FPDS Query Library
About Us
Contact Us

Vendor Legal Organization Name

Human-readable legal name of the vendor organization recorded in the IDV vendor header. It identifies the contractor entity associated with the award and serves as the textual label for the vendor record.

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

Variable Overview

FPDS Query Variable
content__IDV__vendor__vendorHeader__vendorLegalOrganizationName
Title
Vendor Legal Organization Name
FPDS Path
IDV/vendor/vendorHeader/vendorLegalOrganizationName
Description
Human-readable legal name of the vendor organization recorded in the IDV vendor header. It identifies the contractor entity associated with the award and serves as the textual label for the vendor record.
Business Meaning
This field supports vendor-level analysis by making it possible to identify award recipients, group obligations by contractor name, and review concentration, competition, and repeat-award patterns. It is useful for linking FPDS records to external vendor intelligence, especially when analyzing parent/subsidiary structures or comparing awards across time.
Example Value
TO RICOS INCORPORATED
Observed Non-Null Count
1,293,685

FPDS Compare

FPDS Query Variable
content__IDV__vendor__vendorHeader__vendorLegalOrganizationName
FPDS XML Path
IDV/vendor/vendorHeader/vendorLegalOrganizationName
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/vendor/vendorHeader/vendorLegalOrganizationName' into the SQL-ready variable 'content__IDV__vendor__vendorHeader__vendorLegalOrganizationName'.

Use Cases

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

Common Usage

  • Grouping obligations or counts by vendor name
  • Displaying the awarded contractor in reports and dashboards
  • Reconciling FPDS records with external vendor reference data

Common Mistakes

  • Using the name field as a unique key for joins or deduplication
  • Assuming different spellings or legal suffixes represent different entities

Query Guidance

Use in SELECT and GROUP BY for reporting, but join and deduplicate on stable vendor identifiers when available. Normalize case and whitespace, and consider alias mapping or fuzzy matching if you need entity-level rollups across name variants.

SQL Examples

Preview values

SELECT
    content__IDV__vendor__vendorHeader__vendorLegalOrganizationName AS vendor_legal_organization_name
FROM fpds.data
WHERE content__IDV__vendor__vendorHeader__vendorLegalOrganizationName IS NOT NULL
LIMIT 25

Top values

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