Search Results okl_fe_item_residual_all




Overview
Explore in AI Chat

Overview

The OKL_FE_ITEM_RESIDUAL_ALL table is a core data object within the Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, specifically for the OKL (Lease and Finance Management) product module. As indicated by its description, "Item Residual Header," this table serves as the primary repository for managing residual value information associated with individual leased or financed assets (items). Residual values represent the estimated fair market value of an asset at the end of a lease or financing term and are critical for calculating lease accounting entries, determining buyout options, and managing asset portfolios. The table's "_ALL" suffix denotes its support for a multi-organization architecture, meaning it stores data partitioned by operating unit (ORG_ID). Its role is central to the Fair Value Engine and residual value management processes within Oracle Lease Management.

Key Information Stored

The table's structure is designed to link asset details with established residual value categories and historical data. While the full column list is not detailed in the provided excerpt, the foreign key relationships reveal its critical data elements. The primary key is ITEM_RESIDUAL_ID, a unique identifier for each record. Essential foreign keys include INVENTORY_ITEM_ID and ORG_ID, linking to the inventory master (MTL_SYSTEM_ITEMS_B) to identify the specific asset. The RESI_CATEGORY_SET_ID links to OKL_FE_RESI_CAT_ALL_B, associating the item with a predefined residual value category or schedule. The presence of an ORIG_ITEM_RESIDUAL_ID column, which self-references the table's primary key, indicates the table supports versioning or historical tracking of residual value assignments for an item over time, allowing users to trace changes.

Common Use Cases and Queries

This table is primarily accessed for asset portfolio analysis, lease accounting calculations, and audit reporting. Common operational and reporting queries involve joining with related inventory and category tables. A typical use case is retrieving the current residual value setup for assets within a specific operating unit. A sample SQL pattern for such a report would be:

  • SELECT oir.ITEM_RESIDUAL_ID, msib.SEGMENT1 ITEM, msib.DESCRIPTION, rcat.NAME RESIDUAL_CATEGORY, oir.ORIG_ITEM_RESIDUAL_ID
  • FROM OKL.OKL_FE_ITEM_RESIDUAL_ALL oir,
  • INV.MTL_SYSTEM_ITEMS_B msib,
  • OKL.OKL_FE_RESI_CAT_ALL_B rcat
  • WHERE oir.INVENTORY_ITEM_ID = msib.INVENTORY_ITEM_ID
  • AND oir.ORG_ID = msib.ORGANIZATION_ID
  • AND oir.RESI_CATEGORY_SET_ID = rcat.RESI_CATEGORY_SET_ID
  • AND oir.ORG_ID = :p_org_id;

Another critical use case is tracing the history of residual value assignments for a given asset by recursively querying the table using the ORIG_ITEM_RESIDUAL_ID link to the ITEM_RESIDUAL_ID.

Related Objects

The foreign key constraints explicitly define this table's integration within the EBS data model. Key related objects include:

  • MTL_SYSTEM_ITEMS_B: Provides the master inventory item definition and description.
  • OKL_FE_RESI_CAT_ALL_B: The residual category setup table, which defines the residual value schedules or percentages applied to items.
  • MTL_ITEM_CATEGORIES: Links items to their inventory categories, potentially used for residual assignment rules.
  • Self-Referencing (OKL_FE_ITEM_RESIDUAL_ALL): The relationship from ORIG_ITEM_RESIDUAL_ID to ITEM_RESIDUAL_ID creates an internal hierarchy for tracking the lineage of residual value records.

This table is foundational for downstream processes in lease accounting, where its data is likely referenced by various OKL transaction tables and the Fair Value Engine calculation programs.