Search Results src_id

Overview

FA_LIFES_V is a consolidated reporting view within the Oracle E-Business Suite (EBS) Oracle Assets (OFA) module. Its primary purpose is to present a unified lifecycle-date dataset by aggregating life end dates from four distinct sources that exist within the assets domain: asset hierarchy nodes, leases, individual assets, and asset categories. By normalizing these heterogeneous sources into a single result set with a common SRC_TYPE discriminator, the view enables reporting tools, reconciliation scripts, and integration interfaces to query depreciation and expiration horizons across multiple object families without writing separate queries for each source table.

In EBS 12.1.1 and 12.2.2, this view is typically used for period-end analysis, asset retirement forecasting, and lease expiration monitoring. Because it unions data across unrelated transaction streams, it functions as a lightweight abstraction layer above the FA schema, allowing developers to build downstream logic against a stable column projection regardless of which source produced a given row.

Underlying Base Objects

The view is defined over the following documented base objects within the FA schema:

• FA_ASSET_HIERARCHY and FA_ASSET_HIERARCHY_VALUES — joined on ASSET_HIERARCHY_ID to produce hierarchy node rows of SRC_TYPE 'NODE'.
• FA_LEASE_PAYMENTS and FA_LEASES — joined on PAYMENT_SCHEDULE_ID to produce lease rows of SRC_TYPE 'LEASE'.
• FA_BOOKS — filtered on DATE_INEFFECTIVE IS NULL to produce asset-level rows of SRC_TYPE 'ASSET'.
• FA_CATEGORY_BOOK_DEFAULTS — filtered by the current SYSDATE falling between START_DPIS and NVL(END_DPIS, SYSDATE) to produce category-level rows of SRC_TYPE 'CATEGORY'.

The view's union structure means it exposes no single owning table; instead each branch contributes a distinct row family. The ETRM metadata notes that the view is not implemented in every database, so availability must be verified before dependence in custom code.

Key Columns

The view projects a fixed set of columns across all union branches:

• SRC_TYPE — discriminator identifying the origin row family: 'NODE', 'LEASE', 'ASSET', or 'CATEGORY'.
• SRC_ID — the identifier of the source record (asset hierarchy ID, lease ID, asset ID, or category ID depending on SRC_TYPE).
• LEVEL_NUMBER / HIERARCHY_LEVEL — hierarchy depth for node rows; populated as 0 for the other branches.
• BOOK_TYPE_CODE — the depreciation book associated with the row; NULL for lease rows.
• LIFE_END_DATE — the computed or stored end-of-life date, sourced from LIFE_END_DATE, FLP.END_DATE, PRORATE_DATE, or IFA_LIFE_END_DATE depending on the branch.
• LIFE_IN_MONTHS — remaining or total life in months; nonzero primarily for asset and category rows.
• PARENT_HIERARCHY_ID — parent reference for hierarchy node rows; 0 for the remaining branches.

Common Use Cases and Queries

Typical scenarios include forecasting asset retirements by book, auditing lease end dates against lease payment schedules, and reconciling category default lives against booked assets. A representative query returning asset and category life ends for a given book follows:

• SELECT src_type, src_id, book_type_code, life_end_date, life_in_months FROM fa_lifes_v WHERE book_type_code = :p_book AND src_type IN ('ASSET','CATEGORY') ORDER BY life_end_date;
• SELECT src_type, COUNT(*) FROM fa_lifes_v GROUP BY src_type;
• SELECT src_id, life_end_date FROM fa_lifes_v WHERE src_type = 'LEASE' AND life_end_date BETWEEN :from_date AND :to_date;

Because the view mixes sources, filtering on SRC_TYPE is essential for predictable results, and any join back to detail tables must account for the polymorphic SRC_ID.