FPDS Query Library
About Us
Contact Us

Mod Number

A modification number assigned to the Other Transaction IDV contract action. It identifies the specific amendment or change order within the contract’s transaction history, usually as an alphanumeric sequence such as P00007.

Family: Other Transaction IDV
Category: General
Data Type: identifier_or_code
Semantic Type: identifier
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__modNumber
Title
Mod Number
FPDS Path
OtherTransactionIDV/OtherTransactionIDVID/OtherTransactionIDVContractID/modNumber
Description
A modification number assigned to the Other Transaction IDV contract action. It identifies the specific amendment or change order within the contract’s transaction history, usually as an alphanumeric sequence such as P00007.
Business Meaning
This field lets analysts distinguish one contract modification from another and reconstruct the chronological record of changes to an Other Transaction IDV. It is useful for tracking how an agreement evolved over time, identifying the latest action, and separating base awards from subsequent modifications in spend, scope, or term analysis.
Example Value
P00007
Observed Non-Null Count
13,417

FPDS Compare

FPDS Query Variable
content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__modNumber
FPDS XML Path
OtherTransactionIDV/OtherTransactionIDVID/OtherTransactionIDVContractID/modNumber
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionIDV/OtherTransactionIDVID/OtherTransactionIDVContractID/modNumber' into the SQL-ready variable 'content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__modNumber'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building

Common Usage

  • Ordering contract actions within an award history
  • Identifying the latest modification for a given agreement
  • Separating base actions from follow-on changes in analysis

Common Mistakes

  • Using the modification number as a unique award identifier
  • Assuming numeric order without checking the full coded value format

Query Guidance

Use this field in ORDER BY, DISTINCT, and window functions to sequence contract actions within an award key, but do not rely on it alone for uniqueness. In SQL, pair it with the parent award identifier and action date, and compare the raw text values exactly because leading zeros and prefixes such as P00007 may be meaningful.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__modNumber AS mod_number
FROM fpds.data
WHERE content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__modNumber IS NOT NULL
LIMIT 25

Top values

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