Results for “partial_refund”

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

Overview

APPS.OKL_REFUND_UV is a reporting view within the Oracle E-Business Suite (EBS) Enterprise Contracts / Oracle Lease and Finance Management (OKL) module. It consolidates vendor refund information tied to lease and loan contracts, exposing outstanding and partially refunded amounts alongside associated program, contract, and customer identifiers. Its primary role is to support operational and financial reporting on refund activity, particularly refunds administered by vendors under a vendor program. The view is defined in the APPS schema and would typically be queried through an Oracle Forms-based refunds screen, a concurrent program, an OAF page, or a custom report. Because it references multi-org and security-aware objects, its behavior is influenced by the runtime environment (for example, FND_GLOBAL) and OKC_UTIL utility routines.

Underlying Base Objects

The view is composed of several documented base objects:

• OKL_CURE_REFUNDS_ALL (SYNONYM) — the central refunds entity (CRF) that stores refund amount and balance per refund record; drives the projection and the status filter.
• OKC_K_HEADERS_V (VIEW) — contract header information, used twice: once as the lease/loan contract (CHR) and once as the parent program (PROG).
• OKL_K_HEADERS_V (VIEW) — the OKL lease header, joined to CHR to resolve the parent program through KHR_ID.
• OKC_K_PARTY_ROLES_V (VIEW) — contract party roles, used twice: RLE for the LESSEE (customer) and VLE for the OKL_VENDOR role.
• OKX_PARTIES_V (VIEW) — party master information supplying the customer name.
• OKX_VENDORS_V (VIEW) — vendor master supplying the vendor identifier (ID1).
• FND_GLOBAL (PACKAGE) and OKC_UTIL (PACKAGE) — referenced for session/context and utility resolution within the OKC framework.

The joins establish that a refund (CRF) is associated with a contract (CHR) whose SCS_CODE is LEASE or LOAN, and that contract's parent is a PROGRAM (PROG.SCS_CODE = 'PROGRAM'). The contract's LESSEE role supplies the customer, and the parent program's OKL_VENDOR role supplies the vendor.

Key Columns

• VENDOR_PROGRAM_ID / VENDOR_PROGRAM — identifier and description of the parent program managing the vendor relationship.
• CHR_ID / CONTRACT_NUMBER / CONTRACT_DESCRIPTION — the lease or loan contract on which the refund is recorded.
• CUSTOMER_NAME — name of the lessee party attached to the contract.
• REFUND_AMOUNT — the total refund amount established for the refund record.
• TOTAL_REFUNDED — computed as REFUND_AMOUNT minus BALANCE, representing the cumulative amount already refunded.
• BALANCE — the remaining unrecovered refund amount; the view only returns rows where BALANCE > 0.
• CURE_REFUND_ID — unique identifier of the underlying refund record in OKL_CURE_REFUNDS_ALL.
• VENDOR_ID — vendor identifier (OKX_VENDORS_V.ID1) associated with the program.

Filtering enforces CRF.STATUS in ('PENDING','PARTIAL_REFUND'), which is the semantic anchor for the "partial_refund" search context: rows represent refunds that are still open and, when status is PARTIAL_REFUND, only partially settled.

Common Use Cases and Queries

Reporting on open and partially refunded balances, reconciling vendor refunds against contracts, and driving follow-up actions are the primary scenarios. Typical queries filter by program, contract, or vendor. For example:

• List all partial refunds for a program: SELECT CONTRACT_NUMBER, CUSTOMER_NAME, REFUND_AMOUNT, TOTAL_REFUNDED, BALANCE FROM APPS.OKL_REFUND_UV WHERE VENDOR_PROGRAM_ID = :p_program_id;
• Identify outstanding balances by contract: SELECT CHR_ID, CONTRACT_NUMBER, BALANCE FROM APPS.OKL_REFUND_UV WHERE BALANCE > 0 ORDER BY BALANCE DESC;
• Retrieve vendor-specific refunds: SELECT CONTRACT_NUMBER, VENDOR_ID, TOTAL_REFUNDED FROM APPS.OKL_REFUND_UV WHERE VENDOR_ID = :p_vendor_id;
• Summarize total refunded per program: SELECT VENDOR_PROGRAM, SUM(TOTAL_REFUNDED) FROM APPS.OKL_REFUND_UV GROUP BY VENDOR_PROGRAM;

Because the view only surfaces pending and partial refunds with a positive balance, it is well suited to dashboards and exception reports that monitor refunds not yet fully recovered.