Search Results fv_xla_po_ref_v




Overview
Explore in AI Chat

Overview

FV_XLA_PO_REF_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the FV – Federal Financials product. Its purpose is to expose the purchase order and prior-year adjustment reference attributes required by the Subledger Accounting (XLA) and federal funds control processes. The view projects selected columns from the global temporary table FV_EXTRACT_DETAIL_GT, filtered to a single application context, and renames each column with a FEDERAL_ prefix so that the Subledger Accounting extraction logic can consume a stable, semantically explicit interface.

The name itself reflects this role: the XLA segment indicates the subledger accounting integration point, PO indicates the purchasing-related extraction that seeds the data, and REF indicates a reference or lookup view. In effect, FV_XLA_PO_REF_V presents an accounting-ready projection of federal extract detail — fund value, fund category, prior-year amounts, and Treasury Coefficient (TCF) adjustments — without requiring downstream code to reference the temporary table directly.

Underlying Base Objects

ETRM documentation identifies exactly one referenced base object: FV_EXTRACT_DETAIL_GT (TABLE), a global temporary table. This view is therefore a thin, single-table projection rather than a join or aggregate. The crucial behaviour lies in the WHERE clause, which restricts rows to APPLICATION_ID = 201. Application ID 201 corresponds to the Federal Financials application within the EBS application registry, so the view exposes only the FV-owned extract rows that have been populated into the shared temporary table by the federal extraction program.

Because FV_EXTRACT_DETAIL_GT is a global temporary table, the data visible through this view is session-scoped and transient. Rows persist only for the duration of the session or transaction that populated them, typically during the execution of the subledger accounting extract or funds availability process. Consumers must therefore call the view within the context of the same concurrent request or session that performed the extraction; querying it at an arbitrary time from another session will generally return no rows.

Key Columns

Common Use Cases and Queries

The principal use case is diagnostic: confirming that the federal extraction populated correctly before subledger accounting creates the final journal entries, and tracing a specific XLA event back to its fund, prior-year, and anticipation attributes. For example, to inspect the federal attributes of a particular event:

  • SELECT federal_event_id, federal_line_number, federal_fund_value, federal_fund_category, federal_pya_amt, federal_tcf_amt FROM fv_xla_po_ref_v WHERE federal_event_id = :event_id;
  • SELECT federal_fund_category, federal_prior_year_flag, SUM(federal_pya_amt), SUM(federal_tcf_amt) FROM fv_xla_po_ref_v GROUP BY federal_fund_category, federal_prior_year_flag;
  • SELECT COUNT(*) FROM fv_xla_po_ref_v WHERE federal_fund_expired_status = 'Y' AND federal_pya_amt <> 0;

These queries return data only when executed in a session where the federal extract has already been run, reflecting the temporary-table origin of the underlying rows.