Search Results resi_cat_object_id

Overview

The OKL_FE_RESI_CAT_OBJECTS table 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 functions as a junction table that defines the membership of specific inventory items and categories within a Residual Category Set. A Residual Category Set is a configuration used to classify assets for residual value calculations, a critical component in lease accounting and financial forecasting. This table enables the flexible association of tangible assets (items) and logical groupings (categories) to a defined set, forming the basis for automated residual value processing within complex lease portfolios.

Key Information Stored

The table's primary purpose is to store associative relationships, with its key columns serving as foreign keys to other master data tables. The central column is RESI_CATEGORY_SET_ID, which links to the parent residual category set definition (OKL_FE_RESI_CAT_ALL_B). For each set, the table records specific objects using INVENTORY_ITEM_ID and ORGANIZATION_ID to point to a unique item in Inventory (MTL_SYSTEM_ITEMS_B). Alternatively, it can categorize objects using INVENTORY_ITEM_ID, ORGANIZATION_ID, and CATEGORY_SET_ID to link to an item category assignment (MTL_ITEM_CATEGORIES). The unique identifier for each record in this table is RESI_CAT_OBJECT_ID, which is the primary key. This structure allows a single residual category set to contain a mix of individual items and entire item categories.

Common Use Cases and Queries

This table is primarily accessed during the setup and execution of residual value processes. Common operational and reporting scenarios include validating the composition of a residual category set, generating lists of assets included in a specific set for audit purposes, and supporting the data feed for residual value engine calculations. A typical query would join this table to item and category master tables to produce a human-readable list. For example:

• Listing all items in a specific residual category set:
  SELECT msib.segment1 item_code, msib.description
FROM okl_fe_resi_cat_objects obj, mtl_system_items_b msib
WHERE obj.inventory_item_id = msib.inventory_item_id
AND obj.organization_id = msib.organization_id
AND obj.resi_category_set_id = :p_set_id;
• Identifying which residual category sets a given inventory item belongs to:
  SELECT cat_set.name
FROM okl_fe_resi_cat_objects obj, okl_fe_resi_cat_all_b cat_set
WHERE obj.resi_category_set_id = cat_set.resi_category_set_id
AND obj.inventory_item_id = :p_item_id
AND obj.organization_id = :p_org_id;

Related Objects

The functionality of OKL_FE_RESI_CAT_OBJECTS is defined by its relationships with key master data and configuration tables in EBS. The documented foreign key constraints explicitly detail these dependencies:

• OKL_FE_RESI_CAT_ALL_B: The parent table for residual category set definitions. The join is made via the column OKL_FE_RESI_CAT_OBJECTS.RESI_CATEGORY_SET_ID.
• MTL_SYSTEM_ITEMS_B: The Inventory items master table. The join uses the composite key of OKL_FE_RESI_CAT_OBJECTS.INVENTORY_ITEM_ID and ORGANIZATION_ID.
• MTL_ITEM_CATEGORIES: The table storing item-to-category assignments. The join uses the composite key of OKL_FE_RESI_CAT_OBJECTS.INVENTORY_ITEM_ID, ORGANIZATION_ID, and CATEGORY_SET_ID.

These relationships ensure referential integrity, guaranteeing that objects linked to a residual category set are valid and exist within the Oracle Inventory and OKL module setups.