Search Results fv_be_trx_hdrs




Overview
Explore in AI Chat

Overview

FV_BE_TRX_HDRS is the base header table for budget execution transactions within the Oracle E-Business Suite Federal Financials (FV) product. It stores document-level information for all budget execution transactions processed by an agency, and serves as the primary data block underlying the Define Appropriations and Define Fund Distributions forms in Oracle EBS 12.1.1 and 12.2.2. Every budget execution document — whether an appropriation, apportionment, allotment, or fund distribution — begins with a header row in this table, which is subsequently referenced by detail and distribution lines that carry the actual accounting activity.

The table resides in the FV schema and is documented in ETRM 12.2.2 with 70 columns. Its primary key, FV_BE_TRX_HDRS_PK1, is defined on the DOC_ID column. From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: the table is keyed by a surrogate identifier and carries a broad set of descriptive and operational attributes that describe the state of a parent document, rather than acting as a pure hub or a link between two or more business keys. This classification is a heuristic observation on the documented structure and should be treated as a modeling suggestion rather than a prescription.

Key Information Stored

The most significant columns in FV_BE_TRX_HDRS are those that identify the document, describe its accounting context, and track its lifecycle:

  • DOC_ID — the surrogate primary key, generated to uniquely identify each budget execution document header.
  • DOC_NUMBER — the user-visible document number; combined with BUDGET_LEVEL_ID, SET_OF_BOOKS_ID, and SOURCE, it forms the business-key candidate FV_BE_TRX_HDRS_U1.
  • BUDGET_LEVEL_ID — identifies the budget level assigned to the document, which governs the appropriations structure in use.
  • SET_OF_BOOKS_ID — the ledger context in which the transaction is recorded.
  • SOURCE — indicates the originating source of the document, distinguishing manual entry from imported or generated transactions.
  • DOC_STATUS — the current workflow state of the document (for example, entered, approved, or rejected).
  • TRANSACTION_DATE — the effective date of the budget execution transaction.
  • DOC_TOTAL and DISTRIBUTION_AMOUNT — the monetary magnitude of the document and its distributions, respectively.
  • FUND_VALUE and TREASURY_SYMBOL_ID — funding attributes tied to the document, including the Treasury symbol reference.
  • REVISION_NUM and INTERNAL_REVISION_NUM — revision tracking for the document, supporting amendment history.
  • SEGMENT1 through SEGMENT30 and BUDGETING_SEGMENTS — the accounting flexfield segment values that determine the posting combination for the document.
  • BU_GROUP_ID — foreign key to FV_BUDGET_USER_HDR, linking the document to the budget user group that owns it.
  • APPROVAL_ID — foreign key to JTF_UM_APPROVALS_B, tying the document to the Oracle Approvals Management record.
  • PARENT_DOC_ID — self-referencing link used to relate revisions or subordinate documents to their parent.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS flexfield extension columns available for agency-specific customization.

The unique index FV_BE_TRX_HDRS_U2, defined solely on DOC_ID, reinforces the surrogate key, while U1 captures the natural business identity of a document.

Common Use Cases and Queries

Typical usage of FV_BE_TRX_HDRS centers on reporting document status, reconciling budget execution activity, and auditing the workflow history of appropriations and fund distributions.

  • Document status reporting: listing all documents by status and ledger for a given period. 
    SELECT doc_number, transaction_date, doc_status, doc_total
FROM   fv.fv_be_trx_hdrs
WHERE  set_of_books_id = :ledger_id
AND    doc_status = :status;
  • Document lookup by business key: retrieving a header using the natural key columns of FV_BE_TRX_HDRS_U1. 
    SELECT doc_id, doc_total, doc_status
FROM   fv.fv_be_trx_hdrs
WHERE  budget_level_id = :lvl
AND    doc_number = :docnum
AND    set_of_books_id = :sob
AND    source = :source;
  • Revision tracing: following the PARENT_DOC_ID chain to reconstruct amendment history for a document.
  • Approval tracking: joining APPROVAL_ID to JTF_UM_APPROVALS_B to report on approvals outstanding or completed.
  • Group ownership analysis: joining BU_GROUP_ID to FV_BUDGET_USER_HDR to report activity by budget user group.

Related Objects

FV_BE_TRX_HDRS participates in a small but important set of relationships, both as a child and as a parent:

  • FV_BUDGET_USER_HDR — referenced by FV_BE_TRX_HDRS.BU_GROUP_ID; identifies the budget user group associated with each document.
  • JTF_UM_APPROVALS_B — referenced by FV_BE_TRX_HDRS.APPROVAL_ID; supplies approval metadata for the Oracle Approvals Management integration.
  • FV_BE_TRX_HDRS (self-reference) — PARENT_DOC_ID links a header to its parent document, supporting revisions and subordinate documents.
  • Detail and distribution tables in the FV budget execution model that reference FV_BE_TRX_HDRS by DOC_ID, carrying line-level accounting and fund distribution information.
  • The Define Appropriations and Define Fund Distributions forms, which read and write this table as their base header block.
  • Standard FV reporting and inquiry views built over the FV schema that surface budget execution document data to end users.

Because the header row governs the downstream detail and distribution records, updates to DOC_STATUS, approval state, or the accounting segment columns in FV_BE_TRX_HDRS should be treated as consequential and coordinated with the related detail tables.