Results for “program_agreement”

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

Overview

The OKL_CURE_REQUEST_UV view is a reporting and inquiry construct within the Oracle E-Business Suite Lease and Finance Management (OKL) module. It is owned by the APPS schema and holds a VALID status in the ETRM 12.1.1 and 12.2.2 data models. The view consolidates cure-related data — amounts negotiated, amounts received, repurchase obligations, and vendor reporting — into a single denormalized result set for lessors, lessees, and analysts reviewing cure requests against lease contracts.

The view is derived through a UNION of at least two query branches over the same logical join, allowing cure requests of differing statuses or sources to be surfaced together. Users typically query it by CURE_REPORT_ID (the user search term here), which identifies an individual cure report raised against a contract.

Underlying Base Objects

The documented metadata identifies the following base objects behind the view:

• OKL_CURE_REPORTS_ALL — the master cure report table, driving CURE_REPORT_ID, vendor details, approval status, report number, and currency.
• OKL_CURE_AMOUNTS / OKL_CURE_AMOUNTS_ALL — cure amount details attached to a report, joined via CR.CURE_REPORT_ID = CAM.CRT_ID.
• OKC_K_HEADERS_ALL_B (aliased CHR and PA) — the contract and program agreement headers.
• OKL_K_HEADERS — the OKL-specific header table linking contract to program agreement.
• OKC_K_PARTY_ROLES_B — supplies the LESSEE party role, joined to the customer.
• HZ_PARTIES — resolves PARTY_ID into the customer name.
• OKL_CURE_RECEIVED_UV — a nested view aggregating cure amounts already received.
• OKL_NO_OF_CURES_UV — a nested view counting cures in possession.
• OKL_TRX_QUOTES_V — the repurchase quote linked via CAM.QTE_ID.

These are exposed through APPS synonyms, and several are themselves views, so the effective lineage is deeper than a single join.

Key Columns

• CURE_REPORT_ID — primary identifier of the cure report; the most common filter key.
• CONTRACT_NUMBER, CUSTOMER_NAME, PROGRAM_AGREEMENT — the contract, lessee and program agreement context.
• CURE_AMOUNT, NEGOTIATED_AMOUNT, RECEIVED_AMOUNT, CURE_AMOUNT_RECEIVED — monetary measures, defaulted to 0 via NVL.
• REPURCHASE_AMOUNT, REPURCHASE_QUOTE_NUMBER — repurchase exposure and associated quote.
• APPROVAL_STATUS, REQUEST_STATUS, REQUEST_NUMBER — workflow state of the cure request.
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID, CURRENCY_CODE — vendor and currency attributes.
• CRT_ID, CHR_ID, QTE_ID — internal keys for joins and drill-down.

Common Use Cases and Queries

Typical uses include cure aging reports, outstanding cure balance tracking, vendor performance analysis, and reconciliation between negotiated and received amounts.

SELECT contract_number, customer_name, cure_report_id,
       cure_amount, negotiated_amount, received_amount, approval_status
FROM   apps.okl_cure_request_uv
WHERE  cure_report_id = :p_cure_report_id;

To list all open cure requests for a customer:

SELECT contract_number, request_number, cure_amount, request_status
FROM   apps.okl_cure_request_uv
WHERE  UPPER(customer_name) = UPPER(:p_customer)
AND    request_status <> 'COMPLETE';

As a _UV (user view), it is intended for read-only reporting and integration extracts rather than transactional updates. Performance depends on filtering by indexed base columns such as CURE_REPORT_ID or contract number.