Results for “jtot_object2_code”

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

Overview

The OKL_OR_PAYMENT_DETAILS_UV view is a reporting and integration object within the Oracle Lease and Finance Management (OKL) module. It resides in the APPS schema and is delivered with a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. The view exposes payment detail information for lease contracts by decoding structured rule data stored in the Oracle Contracts (OKC) rule repository, specifically the LASLL (lease line) rule information category. Its principal role is to present payment schedules — period counts, periodic amounts, stub periods, stub amounts, and derived start and end dates — in a denormalized, query-friendly form. This allows downstream reports, extracts, and interface programs to consume payment details without directly parsing the raw rule attributes held in OKC_RULES_B.

Underlying Base Objects

The view is defined over the base table OKC_RULES_B, referenced through the alias RUL_LASLL, combined with the FND_DATE package used for canonical-to-date conversion. The documented referenced base objects are:

• OKC_RULES_B (SYNONYM) — the source of all rule attribute values, filtered to the LASLL rule information category.
• FND_DATE (PACKAGE) — provides the CANONICAL_TO_DATE function used to convert Oracle canonical date strings into proper date values for START_DATE and END_DATE.

The view restricts its result set by requiring RULE_INFORMATION_CATEGORY = 'LASLL', a null or '#' value for OBJECT2_ID2 (via NVL(OBJECT2_ID2,'#') = '#'), and JTOT_OBJECT2_CODE = 'OKL_STRMHDR'. Results are ordered by the computed START_DATE. This filtering ties each row to a lease stream header record, linking the rule to a contract line through DNZ_CHR_ID and related identifiers.

Key Columns

• RUL_LASLL_ID — the surrogate identifier of the underlying rule row in OKC_RULES_B. This is the column that users searching for "rul_lasll_id" typically target.
• PERIODS — derived from RULE_INFORMATION3, the number of payment periods.
• PERIODIC_AMOUNT — derived from RULE_INFORMATION6, the recurring payment amount.
• STUB_DAYS and STUB_AMOUNT — derived from RULE_INFORMATION7 and RULE_INFORMATION8, capturing stub-period length and any stub payment amount.
• START_DATE — the canonical date conversion of RULE_INFORMATION2, representing the payment schedule start.
• END_DATE — computed either by adding months (periods multiplied by a frequency factor decoded from OBJECT1_ID1: M=1, Q=3, S=6, A=12) and subtracting one day, or by adding STUB_DAYS minus one when a stub exists.
• RGP_ID, DNZ_CHR_ID, OBJECT2_ID1, OBJECT2_ID2, JTOT_OBJECT2_CODE — linkage identifiers connecting the rule to its contract line and stream header context.

Common Use Cases and Queries

Typical scenarios include generating lease payment schedules for reporting, reconciling periodic versus stub amounts, and extracting lease line data for integration into subledger or accounting processes. A representative query is:

• SELECT RUL_LASLL_ID, PERIODS, PERIODIC_AMOUNT, START_DATE, END_DATE FROM OKL_OR_PAYMENT_DETAILS_UV;
• Filter by contract using the linkage column, for example WHERE DNZ_CHR_ID = :contract_id ORDER BY START_DATE;
• Isolate stub-bearing schedules with WHERE STUB_DAYS IS NOT NULL;
• Aggregate total scheduled value as SELECT PERIODS * PERIODIC_AMOUNT + NVL(STUB_AMOUNT,0) FROM OKL_OR_PAYMENT_DETAILS_UV WHERE DNZ_CHR_ID = :id;

Because the view performs date conversion and rule decoding at query time, consuming applications should treat it as read-only and avoid relying on it for high-volume transactional processing.