Search Results okl_fe_resi_cat_all_b




Overview
Explore in AI Chat

Overview

The OKL_FE_RESI_CAT_ALL_B table is a core data structure within Oracle E-Business Suite's Leasing and Finance Management module (OKL). It functions as the base table for storing residual category sets. In the context of lease accounting and asset management, a residual category set is a logical grouping that defines the expected residual value categories for leased assets at the end of a lease term. This table is essential for configuring and managing the financial treatment of asset residuals, which directly impacts lease classification, revenue recognition, and financial reporting. Its role is foundational, serving as a master reference point for residual valuation rules that are applied to specific lease contracts and their underlying assets.

Key Information Stored

While the provided metadata does not list specific columns beyond key identifiers, the structure and relationships indicate the table's critical data elements. The primary key is the RESI_CATEGORY_SET_ID, a unique identifier for each residual category set. Another significant column is ORIG_RESI_CAT_SET_ID, which creates a self-referential foreign key relationship, suggesting the table supports versioning or hierarchical relationships between category sets (e.g., original vs. modified sets). Typical columns in such a base table would also include standard Oracle EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), an OBJECT_VERSION_NUMBER for optimistic locking, and descriptive attributes like NAME or DESCRIPTION for the category set.

Common Use Cases and Queries

This table is primarily accessed during the setup and execution of lease financial calculations. A common use case is retrieving the residual category set assigned to a specific lease contract or asset to determine the appropriate residual value treatment for accounting entries. Database administrators or developers may query this table to audit setup data or troubleshoot issues with residual calculations. A typical reporting query would join this table to its related transaction tables to list all configured category sets and their usage.

  • Sample Query to List Category Sets:
    SELECT resi_category_set_id, orig_resi_cat_set_id FROM okl.okl_fe_resi_cat_all_b;
  • Use Case: Identifying all lease term objects (OKL_FE_EO_TERM_OBJECTS) linked to a specific residual category set for impact analysis during a setup change.

Related Objects

The OKL_FE_RESI_CAT_ALL_B table is central to the residual management sub-schema, with documented foreign key relationships to several key transaction tables. These relationships enforce data integrity and define how residual category sets are applied.

  • OKL_FE_EO_TERM_OBJECTS: Links via RESI_CATEGORY_SET_ID. This associates a residual category set with a specific lease term or financial engine object.
  • OKL_FE_ITEM_RESIDUAL_ALL: Links via RESI_CATEGORY_SET_ID. This ties the category set to the specific residual values assigned to individual leased items or assets.
  • OKL_FE_RESI_CAT_OBJECTS: Links via RESI_CATEGORY_SET_ID. This likely stores the detailed residual category objects or rules that belong to a defined set.
  • Self-Referential (OKL_FE_RESI_CAT_ALL_B): Links via ORIG_RESI_CAT_SET_ID to RESI_CATEGORY_SET_ID. This allows for tracking the lineage or derivation of one category set from another.