Search Results qp_limit_attributes_u2

Overview

QP.QP_LIMIT_ATTRIBUTES is a transactional table within the Oracle Advanced Pricing (QP) schema that stores the individual attribute definitions used to describe the dimensions of a limit or balance. In Oracle E-Business Suite Release 12.1.1 and 12.2.2, limits and balances allow pricing administrators to constrain or cap the value of pricing adjustments, accruals, or discounts based on one or more qualifying dimensions. Each row in QP_LIMIT_ATTRIBUTES represents one such dimension — for example a customer, product, or pricing qualifier — and links back to its parent limit record through the LIMIT_ID foreign key.

The object is registered in FND Design Data as QP.QP_LIMIT_ATTRIBUTES, has an owner of QP, and resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. From a data modeling perspective, the FK relationship to QP.QP_LIMITS and the presence of a surrogate primary key (QP_LIMIT_ATTRIBUTES_PK on LIMIT_ATTRIBUTE_ID) suggest this object is satellite-leaning: it holds descriptive and qualifying detail that hangs off a parent limit hub. Analysts building a dimensional or Data Vault-style model around Advanced Pricing should consider treating QP_LIMIT_ATTRIBUTES as a satellite of QP_LIMITS, keyed by LIMIT_ATTRIBUTE_ID and dependent on LIMIT_ID.

Key Information Stored

The table's currency of use is defined by a small number of high-value columns. The surrogate primary key is LIMIT_ATTRIBUTE_ID, which uniquely identifies each attribute row and is backed by the unique index QP_LIMIT_ATTRIBUTES_U1. The business relationship to the parent limit is carried by LIMIT_ID, a foreign key referencing QP.QP_LIMITS and indexed through the nonunique index QP_LIMIT_ATTRIBUTES_N1.

• LIMIT_ATTRIBUTE_TYPE — classifies the attribute as a qualifier, product, or pricing attribute, driven by the lookup type LIMIT_ATTRIBUTE_TYPE.
• LIMIT_ATTRIBUTE_CONTEXT — identifies the descriptive flexfield context in the Qualifier or Pricing Attribute structure from which the dimension is drawn.
• LIMIT_ATTRIBUTE — names the specific flexfield segment that represents the limit dimension.
• LIMIT_ATTR_VALUE — holds the value assigned to that dimension; the literal value 'EACH' indicates the limit applies to every element in the dimension.
• LIMIT_ATTR_DATATYPE — denormalised from the descriptive flexfield segment, indicating the datatype of the attribute value.
• COMPARISON_OPERATOR_CODE — defines how the attribute is compared when evaluating the limit.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO columns capturing audit and user context.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program columns identifying the process that created or last modified the row.

Two important secondary indexes exist beyond the primary key: QP_LIMIT_ATTRIBUTES_N1 (LIMIT_ID) supports parent-to-child traversal, and the nonunique QP_LIMIT_ATTRIBUTES_U2 (LIMIT_ATTRIBUTE_CONTEXT, LIMIT_ATTRIBUTE) facilitates lookup of attribute definitions by context and segment.

Common Use Cases and Queries

The most common access pattern is retrieving all attributes belonging to a given limit. A typical query joins the parent limit to its attribute rows and reports the dimension, context, value, and comparison operator. For example:

• Reporting all dimensions configured for a specific limit: SELECT LIMIT_ATTRIBUTE_TYPE, LIMIT_ATTRIBUTE_CONTEXT, LIMIT_ATTRIBUTE, LIMIT_ATTR_VALUE, COMPARISON_OPERATOR_CODE FROM QP.QP_LIMIT_ATTRIBUTES WHERE LIMIT_ID = :p_limit_id;
• Finding where a particular dimension is used across limits: filter on LIMIT_ATTRIBUTE_CONTEXT and LIMIT_ATTRIBUTE, which are supported by QP_LIMIT_ATTRIBUTES_U2.
• Auditing attribute creation and change history using the WHO and concurrent program columns.
• Reconciling flexfield definitions with the denormalised LIMIT_ATTR_DATATYPE to detect drift between the pricing setup and the underlying DFF segment metadata.
• Building a dimensional extract for downstream analytics by pivoting rows on LIMIT_ATTRIBUTE_CONTEXT/LIMIT_ATTRIBUTE into separate columns per dimension.

Related Objects

The primary documented relationship is to the parent limit table, with additional dependencies implied by the descriptive flexfield and lookup metadata referenced in the columns.

• QP.QP_LIMITS — parent table; joined via QP_LIMIT_ATTRIBUTES.LIMIT_ID = QP_LIMITS.LIMIT_ID.
• QP.QP_LIMIT_ATTRIBUTES_PK — primary key constraint on LIMIT_ATTRIBUTE_ID.
• QP_LIMIT_ATTRIBUTES_U1 / _N1 / _U2 — supporting indexes on LIMIT_ATTRIBUTE_ID, LIMIT_ID, and (LIMIT_ATTRIBUTE_CONTEXT, LIMIT_ATTRIBUTE) respectively.
• FND Lookups (LIMIT_ATTRIBUTE_TYPE) — lookup type used to validate LIMIT_ATTRIBUTE_TYPE values.
• QP Descriptive Flexfield definitions — source of LIMIT_ATTRIBUTE_CONTEXT, LIMIT_ATTRIBUTE, and LIMIT_ATTR_DATATYPE.
• Advanced Pricing limits and balances APIs — application program interfaces that read and write these attribute rows when limits are defined or evaluated.