Results for “source_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKL_FE_RESI_CAT_ALL_B table, owned by the OKL schema, is the base table for Residual Category Sets within the Oracle E-Business Suite Leasing and Finance Management module (OKL). Residual category sets are the configurable groupings through which ETRM categorizes contractual residual values on leased assets, and this table serves as the master definition record for each set. Every residual category set used elsewhere in the residual value calculation and amortization flow traces back to a row in this table.

Based on the foreign key structure documented in the ETRM metadata, the table exhibits the characteristics of a Data Vault hub: it carries a single surrogate primary key (RESI_CATEGORY_SET_ID) and is referenced by multiple downstream objects, but contains no direct link relationships to other hubs. This classification is a heuristic modeling suggestion rather than a native ETRM designation, and it is consistent with the table's role as an anchor for residual category configuration rather than a transactional or historical record.

Key Information Stored

The table contains twelve documented columns, of which the following are most significant for configuration, integration, and reporting purposes:

• RESI_CATEGORY_SET_ID — surrogate primary key defined by OKL_FE_RESI_CAT_ALL_B_PK. This is the internal identifier used by all child tables.
• RESI_CAT_NAME — the residual category set name; combined with ORG_ID it forms the unique business key documented as OKL_FE_RESI_CAT_ALL_B_U2.
• ORG_ID — the operating unit / organization identifier, enforcing multi-org partitioning of residual category sets.
• STS_CODE — status code controlling whether the category set is active and available for use.
• SOURCE_CODE — indicates the origin or source system of the record, supporting seeded versus user-defined distinctions.
• ORIG_RESI_CAT_SET_ID — self-referencing foreign key pointing back to OKL_FE_RESI_CAT_ALL_B, used to track the originating category set when copies or derived definitions are created.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the ETRM framework during concurrent updates.
• CREATED_BY, CREATION_DATE — audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns recording the most recent modification and login session.

The two unique indexes, U1 on RESI_CATEGORY_SET_ID and U2 on (RESI_CAT_NAME, ORG_ID), establish both the surrogate and the natural business key, ensuring that category set names are unique within an operating unit.

Common Use Cases and Queries

The primary use case is resolving a residual category set identifier to its descriptive name and organization context during residual value reporting. A typical query joining the base table to downstream residual configurations is:

• SELECT rc.resi_category_set_id, rc.resi_cat_name, rc.org_id, rc.sts_code FROM okl.okl_fe_resi_cat_all_b rc WHERE rc.org_id = :org_id AND rc.sts_code = :active_status;
• Reporting the number of active residual category sets per operating unit.
• Identifying derived or copied category sets by following ORIG_RESI_CAT_SET_ID back to its parent row.
• Auditing recently modified configuration using LAST_UPDATED_BY and LAST_UPDATE_DATE for change-control reporting.
• Validating that a category set referenced in a transaction exists and is active before processing residual calculations.

Related Objects

The documented foreign key relationships identify the following significant dependent objects:

• OKL_FE_RESI_CAT_OBJECTS — references RESI_CATEGORY_SET_ID; holds the categorized objects belonging to each residual category set.
• OKL_FE_ITEM_RESIDUAL_ALL — references RESI_CATEGORY_SET_ID; stores residual values per lease item linked to the set.
• OKL_FE_EO_TERM_OBJECTS — references RESI_CATEGORY_SET_ID; associates term-level objects with the residual category set.
• OKL_FE_RESI_CAT_ALL_B — self-referencing via ORIG_RESI_CAT_SET_ID for origin tracking.

These four relationships form the core dependency chain through which residual category configuration propagates into ETRM residual calculation and reporting processes.