Results for “fv_xla_ap_ref_v”
32 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FV_XLA_AP_REF_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Federal Financials (FV) product. Its purpose is to expose, in a Federal-oriented naming convention, the Accounts Payable subledger accounting extract data that has been staged in the FV_EXTRACT_DETAIL_GT global temporary table. The view filters that staging table to APPLICATION_ID = 200, which is the Oracle Subledger Accounting application identifier corresponding to Payables (AP). In practice, FV_XLA_AP_REF_V acts as the AP-specific access point for Federal fund, obligation, and payment attributes that are consumed by Federal Financials reporting and by downstream extracts that feed Treasury, GTAS, or USSGL-oriented processes. Because it is a view rather than a stored table, it presents no persisted data of its own; every query reflects the current contents of the underlying staging table for the active session.
Underlying Base Objects
The view is defined over a single documented base object, the table FV_EXTRACT_DETAIL_GT, a global temporary table populated during the extract process. The definition is a straightforward projection that renames the technical staging columns into Federal-prefixed aliases, together with a hard-coded filter restricting the result set to the AP application. The column mapping is direct for the fund, obligation, and amount attributes, while FEDERAL_FUND_CAT_DESC is derived through a DECODE on FUND_CATEGORY, translating fund category codes A, B, and C to 'DIRECT' and codes R, S, and T to 'REIMBURSABLE'. This derivation applies no transformation to the monetary values themselves; amounts are surfaced exactly as staged. Because the source is a global temporary table, the view is meaningful only within a session that has already executed the FV extract that populates FV_EXTRACT_DETAIL_GT.
Key Columns
- FEDERAL_EVENT_ID — the subledger accounting event identifier, carried from EVENT_ID, tying each row to the originating AP accounting event.
- FEDERAL_LINE_NUMBER — the line identifier within the accounting event.
- FEDERAL_FUND_VALUE, FEDERAL_FUND_CATEGORY, FEDERAL_FUND_EXPIRED_STATUS — the Treasury Account Symbol fund attributes and the expiration status of the fund.
- FEDERAL_FUND_CAT_DESC — the decoded descriptive value, 'DIRECT' or 'REIMBURSABLE', associated with the fund category.
- FEDERAL_ADJUSTMENT_TYPE, FEDERAL_PRIOR_YEAR_FLAG, FEDERAL_ANTICIPATION — flags indicating the nature of the transaction, its prior-year status, and whether it is anticipated.
- FEDERAL_ANTICIPATED_AMT, FEDERAL_UNANTICIPATED_AMT, FEDERAL_TCF_AMT — anticipated, unanticipated, and Treasury Consolidated Fund components of the amounts.
- FEDERAL_PAID_RECEIVED_AMT — amounts paid or received.
- FEDERAL_PAID_UNEXP_OBG_AMT — the column surfaced from PAID_UNEXPENDED_OBLIGATION. This is the attribute users most commonly seek by the search term "federal_paid_unexp_obg_amt", representing paid amounts applied against unexpended obligations.
- FEDERAL_UNPAID_UNEXP_OBG_AMT, FEDERAL_UNPAID_RECEIVED_AMT, FEDERAL_UNPAID_OPEN_AMT — the corresponding unpaid obligation, received, and open amount balances.
Common Use Cases and Queries
The view is typically queried after an AP extract has been run into FV_EXTRACT_DETAIL_GT, either interactively for validation or embedded within Federal Financials concurrent reports and PL/SQL logic. A diagnostic query focusing on the paid unexpended obligation amount would resemble:
SELECT federal_event_id, federal_line_number, federal_fund_value, federal_paid_unexp_obg_amt, federal_unpaid_unexp_obg_amt
FROM apps.fv_xla_ap_ref_v
WHERE federal_paid_unexp_obg_amt <> 0;
Typical scenarios include reconciling obligated versus expended balances for Treasury reporting, verifying fund category classification through FEDERAL_FUND_CAT_DESC, isolating prior-year adjustments using FEDERAL_PRIOR_YEAR_FLAG, and dividing activity between anticipated and unanticipated amounts. Because the underlying table is session-scoped, a query against the view outside the extract session, or before the extract has run, returns no rows. All columns referenced in the view are documented as available; the object is listed as VALID in the ETRM metadata for both 12.1.1 and 12.2.2.
-
View: FV_XLA_AP_REF_V 12.1.1
APPS.FV_XLA_AP_REF_V·↳ FV_EXTRACT_DETAIL_GT·Explore FV module →
-
View: FV_XLA_AP_REF_V 12.2.2
APPS.FV_XLA_AP_REF_V·↳ FV_EXTRACT_DETAIL_GT·Explore FV module →
-
VIEW: APPS.FV_XLA_AP_REF_V 12.1.1
-
VIEW: APPS.FV_XLA_AP_REF_V 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - FV Tables and Views 12.2.2
Temporary table populated during the Year End Closing process
-
eTRM - FV Tables and Views 12.1.1
Temporary table populated during the Year End Closing process
-
12.2.2 DBA Data 12.2.2
-
eTRM - FV Tables and Views 12.2.2
Temporary table populated during the Year End Closing process
-
12.1.1 DBA Data 12.1.1
-
eTRM - FND Tables and Views 12.2.2
No longer used
-
eTRM - FV Tables and Views 12.1.1
Temporary table populated during the Year End Closing process
-
eTRM - FND Tables and Views 12.1.1
No longer used
-
eTRM - FND Tables and Views 12.2.2
No longer used
-
eTRM - FND Tables and Views 12.1.1
No longer used