Search Results fvfv_appropriation_parameters

Overview

FVFV_APPROPRIATION_PARAMETERS is a read-only reporting view in the Oracle E-Business Suite Federal Financials (FV) module. It consolidates appropriation, fund, and treasury-symbol attributes into a single denormalized structure, allowing federal agencies to report against fund parameter balances—including unliquidated commitments and unliquidated obligations—without joining multiple base tables manually. The view joins FV_TREASURY_SYMBOLS, FV_FUND_PARAMETERS, and GL_SETS_OF_BOOKS, and is defined with the WITH READ ONLY clause, ensuring it cannot be used for DML operations. Its design supports appropriation-status reporting, Treasury symbol reconciliation, and fund-control dashboards, where the unliquidated commitment balance is a frequently queried figure. The view is documented against ETRM 12.1.1 / 12.2.2, and the metadata note "Not implemented in this database" indicates it may be created conditionally during Federal Financials installation or only where the underlying objects exist.

Underlying Base Objects

The view is defined over three documented base objects:

• FV_TREASURY_SYMBOLS (alias FTS) — supplies TREASURY_SYMBOL and TREASURY_SYMBOL_ID, the Treasury account symbol identifying the appropriation.
• FV_FUND_PARAMETERS (alias FFP) — the driving table, supplying fund value, budget authority, transfers, unliquidated commitments/obligations, expended amount, red status, and prior-year recoveries.
• GL_SETS_OF_BOOKS (alias GSB) — supplies SET_OF_BOOKS_NAME via SET_OF_BOOKS_ID.

The join relationships are explicit: FTS.TREASURY_SYMBOL_ID = FFP.TREASURY_SYMBOL_ID and GSB.SET_OF_BOOKS_ID = FFP.SET_OF_BOOKS_ID. Although ETRM lists no further referenced base objects, the view text embeds descriptive-flexfield and lookup directives (_LA:FFP.FUND_CATEGORY, _DF:FV:FV_FUND_DESC_FLEX:FFP), which are interpreted by the Oracle Forms/EBS descriptive-flexfield framework rather than as physical joins.

Key Columns

• TREASURY_SYMBOL — the Treasury account symbol (e.g., agency, main account, sub-account) qualifying the appropriation.
• FUND_VALUE / FUND_PARAMETER_ID — the fund identifier and its surrogate primary key from FV_FUND_PARAMETERS.
• SET_OF_BOOKS_ID / SET_OF_BOOKS_NAME — the ledger context for the balances.
• BUDGET_AUTHORITY — appropriated budget authority recorded against the fund.
• TRANSFERS_IN / TRANSFERS_OUT — funds transferred into or out of the appropriation.
• UNLIQUID_COMMITMENTS — the outstanding commitment balance not yet liquidated; the column central to the user's search.
• UNLIQUID_OBLIGATIONS — obligations incurred but not yet expended (undelivered orders).
• EXPENDED_AMOUNT — cumulative outlays/disbursements.
• RED_STATUS — indicator flagging a fund or transaction awaiting resolution.
• PRIOR_YEAR_RECOVERIES — recoveries applied from prior periods.
• _LA:FUND_CATEGORY and _DF — pseudo-columns carrying lookup and descriptive-flexfield directives.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY.

Common Use Cases and Queries

Typical scenarios include unliquidated commitment analysis, appropriation-status reporting, and reconciliation between budget authority, obligations, and outlays. The following query lists unliquidated commitments by Treasury symbol and ledger:

SELECT treasury_symbol,
       set_of_books_name,
       fund_value,
       unliquid_commitments,
       unliquid_obligations,
       expended_amount,
       budget_authority
  FROM fvfv_appropriation_parameters
 WHERE unliquid_commitments > 0
 ORDER BY treasury_symbol;

A fund-control comparison of authority versus commitments and obligations can be written as:

SELECT treasury_symbol,
       budget_authority,
       transfers_in - transfers_out AS net_transfers,
       unliquid_commitments,
       unliquid_obligations + expended_amount AS total_obligated
  FROM fvfv_appropriation_parameters
 WHERE set_of_books_id = :ledger_id;

Because the view is read-only, it is suited to report development, concurrent-program extract logic, and integration feeds rather than transaction entry. Analysts should confirm that the view exists in the target instance, since the metadata records it as "Not implemented in this database" for the documented environment.