Results for “percentage_of_total_cost”

38 results




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

Overview

OKL_QUICK_QUOTE_LINES_V is a non-key-preserved database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product family, Oracle Lease and Finance Management (OLFM). The view exposes the union of attributes stored in the quick quote line base table and its translation table, providing a single logical source for quick quote line data across both transactional and multilingual reporting requirements.

Within the ETRM object repository the view is recorded as VALID and is catalogued as the reporting and integration interface for OKL_QUICK_QUOTE_LINES_B and OKL_QUICK_QUOTE_LINES_TL. Its principal role is to shield downstream consumers — Oracle Reports, OAF-based OLFM quick quote pages, custom PL/SQL, and outbound interface programs — from the physical join that must be performed between the base entity table and the translation table on the ID column filtered by the user's session language.

Underlying Base Objects

The view is defined over two synonymous references within the APPS schema:

The join implemented in the view text is QQL.ID = QQLT.ID AND QQLT.LANGUAGE = USERENV('LANG'). This inner join restricts the result set to translations existing for the current runtime language, as determined by the USERENV session context. ROWID from the base table is aliased as ROW_ID to provide a row identifier usable by Oracle Forms or OAF.

Key Columns

  • ROW_ID — the base table ROWID; a physical row locator used by client-side row identification, not a stable business key.
  • ID — the surrogate primary key of the quick quote line, used for join, update, and lock behaviour.
  • OBJECT_VERSION_NUMBER — optimistic locking token maintained by the OLFM framework.
  • QUICK_QUOTE_ID — foreign key to the parent quick quote header, establishing line-to-quote ownership.
  • TYPE and BASIS — classify the line and define the calculation basis applied to it.
  • VALUE — the primary numeric or textual value assigned to the line.
  • END_OF_TERM_VALUE_DEFAULT — the column most frequently targeted by searches for end_of_term_value_default. It stores the default end-of-term (residual) value that is proposed when a quick quote line is created or defaulted, as distinct from the calculated or negotiated END_OF_TERM_VALUE column.
  • END_OF_TERM_VALUE — the effective end-of-term value ultimately carried on the line.
  • PERCENTAGE_OF_TOTAL_COST — the proportion of total cost allocated to the line, typically used when BASIS is a percentage-driven basis.
  • ITEM_CATEGORY_ID and ITEM_CATEGORY_SET_ID — identify the item category used for pricing or eligibility logic.
  • LEASE_RATE_FACTOR — the rate factor applied during lease calculation.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield context and segments.
  • SHORT_DESCRIPTION, DESCRIPTION, COMMENTS — translated descriptive fields sourced from the TL table.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The view is typically queried to present quick quote lines in the session language while preserving access to ETRM defaulting attributes such as END_OF_TERM_VALUE_DEFAULT. A representative query retrieving the default and effective residual values for a quick quote is:

  • SELECT qql.quick_quote_id, qql.id, qql.type, qql.basis, qql.value, qql.end_of_term_value_default, qql.end_of_term_value, qql.percentage_of_total_cost FROM okl_quick_quote_lines_v qql WHERE qql.quick_quote_id = :p_quick_quote_id ORDER BY qql.id;
  • Reporting on END_OF_TERM_VALUE_DEFAULT versus END_OF_TERM_VALUE to detect lines where the negotiated residual diverges from the defaulted residual.
  • Aggregating PERCENTAGE_OF_TOTAL_COST by ITEM_CATEGORY_ID to validate that allocation percentages are complete.
  • Joining to OKL_QUICK_QUOTE_HEADERS to expose translated line descriptions alongside quote header information for outbound interfaces.

Because the view is a two-table inner join, consumers must remember that rows without a translation in the session language will not be returned. Queries intended for data migration or audit purposes should therefore consider the base table directly when language coverage may be incomplete.