Search Results qp_pte_segments




Overview
Explore in AI Chat

Overview

QP_PTE_SEGMENTS is a configuration and mapping table within the Oracle Advanced Pricing (QP) module. It stores the attribute mapping methods, attribute mapping levels, and related metadata for individual pricing attributes across all Pricing Transaction Entities (PTEs) to which those attributes are linked. In practical terms, the table defines how a qualifying attribute — sourced from a transactional context such as an order, a line, or a pricing request — is presented, sourced, and constrained when used by the pricing engine. It is therefore a foundational reference object for setting up attribute sourcing, value lists of values (LOVs), and limit enforcement in Advanced Pricing.

From a Data Vault modeling perspective, the FK-derived heuristic classification for this table is standalone, meaning it does not exhibit the hub-and-link pattern typical of a transactional or master-data table. It is best treated as a reference or configuration satellite whose lifetime is governed by setup and development activities rather than by day-to-day transaction flow. The single documented foreign key (SEGMENT_ID referencing CSF_TDS_SEGMENTS) indicates that each row is anchored to a segment definition maintained in the shared segment repository used across Oracle's pricing and related configuration products.

Key Information Stored

The table contains 37 documented columns in the ETRM 12.2.2 schema. The most operationally significant are summarized below.

  • SEGMENT_PTE_ID — Surrogate primary key and the leading column of the unique index QP_PTE_SEGMENTS_U1. It uniquely identifies each mapping between a segment and a PTE.
  • SEGMENT_ID — Foreign key to CSF_TDS_SEGMENTS; identifies the priced attribute or segment being configured.
  • PTE_CODE — The Pricing Transaction Entity code that the segment is mapped to (for example, ORDER, LINE, or PRICING_REQUEST). Forms part of the QP_PTE_SEGMENTS_U2 business-key unique index along with SEGMENT_ID.
  • SEGMENT_LEVEL — Indicates the level at which the attribute is resolved (header versus line, for example), which affects pricing evaluation scope.
  • SOURCING_ENABLED — Flag indicating whether attribute sourcing is active for this segment/PTE combination.
  • SEEDED_SOURCING_METHOD and USER_SOURCING_METHOD — Identify the shipped versus customer-defined sourcing method used to derive the attribute value.
  • SOURCING_STATUS — Tracks the current state of sourcing configuration (for example, complete, incomplete, or error).
  • LOV_ENABLED — Indicates whether the attribute is exposed as a list of values for downstream selection.
  • LIMITS_ENABLED — Indicates whether value limits or restrictions are applied to the attribute.
  • USED_IN_SETUP and USED_IN_SEARCH — Usage flags controlling whether the segment/PTE mapping is referenced during setup screens and search functionality.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield context and attribute columns reserved for customer extensions.
  • ZD_EDITION_NAME — Editioning column present in 12.2.x; participates in both unique indexes (QP_PTE_SEGMENTS_U1 and QP_PTE_SEGMENTS_U2) and underpins edition-based redefinition.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses of this table include troubleshooting attribute sourcing failures, auditing which PTEs a given segment is mapped to, and generating setup reports for pricing configuration reviews. A representative join to the shared segment repository is:

  • SELECT s.segment_pte_id, s.segment_id, s.pte_code, s.segment_level, s.sourcing_status, c.segment_name FROM qp.qp_pte_segments s JOIN csf.csf_tds_segments c ON s.segment_id = c.segment_id WHERE s.pte_code = 'ORDER';
  • To identify segments with sourcing enabled but incomplete status: SELECT segment_id, pte_code FROM qp.qp_pte_segments WHERE sourcing_enabled = 'Y' AND sourcing_status <> 'COMPLETE';
  • To report all PTEs linked to a particular attribute, join on SEGMENT_ID and group by PTE_CODE.
  • For edition-aware queries in 12.2.x, always filter or join on ZD_EDITION_NAME to avoid duplicating rows across editions.

Related Objects

  • CSF_TDS_SEGMENTS — Referenced by the documented foreign key QP_PTE_SEGMENTS.SEGMENT_ID; the master source of segment definitions.
  • QP_PTE_SEGMENTS_U1 and QP_PTE_SEGMENTS_U2 — Unique indexes enforcing the surrogate key and the SEGMENT_ID/PTE_CODE business key.
  • QP_PRICING_ATTRIBUTES — Consumes segment-to-PTE mappings to drive pricing attribute behavior.
  • QP_SOURCING — Sourcing rules that depend on SOURCING_ENABLED and sourcing method configuration stored here.
  • QP_ATTR_SOURCING — Attribute sourcing definitions linked to segment/PTE combinations.
  • QP_QUALIFIERS — Qualifier definitions that reference pricing attributes mapped through this table.
  • QP_LIST_HEADERS and QP_LIST_LINES — Price list structures whose qualifiers ultimately resolve to segments configured here.
  • OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL — Transactional sources whose attributes are mapped via PTE_CODE entries such as ORDER and LINE.

Because the table is flagged standalone and edition-enabled, DBAs should include ZD_EDITION_NAME in any diagnostic script and treat the object as configuration data protected by standard setup privileges rather than transactional data subject to high-volume DML.