FPDS Query Library
About Us
Contact Us

Approved By

Identifier for the person or user account that approved the transaction in the Other Transaction IDV record. It captures the approver recorded in FPDS rather than the approval decision itself.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__transactionInformation__approvedBy
Title
Approved By
FPDS Path
OtherTransactionIDV/contractDetail/transactionInformation/approvedBy
Description
Identifier for the person or user account that approved the transaction in the Other Transaction IDV record. It captures the approver recorded in FPDS rather than the approval decision itself.
Business Meaning
This field supports accountability, review of approval chains, and assessment of who is authorizing procurement actions. Analysts use it to trace approval patterns, validate workflow controls, and group transactions by approving official or account.
Example Value
SANDI.CRAWFORD.OT@SA1700.NAVAIR
Observed Non-Null Count
13,417

FPDS Compare

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

Use Cases

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

Common Usage

  • grouping transactions by approving user or account
  • audit checks on approval authority and workflow compliance
  • filtering records for a specific approver in trend analysis

Common Mistakes

  • assuming the value is always a person name instead of a system user ID
  • joining on this field as if it were a stable cross-system person key

Query Guidance

Use exact-match or normalized string comparisons for filtering and grouping, and apply lowercasing or trimming when matching free-text user IDs. If analyzing approver behavior at scale, aggregate distinct values after standardizing case and format, and validate against sample records before building joins.

SQL Examples

Preview values

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

Top values

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