Results for “xnc_item_actions_tl”

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

Overview

XNC_ITEM_ACTIONS_TL is the translation (language-specific) table for the base table XNC_ITEM_ACTIONS_B within the XNC — Sales for Communications product family. The XNC module belongs to Oracle's Communications industry vertical and is documented as Obsolete in Oracle EBS 12.1.1 and 12.2.2. The table's stated purpose is to hold translated information related to the XNC_ITEM_ACTIONS_B table and its translatable columns, supporting Oracle EBS Multi-Language Support (MLS) so that item action descriptions can be presented in a user's session language.

The _TL suffix follows the standard Oracle EBS MLS convention: a base (_B) table stores language-independent attributes and surrogate keys, while the corresponding _TL table stores the translated text columns, keyed by the base entity identifier plus LANGUAGE. From a Data Vault modeling perspective, the mined relationship data classifies this object heuristically as standalone. In practical terms, XNC_ITEM_ACTIONS_TL behaves as a satellite positioned over the XNC_ITEM_ACTIONS_B hub, carrying descriptive, language-dependent attributes keyed by ITEM_ACTION_ID and LANGUAGE.

Key Information Stored

The documented structure is compact. The columns appearing in the ETRM metadata are:

• ITEM_ACTION_ID — Surrogate identifier of the item action. This is the foreign key back to the base table XNC_ITEM_ACTIONS_B and forms the first component of the composite primary key.
• LANGUAGE — The Oracle language code (for example, US, FR, DE) identifying the translation row. It forms the second component of the composite primary key and is the discriminator that makes each row language-specific.

Together, ITEM_ACTION_ID and LANGUAGE constitute the primary key XNC_ITEM_ACTIONS_TL_PK, which is the object's unique index and therefore the definitive business-key candidate documented for this table. The translated descriptive text columns inherited from the _B table are not enumerated in the available metadata; in standard MLS design these would include the user-facing action name and description fields. No secondary unique indexes are documented. The metadata explicitly records that the table is not implemented in the reference database, reflecting the obsolete status of the XNC module.

Common Use Cases and Queries

The principal use case is language-aware retrieval of item action descriptions, joining the translation table to its base table so that only rows in the caller's language are returned. A typical pattern selects translated attributes for a specific language:

• Retrieve translated item action text for the session language by joining on ITEM_ACTION_ID and filtering LANGUAGE.
• Audit completeness by identifying base rows that lack a translation for a required language.
• Report the set of installed translations per item action for localization and translation-management reviews.

A representative query follows the EBS MLS idiom: select the translated columns from XNC_ITEM_ACTIONS_TL TL, joined to XNC_ITEM_ACTIONS_B B on TL.ITEM_ACTION_ID = B.ITEM_ACTION_ID, restricted with a condition such as TL.LANGUAGE = USERENV('LANG'). Because the object is obsolete and unimplemented, these patterns are primarily relevant to legacy data migration, custom extension audits, and understanding historical schema remnants rather than to new development.

Related Objects

• XNC_ITEM_ACTIONS_B — The base table this translation table serves; joined on ITEM_ACTION_ID.
• XNC_ITEM_ACTIONS_VL — The conventional MLS view that unions base and translation data and exposes translated columns transparently; where present it is the preferred access path.
• XNC_ITEM_ACTIONS_TL_PK — The primary key constraint/index on (ITEM_ACTION_ID, LANGUAGE).
• FND_LANGUAGES — Reference table for valid LANGUAGE codes used in translated rows.
• Other XNC _TL and _B tables in the Sales for Communications schema that share the same MLS design pattern.

Because the relationship data classifies this object as standalone, no additional inbound foreign keys to XNC_ITEM_ACTIONS_TL are documented beyond its link to XNC_ITEM_ACTIONS_B through ITEM_ACTION_ID.