Results for “okl_cure_request_type”

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

Overview

OKL_CURE_INVOICE_UV is an Oracle E-Business Suite view owned by the APPS schema within the OKL – Leasing and Finance Management product. It exposes consolidated cure request information, joining cure reports, cure amounts, contracts, invoices, quotes, and lookup values into a single reporting structure. The view is not a base table; it is a query-only construct intended for reporting and integration scenarios where cure-related financial data must be presented with descriptive meanings rather than raw codes. Cure requests arise in leasing when a lessee or vendor fails to meet contractual obligations and a remediation (cure) amount, negotiated amount, or repurchase is proposed and tracked through an approval lifecycle. OKL_CURE_INVOICE_UV surfaces that lifecycle alongside the associated contract, program agreement, and accounts receivable invoice. Because it is a view, it reflects live committed data from the underlying tables and is governed by the same security and access rules as those tables.

Underlying Base Objects

The view is defined over several documented base objects. Cure report header data comes from OKL_CURE_REPORTS_ALL, while cure amount detail is drawn from OKL_CURE_AMOUNTS_ALL. Contract header information is sourced from OKL_K_HEADERS and OKC_K_HEADERS_B (aliased for both the contract and the program agreement), with rule configuration read from OKC_RULES_B. Invoice linkage is provided by OKL_TRX_AR_INVOICES_B, and quote information by OKL_TRX_QUOTES_ALL_B. Cure amounts already received are aggregated through the OKL_CURE_RECEIVED_UV view. Descriptive code meanings are resolved through FND_LOOKUPS for both the approval status and the report type. The joins are primarily driven by the cure report ID linking to cure amounts and received amounts, and by contract header IDs linking contracts to program agreements and rules.

Key Columns

• REQUEST_NUMBER / REQUEST_DATE – Cure report number and date, from the cure report header.
• APPROVAL_STATUS – Coded approval state of the cure request; the view restricts rows to SENT_TO_VENDOR, APPROVED, ACCEPTANCE_COMPLETED, and ACCEPTANCE_IN_PROGRESS.
• APPROVAL_STATUS_MEANING – The user-facing meaning of the approval status, decoded from FND_LOOKUPS using lookup type OKL_CURE_REQUEST_APPROVE_STATU. This column directly answers the query "approval_status_meaning".
• CURE_AMOUNT / CURE_AMOUNT_RECEIVED / NEGOTIATED_AMOUNT / REPURCHASE_AMOUNT – Financial measures for the cure, each defaulted to zero where null.
• SHORT_FUND_ALLOWED – Derived flag (YES/NO) from a rule attribute indicating whether short funding is permitted.
• TOTAL_NEGOTIATED_AMOUNT – Scalar subquery summing negotiated amounts across all cure amount rows for the report.
• CONTRACT_NUMBER / PROGRAM_AGREEMENT – Contract and program agreement identifiers.
• QUOTE_NUMBER / QTE_ID – Repurchase quote reference.
• CURRENCY_CODE, VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID – Party and currency attributes of the cure.

Common Use Cases and Queries

The most frequent use is approval status reporting, since the view resolves coded statuses into readable meanings. A typical query lists active cure requests with their status and amounts:

SELECT request_number, contract_number, approval_status_meaning,
       cure_amount, negotiated_amount, currency_code
  FROM apps.okl_cure_invoice_uv
 WHERE approval_status_meaning = 'Approved';

Analysts also use the view to reconcile negotiated amounts against amounts received, and to identify cure requests linked to repurchase quotes. Because the view already filters to the four active approval states, it is well suited to dashboards and extracts that must exclude fully closed or rejected requests.