Search Results qp_pte_segments_u1




Overview
Explore in AI Chat

Overview

The QP.QP_PTE_SEGMENTS table is a core configuration table within the Oracle Advanced Pricing module (schema QP). It stores the attribute mapping methods, attribute mapping levels, and related control information that govern how a given pricing attribute (stored in QP_SEGMENTS_B) is linked to one or more Pricing Transaction Entities (PTEs). A Pricing Transaction Entity represents the source document context in which pricing logic executes — for example an order, a line, a price list, or a return. Attributes become available for use in pricing setups only after they have been linked to a PTE through a record in this table. In Oracle EBS 12.1.1 and 12.2.2 the table is owned by QP and resides in the APPS_TS_TX_DATA tablespace.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a standalone link table: SEGMENT_PTE_ID is a system-generated surrogate key that uniquely identifies each PTE-to-attribute association, while the real business relationship is expressed by the combination of SEGMENT_ID and PTE_CODE. This classification is offered only as a heuristic suggestion derived from the documented key structure.

Key Information Stored

The table is documented with 37 columns in ETRM 12.2.2. The most operationally significant columns are:

  • SEGMENT_PTE_ID — system-generated unique identifier; the surrogate primary key, enforced by unique index QP_PTE_SEGMENTS_U1.
  • SEGMENT_ID — foreign key reference to QP_SEGMENTS_B.SEGMENT_ID, tying the row to a specific pricing attribute.
  • PTE_CODE — the Pricing Transaction Entity to which the attribute is linked (VARCHAR2(30)).
  • SEGMENT_LEVEL — indicates the level of the PTE-attribute link; valid values are ORDER, LINE, or BOTH.
  • SOURCING_ENABLED — indicates whether the link is intended to be attribute-sourced by the Build Sourcing Program. Only links with mapping method ATTRIBUTE MAPPING can be enabled.
  • SEEDED_SOURCING_METHOD — the original (seeded) mapping method, preserved even if changed by the user; valid values are ATTRIBUTE MAPPING, CUSTOM SOURCED, or USER ENTERED.
  • USER_SOURCING_METHOD — the current mapping method after any user modification.
  • SOURCING_STATUS — the attribute mapping status of the link.
  • LOV_ENABLED and LIMITS_ENABLED — flags controlling list-of-values and limit behaviors for the mapped attribute.
  • CONTEXT — the descriptive flexfield context for the mapping record.
  • ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield columns for extensible setup data.
  • USED_IN_SETUP and USED_IN_SEARCH — usage flags indicating whether the link participates in pricing setup and search activity.
  • Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
  • ZD_EDITION_NAME — editioning column supporting the 12.2 online patching / edition-based redefinition model; it forms part of both unique business-key indexes.

The documented unique indexes are QP_PTE_SEGMENTS_U1 (SEGMENT_PTE_ID, ZD_EDITION_NAME) and QP_PTE_SEGMENTS_U2 (SEGMENT_ID, PTE_CODE, ZD_EDITION_NAME), making SEGMENT_ID + PTE_CODE the primary business-key candidate. Both indexes reside in APPS_TS_TX_IDX.

Common Use Cases and Queries

The table is most commonly queried when diagnosing why a pricing attribute is not available on a given transaction entity, or when reviewing how attribute sourcing is configured. A typical diagnostic query joins the PTE-attribute link to the attribute definition:

  • Identify all PTEs mapped to a particular attribute: SELECT pte_code, segment_level, sourcing_enabled, user_sourcing_method FROM qp_pte_segments WHERE segment_id = :segment_id;
  • Find attributes linked to a specific PTE and level: SELECT segment_id, segment_level FROM qp_pte_segments WHERE pte_code = :pte_code AND segment_level IN ('ORDER','LINE','BOTH');
  • Audit sourcing changes by comparing seeded versus current methods: SELECT segment_pte_id, seeded_sourcing_method, user_sourcing_method FROM qp_pte_segments WHERE seeded_sourcing_method <> user_sourcing_method;
  • Locate attributes eligible for Build Sourcing: SELECT segment_id FROM qp_pte_segments WHERE sourcing_enabled = 'Y' AND user_sourcing_method = 'ATTRIBUTE MAPPING';
  • Reporting on setup usage: join USED_IN_SETUP and USED_IN_SEARCH flags to determine which PTE-attribute links are actively referenced.

These queries are frequently combined with QP_SEGMENTS_B (to resolve the attribute name) and QP_PTE_ATTR_MAPPING or PTE-related views to present a full picture of pricing attribute configuration.

Related Objects

  • QP.QP_SEGMENTS_B — the primary referenced table; join on QP_PTE_SEGMENTS.SEGMENT_ID = QP_SEGMENTS_B.SEGMENT_ID to resolve attribute details.
  • QP.QP_SEGMENTS_TL — provides translated names for the segment (attribute).
  • CSF_TDS_SEGMENTS — appears in the documented foreign-key relationship referencing SEGMENT_ID.
  • QP.QP_PTE_ATTR_MAPPING — holds the attribute mapping details that depend on the link created here.
  • QP.QP_PRICING_ATTRS_* and PTE metadata tables — consume PTE_CODE and SEGMENT_LEVEL to drive pricing execution.
  • QP.QP_PTE_SEGMENTS_VIEW and related QP views — expose the link data for forms and reports.
  • Oracle Advanced Pricing concurrent programs such as Build Sourcing — read SOURCING_ENABLED, SOURCING_STATUS, and the sourcing-method columns to populate sourcing data.

In Oracle EBS 12.2.2, the presence of ZD_EDITION_NAME in the unique keys reflects the edition-based redefinition architecture introduced with online patching; the same logical structure is present in 12.1.1 without editioning considerations.