Results for “floor_price”

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

Overview

OKL_AM_REPURCHASE_ASSET_HDR_UV is an APPS-owned database view in the Oracle Lease and Finance Management (OKL) module, delivered as part of Oracle E-Business Suite 12.1.1 and 12.2.2. The view consolidates repurchase agreement information for leased assets, joining quote, contract, and asset-return data into a single reporting structure. Its primary role is to expose the relationship between a lease quote, the underlying contract header, the leased asset, and the associated repurchase agreement — including whether repurchase rights apply and at what floor price. The "UV" suffix denotes a user-facing view, typically used in Oracle Forms-based inquiry screens, concurrent extract programs, and custom reporting or integration layers that need a flattened, denormalized view of repurchase asset data.

Underlying Base Objects

The view is defined over several OKC and OKL objects. OKL_TRX_QUOTES_V supplies the quote header (quote number, effective dates, approval and acceptance flags). OKC_K_HEADERS_B provides the contract header identified by contract number, end date, and internal header ID (CHR_ID). OKC_K_LINES_V supplies the contract line identifying the leased asset (KLE), including asset number and description. OKL_ASSET_RETURNS_V supplies the repurchase agreement attributes — the ART_ID, repurchase agreement indicator, and floor price. FND_LOOKUPS decodes the quote status code, OKC_STATUSES_V resolves the line status code to a meaningful status, and OKL_AM_UTIL_PVT.GET_PROGRAM_PARTNER derives the program partner name from the contract header ID. The join links quote to asset-return via the outer-joined ART_ID, contract header to contract line, and asset-return to contract line via KLE_ID.

Key Columns

• QUOTE_ID / QUOTE_NUMBER — Identifies the lease quote record.
• DATE_EFFECTIVE_FROM / DATE_EFFECTIVE_TO — Effective date range of the quote.
• APPROVED_YN / ACCEPTED_YN — Quote workflow status flags.
• CONTRACT_NUMBER / CHR_ID / END_DATE — Contract header identity and termination date.
• ASSET_NUMBER / ASSET_DESCRIPTION / KLE_ID — The leased asset and its contract line identifier.
• ART_ID — The asset-return (repurchase agreement) identifier; this is the key the user searched for. It links the repurchase agreement record to the quote and asset.
• REPURCHASE_AGMT_YN / FLOOR_PRICE — Whether a repurchase agreement exists and the guaranteed floor price.
• STATUS — Decoded quote status from FND_LOOKUPS.
• PROGRAM_PARTNER_NAME — Derived via OKL_AM_UTIL_PVT.
• LINE_STS_CODE / LINE_STATUS — Contract line status code and meaning.
• ORG_ID — Multi-org operating unit identifier.

Common Use Cases and Queries

The view is typically queried to report repurchase exposure by asset or contract, to reconcile quote-to-contract repurchase terms, and to drive downstream integration extracts. Because ART_ID is a central join key, it is frequently used as a filter or lookup anchor.

SELECT quote_number,
       contract_number,
       asset_number,
       art_id,
       repurchase_agmt_yn,
       floor_price,
       line_status
  FROM apps.okl_am_repurchase_asset_hdr_uv
 WHERE org_id = :p_org_id
   AND repurchase_agmt_yn = 'Y';

To locate the repurchase record for a specific asset, filter by ART_ID or ASSET_NUMBER. To review quote status distribution for repurchase-enabled assets, group by STATUS and LINE_STATUS. Because the view references FND_GLOBAL, FND_LOOKUPS, and OKL_AM_UTIL_PVT, it should be queried with the correct application context established so that org-level security and lookup decoding resolve correctly. In 12.1.1 and 12.2.2 the view remains VALID and is safe for custom reporting, though direct dependencies on underlying OKL views mean it should be re-validated after patching the OKL or OKC modules.