Results for “okl_ls_rt_ftr_sets_all_b_u2”

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

Overview

The table OKL.OKL_LS_RT_FTR_SETS_ALL_B is a core lease management object in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, owned by the OKL schema. It stores Lease Rate Factor Sets, which the ETRM documentation defines as "a grouping of lease rate factors based upon certain common attributes. Specifically, the Payment Frequency, Payment in Advance or Arrears, and the Rate." The list of identifying attributes is noted as likely to grow in future releases. In Oracle Lease Management (OLM), a Lease Rate Set is synonymous with a Rate Card, making this table the master repository for pricing structures used to compute lease payments. It resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, and is flagged VALID with FND Design Data reference OKL.OKL_LS_RT_FTR_SETS_ALL_B. Under the heuristic Data Vault classification mined from its FK structure, this object behaves as a standalone hub: it holds the primary business entity (the rate set), while its dependent attributes and relationships radiate outward to satellite and link structures. No incoming foreign keys were identified, reinforcing its position as an independent master record anchored by a single-column surrogate primary key.

Key Information Stored

The table comprises 37 documented columns. The most functionally significant are:

• ID (NUMBER, mandatory): the surrogate primary key, enforced by OKL_LS_RT_FTR_SETS_ALL_B_PK.
• NAME: the rate set name; a business-key candidate unique by itself via OKL_LS_RT_FCTR_SETS_U2 and jointly with ORG_ID via OKL_LS_RT_FTR_SETS_ALL_B_U2.
• ORG_ID: the operating unit that scopes the rate set; part of the composite unique business key.
• RATE: the lease rate factor value; indexed non-uniquely (N1) for rate-based lookups.
• FRQ_CODE (VARCHAR2 30): the payment frequency on which lease rate factors are computed.
• ARREARS_YN: indicates whether payments are made in arrears (Yes) or advance (No).
• START_DATE and END_DATE: the activation and deactivation dates of the rate set, both non-uniquely indexed (N2, N3).
• STS_CODE: the status code governing usability of the set.
• CURRENCY_CODE: the currency in which the rate is denominated.
• LRS_TYPE_CODE: the Lease Rate Set type; indexed non-uniquely (N4).
• END_OF_TERM_ID: foreign key to OKL_FE_EO_TERMS_ALL_B, defining end-of-term treatment; indexed non-uniquely (N5).
• ORIG_RATE_SET_ID: traces a set back to its originating rate set, supporting versioning or copy scenarios.
• OBJECT_VERSION_NUMBER: locking column for concurrent updates.
• PDT_ID and TRY_ID: documented as not currently in use.

Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and fifteen ATTRIBUTE flex columns, plus ATTRIBUTE_CATEGORY, complete the structure. Note that the name-based indexes are valuable for resolving ambiguity between "OKL_LS_RT_FCTR_SETS_U2" (NAME only) and the longer "OKL_LS_RT_FTR_SETS_ALL_B_U2" (NAME, ORG_ID).

Common Use Cases and Queries

Typical scenarios include retrieving active rate cards for a given operating unit and payment convention, validating uniqueness of a rate set name before creation, and reporting on rate coverage across currencies and frequencies.

• Fetch active rate sets: SELECT id, name, rate, frq_code, currency_code FROM okl.okl_ls_rt_ftr_sets_all_b WHERE org_id = :p_org AND sts_code = 'ACTIVE' AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);
• Resolve by business key: filter on NAME and ORG_ID to exploit OKL_LS_RT_FTR_SETS_ALL_B_U2 and avoid a full scan.
• Join to end-of-term terms via END_OF_TERM_ID for payment schedule configuration.
• Rate analysis: aggregate on LRS_TYPE_CODE, FRQ_CODE, and CURRENCY_CODE for pricing reports, using the N1/N4 indexes.
• Duplicate detection: query on ORIG_RATE_SET_ID to find rate sets derived from a source card.

Related Objects

The documented FK relationship anchors this table to OKL.OKL_FE_EO_TERMS_ALL_B via END_OF_TERM_ID. Because the table is classified as standalone, dependent rate factor lines and translations typically reside in sibling OKL tables (rate factor and _TL translation objects) that reference ID. Standard WHO columns link to FND_USER and FND_LOGINS. Reporting views in the OKL schema and the OLM pricing APIs that consume Rate Cards read from this table by ID or by NAME/ORG_ID. ORG_ID aligns with HR_OPERATING_UNITS, and CURRENCY_CODE aligns with FND_CURRENCIES. Always join on the ID surrogate key for performance, reserving the NAME and NAME/ORG_ID unique indexes for interactive lookups.