Search Results qp_segments_b_u3

Overview

QP.QP_SEGMENTS_B is a core Oracle Advanced Pricing reference table that stores the attribute definitions — also called pricing segments — used within every pricing context in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Each row describes a single attribute that can be qualified or priced against, such as an item, customer, order type, or freight charge characteristic. The table is a child of QP_PRC_CONTEXTS_B; every attribute belongs to one and only one context. Price lists, modifiers, qualifiers, and freight and special charge setups all depend on these definitions to determine which columns are available for rule evaluation.

From a Data Vault modeling perspective, the heuristic classification returned for this object is standalone. It can be treated as a reference or lookup hub-style entity rather than a transactional satellite, since it holds configuration metadata rather than event or transaction history. Note that in 12.2.2 the table is edition-enabled, as evidenced by the ZD_EDITION_NAME column that participates in all three unique indexes.

Key Information Stored

The physical schema documents 40 columns. The most significant are:

• SEGMENT_ID — system-generated unique identifier and the surrogate primary key, driven by the unique index QP_SEGMENTS_B_U1 (SEGMENT_ID, ZD_EDITION_NAME).
• SEGMENT_CODE — user-entered attribute code, unique per context via QP_SEGMENTS_B_U2 (SEGMENT_CODE, PRC_CONTEXT_ID, ZD_EDITION_NAME).
• PRC_CONTEXT_ID — foreign key reference to QP_PRC_CONTEXTS_B, identifying the owning pricing context.
• SEGMENT_MAPPING_COLUMN — maps the attribute to its attribute_code in AK_ATTRIBUTES; the third business key, QP_SEGMENTS_B_U3, enforces uniqueness on SEGMENT_MAPPING_COLUMN with PRC_CONTEXT_ID and ZD_EDITION_NAME.
• AVAILABILITY_IN_BASIC — flags whether the attribute is available in Basic and Advanced Pricing ('Y'), Advanced Pricing only ('N'), or Basic Pricing with Freight and special charges ('F').
• SEEDED_FLAG — indicates whether the attribute is Oracle-seeded or customer-defined.
• APPLICATION_ID — the application that created the attribute.
• SEEDED_PRECEDENCE and USER_PRECEDENCE — control display and evaluation order of the attribute.
• REQUIRED_FLAG and PARTY_HIERARCHY_ENABLED_FLAG — control mandatory entry and customer hierarchy qualification.
• CONTEXT, SEEDED_VALUESET_ID, and USER_VALUESET_ID — support list-of-values and validation behavior.
• LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Implementers query this table to enumerate the attributes available in a given pricing context, to troubleshoot missing qualifiers, or to audit seeded versus custom attributes. A typical lookup joins to the parent context table:

SELECT s.segment_id, s.segment_code, s.availability_in_basic
FROM qp.qp_segments_b s, qp.qp_prc_contexts_b c
WHERE s.prc_context_id = c.prc_context_id
AND c.context_code = :context_code
AND s.seeded_flag = 'Y';

Reporting scenarios include identifying all attributes mapped to a specific AK_ATTRIBUTES column, comparing seeded and user precedence values to resolve display ordering, and validating whether an attribute is restricted to Advanced Pricing. Data conversion and patch verification exercises frequently compare SEGMENT_CODE values across environments.

Related Objects

• QP.QP_PRC_CONTEXTS_B — parent table; joined on PRC_CONTEXT_ID, enforcing the one-context-per-attribute rule.
• CSF_TDS_SEGMENTS — referenced by the foreign key on SEGMENT_ID, linking pricing segments to the underlying attribute metadata layer.
• AK_ATTRIBUTES — source of the mapping target for SEGMENT_MAPPING_COLUMN.
• QP_QUALIFIERS and QP_MODIFIERS — consume segment definitions when building pricing and qualifier rules.
• QP_PRICE_LIST_LINES — relies on segment attributes for price list qualification and calculation.
• FND_APPLICATION_VL — resolves APPLICATION_ID to application names in reporting queries.