Results for “okl_am_create_res_quote_uv”

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

Overview

The view APPS.OKL_AM_CREATE_RES_QUOTE_UV is a database object within the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL). It functions as a read-only reporting and integration view, primarily designed to support the creation of residual value quotes. In the context of Oracle EBS 12.1.1 and 12.2.2, this view acts as a critical data source for the "Create Residual Quote" functionality, which is often invoked during lease origination or asset management processes. Its primary role is to present a structured, denormalized dataset that combines contract header information with specific system lookup values, providing a foundation for generating or displaying quote parameters. The view is owned by the APPS schema, ensuring it is accessible to standard EBS application responsibilities. Because it includes the _UV suffix, it is typically classified as a user-facing view intended for use by the Oracle Forms-based UI or external integration scripts that need to programmatically retrieve quote-related context. The view relies heavily on the FND_LOOKUPS table to hard-code a specific quote type (RES_SOLVE_RENT), thereby isolating a particular business scenario—residual solving based on rent—and presenting it in a standardized format for downstream consumption.

Underlying Base Objects

The metadata for this view, documented for ETRM 12.2.2, identifies three referenced base objects. Understanding these is essential to interpreting the view's output:

• OKC_K_HEADERS_B (SYNONYM): This is the core contract header table from the Oracle Contracts (OKC) module. It serves as the primary source for contract-level details, such as contract number, start date, and end date. The view joins this table to provide the foundational lease or contract context. The use of a synonym implies that the view accesses this table via a standard APPS synonym, which points to the underlying OKC base table.
• FND_LOOKUPS (VIEW): The view queries this standard Oracle Application Object Library (FND) view to retrieve lookup codes and their meanings. Specifically, the view filters for a lookup type of OKL_QUOTE_TYPE and a lookup code of RES_SOLVE_RENT. This filter ensures that only the specific residual solve rent quote type is returned, effectively pre-selecting a single business rule configuration.
• FND_GLOBAL (PACKAGE): While not directly referenced in the provided view text, the metadata lists this package. In EBS, FND_GLOBAL is frequently used in views to enforce security (e.g., ORG_ID or user-based access). Its presence suggests that the view may dynamically incorporate session-specific variables, though the excerpted SQL does not explicitly show it.

Key Columns

The view exposes a set of columns that are a mix of actual contract data, literal placeholders, and lookup-derived values. The most significant columns include:

• CONTRACT_NUMBER, START_DATE, END_DATE, CONTRACT_ID: These columns are sourced directly from OKC_K_HEADERS_B and provide the unique identifier and effective dates for the associated contract.
• QTP_CODE and QTP_MEANING: These are the only columns populated from the FND_LOOKUPS join. QTP_CODE will always be RES_SOLVE_RENT, and QTP_MEANING will be the corresponding description (e.g., "Residual Solve Rent"). They define the quote type.
• QRS_CODE, COMMENTS, POP_CODE_END, PURCHASE_AMOUNT, PURCHASE_FORMULA, PURCHASE_FORMULA_ID, PURCHASE_PERCENT, TERM, RENT_AMT: In the documented view text, these columns are explicitly set to NULL. This indicates that the view is a template or a partially implemented data source. The NULL placeholders likely represent fields that are either populated by a subsequent process, derived from other tables not included in this view definition, or are used as bind variables in a hosting form. The inclusion of QRS_CODE as a NULL column is notable; it is a key identifier that would typically be populated in a fully functional quote creation view.

Common Use Cases and Queries

Given that several columns are returned as NULL, this view is not a standalone reporting source for complete quotes. Instead, it is commonly used in two scenarios: as a query source for an Oracle Forms LOV (List of Values) or block, or as a starting point for a more complex query that joins to additional tables to populate the NULL fields. A typical query would be:

SELECT contract_number, contract_id, qtp_code, qtp_meaning, qrs_code
FROM   okl_am_create_res_quote_uv
WHERE  contract_number = :contract_num;

Because QRS_CODE is NULL in this view, a user searching for qrs_code would not find data here directly. However, this view is often the first step in a multi-part process; a developer might use its CONTRACT_ID to look up the actual quote details in a related table such as OKL_QUOTES or a transactional table not included in this view. The view is also useful for confirmation that a contract is eligible for the RES_SOLVE_RENT quote type, as it only returns rows for contracts that satisfy the internal join logic. In EBS 12.1.1 and 12.2.2, such views are frequently called by the Oracle Leasing Quote Creation page to pre-populate header information before the user enters the actual quote values.