A76 Action
Boolean or coded flag indicating whether an A-76 action was applied to the IDV contract record. Values such as "N" suggest a coded yes/no-style indicator rather than a free-text description.
FPDS Compare
Paired Field
Use Cases
- Dictionary lookup and field explanation
- SQL filtering and grouping
- Analytical reporting and reusable query building
- Competition and sole-source analysis
Common Usage
- Filter IDVs associated with A-76 activity
- Segment competition analyses by special procurement condition
- Support compliance and policy reporting on sourcing decisions
Common Mistakes
- Assuming the field is a narrative description rather than a coded indicator
- Using only one observed value without checking for nulls or alternate code values
Query Guidance
In SQL, filter on the observed code values rather than the label, for example WHERE content__IDV__competition__A76Action = 'Y' or 'N' after confirming the dataset's encoding. Use CASE logic to normalize the field to a boolean or three-state flag when combining it with other competition attributes.
SQL Examples
Preview values
SELECT
content__IDV__competition__A76Action AS a76_action
FROM fpds.data
WHERE content__IDV__competition__A76Action IS NOT NULL
LIMIT 25
Flag distribution
SELECT
content__IDV__competition__A76Action AS flag_value,
count() AS record_count
FROM fpds.data
WHERE content__IDV__competition__A76Action IS NOT NULL
GROUP BY flag_value
ORDER BY record_count DESC
Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.