Results for “okl_cure_refund_headers_v”

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

Overview

OKL_CURE_REFUND_HEADERS_V is an APPS-owned database view within the Oracle Lease and Finance Management (OKL) product module. Its documented purpose is to store refunds made to a vendor for cured contracts, presenting refund requests grouped by currency and by vendor or contract. In the context of Oracle EBS 12.1.1 and 12.2.2, this view serves as the reporting and integration access point for cured-contract refund header data. Because the underlying storage is split across a base table and a translation table, the view performs the join that reconstitutes a single logical refund header record, making it convenient for concurrent programs, forms, and external integrations to query refund information without managing the multi-table structure directly. A user searching for "refund_type" will find that column exposed here as REFUND_TYPE, one of the primary classification attributes of a refund header.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through SYNONYM entries: OKL_CURE_REFUND_HEADERS_B, the base (non-translated) table, and OKL_CURE_REFUND_HEADERS_TL, the translation table. The join condition links the two on CURE_REFUND_HEADER_ID, matching the base table's primary key to the corresponding translation row. The base table (aliased CHDB) supplies nearly all functional, descriptive, and Who-column attributes, while the translation table (aliased CHDT) contributes the SFWT_FLAG and DESCRIPTION columns. This B/TL architecture follows Oracle's standard multilingual design, where language-dependent descriptive text is separated from language-independent transactional data. The view also carries ROW_ID derived from the base table ROWID and the standard object version number used for optimistic locking.

Key Columns

• CURE_REFUND_HEADER_ID — Primary identifier for the refund header; the join key between base and translation tables.
• REFUND_HEADER_NUMBER — Business-facing refund header number used for reference and lookup.
• REFUND_TYPE — Classifies the nature of the refund; central to filtering and categorization of cured-contract refunds.
• REFUND_DUE_DATE — Date on which the refund is due.
• CURRENCY_CODE — Currency of the refund; refunds are grouped by currency and vendor/contract.
• TOTAL_REFUND_DUE, DISBURSEMENT_AMOUNT, NEGOTIATED_AMOUNT, RECEIVED_AMOUNT, OFFSET_AMOUNT — Monetary measures tracking refund liability, disbursement, negotiated value, amounts received, and offsets.
• VENDOR_SITE_ID, VENDOR_CURE_DUE, VENDOR_SITE_CURE_DUE — Vendor and vendor-site context, including cure-due associations.
• REFUND_STATUS, PAYMENT_METHOD, PAYMENT_TERM_ID — Processing attributes controlling status and payment characteristics.
• DESCRIPTION, SFWT_FLAG — Translation-table attributes providing descriptive text and the SFWT (Seed/Function/Weather/Translation) flag.
• OBJECT_VERSION_NUMBER and the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — Concurrency control and audit lineage.
• ATTRIBUTE_CATEGORY through ATTRIBUTE1–15 — DFF (descriptive flexfield) columns available for client-specific extension.

Common Use Cases and Queries

Typical uses include reporting outstanding refunds due to vendors on cured contracts, feeding payment reconciliation, and driving integrations that need refund header details grouped by vendor and currency. Analysts frequently filter by REFUND_TYPE and REFUND_STATUS to isolate categories such as negotiated or offset refunds. A representative query follows:

SELECT r.refund_header_number, r.refund_type, r.currency_code,
  r.total_refund_due, r.received_amount, r.offset_amount,
  r.refund_status, r.vendor_site_id, r.refund_due_date
FROM apps.okl_cure_refund_headers_v r
WHERE r.refund_type = :p_refund_type
  AND r.refund_status = 'OPEN'
ORDER BY r.vendor_site_id, r.currency_code;

Because the view already joins the translation table, description text is directly available without an additional language lookup, simplifying both ad-hoc reporting and inbound/outbound interface development.