Results for “doc_number”

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

Overview

The FV_BE_RPR_XLA_V view is a reporting object within the Oracle E-Business Suite Federal Financials (FV) product family. It resides in the APPS schema and carries a VALID status in both the 12.1.1 and 12.2.2 releases. As its description states, the view is used for reporting Reprogram Budget Execution (BE) transactions in Subledger Accounting (SLA). Its purpose is to present a flattened, human-readable projection of reprogram transaction header data joined to the corresponding budget level, so that federal users can report reprogram actions alongside their Subledger Accounting context without navigating the underlying normalized tables directly.

Because the view is read-only and exposes a fixed column set, it functions purely as a reporting and integration surface. It does not participate in transaction entry or validation; instead it is consumed by reports, extracts, and downstream integrations that require a tidy row per reprogram transaction. The literal RPR_SOURCE value of 'REPROGRAM' hard-coded in the view text makes each returned row self-identifying as a reprogram-sourced record, which simplifies unions with other SLA reporting sources.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed as synonyms in the APPS schema:

• FV_BE_RPR_TRANSACTIONS (SYNONYM) — the reprogram Budget Execution transaction header table. It supplies the transaction identity, document number, fund ranges, GL date, and the budget level foreign key and set of books used for the join.
• FV_BUDGET_LEVELS (SYNONYM) — the budget level definition table. It supplies the descriptive BUDGET_LEVEL value associated with each transaction.

The join is an equi-join on both BUDGET_LEVEL_ID and SET_OF_BOOKS_ID, ensuring the budget level description is resolved within the same ledger context as the transaction. Because both referenced objects are synonyms, the view resolves them to their owning schemas at runtime; the view itself is owned by APPS. No outer joins, aggregations, or filters appear in the view text, so the view returns one row per matching reprogram transaction header/budget level combination.

Key Columns

• TRANSACTION_ID — surrogate identifier of the reprogram Budget Execution transaction, taken from the header table.
• DOC_NUMBER — the document number assigned to the reprogram transaction for traceability and reporting.
• FUND_VALUE_FROM — the source fund value for the reprogram action.
• FUND_VALUE_TO — the destination fund value for the reprogram action.
• TRANSACTION_DATE — aliased from the header GL_DATE; the general ledger date of the transaction, used for period and date-range reporting.
• RPR_SOURCE — a constant literal 'REPROGRAM' identifying the record source, useful when the view is combined with other SLA reporting views.
• BUDGET_LEVEL — the descriptive budget level name resolved from FV_BUDGET_LEVELS, providing business meaning to the transaction.

Common Use Cases and Queries

Typical usage includes period-based reprogram reporting, reconciliation of reprogram activity to SLA, and extraction into federal reporting feeds. A simple listing by ledger and budget level can be produced as follows:

• SELECT transaction_id, doc_number, fund_value_from, fund_value_to, transaction_date, budget_level FROM apps.fv_be_rpr_xla_v ORDER BY transaction_date;
• SELECT * FROM apps.fv_be_rpr_xla_v WHERE transaction_date BETWEEN :p_start AND :p_end; — date-bounded reporting for a given period.
• SELECT budget_level, COUNT(*) qty FROM apps.fv_be_rpr_xla_v GROUP BY budget_level; — distribution of reprogram transactions by budget level.

Because the view contains no set-of-books column in its projection, ledger-context filtering is generally achieved by joining back to FV_BE_RPR_TRANSACTIONS on TRANSACTION_ID when a specific ledger scope is required. All access should respect the APPS-owner conventions and MOAC/security expectations applied to the federal financials reporting layer.