Results for “cure_refund_id”

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

Overview

OKL_REFUND_UV is a reporting and inquiry view owned by the APPS schema within Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the OKL – Leasing and Finance Management product family. The view consolidates cure-refund exposure across lease and loan contracts and exposes each refund position in the context of the originating vendor program. Functionally, it answers the operational question: for a given vendor leasing program, which lease or loan contracts still carry an outstanding cure refund, and to which vendor and lessee are those amounts attributable?

The suffix "UV" denotes a user-facing validation or inquiry view, intended primarily for reporting, ad hoc query, and downstream integration rather than for transactional update. Because it joins contract headers, party roles, vendors, and refund balances, it enables a single-query snapshot that would otherwise require multiple coordinated joins against OKC and OKL base entities. The view is documented as VALID and is exposed for customer extension and reporting use in both the 12.1.1 and 12.2.2 code lines.

Underlying Base Objects

The view is defined over a combination of OKL and OKC objects, all referenced through the APPS schema:

• OKL_CURE_REFUNDS_ALL (accessed as a synonym) — the driving entity holding refund amount, balance, cure status, and the CRF.CURE_REFUND_ID surrogate key.
• OKC_K_HEADERS_V and OKL_K_HEADERS_V — contract header views supplying the contract number, short description, and the SCS_CODE discriminator for 'PROGRAM', 'LEASE', and 'LOAN'.
• OKC_K_PARTY_ROLES_V — used twice, once with RLE_CODE = 'LESSEE' for the customer name and once with RLE_CODE = 'OKL_VENDOR' for the vendor linkage.
• OKX_PARTIES_V and OKX_VENDORS_V — party and vendor master views resolving TCA identifiers (ID1/ID2) to human-readable names.
• FND_GLOBAL and OKC_UTIL — standard EBS and contract utility packages used for session context and internal key resolution.

Because several components are views rather than tables, the object is a non-materialized read-only construct that resolves at execution time.

Key Columns

• VENDOR_PROGRAM_ID — the program contract identifier (PROG.ID) that links the refund to a vendor program, and the column most commonly used to filter by program.
• CHR_ID / CONTRACT_NUMBER / CONTRACT_DESCRIPTION — identify the underlying lease or loan contract carrying the refund.
• REFUND_AMOUNT, TOTAL_REFUNDED, BALANCE — the refunded amount, amount already returned (AMOUNT − BALANCE), and the remaining outstanding balance.
• VENDOR_PROGRAM and VENDOR_ID — the program name and the vendor master identifier.
• CUSTOMER_NAME — the lessee party name resolved through OKC_K_PARTY_ROLES_V and OKX_PARTIES_V.
• CURE_REFUND_ID — the surrogate key of the cure refund record, used for drill-down.
• AMOUNT_RECEIVED, CHOICE, and SELECT_FLAG are additional columns returned by the view text for UI/report binding purposes.

Common Use Cases and Queries

Typical scenarios include vendor program refund reporting, aging of outstanding cure balances, and reconciliation of refunds against vendor records. Rows are constrained to CRF.STATUS in ('PENDING','PARTIAL_REFUND') with CRF.BALANCE > 0, so the view returns only open obligations.

Example query to list outstanding refunds for a specific program:

• SELECT contract_number, customer_name, refund_amount, total_refunded, balance FROM apps.okl_refund_uv WHERE vendor_program_id = :p_vendor_program_id ORDER BY contract_number;

Example query to aggregate exposure by program:

• SELECT vendor_program, customer_name, SUM(balance) FROM apps.okl_refund_uv GROUP BY vendor_program, customer_name;

Because the view filters on open status and positive balance, any query that also joins OKL_CURE_REFUNDS_ALL directly should apply consistent status predicates to avoid reconciliation discrepancies.