Search Results qp_segments_b




Overview
Explore in AI Chat

Overview

QP_SEGMENTS_B is a core configuration table within the Oracle Advanced Pricing (QP) module. It stores the attribute (segment) definitions that make up pricing contexts in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Every pricing qualifier, modifier, and price list line operates within a pricing context, and each context is composed of one or more segments defined in this table. QP_SEGMENTS_B is a child of QP_PRC_CONTEXTS_B, meaning the segments it defines belong to a specific pricing context identified by PRC_CONTEXT_ID.

The table is owned by the QP schema, holds 40 documented columns, and is marked VALID in the ETRM 12.2.2 physical schema. Under the heuristic Data Vault classification mined from the foreign key structure, the table is modeled as standalone — that is, it does not participate in a hub/link/satellite parent-child chain beyond its reference to CSF_TDS_SEGMENTS. Treat this as a modeling suggestion only; in native EBS terms it is a transactional reference (lookup) table.

Because pricing contexts drive eligibility and applicability of pricing rules, QP_SEGMENTS_B effectively controls how the pricing engine filters and matches pricing data at runtime. Misconfigured segments lead to incorrect qualifier matching, making this table a frequent subject of troubleshooting and reporting queries.

Key Information Stored

Although 40 columns exist, the following are the most significant for querying and understanding the data:

Common Use Cases and Queries

Typical usage revolves around auditing context definitions, migrating configuration between environments, and diagnosing qualifier matching failures. A common join lists all segments belonging to each pricing context:

  • SELECT s.segment_code, s.segment_mapping_column, s.prc_context_id, s.availability_in_basic, s.required_flag FROM qp_segments_b s WHERE s.prc_context_id = :context_id;
  • Query segments by code and context for a given edition: SELECT * FROM qp_segments_b WHERE segment_code = :code AND prc_context_id = :ctx AND zd_edition_name = 'ORA$BASE';

Reporting use cases include: identifying seeded versus user-defined segments via SEEDED_FLAG; auditing which contexts expose the PARTY_HIERARCHY feature; and building a configuration extract by joining QP_SEGMENTS_B to QP_PRC_CONTEXTS_B to produce a full context-to-segment mapping for FNDLOAD or migration scripts. Concurrent program traceability is possible using PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE when an unexpected segment row appears.

Related Objects

The following objects are the most significant to understand alongside QP_SEGMENTS_B:

  • QP_PRC_CONTEXTS_B — Parent table. Join on PRC_CONTEXT_ID to retrieve the context name and context code that owns each segment.
  • QP_PRC_CONTEXTS_TL — Provides translated context names for reporting.
  • CSF_TDS_SEGMENTS — Referenced indirectly via QP_SEGMENTS_B.SEGMENT_ID (business reference). Used for CRM/Foundation segment metadata.
  • QP_PRC_CONTEXT_DENORM — Denormalized context-to-segment structure populated from this table and used by the pricing engine.
  • FND_VS_VALUES_VL / FND_VS_VALUE_SETS — Resolve the SEEDED_VALUESET_ID and USER_VALUESET_ID references to actual value sets.
  • FND_APPLICATION_VL — Resolves APPLICATION_ID to the owning application name.

These objects, combined with QP_SEGMENTS_B, provide a complete picture of pricing context configuration in Oracle EBS 12.1.1 and 12.2.2.