Search Results fem_channels_tl

Overview

APPS.FEM_CHANNELS_PKG is the primary table-handler (TPK) package for the Enterprise Tax, Regulatory and Compliance Management (ETRM) "Channels" entity in Oracle E-Business Suite. Channels define value-set-based data channel definitions used by the ETRM analytical and reporting infrastructure, associating a channel with a value set and a dimension group, and exposing presentation attributes such as the channel display code and enablement, personalization, and read-only flags. Because the entity is translatable, the package operates against a _B (base) table and an associated _TL (translation) table, which is directly relevant to searches for fem_channels_tl. The package encapsulates all DML for the entity so that callers do not write against the underlying tables directly. It is classified as an OTHER API in ETRM 12.1.1 and is referenced by four other packages, indicating that it is treated as a shared dependency within the ETRM schema.

Key Procedures and Functions

The package body exposes six documented procedures:

• INSERT_ROW — Creates a new channel record. It inserts the base attributes into FEM_CHANNELS_B and then inserts the translatable name and description into FEM_CHANNELS_TL, seeding a row for every installed language returned by FND_LANGUAGES using the session language as SOURCE_LANG. It also returns the ROWID of the newly created base row.
• LOCK_ROW — Obtains a row-level lock on an existing channel record, used to serialize concurrent updates and to verify the object version number before an update.
• UPDATE_ROW — Applies changes to an existing channel, maintaining the object version number and audit columns. Where translatable columns change, it updates FEM_CHANNELS_TL for the appropriate language rather than the base table.
• DELETE_ROW — Removes a channel and its dependent translation rows, enforcing the parent/child relationship between FEM_CHANNELS_B and FEM_CHANNELS_TL.
• ADD_LANGUAGE — Installs translation rows for a newly installed language. It is invoked when a language is added to the applications instance so that existing channels gain a translation row in the new language.
• TRANSLATE_ROW — Updates only the translatable columns (channel name and description) in FEM_CHANNELS_TL for a specified language, leaving base-table attributes untouched.

Tables Accessed

• FEM_CHANNELS_B — The base table holding non-translatable channel attributes: CHANNEL_ID, VALUE_SET_ID, DIMENSION_GROUP_ID, CHANNEL_DISPLAY_CODE, ENABLED_FLAG, PERSONAL_FLAG, READ_ONLY_FLAG, OBJECT_VERSION_NUMBER, and audit columns. The package reads and writes this table for insert, update, delete, and lock operations.
• FEM_CHANNELS_TL — The translation table holding CHANNEL_NAME and DESCRIPTION keyed by CHANNEL_ID, VALUE_SET_ID, LANGUAGE, and SOURCE_LANG. INSERT_ROW populates it for every installed language; ADD_LANGUAGE and TRANSLATE_ROW maintain it thereafter.
• FND_LANGUAGES — Read during INSERT_ROW to enumerate languages with INSTALLED_FLAG of 'I' or 'B', ensuring a translation row is created for each installed language and that duplicate translation rows are avoided via a NOT EXISTS check. The session language is captured using userenv('LANG').

Usage Notes

The package is the supported programmatic entry point for creating and maintaining ETRM channels. It is typically invoked from the ETRM setup forms that maintain channel definitions, where the form calls INSERT_ROW and UPDATE_ROW for user actions and LOCK_ROW before committing changes. ADD_LANGUAGE is invoked from the standard language-installation concurrent process path, which calls the ADD_LANGUAGE routine of registered translatable entity packages. TRANSLATE_ROW is used by the translation-maintenance UI or by the standard translation upload process. Custom code that needs to manipulate channels should call these procedures rather than performing direct DML, because the package enforces the base/translation row pairing, audit-column population, and object-version handling that the rest of the ETRM schema depends upon. Note that the shipped header indicates a PL/SQL body version comparable to the 12.1.1 file set, and the same signature is retained in 12.2.2.