Results for “res_solve_rent”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view APPS.OKL_AM_CREATE_RES_QUOTE_UV is an Oracle Lease and Finance Management (OKL) construct used within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It exposes a unified, denomination-normalized result set designed to feed the "Create Residual Quote" workflow in the asset management module. The _UV suffix denotes a "user view" convention: it is not a physical table but a query layer that presents columns in a shape expected by an OA Framework page, a concurrent program, or an API call.
The name is significant: CREATE_RES_QUOTE refers to the residual value quote creation process, and the view supplies the contract header data alongside a fixed quote-type reference. Its role is primarily as a source for LOV (list of values) and downstream programmatic population rather than as a general reporting view. In practice, OKL_AM_CREATE_RES_QUOTE_UV acts as the entry-point dataset from which a residual quote header is seeded.
Underlying Base Objects
The documented metadata identifies three referenced base objects: OKC_K_HEADERS_B (accessed via a synonym), FND_LOOKUPS (view), and FND_GLOBAL (package). The view text confirms this, selecting from OKC_K_HEADERS_B OKHFV cross-joined with FND_LOOKUPS FND, filtered by a hard-coded lookup pair:
FND.LOOKUP_CODE = 'RES_SOLVE_RENT'FND.LOOKUP_TYPE = 'OKL_QUOTE_TYPE'
Because the filter is static, the view effectively returns a single row per contract header, decorated with a constant quote-type code and meaning. The dependency on FND_GLOBAL implies that ORG_ID or user context may be applied in the underlying form logic rather than in the view SQL itself, since multi-org security is typically enforced through FND_GLOBAL.ORG_ID within the calling page or a secured synonym.
Key Columns
The projected column list is deliberately split into "live" values drawn from the contract header and placeholder NULL columns reserved for the quote creation routine:
CONTRACT_NUMBER,START_DATE,END_DATE— identification and term window of the lease contract, sourced fromOKC_K_HEADERS_B.CONTRACT_ID(aliased fromOKHFV.ID) — the primary key linking to the contract header.QTP_CODEandQTP_MEANING— the quote-type lookup code and its description, constant here.POP_CODE_END— a NULL placeholder for the "period of performance code end" value supplied by the caller (this is the column referenced by the search term).QRS_CODE,COMMENTS,PURCHASE_AMOUNT,PURCHASE_FORMULA,PURCHASE_FORMULA_ID,PURCHASE_PERCENT,TERM,RENT_AMT— all NULL placeholders awaiting input.
Common Use Cases and Queries
This view is typically queried by form logic that pre-populates a residual quote block with contract context. A representative query follows:
- Retrieve contract identifiers and term dates for a residual quote:
SELECT contract_number, contract_id, start_date, end_date, qtp_code, pop_code_end FROM apps.okl_am_create_res_quote_uv; - Filter to a specific contract by number or ID to drive a residual quote creation page.
- Join to
OKC_K_HEADERS_BorOKL_QUOTE_HEADERSdownstream to compare the placeholder values once a quote is committed.
Because POP_CODE_END and the other placeholder columns always return NULL from the view, any logic depending on them must supply values at runtime. This confirms the view's function as a scaffolding layer for residual quote creation rather than a persistent reporting source.