Search Results fa_leases_web_v




Overview
Explore in AI Chat

Overview

FA_LEASES_WEB_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the OFA (Oracle Assets) product family. Its documented purpose is to present information about leases assigned to assets, joining asset master data from FA_ADDITIONS to the corresponding lease records held in FA_LEASES. The view is exposed as a web-facing reporting object, which explains the "_WEB_V" suffix; it is intended for use by Oracle Assets self-service pages, lease inquiry functionality, and custom reporting or integration layers that need a denormalized, read-only projection of lease-to-asset relationships.

The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it holds no data of its own and carries no direct DML capability; all content is derived at query time from the underlying base objects. This makes it safe to query from ad hoc SQL, BI Publisher reports, OBIEE/OBIA extract pipelines, and other downstream integration mechanisms without affecting transactional integrity.

Underlying Base Objects

The view is defined over six documented base objects, all resolved through the APPS schema:

The joins to the category flexfield, asset key flexfield, and category base table are implemented as outer joins, whereas the joins to FA_LEASES and PO_VENDORS are inner joins. Consequently, only assets with a valid LEASE_ID and matching lessor vendor will appear in the result set, and a lease with no linked vendor will be filtered out entirely.

Key Columns

The projection contains asset attributes from FA_ADDITIONS (ASSET_ID, ASSET_NUMBER, ASSET_KEY_CCID, CURRENT_UNITS, ASSET_TYPE, TAG_NUMBER, ASSET_DESCRIPTION, ASSET_CATEGORY_ID, PARENT_ASSET_ID, MANUFACTURER_NAME, SERIAL_NUMBER, MODEL_NUMBER, PROPERTY_TYPE_CODE, PROPERTY_1245_1250_CODE, IN_USE_FLAG, OWNED_LEASED, NEW_USED, UNIT_ADJUSTMENT_FLAG, ADD_COST_JE_FLAG) and lease attributes from FA_LEASES (LEASE_ID, LEASE_NUMBER, LESSOR_ID, LEASE_DESCRIPTION, audit columns, and ATTRIBUTE1 through ATTRIBUTE15 plus ATTRIBUTE_CATEGORY_CODE for descriptive flexfield content).

Supplier information is exposed as VENDOR_ID and VENDOR_NAME from PO_VENDORS. Category context is provided via CATEGORY_TYPE, CAPITALIZE_FLAG, and the derived CATEGORY concatenated segment. The asset key flexfield is surfaced as ASSET_KEY. Particularly useful for filtering are IN_USE_FLAG, OWNED_LEASED (a value of 'LEASED' versus 'OWNED'), and the DFF ATTRIBUTE columns inherited from the lease header.

Common Use Cases and Queries

Typical uses include reconciling leased assets to lessors, producing lease registers for accounting and tax reporting, and validating capitalization and category assignment for leased assets. A simple listing of leased assets by lessor:

  • SELECT asset_number, asset_description, lease_number, vendor_name FROM apps.fa_leases_web_v ORDER BY vendor_name, asset_number;
  • SELECT lease_number, category, COUNT(*) FROM apps.fa_leases_web_v WHERE owned_leased = 'LEASED' GROUP BY lease_number, category;
  • SELECT asset_number, lease_number, attribute1 FROM apps.fa_leases_web_v WHERE lease_id = :p_lease_id;

Because all key flexfield segments are resolved through the KFV views and vendor data through PO_VENDORS, queries should be issued from the APPS schema or with fully qualified names to ensure the synonyms resolve correctly.