Search Results qp_limits_v

Overview

QP_LIMITS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Advanced Pricing (QP). It exposes the definition of pricing limits together with the association of each limit to the Promotion, Deal, or Modifier for which that limit is configured. In Oracle EBS 12.1.1 and 12.2.2 the object is registered as a VALID view, making it a supported read interface for the limits feature of Advanced Pricing.

The view is defined as a simple projection over the base table QP_LIMITS, exposing the complete column list rather than applying any filter, join, or aggregation. As a result, the view behaves as a synonym-like presentation layer: it is functionally equivalent to SELECT * FROM QP_LIMITS but is the object exposed for reporting, extracts, and integrations. The limit definition stored in this view governs the conditions under which a promotion, deal, or modifier is terminated or restricted — for example, limiting the total discount amount, the number of times a promotion is applied, or the quantity eligible for a promotion within an order. Because the view preserves the limit header context (LIST_HEADER_ID, LIST_LINE_ID, LIMIT_NUMBER) alongside the limit's control attributes, it supports both configuration auditing and runtime diagnostics.

Underlying Base Objects

ETRM metadata documents a single referenced base object for this view: the synonym QP_LIMITS, which resolves to the APPS.QP_LIMITS table. The view text confirms a direct, unfiltered selection from QP_LIMITS (aliased QPLMTS), with no joins to other tables and no WHERE clause. Consequently, QP_LIMITS_V inherits the row cardinality and column semantics of QP_LIMITS exactly; no rows are added, removed, or transformed. All DML is performed against QP_LIMITS by the pricing engine and the pricing setup forms; QP_LIMITS_V is read-only in practical use.

Key Columns

• LIMIT_ID — Primary identifier of the limit definition; the join key to any limit-related child records.
• LIST_HEADER_ID / LIST_LINE_ID — Identify the list (promotion, deal, or modifier) header and line to which the limit belongs, providing the Promotion/Deal/Modifier context described in the object description.
• LIMIT_NUMBER — Sequence number distinguishing multiple limits defined for the same list line.
• LIMIT_LEVEL_CODE — The level at which the limit is evaluated (for example, order or line level), determining the scope over which usage is accumulated.
• BASIS — The basis on which the limit is measured, such as amount or quantity.
• LIMIT_EXCEED_ACTION_CODE — The action taken when the limit is exceeded, such as flagging, holding, or disallowing the promotion.
• LIMIT_HOLD_FLAG — Indicates whether exceeding the limit places the transaction on hold.
• ORGANIZATION_FLAG — Indicates whether the limit is organization-specific.
• AMOUNT — The threshold value that defines the limit.
• MULTIVAL_ATTR1_TYPE, MULTIVAL_ATTRIBUTE1, MULTIVAL_ATTR1_CONTEXT, MULTIVAL_ATTR1_DATATYPE (and their ATTR2 counterparts) — Multivalue attribute qualification used to scope the limit to specific attribute-based qualifier sets.
• EACH_ATTR_EXISTS, NON_EACH_ATTR_COUNT, TOTAL_ATTR_COUNT — Denormalized counters describing the qualifier attributes associated with the limit.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — DFF-enabled context and descriptive flexfield columns available for customer-specific extensions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — Standard audit and concurrent program tracking columns.

Common Use Cases and Queries

The view is typically queried to report on promotion limits, to diagnose why a promotion was held or rejected, or to extract limit configuration for migration and integration. A query filtered on the limit level, for example, supports analyzing how many limits operate at order versus line level:

• SELECT limit_id, list_header_id, list_line_id, limit_level_code, basis, amount, limit_exceed_action_code FROM qp_limits_v WHERE limit_level_code = :level;
• SELECT limit_id, list_header_id, list_line_id, limit_number, basis, amount, limit_hold_flag FROM qp_limits_v WHERE list_header_id = :header_id ORDER BY list_line_id, limit_number;
• SELECT limit_exceed_action_code, limit_hold_flag, COUNT(*) FROM qp_limits_v GROUP BY limit_exceed_action_code, limit_hold_flag;
• SELECT limit_id, attribute1, attribute2, context FROM qp_limits_v WHERE context IS NOT NULL;

Because the view exposes the underlying table columns without modification, queries against it return the same results as equivalent queries against QP_LIMITS, and it can be used safely in custom reports, extracts, and BI Publisher data models within Oracle EBS 12.1.1 and 12.2.2.