Search Results qp_segments_tl_u1

Overview

QP.QP_SEGMENTS_TL is the translation (TL) table for pricing segment definitions in Oracle Advanced Pricing, a module of Oracle E-Business Suite. Segments are the building blocks of pricing rules and qualifiers, allowing attributes such as customer category, item, or order type to be combined into configurable conditions. Because these names and descriptions must be presented to users in their local language, Oracle stores translatable text in a dedicated TL table rather than in the base QP_SEGMENTS_B table. This table therefore supplies the multilingual, user-facing labels that describe each segment and its seeded attributes.

The ETRM metadata classifies this object heuristically as standalone under Data Vault modeling—neither a hub, link, nor satellite in the strict sense. Practically, it functions as a classic translation satellite: it carries no independent business identity, only language-specific descriptive columns keyed back to the base pricing segment.

Key Information Stored

The table holds language-dependent text keyed by segment and language. The most significant columns are:

• SEGMENT_ID — Numeric foreign key referencing QP_SEGMENTS_B.SEGMENT_ID; the surrogate identifier linking each translation row to its base segment.
• LANGUAGE — The language code to which the translatable fields are translated.
• SOURCE_LANG — The language in which the translation was originally authored.
• SEEDED_SEGMENT_NAME (VARCHAR2 80) — Description of the seeded (Oracle-provided) segment for the given language.
• USER_SEGMENT_NAME (VARCHAR2 80) — Description of a user-created or user-modified segment.
• SEEDED_DESCRIPTION (VARCHAR2 2000) — Longer description for seeded attributes.
• USER_DESCRIPTION (VARCHAR2 2000) — Extended description for segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking row authorship and modification.

The business-key candidate is the unique index QP_SEGMENTS_TL_U1, defined over SEGMENT_ID, LANGUAGE, and (in 12.2.2) ZD_EDITION_NAME. SEGMENT_ID alone is not unique: it repeats once per translated language. The composite therefore uniquely identifies a translation row. The ZD_EDITION_NAME column supports editioning in Release 12.2.2, ensuring translations remain scoped to the correct edition.

Common Use Cases and Queries

Typical use cases include multilingual reporting, verifying translated segment labels, and diagnosing display problems where a segment name appears in the wrong language. A common query joins the TL table to its base table to retrieve localized names:

SELECT b.segment_id, t.language, t.user_segment_name
FROM   qp.qp_segments_b b,
       qp.qp_segments_tl t
WHERE  b.segment_id = t.segment_id
AND    t.language = USERENV('LANG');

Administrators may also audit which languages have been seeded:

SELECT segment_id, language, source_lang
FROM   qp.qp_segments_tl
ORDER BY segment_id;

Reporting solutions frequently use this table to expose localized pricing qualifier definitions to end users, and interfaces use it to resolve the correct display name during rule setup screens.

Related Objects

The following objects are most significant in relation to QP_SEGMENTS_TL:

• QP.QP_SEGMENTS_B — The base segment table; joined on SEGMENT_ID, supplying the language-independent definition.
• QP_SEGMENTS_TL_U1 — The unique index on SEGMENT_ID, LANGUAGE, and ZD_EDITION_NAME.
• CSF_TDS_SEGMENTS — Referenced relationship noted in the FK data.
• APPS.QP_SEGMENTS_TL — The APPS synonym through which the table is normally accessed.
• QP_SEGMENTS_VL / QP_SEGMENTS_V — Views that typically join base and TL tables for user-facing display.

Because the table is classified as standalone and references no other database object directly, dependencies flow inward from the base segment definition rather than outward to other schemas.