Search Results limit_attribute_context

Overview

QP_LIMIT_ATTRIBUTES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Advanced Pricing (QP). In EBS 12.1.1 and 12.2.2 the object carries a status of VALID and is classified as a VIEW, which means it exposes no storage of its own; it is a thin projection over the limit attribute data maintained by the pricing engine. The view presents the attribute-level detail of pricing limits — the individual conditions, qualifiers, and comparison values that must be satisfied for a price list limit, modifier limit, or promotion limit to take effect.

For users who search on limit_attribute_context, this view is the primary reference, because LIMIT_ATTRIBUTE_CONTEXT is one of its columns. The view therefore serves as the canonical read interface for interrogating which attribute context, attribute, and data type drive a given limit rule, without requiring direct access to the underlying transaction table.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: the synonym QP_LIMIT_ATTRIBUTES. The view text confirms this dependency directly, selecting all of its columns from QP_LIMIT_ATTRIBUTES, aliased in the definition as QPLAT:

SELECT ROWID ROW_ID, LIMIT_ATTRIBUTE_ID, LIMIT_ID, ... FROM QP_LIMIT_ATTRIBUTES QPLAT

Because the definition is a straight projection with no joins, filters, or aggregation, rows in the view correspond one-to-one with rows in the base table. The only transformation is the exposure of the physical ROWID as a synthetic column named ROW_ID. This design keeps the view inexpensive to query and makes it safe for concurrent reporting. The relationship to the base object is therefore one of simple inheritance: a limit header identifies a pricing limit, and each child row in QP_LIMIT_ATTRIBUTES_V describes one attribute condition attached to that limit through LIMIT_ID.

Key Columns

• ROW_ID — the underlying ROWID of the base table row, useful for identifying or de-duplicating records.
• LIMIT_ATTRIBUTE_ID — primary key of the limit attribute record.
• LIMIT_ID — foreign key linking the attribute back to its parent limit definition.
• LIMIT_ATTRIBUTE_TYPE — classifies the attribute condition being applied.
• LIMIT_ATTRIBUTE_CONTEXT — the context under which the attribute is qualified; the column most relevant to searches for limit_attribute_context.
• LIMIT_ATTRIBUTE — identifies the specific attribute used in the limit condition.
• LIMIT_ATTR_VALUE — the value that the attribute must match or be compared against.
• LIMIT_ATTR_DATATYPE — the data type of the attribute value (for example character, number, or date).
• COMPARISON_OPERATOR_CODE — the operator applied in the comparison, such as equals, greater than, or between.
• CONTEXT — the descriptive flexfield context associated with the record, generally paired with the LIMIT_ATTRIBUTE_CONTEXT value.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments carrying additional, installation-specific qualifier information.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID support standard EBS audit and concurrent program traceability.

Common Use Cases and Queries

The view is typically used to audit or report on the qualifiers attached to pricing limits, to troubleshoot why a limit is or is not firing, and to feed integration or extract processes.

Retrieve all attributes for a specific limit:

SELECT LIMIT_ATTRIBUTE_ID, LIMIT_ATTRIBUTE_CONTEXT, LIMIT_ATTRIBUTE, LIMIT_ATTR_VALUE, COMPARISON_OPERATOR_CODE FROM APPS.QP_LIMIT_ATTRIBUTES_V WHERE LIMIT_ID = :p_limit_id;

Find limits qualified by a particular attribute context:

SELECT LIMIT_ID, LIMIT_ATTRIBUTE, LIMIT_ATTR_VALUE FROM APPS.QP_LIMIT_ATTRIBUTES_V WHERE LIMIT_ATTRIBUTE_CONTEXT = :p_context;

List recently modified records for change auditing:

SELECT LIMIT_ATTRIBUTE_ID, LIMIT_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM APPS.QP_LIMIT_ATTRIBUTES_V WHERE LAST_UPDATE_DATE >= :p_from_date ORDER BY LAST_UPDATE_DATE DESC;

Because the view is read-only and unfiltered, it should be queried with predicates on LIMIT_ID or LIMIT_ATTRIBUTE_CONTEXT to avoid full scans against large pricing setups.