Search Results psb_attributes_tl_pk

Overview

PSB_ATTRIBUTES_TL is the translation (multi-language) table for attribute definitions used by the Public Sector Budgeting (PSB) module in Oracle EBS 12.1.1 and 12.2.2. PSB is the budgeting engine that supports public-sector entities in preparing, submitting, and consolidating budget requests. Within that flow, budget attributes drive how budget lines, worksheets, and financial structures are described, validated, and reported. The _TL suffix denotes an Oracle Applications "translation" or "_TL" table: it stores language-dependent descriptive text (such as a display prompt and a translated name) for a language-independent attribute entity, so that the same attribute can present different labels depending on the session's language.

The base, language-independent attribute data lives in a corresponding non-translated table (typically PSB_ATTRIBUTES), keyed by ATTRIBUTE_ID. PSB_ATTRIBUTES_TL supplies the per-language text overlay. A common Oracle implementation pattern is to keep one row per language per attribute, allowing the application to render attribute names and prompts in the logged-in user's language while the underlying budget logic remains language-neutral. The table owner is the PSB schema, and its documented status is VALID. Consistent with the mined Data Vault classification metadata, this object is best modeled as a standalone satellite carrying descriptive (non-key) history for the attribute hub; the language dimension and effective-dating style columns make it a natural fit for a satellite rather than a hub or link.

Key Information Stored

The table contains 10 documented columns. The most important are:

• ATTRIBUTE_ID — surrogate key tying the translation row to the base attribute; appears in the primary key and in the business unique index.
• NAME — the language-specific attribute name shown to users; part of the composite primary key.
• DISPLAY_PROMPT — the localized prompt/label presented on budget entry screens and reports.
• LANGUAGE — the language code (e.g., US, DE, FR) indicating which session language the row serves; part of both keys.
• SOURCE_LANG — the language the row was translated from, supporting Oracle's standard translation workflow.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit who/when columns tracking the most recent change.
• CREATED_BY, CREATION_DATE — standard audit columns recording row creation.

The documented primary key, PSB_ATTRIBUTES_TL_PK, is composite over (NAME, LANGUAGE, ATTRIBUTE_ID). The unique index PSB_ATTRIBUTES_TL_U1 on (ATTRIBUTE_ID, LANGUAGE) is the stronger business-key candidate, since it guarantees exactly one translation row per attribute per language and is the natural lookup path for retrieving the correct localized text.

Common Use Cases and Queries

The primary use case is localized display of PSB attribute definitions. A typical query retrieves the translated NAME and DISPLAY_PROMPT for a given attribute in the user's language:

• SELECT name, display_prompt FROM psb_attributes_tl WHERE attribute_id = :id AND language = USERENV('LANG');
• Joining to the base table: SELECT a.attribute_id, t.name, t.display_prompt FROM psb_attributes a, psb_attributes_tl t WHERE a.attribute_id = t.attribute_id AND t.language = USERENV('LANG');

Reporting uses include multi-language attribute listings for configuration review, translation-completeness checks (attributes lacking a row for a given language), and audit of when prompts were last changed via LAST_UPDATE_DATE. Administrators also use it to verify that SOURCE_LANG and LANGUAGE pairs are consistent during patching or translation uploads. Note that USERENV('LANG') returns the session language, and Oracle stores the language code accordingly.

Related Objects

Because the mined relationship data classifies this table as standalone, no explicit foreign keys are documented. However, the following objects are significant by design and join key:

• PSB_ATTRIBUTES (base attribute table) — joined on ATTRIBUTE_ID; holds the language-independent attribute definition.
• FND_LANGUAGES — reference table for the LANGUAGE and SOURCE_LANG codes.
• PSB_ATTRIBUTES_TL_PK — the composite primary key constraint (NAME, LANGUAGE, ATTRIBUTE_ID).
• PSB_ATTRIBUTES_TL_U1 — the unique business-key index on (ATTRIBUTE_ID, LANGUAGE).
• FND_NEW_MESSAGES / FND_LOOKUPS — frequently consulted alongside _TL tables for localization and configuration maintenance.

Where custom reporting requires multilingual budget output, PSB_ATTRIBUTES_TL is the authoritative source for localized attribute names and prompts in the PSB schema.