Results for “qp_list_headers_tl_u1”

10 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

QP.QP_LIST_HEADERS_TL is the translation (TL) table for Oracle Advanced Pricing list headers within the Oracle E-Business Suite 12.1.1 and 12.2.2 releases. It stores the translatable descriptive attributes — the list NAME and DESCRIPTION — for each price list, modifier list, promotion, or deal defined in the base table QP.QP_LIST_HEADERS_B. The table is owned by the QP schema under FND Design Data QP.QP_LIST_HEADERS_TL, resides in the APPS_TS_TX_DATA tablespace with PCT FREE 10, and is documented as VALID in the ETRM repository.

In a Data Vault modeling sense, the mined relationship structure classifies QP_LIST_HEADERS_TL as satellite-leaning. It is not an independent business hub; it is a dependent descriptive satellite hanging off the QP_LIST_HEADERS_B hub, with the natural key relationship being LIST_HEADER_ID to the referenced base record, plus the LANGUAGE discriminator. This classification reflects that the table holds contextually descriptive text keyed to the parent entity, and is best treated as a satellite when designing analytical or integration models.

Key Information Stored

The table contains eleven documented columns. The most significant are summarized below, distinguishing the surrogate/primary key structure from business-key candidates.

  • LIST_HEADER_ID (NUMBER) — The surrogate that references the primary key of QP_LIST_HEADERS_B. It is the core foreign key linking the translated row to its base definition.
  • LANGUAGE (VARCHAR2) — The database language in which the NAME and DESCRIPTION text is stored. Together with LIST_HEADER_ID it forms the composite primary key QP_LIST_HEADERS_TL_PK.
  • SOURCE_LANG (VARCHAR2) — The language the text mirrors until it is actually translated into LANGUAGE. If no translation exists, edits to the source-language row propagate to this row.
  • NAME (VARCHAR2 240) — The price list name or modifier list number; a business-key candidate.
  • DESCRIPTION (VARCHAR2 2000) — The price list description or modifier list name.
  • VERSION_NO (VARCHAR2 30) — The list version number, user-defined for Promotion or Deal list types; a business-key candidate.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Two unique indexes are documented: QP_LIST_HEADERS_TL_PK (LIST_HEADER_ID, LANGUAGE) as the primary key, and QP_LIST_HEADERS_TL_U1 (NAME, VERSION_NO, LANGUAGE) as an additional uniqueness constraint and the second business-key candidate. The user query string "qp_list_headers_tl_u1" refers directly to this unique index.

Common Use Cases and Queries

A frequent scenario is multilingual reporting: retrieving list names and descriptions for a specific language. For example, the standard query pattern selects all columns from QP.QP_LIST_HEADERS_TL, filtered by LANGUAGE = 'US' and joined to QP_LIST_HEADERS_B on LIST_HEADER_ID.

Another use case is detecting untranslated text. Because SOURCE_LANG records the mirror language, a report can compare LANGUAGE against SOURCE_LANG to identify rows where translation has not been performed. Validating compliance with the QP_LIST_HEADERS_TL_U1 uniqueness rule — ensuring NAME, VERSION_NO, and LANGUAGE combinations are unique — is a common data integrity check during migrations or interfaces.

Pricing administrators also query by NAME to locate a price list or modifier and then join to the base table for operational attributes that are stored only in QP_LIST_HEADERS_B.

Related Objects

  • QP.QP_LIST_HEADERS_B — The base table holding non-translatable list header attributes; joined on LIST_HEADER_ID, and the referenced table for the only documented foreign key relationship.
  • QP_LIST_HEADERS_TL# — The documented dependent object referenced by this table.
  • The QP_LIST_HEADERS_TL_PK and QP_LIST_HEADERS_TL_U1 unique indexes — key structural dependents supporting primary-key lookups and the NAME/VERSION_NO/LANGUAGE business-key constraint.

Downstream pricing objects such as list lines and qualifiers in the QP schema typically tie to the header through LIST_HEADER_ID, making the translated header text available wherever list identity is displayed in a language-specific context.