Search Results pa_amount_types_tl_u1

Overview

PA.PA_AMOUNT_TYPES_TL is the translation (multi-lingual) table for Project Accounting amount types in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to provide multi-lingual support for amount type names. Every amount type defined in the base table PA_AMOUNT_TYPES_B is paired with one or more rows in this table, one per language into which the amount type name has been translated. This separation of language-independent attributes (base table) from language-dependent attributes (translation table) is the standard EBS MLS (Multi-Language Support) design pattern, and it allows users to see amount type names rendered in their session language while preserving a single canonical identifier.

The object resides in the PA schema under FND Design Data PA.PA_AMOUNT_TYPES_TL, with status VALID, and is stored in the APPS_TS_TX_DATA tablespace at PCT Free 40. Its unique index PA_AMOUNT_TYPES_TL_U1 is created in APPS_TS_TX_IDX.

From a Data Vault modeling perspective, the mined relationship data classifies this object as standalone. As a modeling suggestion, a translation table of this kind is most naturally treated as a satellite attached to a hub representing the amount type business key, since it carries descriptive, language-specific attributes rather than relationships between entities. The presence of ZD_EDITION_NAME in the unique key reflects the editioning/online patching architecture used from 12.2 onward.

Key Information Stored

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

• AMOUNT_TYPE_ID (NUMBER(15)) — the system-generated number that uniquely identifies the amount type. This is the surrogate key and the join column back to the base table. It is the first column of the unique index PA_AMOUNT_TYPES_TL_U1.
• LANGUAGE (VARCHAR2) — the defined language code for the row's translated columns. It is the second column of the unique index.
• ZD_EDITION_NAME (VARCHAR2(30)) — the edition name, the third column of the unique index. Because it participates in the unique key, the complete business-key candidate is the composite (AMOUNT_TYPE_ID, LANGUAGE, ZD_EDITION_NAME).
• AMOUNT_TYPE_NAME (VARCHAR2(80)) — the translated name of the amount type, and the principal payload of this table.
• SOURCE_LANG (VARCHAR2) — the actual language of the row's translated columns, used to identify the originating language of the text.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Who columns recorded automatically by EBS for auditing and concurrency control.

Note that AMOUNT_TYPE_NAME is not mandatory at the database level, and the uniqueness constraint applies to the identifier/language/edition combination, not to the translated text itself.

Common Use Cases and Queries

Typical use cases include reporting amount type names in a user's language, validating that translations exist for all required languages, and exporting amount type reference data for integration or conversion projects. A standard retrieval pattern joins the translation table to the base table on the surrogate key:

SELECT b.amount_type_id, t.amount_type_name FROM pa.pa_amount_types_b b, pa.pa_amount_types_tl t WHERE b.amount_type_id = t.amount_type_id AND t.language = USERENV('LANG');

A direct query against the table, as published in the ETRM documentation, is:

SELECT AMOUNT_TYPE_ID, LANGUAGE, SOURCE_LANG, AMOUNT_TYPE_NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, ZD_EDITION_NAME FROM PA.PA_AMOUNT_TYPES_TL;

Common reporting variants include filtering by LANGUAGE to audit coverage, grouping by AMOUNT_TYPE_ID to detect missing translations, and comparing SOURCE_LANG against LANGUAGE to identify untranslated source rows. Because the table is MLS-enabled, ad hoc SQL should always constrain LANGUAGE to avoid returning duplicate rows per amount type.

Related Objects

• PA.PA_AMOUNT_TYPES_B — the base table holding language-independent amount type attributes. PA_AMOUNT_TYPES_TL.AMOUNT_TYPE_ID references PA_AMOUNT_TYPES_B, making this the primary join for any query returning translated names.
• PA.PA_AMOUNT_TYPES_TL# — the editioning view associated with this table, referenced by PA_AMOUNT_TYPES_TL and used in the 12.2 online patching model.
• PA_AMOUNT_TYPES_TL_U1 — the unique index on (AMOUNT_TYPE_ID, LANGUAGE, ZD_EDITION_NAME) in APPS_TS_TX_IDX, which enforces one translated name per amount type per language.
• FND_LANGUAGES — the EBS language reference table, useful for validating the LANGUAGE and SOURCE_LANG values present in this table.
• Amount type consumers in Project Accounting — expenditure and cost transaction tables that reference PA_AMOUNT_TYPES_B by AMOUNT_TYPE_ID and display the translated name from this table in inquiry and reporting screens.

No other database objects are documented as referenced directly by PA_AMOUNT_TYPES_TL beyond the relationship to PA_AMOUNT_TYPES_B.