FPDS Query Library
About Us
Contact Us

Approved By

Identifier for the person or entity that approved the Other Transaction Award record in FPDS. The value is typically an approver email address or username-style string rather than a narrative approval note.

Family: Other Transaction Award
Category: General
Data Type: string
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__contractDetail__transactionInformation__approvedBy
Title
Approved By
FPDS Path
OtherTransactionAward/contractDetail/transactionInformation/approvedBy
Description
Identifier for the person or entity that approved the Other Transaction Award record in FPDS. The value is typically an approver email address or username-style string rather than a narrative approval note.
Business Meaning
This field helps trace approval accountability and identify which official or office validated the transaction. It is useful for audit support, workflow analysis, and understanding approval patterns across awards, organizations, or time periods.
Example Value
STASIA.BAKER.M67854@USMC.MIL
Observed Non-Null Count
38,894

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__transactionInformation__approvedBy
FPDS XML Path
OtherTransactionAward/contractDetail/transactionInformation/approvedBy
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/transactionInformation/approvedBy' into the SQL-ready variable 'content__OtherTransactionAward__contractDetail__transactionInformation__approvedBy'.

Use Cases

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

Common Usage

  • trace approval responsibility for a record
  • group awards by approver or approving office
  • support audit and workflow analyses

Common Mistakes

  • assuming the value is a free-text approval comment
  • using raw values without cleaning case differences or aliases

Query Guidance

Use exact matches for point lookups and GROUP BY for approval pattern analysis. If analyzing approver identity, normalize case and consider parsing the username or domain portion only when the reporting question requires it.

SQL Examples

Preview values

SELECT
    content__OtherTransactionAward__contractDetail__transactionInformation__approvedBy AS approved_by
FROM fpds.data
WHERE content__OtherTransactionAward__contractDetail__transactionInformation__approvedBy IS NOT NULL
LIMIT 25

Top values

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