Search Results okl_fe_eo_term_objects




Overview
Explore in AI Chat

Overview

The table OKL_FE_EO_TERM_OBJECTS is a core data object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module, specifically for versions 12.1.1 and 12.2.2. It serves as the master repository for defining the individual assets or items associated with an End-of-Term (EOT) valuation scenario. The table's primary role is to link a specific End-of-Term valuation version, defined in the OKL_FE_EO_TERM_VERS table, with the tangible or intangible assets being evaluated for their residual value at the conclusion of a lease or finance agreement. This object-level granularity is critical for accurate residual value forecasting, asset disposition planning, and financial reporting within complex leasing portfolios.

Key Information Stored

While the full column list is not provided in the metadata, the documented foreign key relationships and primary key reveal the essential data elements stored. The primary identifier is END_OF_TERM_OBJ_ID. Each record is fundamentally tied to a specific End-of-Term valuation version via the END_OF_TERM_VER_ID foreign key. The table stores references to the asset being valued, which can be defined in two primary ways: as a specific Inventory Item (using INVENTORY_ITEM_ID and ORGANIZATION_ID, linking to MTL_SYSTEM_ITEMS_B) or as a member of an Inventory Item Category (using the same item and org IDs plus CATEGORY_SET_ID, linking to MTL_ITEM_CATEGORIES). Additionally, the table can associate the object with a residual value category via the RESI_CATEGORY_SET_ID, linking to the OKL_FE_RESI_CAT_ALL_B table, which is used for specialized residual value calculations.

Common Use Cases and Queries

This table is central to processes involving the setup and inquiry of end-of-term valuations. A common operational use case is the generation of reports listing all assets included in a specific valuation scenario for review or audit purposes. Development and support tasks frequently involve queries to diagnose data issues or extract configuration details. A typical SQL pattern retrieves all objects for a given valuation version, joining to inventory tables for descriptive information:

  • SELECT obj.*, msib.segment1 item_code FROM okl_fe_eo_term_objects obj, mtl_system_items_b msib WHERE obj.end_of_term_ver_id = :p_ver_id AND obj.inventory_item_id = msib.inventory_item_id AND obj.organization_id = msib.organization_id;

Another critical use case is validating the existence of asset definitions before running batch valuation processes, ensuring all referenced inventory items and categories are valid and active within the system.

Related Objects

The table maintains defined relationships with several key EBS tables, as per the provided metadata. The primary key constraint is OKL_FE_EO_TERM_OBJECTS_PK. The foreign key relationships, detailing how this table references others, are as follows:

  • OKL_FE_EO_TERM_VERS: Via END_OF_TERM_VER_ID. This is the parent table for all End-of-Term valuation scenarios.
  • MTL_SYSTEM_ITEMS_B: Via INVENTORY_ITEM_ID and ORGANIZATION_ID. Links to the Inventory Master to identify a specific asset.
  • MTL_ITEM_CATEGORIES: Via INVENTORY_ITEM_ID, ORGANIZATION_ID, and CATEGORY_SET_ID. Links to the Item Categories, allowing valuation at a category level rather than a specific item.
  • OKL_FE_RESI_CAT_ALL_B: Via RESI_CATEGORY_SET_ID (listed twice, potentially for different contexts or attributes). Links to the Residual Value Category setup.

These relationships enforce data integrity and are essential for constructing accurate joins in reports, interfaces, and custom extensions within the OKL module.