Results for “pa_util_categories_tl”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_UTIL_CATEGORIES_TL is the multi-lingual support (MLS) table for Utilization Categories defined in Oracle Projects (PA). Utilization Categories are used to classify resource utilization and drive reporting, billing, and costing logic within Oracle Projects. This table stores the translated (and base-language) attributes of each utilization category so that the user-defined descriptive text can be stored, displayed, and printed in multiple languages. The table resides in the PA schema and is owned by the Oracle Projects module.

From a heuristic Data Vault modeling perspective, PA_UTIL_CATEGORIES_TL is best classified as a satellite. It carries descriptive, language-dependent attributes (such as NAME and DESCRIPTION) that are functionally dependent on the utilization category identifier, and it is tied directly to the parent entity table PA_UTIL_CATEGORIES_B via the UTIL_CATEGORY_ID foreign key. The metadata additionally classifies the object as a link in the Data Vault relationship graph, reflecting the fact that it connects to multiple reference tables (FND_LANGUAGES for both LANGUAGE and SOURCE_LANG). Either interpretation is a modeling suggestion; operationally the table is a dependent child (satellite) of the utilization category business entity.

Key Information Stored

The table contains 10 documented columns. The most significant are summarized below.

  • UTIL_CATEGORY_ID — Surrogate primary key column referencing the parent entity PA_UTIL_CATEGORIES_B. This is the core identifier linking translations to a utilization category.
  • LANGUAGE — The language code for the row, referencing FND_LANGUAGES. Together with UTIL_CATEGORY_ID it forms the first unique index (PA_UTIL_CATEGORIES_TL_U1), the true business key of the MLS layer.
  • SOURCE_LANG — The source (base) language of the translation, also referencing FND_LANGUAGES. This indicates the language from which the row's content originated.
  • NAME — The translated name of the utilization category. Together with LANGUAGE it forms the second unique index (PA_UTIL_CATEGORIES_TL_U2), enforcing that a category name is unique within a language.
  • DESCRIPTION — The translated descriptive text for the utilization category.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle who-columns capturing audit and concurrency information for each translation row.

Two unique indexes are documented: PA_UTIL_CATEGORIES_TL_U1 on (UTIL_CATEGORY_ID, LANGUAGE) and PA_UTIL_CATEGORIES_TL_U2 on (NAME, LANGUAGE). These represent business-key candidates, while UTIL_CATEGORY_ID remains the surrogate primary key component.

Common Use Cases and Queries

Reporting and integration scenarios typically join this table to the base table to retrieve a category's name in a specific language. A common query filters on a target language and resolves the parent entity:

  • Fetching the translated name and description for a given category: SELECT t.NAME, t.DESCRIPTION FROM PA.PA_UTIL_CATEGORIES_TL t WHERE t.UTIL_CATEGORY_ID = :id AND t.LANGUAGE = USERENV('LANG');
  • Language-completeness audits: SELECT UTIL_CATEGORY_ID, LANGUAGE FROM PA.PA_UTIL_CATEGORIES_TL WHERE UTIL_CATEGORY_ID NOT IN (SELECT UTIL_CATEGORY_ID FROM ... WHERE LANGUAGE = 'US');
  • Joining to the parent: SELECT b.*, t.NAME, t.DESCRIPTION FROM PA.PA_UTIL_CATEGORIES_B b, PA.PA_UTIL_CATEGORIES_TL t WHERE b.UTIL_CATEGORY_ID = t.UTIL_CATEGORY_ID AND t.LANGUAGE = 'US';
  • Validating SOURCE_LANG consistency against the FND_LANGUAGES reference table.

Related Objects

  • PA_UTIL_CATEGORIES_B — Parent base table; joined on UTIL_CATEGORY_ID (foreign key). Holds language-independent attributes.
  • FND_LANGUAGES — Referenced twice: LANGUAGE and SOURCE_LANG provide the list of installed languages and the translation source language.
  • PA_UTIL_CATEGORIES_TL_U1 / _U2 — Unique indexes enforcing the (UTIL_CATEGORY_ID, LANGUAGE) and (NAME, LANGUAGE) business keys.
  • Oracle Projects APIs and concurrent programs that maintain utilization category definitions read and write translations through this table in conjunction with PA_UTIL_CATEGORIES_B.