Results for “okl_cure_refund_headers_b”

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

Overview

OKL_CURE_REFUND_HEADERS_B is a core transactional table in the Oracle Lease and Finance Management (OKL) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores refunds made to a vendor for contracts that have been cured — that is, contracts where the lessee defaulted, the vendor honored a residual or recourse obligation, and the vendor subsequently reimbursed the lessor for the cured balance. The table holds refund requests grouped by currency and by vendor/contract combination, so a single header row represents a refund obligation at a summary level, while the individual contract-level details are carried in the associated detail table.

The object is owned by the OKL schema and is classified VALID in the ETRM data dictionary. With 43 documented columns and a primary key of CURE_REFUND_HEADER_ID, it functions as the parent header of a master-detail pair. The metadata carries no Data Vault classification for this object; heuristically, it behaves as a hub-like anchor for the refund business concept, with the currency, vendor site, and contract references acting as natural business keys. This classification should be treated as a modeling suggestion rather than an authoritative designation.

Key Information Stored

The table records the commercial and administrative attributes of each cure refund request. The most significant columns are:

• CURE_REFUND_HEADER_ID — the surrogate primary key (OKL_CURE_REFUND_HEADERS_B_PK), generated internally and used by all child records.
• REFUND_HEADER_NUMBER — the user-facing business document number; this is a documented business-key candidate (unique index OKL_CURE_REFUND_HEADERS_U2).
• REFUND_TYPE and REFUND_STATUS — classify the refund and track its lifecycle from creation through disbursement or closure.
• REFUND_DUE_DATE — the date on which the refund is expected from the vendor.
• CURRENCY_CODE — the currency in which the refund is denominated; refunds are grouped by currency.
• TOTAL_REFUND_DUE, NEGOTIATED_AMOUNT, RECEIVED_AMOUNT, OFFSET_AMOUNT, and DISBURSEMENT_AMOUNT — the monetary measures covering the amount owed, any negotiated settlement, amounts actually received, offsets applied, and amounts disbursed.
• VENDOR_SITE_ID — identifies the vendor site to which the refund relates.
• PAYMENT_METHOD and PAYMENT_TERM_ID — the expected settlement method and payment terms; PAYMENT_TERM_ID carries a foreign key to PN_PAYMENT_TERMS_ALL.
• VENDOR_CURE_DUE and VENDOR_SITE_CURE_DUE — amounts due at the vendor and vendor-site level.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the OAF/BC4J framework.
• The standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — plus the concurrent program columns PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE, and the 15 descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical reporting requirements include open refund exposure by vendor, aging of refunds past due, and reconciliation of refunds received against amounts owed. A basic exposure query joins the header to the detail table and filters on status:

• Refund aging: select REFUND_HEADER_NUMBER, VENDOR_SITE_ID, CURRENCY_CODE, TOTAL_REFUND_DUE, and REFUND_DUE_DATE, filtering on REFUND_STATUS to isolate outstanding items.
• Amount reconciliation: compare TOTAL_REFUND_DUE against RECEIVED_AMOUNT and OFFSET_AMOUNT to identify shortfalls or over-application.
• Currency exposure: group by CURRENCY_CODE and sum TOTAL_REFUND_DUE to support treasury forecasting.
• Vendor scorecards: aggregate refund volumes and negotiated amounts by VENDOR_SITE_ID to evaluate vendor cure performance.

Because the table is the parent of OKL_CURE_REFUNDS_ALL, nearly all practical queries join on CURE_REFUND_HEADER_ID so that contract-level refund detail can be reported alongside header totals.

Related Objects

• OKL_CURE_REFUNDS_ALL — the principal child table; joined via CURE_REFUND_HEADER_ID to obtain the contract-level refund lines that roll up to each header.
• PN_PAYMENT_TERMS_ALL — referenced through the PAYMENT_TERM_ID foreign key to resolve payment term names for the refund.
• OKL_CURE_REFUND_HEADERS_B_PK — the primary key constraint enforcing uniqueness of CURE_REFUND_HEADER_ID.
• OKL_CURE_REFUND_HEADERS_U1 and OKL_CURE_REFUND_HEADERS_U2 — unique indexes on CURE_REFUND_HEADER_ID and REFUND_HEADER_NUMBER respectively; U2 is the primary business-key candidate.
• PO_VENDORS and PO_VENDOR_SITES_ALL — the typical lookup targets for VENDOR_SITE_ID, providing vendor and site names for reporting.
• OKL_CURE_REFUND_HEADERS_TL-style reporting views and the OKL Cure Refund concurrent programs — the standard maintenance and extraction paths that read and write this table.

Together these objects form the cure refund sub-model within OKL, with OKL_CURE_REFUND_HEADERS_B acting as the document header driving all downstream refund accounting and disbursement activity.