Results for “okl_cure_rfnd_dtls_uv”

44 results




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

Overview

OKL_CURE_RFND_DTLS_UV is an APPS-owned database view within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. Its documented purpose is to present View by Vendor refunds — that is, a flattened, query-ready representation of cure refund activity organized around the vendor from whom amounts are received or to whom amounts are disbursed. In the ETRM 12.2.2 metadata the object is catalogued as a VIEW in the APPS schema with VALID status, meaning it is a supported, compiled read-only construct intended to be consumed by reports, concurrent programs, and integration extracts rather than written to directly.

The identifier "UV" conventionally denotes a user view — an interface layer that shields reporting and integration consumers from the underlying normalized tables. The view correlates a cure refund stage record with its refund header, refund line, originating contract, and the vendor master, and it also joins to FND_LOOKUPS to translate the internal refund status code into a user-facing meaning. This makes it a single source for vendor-oriented refund detail without the caller needing to reproduce the multi-table join.

Underlying Base Objects

The documented referenced base objects are:

  • FND_GLOBAL (PACKAGE) — supplies session context (for example, user and responsibility identifiers) used in the view's filtering logic.
  • FND_LOOKUPS (VIEW) — provides the lookup meaning for the refund status code.
  • OKC_K_HEADERS_ALL_B and OKC_K_HEADERS_B (SYNONYMS) — the contract header tables; the "_B" table supplies the contract number and currency, while the "_ALL_B" table is outer-joined to resolve the offset contract.
  • OKL_CURE_REFUND_STAGE (SYNONYM) — the staging record holding the received amount, vendor, contract reference, and status.
  • OKL_CURE_REFUND_HEADERS_B (SYNONYM) — the refund header, holding the refund header number, refund status, and vendor site.
  • OKL_CURE_REFUNDS_ALL and OKL_CURE_REFUNDS (SYNONYMS) — the refund lines, holding offset amount, offset contract, disbursement amount, and vendor site.
  • PO_VENDORS and PO_VENDOR_SITES_ALL / PO_VENDOR_SITES (VIEWS) — vendor name and formatted vendor address.

The view text is a UNION of at least two SELECT blocks sharing an identical column list, which allows stage-level refund rows to be combined with a second population of records. Join predicates link stage to refund line on CURE_REFUND_STAGE_ID, header to line on CURE_REFUND_HEADER_ID, stage to contract on CHR_ID, and vendor to vendor master on VENDOR_ID.

Key Columns

Common Use Cases and Queries

Typical uses include vendor refund reconciliation, cure refund reporting by contract, and extraction of received versus disbursed amounts for finance reconciliation. A representative query retrieves received amounts by vendor and status:

  • SELECT vendor_name, contract_number, received_amount, disbursement_amount, status FROM apps.okl_cure_rfnd_dtls_uv WHERE received_amount > 0;
  • SELECT contract_number, currency_code, SUM(received_amount) FROM apps.okl_cure_rfnd_dtls_uv GROUP BY contract_number, currency_code;
  • SELECT vendor_name, vendor_address, refund_header_number, offset_amount FROM apps.okl_cure_rfnd_dtls_uv WHERE refund_status = :status;

Because the view joins contract and vendor master data and translates lookup codes, it is suited to report data sources and interface extracts. As a view, it should be queried read-only; all maintenance occurs against the underlying OKL cure refund tables.