Phone No

Telephone number recorded for the vendor's physical location associated with the IDV vendor site. It is a contact attribute for the site, not a measure of award value, performance, or geography.

Family: IDV
Category: Vendor Site Details
Data Type: string
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__vendor__vendorSiteDetails__vendorLocation__phoneNo
Title
Phone No
FPDS Path
IDV/vendor/vendorSiteDetails/vendorLocation/phoneNo
Description
Telephone number recorded for the vendor's physical location associated with the IDV vendor site. It is a contact attribute for the site, not a measure of award value, performance, or geography.
Business Meaning
This field helps analysts identify and contact the specific vendor location tied to an IDV record, support vendor matching and deduplication, and distinguish among multiple sites for the same legal entity. It can also aid data quality checks when reconciling vendor records across FPDS extracts and related procurement datasets.
Example Value
7032793644
Observed Non-Null Count
3,338,431

FPDS Compare

FPDS Query Variable
content__IDV__vendor__vendorSiteDetails__vendorLocation__phoneNo
FPDS XML Path
IDV/vendor/vendorSiteDetails/vendorLocation/phoneNo
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/vendor/vendorSiteDetails/vendorLocation/phoneNo' into the SQL-ready variable 'content__IDV__vendor__vendorSiteDetails__vendorLocation__phoneNo'.

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 contact lookup
  • site-level vendor matching
  • data quality and duplicate review

Common Mistakes

  • assuming the number uniquely identifies the vendor or award
  • joining on raw phone text without normalizing formatting

Query Guidance

Select this field for contact reporting or record review, and normalize it before comparison, for example by stripping non-numeric characters. In SQL, use it as a filter only after cleaning and do not use it as a primary join key unless combined with stronger site identifiers.

SQL Examples

Preview values

SELECT
    content__IDV__vendor__vendorSiteDetails__vendorLocation__phoneNo AS phone_no
FROM fpds.data
WHERE content__IDV__vendor__vendorSiteDetails__vendorLocation__phoneNo IS NOT NULL
LIMIT 25

Top values

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