Results for “repurchase_amount”

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

Overview

OKL_RECONCILE_UV is a reporting view in the APPS schema of Oracle E-Business Suite, owned by the OKL – Lease and Finance Management product. It is a consolidated reconciliation view that exposes cure-related and repurchase-related data for lease and finance contracts, typically in the context of vendor program agreements and structured funding arrangements. Its primary role is to present a unified, denormalized result set that combines display-oriented reconciliation data with cure-tracking information, allowing reporting and integration consumers to query a single object rather than join multiple intermediate views.

The view is classified as VALID and is documented for both EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it stores no data of its own; it derives its rows at query time from its referenced objects.

Underlying Base Objects

The documented view text defines OKL_RECONCILE_UV as a join between two intermediate views, with an outer join on the CHR_ID column:

• OKL_RECONCILE_DISPLAY_UV (V1) – supplies vendor program, contract, eligible cure, claimed cure, repurchase, and report-related columns.
• OKL_RECONCILE_CURES_UV (V2) – supplies cures-in-possession, amount received, and the CURED_FLAG column.

The join predicate is V1.CHR_ID = V2.CHR_ID(+), making OKL_RECONCILE_DISPLAY_UV the driving (outer) source and OKL_RECONCILE_CURES_UV the optional (inner) source. Consequently, every row from V1 is returned, with cure attributes populated only where a matching CHR_ID exists in V2. The documented dependency list also references the FND_GLOBAL and OKC_UTIL packages, which are typically invoked inside the underlying display or cures views to resolve operating unit, user, or contract utility context.

Key Columns

The view exposes fifteen columns. The most significant include:

• VENDOR_PROGRAM – identifier or name of the vendor program under which the contract is reconciled.
• NAME – party or contract-related name associated with the record.
• CONTRACT_NUMBER – the lease/finance contract identifier.
• ELIGIBLE_CURE_AMOUNT and CLAIMED_CURE_AMOUNT – the amount eligible to be cured versus the amount actually claimed.
• CURES_IN_POSSESSION – cure amounts held or received but not yet applied.
• CHOICE – a positionally placed NULL in the select list, retained for interface or report layout compatibility.
• AMOUNT_RECEIVED – cash or value received against cures.
• REPURCHASE_AMOUNT – amount associated with repurchase obligations.
• CURED_FLAG – the flag indicating whether the cure condition has been satisfied for the record.
• REPORT_DATE, REPORT_NUMBER, REPORT_ID – reconciliation reporting identifiers and dates.
• CHR_ID – the join key linking display and cure data.

Common Use Cases and Queries

This view is most often used for cure reconciliation reporting, vendor program monitoring, and downstream integration extracts. A typical query filtering on the cured_flag column follows:

• SELECT contract_number, vendor_program, eligible_cure_amount, claimed_cure_amount, cured_flag FROM apps.okl_reconcile_uv WHERE cured_flag = 'Y';
• SELECT report_number, report_date, SUM(amount_received), SUM(repurchase_amount) FROM apps.okl_reconcile_uv GROUP BY report_number, report_date;
• SELECT * FROM apps.okl_reconcile_uv WHERE chr_id = :chr_id;

Because CURED_FLAG originates in the inner-joined OKL_RECONCILE_CURES_UV, filtering on it implicitly restricts results to records with matching cure data; queries intended to include uncured or cure-less rows should apply NVL or filter with the outer-join semantics in mind.