Search Results availability_in_basic

Overview

The APPS.QP_SEGMENTS_V view is a reporting and integration object within the Oracle Advanced Pricing (QP) module. It presents a complete, language-resolved catalog of pricing segment definitions, combining the physical attributes of each segment with its translated display name. The view is documented as containing "all details about all the attributes along with their translated names," and it is valid and available in both Oracle E-Business Suite 12.1.1 and 12.2.2.

Its principal architectural value is that it performs the language join at the database layer, so consumers do not need to query the base and translation tables separately or apply their own USERENV('LANG') filtering logic. For the search term segment_mapping_column, this view is the authoritative source: the SEGMENT_MAPPING_COLUMN column is exposed directly from the base table and identifies the underlying pricing attribute column to which a segment is mapped. This makes the view central to diagnosing how pricing rule conditions and qualifiers are physically resolved against the pricing transaction tables.

Underlying Base Objects

QP_SEGMENTS_V is defined over two synonyms, QP_SEGMENTS_B and QP_SEGMENTS_TL:

• QP_SEGMENTS_B — the base (non-translated) table, holding all descriptive and control attributes for each segment, joined on SEGMENT_ID.
• QP_SEGMENTS_TL — the translation table, supplying SEEDED_SEGMENT_NAME and USER_SEGMENT_NAME, filtered by T.LANGUAGE = USERENV('LANG').

The join is a one-to-one equijoin on SEGMENT_ID, which guarantees that exactly one translation row — the one matching the session's current language — is returned per segment, preventing duplicate rows regardless of how many translated languages exist in the TL table. Nearly every column is passed through from QP_SEGMENTS_B without transformation; the view adds no computed expressions other than the language predicate. Consequently, the view behaves as a thin, read-only projection suitable for query rather than for DML.

Key Columns

• SEGMENT_ID — primary identifier and join key.
• SEGMENT_CODE — internal code uniquely naming the segment.
• SEGMENT_MAPPING_COLUMN — the physical pricing column to which the segment maps; the definitive linkage between a segment definition and its stored data.
• PRC_CONTEXT_ID — the pricing context to which the segment belongs.
• AVAILABILITY_IN_BASIC — flag indicating whether the segment is available in the basic pricing context.
• SEEDED_FLAG, SEEDED_PRECEDENCE, USER_PRECEDENCE — Oracle-seeded versus customer-defined indicators and their precedence ordering.
• SEEDED_VALUESET_ID, USER_VALUESET_ID and SEEDED_FORMAT_TYPE, USER_FORMAT_TYPE — value set and format configuration, distinguishing seeded from user overrides.
• APPLICATION_ID — owning application for the seeded definition.
• SEEDED_SEGMENT_NAME, USER_SEGMENT_NAME — the translated names from QP_SEGMENTS_TL.
• CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN and the PROGRAM_* columns — standard audit and concurrent program tracking.

Common Use Cases and Queries

Typical uses include validating segment-to-column mappings before configuring pricing rules, enumerating seeded segments delivered by Oracle, and building custom reports that require translated segment names.

• Resolve a mapping column from a segment code:

  SELECT segment_code, segment_mapping_column
  FROM   qp_segments_v
  WHERE  segment_code = :p_segment_code;

• List all customer-defined segments in the current language:

  SELECT segment_id, user_segment_name, segment_mapping_column, prc_context_id
  FROM   qp_segments_v
  WHERE  seeded_flag = 'N'
  ORDER  BY user_precedence;

• Audit seeded segments and their mapping columns:

  SELECT segment_code, seeded_segment_name, segment_mapping_column, application_id
  FROM   qp_segments_v
  WHERE  seeded_flag = 'Y';

• Find segments sharing a mapping column to detect overlaps:

  SELECT segment_mapping_column, COUNT(*)
  FROM   qp_segments_v
  GROUP  BY segment_mapping_column
  HAVING COUNT(*) > 1;