Results for “budget_level”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FV_BE_XLA_V is a reporting view owned by the APPS schema within the Federal Financials (FV) product family of Oracle E-Business Suite. Its documented purpose is to support reporting of Budget Execution (BE) transactions as they relate to Subledger Accounting (SLA). In Oracle EBS 12.1.1 and 12.2.2, SLA provides the accounting engine and repository where subledger transactions are transformed into journal entries, and Federal Financials extends this framework for government-specific budgetary processing. This view offers a denormalized, read-only projection that joins Budget Execution transaction headers with treasury symbol and budget level reference data, allowing reporting tools, custom concurrent programs, and ad hoc SQL to retrieve BE transaction context without directly navigating the more granular base tables.

The view is defined as a simple three-table join and does not itself own data. It serves as a stable reporting interface over Budget Execution transaction headers, presenting attributes such as document identifiers, fund values, transaction dates, and descriptive reference values. Because it abstracts the join logic, consumers can report consistently on BE transactions across the supported releases without reimplementing the underlying relationships.

Underlying Base Objects

The view is defined over three base objects, each exposed through a synonym in the APPS schema:

• FV_BE_TRX_HDRS — the Budget Execution transaction headers table, which supplies the core transaction rows.
• FV_TREASURY_SYMBOLS — the treasury symbol reference table, providing the Treasury Symbol value.
• FV_BUDGET_LEVELS — the budget level reference table, providing the budget level description.

The joins are governed by three key relationships: the transaction header's TREASURY_SYMBOL_ID is matched to the treasury symbol's TREASURY_SYMBOL_ID; the header's BUDGET_LEVEL_ID is matched to the budget level's BUDGET_LEVEL_ID; and the header's SET_OF_BOOKS_ID is matched to the budget level's SET_OF_BOOKS_ID. The inclusion of the SET_OF_BOOKS_ID predicate ensures that budget level descriptions are resolved within the correct ledger context, which is essential in multi-ledger environments where the same budget level identifier may recur across sets of books.

Key Columns

The view exposes seven columns:

• DOC_ID — the unique identifier of the Budget Execution transaction header.
• DOC_NUMBER — the human-readable document number for the BE transaction.
• FUND_VALUE — the monetary value associated with the fund activity of the transaction.
• TRANSACTION_DATE — the effective date of the Budget Execution transaction, central to period and timing analysis.
• BE_SOURCE — an alias for HDR.SOURCE, identifying the originating source of the BE transaction.
• TREASURY_SYMBOL — the treasury symbol resolved from the treasury symbols reference table.
• BUDGET_LEVEL — the descriptive name of the budget level, resolved from the budget levels table.

Common Use Cases and Queries

Typical uses include reconciling Budget Execution activity against SLA-generated accounting, validating that BE transactions carry valid treasury symbols and budget levels, and producing period-based fund value summaries for federal reporting. The view's descriptive columns make it well suited to listing reports where codes alone would be insufficient.

A basic listing joined to SLA data:

• SELECT DOC_ID, DOC_NUMBER, FUND_VALUE, TRANSACTION_DATE, BE_SOURCE, TREASURY_SYMBOL, BUDGET_LEVEL FROM APPS.FV_BE_XLA_V;
• SELECT TREASURY_SYMBOL, SUM(FUND_VALUE) FROM APPS.FV_BE_XLA_V WHERE TRANSACTION_DATE BETWEEN :p_start AND :p_end GROUP BY TREASURY_SYMBOL;
• SELECT * FROM APPS.FV_BE_XLA_V WHERE DOC_NUMBER = :p_doc_number;

For SLA reconciliation, the view is commonly joined to the SLA journal header tables (XLA_AE_HEADERS and XLA_AE_LINES) on the applicable source identifier so that the BE document context is presented alongside its generated accounting entries. Because the view is a join-only construct, its performance depends largely on indexing of the underlying foreign key columns, particularly TREASURY_SYMBOL_ID, BUDGET_LEVEL_ID, and SET_OF_BOOKS_ID on FV_BE_TRX_HDRS.

Oracle Proprietary, Confidential Information.