Results for “psb_budget_year_types_tl”

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

Overview

The PSB_BUDGET_YEAR_TYPES_TL table belongs to the PSB — Public Sector Budgeting product family within Oracle E-Business Suite. PSB is documented as obsolete in the ETRM metadata, meaning it is legacy functionality retained for backward compatibility rather than for new implementations. This table provides multiple-language support details for budget year types, functioning as the translation (TL) table that accompanies the base PSB_BUDGET_YEAR_TYPES_B table. In Oracle EBS multilingual data models, a _TL table stores the translated, language-dependent descriptive attributes — typically the user-facing name and description — keyed by both the underlying entity identifier and a LANGUAGE code.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone. A reasonable modeling suggestion is therefore to treat it as a satellite-like construct attached to the base budget year type entity, where BUDGET_YEAR_TYPE_ID identifies the parent entity and LANGUAGE supplies the natural child key for each translated row. The standalone classification reflects that the mined foreign-key structure did not surface external dependencies for this table.

The ETRM metadata explicitly notes that the object is not implemented in this database, so the description here is based on the documented physical schema rather than live installation evidence.

Key Information Stored

The documented physical schema contains ten columns. The most significant are:

• BUDGET_YEAR_TYPE_ID — the surrogate identifier of the budget year type. This is the foreign-key column linking back to the base entity and is the first component of the primary key.
• LANGUAGE — the language code identifying which translated row is stored. It is the second component of the primary key and distinguishes each translation.
• NAME — the translated, user-facing name of the budget year type. Note that the metadata lists NAME as part of the declared PSB_BUDGET_YEAR_TYPES_TL_PK primary key alongside BUDGET_YEAR_TYPE_ID and LANGUAGE.
• DESCRIPTION — the translated long description associated with the budget year type.
• SOURCE_LANG — the source language from which a translation was derived, used by the EBS translation framework to track the origin language of the row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard Oracle EBS WHO audit columns that capture creation and last-modification metadata for each row.

The metadata documents the unique index PSB_BUDGET_YEAR_TYPES_TL_U1 on (BUDGET_YEAR_TYPE_ID, LANGUAGE), which is the business-key candidate ensuring one translated row per language per budget year type. The surrogate primary key PSB_BUDGET_YEAR_TYPES_TL_PK is documented as (BUDGET_YEAR_TYPE_ID, LANGUAGE, NAME).

Common Use Cases and Queries

Typical usage resolves the translated display name for a budget year type in a given language. A representative pattern joins the translation table to the base table and filters on the session or requested language:

• Retrieve all translations for a budget year type: SELECT BUDGET_YEAR_TYPE_ID, LANGUAGE, NAME, DESCRIPTION FROM PSB_BUDGET_YEAR_TYPES_TL WHERE BUDGET_YEAR_TYPE_ID = :id.
• Resolve the name for a specific language: filter with WHERE LANGUAGE = USERENV('LANG') or an explicit language code, then compare against the _B base row.
• Report coverage of translations, identifying entities missing a row for a target language, using an outer join from the base table to this one.
• Audit reporting on LAST_UPDATED_BY and LAST_UPDATE_DATE to track recently maintained translated descriptions.

Because the product is obsolete, these queries are primarily relevant to legacy reporting, migration assessment, or data-archiving exercises rather than new development.

Related Objects

• PSB_BUDGET_YEAR_TYPES_B — the base (non-translated) table; joined on BUDGET_YEAR_TYPE_ID. This is the primary parent entity for the translation rows.
• PSB_BUDGET_YEAR_TYPES_TL_U1 — the documented unique index enforcing one row per BUDGET_YEAR_TYPE_ID and LANGUAGE.
• PSB_BUDGET_YEAR_TYPES_TL_PK — the documented primary key constraint on BUDGET_YEAR_TYPE_ID, LANGUAGE, and NAME.
• PSB budget year setup pages — the EBS forms and concurrent programs that read translated names for display in the budgeting application.
• FND_LANGUAGES — the standard language reference table validating the LANGUAGE and SOURCE_LANG codes.
• FND standard WHO columns — the audit framework populated through CREATED_BY, CREATION_DATE, and related columns.

The metadata classifies this object as standalone, with no mined foreign-key relationships beyond the base entity linkage described above.