Search Results present_value




Overview
Explore in AI Chat

Overview

FABV_ASSET_LEASES is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OFA (Oracle Assets) product family. It exposes the lease header information maintained in Oracle Assets for capital and operating leases, presenting each lease as a single logical record for reporting and integration purposes. Because the view is defined WITH READ ONLY, it cannot be used to insert, update, or delete lease data; it exists purely as a query surface. The naming convention (FABV_) follows the Oracle Assets reporting-view standard, indicating a query-optimized projection of an underlying transactional table rather than a base entity in its own right. Organizations use this view to build custom reports, extracts, and interfaces that need lease-level attributes without querying the underlying FA_LEASES table directly.

Underlying Base Objects

The view is defined over a single documented base object: FA_LEASES, accessed through a synonym. The ETRM metadata lists the referenced object as FA_LEASES (SYNONYM), meaning the view text resolves the synonym to the underlying APPS table at runtime. There are no joins, unions, aggregations, or outer references in the view definition; it is a straight column projection. Consequently, every row in FABV_ASSET_LEASES corresponds one-to-one with a row in FA_LEASES, and every column in the view is sourced from that table without transformation, derivation, or calculation. This one-to-one relationship makes the view a safe, stable substitute for direct table access in read-only contexts, and it shields reporting code from any future column or storage changes applied to the base table as long as the projected column list is preserved.

Key Columns

The view exposes the following columns, all carried verbatim from FA_LEASES:

  • LEASE_ID — Primary identifier for the lease record; the join key to lease-related detail tables.
  • LEASE_NUMBER — User-facing lease number used for identification and search.
  • DESCRIPTION — Free-text description of the lease.
  • FASB_LEASE_TYPE — Classifies the lease under FASB accounting rules (for example, capital versus operating treatment).
  • COST_CAPITALIZED — Amount capitalized onto the asset books for the lease.
  • TRANSFER_OWNERSHIP / BARGAIN_PURCHASE_OPTION — Flags indicating whether ownership transfers at lease end or a bargain purchase option exists; both are classic capital-lease criteria.
  • FAIR_VALUE / PRESENT_VALUE — The asset fair value and the present value of minimum lease payments, used in lease classification tests.
  • LEASE_TYPE — Internal lease categorization as defined in Oracle Assets.
  • ASSET_LIFE / LEASE_TERM — Expected asset life and the contractual lease term.
  • LESSOR_ID — Identifier of the lessor associated with the lease. This is the column most commonly targeted when users search on "lessor_id," typically to group leases by lessor or join to supplier/lessor reference data.
  • CURRENCY_CODE — Currency in which the lease amounts are denominated.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — Standard audit columns recording creation and last modification metadata.

Common Use Cases and Queries

Typical usage includes lease inventory reporting, capitalization analysis, lessor-level exposure summaries, and audit extracts. A common requirement is retrieving all leases for a specific lessor:

  • SELECT lease_id, lease_number, description, lessor_id, currency_code FROM fabv_asset_leases WHERE lessor_id = :p_lessor_id;
  • SELECT lessor_id, COUNT(*) lease_count, SUM(cost_capitalized) total_capitalized FROM fabv_asset_leases GROUP BY lessor_id;
  • SELECT lease_number, fasb_lease_type, fair_value, present_value, lease_term, asset_life FROM fabv_asset_leases WHERE lease_type = :p_type ORDER BY lease_number;

Because the view is read-only and performs no joins, queries against it are inexpensive, and it can be embedded safely in concurrent programs, BI Publisher data models, and custom OAF or Forms lookups. Reporting code should join LEASE_ID to the relevant Oracle Assets lease detail tables and LESSOR_ID to the appropriate lessor or supplier reference when richer context is required.